pod and cluster storage_pools resources is missing pool id
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Undecided
|
Christian Grabowski |
Bug Description
Sorry, it turns out we need one last piece of data for the pools in both pod.resources.
e.g. in pod.storage_pools:
{
storage_pools: [
{
id: 'b85e27c9-
name: 'default',
type: 'dir',
path: '/var/lib/
total: 984373800960,
used: 40000000000,
available: 944373800960
}
]
}
and in pod.resources.
{
storage_pools: {
'default': {
name: 'default',
path: '/var/lib/
backend: 'dir',
allocated
allocated
total: 984373800960
}
}
}
Related branches
- MAAS Lander: Approve
- Alberto Donato (community): Approve
-
Diff: 63 lines (+34/-0)2 files modifiedsrc/maasserver/models/virtualmachine.py (+2/-0)
src/maasserver/websockets/handlers/tests/test_pod.py (+32/-0)
Changed in maas: | |
assignee: | nobody → Christian Grabowski (cgrabowski) |
status: | New → Triaged |
status: | Triaged → In Progress |
Changed in maas: | |
milestone: | none → 3.1.0 |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 3.1.0 → 3.1.0-rc1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
While this works for pods, and can be added to pod.resources. storage_ pools, only some storage pools on the cluster can have an id, as dir, zfs and btrfs backed storage pools are actually an aggregate of multiple storage pools within the cluster (1 per pod/VMHost), so these would have multiple pool ids. The default pool when composing should be from the pod selected, so if it is for the purpose of sorting, a list of ids can be provide, but would that be usable for the UI?