Manually Reconfiguring VM Resources

In this topic:

About resource reconfiguration

Reconfiguring VM resources means:

  • changing the amount of memory and the number of virtual processors assigned to a VM, or changing the instance type
  • adding or deleting network adapters
  • adding, changing or removing storage

Not all of these options are available on all cloud platforms.

There are three ways to reconfigure VM resources in Commander and the Service Portal:

The method you choose to expose to users depends on how much control you want over VM configuration changes. If you need to control VM configuration changes for some or all of your users, you should require users to apply a recommendation or to submit a change request, rather than allowing them to manually reconfigure VM resources.

This task requires the Service Portal permissions Modify VM CPU & Memory and Modify VM Storage. Service Portal users can reconfigure memory, CPU, storage and network resources (or change the instance type, in the case of public cloud VMs).

Caution: Networks are not filtered by deployment destination or user visibility, which means a user with the Modify VM Network permission is able to see networks that they don't have access to.

Hot/cold resource changes for each cloud platform

What you can change depends on the power state of the VM and the cloud platform. The following table indicates whether you must power off the VM in order to perform each task.

Not Supported indicates that this type of resource change is supported by the cloud platform, but not supported by Commander.

 

Power down required?

vCenter

SCVMM

AWS

Azure

GCP

Modify CPU / memory resources OR change instance type

Dictated by CPU Hot Plug and Memory Hot Plug settings for the VM in vCenter

Yes

Yes

Yes

Yes

Add network adapters

No

Yes

Not Supported

Not Supported

Not Supported

Delete network adapters

Yes

Yes

Not Supported

Not Supported

Not Supported

Modify network adapters

No

No

Not Supported

Change subnet: Yes

Other changes: Not Supported

Not Supported

Add storage

No

No

No

No

Not Supported

Delete storage

No

No

