Mapping Vmware datacenter Cloudstack zone test execution

Transcription

1 Mapping Vmware datacenter Cloudstack zone test execution Test execution results: vmwaremapnew2.xls vmware datacenter cloudstack zone mapping model DVS switch Hypervisor: ESXi ESXi Test Id Test case description Steps Expected Result Priority VMWARE Zone configuration - Advance 1 Vcenter C PP 4.2 H1 zone1 - C1 - H1 PS1 MS - advance zone 1 Vcenter 2 DC with multiple clusters zone creation successful H3 H4 C2 - C2 - H3 DC2 - C3 - zone2 - C3 - H4 PS6 ZPS5 2 Vcenter C PP 4.2 H1 zone1 - C1 - H1 PS1 Z MS - advance zone multiple Vcenters 2 DC multiple clusters different subnet zone creation successful H3 C2 - C2 - H3 VC2 - DC3 - C4 - H4 zone2 - C4 - H4 ZPS5 clusters in different subnet Zone DC AddVMwareDC 1. Vcenter create DC cluster hosts 2. MS Add the Vcenter DC to zone RemoveVMware DC MS Remove Vcenter DC from zone [ /client/api? command=removevmwaredc ] &zoneid=37751cd3-7fe be39- d26a0807a469&_= { "removevmwaredcresponse" : Unknown macro: {"uuidlist"

2 ListVMwareDC MS List Vmware DCs in zone [ command=listvmwaredcs ] &zoneid=37751cd3-7fe be39- d26a0807a469&_= { "listvmwaredcsresponse" : { "count":1," VMwareDC" : [ Unknown macro: {"id" ] AddVMwarecluster MS Add Vmware cluster to Vcenter DC in zone [ /client/api? command=addcluster ] &zoneid=37751cd3-7fe be39- d26a0807a469&hypervisor=vm ware&clustertype=externalman aged &podid=299f284a-7bc7-482b b92a8f790c9&username=Adm inistrator &password=password2&publicv switchtype=vmwaredvs&guestv switchtype=vmwaredvs &url=http%3a%2f%2f %2Fd1% 2Fc2&clustername= RemoveVMwarecluster MS Remove Vmware cluster from Vcenter DC in zone [ /client/api? command=deletecluster ] &id= d-deac-47f a1f001b7 { "deleteclusterresponse" : Unknown macro: { "success" disablecluster disable vmware cluster [ command=updatecluster ] &id= d-deac-47f a1f001b7&allocationstate=Disabled { "updateclusterresponse" : { "cluster" : Unknown macro: {"id" enablecluster enable vmware cluster [ command=updatecluster ] &id= d-deac-47f a1f001b7&allocationstate=Enabled { "updateclusterresponse" : { "cluster" : Unknown macro: {"id" managecluster manage vmware cluster [ command=updatecluster ] &id= d-deac-47f a1f001b7&managedstate=Managed { "updateclusterresponse" : { "cluster" : Unknown macro: {"id"

3 unmanagecluster unmanagae vmware cluster [ command=updatecluster ] &id= d-deac-47f a1f001b7&managedstate=Unmanage d { "updateclusterresponse" : { "cluster" : Unknown macro: {"id" Network M isolated VPC network 1. In advance zone create isolated VPC network [ /client/api? command=createvpc&name=v pc1 ] &displaytext=vpc1&zoneid=377 51cd3-7fe be39- d26a0807a469 &cidr= % 2F16&vpcofferingid=ca01a99f- 579f-4c e bcfb&_= { "createvpcresponse" : Unknown macro: {"id" isolated nonvpc network 1. In advance zone create non VPC network non VPC network creation successful listvpc network states Extend IP range of the network 1. Advance zone Create Shared NW1 scope zone. Vm deployment should succeed. 2. Deploy few Vms in this network. Vm should be assigned address from the extended range. 3. Consume all ips in range All VMs in NW1 unable to access each other 4. Extend Ip range. All VMs in NW1 able to reach DHCP server, gateway 5. Deploy Vm in this network. Restart network 1. Advance zone Create Shared NW1 scope zone. Network restart should succeed. 2. Deploy few Vms in this network. After network restart: 3. Restart Network. All VMs in NW1 unable to access each other All VMs in NW1 able to reach DHCP server, gateway We should be able to deploy new Vms in this network.

4 Restart network with cleanup option Delete network with vms in "Running" state Delete network when there are no Vms associated with it. Stop all Vms in network and wait for network shutdown delete one of the IP range while not in use delete one of the IP range while in use in 1. Advance zone Create Shared NW1 scope zone. 2. Deploy few Vms in this network. 4. Restart Network with cleanup option. 1. Advance zone Create Shared NW1 scope zone <pvlan1, svlan1>. 2. Deploy few Vms in this network 3. Delete Network. 1. Advance zone Create Shared NW1 scope zone. 2. Deploy few Vms in this network. 3. Destroy all the Vms. 4. Delete Network after all the Vms are expunged. 1. Advance zone Create Shared NW1 scope zone. 2. Deploy few Vms in this network. 3. Stop all the Vms. 4. Wait for network scavenger thread to run. In network with multiple IP ranges & no VMs in network, delete one of the IP range In network with multiple IP ranges & VMs in IP range of network, delete one of the IP range with VMs. Network restart should succeed. After network restart: All VMs in NW1 unable to access each other. All VMs in NW1 able to reach DHCP server, gateway We should be able to deploy new Vms in this network.as part of network restart m Router is stopped and started. Following 3 entries for the router should get deleted and re-created in the host:ovs-ofctl dump-flows xenbr01. cookie=0x0, duration= s, table=0, n_packets=8, n_bytes=2748, priority=100,udp,dl_vlan=998, nw_dst= , tp_dst=67 actions=strip_vlan, output:182. cookie=0x0, duration= s, table=0, n_packets=20, n_bytes=1148, priority=200,arp,dl_vlan=998, nw_dst= actions=strip_vlan,output:183. cookie=0x0, duration= s, table=0, n_packets=37, n_bytes=3176, priority=150, dl_vlan=998, dl_dst=06:e0:d8: 00:00:1c actions=strip_vlan, output:18 Network Deletion should fail. Network Deletion should succeed. Network should not be picked up for Shutting down. delete one of the IP range while not in use succeed delete one of the IP range while in use by VMs fail VM Deployment isolated VPC and nonvpc network advance zone VPC network Deploy VM centos with data disk 1. In advance zone create VPC network 2. Deploy VMs with data disk using centos template. Check PF LB rules 2. VMs in running state. PF LB rules should work advance zone VPC network Deploy VM centos without data disk 1. In advance zone create VPC network 2. Deploy VMs without data disk using centos template. Check PF LB rules 2. VMs in running state. PF LB rules should work advance zone VPC network Deploy VM windows with data disk 1. In advance zone create VPC network 2. Deploy VMs using windows template. 2. VMs in running state. PF LB rules should work advance zone nonvpc network Deploy VM centos with data disk 1. In advance zone create nonvpc network 2. Deploy VMs with data disk using centos template. Check PF LB rules 2. VMs in running state. PF LB rules should work

5 advance zone nonvpc network Deploy VM centos without data disk 1. In advance zone create nonvpc network 2. Deploy VMs without data disk using centos template. Check PF LB rules 2. VMs in running state. PF LB rules should work VM Life cycle Stop VM Start VM Destroy VM Restore VM Destroy VM (Expunged) Reboot VM Stop an existing VM that is in "Running" State. [we should flesh out the steps here starting with 'deploy a vm'] Start an existing VM that is in "Stopped" State. Destroy an existing VM that is in "Running" State. Restore a VM instance that is in "Destroyed" state. Destroy an existing VM that is in "Running" State. Wait for the Expunge Interval (expunge.delay). 1.Deploy VM. 2.Reboot VM. 1. Should Not be able to login to the VM. should be "Stopped". "Stopped" 1. Should be able to login to the VM. should be "Running". "Running" 1. Should not be able to login to the VM. should be "Destroyed". "Destroyed" 1. listvm command should should be "Stopped". 2. We should be able to Start this VM successfully. "Destroyed" 1. listvm command should NOT return this VM any more. 2. DB check : 1. VM_INSTANCE table - state should be "Expunging". 2. No entries relating to this VM in the NICS table. 3. No entries relating to this VM in the VOLUMES table. 4. Make sure the volumes get removed from the Primary Storage. 1. Should be able to login to the VM. return the deployed VM. State of this VM should be "Running". Migrate VM 1.Deploy VM. 1. Should be able to login to the VM. 2.Check to make sure you are able to log in to this VM. 3.Migrate vm to another host in the same cluster. should be "Running" and the host should be the host to which the VM was migrated to. Attach ISO 1.Deploy VM. 1.Log in to the Vm. We should be able to see a device attached. 2.Attach ISO to this VM. 2. You should be able to mount this device and use the ISO. Detach ISO 1.Deploy VM. 1.Log in to the Vm. We should be see device is not attached to the VM anymore. Change Service to use less CPU and Memory 2.Attach ISO to this VM. Log in to the Vm and make sure you see a device attached which has the ISO. 3. Detach ISO. 1.Deploy VM using default template, "small" service offering and small data disk offering. 2.Stop VM 1.Log in to the Vm.We should see that the CPU and memory Info of this Vm matches the one specified for "Medium" service offering. 2. Using listvm command verify that this Vm has "Medium" service offering Id.

6 3.Change Service of this Vm to use "Medium" service offr 4.Start VM Change Service to use more CPU and Memory 1.Deploy VM using default template, "Medium' service offering and small data disk offering. 1.Log in to the Vm.We should see that the CPU and memory Info of this Vm matches the one specified for "Medium" service offering. 2.Stop VM 2. Using listvm command verify that this Vm has "small" service offering Id. 3.Change Service of this Vm to use "Small" service offering. 4.Start VM SSVM CPVM VR Life cycle Stop SSVM CPVM VR Stop SSVM VR that is in "Running" State. [we should flesh out the steps here starting with 'deploy a vm' start SSVM CPVM VR Destroy SSVM CPVM VR Restore SSVM CPVM VR Destroy SSVM CPVM VR (Expunged) Reboot SSVM CPVM VR Start an existing VM that is in "Stopped" State. Destroy an existing VM that is in "Running" State. Restore a VM instance that is in "Destroyed" state. Destroy an existing VM that is in "Running" State. Wait for the Expunge Interval (expunge.delay). 1.Deploy VM. 2.Reboot VM. 1. Should Not be able to login to the VM. should be "Stopped". "Stopped" 1. Should be able to login to the VM. should be "Running". "Running" 1. Should not be able to login to the VM. should be "Destroyed". "Destroyed" 1. listvm command should should be "Stopped". 2. We should be able to Start this VM successfully. "Destroyed" 1. listvm command should NOT return this VM any more. 2. DB check : 1. VM_INSTANCE table - state should be "Expunging". 2. No entries relating to this VM in the NICS table. 3. No entries relating to this VM in the VOLUMES table. 4. Make sure volumes get removed from the Primary Storage. New SSVM CPVM are created 1. Should be able to login to the VM. return the deployed VM. State of this VM should be "Running". Migrate SSVM CPVM VR 1.Deploy VM. 1. Should be able to login to the VM. 2.Check to make sure you are able to log in to this VM. 3.Migrate vm to another host in the same cluster. should be "Running" and the host should be the host to which the VM was migrated to. VM live migration

7 1 Vcenter C PP 4.2 H1 zone1 - C1 - H1 VM Migrate H1 to vice versa VM Migrate H1 to H3 vice versa VM Migrate H1 to H4 vice versa successful H3 PS1 cluster primary C2 - C2 - H3 H4 DC2 - C3 - zone2 - C3 - H4 ZPS5 zone primary 2 Vcenter C PP 4.2 H1 zone1 - C1 - H1 VM Migrate H1 to vice versa VM Migrate H1 to H3 vice versa VM Migrate H1 to H4 vice versa successful H3 PS1 cluster primary C2 - C2 - H3 VC2 - DC3 - C4 - H4 zone2 - C4 - H4 ZPS5 zone primary clusters in different subnet Storage volume Attaching Volumes 1.navigate to Storage-volumes 1.shows list of volumes 2.select the detached data disk 3.click on "Actions" and select "Attach Disk" to attach to a particular instace 4. select the instance and click "Ok" button to attach the disk to selected instance in the "Attach Disk" pop-up window 3."Attach Disk" pop-up box will display with list of instances 4. disk should be attached to instance successfully and both UI and database(volumes table) should reflect the changes ( i.e attached disk details should be updated with attached vm_instance ID and device id ) Detaching Volumes 1.navigate to Storage-volumes data disk should be detached from instance and detached data disk details should be updated properly(i.e Instance Name -detached and Device ID is null) 2. selected the data disk which is attached to instance 3.click "Actions" and select the "Detach Disk" Download volumes 1.navigate to Storage-volumes 3. download volume will fail with proper error message "Failed - Invalid state of the volume with ID:. It should be either detached or the VM should be in stopped state" 2. selected the data disk which is attached to instance [some fundamental steps here are missing. in each os after attaching disk, you need to format and mount it before writing to it. downloading a blank volume would probably fail 3.perform download volume. 5. able to download the volume when its not attached to instace

8 4.select another data disk with is not attahced instance 5.perform "download volume " Delete Volumes case 1 case 1: 1.navigate to Storage-volumes volume should be deleted successfully and listvolume should not contain the deleted volume details. 2. selected the data disk 3.click on 'Actions" menu and select the "Delete volume" Case 2: "Delete Volume" menu item not shown under "Actions" menu. case 2 (UI should not allow to delete the volume when it is attahced to instance by hiding the menu Item) 4.select another data disk with is attahced instance 5.clcik on "Actions" menu and check for "Delete Volume" Create Volume 1. Perform "Add volume" by provinding name, availability zone and disk offering details.(i. e go to Storage-Volumes-) volume should be created successfully and listvolumes should contain the created volumes. Database should reflects with new created volume details (volumes table) [we shoudl execute this against every size, sanity check against that but also a few custom sized disk offerings] Upload a data disk call upload volume API with following parameters Upload volume is successful HTTP URL of the data disk, Zone ID, Name, Description, Hyper visor Attach a uploaded data disk call attach volume api with following parameter Verify Attach Volume API will move (and not Copy) the volume from secondary to primary and attach to the vm. Volumeid VM snapshot Create VMSnapshot of Vm in "Stopped" state with root volume with "vm_snapshot_type" set to "Disk" 1. Deploy Vm. 2. Log in to the Vm and create few directories and files. 3. Stop the VM. 4. Create VMSnapshot for this VM with "vm_snapshot_type" set to "Disk" Snapshot should get created successfully. It should be stored in the Primary Storage. /browse/cloudstack-4458 Create VMSnapshot of Vm in "Stopped" state with 1 data disk with "vm_snapshot_type" set to "Disk" 1. Deploy Vm. Attach a data disk to this VM. 2. Log in to the Vm and create few directories and files on the root volume. Create few more directories on the data disk. 3. Stop the VM. 4. Create VMSnapshot for this VM with "vm_snapshot_type" set to "Disk" Snapshot should get created successfully. It should be stored in the Primary Storage. /browse/cloudstack-4458 We should be allowed to initiate Snapshots for multiple Vms in parallel 1. Deploy few Vms. 2. Log in to the each of the Vms and create few directories and files. 3. Create VMSnapshot for all VMs at the same time. Vm Snapshot process for all the Vms should happen in parallel. /browse/cloudstack-4458 We should be abe to revert multiple Vms to different snapshots in parallel 1. Deploy few Vms. 2. Create Vm snapshots for all the Vms. 3. Revert all the above Vms to a snapshot of these Vms in parallel Vm reverts for all the Vms should happen in parallel.

9 2. Create volume from snapshot 3. Create template from snapshot Storage Migration 1 Vcenter C PP 4.2 H1 zone1 - C1 - H1 Migrate PS1 to vice versa Migrate PS1 to vice versa Migrate PS1 to vice versa successful H3 PS1 cluster primary C2 - C2 - H3 H4 DC2 - C3 - zone2 - C3 - H4 ZPS5 zone primary 2 Vcenter C PP 4.2 H1 zone1 - C1 - H1 Migrate PS1 to vice versa Migrate PS1 to vice versa Migrate PS1 to vice versa successful H3 PS1 cluster primary C2 - C2 - H3 VC2 - DC3 - C4 - H4 zone2 - C4 - H4 ZPS5 zone primary clusters in different subnet 15 Migrate volume when VM is running Use MigrateVirtualMachine() with VMId, SPId, when VM is in Running state Should throw appropriate error. Storage migration can happen only if the Vm is in Stopped state. Storage Migration Negative Scenarios CASE I : start VM migration. When the Volume migration is still in progress,restart the management server. Vm migration should fail. There should be a roll back done. Vm state should get back to" Stopped" and volumes should get back to "Ready" state. Attempt to start the VM should succeed using the existing (older). CASE II : start VM migration. When the Volume migration is still in progress, shutdown host which is doing the migration. Vm migration should fail. There should be a roll back done. Vm state should get back to" Stopped" and volumes should get back to "Ready" state Attempt to start the VM should succeed using the existing (older). CASE III : start VM migration. When the Volume migration is still in progress, reboot host which is doing the migration. Vm migration should fail. There should be a roll back done. Vm state should get back to" Stopped" and volumes should get back to "Ready" state Attempt to start the VM should succeed using the existing (older). CASE IV : migrate vm to a pool which belongs to a cluster of different hypervisor type The migration should fail with appropriate error message. Host

10 Force reconnect Host() Force reconnect Host() UpdateHost() - Edit host tags UpdateHost() - Edit host tags deletehost() - > Put the host in maintenance then delete the host Put the host in maintenance mode Put host in maintenance mode bring host out of maintenance mode deletehost() - > Put the host in maintenance and then delete the host Put the host in maintenance mode Put host in maintenance mode. Cancel host maintenance mode. Power down host Power down host Power down host and the power on the host Power down host and the power on the host Reboot host Reboot host Bring down the network connectivity of the host. Bringdown network connectivity of host. Bringup nw connectivity, Bring down the network connectivity of the host. Bring down network connectivity of host. Bring up network connectivity /browse/cloudstack /browse/cloudstack-4513 Template add template 1. Add public/private template 1.database (vm_template table) should be updated with newly created template 2. check UI/ listtemplates command to see the newly added template. 2.UI should show the newly added template 3.listtemplates API should show the newly added template delete template Delete Template: 1.listtemplates should not show the delted template 1.delete a template using UI/ API 2.database should be updated. 3. tempalte should not be displayed in admin UI. 4. template should be removed from secondary store (if no VMs were deployed with it) after.cleanup. interval Edit template Edit Template: 1.data base should be updated with updated values 1. edit the template attribute 2.UI should show the updated template attributes 2. check the updated values are relfecte 3.listTemplate shoud show the template with updated values Download template "1. Add public/private template "1. download template should generate a valid http link to download Check admin can extract any template Check all public templates should be visible to the users and admins check all the system VM templates are not visble to users 2. select the template and click ""Actions"" 3. perform ""Download Template"" admin should able extract and download the templates listtemplates should display all the public templates for all kind of users Listtemplate should not display the system templates" 2. You should be able to download the template with out any issues (no 404, 530, 503 HTTP Errors)" Copy template to other zone Copy template to other zone successful Start a VM from template Start a VM from template successful Download template with isolated network 1.Bring up CS in advanced zone 2.create zone->pod- >cluster>host Verify that SSVM downloads the guest OS templates from server which is in isolated network. Use below sql query to verify the download status of the template.

11 3.Primary and secondary on server in isolated network (Only management network has the reachability to server, public network does not have the reachability) mysql> select * from template_host_ref; 4.Disable zone 5.Set global settings parameter "sec.allowed.internal. sites" to server subnet 6.Restart management server 7.Enable zone ISO verify add ISO 1. Add public/private ISO 1.database (vm_template table) should be updated with newly created ISO 2. check UI/ listiso command to see the newly added template. 2.UI should show the newly added ISO 3.listISos API should show the newly added templat verify delete ISO 1.delete a template using UI/ API 1.listIsos should not show the delted template 2.database should be updated. 3.ISO should not be displayed in admin UI. 4. ISO should be removed from secondary store (if no VMs were deployed with it) after.cleanup.interval Verify Edit ISO 1. edit the ISO attribute 1.data base should be updated with updated values 2. check the updated values are relfected 2.UI should show the updated ISO attributes 3.listISos shoud show the template with updated value Download ISO 1. Add public/private ISO 1. download template should generate the link to download and able to download the template with out any issues 2. select the ISO and click "Actions" :check the ssvm in /var/www /html/userdata 3. perform "Download Template" Copy ISO to other zone 1. perform copy ISO from one zone to another zone copy ISO should be successful and seconday should contain new copied ISO 2.check the newly copied template in another zone primary Add Primary NFS cluster wide Use createstoragepool with url, name, podid, clusterid Primary should be created and should be in Up state Delete Primary NFS Delete Primary NFS Delete successful Storage maintenance mode with one pool Storage maintenance mode with multiple pools Storage maintenance mode cancel Storage maintenance mode cancel Initiate maintenance mode for primary Storage pool VMs and System VMs stopped, Volumes should not be destroyed (no additional pool present) Initiate maintenance mode for Primary with additional pools Cancel maintenance mode (one pool) Cancel maintenance mode (multiple pools) User VMs should be stopped. System VMs should be restarted in another pool User VMs that were stopped should restart and also the system VMs User VMs that were stopped should restart

12 Enable maintenance with local Create VMs when Maintenance mode is on Storage Tags Enable local for System VM and User Vm Put Local in maintenance mode Create User VMs when pools are in maintenance mode Create Storage tag for and use the tag for disk offering User and System VMs should be stopped and restarted when maintenance mode is disabled (?) Should not be able to create VMs and appropriate message should be thrown Should deploy disk on the which matches the tag primary zone wide secondary Add NFS Secondary Seed System VM templates Secondary should get added to the zone. Use addsecondarystorage with url, host listhosts should should show up the added sec as type "secondary" listsystemvm should show up system vms once they are up and running listtemplates should show default templates downloaded and and in Ready state Change Sec Storage server Stop cloud services Sec should be back up Copy files from old to new secondary Change IP in DB in host and host_details Start services Stop and start SSVM Should be able to take snapshots and create templates PVLAN Shared Network scope All 1 PVLAN Deploy VM 1. Advance zone cluster with 2 hosts, Domain D1 domainadmin d1domain, user d1user. Domain D2 user d2user. 2. Create Shared NW1 scope All <pvlan1, svlan1>. 3. As users from different domains, deploy Vms in this network, 1. shared NW1 with pvlan creation succeed. 2. All accounts able to create VMs on NW1. 3.All VMs in NW1 unable to access each other All VMs in NW1 able to reach DHCP server, gateway Shared NW scope Domain 1 PVLAN Deploy VM 1. Advance zone cluster with 2 hosts, Domain D1 domainadmin d1domain, user d1user. Domain D2 user d2user. 2. Create Shared NW1 scope Domain for D1 <pvlan1, svlan1>. 3. As users from different domains, deploy Vms in this network, 1. shared NW1 with pvlan creation succeed. 2. Only accounts from doamin d1 are allowed to create VMs on NW1. 3.All VMs in NW1 unable to access each other All VMs in NW1 able to reach DHCP server, gateway UPGRADE

13 > campo 4.2. Deployment- multiple zones, cluster single DC VC DC cluster host CP vc1 a1 c1 h1 zone 1 h2 after upgrade - VC - add cluster c2 to vc1 a1 : VC DC cluster host CP vc1 a1 c1 h1 zone 1 pod 1 c1 h1 h2 h2 PS1 c2 h4 pod 2 c2 h4 ZPS5 2 Legacy Vcenter Legacy CPP 4.2 H1 zone1 - cluster1 H vmware setup Deployment- multiple zones, cluster single DC deploy VM, assign public IP to VM ensure internet access 2. upgrade campo 4.2 add cluster c2 to Vcenter. add pod2 cluster c2 host h4 to zone1 add cluster PS Legacy CPP Patch B- advance zone 1 Vcenter 2 DC with multiple clusters upgrade campo 4.2 New mapping Vcenter & CPP should work 1. legacy has single DC New mapping Vcenter & CPP NOT allowed PS1 cluster primary DC2 - C2 - H3 cluster2 V C1 - DC2 - C2 - H3 DC3 - C3 - H4 cluster3 V C1 - DC3 - C3 - H4 ZPS5 zone primary 2. upgrade campo 4.2 add to current zone: Vcenter1 - DC1 - cluster1 - Host1 cluster2 - Host2 DC2 - cluster3 - Host3 Vcenter2 - DC3 - cluster4 - Host4 clusters in different subnet 3 Vcenter C PP 4.2 H1 zone1 - cluster1 H1 PS1 DC2 - C2 - H3 cluster2 V C1 - DC2 - C2 - H3 VC2 - DC3 - C4 - H4 cluster3 V C2 - DC3 - C4 - H4 Legacy CPP Patch B - advance zone multiple Vcenters 2 DC multiple clusters different subnet upgrade campo 4.2 New mapping Vcenter & CPP NOT allowed ZPS5 zone primary clusters in different subnet 4 Before upgrade Zone with mixed hypervisors -- Later add additional clusters VMWARE or any other Legacy CPP 4.0 advance zone multiple Vcenters 2 DC multiple clusters different subnet upgrade campo 4.2

14 5 Before Upgrade Nexus vswitch 6 Before Upgrade DVS 2 physical networks after upgrade add dvs Cluster 7 Before Upgrade DVS 2 physical networks after upgrade add Nexus Cluster 8 Test upgrade to new product (with this feature) when the deployment already has multiple zones, where clusters in each zone has one or more of following, 1. Single DC 2. Multiple DCs 3. Multiple vcenters 9 After upgrade, test adding new cluster to existing/new zone, where the cluster belongs to a DC /vcenter that is, 1. Already part of zone 2. Not part of zone after upgrade of new zone Test creation