Suspending an Orchestration v2

When you suspend an orchestration, all nonpersistent resources that were provisioned by that orchestration are deleted. Persistent objects aren’t deleted.

Prerequisites

  • The orchestration that you want to suspend must be in the Ready state or Error state. You can’t suspend orchestration in a transient state such as Starting or Stopping.

  • To complete this task, you must have the Compute_Operations role. If this role isn’t assigned to you or you’re not sure, then ask your system administrator to ensure that the role is assigned to you in Oracle Cloud Infrastructure Classic Console. See Modifying User Roles in Managing and Monitoring Oracle Cloud.

Procedure

  1. Sign in to the Compute Classic console. If your domain spans multiple sites, select the appropriate site. To change the site, click the Site menu near the top of the page.
  2. Click the Orchestrations tab.
  3. Identify the orchestration that you want to suspend. From the menu icon menu, select Suspend.
    The status of the orchestration changes to Suspending.

After all nonpersistent objects have been deleted, the status of the orchestration changes to Suspended. You can view the orchestration, stop it, delete it, or start it again.

To suspend an orchestration using the CLI, use the opc compute orchestration-v2 update name [--desired-state suspend] command. For help with that command, run the command with the -h option. For the instructions to install the CLI client, see Preparing to Use the Compute Classic CLI in CLI Reference for Oracle Cloud Infrastructure Compute Classic.

To delete only the nonpersistent objects in orchestrations v2 using the API, use the PUT /platform/v1/orchestration/orchestrationName method with the query argument desired_state=suspend. For more information, see REST API for Oracle Cloud Infrastructure Compute Classic.