Mirantis Fuel – Openstack installation for Noddy

While we have lots of experience working with cloud automation tools, for OpenStack in particular, it has taken us a little while to get around to checking out Fuel from Mirantis. Here, we give a short summary of our initial impressions of this very interesting tool.

Fuel is primarily a system for deploying Openstack to a set of nodes. It was developed by Mirantis to make their own deployment work easier and they released it to the community. The latest version (v4.0) has been bundled into Mirantis Openstack and is not available separately – don’t waste time looking for a standalone variant of Fuel . (Download here – login required).

Fuel makes it ridiculously easy to get a basic Openstack cluster up and running. A small bit of preparation – mostly on networking in general and switch configuration in particular – is necessary and once this is set up, deployment of your first Openstack cluster is entirely plug and play: just plug the Fuel Master and your servers into the switch and hit deploy.

While the system is generally very easy to use, there were a few smaller points which were not obvious to us from the outset:

  • a dedicated Fuel Master node is required – this cannot be easily run on, say, a VM in a laptop. We used a rather basic Core 2 Duo machine as Fuel Master – it’s probably not recommended, but it worked;
  • The switch configuration is of course important – there were some small differences between the switch config scripts provided in the documentation and the that assumed for the basic installation which became apparent when things did not work out of the box – they were quite easy to fix, however;
    • there is a network test option within Fuel which we only found later – this should be run before deploying;
  • We had a small issue that our spanking new servers did not have their RAID disks activated coming from the factory meaning that our servers were reporting no disk capacity. Fuel did not fall over, but it did not highlight this as an issue and it did appear to enter a somewhat confused state.

Once those basic points were corrected, the Fuel install on the master did a deploy on our 3 node system (1 controller, 2 compute nodes, no internet connection) in about half an hour.

Yep – even Noddy could do this. He might need Big Ears to maintain it, though…


  1. Roman Alekseenkov

    28. January 2014 at 22:35

    Thank you for the feedback! You are welcome to file bugs and improvements via https://launchpad.net/fuel

    Don’t hesitate to contact me directly if you have any questions about Fuel.


    • Sean Murphy

      29. January 2014 at 8:44

      Hi Roman – great work on the tool – it’s v easy to use. I’ll file a bug report for the no disk capacity issue I mentioned (just need to reproduce it and report properly). As I kind of hint at in the article – I think the network test option could be made more apparent (and probably run before the deployment by default) – I’m sure it would save time in lots of cases, but then I guess you guys already know this ­čśë

      • Hello,

        Could You please report about how to resolve this no-disk issue. I’m trying to deploy on a bunch of older serwers with some old adaptec controles. As far as raid1 is used the disks are not recognized by fuel at all. What is interesting i can see those disks at the bootstrap CLI.

Leave a Reply

Your email address will not be published. Required fields are marked *