10 Exalogic vDC Management: Advanced Tasks

This chapter discusses how to perform advanced tasks related to Exalogic Virtual Data Center (vDC) management using the browser user interface (BUI) of Exalogic Control. You can perform these tasks after completing the management tasks described in Chapter 9, "Exalogic vDC Management: Basic Tasks."

This chapter contains the following sections:

10.1 Managing the Exalogic vDC Infrastructure

This section describes how to complete the following tasks:

Before You Begin

Before you can perform these tasks, you must have completed the Cloud Admin tasks, as described in Section 9.1, "Administering the Exalogic vDC and Setting Up the Infrastructure".

10.1.1 Logging In as Cloud Admin User

Log in to the Exalogic Control console as the CloudAdmin user.

For more information about creating this user role, see Section 6.4, "Creating the Cloud Admin User".

10.1.2 Updating an Account

To update an account, complete the following steps:

  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 follows
    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 follows
    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.

10.1.3 Deleting an Account

To delete an account, complete the following steps:

  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 follows
    Description of "Figure 10-3 Delete Account"

  6. To delete the Dept1 account, click Delete.

10.1.4 Removing a Cloud User from an Account

An Account needs at least one Cloud User. You cannot remove a Cloud User from an account, which has a single Cloud User associated.

To remove a Cloud User from an account with multiple Cloud Users, complete the following steps:

  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 follows
    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).

10.1.5 Configuring CPU Oversubscription

This section contains the following topics:

10.1.5.1 Overview of 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


  • Cloud Admin users can also specify a limit for the number of physical CPU thread's cycles that each vCPU can consume. This ensures deterministic performance for vServers on across the vDC. For example, if the CPU Cap is set at 50%, each vCPU can consume only up to 50% of a hardware thread at any point in time.

10.1.5.2 Configuring the CPU Subscription Ratio and CPU Consumption Limit

To enable CPU oversubscription, run the following steps:

  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.

  7. In the CPU Cap field, enter the maximum percentage of a physical CPU thread's cycles that can be allocated to any one virtual CPU.

    For example, if the CPU Cap is set to 50, a vCPU can use up to 50% of the cycles of a physical CPU thread.

    Note:

    Changes to the CPU Cap apply to only vServers created after such a change and not to existing vServers.

  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.

10.1.5.3 Example Scenarios for CPU Oversubscription

This section describes the following example scenarios:

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

  • An Exalogic X2-2 full rack is set up as a virtual datacenter.

  • At the default vCPU-to-physical-CPU-threads ratio of 1:1, 720 vCPUs (24 x 30) are available in the vDC.

  • The Cloud Admin determines that more than 720 vCPUs are required to support the workloads planned for the vDC.

In this scenario, the Cloud Admin can increase the number of vCPUs available in the vDC, by enabling CPU oversubscription. For example, the Cloud Admin can increase the number of vCPUs available in the vDC to 1440 (2 x 24 x 30), by increasing the vCPU-to-physical-CPU ratio to 2:1, as described in Section 10.1.5, "Configuring CPU Oversubscription."

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

  • An Exalogic X2-2 full rack is set up as a virtual datacenter.

  • At the default vCPU-to-physical-CPU-threads ratio of 1:1, 720 vCPUs (24 x 30) are available in the vDC.

  • The vCPU quotas of the accounts in the vDC are fully allocated to the vServers created by the cloud users assigned to the accounts.

  • The memory and storage quotas of the accounts in the vDCs are not yet fully allocated to vServers.

  • Cloud Users want to create more vServers, but cannot do so because the vCPU quota is fully allocated.

In this scenario, the Cloud Admin can allow Cloud Users to create more vServers, by enabling CPU oversubscription. For example, the Cloud Admin can increase the number of vCPUs available in the vDC to 1440 (2 x 24 x 30), by increasing the vCPU-to-physical-CPU ratio to 2:1, as described in Section 10.1.5, "Configuring CPU Oversubscription." Then, the Cloud Admin can increase the vCPU quota of the accounts in the vDC to enable creation of additional vServers.

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

  • An Exalogic X2-2 full rack is set up as a virtual datacenter.

  • CPU oversubscription has been enabled and the oversubscription ratio is currently at 2:1—that is, 1440 vCPUs (2 x 24 x 30) are available in the vDC.

  • The vCPU quotas of the accounts in the vDC are fully allocated to the vServers created by the cloud users assigned to the accounts.

  • The memory and storage quotas of the accounts in the vDCs are not yet fully allocated to vServers.

  • Cloud Users want to create more vServers, but cannot do so because the vCPU quota is fully allocated.

