aboutsummaryrefslogtreecommitdiffstats
path: root/docs/development
diff options
context:
space:
mode:
authorCristina Pauna <cristina.pauna@enea.com>2017-03-22 12:55:10 +0200
committerCristina Pauna <cristina.pauna@enea.com>2017-03-22 12:56:28 +0200
commitb32f9425f4bc80fac6db3f71a17de7be87199e5b (patch)
treecaa9e1a196294f700654d5ededb9f4b2bc2027a3 /docs/development
parentb3ea096a598cacff59722981745d83c2b3cd7a3c (diff)
Update armband documentation for Danube
JIRA: ARMBAND-243 Change-Id: If44f1a9f820793c9b04610fd4db7c05a6675f065 Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
Diffstat (limited to 'docs/development')
-rw-r--r--docs/development/overview/build/build.instruction.rst86
1 files changed, 61 insertions, 25 deletions
diff --git a/docs/development/overview/build/build.instruction.rst b/docs/development/overview/build/build.instruction.rst
index 5fe38cb..6f6cd08 100644
--- a/docs/development/overview/build/build.instruction.rst
+++ b/docs/development/overview/build/build.instruction.rst
@@ -7,7 +7,7 @@ Abstract
========
This document describes how to build the Fuel deployment tool for the
-Danube release of OPNFV build system, dependencies and required
+AArch64 Danube release of OPNFV build system, dependencies and required
system resources.
============
@@ -15,7 +15,7 @@ Introduction
============
This document describes the build system used to build the Fuel
-deployment tool for the Danube release of OPNFV, required
+deployment tool for the AArch64 Danube release of OPNFV, required
dependencies and minimum requirements on the host to be used for the
build system.
@@ -27,6 +27,10 @@ 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.
+
============
Requirements
============
@@ -34,14 +38,14 @@ Requirements
Minimum Hardware Requirements
=============================
-- ~30 GB available disc
+- ~50 GB available disc
- 4 GB RAM
Minimum Software Requirements
=============================
-The build host should run Ubuntu 14.04 or 16.04 operating system.
+The build host should run Ubuntu 14.04 or 16.04 (x86_64) operating system.
On the host, the following packages must be installed:
@@ -58,11 +62,19 @@ On the host, the following packages must be installed:
installation notes for Ubuntu 14.04. Note: use the latest version from
Docker (docker-engine) and not the one in Ubuntu 14.04.
-- git (simply available through $ sudo apt-get install git)
+- git
+
+- make
+
+- curl
+
+Apart from docker, all other package requirements listed above are
+simply available through:
+
+.. code-block:: bash
-- make (simply available through $ sudo apt-get install make)
+ $ sudo apt-get install git make curl
-- curl (simply available through $ sudo apt-get install curl)
============
Preparations
@@ -99,15 +111,15 @@ 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 <https://gerrit.opnfv.org/>
+- Add your generated public key in OPNFV Gerrit (https://gerrit.opnfv.org/)
(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.
-Clone the OPNFV code Git repository with your SSH key
------------------------------------------------------
+Clone the armband@OPNFV code Git repository with your SSH key
+-------------------------------------------------------------
Now it is time to clone the code repository:
@@ -115,24 +127,24 @@ Now it is time to clone the code repository:
$ git clone ssh://<Linux foundation user>@gerrit.opnfv.org:29418/fuel
-Now you should have the OPNFV fuel repository with the Fuel
+Now you should have the OPNFV armband repository with its
directories stored locally on your build host.
Check out the Danube release:
.. code-block:: bash
- $ cd fuel
+ $ cd armband
$ git checkout danube.1.0
-Clone the OPNFV code Git repository without a SSH key
------------------------------------------------------
+Clone the armband@OPNFV code Git repository without a SSH key
+-------------------------------------------------------------
You can also opt to clone the code repository without a SSH key:
.. code-block:: bash
- $ git clone https://gerrit.opnfv.org/gerrit/fuel
+ $ git clone https://gerrit.opnfv.org/gerrit/armband
Make sure to checkout the release tag as described above.
@@ -158,7 +170,7 @@ like:
export http_proxy="http://10.0.0.1:8888/"
-to /etc/default/docker and restarting the Docker daemon.
+to </etc/default/docker> and restarting the Docker daemon.
Setting proxy environment variables prior to build
--------------------------------------------------
@@ -199,6 +211,16 @@ 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):
+
+.. code-block:: bash
+
+ $ make patches-import
+
+
Configure your build environment
================================
@@ -206,7 +228,15 @@ Configure your build environment
standard Danube release **
Select the versions of the components you want to build by editing the
-fuel/build/config.mk file.
+<armband/upstream/fuel/build/config.mk> and
+<armband/upstream/fuel/build/armband.mk> files.
+
+Note! The same observation as above, before altering Makefile, run:
+
+.. code-block:: bash
+
+ $ make patches-import
+
Non official build: Selecting which plugins to build
====================================================
@@ -216,8 +246,8 @@ 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 fuel/build/f_isoroot/Makefile that are
-specified in the environment variable will then be built. In order to
+Only the plugin targets from <armband/upstream/fuel/build/armband.mk> 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
@@ -226,6 +256,8 @@ 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.
+
========
Building
========
@@ -241,11 +273,15 @@ Low level build method using make
The low level method is based on Make:
-From the <fuel/build> directory, invoke <make [target]>
+From the <armband> directory, invoke <make [target]>
Following targets exist:
-- none/all - this will:
+- release - this will do the same as:
+
+ - make submodules-clean patches-import build
+
+- none/all/build - this will:
- Initialize the docker build environment
@@ -266,7 +302,7 @@ Following targets exist:
- 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 <fuel/build/release> subdirectory!
+the <armband/upstream/fuel/build/release> subdirectory!
Abstracted build method using build.sh
======================================
@@ -279,7 +315,7 @@ allows you to:
- push/pull cache and artifacts to an arbitrary URI (http(s):, file:, ftp:)
-For more info type <fuel/ci/build.sh -h>.
+For more info type <armband/ci/build.sh -h>.
=========
Artifacts
@@ -287,7 +323,7 @@ Artifacts
The artifacts produced are:
-- <OPNFV_XXXX.iso> - Which represents the bootable Fuel image, XXXX is
- replaced with the build identity provided to the build system
+- <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.