Draft of the introduction of the requirements doc

Change-Id: I2cf4d0dc72f83c81363e689c0abb1c91b7bdbcee
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>

3 files changed, 114 insertions, 10 deletions

diff --git a/docs/requirements/glossary.rst b/docs/requirements/glossary.rst
index ea731f3..bbef60f 100644
--- a/docs/requirements/glossary.rst
+++ b/docs/requirements/glossary.rst
@@ -10,23 +10,52 @@ mapping/translating the OPNFV terms to terminology used in other contexts.
 
 .. glossary::
 
+    API
+        Application Programming Interface.
+
+    Cloud Computing
+        A model that enables access to a shared pool of configurable computing
+        resources, such as networks, servers, storage, applications, and
+        services, that can be rapidly provisioned and released with minimal
+        management effort or service provider interaction.
+
+    Edge Computing
+        Edge computing pushes applications, data and computing power (services)
+        away from centralized points to the logical extremes of a network.
+
+    Instance
+        Refers in OpenStack terminology to a running VM, or a VM in a known
+        state such as suspended, that can be used like a hardware server.
+
     NFV
-        Network Function Virtualization
+        Network Function Virtualization.
 
     NFVI
-        Network Function Virtualization Infrastructure; totality of all hardware
+        Network Function Virtualization Infrastructure. Totality of all hardware
         and software components which build up the environment in which VNFs are
         deployed.
 
+    SDN
+        Software-Defined Networking. Emerging architecture that decouples the
+        network control and forwarding functions, enabling the network control
+        to become directly programmable and the underlying infrastructure to be
+        abstracted for applications and network services.
+
+    Server
+        Computer that provides explicit services to the client software running
+        on that system, often managing a variety of computer operations. In
+        OpenStack terminology, a server is a VM instance.
+
     VIM
-        Virtualized Infrastructure Manager; functional block that is responsible
+        Virtualized Infrastructure Manager. Functional block that is responsible
         for controlling and managing the NFVI compute, storage and network
         resources, usually within one operator's Infrastructure Domain, e.g.
         NFVI Point of Presence (NFVI-PoP).
 
-    Virtual Machine (VM)
-        Virtualized computation environment that behaves very much like a
-        physical computer/server.
+    VM
+        Virtual Machine. Virtualized computation environment that behaves like a
+        physical computer/server by (re-)creating the computing architecture of a
+        real or hypothetical computer.
 
     Virtual network
         Virtual network routes information among the network interfaces of VM
@@ -34,6 +63,9 @@ mapping/translating the OPNFV terms to terminology used in other contexts.
         connectivity.
 
     VNF
-        Virtualized Network Function. Implementation of an Network Function that
-        can be deployed on a Network Function Virtualization Infrastructure
-        (NFVI).
+        Virtualized Network Function. Implementation of an Network Function
+        that can be deployed on a Network Function Virtualization
+        Infrastructure (NFVI).
+
+    WAN
+        Wide Area Network.
diff --git a/docs/requirements/index.rst b/docs/requirements/index.rst
index 8636377..3a0ec26 100644
--- a/docs/requirements/index.rst
+++ b/docs/requirements/index.rst
@@ -6,6 +6,8 @@ NetReady: Network Readiness
 ***************************
 
 :Project: NetReady, https://wiki.opnfv.org/display/netready/NetReady
+:Editors: TBD
+:Authors: Georg Kunz (Ericsson), <add your name here>
 
 :Abstract: OPNFV provides an infrastructure with different SDN controller
            options to realize NFV functionality on the platform it builds. As
diff --git a/docs/requirements/introduction.rst b/docs/requirements/introduction.rst
index b1672e5..378578e 100644
--- a/docs/requirements/introduction.rst
+++ b/docs/requirements/introduction.rst
@@ -4,4 +4,74 @@
 Introduction
 ============
 
-TBD
+This document represents and describes the results of the OPNFV NetReady
+(Network Readiness) project. Specifically, the document comprises a selection of
+NFV-related networking use cases and their networking requirements, a
+corresponding gap analysis of the aforementioned requirements with respect to
+the current OpenStack networking architecture and a description of potential
+solutions and improvements.
+
+
+Scope
+-----
+
+NetReady is a project within the OPNFV initiative. Its focus is on NFV (Network
+Function Virtualization) related networking use cases and their requirements on
+the underlying NFVI (Network Function Virtualization Infrastructure).
+
+The NetReady project addresses the OpenStack networking architecture,
+specifically OpenStack Neutron, from a NFV perspective. Its goal is to identify
+gaps in the current OpenStack networking architecture with respect to NFV
+requirements and to propose and evaluate improvements and potential complementary
+solutions.
+
+
+Problem Description
+-------------------
+
+Traditionally, OpenStack networking, represented typically by the OpenStack
+Neutron project, targets virtualized data center networking. This comprises
+primarily establishing and managing layer 2 network connectivity among VMs
+(Virtual Machines). Over the past releases of OpenStack, Neutron has accumulated
+an extensive feature set, covering L2 and L3 networking features such as <list
+of examples>.
+
+It is often stated that NFV imposes additional requirements on the networking
+architecture and feature set of the underlying NFVI beyond those of data center
+networking. For instance, the NFVI needs to establish and manage connectivity
+beyond the data center to the WAN (Wide Area Network). Moreover, NFV networking
+use cases often abstract from L2 connectivity and for example focus on L3-only
+connectivity. Hence, the NFVI networking architecture needs to be flexible
+enough to be able to meet the requirements of NFV-related use cases in addition
+to traditional data center networking.
+
+It is an ongoing debate how well the current OpenStack networking architecure
+can meet the additional requirements of NFV networking. Hence, a thorough
+analysis of NFV networking requirements and their relation to the OpenStack
+networking architecture is needed.
+
+
+Goals
+-----
+
+The goals of the NetReady project and correspondingly this document are the
+following:
+
+- This document comprises a collection of relevant NFV networking use cases and
+  clearly describes their requirements on the NFVI. These requirements are
+  stated independently of a particular implementation, for instance OpenStack
+  Neutron. Instead, requirements are formulated in terms of APIs (Application
+  Programming Interfaces) and data models needed to realize a given NFV use
+  case.
+
+- The list of use cases is not considered to be all-emcompassing but it
+  represents a carefully selected set of use cases that are considered to be
+  relevant at the time of writing. More use cases may be added over time.
+
+- This document contains a thorough analysis of the gaps in the current
+  OpenStack networking architecture with respect to the requirements imposed
+  by the selected NFV use cases.
+
+- This document describes the proposed improvements and complementary solutions
+  needed to enable OpenStack to fulfill the identified NFV requirements.
+