Automated allocation – HP Matrix Operating Environment Software User Manual
Page 151
3.
Use the HP Insight managed system setup wizard (MSSW) to configure the system to be
managed. From Systems Insight Manager, select Configure
→Managed system setup wizard.
For more information, see the Insight Managed System Setup Wizard Getting Started Guide
located at the following website:
NOTE:
Cross-technology logical servers are not supported by Matrix infrastructure orchestration. A logical
server created in Matrix infrastructure orchestration (by deploying a service template) cannot be
managed as a cross-technology logical server. For example, if a physical logical server is created
in IO, it cannot be moved to a virtual machine using Matrix OE logical server management.
Similarly, if a virtual logical server is created in IO, it cannot be moved to a server with Virtual
Connect. Only logical servers created or imported in Matrix OE visualization (using Create
→
Logical Server, or Tools
→Logical Servers→Import ) can be moved from physical to virtual or virtual
to physical.
For more information about cross-technology logical servers, see the HP Matrix Operating
Environment Logical Server Management User Guide and the HP Matrix Operating Environment
Recovery Management User Guide located at the following website:
Automated allocation
Allocation is the process of finding the resources to match to the logical objects described in a
template. An infrastructure orchestration template is the logical specification of an infrastructure
service using template components known as logical objects, enabling the user to provision an
infrastructure service from resources.
In infrastructure orchestration templates, logical objects are specified either by attribute value or
by name. Logical server groups and storage are specified by attribute value, and networks are
specified by name or attribute. The process of matching logical objects to resources is a key
capability of infrastructure orchestration and is part of several request types, including Create
Service request.
After validating the arguments of a Create Service request, the infrastructure orchestration controller
performs an allocation. If infrastructure orchestration can locate the resources that match the
template, then the allocation is successful. After a successful match, infrastructure orchestration
reserves the selected resources and provisions to instantiate the infrastructure service specified by
the template. If infrastructure orchestration does not locate the necessary resources, the request
fails, the resources are not reserved, and the infrastructure service is not created.
Matrix infrastructure orchestration can also utilize the allocation process during the provisioning
process. This internal allocation process can begin when infrastructure orchestration cannot
successfully provision a logical sever. Matrix infrastructure orchestration releases the allocated
server and attempts another allocation to find a replacement server and continue the provisioning.
If the reallocation fails, the Create request fails.
When viewing logical resources in isolation, infrastructure orchestration might not be able to
successfully allocate the template. Matrix infrastructure orchestration cannot allocate a network
without successfully allocating the logical server groups connected to that network. Similarly,
infrastructure orchestration cannot allocate logical server groups without successfully allocating the
storage for all the servers within the group.
When infrastructure orchestration executes the allocation algorithm to search for resources, it
attempts to allocate networks, then logical server groups, and finally storage. To maximize the
chances of success, within each category, the allocation algorithm always attempts to allocate the
most constrained logical object first. For example, all the networks in a template are evaluated,
and the network with the smallest number of candidate subnets is chosen to allocate first.
Automated allocation
151