HP Matrix Operating Environment 7.2 Update 1 Infrastructure Orchestration User Guide

4. Delete the organization from the infrastructure orchestration console Organization tab.
Assigning users to an organization
Using the infrastructure orchestration console, the service provider administrator populates the
<organization-id>_Administrators and <organization-id>_Users groups by adding
pre-existing local Windows users. If the CMS is part of a Windows domain, pre-existing Active
Directory users and groups can also be added to the <organization-id>_Administrators and
<organization-id>_Users groups.
When a Highly Available (HA) CMS fails over to a new node, the
<organization-id>_Administrators and <organization-id>_Users groups for each
organization are automatically created on the new node. Groups that are no longer valid for the
currently active node are removed.
NOTE: If the service provider administrator modifies the <organization-id>_Administrators
or <organization-id>_Users groups outside of the organization administrator portal (for
example, in Windows Local Users and Groups), Matrix infrastructure orchestration must be running
in Systems Insight Manager. Otherwise, any changes are lost when infrastructure orchestration is
restarted.
After any changes are made outside of the organization administrator portal, run ioexec sync
Organizations, or wait for IO to synchronize the changes automatically based on the value of
organization.sync.interval in the ..\Program Files\HP\Matrix infrastructure
orchestration\conf\hpio.properties file. The default is 600 seconds (10 minutes).
Adding resources to an organization
The service provider administrator assigns a compute resource to an organization on the
infrastructure orchestration console Organization tab.
The newly created organization contains, by default, Maintenance and Unassigned pools.
IMPORTANT: To be assigned to an organization, a compute resource must be in the service
provider Unassigned pool, and cannot be in use.
After it has been assigned to an organization, the compute resource appears in the organization’s
Unassigned pool. The Organization tab also allows resources to be removed from an organization.
These removed compute resources move to the service provider’s Unassigned pool.
The service provider administrator can assign and unassign:
• A set of compute resources, where a compute resource can be a virtual machine host, a
physical blade, an ESX Resource Pool or a Cloud Resource.
A compute resource cannot be shared among organizations.
The service provider and organization administrator can create resource pools. A compute
resource can be assigned to or from an organization if it is not in use and it is in an Unassigned
pool. Only an organization’s Unassigned pool is visible to the service provider administrator.
HP recommends that all nodes of a cluster are kept at the service provider level or assigned
to the same organization.
• A set of networks.
Networks can be assigned to multiple organizations. Sharing networks among organizations
is not prevented by infrastructure orchestration; it is a service provider policy decision. The
service provider administrator can assign a network to one or multiple organizations. An in-use
network can be de-assigned from an organization. Any existing services are unaffected, but
organization users can no longer create services that use the network. If the service provider
policy forbids network sharing, then any services using the network must be deleted before
the network is re-assigned to another organization.
166 Multi-tenancy in Matrix infrastructure orchestration