Open Stack

I agree that we need to keep a tight focus on all API changes.

However was the problem with the floating IP change just to do with the implementation in Nova or the frequency with which Ceilometer was calling it ?     Whatever guildelines we follow on API changes themselves its pretty hard to protect against the impact of a system with admin creds putting a large load onto the system.

> -----Original Message-----
> From: Michael Still [mailto:mikal at stillhq.com]
> Sent: 12 June 2014 23:36
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [Nova] Review guidelines for API patches
> 
> In light of the recent excitement around quota classes and the floating ip
> pollster, I think we should have a conversation about the review guidelines
> we'd like to see for API changes proposed against nova. My initial proposal is:
> 
>  - API changes should have an associated spec
> 
>  - API changes should not be merged until there is a tempest change to test
> them queued for review in the tempest repo
> 
> Thoughts?
> 
> Michael
> 
> --
> Rackspace Australia
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev