Configure TCP keepalive setting to all nodes

In some cases, it has been observed that services keep their
connection to RabbitMQ when they should not (e.g. during a
controller server hard reboot), creating instability. This patch
aims at fixing this by setting TCP keepalive parameters for
RabbitMQ connections, and setting kernel parameters to send
keepalive packets more often.

Change-Id: I7688a86e4ff617f20d6767f156c5d880e0d4d619
Fixes: bz#1167414
The httpd service should only be installed on the controller node

At the moment the httpd service is installed on every node. It is
not necessary to install the httpd service on the network, storage,
and compute nodes.

Change-Id: I1656a6679fb9bfc26ef4b59b2e2e28dc7f68a71e
Packstack Plugins Clean-up

- Deleted unused import
- Pep8 compliance
- Deleted unused variables

Change-Id: I45f135b2467427cd7ee3b5ba32745af2a631458a
Signed-off-by: Gael Chamoulaud <gchamoul@redhat.com>
Open VXLAN port only to NETWORK_HOSTS

Packstack opens VXLAN port without source-address limit.

It should be open only for source addresses of mahcines running
neutron-l2-agent (like openvswitch)

Fixes: rhbz#1144816

Change-Id: I4c1da8635cf03fa1571c1dad289ba737f65a301d
Use is_virtual instead of is_virtual_packstack

At least on Virtualbox is_virtual_packstack is not working.

$ grep hypervisor /proc/cpuinfo > /dev/null && echo true || echo false
false

Change-Id: I8a1fec615de3eb774950f75e38dfbf334bd81ba2
Merge "Packstack Plugins Clean-up"
Merge "Configure TCP keepalive setting to all nodes"
Merge "Use is_virtual instead of is_virtual_packstack"
Remove deprecated code in packstack/plugins/serverprep_001.py

Change-Id: Ic64b7ea781441267a179bda6b3c69320a049cf60
redis-based group membership coordination for ceilometer

If CONFIG_CEILOMETER_COORDINATION_BACKEND is set to 'redis'
then a redis manifest is created to install redis on the
appropriate host and configure the ceilometer-central-agent
and ceilometer-alarm-evaluator to use it for group membership
coordination.

The other valid option is 'none', in which case no coordination
will be done. 'redis' is the default.

Change-Id: I07261f5fd433c13a57a614c15b13f0cad6c79d6a
Fix issues if ML2 neutron is configured with linuxbridge

+  For linuxbridge, the external_network_bridge option should be empty.
   See: https://github.com/openstack/neutron/blob/master/etc/l3_agent.ini#L43
   We should allow CONFIG_NEUTRON_L3_EXT_BRIDGE to have an empty value.

+  The example given in usage for NEUTRON_LB_PLUGIN_AND_AGENT is false.
   The linuxbridge need to have a mapping between a network and interface,
   not a network and a bridge. See: https://github.com/openstack/neutron/
   blob/master/etc/neutron/plugins/linuxbridge/linuxbridge_conf.ini#L23

+  create_l3_manifests try to read CONFIG_NEUTRON_OVS_BRIDGE_MAPPING
   for all types of bridge. This patch fix the issue by moving the
   'if openvswitch' test.

Closes-Bug: #1399733
Change-Id: Ia7297c9941d93f822ed4b7ea4f4bf4932304ac64
Use '.pp' as default ending for template files

Change-Id: Id5072e5d9f296403b272ac3f57fff2a19f7dea74
Merge "Fix issues if ML2 neutron is configured with linuxbridge"
Merge "Open VXLAN port only to NETWORK_HOSTS"
Fix Tempest Provisioning

- Use 'CONFIG_PROVISION_CIRROS_URL' instead of
  'CONFIG_PROVISION_TEMPEST_CIRROS_URL' which doesn't exist.

Change-Id: Iecc560cddb45dc3fc9c5b74dd852304e5ea19390
Signed-off-by: Gael Chamoulaud <gchamoul@redhat.com>
Change the APP_NAME to Packstack

Instead of 'Welcome to Installer setup utility' it should be
'Welcome to the Packstack setup utility'.

Change-Id: I698d17645f4a53ce738be5ea463335466408ed6e
Update to Fedora 21 and remove Fedora 19 support

With the release of Fedora 21 the end of life of Fedora 19 will come in
1 month (https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle) and
support for Fedora 19 should be dropped.

Change-Id: Ib34f38ebcab07254be0d5edba2964d476767f998
Print the used logfile also at the beginning

Change-Id: Icb3a44c36b50b31b3436c3e693f6d88879b70080
network: set the default floating ip pool name

The default public network used by packstack to create
floating ip is 'public' we should configure nova.conf to use
the good value during the build process to provide the possibility
to use the command 'floating-ip-create' without the optional
argument 'pool'.

Closes-Bug: #1356462
Related-Bug: #1355621
Change-Id: Ie5158b44dee320816fa4eae20bb2e28a4e58c451
Merge "redis-based group membership coordination for ceilometer"