HP CloudSystem Matrix/Matrix Operating Environment 7.2 Integration Interfaces API and CLI Operations Reference Guide

1 Introduction

HP CloudSystem Matrix is the industry’s first Converged Infrastructure platform that doubles

administrator productivity and reduces total cost of ownership (TCO) versus traditional infrastructures.

HP CloudSystem Matrix integrates silos of compute, storage, network, and facilities resources with

unified management to deliver a virtualized, highly automated environment. The HP Matrix

Operating Environment (Matrix OE) provides the automated provisioning, optimization, and

recovery management capabilities for HP CloudSystem Matrix.

This document describes the rich set of HP Matrix OE infrastructure orchestration (IO) interfaces

available to HP customers, partners, and integrators. These interfaces allow customers to integrate

Matrix OE into their business and IT operations processes. Partners and Integrators can use the

interfaces in combination with their own offerings to provide new, rich capabilities. HP is committed

to an industry open standard cloud services API, and submitted this content to the Distributed

Management Task Force (DMTF) Cloud Incubator, which has now been moved to the recently

formed DMTF Cloud Management Working Group.

The API and CLI interfaces were introduced in HP BladeSystem Matrix/Matrix OE (Insight Dynamics)

6.0, and are expected to be compatible with subsequent releases, but are subject to change due

to evolving standards. Future releases may include additional interfaces.

HP Matrix OE infrastructure orchestration provides extensive out-of-the-box functionality that is

pre-integrated with HP Insight Control and HP System Insight Manager software, including:

• A graphical designer used to create templates describing the architecture and requirements

of infrastructure services. These templates are published into a catalog.

• Self service users pick a particular template from the catalog and initiate the creation of an

infrastructure service from that template.

• Administrative users create pools containing blades, virtual machine hosts together with

associated storage and subnets. One or more pools are assigned to one or users and this

defines the potential set of resources that can be used in the processing of self service user

requests. Administrative users also can review, approve, or reject user requests.

• After creation of the service, the self-service user can further extend the service. For example,

add additional disk and server resources to the service. In non-peak periods server resources

can be deactivated, allowing those resources to be powered down, or used by another service.

• IO includes an embedded version of HP Operations Orchestration (OO) workflow engine.

This engine can be used by customers and partners to extend the capabilities of IO and to

allow IO operations to be integrated into the customer environment.

• All access to IO functionality is secured by username/password login and restricted by the

assigned role of the particular user.

◦ The most restrictive role, User, has access to published templates (or a subset) and their

own services. User requests are subject to approval by an Administrator.

◦ The Architect role extends the capability of User, allowing the creation and publication

of templates, as well as the provisioning of non-published templates to allow testing.

◦ The Organization Administrator role extends the role of Architect, and allows the viewing

and manipulation of all services owned by that organization. Organization Administrator

initiated operations do not need their own approval.

◦ The Service Provider Administrator role also extends the role of Architect, and allows the

viewing and manipulation of all services in the environment. Service Provider Administrator

initiated operations do not need their own approval.