Policy management overview
The Service Governor defines policies that determine how cloud end user requests get mapped to underlying resources. Policies specify the automatic selection of compute, network, and storage pools during provisioning. Policies also let cloud administrators specify selection of resources based on customer-based attributes, such as tenants, service quality, and performance.
This topic contains the following sections:
Tags and tag groups
Tags are the basic tool used to manage the automated provisioning of resources and the placement of services.
Cloud administrators can specify tags for the following BMC Cloud Lifecycle Management objects:
- Network containers
- Compute resource pools
- Platform-as-a-service (PaaS) resource pools
- Virtual disk repository pools
- 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.
The following video (8:05) provides an overview of tags in BMC Cloud Lifecycle Management:
For more advice on tagging, see Tagging recommendations and examples.
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:
Controls which resource pools are used when provisioning a service instance.
Controls the placement of network interfaces when provisioning a service instance. Network policies are required when using tags to match network interfaces in the service blueprint to networks in the network container.
Controls which network container a service instance is provisioned within. This is useful when a tenant has more than one network container available.
Controls which PaaS resource pools are used when provisioning a service instance.
Virtual disk repository
Controls what storage is available on a virtual disk repository pool when provisioning a service instance.
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.
Related BMC Communities blog entries
The following links provide supplemental information available from blog entries in BMC Cloud Lifecycle Management Communities: