Menu Close

Chapter 9. Cloud Tenants

A tenant is an OpenStack term for an organizational unit or project. CloudForms creates cloud tenants to match existing OpenStack tenants for managing resources and controlling visibility of objects.


OpenStack tenant mapping must be enabled for cloud tenants to be created. See Section 9.1, “Tenant Mapping” for details.

OpenStack uses tenants for the following reasons:

  • Assigning users to a project
  • Defining quotas for a project
  • Applying access and security rules for a project
  • Managing resources and instances for a project

This helps administrators and users organize their OpenStack environment and define limits for different groups of people. For example, one project might require higher quotas and another project might require restricted access to certain ports. OpenStack allows you to define these limits and apply them to a project.

Red Hat CloudForms can abstract information from tenants including quotas and relationships to other OpenStack objects.

To see multiple tenants in Red Hat CloudForms, the user authenticating to your OpenStack environment from Red Hat CloudForms must be configured to have visibility into these tenants.


This section describes OpenStack cloud tenant usage. For information about tenants created in CloudForms for access and resource control, see Access Control in General Configuration.

9.1. Tenant Mapping

When adding an OpenStack cloud or infrastructure provider, enable tenant mapping in CloudForms to map any existing tenants from that provider.

This means CloudForms will create new cloud tenants to match each existing OpenStack tenant; each new cloud tenant and its corresponding OpenStack tenant will have identical resource assignments (including user and role synchronization) with the exception of quotas. Tenant quotas are not synchronized between CloudForms and OpenStack, and are available for reporting purposes only. You can manage quotas in CloudForms but this will not affect the quotas created in OpenStack.

During a provider refresh, CloudForms will also check for any changes to the tenant list in OpenStack. CloudForms will create new cloud tenants to match any new tenants, and delete any cloud tenants whose corresponding OpenStack tenants no longer exist. CloudForms will also replicate any changes to OpenStack tenants to their corresponding cloud tenants.

If you leave tenant mapping disabled, CloudForms will not create cloud tenants or tenant object hierarchy from OpenStack.

See Chargeback in Managing Providers for information on configuring OpenStack providers.

9.2. Viewing Cloud Tenant Relationships

From ComputeCloudsTenants, click on a specific cloud tenant to view its details.

The screen provides you with a cloud tenant accordion and a cloud tenant summary.

  • Use cloud tenant summary views to change how you are looking at the Summary.
  • Use the cloud tenant accordion to view the Properties of the tenant and its Relationships.
  • Use the cloud tenant summary to see details on Relationships (Cloud Provider, Security Groups, Instances, and Images), Quotas (including all OpenStack Compute, Network, and Volume quotas) and Smart Management (Company Tags).