An orchestration defines the attributes and interdependencies of a collection of compute, networking, and storage resources in Compute Classic. You can use orchestrations to automate the provisioning and lifecycle operations of an entire virtual compute topology.
To create instances using an orchestration, you define the orchestration offline in a JSON-formatted file, upload the orchestration to Compute Classic, and then start the orchestration. All the objects defined in the orchestration are created automatically.
At any time, you can delete and re-create all the instances in an orchestration just by stopping and restarting the orchestration. Storage attachments, security lists, and so on are re-created and associated automatically with the appropriate instances.
In orchestrations v2, you can achieve granular control over each object in an orchestration by defining the persistence of each object. If you want to delete instances in an orchestration but not the associated storage volumes, you can specify persistence for storage volumes and not for instances. That way, when you suspend an orchestration, all nonpersistent objects are deleted, while persistent objects continue to run.
To learn more about orchestration features, terminology, and concepts, see About Orchestrations v2.
To get started with creating instances using orchestrations, see Workflow for Creating Instances Using Orchestrations v2.
After your instance is created, you can log in to your instance. See Logging In to an Instance.
To ensure that Compute Classic instances provide a resilient platform for your workloads, make sure that the latest security patches are applied to the operating system running on the instances. In addition, before deploying applications on an instance, review the security configuration of the operating system and verify that it complies with your security policies and standards.
For security and patching-related guidelines, see the documentation for your operating system.