Open Stack

I'd agree with Angus.


在 2015-07-16 12:05:25，"Angus Salkeld" <asalkeld at mirantis.com> 写道：

On Tue, Jun 30, 2015 at 6:09 PM, Julien Danjou <julien at danjou.info> wrote:
On Mon, Jun 29 2015, Ildikó Váncsa wrote:

> I think removing options from the API requires version bump. So if we plan to
> do this, that should be introduced in v3 as opposed to v2, which should remain
> the same and maintained for two cycles (assuming that we still have this policy
> in OpenStack). It this is achievable by removing the old code and relying on
> the new repo that would be the best, if not then we need to figure out how to
> freeze the old code.

This is not an API change as we're not modifying anything in the API.
It's just the endpoint *potentially* split in two. But you can also
merge them as they are 2 separate entities (/v2/alarms and /v2/*).
So there's no need for a v3 here.



Hi Julien,


I just saw this, and I am concerned this is going to kill Heat's gate (and user's templates).


Will this be hidden within the client so that as long as we have aodh enabled in our gate's devstack
this will just work?


-Angus
 

As the consensus goes toward removal, I'll work on a patch for that.

--
Julien Danjou
/* Free Software hacker
   http://julien.danjou.info */

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150716/743447cb/attachment.html>