Service blueprint tag selections in policies

You can tag a service blueprint at many levels:

• Service blueprint definition (top level)
• Components
• Connections
• Service deployment definitions
• Resource sets
• Compute resources
• Network NICs
• Network VLB pools
• Network paths

Because you can have multiple instances of these levels to specify different options in each service blueprint, you can tag each option level separately to ensure that the proper resources are used during service provisioning. When a service blueprint is tagged differently at different levels, the tag at the more specific level of the service blueprint is used during policy evaluation. 

In network container policies, the policy first tries to match the tags in any of the service deployment definitions of a blueprint. If no match occurs, it then tries to match the tag in the service blueprint definition.

In compute pool policies and virtual disk repository policies, the policy tries to match tags in service blueprints in the following order: compute resources > resource sets > service deployment definitions > components > service blueprint definition.

Example

A service blueprint contains the following tag assignments:

• A service deployment definition is tagged as Silver from the SLA tag group.
• A resource set is tagged as Gold from the SLA tag group.

Suppose that you write a compute pool policy to select resources that are tagged with the SLA tag group when the tag value is matched to service blueprints as the tag source.

When the policy is evaluated, the policy chooses compute pools tagged as Gold from the SLA tag group because the resource set is more specific than service deployment definition.

Related topic

Creating and managing policies