Build instruction for Fuel@OPNFV on AArch64

1. Abstract

This document describes how to build the Fuel deployment tool for the AArch64 Danube release of OPNFV build system, dependencies and required system resources.

2. Introduction

This document describes the build system used to build the Fuel deployment tool for the AArch64 Danube release of OPNFV, required dependencies and minimum requirements on the host to be used for the build system.

The Fuel build system is designed around Docker containers such that dependencies outside of the build system can be kept to a minimum. It also shields the host from any potential dangerous operations performed by the build system.

The audience of this document is assumed to have good knowledge in network and Unix/Linux administration.

Due to early docker and nodejs support on AArch64, we will still use an x86_64 Fuel Master to build and deploy an AArch64 target pool, as well as an x86_64 build machine for building the OPNFV ISO.

3. Requirements

3.1. Minimum Hardware Requirements

  • ~50 GB available disc
  • 4 GB RAM

3.2. Minimum Software Requirements

The build host should run Ubuntu 14.04 or 16.04 (x86_64) operating system.

On the host, the following packages must be installed:

  • An x86_64 host (Bare-metal or VM) with Ubuntu 14.04 LTS installed
    • Note: Builds on Wily (Ubuntu 15.x) are currently not supported
    • A kernel equal- or later than 3.19 (Vivid), simply available through
$ sudo apt-get install linux-generic-lts-vivid

Apart from docker, all other package requirements listed above are simply available through:

$ sudo apt-get install git make curl

4. Preparations

4.1. Setting up the Docker build container

After having installed Docker, add yourself to the docker group:

$ sudo usermod -a -G docker [userid]

Also make sure to define relevant DNS servers part of the global DNS chain in your </etc/default/docker> configuration file. Uncomment, and modify the values appropriately.

For example:

DOCKER_OPTS=" --dns= --dns="

Then restart docker:

$ sudo service docker restart

4.1.1. Setting up OPNFV Gerrit in order to being able to clone the code

  • Start setting up OPNFV gerrit by creating a SSH key (unless you don’t already have one), create one with ssh-keygen
  • Add your generated public key in OPNFV Gerrit ( (this requires a Linux foundation account, create one if you do not already have one)
  • Select “SSH Public Keys” to the left and then “Add Key” and paste your public key in.

4.1.2. Clone the armband@OPNFV code Git repository with your SSH key

Now it is time to clone the code repository:

$ git clone ssh://<Linux foundation user>

Now you should have the OPNFV armband repository with its directories stored locally on your build host.

Check out the Danube release:

$ cd armband
$ git checkout danube.3.0

4.1.3. Clone the armband@OPNFV code Git repository without a SSH key

You can also opt to clone the code repository without a SSH key:

$ git clone

Make sure to checkout the release tag as described above.

4.2. Support for building behind a http/https/rsync proxy

The build system is able to make use of a web proxy setup if the http_proxy, https_proxy, no_proxy (if needed) and RSYNC_PROXY or RSYNC_CONNECT_PROG environment variables have been set before invoking make.

The proxy setup must permit port 80 (http) and 443 (https). Rsync protocol is currently not used during build process.

4.2.1. Important note about the host Docker daemon settings

The Docker daemon on the host must be configured to use the http proxy for it to be able to pull the base Ubuntu 14.04 image from the Docker registry before invoking make! In Ubuntu this is done by adding a line like:

export http_proxy=""

to </etc/default/docker> and restarting the Docker daemon.

4.2.2. Setting proxy environment variables prior to build

The build system will make use the following environment variables that needs to be exported to subshells by using export (bash) or setenv (csh/tcsh).

http_proxy (or HTTP_PROXY)
https_proxy (or HTTP_PROXY)
no_proxy (or NO_PROXY)

As an example, these are the settings that were put in the user’s .bashrc when verifying the proxy build functionality:

export http_proxy=
export https_proxy=
export no_proxy=localhost,,,.sock

4.2.3. Using a ssh proxy for the rsync connection

If the proxy setup is not allowing the rsync protocol, an alternative solution is to use a SSH tunnel to a machine capable of accessing the outbound port 873. Set the RSYNC_CONNECT_PROG according to the rsync manual page (for example to “ssh <username>@<hostname> nc %H 873”) to enable this. Also note that netcat needs to be installed on the remote system!

Make sure that the ssh command also refers to the user on the remote system, as the command itself will be run from the Docker build container as the root user (but with the invoking user’s SSH keys).

Note! Armband build system uses git submodules to track fuel and other upstream repos, so in order to apply the above change, one should first initialize the submodules and apply armband patches (only needed once):

$ make fuel-patches-import

4.3. Configure your build environment

** Configuring the build environment should not be performed if building standard Danube release **

Select the versions of the components you want to build by editing <armband/>.

Note! The same observation as above, before altering Makefile, run:

$ make fuel-patches-import

4.4. Non official build: Selecting which plugins to build

In order to cut the build time for unofficial builds (made by an individual developer locally), the selection if which Fuel plugins to build (if any) can be done by environment variable “BUILD_FUEL_PLUGINS” prior to building.

Only the plugin targets from <armband/> that are specified in the environment variable will then be built. In order to completely disable the building of plugins, the environment variable is set to ” ”. When using this functionality, the resulting iso file will be prepended with the prefix “unofficial-” to clearly indicate that this is not a full build.

This method of plugin selection is not meant to be used from within Gerrit!

Note! So far, only ODL, OVS, BGPVPN and Tacker plugins were ported to AArch64.

5. Building

There are two methods available for building Fuel:

  • A low level method using Make
  • An abstracted method using

5.1. Low level build method using make

The low level method is based on Make:

From the <armband> directory, invoke <make [target]>

Following targets exist:

  • release - this will do the same as:
    • make submodules-clean fuel-patches-import build
  • none/all/build - this will:
    • Initialize the docker build environment
    • Build Fuel from upstream (as defined by fuel-build/config-spec)
    • Build the OPNFV defined plugins/features from upstream
    • Build the defined additions to fuel (as defined by the structure of this framework)
    • Apply changes and patches to fuel (as defined by the structure of this framework)
    • Reconstruct a fuel .iso image
  • clean - this will remove all artifacts from earlier builds.
  • debug - this will simply enter the build container without starting a build, from here you can start a build by enter “make iso”

If the build is successful, you will find the generated ISO file in the <armband/upstream/fuel/build/release> subdirectory!

5.2. Abstracted build method using

The abstracted build method uses the <fuel/ci/> script which allows you to:

  • Create and use a build cache - significantly speeding up the build time if upstream repositories have not changed.
  • push/pull cache and artifacts to an arbitrary URI (http(s):, file:, ftp:)

For more info type <armband/ci/ -h>.

6. Artifacts

The artifacts produced are:

  • <OPNFV_XXXX.iso> - Which represents the bootable Fuel for AArch64 image, XXXX is replaced with the build identity provided to the build system
  • <OPNFV_XXXX.iso.txt> - Which holds version metadata.