BZ#1121185 - rabbitmq AMQP traffic should be load balanced accross all nodes

https://bugzilla.redhat.com/show_bug.cgi?id=1121185
BZ#1124950 - Quickstack nova compute manifest not setting qpid config

https://bugzilla.redhat.com/show_bug.cgi?id=1124950
Merge pull request #330 from jeckersb/qpid_fix

BZ#1124950 - Quickstack nova compute manifest not setting qpid config
Merge pull request #321 from jeckersb/rabbitmq_haproxy_aaa

BZ#1121185 - rabbitmq AMQP traffic should be load balanced accross all n...
controller_common: fixed rabbitmq provider parameters handling for glance
Merge pull request #331 from gabrielecerami/glance-rabbitmq-missing-parameters

WIP: controller_common: fixed rabbitmq provider parameters handling for glanc...
BZ #1123316 - Add nova-conductor with nova-scheduler to colocation constraint

https://bugzilla.redhat.com/show_bug.cgi?id=1123316
Add support to enable ML2 Cisco Nexus plugin
Merge pull request #311 from pkilambi/master

Add support to enable ML2 Cisco Nexus plugin
ceph/rbd on compute: add missiing nova.conf param
Merge pull request #333 from cwolferh/ceph_nova_conf_tweaks

ceph/rbd on compute: add missing nova.conf param
Merge pull request #332 from jguiditta/ha_constraints

BZ #1123316 - Add nova-conductor with nova-scheduler to colocation const...
BZ #1123293 - start-failure-is-fatal should be true.

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

This setting should not be needed any longer for icehouse.
BZ #1123300 - haproxy check options missing interval parameter

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

From BZ: "HA: all "check" options are missing the interval
parameter. This can cause higher recovery times in case of failure."
BZ #1123314 - pacemaker heat op monitor interval to 60s

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

From BZ: "Rubygem-staypuft: HA: Relax the openstack-heat-engine: op
monitor interval to 60 seconds.

Now it's openstack-heat-engine: op monitor interval=30s

appears to be too resource consuming in some cases (like
openstack-heat-engine and causes false positives."
BZ #1123318 - HA: set max_retries=-1 for accessing the DB

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

Services will now continue to retry accessing the db on startup if it
is not available, as the max_retries configuration value in the
openstack .conf files is now set to -1.

From BZ:
"HA: All services are missing max_retries=-1 settings for accessing the DB.

This means that if the DB is not started before the service, the
service will fail to start. This behaviour is currently mitigated by:
start-failure-is-fatal: false, but it is technically incorrect."
Merge pull request #339 from cwolferh/bz1123318_max_retries_-1

BZ #1123318 - HA: set max_retries=-1 for accessing the DB
Merge pull request #335 from jguiditta/ha_cleanup

BZ #1123293 - start-failure-is-fatal should be true.
Use "str2bool_i" instead of "== 'true'"

Generated with:

grep -ril "== 'true'" puppet | xargs sed -i -e "s/map_params('\([^']*\)') == 'true'/str2bool_i(map_params('\1'))/"
BZ#1127816 - HA neutron sets pcs properties before starting service

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

Make quickstack::neutron::all contain neutron::server, so that
resources after quickstack::neutron::all also are after
neutron::server.

See also:
https://docs.puppetlabs.com/puppet/3/reference/lang_containment.html