-
Notifications
You must be signed in to change notification settings - Fork 1.2k
importvm: fix IP address allocation on Shared networks #11811
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
importvm: fix IP address allocation on Shared networks #11811
Conversation
harikrishna-patnala
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.
code LGTM.
Better to test it with shared, L2 and isolated network types.
|
@blueorangutan package |
|
@harikrishna-patnala a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## 4.20 #11811 +/- ##
============================================
- Coverage 16.17% 16.17% -0.01%
- Complexity 13297 13299 +2
============================================
Files 5656 5656
Lines 498331 498338 +7
Branches 60476 60478 +2
============================================
+ Hits 80591 80592 +1
- Misses 408767 408774 +7
+ Partials 8973 8972 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Packaging result [SF]: ✖️ el8 ✖️ el9 ✔️ debian ✖️ suse15. SL-JID 15357 |
|
@blueorangutan package |
|
@nvazquez a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 15359 |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-14602)
|
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.
Pull Request Overview
This PR fixes IP address allocation for importing VMs on Shared networks by updating the import process to handle Shared networks instead of just Basic zones.
- Refactored IP allocation logic to handle Shared networks specifically instead of relying on Basic zone logic
- Removed unused imports and injection dependencies for
IpAddressManager - Updated method naming to reflect the change from Basic zone to Shared network handling
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| UnmanagedVMsManagerImpl.java | Removed unused IP address allocation code and dependencies, simplified IP address initialization |
| NetworkOrchestrator.java | Updated IP allocation logic to handle Shared networks instead of Basic zones, renamed method accordingly |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
vishesh92
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.
clgtm. I did very basic testing by importing the VM from the shared disk. Earlier an IP was assigned to the imported VM (stopped state). After these changes, no IP is assigned to the imported VM. When the VM is started, an IP will be allocated. This should allow the user to import more VMs than the available IPs. But the start VM will probably fail due to unavailability of IPs.
thanks @vishesh92 for the testing I think it would be better to allocate an IP when VM is imported (not started). |
yes I do agree @weizhouapache but with this PR it is supposed to get an IP during import itself right, except for L2 network. Do we need more changes then ? |
thanks @harikrishna-patnala I tested import of Running vms on L2/shared/isolated, all worked I will test it |
|
pushed a commit to update IP state on shared network |
|
@blueorangutan package |
|
@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
@blueorangutan package |
|
@vishesh92
|
rajujith
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.
Looks good except for the IP not getting allocated along with import.
|
@blueorangutan package |
|
@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
thanks @rajujith |
|
Packaging result [SF]: ✖️ debian. SL-JID 15396 |
|
@blueorangutan package |
|
@vishesh92 a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✖️ el8 ✖️ el9 ✖️ debian ✖️ suse15. SL-JID 15397 |
vishesh92
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.
clgtm
|
@blueorangutan package |
|
@rajujith a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✖️ debian ✔️ suse15. SL-JID 15398 |
|
@blueorangutan test |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✖️ debian ✔️ suse15. SL-JID 15402 |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-14631)
|
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
Tested, import works and the IP address is allocated during import in a basic zone.
thanks @rajujith @vishesh92 @harikrishna-patnala for the testing and review Merging |
Description
This PR fixes #11799
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?