Thanks Joe. Still have another question, for which case shall we need to add new extension to the v2 AP? If freeze the v2 api at icehouse-2, then does it mean that we are not allowed to make any changes to v2 api? All api changes should go to v3 directly, right?
Thanks, Jay 2013/12/27 Joe Gordon <joe.gord...@gmail.com> > > > > On Thu, Dec 26, 2013 at 1:03 AM, Jay Lau <jay.lau....@gmail.com> wrote: > >> Hi, >> >> In Icehouse development, do we have some guidelines for nova api change? >> If I want to make some changes for nova api, do I need to update both v2 >> and v3 or just v3? >> > > For every new extension to the v2 API we require the equivalent change to > the v3 api, so that there is nothing in v2 that V3 doesn't support. But > requiring the opposite doesn't make any sense to me, and seems like a waste > of human resources. > > https://etherpad.openstack.org/p/icehouse-summit-nova-v3-api says we want > to freeze the v2 api at icehouse-2, a plan which I full support. > > >> >> There are some patches related to this, hope can get some comments from >> you. >> >> https://review.openstack.org/#/c/52733/ >> https://review.openstack.org/#/c/52867/ >> https://review.openstack.org/#/c/63853/ >> >> Thanks, >> >> Jay >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev