Add start-delay to galera (mysqld) pacemaker resource
Merge pull request #292 from rohara/galera

Add start-delay to galera (mysqld) pacemaker resource
RabbitMQ HA support
Merge pull request #293 from jeckersb/rabbit-ha

RabbitMQ HA support
puppet dep fix
neutron param defaults that do not cause breakeage
rm services no longer in howto, neutron-server now a/a

and add start-delay
Merge pull request #294 from cwolferh/ha_neutron_updates

Ha neutron updates
HA add constraints, start-delays for cinder, glance, heat
Merge pull request #295 from cwolferh/ha_glance_updates

HA add constraints, start-delays for cinder, glance, heat
a less fragile check for cluster_control_ip in pcmk setup
kvm config in compute nodes by puppet fact
Add 10s delay to horizon for consistentency with other services
Merge pull request #298 from bcrochet/horizon-delay

Add 10s delay to horizon for consistentency with other services
Merge pull request #296 from cwolferh/check_for_cluster_control_ip

a less fragile check for cluster_control_ip in pcmk setup
Merge pull request #297 from cwolferh/qemu_kvm_fact

kvm config in compute nodes by puppet fact
Change network_floating_range default

The defaults for the network_fixed_range and network_floating_range
parameters were the same.  Even if this is just defaults that we
expect to be overridden, they should not be the same as that would be
a broken configuration.  They must be separate networks.  Go ahead and
change the defaults of one of them (floating in this case) to be
something that would work.
Merge pull request #300 from russellb/fixed_floating_range_defaults

Change network_floating_range default
BZ #1113294 - HA cinder db_sync fails on 2nd and 3rd nodes

https://bugzilla.redhat.com/show_bug.cgi?id=1113294

Add a puppet dependency to make sure that the first node completes a
db_sync before it is attempted on the other HA nodes.  The same logic
applies for cinder and glance.
remove neutron-db-check, refs to neutron-agents-pre from HA neutron