cloudstack/engine
Harikrishna b774ee5d11
vmware: Datastore cluster synchronization should check if the child datastores are in UP state or not (#7385)
This fix ensures when datastore cluster in VMware is added as a primary storage pool in CloudStack then all the child datastores (which already exists in CS) should be in Up state.

For example:

1. Datastore Cluster DS has two child datastores A and B in vCenter. (B is already added as a storage pool in CloudStack)
2. Now try to add datastore cluster DS into CloudStack as a primary storage pool
3. CloudStack tries to add child datastores A and B in CloudStack, since B is already there in CloudStack, it will reuse the existing storagepool entry and will keep under parent Storage pool DS.

During Step 3 we are now checking if B is Up state or not.
2023-04-11 22:23:12 +05:30
..
api Updating pom.xml version numbers for release 4.18.1.0-SNAPSHOT 2023-03-15 19:38:14 +01:00
components-api vmware: Datastore cluster synchronization should check if the child datastores are in UP state or not (#7385) 2023-04-11 22:23:12 +05:30
network Updating pom.xml version numbers for release 4.18.1.0-SNAPSHOT 2023-03-15 19:38:14 +01:00
orchestration Merge remote-tracking branch 'apache/4.17' into 4.18 2023-03-31 17:00:00 +05:30
schema Fix build failure and 4.18.0.0->4.18.1.0 upgrade path 2023-03-16 13:18:26 +05:30
service Updating pom.xml version numbers for release 4.18.1.0-SNAPSHOT 2023-03-15 19:38:14 +01:00
storage vmware: Datastore cluster synchronization should check if the child datastores are in UP state or not (#7385) 2023-04-11 22:23:12 +05:30
pom.xml Updating pom.xml version numbers for release 4.18.1.0-SNAPSHOT 2023-03-15 19:38:14 +01:00