<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 27, 2016 at 12:00 AM, Joshua Harlow <span dir="ltr"><<a href="mailto:harlowja@fastmail.com" target="_blank">harlowja@fastmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Huang Zhiteng wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">
<br>
On Mon, Sep 26, 2016 at 12:05 PM, Joshua Harlow <<a href="mailto:harlowja@fastmail.com" target="_blank">harlowja@fastmail.com</a><br></span><span class="gmail-">
<mailto:<a href="mailto:harlowja@fastmail.com" target="_blank">harlowja@fastmail.com</a>><wbr>> wrote:<br>
<br>
Huang Zhiteng wrote:<br>
<br>
In eBay, we did some inhouse change to Nova so that our big data<br>
type of<br>
use case can have physical disks as ephemeral disk for this type of<br>
flavors. It works well so far. My 2 cents.<br>
<br>
<br>
Is there a published patch (or patchset) anywhere that people can<br>
look at for said in-house changes?<br>
<br>
<br>
Unfortunately no, but I think we can publish it if there are enough<br>
interests. However, I don't think that can be easily adopted onto<br>
upstream Nova since it depends on other in-house changes we've done to Nova.<br>
<br>
</span></blockquote>
<br>
Is there any blog, or other that explains the full bunch of changes that ebay has done (u got me curious)?<br>
<br>
The nice thing about OSS is that if u just get the patchsets out (even to github or somewhere), those patches may trigger things to change to match your usecase better just by the nature of people being able to read them; but if they are never put out there, then well ya, it's a little hard to get anything to change. </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Anything stopping a full release of all in-house changes?<br>
<br>
Even if they are not 'super great quality' it really doesn't matter :)</blockquote><div>Apology for sidetracking the topic a bit. While we encourage our engineers to embrace community and open source, I think we didn't do a good job to actually emphasize that. 'Time To Market' is another factor, usually a feature requirement becomes deployed service in 2,3 sprint (4~6 weeks), but you know how much can be done in same amount of time in community, especially with Nova. :) <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
-Josh<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Regards<br>Huang Zhiteng</div>
</div></div>