Page History

...

Users are able to resize autonomously their VM, but, since there is a bug in current version the OpenStack Horizon in ADA cloud, this operation can be done only via OpenStack CLI. 

To know how to configure and use the OpenStack CLI, please refer to the link OpenStack CLI .

Before to perform the resize operation: 

...

To resize a VM, it is necessary to:

• Identify theVM ID:

  Code Block
  language bash
  openstack server list --all | grep <VM_name> openstack server show < vm_ID > | grep flavor

• Identify the IDof the new flavor the VM needs:

  Code Block
  language bash
  openstack flavor list

  • In the case of an Ephemeral VM, check the size of root disk of the original VM. Don't resize the VM if the new flavor has a disk smaller than the current one.

  • In the case of a VM with aBootable Disk, the resize will affect only VCPUs number and RAM. The bootable disk will not be changed by the operation.

  
  

  
  

• Perform the resize, remembering to alert the user of the VM's temporary shutdown during the operation.

  Code Block
  language bash
  openstack server resize --flavor <new_flavor_ID> --wait <vm_ID>

• Wait then the operation to "Complete"; at the same time, on the Openstack Dashboard the message "Confirm" will appear next to the server name.  Then use the command:

  Code Block
  language bash
  openstack server resize confirm <vm_ID>

  Issue theresize confirmation in a separate command, since the option --confirm  on the command openstack server resize  is deprecated.

  
  

  
  

• Verify the success of the operation. Since the Dashboard can have visualization bugs, it is best to check via CLI:

  Code Block
  language bash
  openstack server show < vm_ID > | grep flavor

• Ask the user to confirm the success of the operation. To do that they will need to boot the VM, login, and verify the VCPUs number and Memory size are correct with the following commands:

  Code Block
  language bash
  cat /proc/cpuinfo free -g

...