Code review comment for lp:~rackspace-titan/nova/metadata_v1.1
Revision history for this message
| Dan Prince (dan-prince) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
> With that said, I actually have reservations about whether or not this branch
> truly belongs in Nova. It seems like it would be better situated in a metadata
> service somewhere at the top of the stack, possibly attached to the API, and
> simply mapped to instance_ids.
>
> Since I missed this spec originally I won't block it, but I'd like to maybe
> discuss moving the responsibility for this to a different layer post Cactus
--
Hey Matt. We are looking into renaming things now.
So on whether this should exist in nova... We had previously bounced the idea around about whether metadata should be a separate service. It certainly could be and that might work better in some cases. Probably best to discuss that as a separate issue/blueprint.
All this branch does is basically extends the v1.0 implementation (which already used the database) to make metadata a RESTful sub-resource under /servers in the API to support the v1.1 spec.