d6af412fa7
This patch breaks the monolithic bk-ha-guide.xml file into chapters and sections. Section files are placed in subdirectories, with the subdirectories named after the chapters (and parts) to which they belong. This patch just does structural fixes. Once it's in, we can begin to do content cleanup in manageable chunks. Change-Id: I27397834141a3e6c305f60e71350ce869ab7c8a1 Implements: blueprint convert-ha-guide-to-docbook
21 lines
1.0 KiB
XML
21 lines
1.0 KiB
XML
<chapter xmlns="http://docbook.org/ns/docbook"
|
||
xmlns:xlink="http://www.w3.org/1999/xlink"
|
||
xmlns:xi="http://www.w3.org/2001/XInclude"
|
||
version="5.0" xml:id="ha-aa-db">
|
||
<info>
|
||
<title>Database</title>
|
||
</info>
|
||
<simpara>The first step is installing the database that sits at the heart of the
|
||
cluster. When we talk about High Availability, we talk about several databases (for redundancy) and a
|
||
means to keep them synchronized. In this case, we must choose the
|
||
MySQL database, along with Galera for synchronous multi-master replication.</simpara>
|
||
<simpara>The choice of database isn’t a foregone conclusion; you’re not required
|
||
to use MySQL. It is, however, a fairly common choice in OpenStack
|
||
installations, so we’ll cover it here.</simpara>
|
||
|
||
<xi:include href="./ha_aa_db/section_ha_aa_db_mysql_galera.xml"/>
|
||
<xi:include href="./ha_aa_db/section_ha_aa_db_galera_monitoring.xml"/>
|
||
<xi:include href="./ha_aa_db/section_other_ways_to_provide_a_highly_available_database.xml"/>
|
||
|
||
</chapter>
|