Improves the network offering creation form#12951
Improves the network offering creation form#12951Tonitzpp wants to merge 1 commit intoapache:4.20from
Conversation
|
@bernardodemarco a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
Codecov Report✅ All modified and coverable lines are covered by tests.
Additional details and impacted files@@ Coverage Diff @@
## main #12951 +/- ##
=============================================
- Coverage 17.93% 3.52% -14.41%
=============================================
Files 5939 464 -5475
Lines 533147 40065 -493082
Branches 65237 7534 -57703
=============================================
- Hits 95601 1414 -94187
+ Misses 426804 38463 -388341
+ Partials 10742 188 -10554
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:
|
|
UI build: ✔️ |
There was a problem hiding this comment.
Pull request overview
This PR enhances the CloudStack UI network offering creation flow by exposing the specifyipranges API parameter in the form (for isolated guest networks) and aligning the UI default for egressdefaultpolicy with the API default (ALLOW).
Changes:
- Added a
specifyiprangesswitch to the “Add Network Offering” form for isolated guest type offerings. - Updated the form’s default
egressdefaultpolicyvalue fromdenytoallow. - Ensured
specifyiprangesis passed in request params where applicable and removed for L2 offerings.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@Tonitzpp , this is currently targetted for main/23, but I think it may be applicable for 22 or even 20 as well. Care to check? |
|
@DaanHoogland, I tested the changes in both 4.20 and 4.22 versions, and it works in both of them. I will re-target my PR to the 4.20 branch. |
42b4c49 to
c5c5a2d
Compare
|
@blueorangutan package |
|
@DaanHoogland 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 17426 |
Description
Currently, when creating a new network offering through the CloudStack graphical interface it is not possible to specify the
specifyiprangesparameter. Furthermore, the default value of theegressdefaultpolicyfield isDENY, while the API's default isALLOW.This PR made modifications to add the
specifyiprangesfield to the form and change the default value ofegressdefaultpolicy.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
How Has This Been Tested?
In the CloudStack graphical interface, I opened the create new network offering form and checked the new
specifyiprangesparameter was only in theIsolatedguest type and checked that the default value ofegressdefaultpolicyis nowAllow. After creating the new network offering, I created a new network and it was observed in the form that the fields to specify the IPs ranges were present.