SFC design Documents for Brahmaptura release

- Patch set 9  : Addressed Jim Guichard's review comments.
- Patch set 10 : Removed date and revision as its duplicated, according to
                 Chris' review comments.

Change-Id: Idca9696c4b703a3ef93b553fe785449cea0935f0
Signed-off-by: Brady Johnson <brady.allen.johnson@ericsson.com>
(cherry picked from commit de5689105582602e6f2a453bfe9da196cdfc0a99)

1 files changed, 39 insertions, 2 deletions

diff --git a/docs/design/requirements.rst b/docs/design/requirements.rst
index dbedc6f7..3a716351 100644
--- a/docs/design/requirements.rst
+++ b/docs/design/requirements.rst
@@ -1,4 +1,41 @@
 Requirements
-============
+------------
+
+This section defines requirements for the initial OPNFV SFC implementation,
+including those requirements driving upstream project enhancements.
+
+Minimal Viable Requirement
+++++++++++++++++++++++++++
+
+Deploy a complete SFC solution by integrating OpenDaylight SFC with OpenStack
+in an OPNFV environment.
+
+Detailed Requirements
++++++++++++++++++++++
+
+These are the Brahmaputra specific requirements:
+
+1 Placement of SFs on only one Compute node will be supported.
+
+2 The supported Service Chaining encapsulation will be NSH VXLAN-GPE.
+
+3 The version of OVS used must support NSH.
+
+4 The SF VM life cycle will be managed by the Tacker VNF Mgr.
+
+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
+  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.
+
+2 Dynamic movement of SFs across multiple Compute nodes.
+
+3 Load Balancing across multiple SFs
 
-This section will define requirements for the initial OPNFV SFC implementation, including those requirements driving upstream project enhancements.