diff options
author | billyom <billy.o.mahony@intel.com> | 2016-10-18 10:11:03 +0100 |
---|---|---|
committer | billyom <billy.o.mahony@intel.com> | 2016-10-19 11:53:51 +0100 |
commit | 5be83facc4d003b1d34afbd887865317cfdfd5ef (patch) | |
tree | 04cbd075fd2d1fe512e3a1b3df82c13a3d30fbec /docs | |
parent | bcdf6b71395f50ccdcac66fc23fd04b29e395291 (diff) |
Fix doc links for Colorado 2.0
Change-Id: Ib8006c05624a92c2e2f1f61075dd1d2e246d4d0e
Signed-off-by: Billy O'Mahony <billy.o.mahony@intel.com>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/scenarios/os-nosdn-ovs/scenario.description.rst | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/docs/scenarios/os-nosdn-ovs/scenario.description.rst b/docs/scenarios/os-nosdn-ovs/scenario.description.rst index 03e732c..04d88a1 100644 --- a/docs/scenarios/os-nosdn-ovs/scenario.description.rst +++ b/docs/scenarios/os-nosdn-ovs/scenario.description.rst @@ -4,16 +4,19 @@ Introduction ============ -This scenario installs the latest DPDK-enabled Open vSwitch component, +For Fuel this scenario installs the latest DPDK-enabled Open vSwitch component, version - 2.5.90 based on DPDK 16.07. +For Apex this scenario installs the latest DPDK-enabled Open vSwitch component, +version - 2.5.90 based on DPDK 16.04. + Scenario components and composition =================================== This scenario is currently able to be installed using the Fuel and Apex installers. For details on how to install the ovsnfv scenarion using these installer tools please refer to the installation instructions at: - * Fuel installation instruction: http://artifacts.opnfv.org/colorado/fuel/docs/installation-instruction.html - * Apex installation instruction: http://artifacts.opnfv.org/colorado/apex/docs/installation-instruction/index.html + * Fuel installation instruction: http://artifacts.opnfv.org/fuel/colorado/2.0/docs/installation-instruction/index.html + * Apex installation instruction: http://artifacts.opnfv.org/apex/colorado/2.0/docs/installation-instruction/index.html .. Above links need to be updated with the eventual release URL's. This will need to be done closer to the .. release date once the project and docs team have a solution ready and the final version of the installation |