You can set expiry dates for existing services manually, as shown in this topic.

You can set expiry information for new services in one of the following ways:

through the Default Attributes policy, which you can use to assign new services to an expiry group

through a completion workflow with a Set Expiry Date step

when manually deploying a requested service, or when manually cloning a VM

bestpract-checkmark2

Ensure that all services have an expiry date or are set to never expire. To identify those services that do not have an expiry date, create a search using the filters "Expiry Date" and "No Expiry Date Set." For more information about searching, see Searching with the Complete Filter Set.

After you set the expiry date, you can:

instantly identify when a service is due to expire by viewing the Operational pane on the Summary tab of the Operational or VMs and Templates views

search based on expiry state (see Searching with the Complete Filter Set)

run a report based on expiry state

You can control expired services with the Expiry policy (for example, automatically suspend expired services).

You can configure the Compliance policy to carry out actions on services that have no expiry date set (for example, generate an alert for all services without expiry information).

You also have the option of:

clearing the expiry date of a service at any time. Clearing the expiry date means that actions configured in the Expiry policy will not be carried out.

setting a service to never expire. If you set a service to never expire, the Expiry policy actions do not affect it. You can use this feature to label services that have been assessed as valid in your environment.

caution

If you attempt to deploy a VM from a template in the Expired state, the deployment will fail.

Expiry states

Services and templates can have the following expiry states:

Never expires

No expiry date set

Not expired

Expired

Soon to expire

Post expiry

NotePencil-smallThe Expiry policy has three dates whereupon you can trigger actions ('x' number of days before the expiry date, the expiry date, and 'x' number of days after the expiry date). A service has the Expired state between the expiry date and the last trigger date you configure. A service has the Post Expiry state if it continues to exist after the last trigger date. For example, if you keep the default setting of 30 days after the expiry date, a service that continues to exist after 30 days has the Post Expiry state.

Setting an expiry date for a service

Access through:

Views menu > Operational, VMs and Templates, or Datastore

Available to:

Administrator and All Operator Levels of Access Rights

To set an expiry date for a service:

1.Navigate to a service in the tree or in a table.

2.Do one of the following:

For a VM, right-click and choose Lifecycle Management > Set Expiry Date.

For all other service types, right-click and choose Set Expiry Date.

3.In the Set Expiry Date dialog, click the calendar icon and select a date.

4.Click OK.

NotePencil-smallAn expiry date set for a virtual service, stack or auto scaling group automatically applies to all of its children, overriding existing values. But you can always apply a different expiry date to a child VM if required.

Viewing the number of expiry extensions remaining for a service

Access through:

Views menu > Operational, VMs and Templates, or Datastore

Available to:

All Levels of Access Rights

When the expiry policy is configured to allow primary owners to extend the expiry date of a service, a maximum number of allowed extensions can be configured. Both vCommander and Service Portal users can view the number of expiry extensions remaining on a service.

To enable the display of the number of expiry extensions remaining for a service:

1.Navigate to a service, then select a service in the tree, or double-click the service in a table.

2.On the Details pane, click Pick Properties.

3.In the Property Selection dialog, add the property Expiry Extensions Remaining to the Shown Properties, and click OK.

4.If an expiry extension limit was set, the number of extensions remaining is displayed, as shown below. If no extensions remain, the value is 0. If expiry extensions are not allowed, or no maximum was set, the value is blank.

exp-ext-rem

Resetting the number of expiry extensions remaining for a service

Access through:

Views menu > Operational, VMs and Templates, or Datastore

Available to:

Administrator and Operator with Approval Access Rights

When the expiry policy is configured to allow primary owners to extend the expiry date of a service, a maximum number of allowed extensions can be configured. You can reset the count of expiry extensions used for a service, so that the primary owner can continue to extend the expiry date for this service.

To reset the number of expiry extensions remaining for a service:

1.Navigate to a service in the tree or in a table.

For a VM, right-click, and choose Lifecycle Management > Set Expiry Date.

For all other service types, right-click, and choose Set Expiry Date.

2.In the Set Expiry Date dialog, enable Reset Expiry Extension Count.

3.Click OK.