In this scenario, the Cloud Admin can allow Cloud Users to create more vServers, by increasing the CPU oversubscription ratio further. For example, the Cloud Admin can increase the number of vCPUs available in the vDC to 2160 (3 x 24 x 30), by increasing the vCPU-to-physical-CPU ratio to 3:1, as described in Section 10.1.5, "Configuring CPU Oversubscription." Then, the Cloud Admin can increase the vCPU quota of the accounts in the vDC to enable creation of additional vServers.

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

  • An Exalogic X2-2 full rack is set up as a virtual datacenter.

  • CPU oversubscription has been enabled and the ratio is currently at 3:1—that is, 2160 vCPUs (3 x 24 x 30) are available in the vDC.

  • Only 1000 of the available 2160 vCPUs are being used by vServers.

  • The Cloud Admin decides that an oversubscription ratio of 2:1 would suffice for this vDC.

In this scenario, the Cloud Admin can decrease the number of vCPUs available in the vDC to 1440 (2 x 24 x 30), by decreasing the vCPU-to-physical-CPU ratio to 2:1.

Note:

In any of the CPU oversubscription scenarios described earlier, to ensure that application performance across the vDC remains predictable, the Cloud Admin can decrease the CPU Cap—that is, the percentage of CPU cycles that each vCPU can consume (default: 100%). Note that the new CPU Cap is applicable to only the vServers created after the CPU Cap was changed, and not to existing vServers.

10.1.6 Making an OVS Node Unavailable for vServer Placement

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

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

  1. Identify the OVS node that you want to make unavailable for vServer placement.

  2. Tag the OVS node with vserver_placement.ignore_node=true by doing the following:

    1. Log in to Exalogic Control as the ELAdmin user.

    2. From the navigation pane on the left, click Assets.

    3. Under Assets, from the drop-down list, select Server Pools, as shown in the following screenshot:

      Figure 10-5 Exalogic Views List

      Description of Figure 10-5 follows
      Description of "Figure 10-5 Exalogic Views List"

      A list of the OVS nodes is displayed.

    4. Select the OVS node you identified in step 1, as shown in the following screenshot:

      Figure 10-6 Select the OVS Node

      Description of Figure 10-6 follows
      Description of "Figure 10-6 Select the OVS Node"

      The OVS node dashboard is displayed as shown in the following screenshot:

      Figure 10-7 OVS Node Dashboard

      Description of Figure 10-7 follows
      Description of "Figure 10-7 OVS Node Dashboard"

    5. Click the Summary tab.

    6. From the Actions pane on the right, click Edit Tags.

      The Edit Tags dialog box is displayed.

    7. Click the plus (+) button.

    8. Enter vserver_placement.ignore_node as the Tag Name.

    9. Enter true as the Value. The following screenshot shows the Edit Tags dialog box after adding the vserver_placement.ignore_node=true tag:

      Figure 10-8 Edit Tags Dialog Box

      Description of Figure 10-8 follows
      Description of "Figure 10-8 Edit Tags Dialog Box"

    10. Click the Save button.
      Once the job is complete, the tag should be visible in the Summary tab under the Tags table. Any new vServers that you create will be placed on nodes other than ones tagged with vserver_placement.ignore_node=true.

      Note:

      To make the OVS node available for placement again, either delete the tag or set the value of the vserver_placement.ignore_node tag to false.

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

  1. Identify the vServers running on the tagged OVS node by doing the following:

    1. Log in to Exalogic Control as a user with the Cloud Admin role.

    2. From the navigation pane on the left, click vDC Management.

    3. Expand vDCs.

    4. Expand MyCloud.

    5. Expand Server Pools.

    6. Click your server pool as shown in the following screenshot:

      The server pool dashboard is displayed.

    7. Click the Summary tab.

    8. Scroll down to the Oracle VM Servers section as shown in the following screenshot:

      Figure 10-10 List of Oracle VM Servers

      Description of Figure 10-10 follows
      Description of "Figure 10-10 List of Oracle VM Servers "

    9. Select the OVS node you tagged in Task 1: Identify and Tag the OVS Node with vserver_placement.ignore_node=true.

    10. Under the Virtual Machines section, note the vServers hosted on the node.

  2. Stop the vServers you identified in the previous step by following the steps described in Section 9.2.9, "Stopping vServers."

  3. Start the vServers you stopped in the previous step by following the steps described in Section 9.2.10, "Starting vServers."

    Note:

    If a HA-enabled vServer fails, while selecting a node for restarting the failed vServer, Exalogic Control considers all of the available nodes, including those that are tagged with vserver_placement.ignore_node=true. To make an OVS node unavailable to HA-enabled vServers as well, you must perform Task 3 (optional): Place the OVS Node in Maintenance Mode.

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

