lp:~chad.smith/charms/precise/keystone/ha-support
- Get this branch:
- bzr branch lp:~chad.smith/charms/precise/keystone/ha-support
Branch merges
- Adam Gandelman: Pending requested
-
Diff: 91 lines (+51/-0)6 files modifiedhooks/keystone-hooks (+5/-0)
hooks/lib/openstack_common.py (+16/-0)
scripts/add_to_cluster (+2/-0)
scripts/health_checks.d/service_ports_live (+13/-0)
scripts/health_checks.d/service_running (+13/-0)
scripts/remove_from_cluster (+2/-0)
- Adam Gandelman: Pending requested
-
Diff: 1009 lines (+554/-155)11 files modifiedadd_to_cluster (+2/-0)
config.yaml (+37/-0)
health_checks.d/service_ports_live (+13/-0)
health_checks.d/service_running (+13/-0)
hooks/keystone-hooks (+184/-38)
hooks/lib/openstack_common.py (+72/-4)
hooks/utils.py (+189/-112)
metadata.yaml (+6/-0)
remove_from_cluster (+2/-0)
revision (+1/-1)
templates/haproxy.cfg (+35/-0)
Branch information
- Owner:
- Chad Smith
- Status:
- Development
Recent revisions
- 56. By Chad Smith
-
move now-generic save_script_rc to lib/openstack_
common. py. Update health scripts to be more flexible based on OPENSTACK_PORT* and OPENSTACK_SERVICE* environment variables - 55. By Chad Smith
-
update service_* health scripts to source ../scriptsrc to obtain service specific variables. bump revision
- 54. By Chad Smith
-
added shallow add_to_cluster, remove_from_cluster and health_checks.d charm scripts
- 50. By James Page
-
Adds better support for service leaders.
* The service leader is determined depending on how keystone is currently clustered. If there are multiple units, but no hacluster subordinate, the oldest service unit is elected leader (lowest unit number). If hacluster exists and the service is clustered, the CRM is consulted and the node hosting the resources is designated the leader.
* Only the leader may initialize or touch the database (create users, endpoints, etc)
* The leader is responsible for synchronizing a list of service credentials to all peers. The list is stored on disk and resolves the issue of the passwd dump files in /var/lib/keystone/ being out-of-sync among peers.
We can use the same approach in the rabbitmq-server charm if it works out here.
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)
- Stacked on:
- lp:~charmers/charms/precise/keystone/trunk