HP Matrix Operating Environment Software - Manual (Page 13)

Software deployment and service provisioning
Matrix infrastructure orchestration supports a variety of mechanisms for operating system software
deployment. Operating system software can be realized as an image derived from a virtual server,
or as deployment software such as an Insight Control server deployment job, an Ignite-UX job, or
an HP Server Automation (SA) job. Each subtype represents an approach for offering selectable
software that can be installed on a physical or virtual server.
To simplify system software deployment, infrastructure orchestration utilizes virtual machine templates,
physical server deployment jobs, and Operations Orchestration workflows.
During provisioning, infrastructure orchestration executes associated Operations Orchestration
workflows at their respective execution points. After infrastructure orchestration processes the
request, the resulting service is maintained on a user-by-user basis with a set of physical and virtual
resources that reflects the original template design. Running infrastructure services can be modified
in many ways, including adding servers and data disks.
API and CLI support
Matrix infrastructure orchestration supports an Application Programming Interface and a Command
Line Interface (ioexec). For information about using these interfaces, see HP CloudSystem
Matrix/Matrix Operating Environment Integration Interfaces at
Matrix Operating Environment
Information Library .
For each operation, the API call is specified in CamelCase, and the ioexec CLI is specified using
separate words. For example, getOrganization is the API call, while get organization is
the command.
The infrastructure orchestration CLI can be invoked remotely. On the remote CMS command line,
enter ioexec --help for more information.
Alternatively, perform the following steps to invoke the CLI from the remote CMS using default
connection parameters:
1. Copy the zip file from ..\Program Files\HP\Matrix infrastructure
orchestration\cli
to the CMS from which you want to run the CLI.
2. Copy sample-ioexec.properties to the user's home directory (for example, C:\users\
Administrator
).
3. Rename sample-ioexec.properties to ioexec.properties.
4. Modify the file to specify a default host, username, and password, and other values, if desired.
Software deployment and service provisioning 13