ha: Follow convention for pacemaker resource naming
ha: Start the clone resource, not the primitive
Merge pull request #202 from vuntz/ha-convention

Update pacemaker resource names + other conventions for HA
Run "keystone-manage db_sync" on SUSE when HA is enabled

So far, we were not running it because the init script on SUSE does run
it. But with HA enabled, the service starts at the same time on all
nodes, which may result in failures on some nodes because db_sync can't
be run multiple times simultaneously. The end result is that the
pacemaker resource was possilby failing on some nodes, which then
required some manual cleanup.
Update for prepare_role_for_ha_with_haproxy API change
Merge pull request #204 from vuntz/api-change

Update for prepare_role_for_ha_with_haproxy API change
Only run the db_sync the very first time (on SUSE, at least)
Do the db sync only on initial run, and on all platforms
Merge pull request #203 from vuntz/db_sync-for-ha

Run "keystone-manage db_sync" on SUSE when HA is enabled
Only try to delete token if the token create succeeded

Otherwise the code tries to access 'data' which might
not be valid JSON.