Top
ServerView Resource Orchestrator Cloud Edition V3.1.1 Reference Guide (Command/XML)
ServerView
Part 2 File Reference > Chapter 15 XML Files > 15.3 L-Servers > 15.3.2 Definition Information for Virtual L-Servers (XML)
PreviousNext

15.3.2 Definition Information for Virtual L-Servers (XML)

This section explains the XML definitions of virtual L-Servers.

To specify the level, change the Resources element to the Folder element.
Refer to "Example Creating an L-Server in a resource folder or a tenant".

Note

  • When you specify a tag that does not include the element in the subordinate of the XML tag, specify an empty element tag instead of the end tag.

    Example

    • Do not specify an end tag as shown below.

      <?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="L-Server Name" label="Label">
  </LServer>
</Resources>

    • Specify an empty element tag instead of the end tag.

      <?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="L-Server Name" label="Label"/>
</Resources>

The XML definition for a virtual L-Server is shown below.

<?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="L-Server Name" label="Label">
    <Comment>Comment</Comment>
    <TemplateLink name="L-Server Template Name"/>
    <ServerImageLink name="Image Name" version="Image Version" disk="Disk Deployment Settings during Image Specifications(all)" fit_disk_size="Disk Size Extension (true|false)"/>
    <ServerType>Server Type</ServerType>
    <VMType>VM Type</VMType>
    <OSType>OS Type</OSType>
    <CPU>
      <CPUArch>CPU Architecture</CPUArch>
      <CPUPerf>CPU Performance</CPUPerf>
      <NumOfCPU>Number of CPUs</NumOfCPU>
      <CPUReserve>CPU Reservation Performance</CPUReserve>
      <CPUShare>CPU Shares</CPUShare>
      <CPUWeight>CPU Allocation Priority</CPUWeight>
    </CPU>
    <Memory>
      <MemorySize>Memory Size</MemorySize>
      <MemoryReserve>Memory Reservation Capacity</MemoryReserve>
      <MemoryShare>Memory Shares</MemoryShare>
      <DynamicMemory>Dynamic Memory Settings</DynamicMemory>
      <StartupRAM>Initial Memory Size</StartupRAM>
      <MemoryBuffer>Memory Buffer</MemoryBuffer>
      <MemoryWeight>Memory Allocation Priority</MemoryWeight>
    </Memory>
    <Disks>
      <Disk name="Disk Name">
        <DiskIndex>Disk Index</DiskIndex>
        <DiskLink name="Name of the disk created in advance"> or
        <DiskCopy name="Source disk name to copy">
        <DiskSize>Disk Size</DiskSize>
          <Exist>Existing Disk</Exist>
        <From auto="Automatic selection of storage for use">
          <VirtualStorage name="Virtual Storage Resource Name"/>
          <Pool name="Storage Pool Name"/>
        </From>
      </Disk>
    </Disks>
    <NICs>
      <NIC>
        <NICIndex>NIC Index</NICIndex>
        <NetworkLinks>
          <NetworkLink name="Network_name" index="Network_index">
            <IpAddress auto="Automatic IP Configuration" address="IP address"/>
          </NetworkLink>
        </NetworkLinks>
        <MacAddress auto="MAC Address Auto Select" from="Address Set Resource (MAC Address)" pool="Address Pool"/>
      </NIC>
    </NICs>
    <Policy>
      <Redundancy>Redundancy</Redundancy>
      <Positioning>Positioning</Positioning>
      <Exclusion>Exclusion</Exclusion>
      <Priority>Priority</Priority>
      <Repurpose>Server Automatic Release(true|false)</Repurpose>
      <OverCommit>Enabling/Disabling Overcommit</OverCommit>
      <AliveMonitoring>AliveMonitoring Setting(true|false)</AliveMonitoring>
    </Policy>
    <From keep="Retention of a Used Server" auto="Automatic Selection of a Used Server">
      <VmHost name="VM Host Resource Name"/>
      <Pool name="VM Pool Name"/>
    </From>
    <Allocation>Allocation of Resources</Allocation>
    <OSSetting>
      <ComputerName>Computer Name, Hostname</ComputerName>
      <FullName>Full Name</FullName>
      <ProductKey>Product Key</ProductKey>
      <AdminPassword>Administrator Password</AdminPassword>
      <CAL>License Mode</CAL>
      <CALMaxConnection>Maximum Number of Connections</CALMaxConnection>
      <OrganizationName>Organization Name</OrganizationName>
      <DomainName>Domain Name</DomainName>
      <DNSSearchPaths>
        <DNSSearchPath>DNS Search Path</DNSSearchPath>
        <DNSSearchPath>DNS Search Path</DNSSearchPath>
      </DNSSearchPaths>
      <DNSServers>
        <DNSServer nic="NIC Index" ip="DNS IP Address" />
        <DNSServer nic="NIC Index" ip="DNS IP Address" />
      </DNSServers>
      <TimeZone>Time Zone</TimeZone>
      <HardwareClock>Hardware Clock Configuration</HardwareClock>
    </OSSetting>
  </LServer>
</Resources>
Table 15.5 List of Items Specified in XML Definitions for Virtual L-Servers

Element Name

Description

Remarks (Possible Values, Examples)

L-Server name (*1, *2)

(LServer name)

Name of the L-Server

Enter a name for the L-Server.
For details on the characters and the number of characters which can be specified, refer to "16.3.1 [General] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

[VMware]
The value can be changed even when the L-Server is powered on.

Label (*1, *2)

(LServer label)

Label for the L-Server

(optional)

Specify a character string of up to 32 alphanumeric characters or symbols.

Comment (*1, *2)

(Comment)

Comment for the L-Server

(optional)

Specify a character string of up to 256 alphanumeric characters or symbols.

L-Server template name (*2, *3)

(TemplateLink name)

