Mirantis, the pure play OpenStack company, is becoming a very strong OpenStack vendor. The company is among the top contributors to OpenStack projects. And one of Mirantis's projects, Fuel, has now been accepted as an OpenStack project.
Fuel is a GUI-based tool that makes it easier for DevOps to install, deploy and manage OpenStack distributions and plugins.
Fuel is not the only OpenStack cloud deployment and configuration tool, however. Puppet remains the most popular tool; Ansible, which was recently acquired by Red Hat, holds the second spot. And OpenStack has its own official deployment tool TripleO.
So how big is Fuel? Mirantis said in a press statement that Fuel is a huge project with 50 percent more code than Nova and 75 percent more commits per month than Neutron.
According to a survey Fuel is the fifth largest deployment and configuration tool beating TripleO, Canonical’s Juju and Red Hat’s Director. And it is used by giants like PayPal, Cisco WebEx, and NASA.
Fuel was initially developed by Mirantis as a closed source project for its internal services team to help accelerate OpenStack implementation projects. In 2013 the company open sourced Fuel under the Apache 2.0 license to bolster its adoption.
But as a Mirantis project it didn’t garner much outside contribution, though the company claims that they did see external contributions from AT&T, Comcast, NTT, Fujitsu, Hitachi, Mellanox, Rackspace and even their top competitor, Red Hat.
That’s what will change with this announcement. By becoming part of the OpenStack Big Tent, and thus no longer a Mirantis-specific project, Fuel will now attract contributions from other OpenStack vendors.
Talking about the next challenge for Fuel, Boris Renski Co-Founder and CMO at Mirantis wrote in a company blog, “We have solved the problem of initial deployment, so the next big challenge for the Fuel team is to simplify the “day 2” operation of OpenStack environments: applying updates, upgrades, configuration changes, adding and removing services and plugins, scaling up and down, logging, monitoring, and alerting. This whole class of problems is often called “lifecycle management,” and remains largely unaddressed by existing tools."
This article is published as part of the IDG Contributor Network. Want to Join?