Update the documents for compass E release

JIRA: -

1. Rewrite vm and bm deployment docs to satisfy the new release
2. add some images for network architecture
3. Update release name, version, etc.

Change-Id: I1e9d305de5edf60d937868d49966c153d85fd2b5
Signed-off-by: Yifei Xue <xueyifei@huawei.com>

1 files changed, 41 insertions, 0 deletions

diff --git a/docs/release/scenarios/os-nosdn-nofeature-ha.rst b/docs/release/scenarios/os-nosdn-nofeature-ha.rst
new file mode 100644
index 00000000..f2dce3da
--- /dev/null
+++ b/docs/release/scenarios/os-nosdn-nofeature-ha.rst
@@ -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) Justin Chi (HUAWEI) and Yifei Xue (HUAWEI)
+
+This document introduces scenario descriptions for Euphrates 1.0 of
+deployment with no SDN controller and no feature enabled.
+
+.. contents::
+   :depth: 3
+   :local:
+
+============
+Introduction
+============
+
+This scenario is used to deploy an Ocata OpenStack deployment with
+Ceph Jewel, and without SDN controller nor any NFV feature enabled.
+
+Scenario components and composition
+===================================
+
+This scenario includes a set of common OpenStack services which are Nova,
+Neutron, Glance, Cinder, Keystone, Heat, Ceilometer, Gnocchi, Aodh,
+Horizon. Ceph is used as the backend of Cinder on deployed hosts. HAproxy
+is used to balance all the services running on 3 control nodes behind a
+VIP (Virtual IP address).
+
+Scenario usage overview
+=======================
+
+To deploy with this scenario, you just need to assign the
+os-nosdn-nofeature-ha.yaml to DHA file before deployment.
+
+Limitations, Issues and Workarounds
+===================================
+
+References
+==========
+
+For more information on the OPNFV Euphrates release, please visit
+http://www.opnfv.org/euphrates