Adds apex owned scenario release notes

Change-Id: Ia7b50b99b82a01d347ba673e354d80cbb65e608f
Signed-off-by: Tim Rozet <trozet@redhat.com>

2 files changed, 73 insertions, 0 deletions

diff --git a/docs/release/scenarios/os-nosdn-performance-ha/index.rst b/docs/release/scenarios/os-nosdn-performance-ha/index.rst
new file mode 100644
index 00000000..e0dbca7f
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-performance-ha/index.rst
@@ -0,0 +1,15 @@
+.. _os-nosdn-performance-ha:
+
+.. This work is licensed under a Creative Commons Attribution 4.0 International Licence.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) <optionally add copywriters name>
+
+================================================
+os-nosdn-performance-ha overview and description
+================================================
+
+.. toctree::
+   :numbered:
+   :maxdepth: 4
+
+   os-nosdn-performance-ha.rst
diff --git a/docs/release/scenarios/os-nosdn-performance-ha/os-nosdn-performance-ha.rst b/docs/release/scenarios/os-nosdn-performance-ha/os-nosdn-performance-ha.rst
new file mode 100644
index 00000000..8f941286
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-performance-ha/os-nosdn-performance-ha.rst
@@ -0,0 +1,58 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) <optionally add copywriters name>
+
+This document provides scenario level details for Danube 1.0 of
+deployment with no SDN controller and performance options enabled.
+
+.. contents::
+   :depth: 3
+   :local:
+
+============
+Introduction
+============
+
+This scenario is used primarily to demonstrate the performance settings and
+capabilities in Apex. This scenario will  deploy a Newton OpenStack
+deployment without any NFV features or SDN controller enabled.
+
+Scenario components and composition
+===================================
+
+This scenario is composed of common OpenStack services enabled by default,
+including Nova, Neutron, Glance, Cinder, Keystone, Horizon.  Optionally and
+by default, Tacker and Congress services are also enabled.  Ceph is used as
+the backend storage to Cinder on all deployed nodes.
+
+All services are in HA, meaning that there are multiple cloned instances of
+each service, and they are balanced by HA Proxy using a Virtual IP Address
+per service.
+
+The main purpose of this scenario is to serve as an example to show how to
+set optional performance settings in an Apex deploy settings file.
+
+Scenario usage overview
+=======================
+
+The performance options listed in os-nosdn-performance-ha.yaml give an example
+of the different options a user can set in any deploy settings file.  Some
+of these performance options are actually required for other scenarios which
+rely on DPDK.  Options under the nova section like 'libvirtpin' allow a
+user to choose which core to pin nova instances to on the overcloud compute
+node.  Options under 'kernel' allow a user to set kernel specific arguments
+at boot, which include options like hugepages, isolcpus, enabling iommu, etc.
+
+
+Limitations, Issues and Workarounds
+===================================
+
+* `APEX-389 <https://jira.opnfv.org/browse/APEX-389>`_:
+   Compute kernel parameters are applied to all nodes
+
+References
+==========
+
+For more information on the OPNFV Danube release, please visit
+http://www.opnfv.org/danube
+