<div dir="ltr">That's right, we (Fuel devs) are contributing to the TripleO. Our devs contributes into all areas where overlap occurs, and these include TripleO, Ironic and other projects.<div>As we work with the TripleO team, the Fuel team will continue to enhance Fuel based on users demand. Since Fuel has been shipping as part of customer-facing products for about 18 months now, we’re getting some great feedback about what deployment and operation capabilities are needed in production environments on both small and large scale. This makes Fuel a good alternative to TripleO until the two projects reach parity.</div>
<div><br></div><div>Main architectural difference to me is the deployment approach. Fuel deploys (and configures) OpenStack in HA fashion, other (such as MongoDB) components utilizing Puppet. TripleO uses prepared images, which already contain predefined set of roles, and after they are rolled out, only post-configuration is made to the system. TripleO, in this way, seems to be more suited for homogenous deployments, with predefined set of roles for nodes. For Fuel, it was a requirement from the day one to support heterogenous nodes, ability to deploy different combination of roles. While Fuel getting way out of using OS installers to image-based provisioning [1], we see a large demand on ability to support user-defined combination of roles. This leads to such requirements as network setups, disk partitioning layout based on roles applied with allowance for the user to tweak defaults if necessary.</div>
<div><br></div><div>As for Fuel roadmap, we've recently enabled Fuel master node upgrades with the use of LXC & Docker. Current focus is on OpenStack patching & upgrades and pluggable architecture for Fuel, so to make it easily extendable. Obviously, there is a bunch of things we would love to see implemented sooner than later [2], but mentioned are the most important. One of the another important goals is to increase focus on Rally and Tempest to proactively identify areas in OpenStack which need fixing in order to increase robustness, performance, HA-awareness and scalability of OpenStack Core in order to meet increasing users demand.</div>
<div><br></div><div>[1] <a href="http://docs-draft.openstack.org/75/95575/23/check/gate-fuel-specs-docs/52ace98/doc/build/html/specs/5.1/image-based-os-provisioning.html">http://docs-draft.openstack.org/75/95575/23/check/gate-fuel-specs-docs/52ace98/doc/build/html/specs/5.1/image-based-os-provisioning.html</a></div>
<div>[2] <a href="https://blueprints.launchpad.net/fuel">https://blueprints.launchpad.net/fuel</a></div><div><br></div><div>Thanks,</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 9, 2014 at 1:56 AM, Robert Collins <span dir="ltr"><<a href="mailto:robertc@robertcollins.net" target="_blank">robertc@robertcollins.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Well, fuel devs are also hacking on TripleO :) I don't know the exact<br>
timelines but I'm certainly hopeful that we'll see long term<br>
convergence - as TripleO gets more capable, more and more of Fuel<br>
could draw on TripleO facilities, for instance.<br>
<br>
-Rob<br>
<div><div class="h5"><br>
On 9 June 2014 19:41, LeslieWang <<a href="mailto:wqyuwss@hotmail.com">wqyuwss@hotmail.com</a>> wrote:<br>
> Dear all,<br>
><br>
> Seems like both Fuel and TripleO are designed to solve problem of complex<br>
> Openstack installation and Deployment. TripleO is using Heat for<br>
> orchestration. If we can define network creation, OS provision and<br>
> deployment in Heat template, seems like they can achieve similar goal. So<br>
> can anyone explain the difference of these two projects, and future roadmap<br>
> of each of them? Thanks!<br>
><br>
> TripleO is a program aimed at installing, upgrading and operating OpenStack<br>
> clouds using OpenStack's own cloud facilities as the foundations - building<br>
> on nova, neutron and heat to automate fleet management at datacentre scale<br>
> (and scaling down to as few as 2 machines).<br>
><br>
> Fuel is an all-in-one control plane for automated hardware discovery,<br>
> network verification, operating systems provisioning and deployment of<br>
> OpenStack. It provides user-friendly Web interface for installations<br>
> management, simplifying OpenStack installation up to a few clicks.<br>
><br>
> Best Regards<br>
> Leslie<br>
><br>
</div></div>> _______________________________________________<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>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
Robert Collins <<a href="mailto:rbtcollins@hp.com">rbtcollins@hp.com</a>><br>
Distinguished Technologist<br>
HP Converged Cloud<br>
<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>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Mike Scherbakov<br>#mihgen<br><br>
</div>