Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. UI needs to give an action for upgrading vm (when vm is in running / stopped state) just like we give the same option when vm is stopped.

Open Issues

1. Should VMs be always marked for dynamic scaling? If so should this be a VM property or part of compute offering? Should dynamic scaling be treated as premium service, in that case having it in compute offering makes more sense from usage/billing perspective?

...

  1. UI needs to call the new api for this and also keep in mind that this api is async in nature unlike the previous one which was sync.

Open Issues

  1. Should scale down be allowed? It can be explicitly prevented since none of the HVs/guest OS supports it.

...

  1. There is also an option of having a custom compute offering where user can specify values for CPU and RAM during deployment or scaling up. But am not sure if this option can be misused since this is a user level API. Another complexity is to capture usage. Currently it is done based on compute offering.

Test cases

TBD

Appendix

Appendix A:

...