This section explains how to create an L-Server using an L-Server template.
Use the following procedure to create an L-Server using an L-Server template:
Select the ROR console orchestration tree. Select an L-Server template on the [Template List] tab of the Main Panel, and click [Create].
The [Create an L-Server] dialog is displayed.
On the [General] tab, set the following items.
Enter a name for the L-Server.
For Physical L-Servers
Enter up to 64 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), or hyphens ("-").
For Virtual L-Servers
[VMware] [Hyper-V] [OVM for SPARC] [Citrix Xen]
Enter up to 64 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), periods ("."), and hyphens ("-").
[Xen] [OVM for x86 2.2]
Periods (".") cannot be used.
[KVM] [OVM for x86 3.x]
Enter up to 64 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), or hyphens ("-").
[OVM for x86 2.2]
Enter the location using 32 characters or less.
[Solaris Zones]
Enter up to 52 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), periods ("."), and hyphens ("-"). Enter up to 63 characters beginning with an alphanumeric character (upper or lower case), and including alphanumeric characters (upper or lower case), underscores ("_"), periods ("."), and hyphens ("-"). However, names which start with "SUNW" cannot be used.
The name "global" cannot be used when the configuration uses the same name for both a virtual L-Server and a VM. For the configuration to use the same name for both a virtual L-Server and a VM machine, refer to "Table 17.17 List of Items Specified in the Definition File" of "17.8.1 Installation".
Select a resource folder or a tenant to store L-Servers.
Specify an L-Server template created following "15.1.2 Creating" in the "Setup Guide CE".
The L-Server template specified from the [Template List] tab is displayed. Check the specifications (CPU performance, memory capacity, disk capacity (multiple)) for the L-Server to create.
For Physical
Model name, disk capacity (multiple) are displayed.
For Virtual
CPU performance, memory capacity, and disk capacity (multiple) are displayed.
[VMware] [Hyper-V]
When using templates with "all" specified for "ServerImageLink", all disks (system disk and data disks) are deployed as they are in the cloning image.
To check the disk configuration of the L-Server to be created, check the cloning image in advance.
Specify a cloning image to deploy.
Clicking the [Select] button displays the [Select a Cloning Image] dialog.
To manually install an operating system, select [None].
When [None] is selected, it is necessary to select the OS type on the [Server] tab.
When selecting [None], check the [Single path mode] checkbox of [FC path].
For details, refer to "16.2.2 [Server] Tab" and "16.3.2 [Server] Tab".
If you select [Deploy] from [Image deployment], the parameters for the operating system must also be specified.
For details on the items that must be set, refer to "16.2.5 [OS] Tab" and "16.3.5 [OS] Tab".
Note
When creating an L-Server specifying a cloning image, if the OS of a cloning image is Linux, the L-Server is created using the user name and password used when the cloning image was created.
It is recommended to change the password after creating an L-Server to maintain security.
When deploying cloning images, the OS image included in a cloning image is used, but the values of CPU, memory and network are overwritten with the values used when creating an L-Server.
[VMware] [Hyper-V]
When using templates with "all" specified for "ServerImageLink", all disks are created in the same location.
When selecting a storage location, only specify system disks on the [Disk] tab.
If different locations are specified for system disks and data disks, L-Server creation with cloning image deployment may fail.
Disks are created in the same location even if there is a mixture of disks with Thin Provisioning attributes and disks with no Thin Provisioning attributes in the cloning image.
When the setting of "Increasing disk capacity(FitDiskSizeToImage)" is "false", on virtual products, VM guests are temporarily created with the disk size of an image. Therefore, a record of the disk size temporarily created may remain in the log on virtual products.
When creating a virtual L-Server with a cloning image specified, the provisioning attribute of the cloning image takes preference over the provisioning attribute of the storage pool.
Information
For virtual L-Servers, when creating an L-Server, even if the size of the system disk is specified in advance, if the specified size differs from that of the deployed cloning image, the size will be changed to that of the deployed cloning image.
However, the operation explained above is only when the setting of "Increasing disk capacity(FitDiskSizeToImage)" is true, or is not specified.
When the setting of "Increasing disk capacity(FitDiskSizeToImage)" is "false", the disk with the larger disk capacity when the disk size of the image and the disk size of the L-Server template (specified by the DiskSize element, when using XML definitions) are compared, is allocated.
When the data disk size contained in an image is increased, the setting of "Increasing disk capacity(FitDiskSizeToImage)" should be "false", and [ServerImageLink] should be set to "all" L-Server templates.
[VMware] [Hyper-V]
Depending on the server virtualization software used, some restrictions may apply to the operating systems that parameters can be set for and the prerequisites for performing the settings.
For details, refer to the manual of server virtualization software.
Basic software (OS) that can be used on an L-Server is limited to software supported by the server virtualization software.
The image to deploy can be specified when creating an L-Server. Image deployment for Resource Orchestrator uses the following functions of the server virtualization software:
Server Virtualization Software | Function |
|---|---|
VMware vSphere 4.0 | Template, guest OS customization |
Microsoft(R) System Center Virtual Machine Manager 2008 R2 | Template, guest OS operating system profile |
[Solaris Zones]
The cloning image needs to be specified.
When creating an L-Server for which only a configuration definition exists, check the [None (Definition only)] checkbox.
When an L-Server for which only a configuration definition has been created is started, resources will be allocated.
For details, refer to "17.8.2.1 Allocating Resources".
When modifying the configuration of an L-Server for which only a configuration definition was created, refer to "17.8.2.3 Modifying Configuration Definition Information".
Select a network resource to connect to the NIC of the L-Server.
A list of the NICs defined in the L-Server template is displayed. Select the network to connect to each NIC from the [Network to connect] column.
Click the [Select] button in the [Network to connect] column.
The [Select a Network Resource] dialog is displayed.
The following items are displayed: Select the network resource to connect.
- Name (Label)
- Admin LAN
- Subnet address
- Number of addresses (Unused/Total)
For physical L-Servers, the network connection can be selected in addition to these items.
- Connect
Specify when connecting network resources.
- Do not connect
Specify when not connecting network resources, only creating a configuration definition.
Note
The network (NIC) number corresponds to a NIC number (NICIndex) + 1 that is defined in L-Server templates.
[OVM for x86 2.2]
One or more networks must be specified.
A custom label can be defined for the L-Server. User-defined labels make it easier to identify the server.
Enter a maximum of 32 characters.
A custom comment can be defined for the L-Server. For example, registering detailed work content, troubleshooting, and recovery procedures can speed up the recovery of affected applications when a problem occurs.
Enter a maximum of 256 characters.
Click the [OK] button.
The L-Server is created.
The process status can be checked in the Recent Operations area of the ROR console.
When creating a physical L-Server specifying image deployment, clicking [Cancel] in the Recent Operations area displays a confirmation dialog and stops the process.
[OVM for SPARC]
After creating an L-Server, it is necessary to carry out operations based on the environment.
For details, refer to "Operations after creating an L-Server" of "8.8.6 Creating L-Servers" in the "Setup Guide CE".
Note
Note that canceling the creation of a physical L-Server specifying image deployment does not restore the destination server to the state before image deployment took place.
When operations are canceled on the last part, the physical L-Server may remain.
Delete the physical L-Server, from the [Resource] tab on the ROR console. For details on how to delete an L-Server, refer to "17.4 Deleting".
When using a virtual L-Server template, which has inconsecutive disk number [No.], a virtual L-Server with a disk configuration different from the specified content is created.
Configure the network settings of the OS referring to the IP address and network information of the L-Server if necessary.
For details, refer to "7.8 Network Redundancy and VLAN Settings of L-Servers" in the "Setup Guide CE".
Point
When installing an operating system manually on the L-Server or using the management console of server virtualization software, select the L-Server in the orchestration tree, and operate the VM for the Guest_name displayed in [Resource Details].
The following name is automatically allocated for Guest_name:
L-Server_name - Number
Number is automatically set by Resource Orchestrator to avoid overlapping of names on server virtualization software if an L-Server with the same name is created during "Chapter 21 Resource Folder Operations". When 1,000 or more L-Servers are deployed, Number is a four digit numerical value.
For operation without numbering, refer to "Numbering VM names" in "Table 17.17 List of Items Specified in the Definition File" of "17.8.1 Installation". However, L-Servers with the same name cannot be created. Avoid using the same L-Server name more than once.
Note
When creating an L-Server, log off ETERNUSmgr of ETERNUS storage registered on ESC.
When operating NetApp storage in cluster environments and operating a partial system due to system trouble, recover the NetApp storage and return the system to cluster operation before re-commencing operations.
When the status of the VM host and virtual storage is one other than "normal", the resource will be excluded from L-Server allocation regardless of its available space.
When operating a VM host in a cluster system, create an L-Server with the storage resources shared between VM hosts specified.
L-Server cannot be created using storage resources that are not shared between VM hosts.
Depending on the [None (Definition only)] checkbox, the power status of an L-Server after its creation is as follows.
When Checked | When not Checked | |
|---|---|---|
Physical L-Server | Power OFF | Power ON |
Virtual L-Server | Power OFF | Power OFF |
For details on how to start an L-Server, refer to "17.1.1 Starting an L-Server".
When creating a virtual L-Server, the values in the VM specific information definition file are used even if those values have not been set in the L-Server template.
If there are discrepancies between the L-Server template and VM specific information definition file (e.g. CPU performance is lower than CPU Reserve), L-Server creation will fail.
For details on VM specific information definition files, refer to "8.1 Definition Files Commonly Shared when Creating Virtual L-Servers" and "Appendix G Definition Files" in the "Setup Guide CE".
[Hyper-V]
When using dynamic memory or memory weight, the VM host must be either of the following.
Microsoft(R) Windows Server(R) 2008 R2 SP1 or later
Microsoft(R) Windows Server(R) 2012 or later
SCVMM must be one of the following, either of which can manage the VM hosts.
System Center Virtual Machine Manager 2008 R2 SP1 or later
System Center 2012 Virtual Machine Manager or later
When creating an L-Server for which dynamic memory is enabled or memory weight is specified, creation of the L-Server will fail unless there are a VM host and SCVMM satisfying the conditions above.
