Run "ceilometer-dbsync" 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 dbsync 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.
wakeup keystone before any other keystone action
Merge pull request #109 from jsuchome/wakeup_keystone

wakeup keystone before any other keystone action
Update for prepare_role_for_ha_with_haproxy API change
Merge pull request #110 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 #108 from vuntz/db_sync-for-ha

Run "ceilometer-dbsync" on SUSE when HA is enabled
set some timeout to let the services start
Do not bind to port 5560 when doing HA

Port 5560 is used by /usr/lib64/heartbeat/mgmtd
Merge pull request #116 from vuntz/fix-ha-port

Do not bind to port 5560 when doing HA
Merge pull request #113 from jsuchome/pacemaker_timeout

Pacemaker timeout
move mongodb deployment into its own recipe
mongodb replica set support

Use the configure_replicaset library method from the
edelight/chef-mongodb repository by Markus Korn.
install rubygem-mongo immediately
define the mongodb subtree on nodes
use cluster founder as mongodb replica set controller
use pacemaker to handle mongodb service and ordering
clone the mongodb service in pacemaker