| | Isolation Advance zone using PVLANs | | | | | | | |
| | hardware requirement: Cisco Catalyst 4500 software requirement Hypervisor/software switch: Xen /openvswitch KVM/openvswitch vmware/NEXUS vswitch vmware/DVS | | | | | | | |
| | isolation within a shared network VMs deployed using multiple shared networks | | | | | | | |
| | primary VLAN ( pVLAN) - promiscuous ports secondary VLAN (sVLAN) - isolated ports | | | | | | | |
| | | | | | | | | |
| | isolated PVLAN promiscuous PVLAN community PVLAN - unsupported | | | | | | | |
| | External Device unsupported | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
Testcase ID | Test case name | Steps | Expected Results. | Priority | XEN | KVM CentOS 6.3 | KVM Ubuntu 13.04 | VMWARE DVS | VMWARE Nexus vswitch 1000 |
| Shared Network 1 PVLAN | | | | | | | | |
1 | 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. Create Shared NW1 scope All <pVLAN1, sVLAN1>. 2. d1domain deploy VM1 on NW1 on host1 , VM4 on NW1 on host2. d1user deploy VM2 on NW1 on host1, VM5 on NW1 on host2. d2user deploy VM3 on NW1 on host1, VM6 on NW1 on host2. | 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 | P1 | Pass | | | | |
2 | 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. Create Shared NW1 scope Domain for D1 <pVLAN1, sVLAN1>. 2. d1domain deploy VM1 on NW1 on host1 , VM4 on NW1 on host2. d1user deploy VM2 on NW1 on host1, VM5 on NW1 on host2. d2user try deploy VM3 on NW1 on host1, VM6 on NW1 on host2. | 1. shared NW1 with pVLAN creation succeed.
2. All accounts able to create VMs on NW1.d1domain & d1user able to create VMs on NW1. d2user unable 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 | P1 | | | | | |
3 | Shared NW scope Domain subdomain access TRUE 1 PVLAN Deploy VM | 1. Advance zone cluster with 2 hosts, Domain D1 domainadmin d1domain, user d1user. Domain D1/D11 domainadmin d11domain. Domain D2 user d2user.
2. Create Shared NW1 scope Domain for D1 subdomain access TRUE <pVLAN1, sVLAN1>.
3. As users from different domains , deploy Vms in this network,
d1domain deploy VM1 on NW1 on host1 , VM4 on NW1 on host2. d1user deploy VM2 on NW1 on host1, VM5 on NW1 on host2. d11domain deploy VM3 on NW1 on host1, VM6 on NW1 on host2. d2user try deploy VM7 on NW1 on host1, VM8 on NW1 on host2. | 1. shared NW1 with pVLAN creation succeed.
2. Only accounts from doamin d1 and subdomains under this domain are allowed to create VMs on NW1.d1domain, d1user, d11domain able to create VMs on NW1. d2user unable 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 | P1 | | | | | |
4 | Shared NW scope Account 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 Account for d1domainA <pVLAN1, sVLAN1>.
3. As users from different domains , deploy Vms in this network, d1domain deploy VM1 on NW1 on host1 , VM4 on NW1 on host2. d1user try deploy VM2 on NW1 on host1, VM5 on NW1 on host2. d2user try deploy VM3 on NW1 on host1, VM6 on NW1 on host2. | 1. shared NW1 with pVLAN creation succeed.
2. d1domainA able to create VMs on NW1. d1user d2user unable 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 | P1 | | | | | |
5 | Shared NW scope Project 1 PVLAN Deploy VM | 1. Advance zone cluster with 2 hosts, Project P1 w/ account A1 A2 Project P2 w/account B1 B2
2. Create Shared NW1 scope Project for P1 <pVLAN1, sVLAN1>.
3. As users from different projects , deploy Vms in this network,
A1 user deploy VM1 on NW1 on host1 , VM5 on NW1 on host2. A2 user deploy VM2 on NW1 on host1, VM6 on NW1 on host2. B1 user try deploy VM3 on NW1 on host1, VM7 on NW1 on host2. B2 user try deploy VM4 on NW1 on host1, VM8 on NW1 on host2. | 1. shared NW1 with pVLAN creation succeed.
2. A1 user A2 user able to create VMs on NW1. B1 user B2 user unable 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 | P1 | | | | | |
6 | Multiple shared NW scope zone using different PVLANs Deploy VM | 1. Advance zone cluster with 2 hosts, Domain D1 domainadmin d1domain, user d1user. Domain D2 user d2user.
2. Create multiple shared pvlan enabled networks.
Create Shared NW1 scope zone <pVLAN1, sVLAN1>. Create Shared NW2 scope zone <pVLAN2, sVLAN2>. Create Shared NW3 scope zone <pVLAN3, sVLAN3>. Create Shared NW4 scope zone <pVLAN4, sVLAN4>.
3. Make sure we are able to deploy multiple vms successfully in both the networks.
d1domain deploy VM1 on NW1 on host1 , VM4 on NW2 on host2, VM8 on NW3 on host1, VM12 on NW4 on host2 d1user deploy VM2 on NW1 on host1, VM5 on NW2 on host2, VM9 on NW3 on host1, VM13 on NW4 on host2. d2user deploy VM3 on NW1 on host1, VM6 on NW2 on host2, VM10 on NW4 on host1, VM14 on NW4 on host2. | With 1 network,
All VMs in NW1 unable to access each other All VMs in NW1 able to reach DHCP server, gateway
Vm can access Vms from other shared networks.
. shared NW1 NW2 NW3 NW4 with different pVLANs creation succeed. 2. All users able to create VMs on shared NW1 NW2 NW3 NW4 All VMs in each shared NW unable to access each other All VMs among all shared NWs unable to access each other All VMs in in each shared NW able to reach DHCP server, gateway | P1 | Pass | | | | |
7 | Shared NW using PVLAN associated with another shared NW | 1. Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Create Shared NW2 scope zone <pVLAN2, sVLAN1>. | shared NW2 creation FAIL | Fail
CLOUDSTACK-2396 | | | | | |
8 | Shared NW using the same VLAN associated with different PVLANs. | 1. Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Create Shared NW2 scope zone <pVLAN1, sVLAN2>. | shared NW2 creation FAIL | | | | | | |
9 | | Shared NW using PVLAN associated with ZONE VLAN | | | 1. Create Shared NW1 scope zone using ZONE VLAN | shared NW1 creation FAIL | | | shared NW1 creation FAIL | | | | | | | | 10 | |
10 | Should not be allowed to pass isolatedpvlan parameter when creating a isolated network. | | | 1. Try to create a isolated network by passing isolatedpvlan parameter | Network creation should fail | | | Network creation should fail | | | | | | | | 11 | |
11 | Should not be allowed to pass isolatedpvlan parameter when creating a ipv6 enabled network. | | | 1. Try to create a ipv6 enabled shared network by passing isolatedpvlan parameter | Network creation should fail | | | | | Network creation should fail | | | | | | | |
| ListCommand changes | | | | | | | | |
12 | listVirtualMachines() should return PVLAN related parameters | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy Vm in this network.
3. List Vm details using listVirtualMachines() | listVirtualMachines() should return PVLAN related parameters
"isolationuri":"vlan://1611,"broadcasturi":"pvlan://1611-i998" | P1 | | | | | |
13 | listRouters() should return PVLAN related parameters | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy Vm in this network.
3. List router details using listRouters() | listRouters() should return PVLAN related parameters
"isolationuri":"vlan://1611,"broadcasturi":"pvlan://1611-i998" | P1 | | | | | |
14 | listNetworks() should return PVLAN related parameters | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy Vm in this network.
3. List network details using listNetworks() | listNetworks() should return PVLAN related parameters
"broadcasturi":"pvlan://1611-i998" | P1 | | | | | |
15 | listVlanIpranges() should return PVLAN related parameters | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy Vm in this network.
3. List VLAN details using listVlanIpranges() | listVlanIpranges() should return PVLAN related parameters
only Vlan entry is returned | P1 | | | | | |
| | | | | | | | | |
| Vm States | | | | | | | | |
16 | | Deploy Vm in a shared Network that is created by providing secondary Vlan. - User Vm check | | | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy multiple Vms in this network . | | | Vm should be deployed successfully.
For every Vm deployed following 2 entries should be created in the host:
ovs-ofctl dump-flows xenbr0
1. cookie=0x0, duration=306.296s, table=0, n_packets=51, n_bytes=7536, priority=60,dl_vlan=998,dl_src=06:07:c2:00:00:26 actions=output:1
2. cookie=0x0, duration=306.3s, table=0, n_packets=51, n_bytes=7536, priority=50,vlan_tci=0x0000,dl_src=06:07:c2:00:00:26 actions=mod_vlan_vid:998,resubmit:1
Vms should NOT be able to communicate with each other. | | .
| | | | | | | | 17 | | |
17 | Deploy Vm Deploy Vm in a shared Network that is created by providing secondary Vlan. - Router Check | | | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy Vm in this network. | | | Vm should be deployed successfully.
For every router created following 3 entries should be created in the host:
ovs-ofctl dump-flows xenbr0
1. cookie=0x0, duration=3503.373s, table=0, n_packets=8, n_bytes=2748, priority=100,udp,dl_vlan=998,nw_dst=255.255.255.255,tp_dst=67 actions=strip_vlan,output:18
2. cookie=0x0, duration=3503.38s, table=0, n_packets=20, n_bytes=1148, priority=200,arp,dl_vlan=998,nw_dst=10.223.161.110 actions=strip_vlan,output:18
3.cookie=0x0, duration=3503.376s, 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
Vm should be able to go out successfully.
Vm should be able to communicate with the router successfully. | | | | | | | | | | | | |
18 | Stop Vm | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy Vm in this network.
3. Stop VM. | Vm should be stopped successfully.
Following 2 entries of the Vm should get removed from the host:
ovs-ofctl dump-flows xenbr0
1. cookie=0x0, duration=306.296s, table=0, n_packets=51, n_bytes=7536, priority=60,dl_vlan=998,dl_src=06:07:c2:00:00:26 actions=output:1
2. cookie=0x0, duration=306.3s, table=0, n_packets=51, n_bytes=7536, priority=50,vlan_tci=0x0000,dl_src=06:07:c2:00:00:26 actions=mod_vlan_vid:998,resubmit:1 | | | P1 | | | | | |
19 | Start Vm that is in stopped state | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Stop VM.
4. Start VM. | | Vm should be stopped and started successfully.
For every Vm deployed following 2 entries should be removed when stopping the Vm and get added back when the Vm is started in the host:
ovs-ofctl dump-flows xenbr0
1. cookie=0x0, duration=306.296s, table=0, n_packets=51, n_bytes=7536, priority=60,dl_vlan=998,dl_src=06:07:c2:00:00:26 actions=output:1
2. cookie=0x0, duration=306.3s, table=0, n_packets=51, n_bytes=7536, priority=50,vlan_tci=0x0000,dl_src=06:07:c2:00:00:26 actions=mod_vlan_vid:998,resubmit:1
All VMs in NW1 unable to access each other.
All VMs in NW1 able to reach DHCP server, gateway | | | P1 | | | | | |
20 | reboot Vm | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>. 2. Deploy few Vms in this network. 3. Reboot VM. | Vm should be stopped & destroyed successfully.
Following 2 entries of the Vm should get removed from the host:
ovs-ofctl dump-flows xenbr0
1. cookie=0x0, duration=306.296s, table=0, n_packets=51, n_bytes=7536, priority=60,dl_vlan=998,dl_src=06:07:c2:00:00:26 actions=output:1
2. cookie=0x0, duration=306.3s, table=0, n_packets=51, n_bytes=7536, priority=50,vlan_tci=0x0000,dl_src=06:07:c2:00:00:26 actions=mod_vlan_vid:998,resubmit:1 | | | P1 | | | | | |
21 | Destroy Vm | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Destroy VM. | | Vm should be stopped & destroyed successfully.
Following 2 entries of the Vm should get removed from the host:
ovs-ofctl dump-flows xenbr0
1. cookie=0x0, duration=306.296s, table=0, n_packets=51, n_bytes=7536, priority=60,dl_vlan=998,dl_src=06:07:c2:00:00:26 actions=output:1
2. cookie=0x0, duration=306.3s, table=0, n_packets=51, n_bytes=7536, priority=50,vlan_tci=0x0000,dl_src=06:07:c2:00:00:26 actions=mod_vlan_vid:998,resubmit:1 | | | P1 | | | | | |
21 | Restore Vm that is destroyed | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Destroy VM.
4. Even before the expunge interval is passed , restore the VM.
5. Once the Vm is in stopped state , Start this VM. | | After Vm is restored, Vm should be in Running state.
All VMs in NW1 unable to access each other
All VMs in NW1 able to reach DHCP server, gateway
Following 2 entries of the Vm should get created in the host:
ovs-ofctl dump-flows xenbr0
1. cookie=0x0, duration=306.296s, table=0, n_packets=51, n_bytes=7536, priority=60,dl_vlan=998,dl_src=06:07:c2:00:00:26 actions=output:1
2. cookie=0x0, duration=306.3s, table=0, n_packets=51, n_bytes=7536, priority=50,vlan_tci=0x0000,dl_src=06:07:c2:00:00:26 actions=mod_vlan_vid:998,resubmit:1 | | | P1 | | | | | |
22 | Expunge Vm that is destroyed | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Destroy VM.
4. Wait for the Expunge interval to pass. | Vm should be Expunged successfully.
DNS entry of this Vm should be removed from the router. | P1 | | | | | |
23 | | Expunge Vm that is destroyed and deploy a Vm using the same Ip address as the expunged Vm. | | | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Destroy VM.
4. Wait for the Expunge interval to pass.
5. Deploy a Vm using the same Ip address as the expunged Vm | | | Vm deployment shoud succeed.
As part of this VM deployment, router's /etc/dhcphost entry for the expunged Vm gets deleted and the entry pertaining to the new Vm is created.
Following 2 entries of the Vm should get created in the host:
ovs-ofctl dump-flows xenbr0
1xenbr01. cookie=0x0, duration=306.296s, table=0, n_packets=51, n_bytes=7536, priority=60,dl_vlan=998,dl_src=06:07:c2:00:00:26 actions=output:1
2. cookie=0x0, duration=306.3s, table=0, n_packets=51, n_bytes=7536, priority=50,vlan_tci=0x0000,dl_src=06:07:c2:00:00:26 actions=mod_vlan_vid:998,resubmit:1 | | | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Destroy VM.
4. Wait for the Expunge interval to pass.
5. Deploy a Vm using the same Ip address as the expunged Vm | | | | | | | | | Vm deployment shoud succeed.
As part of this VM deployment, router's /etc/dhcphost entry for the expunged Vm gets deleted and the entry pertaining to the new Vm is created.
Following 2 entries of the Vm should get created in the host:
ovs-ofctl dump-flows xenbr0
1. cookie=0x0, duration=306.296s, table=0, n_packets=51, n_bytes=7536, priority=60,dl_vlan=998,dl_src=06:07:c2:00:00:26 actions=output:1
2. cookie=0x0, duration=306.3s, table=0, n_packets=51, n_bytes=7536, priority=50,vlan_tci=0x0000,dl_src=06:07:c2:00:00:26 actions=mod_vlan_vid:998,resubmit:1 | | | | | | | | 24 | |
24 | From user Vm , we should be able to fetch metadata of the VM. | | | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3.From with in the Vm , fetch metadata of the VM. | | | From user Vm , we should be able to fetch metadata of the VM. | | | | | | | | | | | 25 | |
25 | From user Vm , we should be able to fetch userdata of the VM. | | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy Vms in this network by passing userdata.
3.From with in the Vm , fetch userdata of the VM. | | | From user Vm , we should be able to fetch metadata of the VM. | | | | | | | | | | | | |
| Vms being part of same shared network and different isolated network | | | | | | | | | | |
26 | | Vm being part of isolated network and shared network | | | 1. Create a shared network with pvlan – SN1.
2. As account1 , create isolated network N1.
3. As account2 , create isolated network N2.
4. As account1 - Deploy vms - VM1, VM2 in N1 (default) and SN1.
5. As account2 - Deploy vms – VM3, VM4 in N2 (default) and SN1. | | | From VM1 , make sure you are not able to access VM2, VM3 and VM4 using the Ip-address that is assigned to it shared network SN1 | | | | | . | | | | | | | |
27 | Stop and start Vms that are part of isolated and shared network | | Pre Req:
1. Create a shared network with pvlan – SN1.
2. As account1 , create isolated network N1.
3. As account2 , create isolated network N2.
4. As account1 - Deploy vms - VM1, VM2 in N1 (default) and SN1.
5. As account2 - Deploy vms – VM3, VM4 in N2 (default) and SN1.
Steps:
Stop and start Vms | | | From VM1 , make sure you are not able to access VM2, VM3 and VM4 using the Ip-address that is assigned to it shared network SN1. | | | | | | | | | | | 28 | |
28 | Reboot Vms that are part of isolated and shared network | | | Pre Req:
1. Create a shared network with pvlan – SN1.
2. As account1 , create isolated network N1.
3. As account2 , create isolated network N2.
4. As account1 - Deploy vms - VM1, VM2 in N1 (default) and SN1.
5. As account2 - Deploy vms – VM3, VM4 in N2 (default) and SN1.
Steps:
Reboot Vms | | | From VM1 , make sure you are not able to access VM2, VM3 and VM4 using the Ip-address that is assigned to it shared network SN1. | | | | | | | | | | | 29 | |
29 | Vm being part of isolated network and shared network.
Have another machine in the same shared network connected to promiscuous port. | | | Pre Req:
1. Create a shared network with pvlan – SN1.
2. As account1 , create isolated network N1.
3. As account2 , create isolated network N2.
4. As account1 - Deploy vms - VM1, VM2 in N1 (default) and SN1.
5. As account2 - Deploy vms – VM3, VM4 in N2 (default) and SN1.
Steps:
Have another machine in the same shared network connected to promiscuous port. | | | From VM1 , make sure you are not able to access VM2, VM3 and VM4 using the Ip-address that is assigned to it shared network SN1.
From the machine that was added in promiscuous mode , we should be able to reach all the Vms using their Shared network Ipaddress.
From the Vms , we should be able to access this machine | | | | | | | | | | | | |
| | | | | | | | | |
| Network States | | | | | | | | |
30 | Extend Iprange of the network | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Consume all ips in range
4. Extend Ip range.
5. Deploy Vm in this network. | Vm deployment should succeed.
Vm should be assigned address from the extended range.
All VMs in NW1 unable to access each other
All VMs in NW1 able to reach DHCP server, gateway | P2 | | | | | |
31 | Restart network | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Restart Network. | 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. | P2 | | | | | |
32 | Restart network with cleanup option | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
4. Restart Network with cleanup option. | | 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 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 xenbr0
1xenbr01. cookie=0x0, duration=3503.373s, table=0, n_packets=8, n_bytes=2748, priority=100,udp,dl_vlan=998,nw_dst=255.255.255.255,tp_dst=67 actions=strip_vlan,output:18
2182. cookie=0x0, duration=3503.38s, table=0, n_packets=20, n_bytes=1148, priority=200,arp,dl_vlan=998,nw_dst=10.223.161.110 actions=strip_vlan,output:18
3183.cookie=0x0, duration=3503.376s, 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 | | | P2 | | | | | |
33 | Delete network with vms in "Running" state | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network
3. Delete Network. | Network Deletion should fail. | P2 | | | | | |
34 | Delete network when there are no Vms associated with it. | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Destroy all the Vms.
4. Delete Network after all the Vms are expunged. | Network Deletion should succeed. | P2 | | | | | |
35 | Stop all Vms in network and wait for network shutdown | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Stop all the Vms.
4. Wait for network scavenger thread to run. | Network should not be picked up for Shutting down. | P2 |
N/A
|
Network scavenger thread does not destroy shared networks that have no Vms to service. | | | | | |
| | | | | | | | | |
| Router States | | | | | | | | |
36 | Stop Router | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3.Stop Router | Router should get stopped successfully.
All VMs in NW1 unable to access each other.
All VMs in NW1 UNable to reach DHCP server. But should be able to reach gateway and reach out.
Following 3 entries for the router should get deleted from the host:
ovs-ofctl dump-flows xenbr0
1xenbr01. cookie=0x0, duration=3503.373s, table=0, n_packets=8, n_bytes=2748, priority=100,udp,dl_vlan=998,nw_dst=255.255.255.255,tp_dst=67 actions=strip_vlan,output:18
2182. cookie=0x0, duration=3503.38s, table=0, n_packets=20, n_bytes=1148, priority=200,arp,dl_vlan=998,nw_dst=10.223.161.110 actions=strip_vlan,output:18
3183.cookie=0x0, duration=3503.376s, 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
Deploying 18Deploying new Vm should result in the Router getting started.
New VM in NW1 unable to access other All VMs in NW1 but able to reach DHCP server, gateway | | | P2 | | | | | |
37 | stop-start Router | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3.Stop Router
4.Start Router | When Router is stopped: Router should get stopped successfully.
All VMs in NW1 unable to access each other
All other All VMs in NW1 able to reach DHCP server.But should be able to reach gateway and reach out.
Following 3 entries for the router should get deleted and created in the host when router is stopped and started:
ovs-ofctl dump-flows xenbr0
1xenbr01. cookie=0x0, duration=3503.373s, table=0, n_packets=8, n_bytes=2748, priority=100,udp,dl_vlan=998,nw_dst=255.255.255.255,tp_dst=67 actions=strip_vlan,output:18
2182. cookie=0x0, duration=3503.38s, table=0, n_packets=20, n_bytes=1148, priority=200,arp,dl_vlan=998,nw_dst=10.223.161.110 actions=strip_vlan,output:18
3183.cookie=0x0, duration=3503.376s, 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
After 18After Router is started:
Deploying new Vms should succeed | | | P2 | | | | | |
38 | Reboot Router | 1. Advance zone Create Shared NW1 scope zone <pVLAN1, sVLAN1>. 2. Deploy few Vms in this network. Steps: 3.Reboot Router | | Router should get stopped and started successfully.
After router is rebooted successfully , deploy a new Vm.
New VM in NW1 unable to access other All VMs in NW1 but able to reach DHCP server, gateway.
For all existing Vms in NW1:
Should not be able to access other all VMs in NW1 but able to reach DHCP server, gateway. | | | P2 | | | | | |
| | | | | | | | | |
| VM live migration | | | | | | | | |
39 | Host in maintenance mode | 1. Advance zone cluster with 2 hosts. Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. host1 Enable maintenance mode
4. host1 disable maintenance mode
5. host2 enable maintenance mode
6. host1 disable maintenance mode | 3. All VMs on Host1 migrate to Host2 All VMs in NW1 unable to access each other All VMs in NW1 able to reach DHCP server, gateway 5. All VMs on Host2 migrate to Host1 All VMs in NW1 unable to access each other All VMs in NW1 able to reach DHCP server, gateway | | | | | | |
40 | VM live migration for user VM | 1. Advance zone cluster with 2 hosts. Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Perform VM Manual live migration | | After live migration , Vm should still be reachable using its Ip address.
It should not be able to reach any other Vms in the network.
It should still be able to reach DHCP server, gateway.
All other Vms in the network , should not be able to reach this VM.
The following 2 rules should get cleaned up from the old host and be programmed in the new host.
ovs-ofctl dump-flows xenbr0
1xenbr01. cookie=0x0, duration=306.296s, table=0, n_packets=51, n_bytes=7536, priority=60,dl_vlan=998,dl_src=06:07:c2:00:00:26 actions=output:1
2. cookie=0x0, duration=306.3s, table=0, n_packets=51, n_bytes=7536, priority=50,vlan_tci=0x0000,dl_src=06:07:c2:00:00:26 actions=mod_vlan_vid:998,resubmit:1 | | | | | | | | |
41 | VM live migration for Router VM | | | 1. Advance zone cluster with 2 hosts. Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Perform VM Manual live migration for the router. | | | After live migration of router , Vm deployment should succeed.
New VM in NW1 unable to access other All VMs in NW1 but able to reach DHCP server, gateway.
For all existing Vms in NW1:
Should not be able to access other all VMs in NW1 but able to reach DHCP server, gateway.
Following 3 entries for the router should get deleted from the old host and re-created in the current host where the router is running:
ovs-ofctl dump-flows xenbr0
1xenbr01. cookie=0x0, duration=3503.373s, table=0, n_packets=8, n_bytes=2748, priority=100,udp,dl_vlan=998,nw_dst=255.255.255.255,tp_dst=67 actions=strip_vlan,output:18
2182. cookie=0x0, duration=3503.38s, table=0, n_packets=20, n_bytes=1148, priority=200,arp,dl_vlan=998,nw_dst=10.223.161.110 actions=strip_vlan,output:18
3183.cookie=0x0, duration=3503.376s, 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 | | | | | | | | 42 | | | | ha | |
42 | HA | 1. Advance zone cluster with 2 hosts. Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
2. Deploy few Vms in this network.
3. Perform VM Manual live migration for the router. | | After live migration of router , Vm deployment should succeed.
New VM in NW1 unable to access other All VMs in NW1 but able to reach DHCP server, gateway.
For all existing Vms in NW1:
Should not be able to access other all VMs in NW1 but able to reach DHCP server, gateway.
Following 3 entries for the router should get deleted from the old host and re-created in the current host where the router is running:
ovs-ofctl dump-flows xenbr0
1xenbr01. cookie=0x0, duration=3503.373s, table=0, n_packets=8, n_bytes=2748, priority=100,udp,dl_vlan=998,nw_dst=255.255.255.255,tp_dst=67 actions=strip_vlan,output:18
2182. cookie=0x0, duration=3503.38s, table=0, n_packets=20, n_bytes=1148, priority=200,arp,dl_vlan=998,nw_dst=10.223.161.110 actions=strip_vlan,output:18
3183.cookie=0x0, duration=3503.376s, 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 | | | | | | | | | | |
| Upgrade | | | | | | | | |
43 | On an Upgraded set up , make sure that we are able to create a network with secondary vlan and deploy Vms in this network. | | | 1. Deploy an earlier version of cloudstack in advanced zone.
Upgrade to this version.
2. Create Shared NW1 scope zone <pVLAN1, sVLAN1>.
3. Deploy multiple Vms in this network. | | | Vm should be deployed successfully.
For every Vm deployed following 2 entries should be created in the host:
ovs-ofctl dump-flows xenbr0
1xenbr01. cookie=0x0, duration=306.296s, table=0, n_packets=51, n_bytes=7536, priority=60,dl_vlan=998,dl_src=06:07:c2:00:00:26 actions=output:1
2. cookie=0x0, duration=306.3s, table=0, n_packets=51, n_bytes=7536, priority=50,vlan_tci=0x0000,dl_src=06:07:c2:00:00:26 actions=mod_vlan_vid:998,resubmit:1
Vms 1Vms should NOT be able to communicate with each other. | | | | | | | | | | | | |
| | | | | | | | | |
| Upgrade ASF 4.0 -> ASF 4.2 | | | | | | | | |
| | | | | | | | | |
| Upgrade ASF 4.1 -> ASF 4.2 | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
