docs: Sync latest Fuel updates 35/46135/1
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Mon, 23 Oct 2017 15:53:12 +0000 (17:53 +0200)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Mon, 23 Oct 2017 15:54:29 +0000 (17:54 +0200)
Change-Id: I88e2a3f59ccada34dcc88e0b4d864721e6d3242e
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
docs/release/installation/installation.instruction.rst
docs/release/release-notes/release-notes.rst
docs/release/scenarios/os-nosdn-ovs-ha/index.rst [new file with mode: 0644]
docs/release/scenarios/os-nosdn-ovs-ha/os-nosdn-ovs-ha.rst [new file with mode: 0644]
docs/release/scenarios/os-nosdn-ovs-noha/index.rst [new file with mode: 0644]
docs/release/scenarios/os-nosdn-ovs-noha/os-nosdn-ovs-noha.rst [new file with mode: 0644]

index fbf22d1..1b624d2 100644 (file)
@@ -249,7 +249,7 @@ These steps are common both for virtual and baremetal deploys.
 
    .. code-block:: bash
 
-       $ git checkout 5.0.0
+       $ git checkout 5.0.2
 
 #. Start the deploy script
 
@@ -270,7 +270,7 @@ Examples
       $ ci/deploy.sh -b file:///home/jenkins/tmpdir/securedlab \
                      -l ericsson \
                      -p virtual_kvm \
-                     -s os-nosdn-nofeature-noha \
+                     -s os-nosdn-nofeature-noha
 
 #. Baremetal deploy
 
@@ -292,7 +292,7 @@ An aarch64 deploy on pod5 from Arm lab
                      -l arm \
                      -p pod5 \
                      -s os-nosdn-nofeature-ha \
-                     -B pxebr \
+                     -B pxebr
 
 
 =============
index b20b4df..6e1b534 100644 (file)
@@ -61,7 +61,7 @@ Release Data
 | **Project**                          | fuel/armband                         |
 |                                      |                                      |
 +--------------------------------------+--------------------------------------+
-| **Repo/tag**                         | opnfv-5.0.0                          |
+| **Repo/tag**                         | opnfv-5.0.2                          |
 |                                      |                                      |
 +--------------------------------------+--------------------------------------+
 | **Release designation**              | Euphrates 5.0                        |
diff --git a/docs/release/scenarios/os-nosdn-ovs-ha/index.rst b/docs/release/scenarios/os-nosdn-ovs-ha/index.rst
new file mode 100644 (file)
index 0000000..af0105b
--- /dev/null
@@ -0,0 +1,16 @@
+.. _os-nosdn-ovs-ha1:
+
+.. This work is licensed under a Creative Commons Attribution 4.0 International Licence.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) 2017 Mirantis Inc., Enea Software AB and others
+
+========================================
+os-nosdn-ovs-ha overview and description
+========================================
+
+.. toctree::
+   :numbered:
+   :maxdepth: 2
+
+   os-nosdn-ovs-ha.rst
+
diff --git a/docs/release/scenarios/os-nosdn-ovs-ha/os-nosdn-ovs-ha.rst b/docs/release/scenarios/os-nosdn-ovs-ha/os-nosdn-ovs-ha.rst
new file mode 100644 (file)
index 0000000..5e30ab5
--- /dev/null
@@ -0,0 +1,42 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c)2017 Mirantis Inc., Enea Software AB and others
+
+This document provides scenario level details for Euphrates 5.0 of
+deployment with no SDN controller and no extra features enabled.
+
+============
+Introduction
+============
+
+This scenario is used primarily to validate and deploy a Ocata 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. It also installs
+the DPDK-enabled Open vSwitch component.
+
+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.
+
+
+Scenario usage overview
+=======================
+
+Simply deploy this scenario by using the os-nosdn-ovs-ha.yaml deploy
+settings file.
+
+Limitations, Issues and Workarounds
+===================================
+
+None
+
+References
+==========
+
+For more information on the OPNFV Euphrates release, please visit
+http://www.opnfv.org/euphrates
diff --git a/docs/release/scenarios/os-nosdn-ovs-noha/index.rst b/docs/release/scenarios/os-nosdn-ovs-noha/index.rst
new file mode 100644 (file)
index 0000000..066abc9
--- /dev/null
@@ -0,0 +1,16 @@
+.. _os-nosdn-ovs-noha1:
+
+.. This work is licensed under a Creative Commons Attribution 4.0 International Licence.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) 2017 Mirantis Inc., Enea Software AB and others
+
+==========================================
+os-nosdn-ovs-noha overview and description
+==========================================
+
+.. toctree::
+   :numbered:
+   :maxdepth: 2
+
+   os-nosdn-ovs-noha.rst
+
diff --git a/docs/release/scenarios/os-nosdn-ovs-noha/os-nosdn-ovs-noha.rst b/docs/release/scenarios/os-nosdn-ovs-noha/os-nosdn-ovs-noha.rst
new file mode 100644 (file)
index 0000000..7ac4e11
--- /dev/null
@@ -0,0 +1,41 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. (c) 2017 Mirantis Inc., Enea Software AB and others
+
+This document provides scenario level details for Euphrates 5.0 of
+deployment with no SDN controller and no extra features enabled.
+
+============
+Introduction
+============
+
+This scenario is used primarily to validate and deploy a Ocata 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. It also installs
+the DPDK-enabled Open vSwitch component.
+
+
+Scenario usage overview
+=======================
+
+Simply deploy this scenario by using the os-nosdn-ovs-ha.yaml deploy
+settings file.
+
+
+Limitations, Issues and Workarounds
+===================================
+
+Tested on virtual deploy only.
+
+References
+==========
+
+For more information on the OPNFV Euphrates release, please visit
+http://www.opnfv.org/euphrates
+