Versions Compared

Old Version 43

changes.mady.by.user Sateesh Chodapuneedi

Saved on

compared with

New Version 44

changes.mady.by.user Sateesh Chodapuneedi

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: open issue added for zone with multiple hypervisors

...

  1. Considering a model where a CloudStack deployment will have some zones with multiple DCs and some zones with single DC. This comes from the fact that existing CloudStack deployment has zones with multiple DCs. But after upgrade to the new newest version, customer would like to have existing zones to operate as-is. But all new CloudStack zones would be having single DC. In this model, the existing zone with multiple DCs is termed as Legacy zone and it will not support the zone wide features are requires a zone to have only 1 DC. Also operations on legacy zone should be seamless (like adding a cluster etc.) as they were before upgrade. This means the code base doesn't apply any new logic, that affects the functionality, over legacy zone. For example, constraint checks that happen while adding a cluster to new zone should not be done if the zone is legacy zone.
  2. New features like zone wide primary storage doesn't go well with zones having multiple hypervisors. How upgrade handled for such zones?

Impact on other areas/features

...