Open Stack

If we ever have users who feel like they have to "sign the CLA and submit a patch", then we've failed to establish the type of community that we've been going for.

Burt, please meet Tim Bell and Ryan Lane - the chairs of the still-unfortunately-nascent OpenStack Foundation User Committee, and the folks who are responsible for being your non-patching voice within the developer echo-chamber.

Joshua

--

Joshua McKenty
Chief Technology Officer
Piston Cloud Computing, Inc.
+1 (650) 242-5683
+1 (650) 283-6846
http://www.pistoncloud.com

"Oh, Westley, we'll never survive!"
"Nonsense. You're only saying that because no one ever has."

Begin forwarded message:

> From: Burt Holzman <burt at fnal.gov>
> Subject: Re: [openstack-dev] Discussing Amazon API compatibility [Nova][Swift]
> Date: July 27, 2013 11:52:56 AM PDT
> To: <openstack-dev at lists.openstack.org>
> Reply-To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org>
> 
> On 7/26/2013 10:39 AM, Jay Pipes wrote:
>> On 07/26/2013 08:04 AM, Sean Dague wrote:
>>> Also there are EC2 design points that have request lengths greater than
>>> what Apache (or any other web front end) is compiled to support, as they
>>> have the possibility of enourmous GET strings (16K at least). Again,
>>> instead of sensibly requiring to move to POST in those cases. I know we
>>> had to land a change for CERN to allow bigger requests on EC2 calls for
>>> just this reason (we did keep the get length apache sized on OSAPI, so
>>> we didn't break people's attempts to get this behind a real web server).
> 
> I wrote that patch, so now I feel qualified to jump in this thread. :)
> 
>> However, I will say that developers write code to scratch an itch -- or
>> some product manager's itch. So the fact that nobody is all that
>> interested in spending time to code up enhanced EC2 API support in Nova
>> is, well, quite telling that the demand for such things is less than
>> what some people think.
> 
> I know that my user community has little to no experience with openstack
> development, but our still nascent cloud infrastructure is built around
> tools that speak EC2. API translation layers like Deltacloud are just
> another layer we'd need to deploy, operate, monitor, and so on, and on
> the whole I think we'd prefer for the compatibility to be built-in
> rather than yet another service.
> 
> I disagree about measuring user demand -- it's not a great metric here.
> When I tried to throw an issue over the wall to nova development, it got
> thrown back and I was asked to sign the CLA and contribute directly*. I
> think it's tough to gauge user demand if that's the usual answer to
> missing API bits.
> 
> - B
> 
> * I'm not complaining about this -- it's the model for community-driven
> development. (And I can only contribute parasitically, development isn't
> my day job.)
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20130729/a08c7a7e/attachment.html>