diff options
| author |   root <juan.vidal.allende@ericsson.com> | 2017-03-30 09:42:19 +0000 |
|---|---|---|
| committer |   Manuel Buil <mbuil@suse.com> | 2017-03-30 17:05:14 +0000 |
| commit | a6f40087fd15131c50d5cf3594d0ef702cdc40db (patch) | |
| tree | 7261b07567a000a04671d6482d835c32dc4c8493 /docs/development/design/requirements.rst | |
| parent | 6a9c9e69da60996ed3b738dd71b744df61cec9d7 (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>
(cherry picked from commit e61239dbb4f96bb4b798cd3c6e6d6c953d4fcee4)
Diffstat (limited to 'docs/development/design/requirements.rst')
| -rw-r--r-- | docs/development/design/requirements.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/development/design/requirements.rst b/docs/development/design/requirements.rst index 1c15a9b9..6d35d946 100644 --- a/docs/development/design/requirements.rst +++ b/docs/development/design/requirements.rst @@ -16,15 +16,15 @@ in an OPNFV environment. Detailed Requirements +++++++++++++++++++++ -These are the Colorado specific requirements: +These are the Danube specific requirements: 1 The supported Service Chaining encapsulation will be NSH VXLAN-GPE. 2 The version of OVS used must support NSH. -3 The SF VM life cycle will be managed by the Tacker VNF Mgr. +3 The SF VM life cycle will be managed by the Tacker VNF Manager. -4 The supported classifiers will be either ODL Netvirt or ODL GBP. +4 The supported classifier is OpenDaylight NetVirt. 5 ODL will be the OpenStack Neutron backend and will handle all networking on the compute nodes. @@ -32,7 +32,7 @@ These are the Colorado specific requirements: Long Term Requirements ++++++++++++++++++++++ -These requirements are out of the scope of the Colorado release. +These requirements are out of the scope of the Danube release. 1 Dynamic movement of SFs across multiple Compute nodes. |