To make an OVS node unavailable to all vServers, including HA-enabled vServers, do the following:

  1. Migrate all vServers off the OVS node as described in Task 2: Migrate the vServers on the Tagged OVS Node to Other Available OVS Nodes.

  2. Log in to Exalogic Control as the Exalogic Systems Admin user.

  3. From the navigation pane on the left, click Assets.

  4. Under Assets, from the drop-down list, select Server Pools, as shown in the following screenshot:

    Figure 10-11 Exalogic Views List

    Description of Figure 10-11 follows
    Description of "Figure 10-11 Exalogic Views List"

    A list of the OVS nodes is displayed.

  5. Select the OVS node you want to make unavailable, as shown in the following screenshot:

    Figure 10-12 Select the OVS Node

    Description of Figure 10-12 follows
    Description of "Figure 10-12 Select the OVS Node"

    The OVS node dashboard is displayed as shown in the following screenshot:

    Figure 10-13 OVS Node Dashboard

    Description of Figure 10-13 follows
    Description of "Figure 10-13 OVS Node Dashboard"

  6. From the actions pane on the right, click Place in Maintenance Mode.

    Note:

    Before you place an OVS node in maintenance mode, ensure that there are no vServers running on the OVS node. All vServers running on the OVS node must be migrated as described in step 1.

    A confirmation box is displayed.

  7. Click Yes.

10.1.7 Changing Passwords for Components on the Exalogic Machine

See MOS document 1594316.1 at:

https://support.oracle.com/epmos/faces/DocumentDisplay?id=1594316.1

10.2 Managing Account Resources

This section describes the following topics:

Before You Begin

Before you can complete these tasks, you must have completed the Cloud User tasks, as described in Section 9.2, "Creating and Managing Exalogic vDC Resources".

10.2.1 Logging In as a Cloud User

Log in to the Exalogic Control console as a Cloud User that you created in Section 6.4, "Creating the Cloud Admin User".

10.2.2 Updating a Server Template

To update the server template that you previously uploaded in your Account, complete the following steps:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (example: Dept1).

    The Dept1 Account dashboard is displayed.

  3. Click the Server Templates tab.

    A list of Server Templates available in your Account is displayed.

  4. Select the Server Template (for example, Template1) that you previously uploaded to your Account.

  5. Click the pencil icon to update the template.

    The Update Server Template screen is displayed, as shown in Figure 10-14.

    Figure 10-14 Update Server Template

    Description of Figure 10-14 follows
    Description of "Figure 10-14 Update Server Template"

  6. Modify the template details, as necessary.

  7. Click Update.

10.2.3 Deleting a Server Template

To delete the Server Template that you previously uploaded in your Account, complete the following steps:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (Dept1). The Dept1 Account dashboard is displayed.

  3. Click the Server Templates tab. The list of Server Templates available in your Account is displayed.

  4. Select the Server Template (for example, Template1) that you previously uploaded to your Account.

  5. Click the X icon to delete the template. A confirmation message is displayed.

  6. Click OK to confirm.

10.2.4 Updating a vServer

