Create metadata storage for trove instances
Instance metadata is a feature that has been requested frequently by our users. They need a way to store critical information for their instances and have that be associated with the instance so that it is displayed whenever that instance is listed via the API. This also becomes very usable from a testing perspective when doing integration/ci. We can utilize the metadata to store things like what process created the instance, what the instance is being used for, etc... The design for this feature is modeled heavily on the Nova metadata API with a few tweaks in how it works internally.
Blueprint information
- Status:
- Started
- Approver:
- Michael Basnight
- Priority:
- Low
- Drafter:
- Daniel Salinas
- Direction:
- Needs approval
- Assignee:
- Peter Stachowski
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Slow progress
- Milestone target:
-
next
- Started by
- Nikhil Manchanda
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit spec is here: https:/
Im sure this, in some way, is dependent on replication, right?
No replication is dependent on this.
Gerrit topic: https:/
Addressed by: https:/
Add instance metadata functionality to trove
Gerrit review for instance metadata support for python-troveclient
https:/
You should not set a milestone target unless the blueprint has been properly prioritized by the project drivers.
(This is an automated message)
