Created by Adam Gandelman on 2013-03-21 and last modified on 2013-03-21
Get this branch:
bzr branch lp:~gandelman-a/charms/precise/keystone/cloud_archive_vers
Only Adam Gandelman can upload to this branch. If you are Adam Gandelman please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Adam Gandelman

Recent revisions

59. By Adam Gandelman on 2013-03-21

Reinstate original formatting for specifying cloud archive pockets.

Somewhere the parsing changed from cloud:precise-folsom/updates to
cloud:folsom/updates. Make it consitent with scheme used in other

58. By Adam Gandelman on 2013-03-19

Big refactor and cleanup from James.

57. By James Page on 2013-03-11

SSH based hook syncing

56. By James Page on 2013-03-08

Fixup keystone epoch version handling

55. By Adam Gandelman on 2013-03-06

Merge health_checks.d framework.

54. By Adam Gandelman on 2013-03-05

Sync openstack charm helpers.

53. By James Page on 2013-02-18

Use db_host, not private address to ensure VIP is used in HA scenarios

52. By James Page on 2013-02-15

openstack-common: increase server/client timeout to 10seconds

51. By James Page on 2013-02-14

Pass keystone information to services which just need to access keystone

50. By James Page on 2013-02-07

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:
This branch contains Public information 
Everyone can see this information.