No (base disk can't be deleted)

No (base disk can't be deleted)

Not Supported

Modify existing storage

No

Yes

Not Supported

Yes

Not Supported

Reconfiguring resources for vCenter and SCVMM VMs

Access through:

Views menu > Inventory > Infrastructure or Applications

Available to:

Administrator, Operator with Approval, Operator Access Rights

To reconfigure resources for vCenter and SCVMM VMs:

  1. Select a VM in the tree or on the Virtual Machines tab.
  2. Right-click and select Configuration Management > Reconfigure VM Resources.
  3. In the menu, select the resource you want to configure.
  4. CPU & Memory: Specify values for memory size and CPU count as required.

    vCenter: If you've enabled CPU Hot Add, CPU Hot Remove or Memory Hot Add for the VM, you can change CPU and memory resources while the VM is powered on, within the allowed range.

    Caution: If you change the number of virtual processors for a VM after the guest operating system has been installed, the VM may become unstable.

  5. Network: Specify network settings as required. To add adapters for the VM, click Add Network Adapter.

    If you have a large number of networks, click next to the Network drop-down list to open a pop-up dialog for easier searching.

  6. Storage: For existing disks, you can modify their capacity and delete them.

    It's not possible to resize IDE disks, independent disks, or disks involved in a snapshot or linked clone chain.

    To add a disk:

    1. Click Add and then specify disk capacity, disk type and location.
    2. To specify the datastore: Choose Select a datastore from the Location drop-down list. The Select Datastore dialog appears, allowing you to specify the datastore.  Commander provides capacity information to guide your decision.  
    3. The options available in the Disk Provisioning drop-down list depend on the selected datastore and the VM's hardware version:

      vCenter disk provisioning options

      SCVMM disk provisioning options

      • Thin: Allocate disk space on demand. Supports over-allocation of storage resources.
      • SEsparse: Allocate disk space as it's used by the guest OS. Supports over-allocation of storage resources. Block size is configurable and space may be reclaimed.

        The SEsparse format is supported only for hardware version 9 or higher.

      • Thick - Lazy Zeroed: Allocate disk space now. Disk blocks are zeroed out on first write. This is the default format.
      • Thick - Eager Zeroed: Allocate disk space now. All disk blocks are zeroed out during disk creation. This is required to support clustering features such as Fault Tolerance.
      • Dynamically Expanding: Save storage space by creating a small file that grows as data is written to it, up to the configured limit.
      • Fixed Format: Allow the datastore to occupy the entire space provisioned for it by creating a file equivalent in size to the disk you are creating (for example, 20 GB on disk for a 20 GB VHD). This is the default format.

      The datastore where the VM resides and the datastore where the new disk is placed must both be clustered, or must both be non-clustered. All new disks are created as SCSI disks.

    4. To delete a disk, select it in the Disks list and click Delete.

Reconfiguring resources for AWS instances

Access through:

Views menu > Inventory > Infrastructure or Applications

Available to:

Administrator, Operator with Approval, Operator Access Rights

To reconfigure resources for AWS instances:

  1. Select a VM in the tree or on the Virtual Machines tab.
  2. Right-click and select Configuration Management > Reconfigure VM Resources.
  3. To change the instance type, on the Instance Type page, select an instance type from the drop-down list.

    Notes:

    • To change the instance type, the VM must be powered off.
    • Click Details to see the full set of properties for the selected instance type.
    • EBS Optimized: If the selected instance type supports EBS optimization, this option is active. EBS optimization enables additional, dedicated throughput between Amazon EC2 and Amazon EBS, and therefore improved performance for Amazon EBS volumes. Additional charges from AWS apply if you enable this option.
  4. To create a new EBS volume and attach it to this VM, on the Storage page, click Add and specify the following:
    • Device Name: Specify the name that the block device driver for the instance will assign when mounting the volume. The name recommended by Amazon is provided; edit this value if required. See Block Device Mapping in the AWS documentation for more information.
    •  Capacity: Specify the disk capacity, in GB.
    • Volume Type: Select one of the following types from the drop-down list. Hover over the icon for details on each type; see Amazon EBS Volume Types in the AWS documentation for more information.
      • General Purpose (SSD): General purpose Solid-State Drive volume that balances price and performance for a wide variety of transactional workloads. Recommended for system boot volumes, virtual desktops, low-latency interactive apps, development and test environments.
      • Provisioned IOPS (SSD): Highest-performance SSD volume designed for mission-critical applications. Best for critical business applications that require sustained IOPS performance, or more than 10,000 IOPS or 160 MiB/s of throughput per volume, such as large database workloads and EBS-optimized instances. The ratio of IOPS provisioned and the volume size requested can be a maximum of 50.
      • Magnetic: Previous-generation Hard Disk Drive volumes for workloads where data is infrequently accessed. Not recommended for new applications.
      • Throughput Optimized (HDD): Low-cost Hard Disk Drive volume designed for frequently accessed, throughput-intensive workloads. Best for streaming workloads requiring consistent, fast throughput at a low price, such as big data, data warehouses, and log processing. The minimum disk size for this type is 500 GB. can't be a boot volume.
      • Cold (HDD): Lowest-cost Hard Disk Drive volume designed for less frequently accessed workloads. Best for throughput-oriented storage for large amounts of data that is infrequently accessed. The minimum disk size for this type is 500 GB. can't be a boot volume.
    • IOPS: If you select the Provisioned IOPS (SSD) volume type, you must specify the number of I/O operations per second (IOPS) this volume will support. Specify a number between 100 and 10,000. A maximum ratio of 50:1 is permitted between IOPS and volume size; for example, a volume with 3000 IOPS must be at least 60 GB in size. The minimum disk size for this storage type is 4 GB.
    • Encryption: Specify whether to encrypt the disk. Note that not all instance types support disk encryption; see Amazon EBS Encryption in the AWS documentation for the list of supported instance types.
    • Delete on Termination: By default, this disk will be deleted when the VM to which it's attached is terminated. If you want to preserve this disk so that it can be attached to a different VM when this VM is terminated, disable this option.

      The new disk is created in the same availability zone as the instance it's attached to.

  5. To delete a disk, on the Storage page, select a disk and click Delete. Click OK to confirm the deletion.

    You can't remove the base disk.

  6. Click OK.

Reconfiguring resources for Azure instances

Access through:

Views menu > Inventory > Infrastructure or Applications

Available to:

Administrator, Operator with Approval, Operator Access Rights

To reconfigure resources for Azure instances:

  1. Select a VM in the tree or on the Virtual Machines tab.
  2. Right-click and select Configuration Management > Reconfigure VM Resources.
  3. To change the instance type, go to the Instance Type page and select an instance type from the drop-down list. The VM must be powered off.

    Click Details to see the full set of properties for the selected instance type.

  4. To change the subnet, go to the Network page and select a subnet from the list of those available in the VM's network. The VM must be powered off.
  5. To add storage resources, go to the Storage page, click Add and specify the following:
    • Device Name: Edit the suggested device name if required. Managed disk names must be unique in the target resource group. Unmanaged disk names must unique within the VM. The name must contain from 1 to 64 characters, must contain only letters, numbers, hyphens, dots and underscores, and must start with a letter or number.

      Even though you can edit the name for a managed disk, the suggested name will be used.

    • Capacity: Specify the disk capacity in GB. Note that you can't shrink existing disks, and you can't resize existing unmanaged disks.
    • Disk Type: Select one of the following types from the drop-down list:

      SSD: Premium disks (SSD) are backed by solid-state drives and offer consistent, low-latency performance. They provide the best balance between price and performance, and are ideal for I/O-intensive applications and production workloads. Premium disks are not supported for all instance types.

      HDD: Standard disks (HDD) are backed by magnetic drives and are preferable for applications where data is accessed infrequently.

    • Storage Account: For unmanaged disks, select a storage account from the list. You can select only storage accounts that are available in the image's region and support the selected Disk Type.

      Notes:

      • You can't configure encryption for a new disk.
      • Each Azure instance type has limitations for the number and type of disks that can be added.
  6. To delete a disk, go to the Storage page, select a disk, click Delete, and confirm the deletion.

    You can't remove the base disk.

  7. To expand an existing disk, go to the Storage page, select the disk you want to expand, enter a number in the Capacity field, and click OK.

    The VM must be powered off to expand a disk.

Reconfiguring resources for GCP instances

In this release, you can change the instance type for a GCP instance, but you can't change network or storage resources.

In addition to choosing a predefined GCP instance type, you can also choose custom values for memory and CPU. To learn more, see Creating a VM Instance with a Custom Machine Type in the GCP documentation.

To change CPU and memory resources, the instance must be powered off.

Access through:

Views menu > Inventory > Infrastructure or Applications

Available to:

Administrator, Operator with Approval, Operator Access Rights

To change memory and CPU resources for a GCP instance:

  1. Select an instance in the tree or on the Virtual Machines tab.
  2. Right-click and select Configuration Management > Reconfigure VM Resources.
  3. If one of the predefined instance types meets your needs, select it from the drop-down list.

    Click Details to see the full set of properties for the selected instance type.

  4. If none of the predefined instance types fits your needs:
    1. Select Custom from the drop-down list.
    2. Enter values for CPU Count and Memory (GB) as required.

      The maximum CPU count is determined by the region and the CPU platform. Commander doesn't validate your value. If you enter an invalid value, the task may fail.

      The minimum and maximum memory values depend on the value you entered for CPU Count.

    3. A custom machine can have up to 6.5 GB of memory per vCPU. If this isn't enough memory for your workload, enable Extended Memory.

      The maximum extended memory depends on the region. Commander doesn't validate that your value is permitted by the region.

      Caution: Extended memory incurs additional costs. To learn more, see Adding extended memory to a machine type in the GCP documentation.

  5. Click OK.