API still refers to "owner data" rather than "workload annotations"
Bug #1928115 reported by
Björn Tillenius
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Alberto Donato | ||
Bug Description
When implementing workload annotations, we reused the owner data model that we already had, and which was mostly unused.
This means that if you go to the UI, you know see that there are "workload annotation". But if you go to the API, you don't see any mentions of those.
Even though we re-used the owner data model, we should add methods for workload annotations, and eventually even deprecate owner data.
For now, we probably have to live with having both owner data and workload annotations that are the same thing.
Related branches
~ack/maas:1928115-wla-api-naming
- Alberto Donato: Abstain
- MAAS Lander: Needs Fixing
- Christian Grabowski: Approve
-
Diff: 358 lines (+88/-45)7 files modifiedsrc/maasserver/api/devices.py (+7/-2)
src/maasserver/api/machines.py (+3/-2)
src/maasserver/api/nodes.py (+20/-9)
src/maasserver/api/tests/test_devices.py (+2/-2)
src/maasserver/api/tests/test_enlistment.py (+2/-2)
src/maasserver/api/tests/test_machines.py (+8/-6)
src/maasserver/api/tests/test_node.py (+46/-22)
| Changed in maas: | |
| milestone: | none → 3.0.0-rc1 |
Revision history for this message
| Alberto Donato (ack) wrote | #1 |
| Changed in maas: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Alberto Donato (ack) |
| status: | New → In Progress |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We have a similar case with pods vs vmhosts, where the former are deprecated aliases for the second. We should do the same here