Re: [openstack-dev] [nova] Temporary freeze on API changes

2015-02-23 Thread Matthew Gilliard
The devref has merged:
http://docs.openstack.org/developer/nova/devref/api_microversions.html

There are a few corner cases being worked on now, but the information
in there should be enough to add a new API change  version.

MG

On Fri, Feb 20, 2015 at 12:33 AM, Christopher Yeoh cbky...@gmail.com wrote:
 Hi,

 The Nova API subgroup is planning on releasing V2.1 on Monday (changing its
 status from experimental to CURRENT) and merging the first patch which uses
 microversions on top of 2.1 on the Wednesday.

 In the meantime we'd appreciate it if reviewers did not +A any patchset
 which changes the REST API (as it potentially means we'd have to sync
 changes to 2.1 as well. Any future api changes should only be applied to the
 v2.1/v3 tree and use the microversions mechanism.

 When https://review.openstack.org/#/c/140313/ is merged, that will signal
 that microversions
 is enabled and we are open for patches to v2.1 microversions. At this point
 no changes should be accepted to the old v2 api code and anything to the
 v2.1 code base should be done using the microversions mechanism.

 There is devref docs on how to use microversions either merged or working
 its way through gerrit.

 Regards,

 Chris

 __
 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] Temporary freeze on API changes

2015-02-19 Thread Christopher Yeoh
Hi,

The Nova API subgroup is planning on releasing V2.1 on Monday (changing its
status from experimental to CURRENT) and merging the first patch which uses
microversions on top of 2.1 on the Wednesday.

In the meantime we'd appreciate it if reviewers did not +A any patchset
which changes the REST API (as it potentially means we'd have to sync
changes to 2.1 as well. Any future api changes should only be applied to
the v2.1/v3 tree and use the microversions mechanism.

When https://review.openstack.org/#/c/140313/ is merged, that will signal
that microversions
is enabled and we are open for patches to v2.1 microversions. At this point
no changes should be accepted to the old v2 api code and anything to the
v2.1 code base should be done using the microversions mechanism.

There is devref docs on how to use microversions either merged or working
its way through gerrit.

Regards,

Chris
__
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