Orchestration v2 Life Cycle

When you activate an orchestration, all the objects defined in it are created and the orchestration moves to the active state. When you suspend an orchestration, the nonpersistent objects defined in it are deleted and the orchestration moves to the suspended state. When you deactivate an orchestration, all the objects defined in it are deleted and the orchestration moves to the inactive state.

Depicts the states of an orchestration
activating

The orchestration is starting.

Compute Classic is provisioning the objects defined in the orchestration. The time to complete this action varies depending on the number and type of objects that are being provisioned.

active

The orchestration is running.

Compute Classic successfully provisioned all the objects in the orchestration. For example, an orchestration displays that it is in the active state when all its instances have been created, storage volumes are online, and so on.

suspending

The orchestration is being suspended.

  • All the nonpersistent (persistent: false) objects are being deleted.

  • All persistent (persistent: true) objects are being created if they were not already created.

suspended
  • All the nonpersistent objects are deleted.

  • All persistent objects are created if they were not already created.

terminating

The orchestration is being terminated.

Compute Classic is deleting all the objects defined in the orchestration.

inactive

The orchestration is inactive.

Compute Classic successfully deleted all the objects defined in the orchestration.

terminal_error

The orchestration reached an error state from which it can’t recover. You must identify and address the issue.

The following are a few examples of the possible issues:

  • Errors in the template of your orchestration are preventing the orchestration from being created.

  • You don’t have the necessary permissions to provision a specified object.

transient_error

The orchestration is automatically recovering from a failure. You don’t need to intervene.

For example, if an instance crashes and Compute Classice is automatically re-creating the instance, a transient_error is displayed.