Use the Default Ownership policy to automatically assign ownership to new services, ensuring that you can track who is incurring service costs. 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 ownership and ensures that services are always assigned to an owner who can manage them, and are always visible to organization members.
|You can also set ownership information with a workflow step. To ensure that the proper values are set, it's best practice to set metadata through policy or through a completion workflow, not both. The metadata values that are applied last are those that take effect.|
The Default Ownership policy changes ownership of templates, but policy actions are not performed for templates.
Configuration menu > Policies
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 Ownership from the list of policies.
3.On the Policy Name/Description page, enter a name, for example, Default Ownership Policy for Windows in Production (maximum 100 characters), and an optional description.
|If a VM 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.|
5.To select the target for the policy, expand the Operational or VMs and Templates tree if required, and select the infrastructure elements you want.
|Any 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 but rather select a managed system or any infrastructure elements within a managed system.|
7.From the Take Action drop-down menu, select from the options:
•Notify Only: If the policy is triggered, no action is taken for the service. 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.
|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.
8.Select an organization to make new services visible to users in an organization.
|If you assign ownership to one or more organization members in the next step, their organization is automatically selected. For a service to be visible to an organization member, the service must be assigned to the organization.|
9.Assign users to new services by entering a login ID or email address and clicking Add. The account you add must be a local user or group account set up within vCommander or a directory services user or group account.
You can add more than one account and you can assign a primary owner and an IT contact. The first owner added to the policy is automatically assigned as a primary owner; you can change that assignment and the IT contact assignment as required.
10.Decide whether to allow children of the targets to have their own instance of the policy and disable this setting if desired.
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).
See Walk-through: Configuring Organizations for an example of how this override can be useful.