Actions
Bug #26656
closedDisplay memory in consistent way
Difficulty:
medium
Triaged:
Yes
Bugzilla link:
Description
Based on the feedback from the mailing list:
Can you explain why one VM showed 1024Mi where others showed 1Gi for the memory? It looked like it came straight from the API since the console also showed 1Gi where Foreman normally uses GB.
We need to make sure to always use GB while displaying virtual machine memory.
---
There is inconsistency in the reported memory - we should normalize it to a single units:
2.3.3 :016 > c.servers.map { |s| s.memory }
=> ["1Gi", "1024Mi", "1024Mi", "1024M"]
So we got Gi, Mi and M - but that doesn't contradict:
https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#meaning-of-memory
However, can fractions be specified ? Assuming user would like less than 1G vm ?
We faced similar issue with MIQ kubevirt provider here:
https://github.com/ManageIQ/manageiq-providers-kubevirt/blob/master/app/models/manageiq/providers/kubevirt/memory_calculator.rb#L31
Added by Moti Asayag almost 6 years ago
Actions
Fixes #26656 - Fix memory issues (#100)
The PR fixes few memory issues:arguments)
expected format in the VM arguments)
on the defaults
this PR it was considered to be MiB which lead to a lower amount of
memory than expected.