Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  • Multiple clusters can share the same primary storage. In cloudstack, Hyper-V is supported only in a zone where there are no other hypervisors besides Hyper-V. A zone wide primary storage will be available to all Hyper-V hosts in the zone.
  • Multiple zone wide primary storage can be added per zone.
  • A cloudstack cluster setup can have both a cluster wide and zone wide primary storage.
  • On upgrade, existing setup should will not be impacted. That is, after upgrade, existing cluster wide primary storage should will not be impacted and administrator can go ahead and add a zone wide or cluster wide primary storage.
  • In cloudstack, currently only SMB 3.0 is supported as a primary storage on Hyper-V. The support for zone wide primary storage will be implemented only for SMB.

Scenarios

...

  • .
  • An instance can be deployed with its volumes on a zone wide primary storage.
  • A volume can be migrated from one zone wide primary storage to any other shared storage.
  • A cloudstack root administrator can live migrate a running instance with its volumes from on host to another host while its volumes migrate from zone wide primary storage to another shared storage.

Test Guidelines

Functional
  • Add a zone wide primary storage to a setup. A user should be able to deploy an instance with its volume on the zone wide primary storage.
  • If a cluster wide and zone wide primary storage both are available; then when creating a volume with shared disk offering, cloudstack by default looks to place a volume first on a cluster wide storage. Use storage tags on disk offering and zone wide storage pools to make sure volumes get placed on zone wide primary store.
  • Validate a volume on a zone wide primary storage and not attached to any instance can be moved/migrated to other shared storage.
  • Validate a running instance with its volumes on a zone wide primary storage can be migrated to another host and its volumes also move to another shared storage.
  • Have a setup with two clusters and atleast one host in each cluster. Add a cluster wide primary storage to one cluster. Also add a zone wide primary storage. Create an instance in a cluster which has a cluster wide primary storage with the volumes on a cluster wide primary. Live migrate the instance with its volumes to the host in second cluster. It should succeed and the volume of the instance should get live migrated to the zone wide primary store.
  • Validate a zone wide primary storage can be put in maintenance mode and removed.
Negative
  • Validate a volume on a zone wide primary storage and not attached to any instance cannot be moved/migrated to a local storage and vice verse.

Support-ability Characteristics

...

There are no db changes for the feature. Existing schema is sufficient to hold information for a zone wide primary storage for Hyper-V too. Information for a zone wide primary storage is stored in the 'storage_pool' table in the db with the scope as 'Zone' and hypervisor type as 'Hyperv'.

Registering zone wide primary storage

...