upgrade status in external API #8869
Description
This may duplicate #8292 but I'm keeping this separate in case the two diverge. In today's update call we discussed the shape of the "get update status" API. I proposed something like:
- for all deployed components, figure out if their current version corresponds with:
- the current target release
- some other release
- unknown (recently mupdated)
then return an object with:
- current target release (including time it was made the target -- this tells you how long the upgrade has been in progress)
- count of components running each release (by release) -- this implicitly provides some kind of progress, but we don't want to emphasize this too much for various reasons
- time of last blueprint created (tells you if forward progress is being made)
- list of problems (items that are blocking forward progress on the upgrade)
In terms of implementation:
- the implementation of
omdb nexus update-status(and the internal API it's based on) provides a per-component breakdown, so I expect it'll be easy to turn this into counters by-release - the current target release, time set, and latest blueprint times are already available
- the list of blockers is not yet plumbed through somewhere useful. We'll probably want to take the the latest planning report and turn that into something externally-consumable.
Metadata
Metadata
Assignees
Labels
No labels