Re: [openstack-dev] [nova] will the real v2.1/v3 API status please stand up?
2015-02-09 9:26 GMT+09:00 Christopher Yeoh : >> >> I wasn't at the mid-cycle meetup for Kilo but even for Juno I'll admit I >> was a bit lost. It's not my fault, I'm more good looks than brains. :) >> >> When I look at approved specs for Kilo, three pop out: >> >> 1. https://blueprints.launchpad.net/nova/+spec/v2-on-v3-api >> >> 2. https://blueprints.launchpad.net/nova/+spec/api-microversions >> >> 3. https://blueprints.launchpad.net/nova/+spec/v3-api-policy >> > > So we need the first to blueprints for v2.1 microversions. We don't need > v3-api-policy merged to release > v2.1 microversions though I believe it is a separate important bit of work > to reduce tech debt and make > life easier for operators. I think the first one(bp/v2-on-v3-api) only is necessary for dropping 'experimental' label from v2.1 API, because raw v2.1 API(meaning v2.1 without microversions) has already implemented some merits (strong validation, clean code, easy deployment, etc) for developers and operators. >> The only one of those that has a dependency in launchpad is the last one >> and it's dependency is on: >> >> https://blueprints.launchpad.net/nova/+spec/nova-v3-api >> >> Which looks like it was replaced by the v2-on-v3-api blueprint. >> >> If I look at the open changes for each, there are a lot: >> >> 1. >> https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/v2-on-v3-api,n,z >> >> 2. >> https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/api-microversions,n,z >> >> 3. >> https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/v3-api-policy,n,z >> >> Do those all need to merge before the v2.1 API is no longer experimental? As I said at the above, the first branch is necessary for dropping experimental from v2.1 API. In addition, the first branch contains some cleanup patches also. The important patches are just four: * Provide full v2 compatibility https://review.openstack.org/#/c/138599/ https://review.openstack.org/#/c/153466/ https://review.openstack.org/#/c/153137 * Drop experimental from v2 https://review.openstack.org/149948 So we have already done most works for v2.1 API. Thanks Ken Ohmichi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [nova] will the real v2.1/v3 API status please stand up?
Hi, On Sat, Feb 7, 2015 at 8:35 AM, Matt Riedemann wrote: > I'm not going to hide it, I don't know what's going on with the v2.1 API > status, i.e. what is the criteria to that thing dropping it's > 'experimental' label? > > So I caught up with Matt on IRC, repeating some references and discussion here for everyone else > I wasn't at the mid-cycle meetup for Kilo but even for Juno I'll admit I > was a bit lost. It's not my fault, I'm more good looks than brains. :) > > When I look at approved specs for Kilo, three pop out: > > 1. https://blueprints.launchpad.net/nova/+spec/v2-on-v3-api > > 2. https://blueprints.launchpad.net/nova/+spec/api-microversions > > 3. https://blueprints.launchpad.net/nova/+spec/v3-api-policy > > So we need the first to blueprints for v2.1 microversions. We don't need v3-api-policy merged to release v2.1 microversions though I believe it is a separate important bit of work to reduce tech debt and make life easier for operators. > The only one of those that has a dependency in launchpad is the last one > and it's dependency is on: > > https://blueprints.launchpad.net/nova/+spec/nova-v3-api > > Which looks like it was replaced by the v2-on-v3-api blueprint. > > If I look at the open changes for each, there are a lot: > > 1. https://review.openstack.org/#/q/status:open+project: > openstack/nova+branch:master+topic:bp/v2-on-v3-api,n,z > > 2. https://review.openstack.org/#/q/status:open+project: > openstack/nova+branch:master+topic:bp/api-microversions,n,z > > 3. https://review.openstack.org/#/q/status:open+project: > openstack/nova+branch:master+topic:bp/v3-api-policy,n,z > > Do those all need to merge before the v2.1 API is no longer experimental? > > We have an etherpad here which tracks our release criteria for v2.1 and microversions: https://etherpad.openstack.org/p/v2_1_ReleaseCriteria As mentioned above it doesn't include api-policy To make life easier for us I'd also like to request that if you review a changeset that modifies the v2 api that you ensure it also if required is applied to v2.1(v3 code). If it doesn't apply to v3 then ensure a v2-only tag is in the commit message. That will help us verify v2 does not diverge from v2.1 just before release. After that I think v2 code will be essentially frozen except for bug fixes and any api changes will only be made through microversions. Regards, Chris Is the, for lack of a better term, 'completion criteria', being tracked in > an etherpad or wiki page somewhere? I see stuff in the priorities etherpad > https://etherpad.openstack.org/p/kilo-nova-priorities-tracking but it's > not clear to me at a high level what makes v2.1 no longer experimental. > > Can someone provide that in less than 500 words? > > -- > > Thanks, > > Matt Riedemann > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [nova] will the real v2.1/v3 API status please stand up?
I'm not going to hide it, I don't know what's going on with the v2.1 API status, i.e. what is the criteria to that thing dropping it's 'experimental' label? I wasn't at the mid-cycle meetup for Kilo but even for Juno I'll admit I was a bit lost. It's not my fault, I'm more good looks than brains. :) When I look at approved specs for Kilo, three pop out: 1. https://blueprints.launchpad.net/nova/+spec/v2-on-v3-api 2. https://blueprints.launchpad.net/nova/+spec/api-microversions 3. https://blueprints.launchpad.net/nova/+spec/v3-api-policy The only one of those that has a dependency in launchpad is the last one and it's dependency is on: https://blueprints.launchpad.net/nova/+spec/nova-v3-api Which looks like it was replaced by the v2-on-v3-api blueprint. If I look at the open changes for each, there are a lot: 1. https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/v2-on-v3-api,n,z 2. https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/api-microversions,n,z 3. https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/v3-api-policy,n,z Do those all need to merge before the v2.1 API is no longer experimental? Is the, for lack of a better term, 'completion criteria', being tracked in an etherpad or wiki page somewhere? I see stuff in the priorities etherpad https://etherpad.openstack.org/p/kilo-nova-priorities-tracking but it's not clear to me at a high level what makes v2.1 no longer experimental. Can someone provide that in less than 500 words? -- Thanks, Matt Riedemann __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev