openstack/charm-deployment-guide
Code Issues Proposed changes
charm-deployment-guide/deploy-guide/source/app-ha-topology.rst
Peter Matulis 977cef865e Add new appendix for HA 
If OVN will not make it for 20.05 then the section
will be commented out or edited as a tech preview.

Removed MySQL 5 to 8 upgrade steps. Will use a
separate PR.

Change-Id: I047efb5b9d3ced25e5c5332752c02e5e4368d172
2020-04-23 17:11:55 -04:00

1.4 KiB
Raw Blame History

orphan

Cloud topology for HA applications

Note

The information on this page is associated with the topic of 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 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.