Use the following procedure to register a resource to a resource pool:
Register VM Host Resources (Global Zone)
In the ROR console orchestration tree, right-click the target VM pool, and select [Register Resources] from the popup menu.
The [Register Resources] dialog is displayed.
Select the VM host to register.
Click <OK>.
For details, refer to "14.1 VM Host Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Point
When deploying multiple L-Servers to an L-Platform at the same time, deploy the same number of L-Servers as the number of VM hosts in the VM pool.
When using multiple L-Platforms that use the same network, create different VM pools for each L-Platform.
Register Disk Resources
Register the disks used in the non-global zone as disk resources.
When migrating a non-global zone for virtual L-Servers, register the disks shared between multiple global zones as disk resources defined to be shared.
Disk resources can be registered by executing the rcxadm disk register command.
For details on the rcxadm disk register command, refer to "3.3 rcxadm disk" in the "Reference Guide (Command/XML) CE".
To register disk resources, an XML file that contains the information of the disk resources to be registered is necessary.
For the definition of the XML file, refer to "15.4.3 Disk Resources [Solaris Zones]" in the "Reference Guide (Command/XML) CE".
For the commands that support creation of XML files, refer to "5.24 rcxvmdisk" and "5.25 rcxvmdiskagt" in the "Reference Guide (Command/XML) CE".
Register Network Resources
If the NIC and network resources are connected when an L-Server is created, the settings matching the network resource definition will be registered automatically for the VM host that the L-Server will operate on.
For details, refer to "C.7.4 Manual Network Configuration".
Check the information of VLANs and subnets to which the NICs for the VM guest to be imported are connected. These settings are not necessary when there are already network resources corresponding to the combinations of VLANs and subnets. When there are no network resources, use the following procedure to create a new network resource.
In the ROR console orchestration tree, right-click the target network pool, and select [Create Network Resource].
When creating a new network resource, select [New].
When creating a resource using an already registered admin LAN subnet, select [Using existing admin subnet].
The [Create a network resource] dialog is displayed.
Enter the items necessary for network resources.
VLAN ID
When using a VLAN, specify the value. When not using a VLAN, specify an arbitrary VLAN ID that is not used for already created network resource and will not be used in the future.
Uplink port
Do not specify anything.
Detail configuration
Do not configure anything.
For details on how to add the NIC information to the L-Server, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE".
Register Network Device Resources
Create a network resource to be used on the L-Platform. If the type of the network devices is Firewall or SLB, register them to the network pool.
For details, refer to "14.4 Network Devices" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Register Virtual Image Resources
Register the virtual image resources used when creating virtual L-Servers in the resource pool.
It is necessary to create a BladeLogic virtual package in advance and register it with Resource Orchestrator.
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".
