> > > 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. > > Will this be accessible in the same way as currently or it needs changes on > client side?
How about ceilometer-api service returns 301 'Moved Permanently' for any requests to /v2/alarms, redirecting to the new Aodh endpoint? Being a standard HTTP response code, this should be handled gracefully by any (non-broken) HTTP client. Cheers, Eoghan __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