To update a vServer, complete the following steps:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (Dept1). The Dept1 Account dashboard is displayed.

  3. Click the vServers tab. vServers created and running in your Account are listed.

  4. Select the vServer (for example, vserverl) that you previously created in your Account.

  5. Click the pencil icon to update the vServer. The Update vServer screen is displayed, as shown in Figure 10-15.

    Figure 10-15 Update vServer

    Description of Figure 10-15 follows
    Description of "Figure 10-15 Update vServer"

  6. Modify vServer details, as necessary.

  7. Click Update to finish.

10.2.5 Deleting a vServer

To delete a vServer, complete the following steps:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (Dept1). The Dept1 Account dashboard is displayed.

  3. Click the vServers tab. vServers running or stopped in your Account are listed.

  4. If the vServer (for example, vserver1) is running, click the Stop vServer icon (red icon) to stop the vServer. Wait till the job succeeds in the Jobs pane.

  5. Select vserver1, and click the X icon. The Delete vServer screen is displayed, as shown in Figure 10-16.

    Figure 10-16 Delete vServer Screen

    Description of Figure 10-16 follows
    Description of "Figure 10-16 Delete vServer Screen"

    This screen also displays the name of the vServer, its description and status.

  6. Click Delete to confirm.

10.2.6 Updating a Private vNet

To update a private vNet that you previously created in your Account, complete the following steps:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (Dept1). The Dept1 Account dashboard is displayed.

  3. Click the Networks tab. In the Private vNets section, the list of private vNets available in your Account is displayed.

  4. Select the private vNet (for example, vnet1) that you previously created in your Account.

  5. Click the pencil icon to update the private vNet. The Update Private vNet screen is displayed, as shown in Figure 10-17.

    Figure 10-17 Update Private vNet

    Description of Figure 10-17 follows
    Description of "Figure 10-17 Update Private vNet"

  6. Modify private vNet details, as necessary.

  7. Click Update to finish.

10.2.7 Deleting a Private vNet

To delete a private vNet, do the following:

Note:

With this procedure, you can delete a vNet even if it is associated with vServers. So before attempting to delete a private vNet, make sure that the vNet not associated with any vServer.

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (Dept1).

    The Dept1 Account dashboard is displayed.

  3. Click the Networks tab.

    In the Private vNets section, the list of private vNets available in your Account is displayed.

  4. Select the private vNet (for example, vnet1) that you want to delete.

  5. Ensure that the private vNet (vnet1) is not associated with any vServer.

  6. Click the X icon to delete the private vNet.

    A confirmation screen is displayed.

  7. Click Delete.

10.2.8 Allocating Virtual IPs for an Account

Before creating vServers with a static IP address, you must allocate IP addresses for your account as follows:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. From the navigation pane on the left, click vDC Accounts.

  3. Under vDC Accounts, click the name of your account.

    The Account dashboard for your account is displayed.

  4. Click the Networks tab.

    The private vNets and public networks available to your account are displayed.

  5. Select the network for which you want to allocate IP addresses.

  6. Click the Launch Allocate vIP Wizard button as shown in Figure 10-18.

    Figure 10-18 Launch Allocate vIP Wizard Button

    Surrounding text describes Figure 10-18 .

    The Allocate vIP Addresses Wizard is displayed.

  7. In the Number of vIPs field, enter the number of IP addresses you want to reserve for static assignments to vServers.

    The IP addresses that you have allocated are displayed.

  8. Click the Allocate vIP button.

  9. Click OK.

    The IP addresses are now available while creating a vServer with a static IP address as described in step 17 of Section 9.2.8, "Creating vServers."

    Note:

    You can click the View Allocated IP Addresses button to see IP addresses that you can allocate when creating vServers with static IP addresses.

10.2.9 Deallocating Virtual IPs for an Account

IP addresses that are no longer necessary for use as static IP addresses for an account can be deallocated as follows:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. From the navigation pane on the left, click vDC Accounts.

  3. Under vDC Accounts, click the name of your account.

    The Account dashboard for your account is displayed.

  4. Click the Networks tab.

    The private vNets and public networks available to your account are displayed.

  5. Select the network for which you want to deallocate IP addresses.

  6. Click the Launch Deallocate vIP Wizard button as shown in Figure 10-19

    Figure 10-19 Launch Deallocate vIP Wizard Button

    Surrounding text describes Figure 10-19 .

    The Deallocate vIP Addresses Wizard is displayed.

  7. Select the IP addresses that you want to deallocate.

    You can use the Ctrl key to select multiple IP addresses.

  8. Click the Deallocate vIP button.

    The IP addresses that you have deallocated are displayed.

  9. Click OK.

    The IP addresses that you deallocated are now unavailable for static allocation to vServers.

