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
Fix Released
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

Changed in maas:
milestone: none → 3.0.0-rc1
Revision history for this message
Alberto Donato (ack) wrote :

We have a similar case with pods vs vmhosts, where the former are deprecated aliases for the second. We should do the same here

Alberto Donato (ack)
Changed in maas:
importance: Undecided → Medium
assignee: nobody → Alberto Donato (ack)
status: New → In Progress
Alberto Donato (ack)
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers