+1 option one.
On Wed, Jul 11, 2012 at 11:55 AM, Paul McMillan paul.mcmil...@nebula.comwrote:
+1 for option 1. Bite the bullet now, rather than making it worse later.
-Paul
__**_
Mailing list:
You can configure those values thru the paste conf.
[filter:ratelimit]
paste.filter_factory =
nova.api.openstack.limits:RateLimitingMiddleware.factory
limits =(POST, *, .*, 10, MINUTE);(POST, */servers, ^/servers,
50, DAY);(PUT, *, .*, 10, MINUTE);(GET, *changes-since*,
.*changes-since.*, 3,
Separating into subteams seems like a good idea and will allow more focus on
certain areas, but having separate mailing lists for each team might be a
little too overkill, could lead to fragmented development discussions. Even
to have a cursory overview of what's happening in the teams will
to the main openstack list so everyone can get a high-level
overview of the planned changes.
Vish
On Oct 17, 2011, at 9:05 AM, Nirmal Ranganathan wrote:
Separating into subteams seems like a good idea and will allow more focus
on certain areas, but having separate mailing lists for each team
I haven't seen anyone mention this in the mailing list, but thought it was
interesting. The San Diego Super Computing Center's new SDSC Cloud uses
Openstack (Swift)
http://www.sdsc.edu/News%20Items/PR092211_sdsccloud.html
On Wed, Sep 28, 2011 at 9:53 AM, Lauren Sell lau...@openstack.org wrote:
5 matches
Mail list logo
