Open Stack

Hey Everyone,

One of the most important items from the agenda[1] for the Nova meeting on Thursday is discussing some api consistency issues. I wanted to give a little overview on what I want to discuss, so that people have time to prepare in advance of the meeting.

The main issue is that we have a bunch of data that we handle as part of a post to servers that is not in the core api spec. This data really belongs to extensions (and is in fact directly related to a specific extension in most cases). Unfortunately, there is no way to turn processing for this extra data off, which is basically a Very Bad Thing™.

I've been thinking about a simple way to solve this issue, and I've come up with a spec[2] that i think is workable. I'd like to get some decisions on the following at the meeting:

a) is this approach acceptable?
 * does it need to be modified slightly?
 * is renaming the badly named extensions ok?
 * is there a more general approach that extensions could use?
b) is there an alternative to this that is easier/better?
 * alternative: bump minor version of the api?
c) who wants to help on produce the required code in the next week?
d) who wants to help update the documentation?
e) who wants to investigate xml?

Also, a quick heads up on the "Other Potential Issues" section on the agenda[1]. I want to discuss large user/deployer facing issues. I've listed the ones that I know about. I would like to get some consensus on whether we should push to get any of these fixed in Folsom, either during f-3 or bugfixing. If there are other key user issues, let me know so I can add them to the list.

[1] http://wiki.openstack.org/Meetings/Nova
[2] http://wiki.openstack.org/DisableServerExtensions