This section explains how to perform L-Server configuration changes.
When modifying configurations for an L-Server for which only a configuration definition was created, refer to "17.8.2.3 Modifying Configuration Definition Information".
Point
Resource Orchestrator makes periodic queries to VM management software.
When the configuration of a virtual machine is modified using VM management software, periodic queries will reflect the changes on the virtual machines used by a virtual L-Server.
When addition, modification, or deletion of storage is performed using VM management software, changes to the configuration/status of storage of the virtual L-Server are detected.
Resource Orchestrator makes periodic queries to storage devices.
When changes are made to storage using storage management software, the changes to the status of the storage on the physical L-Server are detected.
On virtual L-Servers, the following information is updated:
L-Server Name (*1)
CPU Performance (*2, *3)
Number of CPUs (*2)
Memory Capacity (*4)
VM Management Software Specific Information
Operating System Type
Server Redundancy (*5)
The Number of Disks
Disk Index
Disk Capacity
Device Path
Usage
Type
*1: Confirm the following for the virtual L-Server name and the VM name:
When use of the same name is configured for both a virtual L-Server and a VM, performing the following operations makes the L-Server name match the VM name.
Creating an L-Server
Changing the name of L-Server name basic information
[Solaris Zones (Solaris 11)]
Changing the name of L-Server basic information does not change the VM name.
When use of the same name is configured for both a virtual L-Server and a VM, performing the following operations makes the L-Server name match the VM name when VM information changes are detected.
Changing labels and comments of L-Server basic information
Changing L-Server Specifications
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".
*2: [Solaris Zones]
CPU performance and the number of CPUs should be changed when the cap values of CPUs are changed, and when the resource pool for Solaris Zones used in non-global zone is changed as follows.
When changing managed resource pools for Solaris Zones to unmanaged resource pools for Solaris Zones
When changing unmanaged resource pools for Solaris Zones to managed resource pools for Solaris Zones
*3: For details on the CPU performance and the number of CPUs for OVM for SPARC, refer to "Display of CPU Performance and the Number of CPUs for L-Servers" in "8.8.8 Advisory Notes for OVM for SPARC Usage" in the "Setup Guide CE".
*4: When using VMware, the value to be reflected varies depending on the memory limit settings.
When Unlimited is set for the memory limit, the specified memory size is reflected.
When a particular value is specified for memory limit, that value is reflected.
When using Hyper-V, the value to be reflected varies depending on the dynamic memory settings.
When dynamic memory is enabled, the setting for the maximum memory is reflected.
When dynamic memory is disabled, the setting for the virtual machine memory is reflected.
*5: Updated only when VMware FT is configured or released.
When attaching and detaching disks from a virtual machine are performed consecutively on VM management software, an event log regarding Storage Migration is output.
Note
Network information and physical L-Servers are not updated.
When attachment or detachment of disks is performed using storage management software, the changes to the configuration of storage on the physical L-Server is not detected.
For the created physical L-Server, reflect attachment or detachment of disks using the following procedure:
When a Disk has been Attached
Detach the disk from the physical server using the storage management software.
When the physical server is powered on, it is necessary to change the status of the disk to detach into unused in advance.
Attach the disk to the physical L-Server.
For details, refer to "17.2.3 Attaching and Detaching Disks".
When a Disk has been Detached
Detach the disk from the physical L-Server.
For details, refer to "17.2.3 Attaching and Detaching Disks".
For a physical L-Server linked with a configured physical server, reflect attachment or detachment of disks using the following procedure:
Cancel the link between the physical server and the physical L-Server.
For details, refer to "18.6 Releasing an L-Server".
Create a link between the physical server and the physical L-Server.
For details, refer to "17.8.1 Installation".
Even if modification of the L-Server configuration failed, part of the information may be successfully modified. In this case, it takes a while for the modified information to be reflected. The virtual machine information is reflected through periodic queries.
[KVM] [Solaris Zones (Solaris 10)]
Disk and Network information are not updated.
[Solaris Zones (Solaris 11)]
Network information is not updated.
[Xen] [OVM for x86 2.2]
Server, Disk, and Network information are not updated.
