Difference between revisions of "Trove-Instance-Metadata"
Imsplitbit (talk | contribs) (→Introduction) |
Imsplitbit (talk | contribs) (→Goals) |
||
| Line 6: | Line 6: | ||
= Goals = | = Goals = | ||
| + | # Give trove users the ability to store key/value pairs that have significance to them but is not essential to trove's functionality | ||
| + | # Create a user accessible rest API to manage instance metadata | ||
| + | # Mimic the design/interface used by Nova | ||
| + | # Implement the model so that it acts like a dictionary to make hooking in metadata into the instance very easy and small | ||
| + | |||
= Description = | = Description = | ||
= API = | = API = | ||
Revision as of 01:05, 31 March 2014
Contents
Introduction
This wiki page describes the design for adding user managed metadata to instances.
Blueprint
https://blueprints.launchpad.net/trove/+spec/trove-metadata
Goals
- Give trove users the ability to store key/value pairs that have significance to them but is not essential to trove's functionality
- Create a user accessible rest API to manage instance metadata
- Mimic the design/interface used by Nova
- Implement the model so that it acts like a dictionary to make hooking in metadata into the instance very easy and small
