diff options
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>2016-05-12 18:44:28 +0200
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>2016-05-27 14:44:15 +0000
commit124fcac9d87df19ef6653442370d41b6248b6439 (patch)
parent3e535448fe1bad43d810d9b2ccf66f13bb7c10e5 (diff)
docs/install-instr: Add target specific cfg sect.
Fuel 8.0 adds support for setting up "Offloading Modes" for target nodes. Document how this features should be used (and why/when it's necessary), and also its common limitation of not being applied during Verify Networks step (see related Fuel bug report [1]). While at it, fix minor reference to branch in git tag checkout instructions, as we'd be in detached HEAD and not on a new branch. [1] https://jira.opnfv.org/browse/FUEL-134 [Alexandru.Avadanii@enea.com] Only minor edits and prepared for upstreaming, this is mostly based on previous work from Florin. Change-Id: If7a8ca44541903dbeb6db36bc64fe56b132165cb Signed-off-by: Florin Dumitrascu <florin.dumitrascu@enea.com> Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit a89517cafe2819cbe7c64e2a0653950150910a47)
-rw-r--r--docs/img/fuelconsole1.pngbin0 -> 8269 bytes
-rw-r--r--docs/img/offloadingmodes.pngbin0 -> 23017 bytes
3 files changed, 50 insertions, 1 deletions
diff --git a/docs/img/fuelconsole1.png b/docs/img/fuelconsole1.png
new file mode 100644
index 0000000..61703ca
--- /dev/null
+++ b/docs/img/fuelconsole1.png
Binary files differ
diff --git a/docs/img/offloadingmodes.png b/docs/img/offloadingmodes.png
new file mode 100644
index 0000000..5b3cb17
--- /dev/null
+++ b/docs/img/offloadingmodes.png
Binary files differ
diff --git a/docs/installation-instruction.rst b/docs/installation-instruction.rst
index 787287a..6016393 100644
--- a/docs/installation-instruction.rst
+++ b/docs/installation-instruction.rst
@@ -53,7 +53,7 @@ opnfv/fuel git repository. To retrieve the repository for the Brahmaputra relea
$git clone https://<linux foundation uid>@gerrit.opnf.org/gerrit/fuel
-Check-out the Brahmaputra release tag to set the branch to the
+Check-out the Brahmaputra release tag to set the HEAD to the
baseline required to replicate the Brahmaputra release:
$ git checkout brahmaputra.1.0
@@ -534,6 +534,55 @@ that can be used for installation / deployment of openstack.
- Click <Save Settings> at the bottom to Save your changes
+Target specific configuration
+#. Set up targets for provisioning with non-default "Offloading Modes"
+ Some target nodes may require additional configuration after they are
+ PXE booted (bootstrapped); the most frequent changes are in defaults
+ for ethernet devices' "Offloading Modes" settings (e.g. some targets'
+ ethernet drivers may strip VLAN traffic by default).
+ If your target ethernet drivers have wrong "Offloading Modes" defaults,
+ in "Configure interfaces" page (described above), expand affected
+ interface's "Offloading Modes" and [un]check the relevant settings
+ (see figure below):
+ .. figure:: img/offloadingmodes.png
+#. Set up targets for "Verify Networks" with non-default "Offloading Modes"
+ **NOTE**: Check *Reference 15* for an updated and comprehensive list of
+ known issues and/or limitations, including "Offloading Modes" not being
+ applied during "Verify Networks" step.
+ Setting custom "Offloading Modes" in Fuel GUI will only apply those settings
+ during provisiong and **not** during "Verify Networks", so if your targets
+ need this change, you have to apply "Offloading Modes" settings by hand
+ to bootstrapped nodes.
+ **E.g.**: Our driver has "rx-vlan-filter" default "on" (expected "off") on
+ the Openstack interface(s) "eth1", preventing VLAN traffic from passing
+ during "Verify Networks".
+ - From Fuel master console identify target nodes admin IPs (see figure below):
+ .. code-block:: bash
+ $ fuel nodes
+ .. figure:: img/fuelconsole1.png
+ - SSH into each of the target nodes and disable "rx-vlan-filter" on the
+ affected physical interface(s) allocated for OpenStack traffic (eth1):
+ .. code-block:: bash
+ $ ssh root@ ethtool -K eth1 rx-vlan-filter off
+ - Repeat the step above for all affected nodes/interfaces in the POD.
Verify Networks