This section explains how to create and import cloning images.
Use the following procedure to register cloning images in the image pool.
Create Cloning Images
Copy the "Sample Image File" prepared in "Storage Location of Sample Image" in the Resource Orchestrator manager by default to the "Image Storage Directory".
If necessary, edit the sample image file, and create a new cloning image.
When creating a new image file, refer to "Advisory Notes when Creating a New Image File".
Import Cloning Images
Execute the rcxadm image refresh command to import the cloning image.
For details, refer to "4.1 rcxadm image" in the "Reference Guide (Command/XML) CE".
Register Cloning Images in the Image Pool
Register the cloning image in the image pool.
For details, refer to "14.7.1 Virtual Image Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Storage Location of Sample Image
The storage location of the sample image is as follows:
When using the sample image itself, copy the whole directory in "Image Storage Directory".
[Windows Manager]
Installation_folder\SVROR\Manager\etc\vm_image\zone\sample\zone_sol11
[Linux Manager]
/etc/opt/FJSVrcvmr/vm_image/zone/sample/zone_sol11
Sample Image File
zone_sol11
The files for configuring images for Solaris 11 are as follows:
None of these files can be omitted. If there is a file which does not exist, L-Server creation will end abnormally.
For details on each file, refer to the Solaris manuals.
zone.conf
The following is the file which describes the output result of the following command:
zonecfg -z Non-global_zone_name export |
However, it is necessary to delete the descriptions of zonepath and anet.
The non-global zone is created based on this file.
Describe the following in the sample file.
create -b |
Note
When creating an L-Server, add or modify the following resources and attributes as necessary.
Therefore, do not describe resources or attributes which are in exclusive relationships with these attributes in zone.conf.
zonepath
Even if zonepath is described, it is ignored if there are no problems in the content
When there are problems in the zonepath description, the L-Server creation process will end abnormally.
pool
capped-memory: physical
capped-cpu: ncpus
anet
Even if the anet resource is described, the L-Server will be created successfully if there are no problems in the content.
However, after creation MAC addresses may conflict during operation. In this case, the L-Server will fail to start after stopping.
When there are problems in the descriptions in the anet resource, L-Server creation will end abnormally.
fs
Example combination of resources and attributes in exclusive relationships
capped-cpu and dedicated-cpu
anet and ip-type=shared
ai_manifest.xml
The AI manifest specified when installing an OS.
The package and the disk partition to install are defined in the XML format.
When creating an L-Server, SOLARIS_REPO in the file is replaced with the global zone settings.
The parts that cannot be modified by the user are those underlined.
<?xml version="1.0" encoding="UTF-8"?>
<!--
All rights reserved, Copyright Fujitsu LIMITED 2014
-->
<!DOCTYPE auto_install SYSTEM "file:///usr/share/install/ai.dtd.1">
<auto_install>
<ai_instance name="zone_ror">
<target>
<logical>
<zpool name="rpool">
<filesystem name="export" mountpoint="/export"/>
<filesystem name="export/home"/>
<be name="solaris">
<options>
<option name="compression" value="on"/>
</options>
</be>
</zpool>
</logical>
</target>
<software type="IPS">
<destination>
<image>
<!-- Specify locales to install -->
<facet set="false">facet.locale.*</facet>
<facet set="true">facet.locale.de</facet>
<facet set="true">facet.locale.de_DE</facet>
<facet set="true">facet.locale.en</facet>
<facet set="true">facet.locale.en_US</facet>
<facet set="true">facet.locale.es</facet>
<facet set="true">facet.locale.es_ES</facet>
<facet set="true">facet.locale.fr</facet>
<facet set="true">facet.locale.fr_FR</facet>
<facet set="true">facet.locale.it</facet>
<facet set="true">facet.locale.it_IT</facet>
<facet set="true">facet.locale.ja</facet>
<facet set="true">facet.locale.ja_*</facet>
<facet set="true">facet.locale.ko</facet>
<facet set="true">facet.locale.ko_*</facet>
<facet set="true">facet.locale.pt</facet>
<facet set="true">facet.locale.pt_BR</facet>
<facet set="true">facet.locale.zh</facet>
<facet set="true">facet.locale.zh_CN</facet>
<facet set="true">facet.locale.zh_TW</facet>
</image>
</destination>
<source>
<publisher name="solaris">
<origin name="SOLARIS_REPO"/
</publisher>
</source>
<software_data action="install">
<name>pkg:/entire@latest</name>
<name>pkg:/group/system/solaris-small-server</name>
</software_data>
</software>
</ai_instance>
</auto_install> |
sc_profile.xml
The SC profile specified when installing an OS.
The information configured in the OS, such as the host name or IP address is defined in the XML format.
The parts that cannot be modified by the user are those underlined.
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1"> <service_bundle type="profile" name="sysconfig"> <service version="1" type="service" name="system/config-user"> <instance enabled="true" name="default"> <property_group type="application" name="root_account"> <propval type="astring" name="login" value="root"/> <propval type="astring" name="password" value="ROOT_PASSWORD"/> <propval type="astring" name="type" value="ROOT_TYPE"/> </property_group> <property_group type="application" name="user_account"> <propval type="astring" name="login" value="USER_NAME"/> <propval type="astring" name="password" value="USER_PASSWORD"/> <propval type="astring" name="type" value="normal"/> <propval type="count" name="gid" value="10"/> <propval type="astring" name="shell" value="/usr/bin/bash"/> <propval type="astring" name="roles" value="root"/> <propval type="astring" name="profiles" value="System Administrator"/> <propval type="astring" name="sudoers" value="ALL=(ALL) ALL"/> </property_group> </instance> </service> <service version="1" type="service" name="system/timezone"> <instance enabled="true" name="default"> <property_group type="application" name="timezone"> <propval type="astring" name="localtime" value="TIMEZONE"/> </property_group> </instance> </service> <service version="1" type="service" name="system/environment"> <instance enabled="true" name="init"> <property_group type="application" name="environment"> <propval type="astring" name="LANG" value="LOCALE"/> </property_group> </instance> </service> <service version="1" type="service" name="system/identity"> <instance enabled="true" name="node"> <property_group type="application" name="config"> <propval type="astring" name="nodename" value="HOSTNAME"/> </property_group> </instance> </service> <service version="1" type="service" name="system/console-login"> <instance enabled="true" name="default"> <property_group type="application" name="ttymon"> <propval type="astring" name="terminal_type" value="vt100"/> </property_group> </instance> </service> <service version="1" type="service" name="network/physical"> <instance enabled="true" name="default"> <property_group type="application" name="netcfg"> <propval type="astring" name="active_ncp" value="DefaultFixed"/> </property_group> </instance> </service> <service version="1" type="service" name="network/install"> <instance enabled="true" name="default"> <property_group type="application" name="install_ipv4_interface"> <propval type="astring" name="address_type" value="ADDRESS_TYPE"/> <propval type="net_address_v4" name="static_address" value="IP_ADDRESS"/> <propval type="astring" name="name" value="LINK_NAME/v4"/> <propval type="net_address_v4" name="default_route" value="DEFAULT_ROUTE"/> </property_group> <property_group type="application" name="install_ipv6_interface"> <propval type="astring" name="stateful" value="yes"/> <propval type="astring" name="stateless" value="yes"/> <propval type="astring" name="address_type" value="addrconf"/> <propval type="astring" name="name" value="LINK_NAME/v6"/> </property_group> </instance> </service> <!-- <service version="1" type="service" name="system/name-service/switch"> <property_group type="application" name="config"> <propval type="astring" name="default" value="files"/> <propval type="astring" name="host" value="files dns"/> <propval type="astring" name="printer" value="user files"/> </property_group> <instance enabled="true" name="default"/> </service> <service version="1" type="service" name="system/name-service/cache"> <instance enabled="true" name="default"/> </service> <service version="1" type="service" name="network/dns/client"> <property_group type="application" name="config"> <property type="net_address" name="nameserver"> <net_address_list> <value_node value="DNS_ADDR1"/> <value_node value="DNS_ADDR2"/> <value_node value="DNS_ADDR3"/> </net_address_list> </property> <property type="astring" name="search"> <astring_list> <value_node value="SEARCH_DOM1 SEARCH_DOM2 SEARCH_DOM3"/> </astring_list> </property> </property_group> <instance enabled="true" name="default"/> </service> --> </service_bundle> |
Image Storage Directory
[Windows Manager]
Installation_folder\SVROR\Manager\etc\vm_image\zone\sol11
[Linux Manager]
/etc/opt/FJSVrcvmr/vm_image/zone/sol11
Advisory Notes when Creating a New Image File
Advisory notes when creating a new image file are as follow:
Create a new image based on the sample image.
Do not modify the file name of the sample image.
Do not modify the following values described in the sample image file.
The definition values described in zone.conf, and ai_manifest.xml
New definitions can be added.
Definition values of the following items described in sc_profile.xml
Password of the root account (ROOT_PASSWORD)
root type (ROOT_TYPE)
Setting items of user accounts (USER_NAME, USER_PASSWORD)
Time zone (TIMEZONE)
System locale (LOCALE)
Host name (HOSTNAME)
IP address type (ADDRESS_TYPE)
IP address, subnet mask (IP_ADDRESS)
Default gateway (DEFAULT_ROUTE)
NIC name (LINK_NAME)
The image name detected using the rcxadm image refresh command will be the same as the created folder name.
Example
When a folder named "test" is created to create the image for Solaris 11, the image named "test" is detected.
Installation_folder\SVROR\Manager\etc\vm_image\zone\sol11\test
The directory name must start with an alphabetic character (upper or lower case), and can contain up to 32 alphanumeric characters or underscores ("_"). Images not conforming to this condition cannot be imported.
Use the following procedure to register cloning images in the image pool.
Create a BladeLogic virtual package
From the BladeLogic console, create a BladeLogic virtual package in the following folder.
Depot/ROR/Solaris/vm/container |
The name of the virtual package must start with an alphabetic character (upper or lower case), and can contain up to 32 alphanumeric characters or underscores ("_").
For details, contact Fujitsu technical staff.
Point
There are two methods to create packages. One is to copy the virtual package created when registering the server management software, and the other is to create a new package without using the package created in advance.
Create a package using one of the following methods:
When Creating a New Virtual Package
Configure any necessary additional settings after setting the following items:
[General Settings]
- Zone Name: zone
- Zone Path: /zone
- Resource Pool: pool_resource
- Auto boot on host reboot: unchecked
- Boot Zone after creation: unchecked
- Processor Settings: Default
- Memory Settings: Default
[Network Settings]
- IP Type: Exclusive
[ZFS Data Sets]
- Only UFS can be used as a file system. Do not specify this item.
[Inherited Package-Directories]
- Zone Type: Whole Root
[Custom Attributes]
- zone.cpu-cap is reconfigured, when creating or modifying an L-Server.
When Copying a Virtual Package
Copy the BladeLogic virtual package stored in the following location.
Depot/ROR/Solaris/vm/container/template/Zones |
In the virtual package, only the minimum parameters necessary for operations described in "When Creating a New Virtual Package" are configured. Modify the parameters depending on your environment.
The virtual package is added to Resource Orchestrator, when server management software is registered.
When deploying the created images to VM hosts in Solaris Zones, the images can also be used for other VM hosts.
Register the BladeLogic virtual package with Resource Orchestrator
Refer to "17.5.1 Collecting and Registering" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register the virtual image resource in the resource pool
For details, refer to "14.7.1 Virtual Image Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