Name of the L-Server template to use for the L-Server

(optional)

Specify the resource name of an existing L-Server template.

  • In the case of change of L-Server related with the configured virtual machine

    Only a template name is changed. The composition of L-Server is not changed.

    When you initialize a preset value, please specify as follows.

    <TemplateLink/>

Image name (*2, *3)

(ServerImageLink name)

Name of the cloning image to deploy to the L-Server's boot disk

(optional)

Specify the resource name of an existing cloning image.

Specify using a name containing a resource folder.
For details, refer to "16.1 Creation Using an L-Server Template" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

  • In the case of change of L-Server related with the configured virtual machine

    Only a cloning image name is changed. OS installed is not changed.

    When you initialize a preset value, please specify as follows.

    < ServerImageLink />

[Solaris Zones]
Ensure address set resources are specified.

Image version (*2, *3)

(ServerImageLink version)

Version of the cloning image to deploy to the L-Server's boot disk

(optional)

Specify an integer.

If omitted, the latest version is used.

  • In the case of change of L-Server related with the configured virtual machine

    Only a cloning image version is changed. OS installed is not changed.

    Please refer to "Image name" for initialization of a preset value.

Disk deployment settings during image specification

(ServerImageLink disk)

Disk deployment settings held by images

(optional)

Specify "all".

Create an L-Server with the same disk configuration as an image. When omitted, only system disks are deployed for images.

Enabled when VM type is set to "VMware" or "Hyper-V".

Disk size expansion

(fit_disk_size)

Configure the same size as the disk capacity of the image

(optional)

  • true (by default)

    Create a virtual L-Server with the same disk capacity as that of the image.

  • false

    Compare the disk size of the image and the disk size specified for the DiskSize element, and create an L-Server disk with the larger disk capacity.
    When specifying an L-Server template, and DiskSize is not specified in this XML file, compare the disk size of the image and the disk size specified for the DiskSize element in the template, and create an L-Server disk with the larger disk capacity.
    When the VM type is "VMware" or "Hyper-V", disk size expansion can be specified.
    When omitted, the disk capacity of the image is set.
    This specification is valid only when an image has been specified.
    When creating an L-Server, if expanding the data disk space included in images, set "all" for [ServerImageLink].

Server type (*4)

(ServerType)

Type of server to allocate as an L-Server

Specify "Virtual".

VM type (*2, *4)

(VMType)

Type of VM to allocate as an L-Server

  • VMware

  • Hyper-V

  • RHEL-Xen

  • RHEL-KVM

  • Oracle VM

  • Solaris Containers

  • Citrix-Xen

  • OVM-x86

If omitted, it must be specified when creating the L-Server.

OS type (*1, *2)

(OSType)

Type of OS for the L-Server

This setting can be omitted if an image is specified.

[VMware]
For the values that can be set, refer to the information displayed on the GUI, or the values described in the "NAME" column of the VMware web site (*4).
For environments where both vSphere4 and vSphere5 exist, specify the value described on the VMware Web site (*4) for the "NAME" column.

[Hyper-V]
For the possible values that can be set, refer to the information displayed on the GUI, or the Name of the operating system object that can be obtained from SCVMM.
This information can be obtained using Get-OperatingSystem(System Center Virtual Machine Manager 2008 R2) or Get-SCOperatingSystem(System Center 2012 Virtual Machine Manager) Cmdlet.
The value can be changed even when the L-Server is powered on.

[KVM]
Configure one of following items.

  • Linux

  • Windows

  • Linux(SELinux)

  • Other

The value can be changed even when the L-Server is powered on.

[Xen]
Specify Linux.

[Solaris Zones]
Specify Solaris.

[OVM for x86 2.2] [Solaris Zones] [OVM for SPARC] [Citrix Xen] [OVM for x86 3.2]
OS type cannot be changed irrespective of specification of an image, and the power status of an L-Server.

CPU architecture (*4)

(CPUArch)

CPU architecture of the server to allocate to the L-Server

(optional)

[VMware] [Hyper-V] [KVM] [Xen] [OVM for x86 2.2] [Citrix Xen] [OVM for x86 3.2]
Specify IA.

[Solaris Zones]
Specify SPARC.

When omitted, it is automatically configured according to the VM type. However, when an L-Server template is specified, the value in the L-Server template is used.

CPU performance (*1, *2, *4, *6)

(CPUPerf)

CPU performance to allocate to L-Server

Specify a number with up to one decimal place, in units of gigahertz.

For details on the scope which can be specified, refer to "16.3.2 [Server] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

[VMware] [Hyper-V] [KVM]
The value can be changed even when the L-Server is powered on.

[Xen]
Specify a value "0.1" or larger.

[Solaris Zones]
The value can be changed even when the L-Server is powered on. The changed value will be enabled on the actual virtual machine after it is restarted.

[Citrix Xen]
The value cannot be changed even when the L-Server is powered on.

Number of CPUs (*1, *2 , *4, *6)

(NumOfCPU)

Number of CPUs to allocate to L-Server

Specify an integer equal to or greater than "1".

For details on the scope which can be specified, refer to "16.3.2 [Server] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

[VMware]
When the CPU hot plug option of VM guests is enabled, the value can be added when the L-Server is powered on.

[Xen]
Specify a value "1" or larger.

[Solaris Zones]
The value can be changed even when the L-Server is powered on. The changed value will be enabled on the actual virtual machine after it is restarted.

[Citrix Xen] [OVM for x86 3.2]
The value cannot be changed even when the L-Server is powered on.

CPU reservation performance (*1, *2, *7, *8, *0, *10)

(CPUReserve)

The minimum number of CPU resources to be allocated to an L-Server

(optional)

Specify a number with up to one decimal place, in units of gigahertz.

