This section introduces the following tasks:
An Account entitles designated Cloud Users the authorization to use computing, network, and storage resources of the Exalogic vDC. The Account provides the required capabilities to manage these resources.
The following are the prerequisites for creating an account:
Estimate the resource quotas to be allocated for the account
Identify the Cloud Users to be assigned to the account
The quota for vCPU, memory, and storage resources are defined during Account creation. The Resource Quota Information display in the account wizard creation indicates how much of the corresponding vDC resources can be used. It also displays whether the vDC resources are oversubscribed or undersubscribed.
You can configure an account to be able create a maximum of 4096 private vNets in an account. You can set the limit of number of private vNets that can be created in an account. The allowable number of defined networks is a function of the server pool configuration defined in the Exalogic vDC. Within each server pool, you can create a maximum of 64 private networks. However, note that some networks are already defined for use by Exalogic Control.
During Account creation, the public networks that are available in the vDC are listed. You can set the number of public IP addresses allocated to the account from this resource. This public IP address can be used by the Cloud User to assign to the vServer, as required. You can choose what defined public networks are available to each Account.
You provide an entitlement to the virtual resources for an account. You allocate the resources from the vDC to an account. The resource allocation for all of the accounts in a vDC can be more than the actual resources in a vDC. This oversubscription of the resources must be identified and planned for a vDC. You must configure the virtual resources for an account properly and update the resource configuration when the requirement increases. If an account does not have enough resources, then the Cloud User will get notifications that they cannot create vServers if the resources are not available.As a Cloud Admin user, you must watch the resource usage and configure resources for an account. You can create as many or few Accounts as your business requires. By doing so, you can partition the Exalogic vDC by Account, based on resource allocation.
As a Cloud Admin user, you can update the resource configuration for an account, assign Cloud Users to an account, and delete an account.
You can assign Cloud Users to an account during account creation or separately. Cloud Users have access to only the specific Accounts to which they are added. As a Cloud Admin user, you can manage the access of the Cloud Users to all Accounts in the Exalogic vDC.
A vServer Type is a profile that defines the memory and virtual CPUs to be allocated to vServers creating by using that profile. A Cloud User is restricted to using these definitions to create vServers.
The following default system-defined vServer types are available in the Exalogic vDC:
EXTRA_LARGE: 16 GB memory and 4 vCPUs
LARGE: 8 GB memory and 2 vCPUs
SMALL: 4 GB memory and 1 vCPU
As a Cloud Admin user, you can create additional vServer types and delete them. However, you cannot delete the system-defined vServer types. For information about creating vServer types, see Creating vServer Types.
When you create a vServer type, the following information is displayed in the wizard, based on the resources defined:
The number of Oracle VM Servers in the Exalogic vDC that have sufficient physical resources to host a vServer with the selected resources
An estimation of the number of vServers that can be hosted using the available physical resources in the vDC