Assigning Groups to Services with the Default Attributes Policy

Use the Default Attributes policy to automatically assign the following metadata for new services:

expiry date

expiry group

guest OS scan group

maintenance group

power schedule group

rightsizing group

NotePencil-smallExpiry groups and maintenance groups apply to VMs, virtual services, stacks, auto scaling groups, databases and load balancers. Other group types apply only to VMs.

This policy works in two ways:

During a Embotics® vCommander® deployment (automated or manual), if vCommander finds a policy targeting the selected destination, it calculates the policy actions and combines them with the other metadata (inherited from the source template and supplied on the request form). During automated deployment, vCommander applies the combined values. During manual deployment, vCommander populates the wizard with the combined values.

The policy is triggered when a new service is created directly in the managed system — that is, outside of vCommander.

Creating this policy can help you reduce the administrative time required to set service metadata and ensures that services are always assigned to an owner who can manage them, and are always visible to organization members.

NotePencil-smallAny configuration of this policy on a system-wide basis can affect all managed systems that are managed by vCommander now and can affect all managed systems that are added to vCommander in the future. If you do not want all managed systems to be automatically affected by this policy, configure the policy by selected infrastructure elements only.

How does the Default Attributes policy affect templates?

The Default Attributes policy assigns groups to templates, but policy actions are not performed for templates.

Before you start: Create groups

Before configuring the Default Attributes policy, make sure you've created the groups you will assign through the policy. See the following for more information on creating groups:

Managing the Service Lifecycle with the Expiry Policy

Scanning a Guest Operating System

Configuring Maintenance Windows

Configuring VM Power Schedules

Configuring Rules for VM Rightsizing

Configuring the Default Attributes policy

Access through:

Configuration menu > Policies

Available to:

vCommander Role of Superuser and Enterprise Admin

Administrator Access Rights

1.On the Policies tab, click Add.

2.On the Choose a Policy page, select Default Attributes from the list of policies, then click Next.

3.On the Policy Name/Description page, enter a name (for example, Default Attributes Policy for Production), and an optional description, then click Next.

4.On the Choose a Target page, from the Target View Type list, select Operational or VMs and Templates and in the Operational or VMs and Templates tree select a target for the policies.

NotePencil-smallIf a service is deployed into a location where multiple policies target the Operational view and the VMs and Templates view, the policy targeting the Operational view takes precedence.
NotePencil-smallAny configuration of this policy on a system-wide basis can affect all managed systems that are managed by vCommander now and can affect all managed systems that are added to vCommander in the future. If you do not want all managed systems to be automatically affected by this policy, do not select Operational or VMs and Templates as a target. Instead, select a managed system or any infrastructure elements within a managed system.

5.On the Configure the Policy page, do the following, then click Next:

If you want the policy to come into effect immediately after you finish configuring it, select Enable Policy.

In the Take Action area, choose an option:

Notify Only: If the policy is triggered, no action is taken. An alert is created, notifying you that the policy has triggered. See also Subscribing to Policy Alerts.

Run [Workflow]: Existing command workflows appear for selection, organized by target type. If the policy is triggered, the selected workflow is run.

NotePencil-small        You must choose a workflow with a target type that matches the target of the policy; otherwise, the workflow will fail. For example, if the selected workflow's target type is "VM", the workflow will fail if the policy targets a database. A workflow with a target type of All Types can be run on all service types.

Click Add Workflow to set up a new command workflow.

In the Expiry area, choose one of the following:

If you want the service to expire in a given number of days after the service is added to the inventory, enable Set Expiry Date and enter the number of days from 1 to 9999.

If you want the service to never expire, enable Never Expires.

Enable or clear the last check box to set whether you want to allow children of the targets to have their own instance of the policy.

If you enable this option, other instances of this policy can be applied to any infrastructure elements and services that are children of the parent infrastructure element you have selected (an override).

6.On the Configure Groups page, click Add Groups, then in the Add Groups dialog, select the groups you want to add, and click OK.

You can choose one or more of the following group types.  

Expiry

Guest OS Scan

Maintenance

Power Schedule

Rightsizing

7.Back on the Configure Groups page, select specific groups for each type, then click Next.

8.On the Summary page, review the summary of your policy configuration, then click Finish to complete the configuration.