diff options
| author |   root <juan.vidal.allende@ericsson.com> | 2017-03-30 09:42:19 +0000 |
|---|---|---|
| committer | root <juan.vidal.allende@ericsson.com> | 2017-03-30 13:03:12 +0000 |
| commit | e61239dbb4f96bb4b798cd3c6e6d6c953d4fcee4 (patch) | |
| tree | 39374f192a83aaa7c19c29b6e6ba2c0afd5e90ba /docs/release/configguide/feature.configuration.rst | |
| parent | 89b68dcce2e79251e38e6231a3556b1bdc5fea79 (diff) | |
Remove references to older releases on documentation
- Rename all Brahmaputra/Colorado links to Danube
- Bumped OvS version from 2.5.90 to 2.6.1
- Bumped ODL version from Boron to Boron SR2
- Changed release date
Change-Id: I4286cbd074b377b4b33e25f33646bb05075f10f5
Signed-off-by: Juan Vidal <juan.vidal.allende@ericsson.com>
Diffstat (limited to 'docs/release/configguide/feature.configuration.rst')
| -rw-r--r-- | docs/release/configguide/feature.configuration.rst | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/release/configguide/feature.configuration.rst b/docs/release/configguide/feature.configuration.rst index f5502082..8bd39436 100644 --- a/docs/release/configguide/feature.configuration.rst +++ b/docs/release/configguide/feature.configuration.rst @@ -12,9 +12,9 @@ SFC feature desciription For details of the scenarios and their provided capabilities refer to the scenario description documents: -- http://artifacts.opnfv.org/sfc/colorado/docs/scenarios_os-odl_l2-sfc-ha/index.html +- http://artifacts.opnfv.org/sfc/danube/docs/scenarios_os-odl_l2-sfc-ha/index.html -- http://artifacts.opnfv.org/sfc/colorado/docs/scenarios_os-odl_l2-sfc-noha/index.html +- http://artifacts.opnfv.org/sfc/danube/docs/scenarios_os-odl_l2-sfc-noha/index.html The SFC feature enables creation of Service Fuction Chains - an ordered list @@ -68,7 +68,7 @@ Pre-configuration activites - Preparing the host to install Fuel by script .. instructions applicable to the deploy tool used in the scenario. Before starting the installation of the SFC scenarios some preparation of the -machine that will host the Colorado Fuel cluster must be done. +machine that will host the Danube Fuel cluster must be done. Installation of required packages --------------------------------- @@ -99,17 +99,17 @@ CI is deploying the scenario. First of all the opnfv-fuel repository needs to be cloned: :: - git clone -b 'stable/colorado' ssh://<user>@gerrit.opnfv.org:29418/fuel + git clone -b 'stable/danube' ssh://<user>@gerrit.opnfv.org:29418/fuel -This command copies the whole colorado branch of repository fuel. +This command copies the whole danube branch of repository fuel. Now download the appropriate OPNFV Fuel ISO into an appropriate folder: :: - wget http://artifacts.opnfv.org/fuel/colorado/opnfv-colorado.1.0.iso + wget http://artifacts.opnfv.org/fuel/danube/opnfv-danube.1.0.iso The exact name of the ISO image may change. -Check https://www.opnfv.org/opnfv-colorado-fuel-users to get the latest ISO. +Check https://www.opnfv.org/opnfv-danube-fuel-users to get the latest ISO. Simplified scenario deployment procedure using Fuel =================================================== @@ -242,7 +242,7 @@ Openvswitch are not provided install them by: If plugins are installed and you want to update them use --force flag. -Note that One may inject other - Colorado compatible - plugins to the Fuel +Note that One may inject other - Danube compatible - plugins to the Fuel Master host using the command scp: scp <plugin>.rpm root@10.20.0.2:<plugin>.rpm |