Specify a value in the range from "0" to the upper limit of the CPU performance.
If left blank, the values will differ when creating or modifying the L-Server.

  • When creating

    "0" is set.

  • When modifying

    The current value of the L-Server is retained.

Enabled when VM type is set to "VMware" or "Hyper-V".

The value can be changed even when the L-Server is powered on.

CPU shares (*1, *2, *7, *8, *9)

(CPUShare)

The relative proportion for allocation of CPU resources on an L-Server

(optional)

Specify an integer equal to or greater than "1". (*9)

If left blank, the values will differ when creating or modifying the L-Server.

  • When creating

    A number determined by multiplying the value specified for Number of CPUs by 1,000 is set.

  • When modifying

    The current value of the L-Server is retained.

Enabled when VM type is set to "VMware".

The value can be changed even when the L-Server is powered on.

CPU allocation priority (*1, *2, *10)

(CPUWeight)

CPU allocation priority

(optional)

Specify the priority for CPU allocation.

[Hyper-V]
Specify an integer between 1 and 10,000.

If left blank, the values will differ when creating or modifying the L-Server.

  • When creating

    "100" is set.

  • When modifying

    The current value of the L-Server is retained.

The value can be changed even when the L-Server is powered on.

[Citrix Xen]
Specify an integer between 1 and 65535.
If omitted, no values are set for L-Servers.

If left blank, the values will differ when creating or modifying the L-Server.

  • When creating

    The default values for virtualization software are configured.

  • When modifying

    The current value of the L-Server is retained.

The value cannot be changed even when the L-Server is powered on.

Memory size (*1, *2, *4, *6)

(MemorySize)

Size of memory to allocate to L-Server

Specify a number with up to one decimal place, in units of gigabytes.

For details on the scope which can be specified, refer to "16.3.2 [Server] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

[VMware]
When the memory hot add option of VM guests is enabled, the value can be added when the L-Server is powered on.

[KVM]
The value can be changed even when the L-Server is powered on.

[Xen]
Specify a value "0.1" or larger.

[Solaris Zones]
The value can be changed even when the L-Server is powered on. The changed value will be enabled on the actual virtual machine after it is restarted.

[Citrix Xen]
The value cannot be changed even when the L-Server is powered on.

[OVM for x86 3.2]
Specify a number between 0.3 and 1024.
The value cannot be changed even when the L-Server is powered on.

Memory reservation capacity (*1, *2, *7, *8, *9)

(MemoryReserve)

The minimum amount of memory resources to be reserved for an L-Server

(optional)

Specify a number with up to one decimal place, in units of gigabytes.

Specify a value in the range from "0" to the upper limit of Memory Size.
If left blank, the values will differ when creating or modifying the L-Server.

  • When creating

    The value specified for memory size is set. (*10)

  • When modifying

    The current value of the L-Server is retained.

Enabled when VM type is set to "VMware" or "Citrix-Xen".

[VMware]
The value can be changed even when the L-Server is powered on.

[Citrix Xen]
The value cannot be changed even when the L-Server is powered on.

Memory shares (*1, *2, *7, *8, *9)

(MemoryShare)

The relative proportion for allocation of memory resources on an L-Server

(optional)

Specify an integer equal to or greater than "0". (*9)

If left blank, the values will differ when creating or modifying the L-Server.

  • When creating

    A number determined by multiplying the value specified for Memory Size by 1024 by 10 is set.

  • When modifying

    The current value of the L-Server is retained.

Enabled when VM type is set to "VMware".

The value can be changed even when the L-Server is powered on.

Dynamic memory settings (*1, *2, *10)

(DynamicMemory)

Dynamic memory settings

(optional)

Set enabling/disabling of dynamic memory.

  • When enabling dynamic memory

    Specify "true".

  • When disabling dynamic memory

    Specify "false".

If left blank, the values will differ when creating or modifying the L-Server.

  • When creating

    • If Initial Memory Size or Memory Buffer is already set

      "true" is set.

    • If Initial Memory Size or Memory Buffer is not set

      "false" is set.

    Even when the initial memory size and memory buffer are not specified in the L-Server XML file, if they are defined in the L-Server template or VM unique information definition file those values will be reflected on the L-Server. Therefore, the values of dynamic memory are configured depending on the values.

  • When modifying

    The current value of the L-Server is retained.

If dynamic memory is disabled when creating or modifying an L-Server, the specified values for the initial memory size and memory buffer are ignored (including any existing setting values).
Enabled when VM type is set to "Hyper-V".
For the GUI and command (in text format) operations, "on" is displayed to indicate the enabled status and "off" for the disabled status.

Initial memory size (*1, *2, *10)

(StartupRAM)

Initial memory size

Specify an initial memory capacity to be allocated at startup.

Specify the memory capacity in the range of 0.1 to the value specified for Memory size.
When specifying this element, either specify "true" to enable dynamic memory or leave the dynamic memory settings blank (this includes the L-Server template and the VM unique information definition file). If dynamic memory is disabled, the specified value is ignored.
If left blank, the values will differ when creating or modifying the L-Server.

  • When creating

    Memory size is set.

  • When modifying

    The current value of the L-Server is retained.

Enabled when VM type is set to "Hyper-V".

Memory buffer (*1, *2, *10)

(MemoryBuffer)

Available memory to be reserved as a buffer (%)

(optional)

Specify an initial memory capacity to be allocated to the virtual machine.

Specify an integer between 5 and 2,000.
When specifying this element, either specify "true" to enable dynamic memory or leave the dynamic memory settings blank (this includes the L-Server template and the VM unique information definition file). If dynamic memory is disabled, the specified value is ignored.
If left blank, the values will differ when creating or modifying the L-Server.

  • When creating

    "20" is set.

  • When modifying

    The current value of the L-Server is retained.

Enabled when VM type is set to "Hyper-V".

The value can be changed even when the L-Server is powered on.

