David Ames e94f7882cb 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. Partial-bug: #1677647 Change-Id: Ifd4e975d9abbb9f7a8b0f12c8f0a8cf8f78595b6		2017-04-25 14:32:19 -07:00
..
__init__.py	Resync charmhelpers for licensing change	2016-07-06 16:39:15 +01:00
deployment.py	Update Amulet defs, series metadata and c-h sync	2016-11-28 14:55:42 -06:00
utils.py	Avoid shared-db change when using access-network	2017-04-25 14:32:19 -07:00