-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Added hot plugging of vifs in case of VMware isolated networks #5912
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…g router.extra.public.nics in case of VMware. Added hot plugging of vifs whenever required in case of isolated networks. VPC networks already uses hotplugging of vifs.
|
@blueorangutan package |
|
@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
plugins/hypervisors/vmware/src/main/java/com/cloud/hypervisor/guru/VmwareVmImplementer.java
Show resolved
Hide resolved
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2402 |
|
@blueorangutan test centos7 vmware-67u3 |
|
@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests |
borisstoyanov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, manually tested
|
@blueorangutan test centos7 vmware-67u3 |
|
@harikrishna-patnala a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests |
|
@blueorangutan package |
|
@weizhouapache a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2444 |
|
@blueorangutan test |
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-3143)
|
|
Trillian test result (tid-3144)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - manual testing to confirm change required
|
@harikrishna-patnala can you check/address any outstanding review comments |
|
@rohityadavcloud a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2450 |
|
@blueorangutan test centos7 vmware-67u3 |
weizhouapache
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@harikrishna-patnala
I have tested many scenarios with isolated networks and vpcs.
all looks ok, except an issue: #5934
I think it is not related to this PR.
|
Thanks for all the testing @weizhouapache @rohityadavcloud @borisstoyanov |
did you test that issue in a generic 4.16, @weizhouapache ? |
@DaanHoogland |
|
good merging... |
Description
This PR fixes #5716 where isolated network VR failed to deploy when Vmxnet3 adapter type is used and when router.extra.public.nics is not 0. This is because of the extra nics that are reserved in the VR based on the global setting router.extra.public.nics.
To address the issue we have now implemented nic hot plugging for isolated networks because systemvm templates had open-vm-tools installed and support hot plugging which is what is already used in the case of VPC VR.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Steps to reproduce:
After the fix, following are the test cases that are performed
Followed the same steps with vmware.systemvm.nic.device.type value E1000 and VR came up and subsequent operations of acquiring IP, enabling static NAT worked fine.