Update passwords migration script to remove node attributes

On update, we want to use the db password (and metering secret) from the
proposal / role, and not the ones that might have been generated on the node
(through the cookbook). As the passwords are a "normal" attribute on the node,
but a "default" attribute on the role, the old ones from the node is used.
Which means we really need to remove them to get the new ones used.

To minimize config changes, we actually import the passwords from one
node (which should be good enough in most cases as we allow only one
ceilometer proposal, so only one node should have the passwords).
Use new synchronization helpers to avoid races when deploying with HA

There are a number of possible races when deploying ceilometer for the
first time:

 - when creating of the database / database user
 - when registering the endpoint and creating users in keystone
 - running the db sync
Wait for mongodb on all nodes of the cluster, not just the founder
Merge pull request #101 from vuntz/drop-db-node

Update passwords migration script to remove node attributes
Merge pull request #102 from vuntz/sync-marks

Use new synchronization helpers to avoid races when deploying with HA
Use new CrowbarPacemakerHelper.is_cluster_founder? helper
Configuration of active-pasive HA for ceilometer-agent-central:

Creating cluster resource configuration for pacemaker.

use LSB service until OCF agent is able to use LSB services internally

use PacemakerServiceObject's helper
Manage ceilometer-api services via pacemaker clone LWRP
Add synchronization marks around the creation of pacemaker resources
Added ceilometer pacemaker support for collector service and
group it with ceilometer api as server-group
Merge pull request #97 from jsuchome/pacemaker

Configuration of active-passive HA for ceilometer-agent-central:
Merge pull request #104 from vuntz/is-founder

Use new CrowbarPacemakerHelper.is_cluster_founder? helper
Add insecure flag to keystone_authtoken config when required
Merge pull request #105 from rhafer/keystone_insecure

Add insecure flag to keystone_authtoken config when required
ha: Follow convention for pacemaker resource naming
ha: Do not pass is-managed / target-role meta when creating resources

We are happy with the default values.
Merge pull request #107 from vuntz/ha-convention

Update pacemaker resource names + other conventions for HA
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