Memory allocation priority (*1, *2, *10)

(MemoryWeight)

Memory allocation priority

(optional)

Specify the priority for memory allocation.

Specify an integer between 0 and 10,000.
If left blank, the values will differ when creating or modifying the L-Server.

  • When creating

    "5,000" is set.

  • When modifying

    The current value of the L-Server is retained.

Enabled when VM type is set to "Hyper-V".

The value can be changed even when the L-Server is powered on.

Disk name (*2, *13, *14)

(Disk name)

The disk name to allocate to L-Servers

(optional)

Specify a character string beginning with an alphanumeric character and containing up to 32 alphanumeric characters, underscores ("_"), and hyphens ("-"). If omitted, a name is automatically generated.

When specifying a disk which was created in advance or a disk which was automatically created and saved, do not specify the same name as those of the disks.

In the following cases, the value is ignored.

  • When the specified disk name is different from the name of a disk which was either created in advance or automatically created and saved

  • When the VM type is "RHEL-KVM" or "Solaris Containers" and the following are specified for the disk:

    • Existing Disk

    • Disk Size

Disk index (*2, *3, *13, *14)

(DiskIndex)

Number of the disk to allocate to the L-Server

Specify an integer starting from "0".

0: Boot disk
Other than 0: Data disk

[VMware]
Specify a number between 0 and 55.

[Hyper-V]
Specify a number between 0 and 59.

[Xen]
Specify a number between 0 and 251.

[KVM]
Specify a number between 0 and 16.

[OVM for x86 2.2]
When the L-Server is an HVM (Hardware Virtualized Machine), specify a number between 0 and 7.
When the L-Server is a PVM (Para-Virtualized Machine), specify a number between 0 and 59.

[Solaris Zones]
0

[Citrix Xen]
Specify a number between 0 and 13.

[OVM for x86 3.2]
When the L-Server is an HVM (Hardware Virtualized Machine), specify a number between 0 and 2.
When the L-Server is a PVM (Para-Virtualized Machine), specify a number between 0 and 102.
When the L-Server is a PVHVM (Para-Virtualized Hardware Virtual Machine), specify a number between 0 - 105.

Name of the disk created in advance (*2)

(DiskLink name)

The name of a disk created in advance for allocation to the L-Server

(optional)

Specify a disk which already exists.

When the VM type is "RHEL-Xen", "RHEL-KVM", "Hyper-V", or "Solaris Containers", the disk name can be specified.

  • For "RHEL-Xen"

    This element cannot be specified, for disks with the number "0".
    The name of the source disk to be copied cannot be specified at the same time.
    For an L-Server, a single disk created in advance cannot be specified multiple times.
    When specifying the name at the same time as the disk size, the disk size for the disk name created in advance is reflected on the new disk.

  • For "RHEL-KVM" and "Solaris Containers"

    For an L-Server, a single disk created in advance cannot be specified multiple times.
    Disk size cannot be specified at the same time.

  • For "Hyper-V"

    This element cannot be specified, for disks with the number "0". For an L-Server, a single disk cannot be specified multiple times. Disks being used by other L-Servers cannot be specified. When specifying the name at the same time as the disk size, the disk size for the disk name automatically created and saved is reflected on the new disk.

Existing disk (*2)

(Exist)

Specifies that the disk to allocate to the L-Server was a virtual disk created in advance using storage management software

(optional)

  • true

    Specify when selecting a disk automatically from virtual disks created using storage management software. The selected disk has the same size as specified using the Disk Size element.
    If the VM type is "RHEL-KVM" or "Solaris Containers", this value must be specified when allocating a disk to an L-Server with disk size specified.

Source disk name to copy (*4)

(DiskCopy name)

Data disk name of the source to copy the content from

(optional)

Specify the disk name of the source data disk to copy the content from.

When the VM type is "RHEL-Xen", the disk name can be specified.
This element cannot be specified, for disks with the number "0".
The name of a disk created in advance cannot be specified at the same time.
When specifying the name at the same time as the disk size, the disk size for the disk name of the source to be copied is reflected to the new disk.

Disk size (*2, *4)

(DiskSize)

Size of disk to create

Specify a number with up to one decimal place, in units of gigabytes.

For details on the scope which can be specified, refer to "16.3.3 [Disk] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
The disk size can be omitted when specifying the name of a disk created in advance at the same time.
The disk name information created in advance is given priority when a disk name created in advance is specified at the same time.
For L-Servers, the disk size can be omitted when specifying a disk name created in advance or the disk name of the source to be copied at the same time. The information of the disk name created in advance or the name of the source disk to be copied is given priority when the information is specified at the same time.

[Xen]
Specify a number between 0.1 and 999.9.

Automatic selection of storage to use (*2)

(From auto)

Automatically selects the storage destination used for an L-Server

(optional)

  • true

    Specify to automatically select the resource destination.

  • false

    Specify to not automatically select resources.

If omitted, the resource is automatically selected if "Virtual storage resource name" or "Storage pool name" is not specified.

Virtual storage resource name (*2, *3)

(VirtualStorage name)

Virtual storage from which the disk to allocate to the L-Server is created
If specified at the same time as storage pool, priority is given to this attribute.

(optional)

Specify the resource name of an existing virtual storage.

  • In the case of change of L-Server related with the configured virtual machine

    The virtual storage name is changed. The storage currently used is not changed.

    When you initialize a preset value, please specify as follows.

    <From auto="true"/>

[Hyper-V]
When specifying this element, specify the same virtual storage for all disks.

Storage pool name (*2, *3)

(Pool name)

Resource pool for extracting the virtual storage to create the disk to allocate to the L-Server

(optional)

Specify the resource name of an existing storage pool.

