Prefill custom compute offering values for VMware import#13237
Prefill custom compute offering values for VMware import#13237andrijapanicsb wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #13237 +/- ##
=========================================
Coverage 18.10% 18.10%
- Complexity 16746 16748 +2
=========================================
Files 6037 6037
Lines 542933 542945 +12
Branches 66487 66494 +7
=========================================
+ Hits 98283 98292 +9
- Misses 433602 433605 +3
Partials 11048 11048
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:
|
|
@blueorangutan package |
|
@andrijapanicsb a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 18023 |
There was a problem hiding this comment.
Pull request overview
This PR improves the VMware unmanaged-instance import flow by ensuring custom compute offering inputs are prefilled from the discovered source VM sizing (instead of generic fallback defaults), and by forcing a refresh of the custom input component when the selected offering or discovered sizing changes.
Changes:
- Force
<compute-selection>to be recreated when the selected offering or discovered CPU/memory/speed values change (via a computed:key). - Introduce a computed prefill payload for custom compute offerings that clamps CPU/memory to constrained min/max when applicable.
- Default unknown/zero CPU speed to
2000MHz when using custom offerings.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
0 MHz.Problem
When importing a VMware VM and selecting a custom unconstrained compute offering, the UI could prefill the custom fields with generic fallback values instead of the discovered source VM sizing:
10 MHz32 MBThis happened even when the source VM details already showed useful sizing information, for example
3 CPUand4096 MBmemory.Existing Behavior
serviceofferingdetailswith min/max CPU and memory bounds.1 CPU,0 MHz, and32 MB.New Behavior
0or unknown, the UI now defaults the custom CPU speed field to2000 MHz.Testing
git diff --check.ui/src/views/tools/ImportUnmanagedInstance.vue.