Operating Environment Software Instruction Manual

To edit a virtual server
1. Open the infrastructure orchestration console, self service portal, or organization administrator
portal
2. Select the Services or My Services tab
3. Select a service and click Details or View Details
4. From the Actions or Server Actions list, select Edit virtual servers
5. Expand the tree and select the virtual machine you want to edit
6. Increase or decrease the number of processors by using the arrows in the Number of Processors
field, up to the Maximum (shown in red).
The initial and maximum values are specified on the infrastructure orchestration designer
Configure Server Group Config tab, in Processors Per Server.
7. Enter a new value in the Memory Size field, up to the Maximum (shown in red).
The initial and maximum values are specified on the infrastructure orchestration designer
Configure Server Group Config tab, in Memory Size.
The Cost per Processor and Cost per Unit of Memory are also displayed, and reflect the values
entered on the Configure Server Group Config tab.
The Total Reconfiguration Cost shows the total changed cost of the increased or decreased
number of processors or amount of memory, based on the per unit cost specified on the
Configure Server Group Config tab.
During this operation, infrastructure orchestration:
• Validates the request
• Obtains approval
• Sends an edit logical server request to Matrix OE logical server management with the
corresponding parameters for each of the request’s target servers
• Updates the IO service metadata based on the request execution results
Provisioning physical servers using local disk
Matrix infrastructure orchestration includes support for Virtual Connect logical servers using a local
disk for boot. (Local disk is also referred to as DAS, or Direct Attached Storage.) Although these
logical servers lack the flexible movement of those using boot from SAN, a logical server using
local disk boot can be initially activated on a server, the operating system installed on the local
disk, and then later suspended and activated back onto that same physical server. If the logical
server is activated on a different physical server (with a local disk of suitable size), the operating
system must be re-deployed.
In a Virtual Connect environment, the Matrix OE software automatically gathers information about
server blades (memory, processors, and potential connectivity). Local disk information is not currently
gathered, so it is necessary to annotate the collected server information to indicate if it has a local
disk with particular properties. Local disk boot volumes are not represented by storage pool entries.
You can enable Matrix infrastructure orchestration to provision to a physical server using local
disk. This involves some manual edits of property files to ensure that Matrix is aware of the servers
that have local disks and that have mobility restrictions.
See “Modifying physical servers with local disk information” in the HP Matrix Operating Environment
Logical Server Management User Guide at http://www.hp.com/go/matrixoe/docs.
Allocating servers to a VM Host
Matrix infrastructure orchestration uses the following guidelines to determine the VM Host that will
host a newly provisioned virtual machine.
Matrix infrastructure orchestration lifecycle operations 97