If there are storage pools with the same name on different levels, the level must also be specified.
Resource_folder/Resource_pool

  • In the case of change of L-Server related with the configured virtual machine

    The storage pool name is changed. The storage currently used is not changed.

    When you initialize a preset value, please specify as follows.

    <From auto="true"/>

[Hyper-V]
When specifying this element, specify the same storage pool for all disks.

NIC index (*2)

(NICIndex)

Number to identify the NIC definition to allocate to the L-Server

Specify an integer starting from "0".

NIC number (NICIndex) + 1 corresponds to a network (NIC) number of the [General] tab in the [Create an L-Server] dialog.

[VMware]
Specify a number between 0 and 9.

[Hyper-V]
Specify a number between 0 and 7.

[KVM]
Specify a number between 0 and 7.

[Xen]
Specify a number between 0 and 14.

[KVM]
Specify a number between 0 and 7.

[OVM for x86 2.2]
Specify a number between 0 and 7.

[Solaris Zones]
Specify a number between 0 and 7.

[Citrix Xen]
Specify a number between 0 and 6.

[OVM for x86 3.2]
Specify a number between 0 and 7.

Network name (*2, *15)

(NetworkLink name)

Name of the network that the L-Server connects to

Specify the name of an existing network resource.

  • VM type is "VMware" or "Hyper-V", and it is effective only when the network resource is not connected to NIC.

    Setup of a Network name is carried out to NIC corresponding to the specified MAC Address.

    Therefore, please be sure to specify a MAC Address.

Network index

(NetworkLink index)

Network index

Specify "0" for the network index.

When creating L-Servers, this attribute can be omitted. When modifying L-Server specifications, this attribute must be specified.

MAC address

(MacAddress)

The MAC address to allocate to the L-Server NIC

The MAC address can be specified using the following methods:

<MacAddress auto="true" from="Address Set Resource(MAC Address)"/>
or
<MacAddress auto="true" pool="Address Pool"/>
or
<MacAddress auto="true"/>
An address in the MAC address range set in the MACAddressSetResource, or the MAC address range registered in the specified address pool, or the MAC address range registered in accessible address pools will automatically be allocated.
When address set resource and address pool are specified at the same time, the address set resource has priority.

  • In the case of change of L-Server related with the configured virtual machine

    When you set an IP address and a Network name, please be sure to specify in the format of the following.

    <MacAddress>XX:XX:XX:XX:XX:XX</MacAddress>

    In addition, change of a MAC Address cannot be performed.

  • When the VM type is "RHEL-Xen"

    Ensure address set resources are specified.

  • When the VM type is "RHEL-KVM" or "Citrix-Xen"

    The address set resources can be omitted. When omitted, the Mac address is automatically allocated from the MAC address range registered in accessible address pools.
    When modifying an L-Server that only has configuration definition created, NIC cannot be changed. Therefore, do not specify the MacAddress element.

IP address (*2, *15)

(IpAddress)

IP address to allocate to L-Servers

(optional)

The IP can be specified using the following methods:

<IpAddress auto="false" address="xxx.xxx.xxx.xxx"/>
Specify an IP address.

<IpAddress auto="true"/>
An IP address is automatically assigned from the address range set for the network resource.
Even if the IpAddress element is omitted, an IP address is automatically assigned from the address range set for the network resource.

  • In the case of change of L-Server related with the configured virtual machine

    VM type is "VMware" or "Hyper-V", and it is effective only when the network resource is not connected to NIC.

    Setup of an IP address is carried out to NIC corresponding to the specified MAC Address. Therefore, please be sure to specify a MAC Address.

Redundancy (*1, *2, *4, *16)

(Redundancy)

Server redundancy to allocate to L-Servers

(optional)

  • None

    No redundancy

  • HA

    Places in a server with HA set

    When "Solaris Containers" is configured for the VM type, it is placed in a server which has a spare server

If omitted, "None" is set.
For details on the redundancy, refer to "16.3.2 [Server] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When "RHEL-Xen" or "RHEL-KVM" has been specified for the VM type, only "None" can be specified.

Positioning (*1, *2, *4)

(Positioning)

Physical location of the server to allocate to L-Servers

(optional)

  • Fixed

    Fixed physical position

  • AttachAtBoot

    Position changes upon startup

If omitted, "Fixed" is set.
When "RHEL-Xen" has been specified for the VM type, only "Fixed" can be specified.

Exclusion (*1, *2)

(Exclusion)

Exclusive operation with another virtual machine on a physical server

(optional)

Specify the L-Server_name or the Resource_folder_name.

To specify L-Server names or resource folder names that are arranged in a hierarchy, the level must also be specified.

/Folder1/Folder2
/Folder1/L-Server3

Specify resources included in the access scope.

  • When changing

    When you initialize a preset value, please specify as follows.

    <Exclusion/>

Priority (*1, *2)

(Priority)

Priority when allocating resources or creating an L-Server

(optional)

When the L-Server is the target of batch power operations, or when performing batch creation of multiple L-Servers using XMLs of resource folders, specify the priority in the range of 1 to 256.

Smaller values indicate higher priority.
If omitted, "128" is set.
When "0" is specified, the server is excluded from batch power operations.
If a VM type other than "RHEL-Xen" is specified, L-Servers are created depending on the priority which has been specified.

Server automatic release (*1, *2)

(Repurpose)

Automatic release of servers during power off

(optional)

Specify whether to automatically release the servers allocated to the L-Server, when they are powered off.

  • When using automatic release

    Specify "true".

  • When not using automatic release

    Specify "false".

If the values of this attribute and "Server Automatic Release" of the L-Server template are omitted, the value that is set in the definition file is used.
For details on the definition file, refer to "17.8.1 Installation" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Enabling/disabling overcommit (*1, *2)

(OverCommit)

Setting for overcommit

(optional)

Set enabling/disabling of overcommit.

