<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Mar 16, 2014 at 5:09 PM, Tom Fifield <span dir="ltr"><<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>></span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">On 17/03/14 09:07, Beth Cohen wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">
Folks -<br>
We have one that ended up in the Business and strategy track that<br>
belongs in Storage:<br>
<br></div>
*<a href="https://www.openstack.org/track-chairs/Show/898" target="_blank">https://www.openstack.org/<u></u>track-chairs/Show/898</a> *(Using Numerical<div class=""><br>
Models of Swift Performance to Build Better and More Cost-Effective Systems)<br>
</div></blockquote>
<br>
Here's a few from ops track.<br>
<br>
Consider for Apps on OpenStack:<br>
<br>
Application deployment and auto-scaling on OpenShift using Heat 86      121     1.41    <br>
<br>
Develop and test on dynamic OpenStack clusters  64      5       0.08<br>
<br>
<br>
Consider for Business:<br>
<br>
Is OpenStack ready for adoption in the Enterprise?      59      11      0.19<br>
Politics vs. Engineering Balance in Services Migration and Integration  75      14      0.19<br>
Ready for OpenStack? What to Do When You Are and They're Not    86      68      0.79<br>
OpenStack Distributions: Do We Really Need Them?        93      92      0.99<br>
OpenStack Barriers to Enterprise Adoption       79      70      0.89<br>
<br>
Consider for Compute:<br>
<br>
Massive Scale OpenStack with Brokerless Oslo.Messaging  81      86      1.06<br>
<br></blockquote><div><br></div><div>Although I cannot speak for the other to co-chairs of the Compute track, based on what we discussed we probably want to pass up on this talk.  We wanted our track to focus on technologies that are already available to users instead of blueprints that are still in progress [1][2].  </div>

<div><br></div><div>[1] <a href="https://blueprints.launchpad.net/oslo.messaging/+spec/amqp10-driver-implementation">https://blueprints.launchpad.net/oslo.messaging/+spec/amqp10-driver-implementation</a><br></div><div>[2] <a href="https://review.openstack.org/#/c/75815/">https://review.openstack.org/#/c/75815/</a><br>

</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Consider for other OSS projects:<br>
Scalable Monitoring as a Service for Operations and Customers   69      61      0.88<div class=""><div class="h5"><br>
<br>
Regards,<br>
<br>
<br>
Tom<br>
<br>
______________________________<u></u>_________________<br>
Openstack-track-chairs mailing list<br>
<a href="mailto:Openstack-track-chairs@lists.openstack.org" target="_blank">Openstack-track-chairs@lists.<u></u>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-track-chairs</a><br>
</div></div></blockquote></div><br></div></div>