From 5bd99052ed055c76efbc479f00edb09b5780cb56 Mon Sep 17 00:00:00 2001 From: cristinapauna Date: Wed, 14 Sep 2016 17:15:18 +0300 Subject: Update documentation with AArch64 specifics The documentationfrom Fuel was introduced to armband project by https://gerrit.opnfv.org/gerrit/#/c/20679/ This patch updates it with aarch64 specifics Change-Id: I05eccef015fd399e7d05a0505e85e733a8e95f1d Signed-off-by: cristinapauna --- docs/buildprocedure/build.instruction.rst | 103 ++++++++++++++++++++---------- docs/buildprocedure/index.rst | 6 +- 2 files changed, 74 insertions(+), 35 deletions(-) (limited to 'docs/buildprocedure') diff --git a/docs/buildprocedure/build.instruction.rst b/docs/buildprocedure/build.instruction.rst index d755ee5f..884fa590 100644 --- a/docs/buildprocedure/build.instruction.rst +++ b/docs/buildprocedure/build.instruction.rst @@ -9,15 +9,15 @@ Abstract ======== This document describes how to build the Fuel deployment tool for the -Colorado release of OPNFV build system, dependencies and required -system resources. +AArch64 Colorado release of OPNFV build system, dependencies and +required system resources. ============ Introduction ============ This document describes the build system used to build the Fuel -deployment tool for the Colorado release of OPNFV, required +deployment tool for the AArch64 Colorado release of OPNFV, required dependencies and minimum requirements on the host to be used for the build system. @@ -29,6 +29,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 ============ @@ -36,14 +40,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: @@ -60,11 +64,21 @@ 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 -- make (simply available through $ sudo apt-get install make) +- fuseiso + +Apart from docker, all other package requirements listed above are +simply available through: + +.. code-block:: bash + + $ sudo apt-get install git make curl fuseiso -- curl (simply available through $ sudo apt-get install curl) ============ Preparations @@ -101,40 +115,40 @@ 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 +- 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: .. code-block:: bash - $ git clone ssh://@gerrit.opnfv.org:29418/fuel + $ git clone ssh://@gerrit.opnfv.org:29418/armband -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 Colorado release: .. code-block:: bash - $ cd fuel + $ cd armband $ git checkout colorado.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. @@ -160,7 +174,7 @@ like: export http_proxy="http://10.0.0.1:8888/" -to /etc/default/docker and restarting the Docker daemon. +to and restarting the Docker daemon. Setting proxy environment variables prior to build -------------------------------------------------- @@ -201,6 +215,17 @@ 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 ================================ @@ -208,7 +233,15 @@ Configure your build environment standard Colorado release ** Select the versions of the components you want to build by editing the -fuel/build/config.mk file. + and + 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 ==================================================== @@ -218,9 +251,9 @@ 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 -completely disable the building of plugins, the environment variable +Only the plugin targets from 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. @@ -228,6 +261,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 and BGPVPN plugins were ported to AArch64. + ======== Building ======== @@ -243,11 +278,15 @@ Low level build method using make The low level method is based on Make: -From the directory, invoke +From the directory, invoke 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 @@ -268,12 +307,12 @@ 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 subdirectory! +the subdirectory! Abstracted build method using build.sh ====================================== -The abstracted build method uses the script which +The abstracted build method uses the script which allows you to: - Create and use a build cache - significantly speeding up the @@ -281,7 +320,7 @@ allows you to: - push/pull cache and artifacts to an arbitrary URI (http(s):, file:, ftp:) -For more info type . +For more info type . ========= Artifacts @@ -289,8 +328,8 @@ Artifacts The artifacts produced are: -- - Which represents the bootable Fuel image, XXXX is - replaced with the build identity provided to the build system +- - Which represents the bootable Fuel for AArch64 image, + XXXX is replaced with the build identity provided to the build system - - Which holds version metadata. @@ -298,8 +337,8 @@ The artifacts produced are: References ========== -1) `OPNFV Installation instruction for the Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/fuel/colorado/docs/installationprocedure/index.html +1) `OPNFV Installation instruction for the AArch64 Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/armband/colorado/docs/installationprocedure/index.html -2) `OPNFV Build instruction for the Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/fuel/colorado/docs/buildprocedure/index.html +2) `OPNFV Build instruction for the AArch64 Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/armband/colorado/docs/buildprocedure/index.html -3) `OPNFV Release Note for the Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/fuel/colorado/docs/releasenotes/index.html +3) `OPNFV Release Note for the AArch64 Colorado release of OPNFV when using Fuel as a deployment tool `_: http://artifacts.opnfv.org/armband/colorado/docs/releasenotes/index.html diff --git a/docs/buildprocedure/index.rst b/docs/buildprocedure/index.rst index 4f88814b..49f64c31 100644 --- a/docs/buildprocedure/index.rst +++ b/docs/buildprocedure/index.rst @@ -4,9 +4,9 @@ .. You should have received a copy of the license along with this work. .. If not, see . -********************************* -Build instruction for Fuel\@OPNFV -********************************* +******************************************** +Build instruction for Fuel\@OPNFV on AArch64 +******************************************** .. toctree:: :numbered: -- cgit 1.2.3-korg