Multi-Tenancy in HP Matrix Operating Environment Infrastructure Orchestration

18
The Service Provider Administrator must use the Matrix logical server management capabilities to perform the
“Manual clean-up process” as described in the Matrix infrastructure orchestration User Guide. Once this has been
performed, the Organization Administrator can move the blade(s) back to a server pool. In IO v7.3, the necessary
communication between an Organization Administrator and a Service Provider Administrator is out of band.
Additional features for Multi-Tenancy
The Matrix 7.3 release introduced a variety of features which offer value in a multi-tenancy environment (as well as
other environments). The Service Provider Administrator can choose to take advantage of the features summarized
below. More detail is available in the Matrix Operating Environment 7.3 Release Notes and Matrix infrastructure
orchestration User Guide (at http//www.hp.com/go/matrixoe/docs
).
• Optional License Agreement: Can enable the display of a license agreement and require the acceptance of terms
before a service request can be submitted. The Administrator or User cannot click “Submit” until they check the
box indicating they accept the terms. The Service Provider Administrator can customize the link to the terms and
the text for the checkbox.
• Customized Server Actions: The Service Provider Administrator can specify up to three Operations Orchestration
workflows which can be invoked from the Server Actions menu. The workflows are common across the Service
Provider and all Organizations.
• Skip OS Customization: The Service Provider Administrator can make the Matrix infrastructure orchestration NOT
automate the customization of an OS. Once enabled, this can be set by the Service Provider Architect for the
appropriate templates being used by the Organizations. It is still necessary that the OS customization be
performed, perhaps through Operations Orchestration workflows.
• Configure IP Assignment Type as None/External: The Service Provider Architect can indicate a particular network
connection within a Matrix IO service template does not require a Matrix-managed IP address. There may be no
need for an IP address (e.g., if doing active/active NIC teaming), or the IP addresses could be managed
external to Matrix. It is necessary to have a Matrix-managed IP address on the primary network interface for
each server.
• Console Access: By default, the 7.3 release includes links for SSH, VNC, and RDP. In order to work, the systems
and browsers must be appropriately configured, e.g. PuTTY to handle SSH links, with URL protocol handler
registered in browser. The Service Provider Administrator can adjust the URL launches (e.g., adding telnet if
desired).
API/CLI for Multi-Tenancy
All the API operations and CLI commands respect organization and Service Provider access rights. When invoked by
an Organization Administrator, a command can only access resources assigned to the organization or objects, such
as requests, created by the organization roles. In the case of Organization Users, access is restricted to resources
assigned to the User or objects created by him. Similarly, results of commands are filtered so that they only return
assigned resources.
The following is a full list of the organization specific commands:
• listOrganization
• getOrganization
• createOrganization
• deleteOrganization
• assignTemplateToOrganization
• unassignTemplateFromOrganization
• assignServerToOrganization
• unassignServerFromOrganization
• assignSubnetToOrganization
• unassignSubnetFromOrganization
• assignSoftwareToOrganization
• unassignSoftwareFromOrganization
• assignAdministratorsToOrganization