Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Decommissioning cloud services in the legacy console

When you create cloud services, you specify a date in the future when the service will be decommissioned. However, you can decommission a service before the planned decommission date.

If you decommission a database, the database is deleted in BMC Database Automation.

To decommission a service

  1. From the list of services in the My Services tab of the My Cloud Services console, highlight the service that you want to decommission.
  2. Choose one of these methods to perform the action:
    • Click the Decommission button  decommission_button.jpg.
    • Click the Operator Action icon operator_action_button.jpgand choose Decommission.
    • Right-click the service and choose Decommission from the pop-up menu.

A prompt bar at the top of the Service Instances pane displays an informational message that shows the action is in progress.  For detailed information regarding the status of the decommissioning action, highlight the service in the list on the Services link bar of the Activities tab and click the Advanced Error Information icon advanced_error_info_icon.jpg.

When a service is decommissioned, BMC Cloud Lifecycle Management takes the following actions, in order:

  1. Sets the contractline status to Terminated/Expired.
  2. Stops the service offering instance.
  3. Decommissions sensors.
  4. Deletes the policy domain.
  5. Deletes server groups, which includes the following actions for each server group:
    1. Deletes logical communication paths.
    2. Deletes compute containers, which includes the following actions for each compute container:
      1. Releases NICs and IP addresses.
      2. Deletes DNS entries.
      3. Releases any attached storage.
    3. Deletes load balancer pool entries and load balancer pools.
  6. Updates user quotas.

Note

If decommissioning fails due to an issue in BMC Server Automation, BMC Database Automation, vCloud, or the Docker daemon host, the service offering instance entries are deleted from BMC Cloud Lifecycle Management and the cloud database. However, the VMs, vApps, or conatiners are not removed from BMC Server Automation, BMC Database Automation, vCloud, or Docker host.

Related topic

Managing-cloud-resources, especially Managing your services.

What-s-changed-in-the-new-My-Cloud-Services-Console.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*