patches, docs: Remove MySQL WSREP SST provider

xtrabackup issues have been fixed with the latest version of
percona-xtrabackup DEBs we added to linux.enea.com, so remove
MySQL WSREP SST provider patches and corresponding docs.

Closes-bug: ARMBAND-52

Change-Id: I743e9b6ed242cf15e3063d7dcf7e05d0cee198f2
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>

2 files changed, 0 insertions, 23 deletions

diff --git a/docs/img/fuelwsrepsst.png b/docs/img/fuelwsrepsst.png
deleted file mode 100644
index 90ded440..00000000
--- a/docs/img/fuelwsrepsst.png
+++ /dev/null
diff --git a/docs/installation-instruction.rst b/docs/installation-instruction.rst
index 356f4110..b7edd91c 100644
--- a/docs/installation-instruction.rst
+++ b/docs/installation-instruction.rst
@@ -582,29 +582,6 @@ that can be used for installation / deployment of openstack.
 Target specific configuration
 -----------------------------
 
-#. [AArch64 specific] Configure MySQL WSREP SST provider
-
-   **NOTE**: This option is only available for ArmbandFuel@OPNFV, since it
-   currently only affects AArch64 targets (see *Reference 15*).
-
-   When using some AArch64 platforms as controller nodes, WSREP SST
-   synchronisation using default backend provider (xtrabackup-v2) might fail,
-   so a mechanism that allows selecting a different WSREP SST provider
-   has been introduced.
-
-   In the FUEL UI of your Environment, click the <Settings> tab, click
-   <OpenStack Services> on the left side pane (see figure below), then
-   select one of the following options:
-
-   - xtrabackup-v2 (default provider, AArch64 stability issues);
-
-   - rsync (AArch64 validated, better or comparable speed to xtrabackup,
-     takes the donor node offline during state transfer);
-
-   - mysqldump (untested);
-
-   .. figure:: img/fuelwsrepsst.png
-
 #. Set up targets for provisioning with non-default "Offloading Modes"
 
    Some target nodes may require additional configuration after they are