About Instances

An instance is a logical representation of a compute resource that has attributes that defines network, storage RAM, and vCPU requirements.

When an instance is launched, a virtual machine is created and configured based on the instance attributes. During the life of a single instance, many virtual machines are created and destroyed if the instance is shut down and restarted. Storage and network resources allocated when the instance is launched are released only when the instance is deleted. Storage and network resources are not released when the instance is shut down. This enables an instance to be shut down and restarted any number of times, similar to powering off and powering on a physical machine. Each time an instance is shut down the corresponding virtual machine is destroyed and the compute resources it was using (RAM, vCPU) are also released. When the instance is restarted, a new virtual machine is created and configured to use the existing storage and network resources, and new compute resources (RAM, vCPU) are allocated.

The identity of the instance is also preserved across shutdown or restart boundaries. Instances can only be created or launched through orchestrations. A single orchestration can contain one or more instances, and relationships can be defined among the instances to control their relative placement on the physical hardware. For example, instances that need to share resources or communicate frequently need to be placed on the same node. However, if an application must be highly available, then each instance must be placed on a different node. Once an instance is running, it can be shut down and restarted individually. If an instance is shut down outside the context of the owning orchestration, then the orchestration registers a warning state indicating that an instance it expects to be running was explicitly shut down by a user. If an instance terminates unexpectedly, then the orchestration registers an error state.

When defining an instance, you can specify the following attributes:

  • Number of CPUs and RAM in the form of shapes

  • EoIB network for external access

  • IPoIB network for internal communication

  • Service networks

  • Domain Naming System (DNS)

  • NIS

  • Storage volumes

  • SSH keys for passwordless access

  • Attributes