Policy management overview

 Cloud administrators can specify tags for the following BMC Cloud Lifecycle Management objects:

• Network containers
• Networks
• Compute resource pools
• Platform-as-a-service (PaaS) resource pools
• Virtual disk repository pools
• Tenants
• Service blueprints

Cloud administrators associate tags with tag groups, which organize tags used in the cloud. For example, the cloud administrator might create a tag group named Location to group all of the tags that specify network locations. The cloud administrator might also create a tag group named SLA for the tags representing different service levels offered to tenants.

Any taggable object can be associated with the same tag group and tag. For example, a cloud administrator might apply the SLA tag group and the Bronze tag to a network container, and the Bronze tag to a compute resource pool, ensuring the placement of Bronze requests to the Bronze-tagged network container and compute resource pool.

Taggable objects can use more than one tag from the same or different tag groups. For example, the cloud administrator can tag a compute resource pool with Bronze and vSphere tags to ensure that only Bronze requests for vSphere hypervisors are provisioned to that compute resource pool. The cloud administrator might also specify that a request from the NYC location be deployed with resources in either a Bronze or Silver compute resource pool.

Consider creating all of the tag groups and tags you expect to need before applying tags to cloud resources. This ensures that you apply tags consistently, and helps you manage your policies more efficiently.

Policies match tags between

• Service blueprints and available resources

• Tenants and available resources

Policies applied to service blueprints

When you apply policies to a service blueprint and then provision a service instance based on that blueprint, tag matching dictates which resources are used for the service instance.

For a service blueprint, you can create the following types of policies:

You can tag a service blueprint at many levels, including the service level (the top), the definition level, and at the level of compute and PaaS resources.

Policies applied to tenants

You can create policies that map tenants to resources. This lets you control which resources are used when provisioning a service instance requested by a specific tenant user. Policies based on tenant tags are useful only when two or more tenants share a network container but require different resource pools.