From f8d3ff4a616c98cbaefd9b6b2f270baf5e55a6cd Mon Sep 17 00:00:00 2001 From: Graham Hayes Date: Fri, 13 Feb 2015 17:52:29 +0000 Subject: [PATCH] Fix Production Arch docs Change-Id: I203da7b1bd3071cc88e935ef473d52fe6be8f8a8 --- doc/source/production-architecture.rst | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/doc/source/production-architecture.rst b/doc/source/production-architecture.rst index f6ebbcf9..21a80e2f 100644 --- a/doc/source/production-architecture.rst +++ b/doc/source/production-architecture.rst @@ -4,11 +4,6 @@ Production Architecture ============================= -Multi-Zone Architecture ------------------------ - -.. image:: images/Designate-MultiZone.png - Outline ------- This document outlines what a production environment hosting Designate could look like, it follows an in-cloud model, where Designate would be hosted on instances in an OpenStack cloud. It's supposed to complement the @@ -29,7 +24,10 @@ Roles A Designate deploy breaks down into several key roles: - `Designate API`_ +- `Designate Sink`_ - `Designate Central`_ +- `Designate MiniDNS`_ +- `Designate Pool Manager`_ - `Message Queue`_ - `Database`_ (MySQL or derivative) - `DNS Backend`_ @@ -40,13 +38,21 @@ Typically, API nodes would be made available in multiple AZs, providing redundan In a Multi-AZ deployment, the API nodes should be configured to talk to all members of the MQ Cluster - so that in the event of MQ node failing, requests continue to flow to the MQ. +Designate Sink +~~~~~~~~~~~~~~~~~~~~~~~ +In a Multi-AZ deployment, the sink node should be configured to talk to all members of the MQ Cluster - so that in the event of MQ node failing, requests continue to flow to the MQ. + Designate Central ~~~~~~~~~~~~~~~~~~~~~~~ In a Multi-AZ deployment, the Central nodes should be configured to talk to all members of the MQ Cluster - so that in the event of MQ node failing, requests continue to be processed. -Designate Sink +Designate MiniDNS ~~~~~~~~~~~~~~~~~~~~~~~ -In a Multi-AZ deployment, the sink node should be configured to talk to all members of the MQ Cluster - so that in the event of MQ node failing, requests continue to flow to the MQ. +In a Multi-AZ deployment, the MiniDNS nodes should be configured to talk to all members of the MQ Cluster - so that in the event of MQ node failing, requests continue to be processed. It should also be configured to talk to multiple DB servers, to allow for reliable access to the data store + +Designate Pool Manager +~~~~~~~~~~~~~~~~~~~~~~~ +In a Multi-AZ deployment, the Pool Manager nodes should be configured to talk to all members of the MQ Cluster - so that in the event of MQ node failing, requests continue to be processed. Message Queue ~~~~~~~~~~~~~