HP Logical Server Management Best Practices

and thus it is necessary to annotate the collected server information with local disk information. Local disk boot

volumes are not represented by storage pool entries. Rather, the server is annotated to indicate is has a local disk

with particular properties.

These annotations are done through the following steps:

1. Use the lsmutil -export –an –file filename.xml command to create a filename.xml file

containing the servers that can support a local disk.

2. Edit the filename.xml file to include local disk information for appropriate servers.

3. Use the lsmutil -import –an –file –filename.xml command to make Matrix OE aware of that

new information.

There is an option to the lsmutil command to enable the administrator to export an XML file containing the physical

resources representing server blades on which a logical server may be activated. That file can be annotated to

indicate various blades have local disks, and imported to ensure Matrix OE is now aware of the local disk properties.

When Matrix infrastructure orchestration is provisioning resources, it will be able to determine which physical blades

have suitable local disks to meet the needs specified in the template. Matrix infrastructure orchestration can then

create and activate a logical server as appropriate. It is currently not possible to create a logical server through the

Create Logical Server graphical user interface and specify local disk. Local disk support is only available for logical

servers created by MatrixIO.

The lsmutil -export –an –file filename.xml command is used to create an XML file which contains the

current descriptions of the physical servers in the environment. The format of the file is discussed below.

The created file will contain a <CliComputePhysical> element for each physical blade server capable of hosting

a logical server. Each is identified by a name and a UUID. The portability group is also indicated.

The following XML example shows one physical resource which does have a local disk defined.

<?xml version="1.0" encoding="UTF-8" ?>

<name>lsaserver04</name>

<portabilityGroupName>razor_saw</portablityGroupName>

<name>local_disk1</name>

<description>My Local Disk</description>

<storageType>LOCAL</storageType>

<sharable>false</sharable>

</CliLocalDisk>

</CliComputePhysical>

</ComputeActuals>

The file can be edited to indicate local disk information in the <CliLocalDisk> element of the

<CliComputePhysical> for each physical server having local disk to be used for boot. Key properties (shown in

bold in the above XML) are:

 <name> to identify the disk

 <storageType> set to LOCAL

 <storageSizeType> set to MB or GB

 <raidLevel> set to NONE