Use the same password for proposal and role on migration

We use a class variable for this.

Also note that there's no need to remove password from node attributes
as they are in a wrong namespace there anyway, so won't conflict.
Use new synchronization helpers to avoid races when deploying with HA

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

 - when creating of the database / database user

Ideally, we would also do that for the db sync, but it's not possible
because this happens in a notification. It should be fine, though, as
the first sync for the database should give enough advance time to the
cluster founder to avoid an issue there.
Merge pull request #145 from vuntz/improve-db-migration

Use the same password for proposal and role on migration
Merge pull request #146 from vuntz/sync-marks

Use new synchronization helpers to avoid races when deploying with HA
Actually set the caching key prefix

This was accidentally missing in a rebase of
https://github.com/crowbar/barclamp-nova_dashboard/pull/121

(cherry picked from commit cd434536e1bab217bdcc95cf78e789de7580b472)
Syntax error

(cherry picked from commit 655cb21daf343066bdaccabaa2f000473a691aab)
Merge pull request #147 from dirkmueller/release/roxy/master

Actually set the caching key prefix
Add pacemaker resource to monitor apache for horizon
Merge pull request #149 from vuntz/ocf

Add pacemaker resource to monitor apache for horizon
Cisco ml2 driver is not compatible with n1kv panel

If the ml2 cisco driver is in use, the n1kv panel for horizon should
not be activated
Merge pull request #134 from rossella/release/roxy/master

Cisco ml2 driver is not compatible with n1kv panel
ha: Follow convention for pacemaker resource naming
Merge pull request #150 from vuntz/ha-convention

Update pacemaker resource names + other conventions for HA
ha: Do not pass params for depth 10 monitoring

The params were specific to each node (because they contain the IP
address of the node), and since we don't do depth 10 monitoring anyway,
we can drop that.
Sort memcache servers in configuration

The order does matter according to the memcache documentation.
Merge pull request #153 from vuntz/sort-memcache

Sort memcache servers in configuration
Merge pull request #152 from vuntz/fix-ocf

ha: Do not pass params for depth 10 monitoring
Update for prepare_role_for_ha_with_haproxy API change
Merge pull request #155 from vuntz/api-change

Update for prepare_role_for_ha_with_haproxy API change