From 55427ec21a17cd601a4abb2cab4de4694ba1a702 Mon Sep 17 00:00:00 2001 From: Tim Rozet Date: Thu, 30 Mar 2017 22:08:05 -0400 Subject: More doc updates for Danube Change-Id: I125548acde034d8c4c85cce93fb001ba06c8ab33 Signed-off-by: Tim Rozet (cherry picked from commit 1d655538cfe9a665c5e12dc8b910ddaaae21bae7) --- docs/release/installation/architecture.rst | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) (limited to 'docs/release/installation/architecture.rst') diff --git a/docs/release/installation/architecture.rst b/docs/release/installation/architecture.rst index ae634cc4..eff5d35d 100644 --- a/docs/release/installation/architecture.rst +++ b/docs/release/installation/architecture.rst @@ -30,7 +30,7 @@ Undercloud ---------- The undercloud is not Highly Available. End users do not depend on the -underloud. It is only for management purposes. +undercloud. It is only for management purposes. Overcloud --------- @@ -47,7 +47,7 @@ will run the following services: - Ceph Monitors and OSDs Stateless OpenStack services - All running statesless OpenStack services are load balanced by HA Proxy. + All running stateless OpenStack services are load balanced by HA Proxy. Pacemaker monitors the services and ensures that they are running. Stateful OpenStack services @@ -65,9 +65,13 @@ RabbitMQ establishment of clustering across cluster members. OpenDaylight - OpenDaylight is currently installed on all three control nodes but only - started on the first control node. OpenDaylight's HA capabilities are not yet - mature enough to be enabled. + OpenDaylight is currently installed on all three control nodes and started as + an HA cluster unless otherwise noted for that scenario. OpenDaylight's + database, known as MD-SAL, breaks up pieces of the database into "shards". + Each shard will have its own election take place, which will determine + which OpenDaylight node is the leader for that shard. The other + OpenDaylight nodes in the cluster will be in standby. Every Open vSwitch + node connects to every OpenDaylight to enable HA. HA Proxy HA Proxy is monitored by Pacemaker to ensure it is running across all nodes @@ -127,9 +131,9 @@ issues per scenario. The following scenarios correspond to a supported +-------------------------+-------------+---------------+ | os-nosdn-ovs-noha | OVS for NFV | Yes | +-------------------------+-------------+---------------+ -| os-nosdn-fdio-ha | FDS | Yes | +| os-nosdn-fdio-ha | FDS | No | +-------------------------+-------------+---------------+ -| os-nosdn-fdio-noha | FDS | Yes | +| os-nosdn-fdio-noha | FDS | No | +-------------------------+-------------+---------------+ | os-nosdn-kvm-ha | KVM for NFV | Yes | +-------------------------+-------------+---------------+ -- cgit 1.2.3-korg