add designate barclamp (SCRD-8739)

xml/depl_nodes.xml

@@ -54,6 +54,12 @@
  </para>
  <orderedlist spacing="normal">
   <listitem>
+<!-- Designate -->
+   <para>
+    <xref linkend="sec.depl.ostack.designate" xrefstyle="select:title nopage"/>
+   </para>
+  </listitem>
+  <listitem>
 <!-- Pacemaker -->
    <para>
     <xref linkend="sec.depl.ostack.pacemaker" xrefstyle="select:title nopage"/>
@@ -150,6 +156,76 @@
    </para>
   </listitem>
  </orderedlist>
+ <sect1 xml:id="sec.depl.ostack.designate">
+  <title>Deploying Designate</title>
+  <para>
+    &desig; provides &productname; DNS as a Service (DNSaaS). It is used to
+    create and propagate zones and records over the network using pools of DNS
+    servers. Deployment defaults are in place, so not much is required to
+    configure &desig;. &o_netw; needs additional settings for integration with
+    &desig;. The &desig; barclamp does not configure these &o_netw; settings; an
+    admin can enable them if necessary. For more information, see the <link
+    xlink:href="https://docs.openstack.org/designate/latest/contributor/integrations.html">OpenStack
+    Integrations</link>.
+  </para>
+  <para>
+    The &desig; barclamp relies heavily on dns barclamp and expects
+    it to be applied without any failures.
+  </para>
+  <variablelist>
+    <varlistentry>
+      <term>designate-server role</term>
+      <listitem>
+        <para>
+          Installs the &desig; server packages and configures the mini-dns (mdns)
+          service required by &desig;.
+        </para>
+      </listitem>
+    </varlistentry>
+    <varlistentry>
+      <term>designate-worker role</term>
+      <listitem>
+       <para>
+        Configures a &desig; worker on the selected nodes. &desig; uses the
+        workers to distribute its workload.
+        </para>
+      </listitem>
+    </varlistentry>
+  </variablelist>
+  <para>
+    <literal>&desig; Sink</literal> is an optional service and is not configured as part
+    of this barclamp.
+  </para>
+  <para>
+    &desig; uses pool(s) over which it can distribute zones and
+    records, these pool(s) are not created by &crow;. Pools can have
+    varied configuration. Any misconfiguration can lead to
+    information leakage.
+  </para>
+  <para>
+    One possible configuration of pools is created by &crow; on a node
+    with <literal>designate-api</literal> role in
+    <filename>/etc/designate/pools.crowbar.yaml</filename>. Copy
+    this file and edit it according to the requirements. Then provide this
+    configuration to &desig; using the command:
+  </para>
+  <screen>&prompt.ardana;designate-manage pool update --file /etc/designate/pools.crowbar.yaml</screen>
+  <para>
+   Editing the &desig; proposal
+  </para>
+  <informalfigure>
+   <mediaobject>
+    <textobject><phrase>Edit &desig; Proposal</phrase>
+    </textobject>
+    <imageobject role="fo">
+     <imagedata fileref="designate-edit-proposal.png" width="100%" format="png"/>
+    </imageobject>
+    <imageobject role="html">
+     <imagedata fileref="designate-edit-proposal.png" width="75%" format="png"/>
+    </imageobject>
+   </mediaobject>
+  </informalfigure>
+ </sect1>
  <sect1 xml:id="sec.depl.ostack.pacemaker">
   <title>Deploying Pacemaker (Optional, &haSetup; Only)</title>
 

xml/depl_overview.xml

@@ -236,6 +236,11 @@
      &o_orch;, an orchestration engine.
     </para>
    </listitem>
+   <listitem>
+    <para>
+     &desig; provides DNS as a Service (DNSaaS)
+    </para>
+   </listitem>
    <listitem>
     <para>
      &o_meter; server and agents. &o_meter; collects CPU and networking data