cloudstack/engine/storage
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
..
cache Updating pom.xml version numbers for release 4.18.1.0-SNAPSHOT 2023-03-15 19:38:14 +01:00
configdrive Updating pom.xml version numbers for release 4.18.1.0-SNAPSHOT 2023-03-15 19:38:14 +01:00
datamotion Updating pom.xml version numbers for release 4.18.1.0-SNAPSHOT 2023-03-15 19:38:14 +01:00
image Updating pom.xml version numbers for release 4.18.1.0-SNAPSHOT 2023-03-15 19:38:14 +01:00
integration-test Updating pom.xml version numbers for release 4.18.1.0-SNAPSHOT 2023-03-15 19:38:14 +01:00
snapshot Updating pom.xml version numbers for release 4.18.1.0-SNAPSHOT 2023-03-15 19:38:14 +01:00
src Create API to reassign volume (#6938) 2023-01-27 11:10:56 +01:00
volume 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
storage.ucls CLOUDSTACK-10105: Use maven standard project structure in all projects (#2283) 2018-01-20 03:19:27 +05:30