If left blank, "false" is set.

  • When enabling overcommit

    Specify "true".

  • When disabling overcommit

    Specify "false".

Alive monitoring settings (*1, *2, *4, *16)

(AliveMonitoring)

Alive Monitoring Settings

(optional)

  • When enabling alive monitoring

    Specify "true"

  • When disabling alive monitoring

    Specify "false"

If omitted and not specified when creating the L-Server, "false" is set.

Retention of a used server (*2)

(From keep)

Retains the server destination used for an L-Server

(optional)

  • true

    Specify when retaining the resource destination.

  • false

    Specify when not retaining the resource destination.

If not specified, "true" is set.

Automatic selection of a used server(*2)

(From auto)

Automatically selects the server destination used for an L-Server

(optional)

  • true

    Specify to automatically select the resource destination.

  • false

    Specify to not automatically select resources.

If omitted, when "VM host" or "VM pool name" is specified, the "VM host" or the "VM pool name" is given priority.

When "VM host" or "VM pool name" is not specified, the resource is automatically selected.

VM host resource name (*1, *2)

(VmHost name)

VM host to create the VM to allocate to the L-Server
If specified at the same time as resource pool, priority is given to this attribute.

(optional)

Specify the resource name of a registered VM host.

If not retaining a server to use, this is valid only when allocating for the first time.

  • When changing

    When you initialize a preset value, please specify as follows.

    <From auto="true"/>

VM pool name (*1, *2)

(Pool name)

Resource pool to extract the VM host to create the VM to allocate to the L-Server from

(optional)

Specify the resource name of a registered VM pool.

If there are VM pools with the same name on different levels, the level must also be specified.
Resource_folder/Resource_pool
If not retaining a server to use, this is valid only when allocating for the first time.

  • When changing

    When you initialize a preset value, please specify as follows.

    <From auto="true"/>

Allocation of resources

(Allocation)

Status of resources allocated to the L-Server

(optional)

  • true

    Specify to allocate resources.

  • false

    Only specify when creating a configuration definition.

If this attribute is omitted, the value set in the definition file is used.
For details on the definition file, refer to "17.8.1 Installation" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

Computer name, hostname (*2, *17)

(ComputerName)

Computer name and hostname

[VMware]
For specifiable values, refer to "C.2.9 [OS] Tab Configuration" in the "Setup Guide CE".

[Hyper-V]
For specifiable values, refer to "C.3.9 [OS] Tab Configuration" in the "Setup Guide CE".

[Xen]
Only host name can be specified.

[Solaris Zones]
For specifiable values, refer to "C.7.7 [OS] Tab Configuration" in the "Setup Guide CE".

Full name (*2, *17)

(FullName)

Full name used for Windows

[VMware]
For specifiable values, refer to "C.2.9 [OS] Tab Configuration" in the "Setup Guide CE".

[Hyper-V]
For specifiable values, refer to "C.3.9 [OS] Tab Configuration" in the "Setup Guide CE".

[Solaris Zones]
For specifiable values, refer to "C.7.7 [OS] Tab Configuration" in the "Setup Guide CE".

Product key (*2, *17)

(ProductKey)

Windows product key

Administrator password (*2, *17)

(AdminPassword)

Administrator password used for the OS

License mode (*2, *17)

(CAL)

Client access license set for Windows

Maximum number of connections (*2, *17)

(CALMaxConnection)

Number of client connections set for Windows

Organization name (*2, *17)

(OrganizationName)

Organization name used for Windows

Domain name (*2, *17)

(DomainName)

Domain name used for the OS

DNS search path (*2, *17)

(DNSSearchPath)

DNS search path used for Linux

To specify multiple values, use multiple elements.

<DNSSearchPaths>
<DNSSearchPath>DNS Search Path1</DNSSearchPath>
<DNSSearchPath>DNS Search Path2</DNSSearchPath>
</DNSSearchPaths>

[VMware]
For specifiable values, refer to "C.2.9 [OS] Tab Configuration" in the "Setup Guide CE".

[Hyper-V]
For specifiable values, refer to "C.3.9 [OS] Tab Configuration" in the "Setup Guide CE".

NIC index (*2, *17)

(DNSServer nic)

NIC index used to set the DNS

Specify the NIC index used to set the DNS IP address.

  • When the OS is Windows

    This index is required.

  • When the OS is Linux

    Do not specify any nic attributes.

Specify a number between 0 and 9.

DNS IP address (*2, *17)

(DNSServer ip)

DNS IP address

  • When the OS is Windows

    Specify the DNS IP address to set for each NIC.

  • When the OS is Linux

    Specify the DNS IP address to set for the system.

Time zone (*2, *17)

(TimeZone)

Time zone for the OS

  • For the time zones that can be specified using Windows, refer to the Microsoft web site. (*12)
    Convert the value from the "Index" column to a decimal, or specify a value from the "Time" column.

  • Examples of the time zones that can be specified using Linux are listed below. To specify other time zones, refer to the information displayed using commands provided by the OS such as timeconfig.

    • Asia/Tokyo

    • US/Pacific

    • US/Central

    • US/Eastern

    • Europe/Berlin

    • Europe/Amsterdam

    • Europe/London

    • Asia/Seoul

    • Asia/Hong_Kong

    • Australia/Canberra

Hardware clock configuration (*2, *17)

(HardwareClock)

Clock configuration used for Linux

[VMware]
For specifiable values, refer to "C.2.9 [OS] Tab Configuration" in the "Setup Guide CE".

[Hyper-V]
For specifiable values, refer to "C.3.9 [OS] Tab Configuration" in the "Setup Guide CE".

