diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/buildprocedure/build.instruction.rst | 103 | ||||
| -rw-r--r-- | docs/buildprocedure/index.rst | 6 | ||||
| -rw-r--r-- | docs/installationprocedure/img/fuelmenu2a.png | bin | 0 -> 11511 bytes | |||
| -rw-r--r-- | docs/installationprocedure/img/fuelwsrepsst.png (renamed from docs/img/fuelwsrepsst.png) | bin | 59206 -> 59206 bytes | |||
| -rw-r--r-- | docs/installationprocedure/img/plugins_aarch64.png | bin | 0 -> 60058 bytes | |||
| -rw-r--r-- | docs/installationprocedure/index.rst | 6 | ||||
| -rw-r--r-- | docs/installationprocedure/installation.instruction.rst | 107 | ||||
| -rw-r--r-- | docs/releasenotes/index.rst | 6 | ||||
| -rw-r--r-- | docs/releasenotes/release-notes.rst | 60 |
9 files changed, 186 insertions, 102 deletions
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 <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: .. code-block:: bash - $ git clone ssh://<Linux foundation user>@gerrit.opnfv.org:29418/fuel + $ git clone ssh://<Linux foundation user>@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 </etc/default/docker> 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. +<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 ==================================================== @@ -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 <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 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 <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 @@ -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 <fuel/build/release> subdirectory! +the <armband/upstream/fuel/build/release> subdirectory! Abstracted build method using build.sh ====================================== -The abstracted build method uses the <fuel/ci/build.sh> script which +The abstracted build method uses the <armband/ci/build.sh> 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 <fuel/ci/build.sh -h>. +For more info type <armband/ci/build.sh -h>. ========= Artifacts @@ -289,8 +328,8 @@ 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. @@ -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>`_: 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>`_: 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>`_: 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>`_: 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>`_: 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>`_: 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 <http://creativecommons.org/licenses/by/4.0/>. -********************************* -Build instruction for Fuel\@OPNFV -********************************* +******************************************** +Build instruction for Fuel\@OPNFV on AArch64 +******************************************** .. toctree:: :numbered: diff --git a/docs/installationprocedure/img/fuelmenu2a.png b/docs/installationprocedure/img/fuelmenu2a.png Binary files differnew file mode 100644 index 00000000..396c1237 --- /dev/null +++ b/docs/installationprocedure/img/fuelmenu2a.png diff --git a/docs/img/fuelwsrepsst.png b/docs/installationprocedure/img/fuelwsrepsst.png Binary files differindex 90ded440..90ded440 100644 --- a/docs/img/fuelwsrepsst.png +++ b/docs/installationprocedure/img/fuelwsrepsst.png diff --git a/docs/installationprocedure/img/plugins_aarch64.png b/docs/installationprocedure/img/plugins_aarch64.png Binary files differnew file mode 100644 index 00000000..a824aebc --- /dev/null +++ b/docs/installationprocedure/img/plugins_aarch64.png diff --git a/docs/installationprocedure/index.rst b/docs/installationprocedure/index.rst index 8e61be21..ed4db110 100644 --- a/docs/installationprocedure/index.rst +++ b/docs/installationprocedure/index.rst @@ -4,9 +4,9 @@ .. You should have received a copy of the license along with this work. .. If not, see <http://creativecommons.org/licenses/by/4.0/>. -**************************************** -Installation instruction for Fuel\@OPNFV -**************************************** +*************************************************** +Installation instruction for Fuel\@OPNFV on AArch64 +*************************************************** .. toctree:: :numbered: diff --git a/docs/installationprocedure/installation.instruction.rst b/docs/installationprocedure/installation.instruction.rst index 5dedb148..00ca1032 100644 --- a/docs/installationprocedure/installation.instruction.rst +++ b/docs/installationprocedure/installation.instruction.rst @@ -9,8 +9,9 @@ Abstract ======== This document describes how to install the Colorado release of -OPNFV when using Fuel as a deployment tool, covering its usage, -limitations, dependencies and required system resources. +OPNFV when using Fuel as a deployment tool, with an AArch64 (only) +target node pool. It covers its usage, limitations, dependencies +and required system resources. ============ Introduction @@ -18,7 +19,8 @@ Introduction This document provides guidelines on how to install and configure the Colorado release of OPNFV when using Fuel as a -deployment tool, including required software and hardware configurations. +deployment tool, with an AArch64 (only) target node pool, +including required software and hardware configurations. Although the available installation options give a high degree of freedom in how the system is set-up, including architecture, services @@ -34,26 +36,27 @@ networking and Unix/Linux administration. Preface ======= -Before starting the installation of the Colorado release of -OPNFV, using Fuel as a deployment tool, some planning must be +Before starting the installation of the AArch64 Colorado 1.0 release +of OPNFV, using Fuel as a deployment tool, some planning must be done. Retrieving the ISO image ======================== First of all, the Fuel deployment ISO image needs to be retrieved, the -Fuel .iso image of the Colorado release can be found at *Reference: 2* +ArmbandFuel .iso image of the AArch64 Colorado release can be found +at *Reference: 2* Building the ISO image ====================== -Alternatively, you may build the Fuel .iso from source by cloning the -opnfv/fuel git repository. To retrieve the repository for the Colorado -release use the following command: +Alternatively, you may build the Armband Fuel .iso from source by cloning +the opnfv/armband git repository. To retrieve the repository for the AArch64 +Colorado 1.0 release use the following command: .. code-block:: bash - $ git clone https://gerrit.opnfv.org/gerrit/fuel + $ git clone https://gerrit.opnfv.org/gerrit/armband Check-out the Colorado release tag to set the HEAD to the baseline required to replicate the Colorado release: @@ -62,11 +65,11 @@ baseline required to replicate the Colorado release: $ git checkout colorado.1.0 -Go to the fuel directory and build the .iso: +Go to the armband directory and build the .iso: .. code-block:: bash - $ cd fuel/build; make all + $ cd armband; make all For more information on how to build, please see *Reference: 14* @@ -77,7 +80,7 @@ Next, familiarize yourself with Fuel by reading the following documents: - Fuel Installation Guide, please see *Reference: 8* -- Fuel User Guide, please see *Reference: 9* +- Fuel QuickStart, please see *Reference: 9* - Fuel Developer Guide, please see *Reference: 10* @@ -110,13 +113,13 @@ Hardware requirements ===================== The following minimum hardware requirements must be met for the -installation of Colorado using Fuel: +installation of AArch64 Colorado 1.0 using Fuel: +--------------------+------------------------------------------------------+ | **HW Aspect** | **Requirement** | | | | +====================+======================================================+ -| **# of nodes** | Minimum 5 (3 for non redundant deployment): | +| **AArch64 nodes** | Minimum 5 (3 for non redundant deployment): | | | | | | - 1 Fuel deployment master (may be virtualized) | | | | @@ -126,7 +129,7 @@ installation of Colorado using Fuel: | | - 1 Compute (1 co-located Ceph-OSD role) | | | | +--------------------+------------------------------------------------------+ -| **CPU** | Minimum 1 socket x86_AMD64 with Virtualization | +| **CPU** | Minimum 1 socket AArch64 (ARMv8) with Virtualization | | | support | +--------------------+------------------------------------------------------+ | **RAM** | Minimum 16GB/server (Depending on VNF work load) | @@ -135,6 +138,8 @@ installation of Colorado using Fuel: | **Disk** | Minimum 256GB 10kRPM spinning disks | | | | +--------------------+------------------------------------------------------+ +| **Firmware** | UEFI compatible (e.g. EDK2) with PXE support | ++--------------------+------------------------------------------------------+ | **Networks** | 4 Tagged VLANs (PUBLIC, MGMT, STORAGE, PRIVATE) | | | | | | 1 Un-Tagged VLAN for PXE Boot - ADMIN Network | @@ -143,6 +148,8 @@ installation of Colorado using Fuel: | | or spread out over multiple NICs as your hardware | | | supports. | +--------------------+------------------------------------------------------+ +| **1 x86_64 node** | - 1 Fuel deployment master, x86 (may be virtualized) | ++--------------------+------------------------------------------------------+ =============================== Help with Hardware Requirements @@ -150,8 +157,6 @@ Help with Hardware Requirements Calculate hardware requirements: -For information on compatible hardware types available for use, please see *Reference: 11*. - When choosing the hardware on which you will deploy your OpenStack environment, you should think about: @@ -199,7 +204,7 @@ reference platform stack across a server cluster. Install Fuel master =================== -#. Mount the Colorado Fuel ISO file/media as a boot device to the jump host server. +#. Mount the Colorado Armband Fuel ISO file/media as a boot device to the jump host server. #. Reboot the jump host to establish the Fuel server. @@ -225,10 +230,17 @@ Install Fuel master #. In the "Network Setup" section - Configure DHCP/Static IP information for your FUEL node - For example, ETH0 is 10.20.0.2/24 for FUEL booting and ETH1 is DHCP in your corporate/lab network (see figure below). - - Configure eth1 or other network interfaces here as well (if you have them present on your FUEL server). +- **NOTE**: ArmbandFuel@OPNFV requires internet connectivity during bootstrap + image building, due to missing arm64 (AArch64) packages in the partial + local Ubuntu mirror (consequence of ports.ubuntu.com mirror architecture). + + - Configuration of ETH1 interface for connectivity into your corporate/lab + network is mandatory, as internet connection is required during deployment. .. figure:: img/fuelmenu2.png + .. figure:: img/fuelmenu2a.png + #. In the "PXE Setup" section (see figure below) - Change the following fields to appropriate values (example below): - DHCP Pool Start 10.20.0.3 @@ -256,11 +268,14 @@ Install Fuel master .. figure:: img/fuelmenu4.png -#. OPTION TO ENABLE PROXY SUPPORT - In the "Bootstrap Image" section (see figure below), edit the following fields to define a proxy. (**NOTE:** cannot be used in tandem with local repository support) +#. **DO NOT CHANGE** anything in "Bootstrap Image" section (see figure below). - - Navigate to "HTTP proxy" and enter your http proxy address + In ArmbandFuel@OPNFV, this data is **NOT** actually used for bootstrap + image building. Any change here will replace the configuration from + the OPNFV bootstrap build scripts and will lead to a failed bootstrap + image build. - - Select <Check> and press [Enter] + **NOTE:** Cannot be used in tandem with local repository support. .. figure:: img/fuelmenu5.png @@ -276,7 +291,7 @@ Install Fuel master #. Start the installation. - - Select Quit Setup and press Save and Quit. + - Press <F8> - The installation will now start, wait until the login screen is shown. @@ -288,9 +303,15 @@ the login prompt, you should boot the Node Servers (Your Compute/Control/Storage blades, nested or real) with a PXE booting scheme so that the FUEL Master can pick them up for control. +**NOTE**: AArch64 target nodes are expected to support PXE booting an +EFI binary, i.e. an EFI-stubbed GRUB2 bootloader. + +**NOTE**: UEFI (EDK2) firmware is **highly** recommended, becoming +the **de facto** standard for ARMv8 nodes. + #. Enable PXE booting - - For every controller and compute server: enable PXE Booting as the first boot device in the BIOS boot order menu, and hard disk as the second boot device in the same menu. + - For every controller and compute server: enable PXE Booting as the first boot device in the UEFI (EDK2) boot order menu, and hard disk as the second boot device in the same menu. #. Reboot all the control and compute blades. @@ -323,6 +344,9 @@ Install additional Plugins/Features on the FUEL node .. figure:: img/plugin_install.png + **NOTE**: AArch64 Colorado 1.0 ships only with ODL, OVS and BGPVPN plugins, + see *Reference 15*. + Create an OpenStack Environment =============================== @@ -332,7 +356,7 @@ Create an OpenStack Environment .. figure:: img/newenv.png -#. Select "<Mitaka on Ubuntu 14.04>" and press <Next> +#. Select "<Mitaka on Ubuntu 14.04 (aarch64)>" and press <Next> #. Select "compute virtulization method". @@ -342,7 +366,7 @@ Create an OpenStack Environment - Select "Neutron with ML2 plugin" - - Select "Neutron with tunneling segmentation" (Required when using the ODL or ONOS plugins) + - Select "Neutron with tunneling segmentation" (Required when using the ODL plugin) - Press <Next> @@ -477,7 +501,7 @@ Enable Plugins - Enable and configure the plugins of your choice - .. figure:: img/plugins.png + .. figure:: img/plugins_aarch64.png Allocate nodes to environment and assign functional roles ========================================================= @@ -490,7 +514,7 @@ Allocate nodes to environment and assign functional roles - Click on the <+Add Nodes> button - - Check <Controller>, <Telemetry - MongoDB> and optionally an SDN Controller role (OpenDaylight controller/ONOS) in the "Assign Roles" Section. + - Check <Controller>, <Telemetry - MongoDB> and optionally an SDN Controller role (OpenDaylight controller) in the "Assign Roles" Section. - Check one node which you want to act as a Controller from the bottom half of the screen @@ -526,8 +550,17 @@ Allocate nodes to environment and assign functional roles .. figure:: img/interfaceconf.png -OPTIONAL - Set Local Mirror Repos -================================= +OPTIONAL - UNTESTED - Set Local Mirror Repos +=========================================== + +**NOTE**: AArch64 Colorado 1.0 does not fully support local Ubuntu mirrors, +or at least does not ship with arm64 packages in local repos by default. +In order to use local (partial) Ubuntu mirrors, one should add arm64 packages +by hand to the existing amd64 mirrors and re-generate repo metadata. +Local MOS/Auxiliary repos contain packages for both amd64 and arm64. + +**NOTE**: Below instruction assume you already added (by hand) arm64 +Ubuntu necessary packages to the local repository! The following steps must be executed if you are in an environment with no connection to the Internet. The Fuel server delivers a local repo @@ -662,6 +695,8 @@ Installation health-check - Allow tests to run and investigate results where appropriate + - Check *Reference 15* for known issues / limitations on AArch64 + .. figure:: img/health.png ========== @@ -696,19 +731,19 @@ Fuel 8) `Fuel Installation Guide <http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide.html>`_: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-install-guide.html -9) `Fuel User Guide <http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide.html>`_: http://docs.openstack.org/developer/fuel-docs/userdocs/fuel-user-guide.html +9) `Fuel QuickStart Guide <https://docs.mirantis.com/openstack/fuel/fuel-9.0/quickstart-guide.html>`_: https://docs.mirantis.com/openstack/fuel/fuel-9.0/quickstart-guide.html 10) `Fuel Developer Guide <http://docs.openstack.org/developer/fuel-docs/devdocs/develop.html>`_: http://docs.openstack.org/developer/fuel-docs/devdocs/develop.html 11) `Fuel Plugin Developers Guide <http://docs.openstack.org/developer/fuel-docs/plugindocs/fuel-plugin-sdk-guide.html>`_: http://docs.openstack.org/developer/fuel-docs/plugindocs/fuel-plugin-sdk-guide.html -12) `Fuel OpenStack Hardware Compatibility List <https://www.mirantis.com/products/openstack-drivers-and-plugins/hardware-compatibility-list>`_: https://www.mirantis.com/products/openstack-drivers-and-plugins/hardware-compatibility-list +12) `(N/A on AArch64) Fuel OpenStack Hardware Compatibility List <https://www.mirantis.com/products/openstack-drivers-and-plugins/hardware-compatibility-list>`_: https://www.mirantis.com/products/openstack-drivers-and-plugins/hardware-compatibility-list Fuel in OPNFV ============= -13) `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>`_: http://artifacts.opnfv.org/fuel/colorado/docs/installationprocedure/index.html +13) `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>`_: http://artifacts.opnfv.org/armband/colorado/docs/installationprocedure/index.html -14) `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>`_: http://artifacts.opnfv.org/fuel/colorado/docs/buildprocedure/index.html +14) `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>`_: http://artifacts.opnfv.org/armband/colorado/docs/buildprocedure/index.html -15) `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>`_: http://artifacts.opnfv.org/fuel/colorado/docs/releasenotes/index.html +15) `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>`_: http://artifacts.opnfv.org/armband/colorado/docs/releasenotes/index.html diff --git a/docs/releasenotes/index.rst b/docs/releasenotes/index.rst index db97a749..91fedf23 100644 --- a/docs/releasenotes/index.rst +++ b/docs/releasenotes/index.rst @@ -4,9 +4,9 @@ .. You should have received a copy of the license along with this work. .. If not, see <http://creativecommons.org/licenses/by/4.0/>. -***************************** -Release notes for Fuel\@OPNFV -***************************** +**************************************** +Release notes for Fuel\@OPNFV on AArch64 +**************************************** .. toctree:: :numbered: diff --git a/docs/releasenotes/release-notes.rst b/docs/releasenotes/release-notes.rst index fa9e98e0..e87699e2 100644 --- a/docs/releasenotes/release-notes.rst +++ b/docs/releasenotes/release-notes.rst @@ -9,18 +9,25 @@ Abstract ======== This document compiles the release notes for the Colorado 1.0 release of -OPNFV when using Fuel as a deployment tool. +OPNFV when using Fuel as a deployment tool, with an AArch64 (only) target +node pool. =============== Important notes =============== These notes provides release information for the use of Fuel as deployment -tool for the Colorado 1.0 release of OPNFV. +tool for the AArch64 Colorado 1.0 release of OPNFV. -The goal of the Colorado release and this Fuel-based deployment process is -to establish a lab ready platform accelerating further development -of the OPNFV infrastructure. +The goal of the AArch64 Colorado release and this Fuel-based deployment process +is to establish a lab ready platform accelerating further development +of the OPNFV on AArch64 infrastructure. + +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. + +Although not currently supported, mixing x86_64 and AArch64 architectures +inside the target pool will be possible later. Carefully follow the installation-instructions provided in *Reference 13*. @@ -28,11 +35,17 @@ Carefully follow the installation-instructions provided in *Reference 13*. Summary ======= -For Colorado, the typical use of Fuel as an OpenStack installer is +For AArch64 Colorado, the typical use of Fuel as an OpenStack installer is supplemented with OPNFV unique components such as: - `OpenDaylight <http://www.opendaylight.org/software>`_ version "Beryllium SR3" [1]_ - 'http://www.opendaylight.org/software' +- `Open vSwitch for NFV <https://wiki.opnfv.org/ovsnfv>`_ 'https://wiki.opnfv.org/ovsnfv' + +- `BGPVPN <http://docs.openstack.org/developer/networking-bgpvpn>`_ 'http://docs.openstack.org/developer/networking-bgpvpn/' + +The following OPNFV plugins are not yet ported for AArch64: + - `ONOS <http://onosproject.org/>`_ version "Drake" - 'http://onosproject.org/' - `Service function chaining <https://wiki.opnfv.org/service_function_chaining>`_ 'https://wiki.opnfv.org/service_function_chaining' @@ -41,8 +54,6 @@ supplemented with OPNFV unique components such as: - `NFV Hypervisors-KVM <https://wiki.opnfv.org/nfv-kvm>`_ 'https://wiki.opnfv.org/nfv-kvm' -- `Open vSwitch for NFV <https://wiki.opnfv.org/ovsnfv>`_ 'https://wiki.opnfv.org/ovsnfv' - - `VSPERF <https://wiki.opnfv.org/characterize_vswitch_performance_for_telco_nfv_use_cases>`_ 'https://wiki.opnfv.org/characterize_vswitch_performance_for_telco_nfv_use_cases' As well as OPNFV-unique configurations of the Hardware- and Software stack. @@ -60,7 +71,7 @@ OPNFV CI pipeline including: - build-instructions -- The Colorado Fuel installer image (.iso) built by Jenkins +- The Colorado Fuel installer image AArch64 (.iso) built by Jenkins - Automated deployment of Colorado with running on bare metal or a nested hypervisor environment (KVM) @@ -71,13 +82,13 @@ Release Data ============ +--------------------------------------+--------------------------------------+ -| **Project** | fuel | +| **Project** | armband | | | | +--------------------------------------+--------------------------------------+ | **Repo/tag** | colorado.1.0 | | | | +--------------------------------------+--------------------------------------+ -| **Release designation** | Colorado 1.0 follow-up release | +| **Release designation** | Colorado 1.0 main release | | | | +--------------------------------------+--------------------------------------+ | **Release date** | September 22 2016 | @@ -86,11 +97,8 @@ Release Data | **Purpose of the delivery** | Colorado alignment to Released | | | Fuel 9.0 baseline + Bug-fixes for | | | the following feaures/scenarios: | -| | - NFV Hypervisors-KVM | | | - Open vSwitch for NFV | | | - OpenDaylight | -| | - SDN distributed routing and VPN | -| | - Service function chaining | | | | +--------------------------------------+--------------------------------------+ @@ -99,7 +107,7 @@ Version change Module version changes ---------------------- -This is a follow-up release to Colorado 1.0. It is based on +This is a main release. It is based on following upstream versions: - Fuel 9.0 Base release @@ -108,12 +116,11 @@ following upstream versions: - OpenDaylight Beryllium SR3 release [1]_ -- ONOS Drake release Document changes ---------------- -This is a follow-up release to Colorado 1.0. It -comes with the following documentation: +This is a main release. +It comes with the following documentation: - Installation instructions - *Reference 13* - **Changed** @@ -136,7 +143,7 @@ Bug corrections **JIRA TICKETS:** -`Workarounds <https://jira.opnfv.org/issues/?filter=11121>`_ 'https://jira.opnfv.org/issues/?filter=11121' +`Workarounds <https://jira.opnfv.org/issues/?filter=11175>`_ 'https://jira.opnfv.org/issues/?filter=11175' (Also See respective Integrated feature project's bug tracking) @@ -146,7 +153,7 @@ Deliverables Software deliverables --------------------- -Fuel-based installer iso file found in *Reference 2* +AArch64 Fuel-based installer iso file found in *Reference 2* Documentation deliverables -------------------------- @@ -172,13 +179,16 @@ System Limitations - **Max number of networks:** 65k +- **Fuel master arch:** x86_64 + +- **Target node arch:** aarch64 Known issues ============ **JIRA TICKETS:** -`Known issues <https://jira.opnfv.org/issues/?filter=11119>`_ 'https://jira.opnfv.org/issues/?filter=11119' +`Known issues <https://jira.opnfv.org/issues/?filter=11176>`_ 'https://jira.opnfv.org/issues/?filter=11176' (Also See respective Integrated feature project's bug tracking) @@ -187,7 +197,7 @@ Workarounds **JIRA TICKETS:** -`Workarounds <https://jira.opnfv.org/issues/?filter=11120>`_ 'https://jira.opnfv.org/issues/?filter=11120' +- (Also See respective Integrated feature project's bug tracking) @@ -241,10 +251,10 @@ Fuel Fuel in OPNFV ============= -13) `OPNFV Installation instruction for the Colorado release of OPNFV when using Fuel as a deployment tool <http://artifacts.opnfv.org/fuel/colorado/docs/installation-instruction.html>`_ 'http://artifacts.opnfv.org/fuel/colorado/docs/installation-instruction.html' +13) `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>`_ 'http://artifacts.opnfv.org/armband/colorado/docs/installationprocedure/index.html' -14) `OPNFV Build instruction for the Colorado release of OPNFV when using Fuel as a deployment tool <http://artifacts.opnfv.org/fuel/colorado/docs/build-instruction.html>`_ 'http://artifacts.opnfv.org/fuel/colorado/docs/build-instruction.html' +14) `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>`_ 'http://artifacts.opnfv.org/armband/colorado/docs/buildprocedure/index.html' -15) `OPNFV Release Note for the Colorado release of OPNFV when using Fuel as a deployment tool <http://artifacts.opnfv.org/fuel/colorado/docs/release-notes.html>`_ 'http://artifacts.opnfv.org/fuel/colorado/docs/release-notes.html' +15) `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>`_ 'http://artifacts.opnfv.org/armband/colorado/docs/releasenotes/index.html' .. [1] OpenDaylight Boron RC2 is used when Service Function Chaining is enabled in Fuel plugin. |
