From 5a04e6a8c98e7cb65028599c4ad3ea2f4fbb71c1 Mon Sep 17 00:00:00 2001
From: Toma Bilius <toma.bilius@enea.com>
Date: Wed, 31 Mar 2021 17:10:03 +0300
Subject: How can an user reconfigure a HA cluster?

Change-Id: I44f752865ab67abd35fa65ed9a9da67c68a6b9ea
Signed-off-by: Toma Bilius <toma.bilius@enea.com>
---
 .../doc/advanced_configurations.xml                | 88 +---------------------
 1 file changed, 3 insertions(+), 85 deletions(-)

(limited to 'doc')

diff --git a/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
index 10f1e65..e321cf9 100644
--- a/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
+++ b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
@@ -957,91 +957,9 @@ Configuration complete.</programlisting>
         View</emphasis>. The list of Enea Edge Management servers should be
         displayed, with one listed as Primary and the rest as Backup.</para>
 
-        <para>The High Availability configuration can be changed at a later
-        point, if, for instance, the IPs of the cluster have changed. Before 
-          changing the settings in the configuration files, the Enea Edge 
-          Management application must first be stopped, followed by the 
-          MariaDB database.</para>
-          
-          <para>To change cluster settings, do the following:</para>
-
-        <itemizedlist>
-          <listitem>
-            <para>Change the configuration of the MariaDB with the new IPs: go
-            to <filename>/etc/my.cnf.d/wsrep.cnf</filename> and modify the
-            <literal>wsrep_cluster_address</literal> property.</para>
-          </listitem>
-
-          <listitem>
-            <para>Go to the Enea Edge Management installation folder, then to
-            application/config and edit
-            <filename>databaseConfig.xml</filename>. Change the list of IPs
-            under the <literal>&lt;location&gt;</literal> tag. The order of
-            the IPs is important, since the Edge Management will try to
-            contact them sequentially. Placing the local IP first (the one
-            identified by the protect.interface, see below) will improve
-            communication latency, since it will be done on the local
-            bus.</para>
-          </listitem>
-
-          <listitem>
-            <para>In the same folder, edit the
-            <filename>elementCenter.xml</filename> file. Below are the most
-            important properties relating to the High Availability
-            feature:</para>
-
-            <itemizedlist>
-              <listitem>
-                <para><emphasis role="bold">protect.enabled</emphasis>:
-                boolean value that enables protection mode.</para>
-              </listitem>
-
-              <listitem>
-                <para><emphasis role="bold">protect.group</emphasis>: the name
-                of the protection group.</para>
-              </listitem>
-
-              <listitem>
-                <para><emphasis
-                role="bold">protect.heartbeat.seconds</emphasis>: the time
-                resolution in which a primary server failure is detected. A
-                primary failure during the heartbeat signal period means that
-                service will no longer be available until the next heartbeat
-                occurs. One of the backup servers will take over as primary
-                afterwards.</para>
-              </listitem>
-
-              <listitem>
-                <para><emphasis
-                role="bold">protect.virtualIpAddress</emphasis>: the IP
-                address of the cluster. This value must be the same for all
-                members of the cluster.</para>
-              </listitem>
-
-              <listitem>
-                <para><emphasis role="bold">protect.vipNetmask</emphasis>: the
-                netmask of the virtual IP.</para>
-              </listitem>
-
-              <listitem>
-                <para><emphasis role="bold">protect.interface</emphasis>: the
-                interface responsible for handling ucpeManager traffic,
-                identified by IP address.</para>
-              </listitem>
-
-              <listitem>
-                <para><emphasis
-                role="bold">protect.arbiterIpAddress</emphasis>: the IP
-                address of the arbiter, used to elect a primary server.</para>
-              </listitem>
-
-              <listitem>
-                <para><emphasis role="bold">protect.arbiterPort</emphasis>:
-                the port to ping on the arbiter.</para>
-              </listitem>
-            </itemizedlist>
-          </listitem>
-        </itemizedlist>
+        <para>To change the configuration at a later point after the
+        installation, either uninstall and then reinstall the product, or
+        contact Enea Support.</para>
       </section>
     </section>
 
-- 
cgit v1.2.3-54-g00ecf