*1: Values that can be changed by modifying an L-Server. Even if an L-Server template name or the content of an L-Server template is modified, the configuration of L-Servers already created using the template will not be modified. Only change the OS type if no OS is installed.
*2: Values can be changed by modifying an L-Server, only when its status is "defined" (only the configuration definition has been created). When modifying an L-Server for which only the configuration definition has been created, unmodified information must be described also.
*3: In L-Server related to the virtual machine, a value can be changed.
*4: Specify if no L-Server template is used or if the values specified in the L-Server template will not be used.
*5: For details on the possible values, refer to the VMware web site below.

VMware web site

URL:
http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vim.vm.GuestOsDescriptor.GuestOsIdentifier.html

*6: The value can be modified using the rcxadm lserver modify command. For details on the rcxadm lserver modify command, refer to "3.6 rcxadm lserver".
*7: For VMware, the value can be changed.
*8: When the VM type of an L-Server is VMware, the specified value is reflected.
*9: When the VM type of an L-Server is Hyper-V, the specified value is reflected.
*10: For the values that can be specified, refer to the "vSphere Resource Management Guide" of VMware.

Refer to the relevant version of the document, referring to the following URL:

URL: http://www.vmware.com/support/pubs/

*11: When omitted, the memory reservation capacity will be the same value as the value for the memory size, and the memory overcommit function will be disabled. When using the memory overcommit function, specify the value.
*12: Information to be specified individually after the image is deployed. Only specify if there is no OS property definition file or if you want to change the existing values. For OVM for x86 2.2, OVM for x86 3.2, the values cannot be specified individually. If set, the value is ignored.
*13: Refer to the Microsoft web site below.

Microsoft web site

URL: http://support.microsoft.com/kb/973627/en-us/

*14: If this is changed while the power is on, there may be cases where behavior is problematic or where the changes are not recognized.
*15: Only when it meets the following requirements with L-Server related to the virtual machine, the value can be changed.

*16: The values for an L-Server deployed from an L-Platform can be changed by changing the configuration. In this case, use an XML file which only contains the elements for alive monitoring settings and redundancy.

*17: When specifying "all" for disk deployment settings during image specification, it is recommended to omit the specifications for disks with numbers other than "0". When specifying disks with numbers other than "0", specify the appropriate disk numbers.

*18: When specifying "all" for disk deployment settings during image specifications, all disks are created in the same storage destination as the boot disks. When specifying the destination for storage of disks, define only the disk with the number "0".

Example

  • Creating an L-Server that does not deploy a cloning image using an L-Server template

    <?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="first_server">
    <TemplateLink name="small"/>
    <ServerType>Virtual</ServerType>
    <OSType>Red Hat Enterprise Linux 5 (32-bit)</OSType>
    <NICs>
      <NIC>
        <NICIndex>0</NICIndex>
          <NetworkLinks>
            <NetworkLink name="net01"/>
          </NetworkLinks>
      </NIC>
    </NICs>
  </LServer>
</Resources>

  • Creating an L-Server that deploys a cloning image using an L-Server template (pre-configured OS property definition file)

    <?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="second_server">
    <TemplateLink name="small"/>
    <ServerType>Virtual</ServerType>
    <ServerImageLink name="/ImagePool/master_image"/>
    <NICs>
      <NIC>
        <NICIndex>0</NICIndex>
          <NetworkLinks>
            <NetworkLink name="net01"/>
          </NetworkLinks>
      </NIC>
    </NICs>
    <OSSetting>
      <ComputerName>host2</ComputerName>
    </OSSetting>
  </LServer>
</Resources>

  • Creating an L-Server with the same disk configuration as the cloning image using an L-Server template (pre-configured OS property definition file)

    <?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="L-Server_with_datadisk">
    <TemplateLink name="small_with_datadisk"/>
    <ServerType>Virtual</ServerType>
    <ServerImageLink name="/ImagePool/master_image_with_datadisk" disk="all"/>
    <NICs>
      <NIC>
        <NICIndex>0</NICIndex>
          <NetworkLinks>
            <NetworkLink name="net01"/>
          </NetworkLinks>
      </NIC>
    </NICs>
    <OSSetting>
      <ComputerName>host2</ComputerName>
    </OSSetting>
  </LServer>
</Resources>

  • Creating an L-Server that deploys a Linux cloning image without using an L-Server template (pre-configured OS property definition file)

    <?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="L-Server">
    <ServerImageLink name="/ImagePool/RHEL5"/>
    <ServerType>Virtual</ServerType>
    <CPU>
      <CPUPerf>1.0</CPUPerf>
      <NumOfCPU>1</NumOfCPU>
    </CPU>
    <Memory>
      <MemorySize>2</MemorySize>
    </Memory>
    <Disks>
      <Disk>
        <DiskIndex>0</DiskIndex>
        <DiskSize>20.0</DiskSize>
      </Disk>
      <Disk>
        <DiskIndex>1</DiskIndex>
        <DiskSize>30.0</DiskSize>
      </Disk>
    </Disks>
    <NICs>
      <NIC>
        <NICIndex>0</NICIndex>
        <NetworkLinks>
          <NetworkLink name="net01"/>
        </NetworkLinks>
      </NIC>
    </NICs>
    <Policy>
      <Redundancy>None</Redundancy>
      <Positioning>Fixed</Positioning>
    </Policy>
    <OSSetting>
      <ComputerName>host1</ComputerName>
      <DomainName>xx.zz.yy</DomainName>
      <DNSSearchPaths>
        <DNSSearchPath>10.20.30.40</DNSSearchPath>
      </DNSSearchPaths>
    </OSSetting>
  </LServer>
