HP Matrix Operating Environment 7.3 and 7.3 Update 1 Infrastructure Orchestration User Guide

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
NOTE: Some virtualization technologies support the ability to modify memory and/or CPU
attributes without rebooting the VM (For example, enabling HotAddMemory and HotPlugCPU
on virtual machines). When supported by the virtualization technologies, these capabilities are
enabled by default for VMs created by Matrix infrastructure orchestration or by Matrix OE
Visualization. The steps required for the guest OS to recognize such changes are OS dependent.
The GUI, CLI, and API forms of this operation provide an option to cancel the request if the
hypervisor requires a reboot. The GUI defaults to a selected check box to avoid the reboot, which
can be cleared to allow the reboot. The API and CLI continue to perform the reboot by default, but
an administrator can specify new options avoid the reboot.
Support for this feature varies by VM type as noted in the following table:
Processor Changes (HotPlugCPU)Memory Changes (HotAddMemory)
VM type
SupportedSupportedVMware ESXi
Not supportedDynamic Memory supported in
Hyper-V 2012 only
Microsoft Hyper-V
Not supportedNot supportedHP Integrity
Managing floating IP addresses
Some cloud providers support floating (also known as elastic) IP addresses, which provide the
ability to manage the assignment of public IP addresses to servers.
From the tab in infrastructure orchestration console, you can perform the following:
Create a new floating IP address and associate it with a cloud logical server.
Move an existing floating IP address from one cloud logical server to another.
Remove a floating IP address from a cloud logical server and release its allocation.
116 Matrix infrastructure orchestration provisioning and allocation