Table 1-1 lists a few important terms and their definitions.
Table 1-1 Important Terms and Definitions
| Term | Description |
|---|---|
|
Virtualized Data Center (vDC) |
A collection of physical compute nodes and storage that sit on the Exalogic fabric. These physical resources are organized into a pool that can then be accessed by self-service users. It offers an access point through which to allocate and control the resources inside. |
|
Account |
A container for virtual resources in the Exalogic vDC. It includes the concept of quotas for the amount of CPU, memory, storage and networking resources that may be consumed within the context of that account (within the scope of a single vDC). Note: An account is created by the Cloud Admin user. |
|
Quota |
A limit for vCPU, memory, and storage resources defined while creating an account. |
|
Account Resource Limits |
The sum total of resources available to all users executing in the context of that Account. |
|
Exalogic Systems Admin |
The role for a user who is responsible for overall monitoring and management of the Exalogic machine, including its hardware components and network management. |
|
Cloud Admin |
The role for a user who configures the cloud. A Cloud Admin user creates Accounts and sets quotas. In addition, a Cloud Admin user monitors the resource consumption and Cloud User activities within the vDC. |
|
Cloud User |
The role for a user that consumes resources in the Exalogic vDC. Deploying vServers and applications is the primary responsibility of this user. A given cloud user may have access privileges to multiple Accounts within the Exalogic vDC. |
|
Access Keys |
Used for authentication of cloud user requests to a cloud account. |
|
Key Pairs |
Defines the cloud user credentials to access a vServer. |
|
Exalogic Guest Base Template |
Exalogic supports Oracle VM (OVM) server templates for the x86 processor architecture. All applications deployed on Exalogic must be deployed to vServers that are derived from a specialized server template that contains software and tools that are required for the proper functioning of vServers on Exalogic. This special server template is called the Exalogic Guest Base Template. |
|
Server Template |
An operating system image in a certain format that can be used to create a new vServer. Exalogic supports Oracle VM (OVM) Server templates for the x86 processor architecture. A server template is not just an operating system; it also contains application artifacts. In the Exalogic environment, the server template is a derivation of the Exalogic Guest Base Template. All vServers created in the Exalogic vDC are based on a server template. |
|
Virtual Server (vServer) |
An entity that provides the outward interface of a stand-alone operating system. This entity is a virtual machine with guest operating system, which consumes CPU and memory resources. A vServer can be a member of one or more vNets. |
|
Virtual Network (vNet) |
A networking construct that dictates which vServers may communicate with which other vServers. A vNet is created by a cloud user. The number of vNets that may be created depends on the quota allocated to an account. |
|
Volume |
A piece of storage. It consumes storage resources from an account. A volume that contains a bootable image of an operating system is called a Root Volume. Volumes have their own lifecycle and exist beyond the scope of the vServers that attach them. A volume is created by a cloud user. It can be created with an explicit command, but can also be created as a side effect of vServer creation. |
|
Snapshot |
A point-in-time image of a volume. A snapshot is created by a cloud user. |