<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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.<div><br></div><div>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.</div><div><br></div><div>Joshua</div><div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>--</div><div><br></div><div>Joshua McKenty</div><div>Chief Technology Officer</div><div>Piston Cloud Computing, Inc.</div><div>+1 (650) 242-5683</div><div>+1 (650) 283-6846</div><div><a href="http://www.pistoncloud.com">http://www.pistoncloud.com</a></div><div><br></div><div>"Oh, Westley, we'll never survive!"<br>"Nonsense. You're only saying that because no one ever has."</div></div></div>
</div>
<div><br><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span style="font-family:'Helvetica'; font-size:medium;">Burt Holzman <<a href="mailto:burt@fnal.gov">burt@fnal.gov</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Subject: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><b>Re: [openstack-dev] Discussing Amazon API compatibility [Nova][Swift]</b><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span style="font-family:'Helvetica'; font-size:medium;">July 27, 2013 11:52:56 AM PDT<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>To: </b></span><span style="font-family:'Helvetica'; font-size:medium;"><<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Reply-To: </b></span><span style="font-family:'Helvetica'; font-size:medium;">OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br></span></div><br><div>On 7/26/2013 10:39 AM, Jay Pipes wrote:<br><blockquote type="cite">On 07/26/2013 08:04 AM, Sean Dague wrote:<br><blockquote type="cite">Also there are EC2 design points that have request lengths greater than<br>what Apache (or any other web front end) is compiled to support, as they<br>have the possibility of enourmous GET strings (16K at least). Again,<br>instead of sensibly requiring to move to POST in those cases. I know we<br>had to land a change for CERN to allow bigger requests on EC2 calls for<br>just this reason (we did keep the get length apache sized on OSAPI, so<br>we didn't break people's attempts to get this behind a real web server).<br></blockquote></blockquote><br>I wrote that patch, so now I feel qualified to jump in this thread. :)<br><br><blockquote type="cite">However, I will say that developers write code to scratch an itch -- or<br>some product manager's itch. So the fact that nobody is all that<br>interested in spending time to code up enhanced EC2 API support in Nova<br>is, well, quite telling that the demand for such things is less than<br>what some people think.<br></blockquote><br>I know that my user community has little to no experience with openstack<br>development, but our still nascent cloud infrastructure is built around<br>tools that speak EC2. API translation layers like Deltacloud are just<br>another layer we'd need to deploy, operate, monitor, and so on, and on<br>the whole I think we'd prefer for the compatibility to be built-in<br>rather than yet another service.<br><br>I disagree about measuring user demand -- it's not a great metric here.<br>When I tried to throw an issue over the wall to nova development, it got<br>thrown back and I was asked to sign the CLA and contribute directly*. I<br>think it's tough to gauge user demand if that's the usual answer to<br>missing API bits.<br><br>- B<br><br>* I'm not complaining about this -- it's the model for community-driven<br>development. (And I can only contribute parasitically, development isn't<br>my day job.)<br><br>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></div></blockquote></div><br></div></body></html>