Pod hints do not include hugepage data
Bug #1897996 reported by
Caleb Ellis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Alberto Donato |
Bug Description
The pod websocket object has "hints" for some of its properties, namely allocated/free cores/memory/
Similarly, a machine that is the host of a LXD pod will have the non-hugepage memory total shown in the machine list.
It would be good if the hints could be updated to include hugepage memory, if applicable.
Related branches
~ack/maas:vm--resources-memory-free-exclude-hugepages
Merged
into
maas:master
- Björn Tillenius: Approve
- MAAS Lander: Approve
-
Diff: 98 lines (+12/-9)2 files modifiedsrc/maasserver/models/tests/test_virtualmachine.py (+9/-9)
src/maasserver/models/virtualmachine.py (+3/-0)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Memory in pod hints should indeed include all the memory, not just the general one when there's hugepages. I'll fix that.
For machines that are LXD pods, the machine memory reported in the machine listing (or details) page should be the total (discovered on commissioning), so it shouldn't include hugepages.