Mysql Router

  • MySQL Charm Maintainers
  • Cloud
Channel Revision Published Runs on
latest/edge 256 16 Oct 2024
Ubuntu 24.04 Ubuntu 23.10 Ubuntu 23.04 Ubuntu 22.10 Ubuntu 22.04 Ubuntu 20.04
latest/edge 255 16 Oct 2024
Ubuntu 24.04 Ubuntu 23.10 Ubuntu 23.04 Ubuntu 22.10 Ubuntu 22.04 Ubuntu 20.04
latest/edge 254 16 Oct 2024
Ubuntu 24.04 Ubuntu 23.10 Ubuntu 23.04 Ubuntu 22.10 Ubuntu 22.04 Ubuntu 20.04
latest/edge 253 16 Oct 2024
Ubuntu 24.04 Ubuntu 23.10 Ubuntu 23.04 Ubuntu 22.10 Ubuntu 22.04 Ubuntu 20.04
latest/edge 201 19 Jun 2024
Ubuntu 24.04 Ubuntu 23.10 Ubuntu 23.04 Ubuntu 22.10 Ubuntu 22.04 Ubuntu 20.04
latest/edge 108 12 Sep 2023
Ubuntu 24.04 Ubuntu 23.10 Ubuntu 23.04 Ubuntu 22.10 Ubuntu 22.04 Ubuntu 20.04
latest/edge 62 10 Feb 2023
Ubuntu 24.04 Ubuntu 23.10 Ubuntu 23.04 Ubuntu 22.10 Ubuntu 22.04 Ubuntu 20.04
8.0/stable 257 17 Oct 2024
Ubuntu 22.04 Ubuntu 20.04
dpe/candidate 225 28 Aug 2024
Ubuntu 22.04 Ubuntu 20.04
dpe/candidate 224 28 Aug 2024
Ubuntu 22.04 Ubuntu 20.04
dpe/candidate 223 28 Aug 2024
Ubuntu 22.04 Ubuntu 20.04
dpe/beta 225 23 Aug 2024
Ubuntu 22.04 Ubuntu 20.04
dpe/beta 224 23 Aug 2024
Ubuntu 22.04 Ubuntu 20.04
dpe/beta 223 23 Aug 2024
Ubuntu 22.04 Ubuntu 20.04
dpe/edge 260 25 Oct 2024
Ubuntu 22.04 Ubuntu 20.04
dpe/edge 259 25 Oct 2024
Ubuntu 22.04 Ubuntu 20.04
dpe/edge 258 25 Oct 2024
Ubuntu 22.04 Ubuntu 20.04
8.0.19/stable 26 05 May 2022
Ubuntu 22.04 Ubuntu 20.04
8.0.19/edge 26 05 May 2022
Ubuntu 22.04 Ubuntu 21.10 Ubuntu 21.04 Ubuntu 20.10 Ubuntu 20.04
8.0.19/edge 15 26 Apr 2022
Ubuntu 22.04 Ubuntu 21.10 Ubuntu 21.04 Ubuntu 20.10 Ubuntu 20.04
juju deploy mysql-router --channel dpe/edge
Show information

Platform:

Ubuntu
24.04 23.10 23.04 22.10 22.04 21.10 21.04 20.10 +1

Get a MySQL Router up and running

This is part of the MySQL Router Tutorial. Please refer to this page for more information and the overview of the content. The following document will deploy “MySQL Router” together with “MySQL server” (coming from the separate charm “Charmed MySQL”).

Deploy Charmed MySQL + MySQL Router

To deploy Charmed MySQL + MySQL Router, all you need to do is run the following commands:

juju deploy mysql --channel 8.0
juju deploy mysql-router --channel dpe/edge

Juju will now fetch charms from Charmhub and begin deploying it to the LXD VMs. This process can take several minutes depending on how provisioned (RAM, CPU, etc) your machine is. You can track the progress by running:

juju status --watch 1s

This command is useful for checking the status of Juju applications and gathering information about the machines hosting them. Some of the helpful information it displays include IP addresses, ports, state, etc. The command updates the status of charms every second and as the application starts you can watch the status and messages of their change. Wait until the application is ready - when it is ready, juju status will show:

TODO

:tipping_hand_man: Tip: To exit the screen with juju status --watch 1s, enter Ctrl+c. If you want to further inspect juju logs, can watch for logs with juju debug-log. More info on logging at juju logs.

At this stage MySQL Router will stay in blocked state due to missing relation/integration with MySQL DB, let’s integrate them:

juju integrate mysql mysql-router

Shortly the juju status will report new blocking reason Missing relation: database as it waits for a client to consume DB service, let’s deploy data-integrator and request access to database test123:

juju deploy data-integrator --config database-name=test123
juju relate data-integrator mysql-router

In couple of seconds, the status will be happy for entire model:

TODO

Access database

The first action most users take after installing MySQL is accessing MySQL. The easiest way to do this is via the MySQL Command-Line Client mysql. Connecting to the database requires that you know the values for host, username and password. To retrieve the necessary fields please run data-integrator action get-credentials:

juju run data-integrator/leader get-credentials

Running the command should output:

TODO

The host’s IP address can be found with juju status (the application hosting the MySQL Router application):

...
TODO
...

To access the MySQL database via MySQL Router choose read-write (port 6446) or read-only (port 6447) endpoints:

mysql -h 10.152.183.52 -P6446 -urelation-4-6 -pNu7wK85QU7dpVX66X56lozji test123

Inside MySQL list DBs available on the host show databases:

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| performance_schema |
| test123            |
+--------------------+
3 rows in set (0.00 sec)

:tipping_hand_man: Tip: if at any point you’d like to leave the MySQL client, enter Ctrl+d or type exit.

You can now interact with MySQL directly using any MySQL Queries. For example entering SELECT VERSION(), CURRENT_DATE; should output something like:

mysql> SELECT VERSION(), CURRENT_DATE;
+-------------------------+--------------+
| VERSION()               | CURRENT_DATE |
+-------------------------+--------------+
| 8.0.34-0ubuntu0.22.04.1 | 2023-10-17    |
+-------------------------+--------------+
1 row in set (0.00 sec)

Feel free to test out any other MySQL queries. When you’re ready to leave the MySQL shell you can just type exit. Now you will be in your original shell where you first started the tutorial; here you can interact with Juju and LXD.

Remove the user

To remove the user, remove the relation. Removing the relation automatically removes the user that was created when the relation was created. Enter the following to remove the relation:

juju remove-relation mysql-router data-integrator

Now try again to connect to the same MySQL Router you just used above:

mysql -h 10.152.183.52 -P6446 -urelation-4-6 -pNu7wK85QU7dpVX66X56lozji test123

This will output an error message:

ERROR 1045 (28000): Access denied for user 'relation-4-6'@'mysql-router-1.mysql-router-endpoints.tutorial.svc.clust' (using password: YES)

As this user no longer exists. This is expected as juju remove-relation mysql-router data-integrator also removes the user. Note: data stay remain on the server at this stage!

Relate the the two applications again if you wanted to recreate the user:

juju relate data-integrator mysql-router

Re-relating generates a new user and password:

juju run data-integrator/leader get-credentials

You can connect to the database with this new credentials. From here you will see all of your data is still present in the database.


Help improve this document in the forum (guidelines). Last updated 1 year, 15 days ago.