You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. cluster-vsan-1 is tagged with zone-a. So, vsanDatastore inherits zone-a since all the hosts under zone-a have vsanDatastore mounted on them.
67
67
2. cluster-vsan-2 is tagged with zone-b. So, vsanDatastore (1) inherits zone-b since all the hosts under zone-b have vsanDatastore (1) mounted on them.
68
68
3. sharedVmfs-0 inherits both zone-a and zone-b since all the hosts in both zone-a and zone-b have this datastore mounted on them.
69
69
4. cluster-3 is tagged with zone-c. cluster-3 only contains host-7.
70
-
5. host-8 is not under any cluster and is tagged with zone-c.
71
-
6. Since there are no shared datastores between host-7 under cluster-3 and host-8, no datastores in the environment inherit zone-c.
72
-
7. The six worker nodes are distributed among the hosts as shown in the above illustration.
73
-
8. Two storage policies are created on VC. One is a VSAN storage policy named as compatpolicy with hostFailuresToTolerate capability set to 1.
74
-
Second is a VSAN storage policy named as noncompatpolicy with hostFailuresToTolerate capability set to 4.
70
+
5. host-3 under cluster-vsan-1 is tagged with zone-c.
71
+
6. Since there are no shared datastores between host-7 under cluster-3 and host-3 under cluster-vsan-1, no datastores in the environment inherit zone-c.
72
+
7. host-8 under datacenter-2 and cluster-1 is tagged with zone-d. So, localDatastore attached to host-8 inherits zone-d.
73
+
8. The six worker nodes are distributed among the hosts as shown in the above illustration.
74
+
9. Two storage policies are created on VC. One is a VSAN storage policy named as compatpolicy with hostFailuresToTolerate capability set to 1.
75
75
76
76
Testsuite description :
77
77
1. Tests to verify that zone labels are set correctly on a dynamically created PV.
@@ -80,6 +80,7 @@ import (
80
80
datastore and VSAN capabilities.
81
81
4. Tests to verify dynamic pv creation using availability zones fails in combination with other storage class parameters such as storage policy,
82
82
datastore and VSAN capabilities specifications when any of the former mentioned parameters are incompatible with the rest.
83
+
5. Tests to verify dynamic pv creation using availability zones work across different datacenters in the same VC.
ginkgo.It("Verify a pod is created and attached to a dynamically created PV, based on the allowed zones specified in storage class when the datastore under the zone is present in another datacenter", func() {
319
+
ginkgo.By(fmt.Sprintf("Creating storage class with zone :%s", zoneD))
ginkgo.It("Verify a pod is created and attached to a dynamically created PV, based on the allowed zones and datastore specified in storage class when there are multiple datastores with the same name under different zones across datacenters", func() {
325
+
ginkgo.By(fmt.Sprintf("Creating storage class with zone :%s and datastore name :%s", zoneD, localDatastore))
ginkgo.It("Verify a pod is created and attached to a dynamically created PV with storage policy specified in storage class in waitForFirstConsumer binding mode", func() {
314
332
ginkgo.By(fmt.Sprintf("Creating storage class with waitForFirstConsumer mode and storage policy :%s", compatPolicy))
0 commit comments