[Ref Arch, RN7.0] Neutron DVR, VXLAN

- Adds info on Distributed Virtual Router to the
Neutron Network Topologies section of Reference
Architectures.
- Adds info on DVR to the Public and Floating IP
address requirements section.
- Adds info on DVR into the New Features section
of Release Notes.
- Adds info on Neutron VXLAN support into the
New Features section of Release Notes.

Change-Id: Iba077e570c1cd5ce2b002a5b99071dcd0d508329
Implements: blueprint neutron-dvr-deployment
Implements: blueprint neutron-vxlan-support

pages/reference-architecture/6050-neutron-topologies.rst

@@ -36,4 +36,4 @@ to act as a virtual Neutron router in HA (if deploying in HA mode).
 .. include:: /pages/reference-architecture/neutron-intro/0260-neutron-config.rst
 .. include:: /pages/reference-architecture/neutron-intro/0300-neutron-limits.rst
 .. include:: /pages/reference-architecture/neutron-intro/0500-nic-usage.rst
-
+.. include:: /pages/reference-architecture/neutron-intro/0600-neutron-dvr.rst

pages/reference-architecture/network-concepts/6020-public-floating-ip.rst

@@ -48,8 +48,12 @@ Fuel cannot configure Neutron with external workarounds at this time.
   requires one IP address from the Public IP range. This IP address
   goes to the node's bridge to the external network ("br-ex").
 
-* Two additional IP addresses for the environment's Virtual IPs and one for
-  the default gateway are required.
+* Two additional IP addresses for the environment's Virtual IPs and one
+  for the default gateway are required.
+
+* When the Neutron DVR feature is enabled, it requires one additional
+  IP address for each Compute node in case you plan to use Floating IPs
+  in the deployment.
 
 .. note::
 
@@ -172,3 +176,10 @@ addresses:
 
    **n/a** - this value is not applicable to Nova-Network environments.
 
+With DVR enabled, you need to add one additional IP for each Compute
+node in case you plan to use Floating IPs in the deployment. Based on
+the data in the table, for the Public IP range you need:
+
+* for VLAN: (X+N) + 10 = **16**
+
+* For GRE: (X+Z+N) + 10 = **34**

pages/reference-architecture/neutron-intro/0600-neutron-dvr.rst

@@ -0,0 +1,63 @@
+
+.. _neutron-dvr-ref-arch:
+
+Neutron with DVR
+----------------
+
+You can enable Distributed Virtual Routers in Neutron. The following
+diagram shows the implementation of network with Distributed Virtual
+Router enabled:
+
+.. image:: /_images/neutron_dvr_ref-arch.png
+
+When a network configuration requires L3 routers, neutron-server
+distributes the L3 routers across Compute nodes. To enable this
+functionality, each Compute node must have an access to the Public
+network. Enhanced L3 agents are running on each and every Compute node
+(this is not a new agent, this is an updated version of the existing
+L3 agent). The L3 agent can operate in legacy (centralized router) or
+in distributed router mode.
+
+When using Neutron DVR, the L3 agent on Compute node creates one
+new namespace for all the Floating IPs per external network that is
+shared among the tenants. It also creates an external gateway port
+inside each namespace for the external traffic to flow through. This
+port consumes additional IP address from the external network. Such
+namespaces are created on the Compute node only in case there are
+VMs with Floating IP residing on this node.
+
+Inter VM traffic between the tenant's subnets does not need to reach
+the router in the Controller node and is routed locally from the
+Compute node. Also, the Floating IP traffic for a VM from a Compute
+node directly hits the external network from the Compute node instead
+of going through the router on the Controller node. This helps to
+increase performance.
+
+The Metadata agent is distributed as well and is hosted on all Compute
+nodes, and the Metadata Proxy is hosted on all the distributed routers.
+
+This implementation is specific to ML2 with OVS driver. All three
+types of segmentation are supported: GRE, VXLAN, and VLAN.
+
+.. note:: Neutron Distributed Virtual Router provides the legacy SNAT
+   functionality for the default SNAT for all private VMs. SNAT
+   service is not distributed, it is centralized and the service node
+   hosts the service. Since the DVR architecture is not fully
+   fault-tolerant, the outbound traffic for VMs without Floating IPs
+   goes through one L3 agent node and is prone to failure of a single
+   node.
+
+**Requirements**
+
+You can use Neutron with DVR if your environment meets the following
+requirements:
+
+* ML2-OVS/L2-pop
+   DVR feature is supported only by ML2 plugin with OVS mechanism driver.
+   If using tunnel segmentation (VXLAN, GRE), L2 population mechanism
+   should be enabled as well (you can do this in the *Settings* tab of
+   the Fuel web UI).
+
+* OVS and kernel versions
+   Proper operation of DVR requires OpenvSwitch 2.1 or newer, and VXLAN
+   requires kernel 3.13 or newer.

pages/release-notes/v7-0/new_features.rst

@@ -17,7 +17,7 @@ New Features Included in Mirantis OpenStack 7.0
 .. include:: /pages/release-notes/v7-0/new_features/kilo_support.rst
 .. include:: /pages/release-notes/v7-0/new_features/master_node_upgrade.rst
 .. include:: /pages/release-notes/v7-0/new_features/plugins.rst
-
+.. include:: /pages/release-notes/v7-0/new_features/neutron.rst
 
 
 .. seealso::

pages/release-notes/v7-0/new_features/neutron.rst

@@ -0,0 +1,12 @@
+Neutron-related features
+------------------------
+
+Neutron features supported in 7.0
++++++++++++++++++++++++++++++++++
+
+* Neutron Distributed Virtual Router (DVR). Neutron DVR significantly
+  increases performance and eliminates a single point of failure. For
+  more information, see :ref:`Neutron with DVR <neutron-dvr-ref-arch>`.
+
+* Networking options have been amended from VLAN and GRE to VLAN and
+  tunneling. The default tunnel protocol has been changed to VXLAN.