openstack
/
charm-mysql-innodb-cluster
Code Issues Proposed changes

Fix code block and move section 

Change-Id: I272144ab7bab470ba5e627eb67451c449ce42a82
This commit is contained in:
Peter Matulis 2020-08-04 21:53:05 -04:00
parent da0896fbeb
commit b45f5b00b9
1 changed files with 13 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
src/README.md
View File

@ -19,23 +19,6 @@ therefore does not deploy on a single unit.
See file `config.yaml` for the full list of configuration options, along with
their descriptions and default values.
### TLS
TLS communication between MySQL InnoDB Cluster and its cloud clients is
supported.
Due to the circular dependency between the vault and mysql-innodb-cluster
applications, the enablement of this feature can only be done
post-deployment (once vault has been initialised and has a root Certificate
Authority).
Enable database TLS communication with this relation:
.. code-block:: none
juju add-relation mysql-innodb-cluster:certificates vault:certificates
## Deployment
To deploy a three-node cluster:
@ -62,6 +45,19 @@ Nodes can be added to the cluster as Read Only nodes:
See [OpenStack high availability][cdg-app-ha-mysql8] in the [OpenStack Charms
Deployment Guide][cdg] for more deploy instructions.
## TLS
TLS communication between MySQL InnoDB Cluster and its cloud clients is
supported.
Due to the circular dependency between the vault and mysql-innodb-cluster
applications, the enablement of this feature can only be done post-deployment
(once vault has been initialised and has a root Certificate Authority).
Enable database TLS communication with this relation:
juju add-relation mysql-innodb-cluster:certificates vault:certificates
## Actions
This section lists Juju [actions][juju-docs-actions] supported by the charm.