Thanks for the clarification Alex! The problem in this case was actually related to a missing parameter for the mysql router and that was the reason why the installation was failing. There is a db-router parameter that has to be defined in order to assign the mysql router and the inno db cluster to a specific network. This is already documented in https://bugs.launchpad.net/charm-mysql-router/+bug/1881171
Thanks for the clarification Alex! The problem in this case was actually related to a missing parameter for the mysql router and that was the reason why the installation was failing. There is a db-router parameter that has to be defined in order to assign the mysql router and the inno db cluster to a specific network. This is already documented in https:/ /bugs.launchpad .net/charm- mysql-router/ +bug/1881171
[...] mysql-router: charmers- next/mysql- router mysql-router: charmers- next/mysql- router mysql-router: charmers- next/mysql- router mysql-router: charmers- next/mysql- router mysql-router: charmers- next/mysql- router mysql-router: charmers- next/mysql- router mysql-router: charmers- next/mysql- router
services:
keystone-
charm: cs:~openstack-
bindings:
db-router: *internal-space
nova-
charm: cs:~openstack-
bindings:
db-router: *internal-space
glance-
charm: cs:~openstack-
bindings:
db-router: *internal-space
neutron-
charm: cs:~openstack-
bindings:
db-router: *internal-space
dashboard-
charm: cs:~openstack-
bindings:
db-router: *internal-space
heat-
charm: cs:~openstack-
bindings:
db-router: *internal-space
placement-
charm: cs:~openstack-
bindings:
db-router: *internal-space
[...]
mysql- innodb- cluster: charmers- next/mysql- innodb- cluster buffer- pool-size: 512M binlogs: True connections: *mysql-connections
charm: cs:~openstack-
num_units: 3
bindings:
"": *oam-space
cluster: *internal-space
# added shared-db to db-router
db-router: *internal-space
shared-db: *internal-space
options:
source: *openstack-origin
innodb-
wait-timeout: 3600
enable-
max-
to:
- lxd:1
- lxd:2
- lxd:3