<div dir="ltr">Mike,<div><br></div><div>It's great that we are continuing to align fuel with TripleO. I've been toying with the idea of using TripleO components and CEPH to enhance our CI infra for a while now, and this announcement has encouraged me to write it down. I've proposed a BP for "Super fast deploy CI" that would help us perform CI better by "accelerate fuel CI testing by taking reasonable shortcuts integrating with several existing components like TripleO and CEPH".</div>
<div><br></div><div>Blueprint: <a href="https://blueprints.launchpad.net/fuel/+spec/fuel-superfastdeploy-ci">https://blueprints.launchpad.net/fuel/+spec/fuel-superfastdeploy-ci</a></div><div>Pad Spec: <a href="https://etherpad.openstack.org/p/bp-fuel-superfastdeploy-ci">https://etherpad.openstack.org/p/bp-fuel-superfastdeploy-ci</a></div>
<div><br></div><div>--</div><div>Andrew Woodward</div><div>Mirantis</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 12, 2013 at 6:31 AM, Mike Scherbakov <span dir="ltr"><<a href="mailto:mscherbakov@mirantis.com" target="_blank">mscherbakov@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="font-size:13px;font-family:Arial;vertical-align:baseline;white-space:pre-wrap">Folks,</span></p>
<br><span style="font-size:13px;font-family:Arial;vertical-align:baseline;white-space:pre-wrap"></span><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="font-size:13px;font-family:Arial;vertical-align:baseline;white-space:pre-wrap">Most of you by now have heard of Fuel, which we’ve been working on as a related OpenStack project for a period of time -</span><a href="https://github.com/stackforge/fuel-main" style="text-decoration:none" target="_blank"><span style="font-size:13px;font-family:Arial;color:rgb(34,34,34);vertical-align:baseline;white-space:pre-wrap"> </span></a><span style="font-size:13px;font-family:Arial;vertical-align:baseline;white-space:pre-wrap">see </span><a href="https://launchpad.net/fuel" style="text-decoration:none" target="_blank"><span style="font-size:13px;font-family:Arial;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">https://launchpad.net/fuel</span></a><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial"> and </span><a href="https://wiki.openstack.org/wiki/Fuel" style="text-decoration:none" target="_blank"><span style="font-size:13px;font-family:Arial;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">https://wiki.openstack.org/wiki/Fuel</span></a><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial">. The aim of the project is to provide a distribution agnostic and plug-in agnostic engine for preparing, configuring and ultimately deploying various “flavors” of OpenStack in production. We’ve also used Fuel in most of our customer engagements to stand up an OpenStack cloud.</span></p>
<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial"> </span></p><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt">
<span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial">At the same time, we’ve been actively involved with TripleO, which we believe to be a great effort in simplifying deployment, operations, scaling (and eventually upgrading) of OpenStack.</span></p>
<br><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial"></span><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial">Per our discussions with core TripleO team during the Icehouse summit, we’ve uncovered that while there are certain areas of collision, most of the functionality in TripleO and Fuel is complementary. In general, Fuel helps solve many problems around “step zero” of setting up an OpenStack environment, such as auto-discovery and inventory of bare metal hardware, pre-deployment & post-deployment environment checks, and wizard-driven web-based configuration of OpenStack flavors. At the same time, TripleO has made great progress in deployment, scaling and operations (with Tuskar).</span></p>
<br><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial"></span><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial">We’d like to propose an effort for community consideration to bring the two initiatives closer together to eventually arrive at a distribution agnostic, community supported framework covering the entire spectrum of deployment, management and upgrades; from “step zero” to a fully functional and manageable production-grade OpenStack environment.</span></p>
<br><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial"></span><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial">To that effect, we propose the following high-level roadmap plans for this effort: </span></p>
<br><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial"></span><ul style="margin-top:0pt;margin-bottom:0pt"><li dir="ltr" style="vertical-align:baseline;list-style-type:disc;font-size:13px;font-family:Arial">
<p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="font-size:13px;vertical-align:baseline;white-space:pre-wrap">Keep and continue to evolve bare-metal discovery and inventory module of Fuel, tightly integrating it with Ironic.</span></p>
</li><li dir="ltr" style="vertical-align:baseline;list-style-type:disc;font-size:13px;font-family:Arial"><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="font-size:9px;font-family:'Times New Roman';vertical-align:baseline;white-space:pre-wrap"> </span><span style="font-size:13px;vertical-align:baseline;white-space:pre-wrap">Keep and continue to evolve Fuel’s wizard-driven OpenStack flavor configurator. In the near term we’ll work with the UX team to unify the user experience across Fuel, TripleO and Tuskar. We are also thinking about leveraging diskimagebuilder.</span></p>
</li><li dir="ltr" style="vertical-align:baseline;list-style-type:disc;font-size:13px;font-family:Arial"><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="font-size:13px;vertical-align:baseline;white-space:pre-wrap">Continue to evolve Fuel’s pre-deployment (DHCP, L2 connectivity checks) and post-deployment validation checks in collaboration with the TripleO and Tempest teams.</span></p>
</li><li dir="ltr" style="vertical-align:baseline;list-style-type:disc;font-size:13px;font-family:Arial"><p dir="ltr" style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style="font-size:13px;vertical-align:baseline;white-space:pre-wrap">Eventually replace Fuel’s current orchestration engine </span><a href="https://github.com/stackforge/fuel-astute/" style="text-decoration:none" target="_blank"><span style="font-size:13px;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">https://github.com/stackforge/fuel-astute/</span></a><span style="font-size:13px;vertical-align:baseline;white-space:pre-wrap"> with Heat</span></p>
</li></ul><br><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial"></span><span style="vertical-align:baseline;font-size:13px;white-space:pre-wrap;font-family:Arial">We’d love to open discussion on this and hear everybody’s thoughts on this direction.</span></span><span class="HOEnZb"><font color="#888888"><br clear="all">
<div><br></div>-- <br><div dir="ltr"><div>Mike Scherbakov</div><div>Fuel Engineering Lead</div><div>#mihgen</div></div>
</font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>