</Resources>

  • Creating an L-Server with the same disk configuration as the cloning image without using an L-Server template (specifying the storage destination and pre-configured OS property definition file)

    <?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="L-Server">
    <ServerImageLink name="/ImagePool/master_image_with_datadisk" disk="all"/>
    <ServerType>Virtual</ServerType>
    <CPU>
      <CPUPerf>1.0</CPUPerf>
      <NumOfCPU>1</NumOfCPU>
    </CPU>
    <Memory>
      <MemorySize>2</MemorySize>
    </Memory>
    <Disks>
      <Disk>
        <DiskIndex>0</DiskIndex>
        <From>
          <VirtualStorage name="/StoragePool/SAN001"/>
        </From>
      </Disk>
    </Disks>
    <NICs>
      <NIC>
        <NICIndex>0</NICIndex>
        <NetworkLinks>
          <NetworkLink name="net01"/>
        </NetworkLinks>
      </NIC>
    </NICs>
    <Policy>
      <Redundancy>None</Redundancy>
      <Positioning>Fixed</Positioning>
    </Policy>
    <OSSetting>
      <ComputerName>host1</ComputerName>
      <DomainName>xx.zz.yy</DomainName>
      <DNSSearchPaths>
        <DNSSearchPath>10.20.30.40</DNSSearchPath>
      </DNSSearchPaths>
    </OSSetting>
  </LServer>
</Resources>

  • Creating an L-Server in a resource folder or a tenant

    <?xml version="1.0" encoding="utf-8"?>
<Folder name="Resource Folder Name or Tenant Name">
  <LServer name="L-Server Name" label="Label">
    ...
  </LServer>
</Folder>
    Table 15.6 List of Items Specified in XML Definitions when Creating an L-Server in a Resource Folder or a Tenant

    Element Name

    Description

    Remarks (Possible Values, Examples)

    Resource folder name or Tenant name (*1)

    (Folder name)

    Name of the resource folder or the tenant to place the L-Server in

    (optional)

    To specify the level, use the following format:

    Resource_folder_name/Resource_folder_name
    Tenant_name/Resource_folder_name
    Resource_folder_name/Tenant_name

    *1: Specify if creating an L-Server in a resource folder or a tenant.

  • Creating an L-Server (with one NIC) on a specific host without deploying cloning images using an L-Server template (for RHEL-Xen)

    <?xml version="1.0" encoding="utf-8"?>
<Resources>
  <LServer name="first_server">
    <TemplateLink name="template1"/>
    <ServerType>Virtual</ServerType>
    <OSType>Linux</OSType>
    <NICs>
      <NIC>
        <NICIndex>0</NICIndex>
        <NetworkLinks>
          <NetworkLink name="net01"/>
        </NetworkLinks>
        <MacAddress auto="true" from="mac_address_set"/>
      </NIC>
    </NICs>
    <From>
      <VmHost name="vmhost1"/>
    </From>
  </LServer>
</Resources>

  • Creating another L-Server using detailed L-Server information

    Modify the following information.

    • Modify the name attribute of the LServer element

    • Delete the DiskLink and MacAddress elements, and the name attribute of the Disk elements

    • Delete the IpAddress element and replace the NetworkLink element with an empty element tag

    • Add the OSSetting element

      When the name attribute of the NetworkLink element is left blank, add an appropriate network resource name.

    The following example is used to create an L-Server that has the same configuration as one already created, using the detailed information of the L-Server created with a Linux cloning image that has been deployed.

    When deploying a Windows cloning image, changes should be made referring to the XML definition shown above.

    <?xml version="1.0" encoding="utf-8"?>
<Resources>
<LServer name="L-Server2" id="rctest_1220" label="">
  <Comment></Comment>
  <TemplateLink name="sample_small" id="rctest_23" />
  <ServerType>Virtual</ServerType>
  <VMType>VMware</VMType>
  <OSType>Red Hat Enterprise Linux 5 (32-bit)</OSType>
  <CPU>
    <CPUArch>IA</CPUArch>
    <CPUPerf>1.0</CPUPerf>
    <NumOfCPU>1</NumOfCPU>
  </CPU>
  <Memory>
    <MemorySize>1.0</MemorySize>
  </Memory>
  <Disks>
      <Disk>
        <DiskIndex>0</DiskIndex>
        <DiskSize>10.0</DiskSize>
      </Disk>
  </Disks>
  <NICs>
    <NIC>
      <NICIndex>0</NICIndex>
      <MacAddress>00:50:56:8c:0b:2e</MacAddress>
      <NetworkLinks>
        <NetworkLink name="vnet30" index="0" vlan_mode="tagged" id="rctest_1123" >
          <IpAddress auto="true" address=""/>
        </NetworkLink>
      </NetworkLinks>
    </NIC>
  </NICs>
<ExternalIdentifier>42114bec-d26d-0c3d-c9aa-080a0c40d020</ExternalIdentifier>
  <Current>
        <VmHost name="gekkou-pri" id="rctest_62" />
        <VmGuest name="L-Server1-75" id="rctest_1224" />
  </Current>
  <ExternalProfile/>
  <ServerImageLink name="/ImagePool/pool" version="1" id="rctest_132" />
  <Policy>
    <Redundancy>None</Redundancy>
    <Positioning>Fixed</Positioning>
    <Exclusion></Exclusion>
    <Priority>128</Priority>
    <Repurpose>false</Repurpose>
  </Policy>
  <Status>
    <ResourceStatus>stop</ResourceStatus>
    <PowerStatus>off</PowerStatus>
    <AllocationStatus>attached</AllocationStatus>
    <MaintenanceMode>active</MaintenanceMode>
    <Resources>allocated</Resources>
    <ServerAllocationStatus>true</ServerAllocationStatus>
    <DiskAllocationStatus>true</DiskAllocationStatus>
    <AddressAllocationStatus>true</AddressAllocationStatus>
  </Status>
  <OSSetting>
    <DNSSearchPaths>
      <DNSSearchPath>10.20.30.40</DNSSearchPath>
    </DNSSearchPaths>
  </OSSetting>
</LServer>
</Resources>

PreviousNext
Copyright 2010-2013 FUJITSU LIMITED