Thanks for catching this, we totally missed content-type versioning in our discussion. I think we need to talk about this with the team on IRC, as I know we have some differing opinions. I'll put it on the agenda for the next meeting.
Brian On Nov 4, 2011, at 4:49 PM, Jorge Williams wrote: > Thoughts on v1.1 -> v2 rename. > > 1. As stated: URI changes /v1.1/ to /v2/ though we keep redirecting 1.1 > requests to v2.0. > 2. Mime type accepts version=2 as a parameter but still responds to > version=1.1 so the following will remain valid mimeTypes: > a) application/vnd.openstack.compute+xml;version=1.1 and > application/vnd.openstack.compute+xml;version=2 (should this be v2?) > b) application/vnd.openstack.compute+json;version=1.1 and > application/vnd.openstack.compute+json;version=2 > 3. XML namespace stays the same, I don't see a compelling reason to change > it. > > Thoughts? > > -jOrGe W. > > On Nov 4, 2011, at 3:08 PM, Brian Waldon wrote: > >> The nova-api team just had it's first meeting and I wanted to share with >> everybody some important decisions that were made: >> >> 1) Team Definition >> - The nova-api team is going to "Own the design and implementation of Nova's >> public and private HTTP APIs" >> - This team should be the driving force behind the definition of the >> OpenStack Compute API, however, this needs to happen with the greater >> community as this team does not fully own this specification >> - This team does not own the EC2 compatibility API (Vish will establish a >> new team to own that). This might mean there is a better name than 'nova-api' >> >> 2) OpenStack Compute API Versioning >> - Moving forward, we should only expose major versions in the URI >> - We should call the existing v1.1 API 'v2' due to the major versioning >> distinction made between v1.0 and v1.1. We will maintain compatibility with >> the existing v1.1 URI with a redirect (/v1.1 -> /v2) >> - There is still a lot to discuss w.r.t. minor versioning and what that >> looks like at the Essex release. Expect to see this decision made at a later >> time >> - Most of the existing extensions will be rolled into the v2 API release at >> Essex >> >> 3) Blueprint Highlights >> - separate-nova-volumeapi - During Essex, we plan to create a new api >> endpoint specifically for our volumes service. >> - separate-nova-metadata - We also plan to extract the metadata service from >> the EC2 api and make it separately deployable. >> - separate-nova-adminapi - The existing admin-only functionality will be >> removed from Nova's implementation of the OpenStack Compute API and made >> separately deployable >> >> I'm sorry to any of those of you that could not attend due to poor timing. >> Hopefully we can find a time that works better for all of us. For those of >> you that want to attend future meetings, please contact me and tell me what >> time range is best for you. Thanks vishy, jorgew, DuncanT, westmaas, ttx, >> and xtoddx for being there today! >> >> Brian Waldon >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp > -------------------------------------- Brian Waldon Cloud Software Developer Rackspace Hosting
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
