You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Bug Reference

https://issues.apache.org/jira/browse/CLOUDSTACK-658

Branch

master, 4.1.0

Introduction

It is not always possible to exactly identify the CPU and RAM requirements at the time of deploying a VM. But for various reasons it may be required to scale up these resources later on. At that time there is no other way but to restart the VM with increased resources. Dynamic scaling for CPU and RAM feature would allow to change these resources for a running VM avoiding any downtime.

Purpose

This document describes the specifications and design of the feature.

References

  • relevant links

Document History

Glossary

Feature Specifications

  • Ability to scale up CPU and/or RAM for running user VMs based on predefined compute offerings
  • Ability to scale up CPU and/or RAM for running system VMs based on predefined system compute offerings
  • If scaling up requires a migration it will be limited within the cluster only - if the current host where VM is running has capacity then simply the resources will be scaled up, if not live migration will be done within the cluster and then resources will be scaled up. If no suitable host is found operation will fail. In future if live migration across across clusters is possible then this constraint can be relaxed.
  • Ability to mark the VM for scale up at creation time (see open issue#1)
  • Ability to scale down CPU and RAM (see open issue#2)
  • No check for guest OS compatibility (can be considered only if there is a concise document/API listing for supported guest OS's for each hypervisor)
  • Only supported for newly created VMs, existing VMs (from prior CS releases) won't have the capability to scale up*- ability to scale up CPU and/or RAM for running system VMs based on predefined system compute offerings*
    - scale up would be scoped to the same cluster - if the current host where VM is running has capacity then simply the resources will be scaled up, if not live migration will be done within the cluster and then resources will be scaled up. If no suitable host is found operation will fail. In future if live migration across across clusters is possible then this constraint can be relaxed.
    - ability to mark the VM for scale up (see open issue#1)
    - ability to scale down CPU and RAM (see open issue#2)
    - no check for guest OS compatibility (can be considered only if there is a concise document/API listing for supported guest OS for each hypervisor)

- only supported for newly created VMs, existing VMs (from prior CS releases) won't have the capability to scale up- ability to scale up CPU and/or RAM for running user VMs based on predefined compute offerings
- ability to scale up CPU and/or RAM for running system VMs based on predefined system compute offerings
- scale up would be scoped to the same cluster - if the current host where VM is running has capacity then simply the resources will be scaled up, if not live migration will be done within the cluster and then resources will be scaled up. If no suitable host is found operation will fail. In future if live migration across across clusters is possible then this constraint can be relaxed.
- ability to mark the VM for scale up (see open issue#1)
- ability to scale down CPU and RAM (see open issue#2)
- no check for guest OS compatibility (can be considered only if there is a concise document/API listing for supported guest OS for each hypervisor)
- only supported for newly created VMs, existing VMs (from prior CS releases) won't have the capability to scale 

Hypervisor support

- Currently planning to do it for Vmware. Support for other HVs can also be added based on HV capabilities.

Use cases

- End users can scale up CPU and/or RAM for running VMs

Architecture and Design description

A new command class needs to be defined for actually changing CPU/RAM at agent layer. This needs to be handled for the supported HVs.

ReconfigureVMCommand: This will have the updated CPU and RAM values as members

*Allocation logic: *Refer to flow chart below

Web Services APIs

list changes to existing web services APIs and new APIs introduced with signatures and throughout documentation

UI flow

  • either demonstrate it visually here or link to relevant mockups

Appendix

Appendix A:

Appendix B:

  • No labels