Managing Service Expiry

Ensuring that all services have an expiry date or are set never to expire means that you have greater control over your cloud infrastructure. For example, you can avoid paying for unneeded services while ensuring that critical services are never decommissioned.

Once you set the expiry date, you can:

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 can control expired services with the Expiry policy (for example, you can automatically decommission expired services).

In this topic:

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

Setting expiry information for existing services

Access through:

Views menu > Operational, Deployed, or Storage

Available to:

Administrator and All Operator Levels of Access Rights

To set an expiry date for an existing 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, select a date, and click OK.

    An expiry date set for a virtual service, application 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.

Setting expiry information for new services

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

If multiple methods are configured, they're applied in the order specified above, with the first item in the list taking precedence. See also Order of Precedence for Metadata and Service Settings.

Viewing the number of remaining expiry extensions

Access through:

Views menu > Operational, Deployed, or Storage

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.

Resetting the number of expiry extensions remaining for a service

Access through:

Views menu > Operational, Deployed, or Storage

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 select Lifecycle Management > Set Expiry Date.
    • For all other service types, right-click, and select Set Expiry Date.
  2. In the Set Expiry Date dialog, enable Reset Expiry Extension Count.
  3. Click OK.