8.3.2 Setting virtualization configuration information
To manage a virtualization system configuration, you must set virtualization configuration information in IM Configuration Management. Even if you manage a system hierarchy that includes virtual hosts, you do not have to set virtualization configuration information when you do not use the function that displays virtual system configuration on the Host List page. For details, see 8.3 Virtualization configuration management.
The following three methods can be used to set virtualization configuration information.
- Organization of this subsection
(1) Entering host information of virtual hosts in IM Configuration Management
Directly register virtual hosts as the hosts to be managed. Select Virtual host for the host type, and then specify VMM host.
(2) Importing information of hosts in virtualization configuration
Acquire information of hosts in virtualization configuration, and merge it with the host input information file that is output from IM Configuration Management. Then import the merged host input information file into IM Configuration Management.
The following figure shows the flow of updating information of hosts in virtualization configuration.
|
If there are multiple virtualization configuration information files, repeat the jcfmkhostsdata command as many times as the number of files to complete updating host information.
The following figure shows an example of updating virtualization configuration information.
|
(3) Performing collection or batch-collection of virtualization configuration from the IM Configuration Management window
Addition of VMM hosts and changes of virtualization configuration are applied to virtualization configuration information, and the information is displayed in the IM Configuration Management window.
(a) When host information is updated
If collected virtualization configuration information includes host information that indicates that a host is already registered in the IM configuration management database, IM Configuration Management treats the collected host information and the registered host information as being the same and updates the host type in the host information. If the host type in the collected host information differs from the host in the host information registered in the IM configuration management database, IM Configuration Management does not update the host information because the hosts might be different despite having the same host name. If, however, the host type of the hosts is Unknown, IM Configuration Management updates the host information. Note also that the status of the collection of virtualization configuration information is not the same for a registered host whose host type is different and for a virtualization system management host managing a registered host whose host type is different. Table 8-21 describes the host type conditions for updating host information, and Table 8-22 describes changes in the status of the collection for virtualization configuration information.
Type of host from which information collected |
Registered host type |
|||
---|---|---|---|---|
Physical host |
Logical host |
Virtual host |
Unknown |
|
Physical host |
Y |
N |
N |
Y |
Logical host |
-- |
-- |
-- |
-- |
Virtual host |
Y/N#1 |
N |
Y |
Y |
Unknown (hosts managed by HCSM not running Hitachi Compute Blade logical partitioning feature) |
N |
N |
N |
Y |
Unknown#2 |
Y |
-- |
Y |
-- |
- Legend:
-
Y: Can be updated.
Y/N: Can be updated conditionally.
N: Cannot be updated.
--: Not applicable.
#1: Host information can be updated if the host meets both of the following conditions. The host type of the host meeting the conditions is Virtual host.
-
KVM is the registered virtual manager type of the host.
-
Hitachi Compute Blade logical partitioning feature is the virtual manager type of the VMM host.
#2: The relevant host does not exist in the collected data, or the data has been deleted.
Status of virtualization configuration information collection |
Trigger for changing the status of virtualization configuration information collection |
---|---|
No information collected |
Host information has not been collected yet. |
Collection failed |
The collection of host information failed because an attempt to connect to the host failed, the user could not be authenticated in the OS, or a condition for managing the virtualization system configuration was not met. |
Information collected |
The collection of host information was successful. |
Mismatch |
The host type in the collected host information differs from the host type registered in the IM configuration management database. |
When virtualization configuration information is collected from the virtualization system management host, the virtualization configuration information on the hosts managed by the virtualization system management host is updated. Also, when this information is collected, the information (VMM host information) about the relationship between the virtualization system management host and VMM hosts is collected and stored in the IM configuration management database. However, if the virtualization system management host is deleted or the virtualization configuration information of the virtualization system management host is changed, the stored VMM host information will be deleted. For details, see 8.3.2(3)(c) When VMM host information is deleted.
If virtualization configuration is changed when virtualization configuration is collected, the virtualization configuration is changed as shown in the following table.
Change |
Virtualization configuration after collection |
---|---|
A virtual host is added. |
The host is added, and VMM host information is provided. |
A virtual host is deleted. |
|
A virtual host is moved. |
VMM host information of the host is updated. |
A stopped virtual host starts. |
No configuration change. |
A running virtual host stops. |
No configuration change. |
A running virtual host is suspended. |
No configuration change. |
A VMM host is added. |
The VMM host and virtual hosts running on the VMM host are registered. |
A VMM host is deleted. |
|
(b) When virtualization configuration information is deleted
If the host type in the collected virtualization configuration information is Logical host or Unknown, virtualization configuration information cannot be maintained. Therefore, even if virtualization configuration information is set when the host type is Physical host or Virtual host, if the host type is changed to Logical host or Unknown, the virtualization configuration information is deleted.
The following table describes the cases when virtualization configuration information is deleted when the host type is changed.
Host type before change |
Host type after change |
|||
---|---|---|---|---|
Physical host |
Logical host |
Virtual host |
Unknown |
|
Physical host |
N |
Y |
N |
Y |
Logical host |
-- |
-- |
-- |
-- |
Virtual host |
N |
Y |
N |
Y |
Unknown# |
-- |
-- |
-- |
-- |
- Legend:
-
Y: Deleted.
N: Not deleted.
--: Not applicable.
#: The relevant host does not exist in the collected data, or the data has been deleted.
(c) When VMM host information is deleted
VMM host information is deleted from the IM configuration management database in the following cases:
-
The virtualization system management host on which vCenter, JP1/SC/CM, SCVMM, or HCSM is installed is deleted.
-
The virtual manager type of the virtualization system management host on which vCenter, JP1/SC/CM, SCVMM, or HCSM is installed is changed.
-
The host type of the virtualization system management host on which vCenter, JP1/SC/CM, SCVMM, or HCSM is installed is changed.