10.2.10 Updating a Distribution Group

To update a Distribution Group that you previously created in your Account, complete the following steps:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (Dept1). The Dept1 Account dashboard is displayed.

  3. Click the vServers tab. Distribution Groups available in your Account are listed.

  4. Ensure that the Distribution Group (Dept1-distrgrp11) is not associated with any running vServers.

  5. Select the Distribution Group (for example, Dept1-distgrp1) that you previously created in your Account.

  6. Click the pencil icon to update the Distribution Group. The Update Distribution Groups screen is displayed, as shown in Figure 10-20.

    Figure 10-20 Update Distribution Groups

    Description of Figure 10-20 follows
    Description of "Figure 10-20 Update Distribution Groups"

  7. Modify Distribution Group details, as necessary.

  8. Click Update to finish.

10.2.11 Deleting a Distribution Group

To update a Distribution Group that you previously created in your Account, complete the following steps:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (Dept1). The Dept1 Account dashboard is displayed.

  3. Click the vServers tab. Distribution Groups available in your Account are listed.

  4. Select the Distribution Group (for example, Dept1-distgrp1) that you previously created in your Account.

  5. Click the X icon to delete the Distribution Group.

    Note:

    You can delete a Distribution Group only if it does not have assigned vServers.

  6. If the Distribution Group does not have assigned vServers, click Delete to confirm.

10.2.12 Updating a Volume

To update a volume that you previously created in your Account, complete the following steps:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (Dept1). The Dept1 Account dashboard is displayed.

  3. Click the Storage tab.

  4. Click the Volumes tab. Volumes in your Account are listed.

  5. Select the volume (for example, Volume1) that you previously created in your Account.

  6. Click the pencil icon to update the volume. The Update Volume screen is displayed, as shown in Figure 10-21.

    Figure 10-21 Update Volume

    Description of Figure 10-21 follows
    Description of "Figure 10-21 Update Volume"

  7. Modify volume details, as necessary.

  8. Click Update to finish.

10.2.13 Deleting a Volume

To delete a volume that you previously created in your Account, complete the following steps:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (Dept1). The Dept1 Account dashboard is displayed.

  3. Click the Storage tab.

  4. Click the Volumes tab. Volumes in your Account are listed.

  5. Ensure that the Volume (Volume1) is not attached to any vServer.

  6. Select the volume (for example, Volume1) that you previously created in your Account.

  7. Click the X icon to delete the volume. The Update Volume screen is displayed.

  8. Click Delete to finish.

10.2.14 Updating a Snapshot

To update a volume Snapshot that you previously created in your Account, complete the following steps:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (Dept1). The Dept1 Account dashboard is displayed.

  3. Click the Storage tab.

  4. Click the Snapshots tab. Snapshots in your Account are listed.

  5. Select the Snapshot (for example, Vol1_snapshot) that you previously created in your Account.

  6. Click the pencil icon to update the Snapshot. The Update Snapshot screen is displayed, as shown in Figure 10-22.

    Figure 10-22 Update Snapshot

    Description of Figure 10-22 follows
    Description of "Figure 10-22 Update Snapshot"

  7. Modify Snapshot details, as necessary.

  8. Click Update to finish.

10.2.15 Deleting a Snapshot

To delete a volume Snapshot that you previously created in your Account, complete the following steps:

  1. Log in to the Exalogic Control console as a Cloud User.

  2. In the navigation pane on the left, click vDC Accounts. Under vDC Accounts, click the name of your Account (Dept1). The Dept1 Account dashboard is displayed.

  3. Click the Storage tab.

  4. Click the Snapshots tab. Snapshots in your Account are listed.

  5. Select the Snapshot (for example, Vol1_snapshot) that you previously created in your Account.

  6. Click the X icon to delete the Snapshot. A confirmation screen is displayed.

  7. Click Delete to confirm.