Once again allow a VM to be on multiple networks from VPCs#3754
Once again allow a VM to be on multiple networks from VPCs#3754DaanHoogland merged 1 commit intoapache:4.13from
Conversation
|
@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-449 |
|
@blueorangutan test |
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-588)
|
GabrielBrascher
left a comment
There was a problem hiding this comment.
LGTM based on code review, if conditional removal looks ok on that context.
borisstoyanov
left a comment
There was a problem hiding this comment.
LGTM, manually verified the constraint is no more, I was able to deploy a VM directly into 3 tiers from a VPC. Other question is if reverting of this constraint would cause grief with people setup.
* create template from snapshot regression (partly reverted) (#3767) * Once again allow a VM to be on multiple networks from VPCs (#3754) to once again allow a VM to be on multiple networks from VPCs * convert protocal names to be found as labels (#3747) * convert protocal names to be found as labels * format * filter hosts to query on zone wide storage (#3733) * config: add isdynamic flag in configuration response (#3729) Co-authored-by: Wei Zhou <ustcweizhou@gmail.com>
* 4.13: Added zone check for attach iso (#3755) config: add isdynamic flag in configuration response (#3729) filter hosts to query on zone wide storage (#3733) convert protocal names to be found as labels (#3747) Once again allow a VM to be on multiple networks from VPCs (#3754) create template from snapshot regression (partly reverted) (#3767)
to once again allow a VM to be on multiple networks from VPCs
revert b13acc6
to once again allow a VM to be on multiple networks from VPCs
Fixes: #3702
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?