About System Tags
A tag is a tenant-owned resourced that is automatically shared with all users within the tenant. It can also be shared with read access to all users in all sub-tenants within this tenant.
The System Tags list page (Admin > Reports > System Tags) sorts the list by listing the most recently created first (by default), but they can also be sorted by name.
The Systems Tags page lists tags even when a tag is shared from a parent tenant as shown in the following screenshot.
Tags created by a parent tenant and shared with a sub tenant retain their name. By default, all tags are sorted with most recently updated tags at the bottom of the list.
Managing System Tags
To manage system tags, click Admin > System Tags in the CCM UI to display the System Tags page.
The System Tags page lists lets you perform the tasks that the following table describes.
|Add a new system tag.|
Click the Add System Tag link.
|View or update an existing system tag.|
Click the Edit link in the Actions column for the system tag. The Edit System Tag page for the system tag displays.
|Delete a system tag.|
Click the Delete link in the Actions column for the system tag.
Adding a System Tag
When you add a system tag, you create a new tag based on configuration settings that you make. To add a system tag, follow these steps:
On the System Tags page, click the Add System Tag link.
The Add System Tag page displays.
In the Name field, enter a brief and unique descriptive name for the system tag.
The name can include letters, numbers, and underscores (_).
(Optional) In the Description field, enter a brief description of the system tag.
Click the Save button.
Share with Sub-tenants
A tag is a tenant-owned resourced that can be shared with users/groups within the tenant as well as user/groups in other sub-tenants in the hierarchy:
If one user/group in a tenant has manage access to a tag, then all users/groups in the tenant will also have manage access to this tags.
If you share a tag with any user/group in a sub-tenant, that user/group will have read-only access for tags in the tenant.
The System Tags have a Share with Sub-tenants toggle switch column:
On: Users in tenants that are further down the hierarchy can only View (read only) these tags.
Off: Default. No user in any sub-tenant can view or use a tag in this state. The tenant admin can grant permissions to sub-tenants by enabling the (ON) toggle switch for the required tag.
When a deployment environment or application profile is shared with a sub-tenant or users in a sub-tenant, all policies (and system tags) associated with that environment or app profile can still be used in the shared environment or application profile.
Isolation tags are different from system tags. Isolation tags are based on the string provided by a user when launching a job. See Security and Firewall Rules > Isolation Tags and the Submit Job API pages for additional context.
Applying Tags as Annotations
You can apply tags as annotations to associate custom information with resources in the CloudCenter platform. After you add a tag, you can then use that tag to filter VMs or containers. The following table identifies the annotation terminology used for each cloud.
You can apply tags in one of two ways from the UI:
From the application profile, on the Basic Information tab:
Specify the tags for in the application profile so you can use the tags as filters to search for this application. See Model a New Application Profile to specify the tag in an application profile.
Associate metadata relevant to your environment in the application profile. See Metadata for Custom Properties for additional context.
You can also override the name-value pair in the Metadata at the time of deployment. See Topology Modeler for explicit details on the Basic Information tab.
Predefined System tags as specified earlier in this page.
You can update the tag for each deployment in the Associate Tags field in the Deployment Details page.
To do this, the tag should already be added as specified in the Adding a System Tag section earlier in this page. See Deployment Details for additional context on updating a tag for a specific deployment.