openstack
/
charm-deployment-guide
Code Issues Proposed changes

Remove the reference cloud files for now 

I am working with the SQA team to get a modern
cloud topology. Will replace and augment when
this happens.

Change-Id: I20412e0a560ce93fd72626e62c5950b7aafa73a8
This commit is contained in:
Peter Matulis 2020-04-28 12:04:52 -04:00
parent e8882ffe58
commit 142503ce54
3 changed files with 2 additions and 63 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
deploy-guide/source/app-ha-juju-status.rst
View File

@ -1,21 +0,0 @@
:orphan:
.. _reference_cloud_ha:
===================================
Reference cloud for HA applications
===================================
.. note::
The information on this page is associated with the topic of :ref:`OpenStack
high availability <ha>`. See that page for background information.
The cloud is represented in the form of :command:`juju status` output.
**The below is to be edited. Based on a cloud from Solutions QA.**
.. code-block:: console
Model Controller Cloud/Region Version SLA Timestamp
openstack foundations-maas maas_cloud 2.6.2 unsupported 16:26:29Z

36
deploy-guide/source/app-ha-topology.rst
View File

@ -1,36 +0,0 @@
:orphan:
.. _cloud_topology_ha:
==================================
Cloud topology for HA applications
==================================
.. note::
The information on this page is associated with the topic of :ref:`OpenStack
high availability <ha>`. See that page for background information.
**The below is to be edited. Based on a cloud from Solutions QA.**
This page contains the analysis of cloud machines. The ideal is to do this for
every machine in a cloud in order to determine the *cloud topology*. Six
machines are featured here. They represent a good cross-section of an *Ubuntu
OpenStack* cloud. See :ref:`Reference cloud for HA applications
<reference_cloud_ha>` for the cloud upon which this exercise is based.
Generally speaking, the cloud nodes are hyperconverged and this is the case for
three of the chosen machines, numbered **17**, **18**, and **20**. Yet this
analysis also looks at a trio of nodes dedicated to the `Landscape project`_:
machines **3**, **11**, and **12**, each of which are not hyperconverged.
.. note::
Juju applications can be given custom names at deployement time (see
`Application groups`_ in the Juju documentation). This document will call
out these `named applications` wherever they occur.
.. LINKS
.. _Application groups: https://jaas.ai/docs/application-groups
.. _Landscape project: https://landscape.canonical.com

8
deploy-guide/source/app-ha.rst
View File

@ -26,12 +26,8 @@ Cloud topology guidelines
Deploying applications under HA will involve multiple application units being
distributed amongst the available cloud nodes, thereby dramatically influencing
the cloud topology.
The output of the :command:`juju status` command is a natural way for Juju
operators to view their cloud's topology. See :ref:`Cloud topology for HA
applications <cloud_topology_ha>` for an example of a topology that abides by
the these guidelines.
the cloud topology. The output of the :command:`juju status` command is a
natural way for Juju operators to view their cloud's topology.
MAAS zones and failure domains
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~