diff options
Diffstat (limited to 'docs/requirements')
| -rw-r--r-- | docs/requirements/01-intro.rst | 10 | ||||
| -rw-r--r-- | docs/requirements/02-use_cases.rst | 22 | ||||
| -rw-r--r-- | docs/requirements/03-architecture.rst | 9 | ||||
| -rw-r--r-- | docs/requirements/04-gaps.rst | 6 | ||||
| -rw-r--r-- | docs/requirements/05-implementation.rst | 3 | ||||
| -rw-r--r-- | docs/requirements/06-summary.rst | 3 | ||||
| -rw-r--r-- | docs/requirements/99-references.rst | 3 | ||||
| -rw-r--r-- | docs/requirements/glossary.rst | 5 | ||||
| -rw-r--r-- | docs/requirements/index.rst | 23 |
9 files changed, 24 insertions, 60 deletions
diff --git a/docs/requirements/01-intro.rst b/docs/requirements/01-intro.rst index a60217b..86fcd7f 100644 --- a/docs/requirements/01-intro.rst +++ b/docs/requirements/01-intro.rst @@ -13,12 +13,14 @@ Edge NFVI location has certain specific requirements related to: 1. Appropriate Tunneling for User Traffic across WAN (Ethernet, IP/MPLS) links #. Appropriate Tunneling for Management Traffic across WAN links -#. Including reachability requirements to the compute platform (‘eth0’ resilience) +#. Including reachability requirements to the compute platform (‘eth0’ resilience, + this also include backup path through other media e.g. 4G/5G) #. Extending Multi-DC management to address many small "DC" locations #. Monitoring Capabilities required for a remote Compute Node #. Squaring Bare Metal with remote survivability and whether IaaS is more appropriate for remote locations +#. Security.As demarcation technology is operated in an un-trusted environment (CSP perspective) + additional means need to be implemented. Similarly, the enterprise might have concerns if + the security architecture is impacted as VNFs provide functions at different locations than + the precious hardware; topics like authentication, authorization, securing the traffic. -Revision: _sha1_ - -Build date: |today| diff --git a/docs/requirements/02-use_cases.rst b/docs/requirements/02-use_cases.rst index 9ed0381..bcadeb8 100644 --- a/docs/requirements/02-use_cases.rst +++ b/docs/requirements/02-use_cases.rst @@ -3,26 +3,25 @@ Use cases and scenarios There are several use cases related to Edge NFV: -1. Isolated vE-CPE. +1. vE-CPE. [vE-CPE]_ is related to most popupar NFV use case where NFVI compute node is - located at customer premises. Typical applications are virtual Firewall and Virtual BGP router; - in simplest case two virtual appliances are hosted at the same CPE compute node. + located at customer premises. Typical applications are virtual Firewall and Virtual BGP router; + VNF chain can be hosted in vE-CPU host and/or DC -#. Distributed VE-CPE. - It is the same as above but at least one virtual appliance is - hosted on another compute node, presumably in DC. +2. Stand-alone vE-CPE. + It is the same as above but all virtual appliances are hosted at the same CPE compute node. -#. Residential GW. - Similar to Isolated vE-CPE, the major difference is scale. Typical VNFs are "WAN fault monitoring", +3. Residential GW. + Similar to vE-CPE, the major difference is scale. Typical VNFs are "WAN fault monitoring", "Performance monitoring". Ratio between deplyed vE-CPE and Residential GW might reach 1:100 or even 1:1000, thus VNF management overhead must be minimized. For instance, self-termination after predefined activity period seems preferable over explicit VNF removing via management system. -#. Distributed Base station. +4. Distributed Base station. TBD. What is the difference for it? -#. Network connectivity. +5. Network connectivity. In most cases CPE is connected to Metro Ethernet [#f1]_ . @@ -30,6 +29,3 @@ There are several use cases related to Edge NFV: .. [#f1] In all above use cases management traffic is coming inband with tenant traffic. -Revision: _sha1_ - -Build date: |today| diff --git a/docs/requirements/03-architecture.rst b/docs/requirements/03-architecture.rst index 3af5667..80750b1 100644 --- a/docs/requirements/03-architecture.rst +++ b/docs/requirements/03-architecture.rst @@ -4,7 +4,10 @@ High level architecture and general features Functional overview ------------------- -Functional overview is here. +We foresee two OpenStack deployment models: + 1. Single-cloud. Centralized OpenStack controller and ENFVI nodes are Compute nodes + 2. Multi-cloud. Each NFVI node contains OpenStack controller, thus it becomes "embedded cloud" + with single compute node Architecture Overview --------------------- @@ -21,7 +24,3 @@ High level northbound interface specification What is northbound here? VIM controller? - -Revision: _sha1_ - -Build date: |today| diff --git a/docs/requirements/04-gaps.rst b/docs/requirements/04-gaps.rst index 6c1bbfb..c0fbc39 100644 --- a/docs/requirements/04-gaps.rst +++ b/docs/requirements/04-gaps.rst @@ -14,7 +14,7 @@ Network related gaps 1GE interfaces are not part of CI. 3. Tunneling technology: - a. Case isolated NFVI - 802.1ad S-VLAN or MPLS. + a. Case stand-alone NFVI - 802.1ad S-VLAN or MPLS. #. Case distributed NFVI - VXLAN or NVGRE over 802.1ad. * VXLAN and NVGRE tunnels don't support OAM check. #. All above tunneling technology don't support integrity check. @@ -58,7 +58,3 @@ Deployment gaps #. Kernel and Hypervisor are hardened. Only OpenStack agents might be added during deployment. #. AMT or IPMI shall not be used for SW deployment. -Revision: _sha1_ - - -Build date: |today| diff --git a/docs/requirements/05-implementation.rst b/docs/requirements/05-implementation.rst index 3dc88bd..ea5b0d9 100644 --- a/docs/requirements/05-implementation.rst +++ b/docs/requirements/05-implementation.rst @@ -35,6 +35,3 @@ Blueprints TBD -Revision: _sha1_ - -Build date: |today| diff --git a/docs/requirements/06-summary.rst b/docs/requirements/06-summary.rst index a8c7477..035f6ba 100644 --- a/docs/requirements/06-summary.rst +++ b/docs/requirements/06-summary.rst @@ -4,6 +4,3 @@ Summary and conclusion TBD -Revision: _sha1_ - -Build date: |today| diff --git a/docs/requirements/99-references.rst b/docs/requirements/99-references.rst index 5548c45..dbf6cab 100644 --- a/docs/requirements/99-references.rst +++ b/docs/requirements/99-references.rst @@ -12,6 +12,3 @@ References and bibliography .. [firewall] OpenStack FW, [Online]. Available at http://docs.openstack.org/juno/config-reference/content/firewalls-default-ports.html -Revision: _sha1_ - -Build date: |today| diff --git a/docs/requirements/glossary.rst b/docs/requirements/glossary.rst index b9a4163..abe0bf6 100644 --- a/docs/requirements/glossary.rst +++ b/docs/requirements/glossary.rst @@ -12,6 +12,8 @@ mapping/translating the OPNFV terms to terminology used in other contexts. CPE Customer Premices Equipment + CSP + Communication Service Provider DC Data Center NFV @@ -23,6 +25,3 @@ mapping/translating the OPNFV terms to terminology used in other contexts. vE-CPE Virtual Enterprise-Customer Premises Equipment -Revision: _sha1_ - -Build date: |today| diff --git a/docs/requirements/index.rst b/docs/requirements/index.rst index 2389aa2..c0efd81 100644 --- a/docs/requirements/index.rst +++ b/docs/requirements/index.rst @@ -1,16 +1,5 @@ -.. ENFV documentation master file, created by - sphinx-quickstart on Tue Nov 03 15:32:31 2015. - You can adapt this file completely to your liking, but it should at least - contain the root `toctree` directive. - -.. image:: ../etc/opnfv-logo.png - :height: 40 - :width: 200 - :alt: OPNFV - :align: left - -Welcome to ENFV's documentation! -================================ +ENFV: Edge NFV requirements project +==================================== Contents: @@ -26,12 +15,4 @@ Contents: 99-references.rst glossary.rst -Indices and tables -================== - -* :ref:`search` - -Revision: _sha1_ - -Build date: |today| |