Multi-Tenancy in HP Matrix Operating Environment Infrastructure Orchestration

ManualsBrandsHP ManualsSoftwareHP Matrix Operating Environment w/Insight Control 24x7 Supp Tracking Lic

Technical white paper

Multi-Tenancy in HP Matrix

Operating Environment

Infrastructure Orchestration

Table of Contents

Introduction .................................................................................................................................. 2

Multi-Tenancy ............................................................................................................................... 2

Service Provider and Organization levels ........................................................................................ 2

Console ....................................................................................................................................... 3

Template Tab............................................................................................................................ 3

Request and Services Tabs ......................................................................................................... 4

Servers Tab .............................................................................................................................. 4

Storage, Users, Networks, and Software Tabs .............................................................................. 5

Calendar Tab ........................................................................................................................... 5

Organization............................................................................................................................ 5

Organization Administrator Portal .................................................................................................. 7

Home Tab ................................................................................................................................ 8

Templates Tab .......................................................................................................................... 8

Requests Tab ............................................................................................................................ 8

Services Tab ............................................................................................................................. 8

Servers Tab .............................................................................................................................. 8

Software Tab ............................................................................................................................ 8

Networks Tab ........................................................................................................................... 8

Organization Tab ..................................................................................................................... 8

Users Tab ................................................................................................................................. 9

Organization Users and the Self Service Portal ................................................................................ 9

Customizing the Organization Self Service and Administrator Portals ................................................. 9

Integration with Active Directory ................................................................................................... 11

Logical Server Hostnames ............................................................................................................ 12

Access to Resources .................................................................................................................... 12

Information Security .................................................................................................................... 15

Multi-Tenancy and IO Template Design ......................................................................................... 16

Capacity Pools ........................................................................................................................... 16

Physical Provisioning Failures ....................................................................................................... 17

Additional features for Multi-Tenancy ............................................................................................ 18

API/CLI for Multi-Tenancy ............................................................................................................ 18

INDEX ....................................................................................................................................... 20

Click here to verify the latest version of this document

Summary of content (21 pages)

