andrijapanicsb commented on issue #3732: [Vmware] Enable PVLAN support on L2 networks URL: https://github.com/apache/cloudstack/pull/3732#issuecomment-583147095 TestID | Test Name | Steps | Expected Results | Status -- | -- | -- | -- | -- | Backward compatibility API syntax check | (API command expected to succeed) | | 1 | Create a promiscuous PVLAN setup using old API syntax (no 'isolatedpvlantype' parameter, but identical values for ‘vlan’ and ‘isolatedpvlan’ parameters) | Execute the ‘createNetwork’ API via CloudMonkey, using default ‘DefaultL2NetworkOfferingVlan’ and passing the PVLAN parameters as below: vlan=1050 isolatedpvlan=1050 | A network is created, and when attached to a running VM, the appropriate Port Group is created on dvSwitch1 | Passed 2 | Create an isolated PVLAN setup using old API syntax (no 'isolatedpvlantype' parameter, but different values for ‘vlan’ and ‘isolatedpvlan’ parameters) | … vlan=1050 isolatedpvlan=150 | A network is created, and when attached to a running VM, the appropriate Port Group is created on dvSwitch1 | Passed | Positive checks | (API command expected to succeed) | | 3 | Primary 1020, Isolated Secondary 1021 | … vlan=1020 isolatedpvlan=1021 isolatedpvlantype=isolated | A network is created, and when attached to a running VM, the appropriate Port Group is created on dvSwitch1 | Passed 4 | Primary 1020, Secondary Promiscuous (1020) | … vlan=1020 isolatedpvlan=1020 isolatedpvlantype=promiscuous | A network is created, and when attached to a running VM, the appropriate Port Group is created on dvSwitch1 | Passed 5 | Primary 1020, Secondary Community 1022 | … vlan=1020 isolatedpvlan=1022 isolatedpvlantype=community | A network is created, and when attached to a running VM, the appropriate Port Group is created on dvSwitch1 | Passed 6 | Create additional Secondary Community 1023, on the same Primary 1020 | … vlan=1020 isolatedpvlan=1023 isolatedpvlantype=community | A network is created, and when attached to a running VM, the appropriate Port Group is created on dvSwitch1 | Passed 7 | Create a promiscuous network without using ‘isolatedpvlan’ parameter | … vlan=1060 isolatedpvlantype=promiscuous | A network is created, and when attached to a running VM, the appropriate Port Group is created on dvSwitch1 | Passed | Negative checks | (API command expected to fail) | | Passed 8 | ‘isolatedpvlan’ parameter missing, while ‘isolatedpvlantype’ != promiscuous | … vlan=1070 isolatedpvlantype=isolated | API call should fail: Error: (HTTP 431, error code 4350) Private VLAN ID has not been set, therefore Promiscuous type is expected | Passed 9 | ‘isolatedpvlan’ parameter missing, while ‘isolatedpvlantype’ != promicuous | … vlan=1070 isolatedpvlantype=community | API call should fail: Error: (HTTP 431, error code 4350) Private VLAN ID has not been set, therefore Promiscuous type is expected | Passed 10 | Create identical PVLAN setup that already exist, Primary 1020 and Secondary Promiscuous (1020) | … vlan=1020 isolatedpvlan=1020 isolatedpvlantype=promiscuous | API call should fail: Error: (HTTP 431, error code 4350) Network with primary vlan 1020 and secondary vlan 1020 type Promiscuous already exists or overlaps with other network pvlans in zone 1 | Passed 11 | Create identical PVLAN setup that already exist, Primary 1020 and using Secondary Isolated 1022 (that is the value of an existing Secondary Community) | … vlan=1020 isolatedpvlan=1022 isolatedpvlantype=isolated | API call should fail: Error: (HTTP 431, error code 4350) Network with primary vlan 1020 and secondary vlan 1022 type Isolated already exists or overlaps with other network pvlans in zone 1 | Passed 12 | Create identical PVLAN setup that already exist, Primary 1020 and using identical Secondary Community (1022 or 1023) | … vlan=1020 isolatedpvlan=1023 isolatedpvlantype=community | API call should fail: Error: (HTTP 431, error code 4350) Network with primary vlan 1020 and secondary vlan 1023 type Community already exists or overlaps with other network pvlans in zone 1 | Passed 13 | Create identical PVLAN setup that already exist, Primary 1020 and using Secondary Community 1021 (that is the value of an existing Secondary Isolated) | … vlan=1020 isolatedpvlan=1021 isolatedpvlantype=community | API call should fail: Error: (HTTP 431, error code 4350) Network with primary vlan 1020 and secondary vlan 1021 type Community already exists or overlaps with other network pvlans in zone 1 | Passed 14 | Create "overlapping" PVLAN setup, using already used Primary 1020, but different/unique Secondary Isolated | … vlan=1020 isolatedpvlan=1033 isolatedpvlantype=isolated | API call should fail: Error: (HTTP 431, error code 4350) Network with primary vlan 1020 and secondary vlan 1033 type Isolated already exists or overlaps with other network pvlans in zone 1 | Passed 15 | Not testing using already used Primary 1020, but different/unique Community, since it will work by design | NA | NA | NA 16 | Create "overlapping" PVLAN setup, using unique/new Primary 1030, but same Isolated 1021 that is used already | … vlan=1030 isolatedpvlan=1021 isolatedpvlantype=isolated | API call should fail: Error: (HTTP 431, error code 4350) Network with primary vlan 1030 and secondary vlan 1021 type Isolated already exists or overlaps with other network pvlans in zone 1 | Passed 17 | Create "overlapping" PVLAN setup, using unique/new Primary 1030, but same Community 1023 that is used already | … vlan=1030 isolatedpvlan=1023 isolatedpvlantype=community | API call should fail: Error: (HTTP 431, error code 4350) Network with primary vlan 1030 and secondary vlan 1023 type Community already exists or overlaps with other network pvlans in zone 1 | Passed 18 | (VLANs 960-980 configured as reserved for the Physical network guest traffic) Confirm that the Primary VLAN overlap check is in place | … vlan=979 isolatedpvlan=980 isolatedpvlantype=community | API call should fail: Error: (HTTP 431, error code 4350) The VLAN tag 979 is already being used for dynamic vlan allocation for the guest network in zone ref-trl-374-v-M7-apanic | Passed 19 | (VLANs 960-980 configured as reserved for the Physical network guest traffic) Confirm that the Secondary VLAN overlap check is in place | … vlan=988 isolatedpvlan=980 isolatedpvlantype=community | API call should fail: Error: (HTTP 431, error code 4350) The VLAN tag 980 is already being used for dynamic vlan allocation for the guest network in zone ref-trl-374-v-M7-apanic | Passed 20 | Create PVLAN setup where Promiscuous Secondary VLAN has value different than the Primary VLAN | … vlan=1040 isolatedpvlan=1044 isolatedpvlantype=promiscuous | API call should fail: Error: (HTTP 431, error code 4350) Private VLAN type is set to Promiscouos, but VLAN ID and Secondary VLAN ID differ | Passed 21 | Create PVLAN setup where Isolated Secondary VLAN has the same value as the Primary VLAN | … vlan=1040 isolatedpvlan=1040 isolatedpvlantype=isolated | API call should fail: Error: (HTTP 431, error code 4350) Private VLAN type is set to Isolated, but VLAN ID and Secondary VLAN ID are equal | Passed 22 | Create PVLAN setup where Community Secondary VLAN has the same value as the Primary VLAN | … vlan=1040 isolatedpvlan=1040 isolatedpvlantype=community | API call should fail: Error: (HTTP 431, error code 4350) Private VLAN type is set to Community, but VLAN ID and Secondary VLAN ID are equal | Passed | Positive checks on second Physical network | (API command expected to succeed) | | 23 | Confirm it’s possible to create an identical PVLAN setup on second Physical network (dvSwitch2) using Primary 1020 and Secondary Isolated 1021, that already exists on the first Physical network (dvSwitch1) | Ensure to have another/additional Physical network and add "Guest" traffic type with a reserved range of VLAN IDs for guest networks. Set the same tag on both the Physical network and the ‘DefaultL2NetworkOfferingVlan’ network offering, to ensure that the new guest network will be created on this new Physical network. Repeat the test No.3 – creating the PVLAN setup using the same Primary VLAN 1020 and Secondary Isolated VLAN 1021, that already exists on the original/different Physical network … vlan=1020 isolatedpvlan=1021 isolatedpvlantype=isolated | A network is created, and when attached to a running VM, the appropriate Port Group is created on dvSwitch2 | Passed | VM ingestion of PVLAN-enabled VMs | (API command expected to succeed) | | 24 | Import VM with a PVLAN network setup (single NIC, Promiscuous), with explicitly assigning NIC to an ACS L2 network | Have a stopped VM with a single NIC on the vSphere Port Group "net2000-p2000" (Primary VLAN 2000, Secondary Promiscuous VLAN 2000). Create an L2 PVLAN network in CloudStack with the same combination of Primary and Secondary VLANs. Import the VM by explicitly stating the destination ACS network for the NIC of the VM. Start the VM. | VM is imported and start successfully, while the NIC is moved from the "net2000-p2000" to the new port groups (with identical PVLAN setup) created by ACS "cloud.guest.2000.s2000.200.1-dvSwitch1" | Passed 25 | Import VM with a PVLAN network setup (single NIC, Isolated), with auto-assigning NIC to an ACS L2 network. | Have a running VM with a single NIC on the vSphere Port Group "net2000-i2001" (Primary VLAN 2000, Secondary Isolated VLAN 2001). Create an L2 PVLAN network in CloudStack with the same combination of Primary and Secondary VLANs. Import the VM without explicitly stating the destination ACS network for the NIC of the VM. Stop and start the VM. | VM is imported to the correct ACS network and then stopped and started successfully. VM’s NIC is moved from the "net2000-i2001" to the new port groups (with identical PVLAN setup) created by ACS "cloud.guest.2000.s2001.200.1-dvSwitch1" | Passed 26 | Import VM with a PVLAN network setup (4 NICs, different PVLAN setup), with auto-assigning NICs to ACS L2 networks | Have a running VM with a 4 NIC on the vSphere Port Groups "net2000-c2003"(Primary VLAN 2000, Secondary Community VLAN 2003), "net2000-c2002"(Primary VLAN 2000, Secondary Community VLAN 2002), "net2000-i2001"(Primary VLAN 2000, Secondary Isolated VLAN 2001) and "net2000-p2000"(Primary VLAN 2000, Secondary Promiscuous VLAN 2000). Create 4 x L2 PVLAN network in CloudStack with the same combination of Primary and Secondary VLANs the existing Port Groups have. Import the VM without explicitly stating destination ACS networks for the NICs of the VM. Stop and start the VM. | VM is imported to the correct ACS networks and then stopped and started successfully. VM's NICs are moved from the original Port Groups to the new ones(with respectively identical PVLAN setup) created by ACS i.e. "cloud.guest.2000.s2003.200.1-dvSwitch1", "cloud.guest.2000.s2002.200.1-dvSwitch1", "cloud.guest.2000.s2001.200.1-dvSwitch1" and "cloud.guest.2000.s2000.200.1-dvSwitch1". | Passed
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
