juju deploy mysql-innodb-cluster
MySQL InnoDB Cluster Read more
Discuss this charm
Share your thoughts on this charm with the community on discourse.
Important: The eoan series is the first series supported by the mysql-innodb-cluster and mysql-router charms. These charms replace the percona-cluster charm starting with the focal series.
config.yaml of the built charm (or see the charm in the Charm
Store) for the full list of configuration options,
along with their descriptions and default values. See the Juju
documentation for details on configuring applications.
MySQL 8 is natively HA and requires at least three database units, which are often containerised. To deploy a three-node cluster to new containers on machines '0', '1', and '2':
juju deploy -n 3 --to lxd:0,lxd:1,lxd:2 mysql-innodb-cluster
A cloud application is joined to the database via an instance of mysql-router. For a pre-existing keystone application:
juju deploy mysql-router keystone-mysql-router juju add-relation keystone-mysql-router:db-router mysql-innodb-cluster:db-router juju add-relation keystone-mysql-router:shared-db keystone:shared-db
TLS communication between MySQL InnoDB Cluster and its cloud clients is supported out of the box via a self-signed CA certificate bundled within MySQL itself.
A better option is to use a certificate signed by a Vault-based CA. This can be done once Vault has been initialised and has a root CA:
juju add-relation mysql-innodb-cluster:certificates vault:certificates
See the vault charm README for more information.
This section lists Juju actions supported by the charm.
Actions allow specific operations to be performed on a per-unit basis. To
display action descriptions run
juju actions --schema mysql-innodb-cluster.
If the charm is not deployed then see file
The OpenStack Charms project maintains two documentation guides:
- OpenStack Charm Guide: for project information, including development and support notes
- OpenStack Charms Deployment Guide: for charm usage information
Please report bugs on Launchpad.