You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
UI: Please change memory setting in flex compute offering from MiB to GiB #14082
As a user, I'd like to be able to set the memory size of my instances in GiB without having to calculate the correct MiB value.
Entering values in MiB tends to lead to entering round numbers of 1,000. This then results in odd GiB values.
If a VM with less than 1 GiB is ever actually needed, you can enter 0.5 GiB, for example.
However, this use case is likely to occur much less frequently than higher GiB values.
Maybe it could include a drop-down menu next to the value that uses GiB as the default but also allows MiB to be selected. But I think GiB is the most helpful for most people.
Requests that the memory-size input field for flexible compute offerings in the UI accept/display values in GiB instead of MiB, to avoid awkward MiB values when users intend round GiB numbers. This is a small UX/UI enhancement request.
📊 Assessment
Dimension
Value
Reasoning
Type
type:enhancement
Pure UX improvement request, not a bug.
Component
component:UI
Change is scoped to the compute offering creation/edit UI.
Severity
n/a
Not applicable — this is an enhancement, not a bug.
Labels
type:enhancement, component:UI
See above.
Coding agent
Needs more info
The UI change itself (unit toggle/dropdown, or switching displayed unit) is well-scoped and self-contained, but the exact desired UX (default unit, whether MiB should remain selectable, whether API/backend storage unit changes) isn't fully specified and would benefit from maintainer/UX input before implementation.
🔗 Similar issues
No similar or duplicate open issues were found for this request.
💡 Notes and suggestions
A reasonable implementation path: keep the underlying API/DB value in MiB (no backend changes needed) and only change the UI form to accept/display GiB, with a unit dropdown (GiB default, MiB optional) as the author suggests, converting to MiB before submission.
Relevant UI code is likely in ui/src/views/offering/ (compute offering forms) — worth checking for existing unit-handling patterns (e.g. how disk offering size fields handle GB/MB, if any) to keep UX consistent across the product.
This could be a good "help wanted" / newcomer-friendly UI task if a maintainer scopes the exact desired interaction.
@DaanHoogland
Since my colleagues and I aren't developers, unfortunately not. I also don't want to just throw in some AI-generated code here that I only half understand.
But we'd be happy to help with testing and verification in our test environment.
that’s ok @jl0815 , it does however mean that we cannot guarantee any delivery date ;) AI generated code is only appreciated if it is human reviewed/amended and tested. So you could go that path if you wish.
Activity
github-actions commentedon Sep 8, 2026
🎯 Triage report
Requests that the memory-size input field for flexible compute offerings in the UI accept/display values in GiB instead of MiB, to avoid awkward MiB values when users intend round GiB numbers. This is a small UX/UI enhancement request.
📊 Assessment
type:enhancementcomponent:UI🔗 Similar issues
No similar or duplicate open issues were found for this request.
💡 Notes and suggestions
ui/src/views/offering/(compute offering forms) — worth checking for existing unit-handling patterns (e.g. how disk offering size fields handle GB/MB, if any) to keep UX consistent across the product.Add this agentic workflows to your repo
To install this agentic workflow, run
DaanHoogland commentedon Sep 9, 2026
Nice proposal @jl0815, do you have manpower to work on it?
jl0815 commentedon Sep 10, 2026
@DaanHoogland
Since my colleagues and I aren't developers, unfortunately not. I also don't want to just throw in some AI-generated code here that I only half understand.
But we'd be happy to help with testing and verification in our test environment.
DaanHoogland commentedon Sep 10, 2026
that’s ok @jl0815 , it does however mean that we cannot guarantee any delivery date ;) AI generated code is only appreciated if it is human reviewed/amended and tested. So you could go that path if you wish.
saurabhkushwaha438 commentedon Sep 12, 2026
can i work on this issue
RosiKyu commentedon Sep 30, 2026
@saurabhkushwaha438 are you still planning to work on this issue and create a PR for the 24.0 release?
saurabhkushwaha438 commentedon Oct 7, 2026
Should I add the toggle menu everywhere MiB is currently used or for some specific component or section ?
DaanHoogland commentedon Oct 12, 2026
I suppose this is your call @saurabhkushwaha438 , but in general consistency is appreciated.