I was able to get the percona-cluster to fetch the correct private-
address by using access-network option to specify the correct network
where I expected this private-address to be on.
Note that I also was using the access binding to specify space
associated with that subnet so not sure if both binding and access-
network are needed. However, the access binding by itself did not work.
For example:
With space oil set mapped to 192.0.5.0/24
percona-cluster:
charm: cs:trusty/percona-cluster
num_units: 1
options:
sst-password: root
root-password: root
max-connections: 1500
access-network: 192.0.5.0/24
source: cloud:trusty-mitaka
bindings:
access: oil
to:
- lxc:3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1657305
Title:
percona cluster getting wrong private ip
To manage notifications about this bug go to:
https://bugs.launchpad.net/opnfv/+bug/1657305/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
