diff options
author | 2016-09-07 18:47:37 +0200 | |
---|---|---|
committer | 2016-09-07 18:50:57 +0200 | |
commit | b19f458802d93ea37fc46aa6018b6c6c5586cca3 (patch) | |
tree | 649e57dfe4b8b6d8af8b27e40b85e9241411b37f /docs/design/requirements.rst | |
parent | 1d2bdd9241564b0e848888b7f2491afef4ecedca (diff) |
Update from Brahmaputra to Colorado
- Patch Set 2 : fixed broken link
Change-Id: Iec5356ad7fcce4b3125e117b6d14f31ca461bf5d
Signed-off-by: Brady Johnson <brady.allen.johnson@ericsson.com>
Diffstat (limited to 'docs/design/requirements.rst')
-rw-r--r-- | docs/design/requirements.rst | 22 |
1 files changed, 9 insertions, 13 deletions
diff --git a/docs/design/requirements.rst b/docs/design/requirements.rst index 3a790200..1c15a9b9 100644 --- a/docs/design/requirements.rst +++ b/docs/design/requirements.rst @@ -16,29 +16,25 @@ in an OPNFV environment. Detailed Requirements +++++++++++++++++++++ -These are the Brahmaputra specific requirements: +These are the Colorado specific requirements: -1 Placement of SFs on only one Compute node will be supported. +1 The supported Service Chaining encapsulation will be NSH VXLAN-GPE. -2 The supported Service Chaining encapsulation will be NSH VXLAN-GPE. +2 The version of OVS used must support NSH. -3 The version of OVS used must support NSH. +3 The SF VM life cycle will be managed by the Tacker VNF Mgr. -4 The SF VM life cycle will be managed by the Tacker VNF Mgr. +4 The supported classifiers will be either ODL Netvirt or ODL GBP. -5 The supported classifiers will be either ODL Netvirt or ODL GBP. - -6 ODL will be the OpenStack Neutron backend and will handle all networking +5 ODL will be the OpenStack Neutron backend and will handle all networking on the compute nodes. Long Term Requirements ++++++++++++++++++++++ -These requirements are out of the scope of the Brahmaputra release. - -1 Placing SFs on multiple Compute nodes. +These requirements are out of the scope of the Colorado release. -2 Dynamic movement of SFs across multiple Compute nodes. +1 Dynamic movement of SFs across multiple Compute nodes. -3 Load Balancing across multiple SFs +2 Load Balancing across multiple SFs |