PAGE 1
Technical white paper Multi-Tenancy in HP Matrix Operating Environment Infrastructure Orchestration Table of Contents Introduction ..................................................................................................................................2 Multi-Tenancy ...............................................................................................................................2 Service Provider and Organization levels ................................................................
PAGE 2
Introduction This document, which is aimed at readers familiar with IO, describes the Multi-Tenancy feature in HP Matrix OE infrastructure orchestration version 7.3. When significant differences exist in other versions of the solution (such as pre-7.0, 7.0, 7.1, or 7.2) they will be noted. It covers the notion of Organization and the role of the three IO portals: Administrator Console, Organization Administrator Portal and the Self-Service Portal, as well as the multi-tenancy features of the API/ CLI.
PAGE 3
• Organizations o o An organization has its own virtual IO system with  Organization Administrator and Organization User roles.  Maintenance and Unassigned Pools Organizations are created dynamically by the Service Provider Administrator who makes resources available to them. Organizations have unique names. o The Organization Admin uses an Organization Portal to manage the Organization’s virtual IO system.
PAGE 4
Request and Services Tabs The Service Provider Administrator has full access and control of all requests and services in the entire IO system, irrespective of whether they originate from the Service Provider or an organization. Figure 3: Requests Tab The Request messages in the Request tab also show the organization affiliation of the User who submits the Request. Similarly the Services tab shows the affiliation of each Service.
PAGE 5
Figure 6: Console Servers tab Details Storage, Users, Networks, and Software Tabs The Storage tab lists the available storage resources and their details. The Users tab lists all the Users at the Service Provider level and counts of the number of Server Pools and Templates that have been assigned to each User. The Networks tab lists all the networks available and allows network details to be displayed; likewise the Software tab lists all the available software items.
PAGE 6
Organizations must be given unique names. The Service Provider administrator populates the Organization Administrator and Organization User roles by adding pre-existing local Windows Users. If the CMS is part of a Windows domain, pre-existing Active Directory Users or Groups can also be added. The organization can be edited at any time, e.g., administrators and users can be added or removed. Organizations are given a unique identifier, of form org, when they are created.
PAGE 7
The Organization tab also allows resources to be removed from an organization, by moving them from right to left. The servers move to the Service Provider’s Unassigned Pool. Figure 10: Returning servers to the Service Provider NOTE: An organization can be deleted only if it has no compute servers and no services.
PAGE 8
Home Tab View a dashboard summarizing resource availability, provisioned servers, and request activity. Templates Tab View the templates assigned to the organization both published and unpublished. Templates can be assigned to and unassigned from Organization Users. However unpublished templates can be used by administrators. Submit create service requests using a template and the resources assigned to the organization.
PAGE 9
Users Tab View a list of users and groups and the pools assigned to them. A user can be a member of multiple groups. Organization Users and the Self Service Portal Organization Users access IO via the Self-Service Portal 3 which has a few minor changes from pre-7.0 versions: • • • The URL has the form https://:51443/ssp/ 4 The login page can be customized by the Organization Admin.
PAGE 10
The Change buttons allow new images to be uploaded and various text fields to be modified. Updates can be undone using Restore Default 5. The Links section on the Home page of the Self Service Portal, can also be customized, by default the links are Getting started, View services, View requests and View messages. The Organization Admin can modify the text and the URL of these links, for example to provide a user support link for the Organization.
PAGE 11
Figure 15: The login page for the blue sky cloud Self Service Portal. Integration with Active Directory IO works with one or more Active Directories allowing Windows User Groups, as well as individual Users, to be given access to resources. Nested AD Groups to a depth 1 are supported 6; see Figure 16 below. When IO is installed, three local User Groups (HPIO_Administrators, HPIO_Architects and HPIO_Users) are created.
PAGE 12
Logical Server Hostnames Each logical server belonging to a service has a hostname. Hostnames are constructed from • • • A string in the IO template and A hostname completion string supplied when the create service request is submitted An integer identifying the logical server within its logical server group. IO utilizes the Matrix OE logical server management capabilities to provision services, which requires that hostnames be globally unique.
PAGE 13
Service Provider User Access Organization User/Group Access How Created Service Provider Admin Controls Storage Pool Entries 8 Matrix autogenerates, or Service Provider Admin creates using Matrix OE visualization, optionally using HP SPM Based on need, can have separate SPM storage templates for each organization 9, or share templates. Can tag storage by organization.
PAGE 14
Provider Administrator can see all the compute resources assigned to an organization; however the structure of the organization’s Server Pool is not visible. An organization has its own Maintenance Pool which holds compute resources that have been withdrawn from use. The Organization Administrator can move servers in and out of the Maintenance pool. All the nodes of a cluster should be kept at the Service Provider level or be assigned to the same organization; this is not enforced by IO.
PAGE 15
Information Security A key requirement for multi-tenancy is to ensure that information from one organization does not leak to another, thus it is important that the IO artifacts are kept private. The following tables show the filtering of information.
PAGE 16
Multi-Tenancy and IO Template Design In order for an IO template to be used for provisioning by members of an organization, there must be accessible resources assigned to the organization. The following are necessary but not sufficient constraints. Networks: • In order to have one template assigned to multiple organizations, specify its networks by desired attribute. o Define a set of networks and assign each to a different organization.  Hint: Use of a naming convention (e.g. mgmt-1, mgmt-2 etc.
PAGE 17
Figure 17: ESX resource pool parent VMware Resource Pools are intended to be used in a multi-tenancy environment to allow the sharing of a VMcluster (or host) between different organizations. In a clustered situation they are most effective if HA/DRS is switched on as it allows virtual machine load to be dynamically balanced across hosts.
PAGE 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.
PAGE 19
• unassignAdministratorsFromOrganization • assignUsersToOrganization • unassignUsersFromOrganization • syncOrganizations Note that renaming an organization cannot be done from the API/CLI only from the Service Provider Admin Console. The full specification of the API and CLI is contained in the HP CloudSystem Matrix/Matrix Operating Environment Integration Interfaces API and CLI Operations Reference Guide available at http://www.hp.com/go/matrixoe/docs.
PAGE 20
INDEX Active Directory, 12 Cloud Resources in IO, 20 Clusters assigning clusters to Organizations, 15 assigning VMclusters to Organizations, 19 VMclusters and ESX resource pools, 18 Compute Resources access rules, 13 assigning to an Organization, 7, 14 ESX Resource Pools best practice assigning to Organizations, 19 definition, 18 deletion of, 19 discovery of, 19 homogeneous IO server Pools, 19 parent of, 19 IO Templates access rules, 13 assigning to multiple Organizations, 18 created by Service Provider Arc
PAGE 21
Sign up for updates hp.com/go/getupdated Share with colleagues © Copyright 2013–2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.