Oracle Compute Cloud Service Terminology

The following table lists the terminology used in Oracle Compute Cloud Service on OPCM.

Table 1-1 Terminology

Term Description

A container for system objects, such as users and virtual machine instances. A tenant can represent a whole organization or departments in an organization.

Tenant user

Users who are assigned this role consume the network, compute, and storage resources allocated to them by creating virtual machines that support their application requirements.


An orchestration is a JavaScript Object Notation (JSON) formatted file that groups one or more objects, such as instances and storage volumes, so that they can be managed as a unit. Within an orchestration, you can specify dependencies to control the sequence in which the objects are created and destroyed.

Launch plan

A launch plan is a JavaScript Object Notation (JSON) formatted orchestration section that defines the properties of one or more instances in Oracle Compute Cloud Service. The attributes in a launch plan include the instance label and name, the image and shape to be used for the instance, and so on.


An instance is a logical representation of a compute resource that has attributes defining network, storage, and compute resource (RAM, 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 can be created and destroyed if the instance is shut down and restarted.


A shape is a resource profile that specifies the number of CPUs and the amount of memory to be allocated to an instance in Oracle Compute Cloud Service.

Machine images

A machine image is a template of a virtual hard disk of a specific size with an installed operating system. You use machine images to create virtual machine instances in Oracle Compute Cloud Service.

Image List

An image list is a collection of Oracle Compute Cloud Service machine images. Each machine image in an image list is identified by a unique entry number.

Storage Volume

A storage volume is a virtual disk that provides persistent block storage space for instances in Oracle Compute Cloud Service.

Volume snapshot

A point-in-time image of an existing storage volume.

Instance snapshot

A point-in-time state of a virtual machine's boot disk. The output of a snapshot is a machine image, which can be used as a template to create a new instance.


InfiniBand is a networking communication standard used in high performance computing. Oracle's InfiniBand network solutions deliver the application isolation and elasticity required to consolidate and virtualize enterprise business applications and cloud computing infrastructures.
IP over InfiniBand (IPoIB) IP over InfiniBand (IPoIB) enables applications running in separate virtual machines to communicate with each other over a private channel by using native InfiniBand protocols and without the overhead of Ethernet.
Ethernet over InfiniBand (EoIB) Ethernet over InfiniBand (EoIB) enables applications on an InfiniBand fabric to communicate with the Ethernet networks external to OPCM.
Tenant networks Networks that are assigned exclusively for use by instances in a tenant.
Tenant EoIB networks Networks assigned for use by instances to communicate with external Ethernet networks.
Tenant IPoIB networks Networks assigned for use to communicate across the instances in a tenant.
vEthernet A layer 2 network that helps you isolate Oracle Compute Cloud Service instances created on OPCM. For example, you can create networks to isolate instances used by different departments in your company.

Tenant network vNet

A vNet represents an IP subnet on a given vEthernet. The subnet includes the CIDR and IP address range that are available for users to use for their instances.

vNet reservation

A vNet reservation is a public or private IP address that you can attach to an Oracle Compute Cloud Service instance.


A collection of user defined key and value pairs that is made available to an instance through the metadata service. The attributes under user_data are made available through the metadata service.

Instance metadata, including user-defined data is available at within an instance.


A relationship is defined as part of an orchestration. There are two types of relationships, one between oplans and another between instances. An oplan relationship defines the dependencies between oplans in an orchestration. An instance relationship defines the affinity or anti-affinity rules for the placement of the instances.

Oplan relationships are specified at the same level as oplans in an orchestration, and instance relationships are specified inside a launch plan.