vpc: add bypassvlanoverlapcheck parameter when create private gateway#3899
vpc: add bypassvlanoverlapcheck parameter when create private gateway#3899DaanHoogland merged 1 commit intoapache:masterapache/cloudstack:masterfrom ustcweizhou:4.14-private-gateway-overlap-vlanustcweizhou/cloudstack:4.14-private-gateway-overlap-vlanCopy head branch name to clipboard
Conversation
|
@rhtyd this is the fix for trillian test |
|
@blueorangutan package |
|
@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✖centos6 ✔centos7 ✔debian. JID-923 |
|
@blueorangutan test |
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-1069)
|
|
@DaanHoogland @andrijapanicsb cc @PaulAngus @borisstoyanov @nvazquez - need more eye to ensure this does not cause any regression |
|
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + vmware-65u2) has been kicked to run smoke tests |
|
Trillian test result (tid-1077)
|
|
@blueorangutan test centos7 xenserver-71 |
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + xenserver-71) has been kicked to run smoke tests |
|
Trillian test result (tid-1081)
|
|
this is a lot of code change for a little functional change, what I've seen so far looks good, but I do want to take an hour or so later to go through it line by line. If others test extensively that fina as well, by me. |
@DaanHoogland in test_privategw_acl.py, it tests the vm connectivity between two VPCs. The two VPCs connect each time by private gateways. The two private gateways have same cidr/vlan, but different gateway (gateway of private gateway in a VPC is the ip attached on another VPC). Therefore I add vpcid to method getPrivateNetwork so they are mapped to different network (with correct gateway). It has another issue that they use same vlan, so I have to add bypassvlanoverlapcheck parameter. |
Commit e894238d904a9c49c1140371f612a51d251efc1 (apache#3899) allowed private gateways to bypass vlan check while refactoring it did not cover the case for L2 but only shared network. This fix will re-enable honouring the bypass vlan check option for L2 guest network (in addition to the Shared networks). Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
* engine: honour bypass VLAN id/range for L2 networks Commit e894238d904a9c49c1140371f612a51d251efc1 (#3899) allowed private gateways to bypass vlan check while refactoring it did not cover the case for L2 but only shared network. This fix will re-enable honouring the bypass vlan check option for L2 guest network (in addition to the Shared networks). Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com> * Update NetworkOrchestrator.java
Description
The vlan of private gateways in VPCs should not be same. In some edge cases, vlan of private gateways are same (for example in test_privategw_acl.py).
Similar as shared network, add bypassvlanoverlapcheck parameter when create private gateway.
This also fixes #3859 .
the root cause is #3859 (comment)
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
Run test_privategw_acl.py several times, no failure any more.