aboutsummaryrefslogtreecommitdiffstats
path: root/docs/release
diff options
context:
space:
mode:
Diffstat (limited to 'docs/release')
-rw-r--r--docs/release/installation/installation.instruction.rst38
-rw-r--r--docs/release/release-notes/release-notes.rst6
2 files changed, 34 insertions, 10 deletions
diff --git a/docs/release/installation/installation.instruction.rst b/docs/release/installation/installation.instruction.rst
index 80520fed..e24fe27c 100644
--- a/docs/release/installation/installation.instruction.rst
+++ b/docs/release/installation/installation.instruction.rst
@@ -338,7 +338,7 @@ Install additional Plugins/Features on the FUEL node
.. figure:: img/plugin_install.png
- **NOTE**: AArch64 Colorado 1.0 ships only with ODL, OVS, BGPVPN and Tacker
+ **NOTE**: AArch64 Danube 1.0 ships only with ODL, OVS, BGPVPN, SFC and Tacker
plugins, see *Reference 15*.
Create an OpenStack Environment
@@ -350,7 +350,7 @@ Create an OpenStack Environment
.. figure:: img/newenv.png
-#. Select "<Mitaka on Ubuntu 14.04 (aarch64)>" and press <Next>
+#. Select "<Newton on Ubuntu 16.04 (aarch64)>" and press <Next>
#. Select "compute virtulization method".
@@ -547,6 +547,10 @@ Allocate nodes to environment and assign functional roles
OPTIONAL - Set Local Mirror Repos
=================================
+**NOTE**: Support for local mirrors is incomplete in Danube 1.0.
+You may opt in for it to fetch less packages from internet during deployment,
+but an internet connection is still required.
+
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
that can be used for installation / deployment of openstack.
@@ -555,11 +559,11 @@ that can be used for installation / deployment of openstack.
- Replace the URI values for the "Name" values outlined below:
- - "ubuntu" URI="deb http://<ip-of-fuel-server>:8080/mirrors/ubuntu/ trusty main"
+ - "ubuntu" URI="deb http://<ip-of-fuel-server>:8080/mirrors/ubuntu/ xenial main"
- - "mos" URI="deb http://<ip-of-fuel-server>::8080/mitaka-9.0/ubuntu/x86_64 mos9.0 main restricted"
+ - "mos" URI="deb http://<ip-of-fuel-server>::8080/newton-10.0/ubuntu/x86_64 mos10.0 main restricted"
- - "Auxiliary" URI="deb http://<ip-of-fuel-server>:8080/mitaka-9.0/ubuntu/auxiliary auxiliary main restricted"
+ - "Auxiliary" URI="deb http://<ip-of-fuel-server>:8080/newton-10.0/ubuntu/auxiliary auxiliary main restricted"
- Click <Save Settings> at the bottom to Save your changes
@@ -589,6 +593,28 @@ Target specific configuration
.. figure:: img/fuelwsrepsst.png
+#. [AArch64 specific] Use kernel 4.8 for experimental GICv3 features
+
+ **NOTE**: This kernel is required for: SFC scenarios, GICv3 live migration.
+
+ **NOTE**: This kernel is included in the Armband ISO, all that is needed
+ for it to be used in a specific environemnt is to explicitly add it to
+ the list of packages that will be installed by baremetal provisioning.
+
+ In the FUEL UI of your Environment, click the <Settings> tab, click
+ <General> on the left side pane, then at the bottom of the page, in the
+ <Provision> subsection, amend the package list:
+
+ - remove <linux-headers-generic-lts-xenial>;
+
+ - remove <linux-image-generic-lts-xenial>;
+
+ - add <linux-image-4.8.0-9944-generic>;
+
+ - add <linux-headers-4.8.0-9944-generic>;
+
+ - add <linux-image-extra-4.8.0-9944-generic> (optional);
+
#. Set up targets for provisioning with non-default "Offloading Modes"
Some target nodes may require additional configuration after they are
@@ -715,7 +741,7 @@ Fuel
11) `Fuel Plugin Developers Guide <http://docs.openstack.org/developer/fuel-docs/plugindocs/fuel-plugin-sdk-guide.html>`_
12) `(N/A on AArch64) Fuel OpenStack Hardware Compatibility List <https://www.mirantis.com/software/hardware-compatibility/>`_
-Fuel in OPNFV
+Armband Fuel in OPNFV
13) `OPNFV Installation instruction for the AArch64 Danube release of OPNFV when using Fuel as a deployment tool <http://artifacts.opnfv.org/armband/docs/release_installation/index.html>`_
diff --git a/docs/release/release-notes/release-notes.rst b/docs/release/release-notes/release-notes.rst
index cbc2f032..22922fd6 100644
--- a/docs/release/release-notes/release-notes.rst
+++ b/docs/release/release-notes/release-notes.rst
@@ -38,12 +38,12 @@ supplemented with OPNFV unique components such as:
- `OpenDaylight <http://www.opendaylight.org/software>`_
- `Open vSwitch for NFV <https://wiki.opnfv.org/ovsnfv>`_
-- `BGPVPN <http://docs.openstack.org/developer/networking-bgpvpn>`_
- `Tacker <https://wiki.openstack.org/wiki/Tacker>`_
+- `Service Function Chaining <https://wiki.opnfv.org/service_function_chaining>`_
The following OPNFV plugins are not yet ported for AArch64:
-- `Service Function Chaining <https://wiki.opnfv.org/service_function_chaining>`_
+- `BGPVPN <http://docs.openstack.org/developer/networking-bgpvpn>`_
- `SDN distributed routing and VPN <https://wiki.opnfv.org/sdnvpn>`_
- `NFV Hypervisors-KVM <https://wiki.opnfv.org/nfv-kvm>`_
- `VSPERF <https://wiki.opnfv.org/characterize_vswitch_performance_for_telco_nfv_use_cases>`_
@@ -238,5 +238,3 @@ Fuel in OPNFV
14) `OPNFV Build instruction for the AArch64 Danube release of OPNFV when using Fuel as a deployment tool <http://artifacts.opnfv.org/armband/docs/development_overview_build/index.html>`_
15) `OPNFV Release Note for the AArch64 Danube release of OPNFV when using Fuel as a deployment tool <http://artifacts.opnfv.org/armband/docs/release_release-notes/index.html>`_
-
-.. [1] OpenDaylight Boron RC2 is used when Service Function Chaining is enabled in Fuel plugin.