Fuel Development Examples

Fuel Development Examples

This section provides examples of the Fuel development process. It builds on the information in the How to contribute document, and the Fuel Development Quick-Start Guide which illustrate the development process for a single Fuel component. These examples show how to manage development and integration of a more complicated example.

Any new feature effort should start with the creation of a blueprint where implementation decisions and related commits are tracked. More information on launchpad blueprints can be found here: https://wiki.openstack.org/wiki/Blueprints.

Understanding the Fuel architecture helps you understand which components any particular addition will impact. The following documents provide valuable information about the Fuel architecture, and the provisioning and deployment process:

Adding Zabbix Role

This section outlines the steps followed to add a new role to Fuel. In this case, monitoring service functionality was added by enabling the deployment of a Zabbix server configured to monitor an OpenStack environment deployed by Fuel.

The monitoring server role was initially planned in this blueprint. Core Fuel developers provided feedback to small commits via Gerrit and IRC while the work was coming together. Ultimately the work was rolled up into two commits including over 23k lines of code, and these two commits were merged into fuel-web and fuel-library.

Additions to Fuel-Web for Zabbix role

In fuel-web, the Support for Zabbix commit added the additional role to Nailgun. The reader is urged to review this commit closely as a good example of where specific additions fit. In order to include this as an option in the Fuel deployment process, the following files were included in the commit for fuel-web:

UI components:


Testing additions:


General Nailgun additions:


Additions to Fuel-Library for Zabbix role

In addition to the Nailgun additions, the related Puppet modules were added to the fuel-library repository. This Zabbix fuel-library integration commit included all the puppet files, many of which are brand new modules specifically for Zabbix, in addition to adjustments to the following files:


Once all these commits passed CI and had been reviewed by both community members and the Fuel PTLs, they were merged into master.

Adding Hardware Support

This section outlines the steps followed to add support for a Mellanox network card, which requires a kernel driver that is available in most Linux distributions but was not loaded by default. Adding support for other hardware would touch similar Fuel components, so this outline should provide a reasonable guide for contributors wishing to add support for new hardware to Fuel.

It is important to keep in mind that the Fuel node discovery process works by providing a bootstrap image via PXE. Once the node boots with this image, a basic inventory of hardware information is gathered and sent back to the Fuel controller. If a node contains hardware requiring a unique kernel module, the bootstrap image must contain that module in order to detect the hardware during discovery.

In this example, loading the module in the bootstrap image was enabled by adjusting the ISO makefile and specifying the appropriate requirements.

Adding a hardware driver to bootstrap

The Added bootstrap support to Mellanox commit shows how this is achieved by adding the modprobe call to load the driver specified in the requirements-rpm.txt file, requiring modification of only two files in the fuel-main repository:



Any package specified in the bootstrap building procedure must be listed in the requirements-rpm.txt file explicitly. The Fuel mirrors must be rebuilt by the OSCI team prior to merging requests like this one.


Changes made to bootstrap do not affect package sets for target systems, so in case if you’re adding support for NIC, for example, you have to add installation of all related packages to kickstart/preceed as well.

The Adding OFED drivers installation commit shows the changes made to the preseed (for Ubuntu) and kickstart (for CentOS) files in the fuel-library repository:


Though this example did not require it, if the hardware driver is required during the operating system installation, the installer images (debian-installer and anaconda) would also need to be repacked. For most installations though, ensuring the driver package is available during installation should be sufficient.

Adding to Fuel package repositories

If the addition will be committed back to the public Fuel codebase to benefit others, you will need to submit a bug in the Fuel project to request the package be added to the repositories.

Let’s look at this process step by step by the example of Add neutron-lbaas-agent package bug:

  • you create a bug in the Fuel project providing full description on the packages to be added, and assign it to the Fuel OSCI team
  • you create a request to add these packages to Fuel requirements-*.txt files Add all neutron packages to requirements You receive +1 vote from Fuel CI if these packages already exist on either Fuel internal mirrors or upstream mirrors for respective OS type (rpm/deb), or -1 vote in any other case.
  • if requested packages do not exist in the upstream OS distributive, OSCI team builds them and then places on internal Fuel mirrors
  • OSCI team rebuilds public Fuel mirrors with Add all neutron packages to requirements request
  • Add all neutron packages to requirements request is merged


The package must include a license that complies with the Fedora project license requirements for binary firmware. See the Fedora Project licensing page for more information.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.