The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter includes the following sections:
Multi-tenancy allows you to divide up the large physical infrastructure of an instance into logical entities known as organizations. As a result, you can achieve a logical isolation between organizations without providing a dedicated physical infrastructure for each organization.
You can assign unique resources to each tenant through the related organization, in the multi-tenant environment. These resources can include different policies, pools, and quality of service definitions. You can also implement locales to assign or restrict user privileges and roles by organization, if you do not want all users to have access to all organizations.
If you set up a multi-tenant environment, all organizations are hierarchical. The top-level organization is always root. The policies and pools that you create in root are system-wide and are available to all organizations in the system. However, any policies and pools created in other organizations are only available to organizations that are above it in the same hierarchy. For example, if a system has organizations named Finance and HR that are not in the same hierarchy, Finance cannot use any policies in the HR organization, and HR cannot access any policies in the Finance organization. However, both Finance and HR can use policies and pools in the root organization.
If you create organizations in a multi-tenant environment, you can also set up one or more of the following for each organization or for a sub-organization in the same hierarchy:
The root organization is always the top level organization.
In a multi-tenant environment, Cisco UCS uses the hierarchy of an organization to resolve the names of policies and resource pools. When Cisco UCS Manager searches for details of a policy or a resource assigned to a pool, the following occurs:
In this example, all organizations are at the same level below the root organization. For example, a service provider creates separate organizations for each customer. In this configuration, organizations only have access to the policies and resource pools assigned to that organization and to the root organization.
In this example, a service profile in the XYZcustomer organization is configured to use servers from the XYZcustomer server pool. When resource pools and policies are assigned to the service profile, the following occurs:
In this example, each organization includes at least one suborganization. For example, a company could create organizations for each major division in the company and for subdivisions of those divisions. In this configuration, each organization has access to its local policies and resource pools and to the resource pools in the parent hierarchy.
In this example, the Finance organization includes two sub-organizations, AccountsPayable and AccountsReceivable. A service profile in the AccountsPayable organization is configured to use servers from the AP server pool. When resource pools and policies are assigned to the service profile, the following occurs:
The following example creates an organization named Finance under the root organization and commits the transaction:
UCS-A# scope org / UCS-A /org # create org Finance UCS-A /org* # commit-buffer UCS-A /org #
Command or Action | Purpose | |||
---|---|---|---|---|
Step 1 | UCS-A# scope org / | Enters the root organization mode. |
||
Step 2 | UCS-A /org # scope org org-name | Enters organization mode for the specified organization.
|
||
Step 3 | UCS-A /org # create org org-name | Creates the specified organization under the previously configured non-root organization and enters organization mode for the specified organization. |
||
Step 4 | UCS-A /org # commit-buffer | Commits the transaction to the system configuration. |
The following example creates an organization named Finance under the NorthAmerica organization and commits the transaction:
UCS-A# scope org / UCS-A /org # scope org NorthAmerica UCS-A /org # create org Finance UCS-A /org* # commit-buffer UCS-A /org #
Command or Action | Purpose | |
---|---|---|
Step 1 | UCS-A# scope org / | Enters the root organization mode. |
Step 2 | UCS-A /org # delete org org-name | Deletes the specified organization. |
Step 3 | UCS-A /org # commit-buffer | Commits the transaction to the system configuration. |
The following example deletes the organization under the root organization named Finance and commits the transaction:
UCS-A# scope org / UCS-A /org # delete org Finance UCS-A /org* # commit-buffer UCS-A /org #