David Ames 19097f6aac Avoid shared-db change when using access-network ... When the percona-cluster charm sets an access-network but the default unit-get address is not on that network extra shared-db relations get executed. This is specifically a problem when running upgrades and trying to avoid API downtime. The root cause is that the access-network is not checked until the SharedDBContext is consulted. But then db_joined function will change it back to the wrong ip on subsequent runs. This change adds a check for access-network on the relation during the db_joined function and pushes IP selection off to get_relation_ip. Charm helpers sync to pull in changes to get_relation_ip. Change-Id: I05d4c472e2135740f964a4621f1f755f900a10f8 Partial-bug: #1677647		2017-04-26 15:22:07 -07:00
..
__init__.py	Resync charmhelpers for licensing change	2016-07-06 16:41:17 +01:00
nrpe.py	Avoid shared-db change when using access-network	2017-04-26 15:22:07 -07:00
volumes.py	Resync charmhelpers for licensing change	2016-07-06 16:41:17 +01:00