This change sets the configuration option [DEFAULT].unknown_config_option to warning on upgrade-charm and on config-changed, this allows clusters running mysql-8.0.29 with the "name" key set to run. This option is set to "warning" by default, although mysqlrouter set it to "error". More details at https://dev.mysql.com/doc/mysql-router/8.0/en/mysql-router-conf-options.html#option_mysqlrouter_unknown_config_option Closes-Bug: #1971565 Change-Id: I9613706f1e2b573af10562fb6fbf0b9a7aedf6da
|2 weeks ago|
|actions||2 years ago|
|files||2 years ago|
|lib||2 weeks ago|
|reactive||1 year ago|
|templates||2 months ago|
|tests||4 weeks ago|
|HACKING.md||3 years ago|
|README.md||8 months ago|
|actions.yaml||2 years ago|
|config.yaml||6 months ago|
|icon.svg||3 years ago|
|layer.yaml||3 years ago|
|metadata.yaml||1 month ago|
|test-requirements.txt||3 months ago|
|tox.ini||8 months ago|
|wheelhouse.txt||10 months ago|
The mysql-router charm provides a MySQL 8 Router; it proxies database requests from a principle application to a MySQL 8 InnoDB Cluster. MySQL Router handles cluster communication and understands the cluster schema.
It is a subordinate charm that is used in conjunction with the mysql-innodb-cluster charm. It is also used with a principle charm that supports the 'mysql-shared' interface. The current list of such charms can be obtained from the Charm Store (the charms officially supported by the OpenStack Charms project are published by 'openstack-charmers').
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.
The charm is deployed as a subordinate to a principle application and then related to the central mysql-innodb-cluster application:
principle charm A <---> mysql-router A <---> principle charm B <---> mysql-router B <---> mysql-innodb-cluster principle charm C <---> mysql-router C <--->
config.yaml for the full list of configuration options, along with
their descriptions and default values.
To deploy a MySQL 8 Router for joining, say, Keystone to the cloud database:
juju deploy mysql-router keystone-mysql-router
Note: The mysql-router application is typically given a name that corresponds to the associated principle application.
Add a relation to the principle application (via the shared-db endpoint):
juju add-relation keystone:shared-db keystone-mysql-router:shared-db
Then add a relation to the mysql-innodb-cluster application (via the db-router endpoint):
juju add-relation keystone-msyql-router:db-router mysql-innodb-cluster:db-router
Important: When network spaces are used, the mysql-router and mysql-innodb-cluster charms must be configured such that the 'db-router' endpoint is bound to the same space.
Scale out is accomplished by adding units to the principle application:
juju add-unit keystone
Note: If more than one mysql-router application is placed on the same machine the
base-portconfiguration option is needed to ensure non-conflicting TCP port numbers are used (the default is '3306').
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-router. 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.