Managing the Exalogic vDC Infrastructure

1. Log in to the Exalogic Control console as the CloudAdmin user.
2. In the navigation pane on the left, click vDC Management. Under vDCs, click the name of the default Exalogic vDC (MyCloud).
3. Expand Accounts under MyCloud. The accounts in the vDC are listed.
4. To update an account (for example, Dept1), select Dept1 listed under Accounts in the navigation pane on the left.
5. Click Update Account on the Actions pane. The Update Account wizard is displayed, as shown in Figure 10-1.

   Figure 10-1 Specify Account Details

   
   Description of "Figure 10-1 Specify Account Details"
6. Click Next.

   The Specify Account Resource Limits screen is displayed, as shown in Figure 10-2.

   Figure 10-2 Specify Account Resource Limits

   
   Description of "Figure 10-2 Specify Account Resource Limits"

   In this screen, you can update resource limits in Dept1. For example, change the Memory limit from 100 GB to 400 GB.

7. After updating the values, click Next.

   The Summary screen is displayed.

8. Review the summary, and click Finish.

1. Log in to the Exalogic Control console as the CloudAdmin user.
2. In the navigation pane on the left, click vDC Management. Under vDCs, click the name of the default Exalogic vDC (MyCloud).
3. Expand Accounts under MyCloud. The accounts in the Exalogic vDC are listed.
4. To delete an account (for example, Dept1), select Dept1 listed under Accounts in the navigation pane on the left.

   Note:

   Deleting an account removes all resources in the account, such as Server Templates, volumes, vServers, and private vNets. When you try to delete an account that has running vServers, the following message is displayed:

   You cannot delete this account because there are virtual servers in running state. Shut down all the virtual servers to delete the account.

5. Click Delete Account on the Actions pane. The Delete Account screen is displayed, as shown in Figure 10-3.

   Figure 10-3 Delete Account

   
   Description of "Figure 10-3 Delete Account"
6. To delete the Dept1 account, click Delete.

1. Log in to the Exalogic Control console as the CloudAdmin user.
2. In the navigation pane on the left, click vDC Management. Under vDCs, click the name of the default Exalogic vDC (MyCloud).
3. Expand Accounts under MyCloud. The accounts in the Exalogic vDC are listed.
4. To remove a Cloud User from an account (for example, myclouduser1 assigned to Dept1), select Dept1 listed under Accounts in the navigation pane on the left. The Dept1 account dashboard is displayed.
5. In the Dept1 dashboard, click the Users tab. A list of the Cloud Users assigned to the Dept1 Account is displayed as shown in Figure 10-4.

   Figure 10-4 List of Cloud Users Assigned to an Account

   
   Description of "Figure 10-4 List of Cloud Users Assigned to an Account"
6. Select a Cloud User (for example, myclouduser1), and click the X icon (Launch Delete User Wizard). The Remove User from Account screen is displayed.
7. Click Remove to remove the user (myclouduser1).

This section contains the following topics:

• Overview of CPU Oversubscription

• Configuring the CPU subscription Ratio and CPU Consumption Limit

• Example Scenarios for CPU Oversubscription

In an Exalogic vDC, the underlying CPU hardware resources of the machine are allocated to the vServers in the form of vCPUs. By default, each vCPU consumes one CPU hardware thread.

For example, each Sun Fire X4170 M2 compute node on an Exalogic X2-2 machine consists of two 6-core sockets—that is, 12 cores per compute node. Each core supports two hardware threads. So a single X2-2 compute node can support 24 vCPUs—one vCPU per hardware thread—in the default configuration.

To improve hardware utilization and to facilitate denser consolidation of applications, starting with the Exalogic Elastic Cloud Software release 2.0.4.0.0, the Exalogic vDC can be configured to support more vCPUs than the available CPU threads—that is, the CPU resources can be oversubscribed.

• Cloud Admin users can enable CPU oversubscription by increasing the vCPU-to-physical-CPU-threads ratio. For example, in a vDC that is based on a standard Exalogic X2-2 machine, when the vCPU-to-physical-CPU-threads ratio is increased from the default 1:1 to 2:1, the number of vCPUs available on each Sun Fire X4170 M2 compute node on an Exalogic X2-2 machine increases from 24 to 48. Table 10-1 shows the number of vCPUs available in the vDC at various vCPU-to-physical-CPU-threads ratios.

  Table 10-1 Number of vCPUs at Different vCPU-to-Physical-CPU-threads Ratios

  vCPU-to-Physical-CPU-threads Ratio	X2-2 Full	X2-2 1/2	X2-2 1/4	X2-2 1/8
  1:1 – CPU oversubscription not enabled	720	384	192	96
  2:1	1440	768	384	192
  3:1	2160	1152	576	288

1. Log in to Exalogic control as the Cloud Admin.
2. From the navigation pane on the left, select vDC Management.
3. Expand vDCs and select the vDC you want to modify.
4. From the actions pane on the right, select Edit Virtual Datacenter.

   The Edit Virtual Datacenter wizard is displayed.

5. You can use the initial screens of the Edit Virtual Datacenter wizard to change the name, description, and tags of the vDC. If you do not want to change any of these settings, click Next till the Specify vCPU Sizing screen is displayed.
6. In the vCPU to Physical CPU Threads Ratio field, enter the maximum number of virtual CPUs that can share each physical CPU thread. Decimal values can be entered.

   For example, if the vCPU to Physical CPU Threads Ratio field is set to 2, each virtual CPU will receive at least 50% of the cycles of a physical CPU thread.

   Note:

   As the CPU oversubscription ratio increases, performance may be affected, but the utilization of CPU resources improves. The CPU oversubscription ratio that you might want to use is at most 3:1. At extremely high ratios, the risk of instability of the system increases.

   For racks hosting production vServers, CPU oversubscription must be 1:1 to avoid performance issues.

7. Do not modify the CPU Cap from its default value of 100%.

   Note:

   CPU Cap feature is deprecated.

8. Click Next.

   The Edit Volume Storage screen is displayed. If required, select more storage resources to allocate to the vDC from the list; otherwise proceed to the next step.

9. Click Next.

   The Summary screen is displayed.

10. Review the updated settings of the vDC and click Finish.

This section describes the following example scenarios:

• Scenario 1: Increasing the Number of vCPUs in a New VDC

• Scenario 2: Increasing the Number of vCPUs in a Running, Fully Subscribed VDC

• Scenario 3: Increasing the Number of vCPUs in a Running, Oversubscribed VDC

• Scenario 4: Decreasing the Number of vCPUs in a Running, Oversubscribed VDC

In certain situations, you may want to make an OVS node unavailable for vServer placement. For example, when you want to perform maintenance on a compute node.

To make an OVS node unavailable for vServer placement, you must perform the following tasks:

Task 1: Identify and Tag the OVS Node with vserver_placement.ignore_node=true

Task 2: Migrate the vServers on the Tagged OVS Node to Other Available OVS Nodes

Task 3 (optional): Place the OVS Node in Maintenance Mode