VIPs lack colocation constraints

[Andrea Ieri]

VIPs should only be instantiated when haproxy is running. If haproxy is down, the VIP should be moved onto a unit where haproxy is functional.

This can be implemented by setting a colocation constraints, e.g.:

crm configure colocation vip_with_haproxy inf: <vip group> <haproxy clone set>

How to reproduce:
* on a unit where a VIP is held, block haproxy from running (e.g. service haproxy stop ; chmod -x /usr/sbin/haproxy

Expected result:
* the VIP group resource will be transitioned onto a different unit

Current result:
* the VIP group does not move

NOTE: colocation constraints won't work if the haproxy resource is marked as started, i.e. this bug depends on LP#1810918
NOTE: I experienced this on neutron-apis, but this bug appears to affect all principal charms

[James Page (james-page)]

bug 1810918