move pacemaker_vip_primitive definition to crowbar-pacemaker cookbook

The pacemaker_vip_primitive definition only works in a Crowbar
environment (due to retrieving the VIP name/address from Crowbar's
data bag for the relevant network), so it belongs in the
crowbar-pacemaker cookbook not the pacemaker cookbook.
haproxy: Allow configuring the default balancing algorithm
Use source balancing for haproxy in Crowbar

This is what is recommended in the HA guide for OpenStack. And in the
end, it's fine with us because we are less interested in load balancing
than in making sure that everything works perfectly all the time.
Merge pull request #89 from vuntz/haproxy-balance

Use source balancing for haproxy
Merge pull request #81 from aspiers/move-vip-definition

move pacemaker_vip_primitive definition to crowbar-pacemaker cookbook
changes to superclasses should trigger all tests
Merge pull request #91 from aspiers/guard-superclasses

changes to superclasses should trigger all tests
corosync: Add attribute to not start corosync on boot after fencing

If the node[:corosync][:require_clean_for_autostart] attribute is set to
true, then corosync will not start on boot automatically, nor through
chef-client, if the file /var/spool/corosync/block_automatic_start
exists.

On proper shutdown, one new init script (corosync-shutdown) is used to
remove that file and stopping corosync, resulting in the next boot to
have corosync starting.

This allows to not start corosync after fencing, to avoid a never-ending
deathmatch, or a fencing loop.
Expose require_clean_for_autostart attribute in crowbar