• Elastic Cloud Server

ecs
  1. Help Center
  2. Elastic Cloud Server
  3. User Guide
  4. Configuration Modifications
  5. Modifying ECS vCPU and Memory Specifications
  6. General Operations for Modifying Specifications

General Operations for Modifying Specifications

Scenarios

If the ECS specifications do not meet service requirements, you can modify the ECS specifications, including vCPUs and memory. Certain ECSs allow you to change their types when you modify their specifications.

Specifications can be modified between general-purpose (S1, C1, C2, or M1) and H1 ECSs and from XEN to KVM ECSs.

  • If you want to change a general-purpose ECS to an H1 ECS, manually configure the source ECS, install the required driver on it, and modify the specifications. For details, see section Changing a General-Purpose ECS to an H1 ECS.
  • If you want to change an H1 ECS to a general-purpose ECS, perform the operations provided in this section.
  • Before changing a XEN ECS to a KVM ECS, manually install the required driver on the ECS. Otherwise, the ECS will be unavailable after the modification is performed. For example, starting the OS will fail.

    For details, see sections Changing a XEN ECS to a KVM ECS (Windows) and Changing a XEN ECS to a KVM ECS (Linux).

  • For instructions about how to modify the specifications of other ECSs, see this section.

Background

To obtain the virtualization type of an ECS, perform the following operations:

  1. On the page providing details about the ECS, view the ECS specifications.
    Figure 1 Viewing ECS specifications
  2. Check the specifications tables in section ECS Types for the virtualization type.

Notes

  • If ECS specifications are downgraded, the ECS performance is deteriorated.
  • Certain ECSs do not support specifications modification currently. For details about available ECS types as well as their functions and usage, see section "Notes" in ECS Types.

Step 1: Modify Specifications

The following section provides only general operations for modifying specifications. For instructions about how to change a general-purpose ECS to an H1 ECS, see section Changing a General-Purpose ECS to an H1 ECS. For instructions about how to change a XEN ECS to a KVM ECS, see section Changing a XEN ECS to a KVM ECS (Windows) or Changing a XEN ECS to a KVM ECS (Linux).

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Computing, click Elastic Cloud Server.
  4. On the Elastic Cloud Server page, view the status of the target ECS.

    If the ECS is not in Stopped state, click More in the Operation column and select Stop.

  5. Click More in the Operation column and select Modify Specifications.

    The Modify ECS Specifications page is displayed.

  6. Select the new ECS type, vCPUs, and memory as prompted.
  7. (Optional) Set DeH.

    If the ECS is created on a DeH, the system allows you to change the DeH.

    To do so, select the target DeH from the drop-down list. If no DeH is available in the drop-down list, remaining DeH resources are insufficient and cannot be used to create the ECS with specifications modified.

  8. (Optional) Select the check box to confirm the ECS configuration.
  9. Click OK.
  10. On the Modify ECS Specifications page, confirm the modified vCPU and memory specifications and click Submit.
  11. Check whether the specifications have been modified.

    After modifying the specifications, you can check whether the specifications have been modified in Failures.

    1. Check whether Failures is displayed on the management console. For details, see section Viewing Failures.
      • If yes, go to step 11.b.
      • If no, the specifications have been modified.
    2. Click Failures. Then, in the Failures dialog box, click Operation Failures and check whether the task is contained in the list by Name/IDOperated At, or Task.
      • If yes, the specifications modification failed. See section Follow-up Procedure for failure causes.
      • If no, the specifications have been modified.

Step 2: Check Disk Attachment

After specifications are modified, disk attachment may fail. Therefore, check disk attachment after specifications modification. If disks are properly attached, the specifications modification is successful.

  • Windows
    1. Check whether the number of disks displayed on the Computer page after specifications modification is the same as that before specifications modifications.
      • If yes, the disks are properly attached. No further action is required.
      • If no, an error has occurred in disk attachment. In such a case, go to 2.

      An example is provided as follows:

      An ECS running Windows Server 2008 has one system disk and two data disks attached before specifications modifications.

      Figure 2 Disk attachment before specifications modification

      After the specifications are modified, check disk attachment.

      Figure 3 Disk attachment after specifications modification

      Only one system disk is displayed. Data disks failed to attach after the specifications modification.

    2. Set the affected disks to be online.
      1. Click Start in the task bar. In the displayed Start menu, right-click Computer and choose Manage from the shortcut menu.

        The Server Manager page is displayed.

      2. In the navigation pane on the left, choose Storage > Disk Management.

        The Disk Management page is displayed.

      3. In the left pane, the disk list is displayed. Right-click the affected disk and choose Online from the shortcut menu to make it online.
        Figure 4 Making the disk online
    3. On the Computer page, check whether the number of disks is the same as that before the specifications modification.
      • If yes, no further action is required.
      • If no, contact customer service.
      Figure 5 Disk attachment after disk online
  • Linux
    1. Log in to the ECS as user root.
    2. Run the following command to view the disks attached before specifications modification:

      fdisk -l | grep 'Disk /dev/'

      Figure 6 Viewing disks attached before specifications modification

      As shown in Figure 6, the ECS has three disks attached: /dev/vda, /dev/vdb, and /dev/vdc.

    3. Run the following command to view disks attached after specifications modification:

      df -h| grep '/dev/'

      Figure 7 Viewing disks attached after specifications modification

      As shown in Figure 7, only one disk /dev/vda is attached to the ECS.

    4. Check whether the number of disks obtained in 2 is the same as that obtained in 3.
      • If yes, the specifications have been modified. No further action is required.
      • If no, the disk attachment failed. In such a case, go to 5.
    5. Run the mount command to attach the affected disks.

      An example is provided as follows:

      mount /dev/vbd1 /mnt/vbd1

      In the preceding command, /dev/vbd1 is the disk to be attached, and /mnt/vbd1 is the path for disk attachment.

      Ensure that /mnt/vbd1 is empty. Otherwise, the attachment will fail.

    6. Run the following commands to check whether the numbers of disks before and after specifications modification are the same:

      fdisk -l | grep 'Disk /dev/'

      df -h| grep '/dev/'

      • If yes, no further action is required.
      • If no, contact customer service.
      Figure 8 Checking the number of disks attached

      As shown in Figure 8, the numbers of disks before and after specifications modification are the same. The disks are /dev/vda, /dev/vdb, and /dev/vdc.

Follow-up Procedure

Perform the following operations in the event of a specifications modification failure:

  1. Log in to the management console.
  2. Under Management & Deployment, click Cloud Trace Service.
  3. In the navigation pane on the left, choose Trace List.
  4. In the Trace Name column, locate the resizeServer event by resource ID.

    The resource ID is the ID of the ECS on which the specifications modification failed.

  5. Click View Trace in the Operation column to view the failure cause.

    If the fault cannot be rectified based on logs, contact customer service for technical support.