Re-enable update with last Puppet references

This reverts commit 6e48cbc9d5d371aca0a804a6b9834153b6266606.

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Merge pull request #616 from enovance/refs-openstack

Re-enable update with last Puppet references
[galera] Improve clustercheck script
[galera] Some master/slave tweaks

This adds some tweaks for galera master/slave setup

It also allows to customize the galera gcache size,
This value depends mainly of the database traffic.
But the default value of 128M is clearly to low for us, this means
if a down node comeback and the data that need to be transfered is
greater than 128MB a full sync if done instead of an incremental.

So we use 1G by default and that should
changed in case of a deployement with a big database workload.
[galera] use same value for galera and haproxy max conn

Use same value for galera and haproxy max connection

The extra connection will be dropped by haproxy instead of galera.
Merge pull request #617 from sileht/sileht/galera-tweak

Sileht/galera tweak
Disable TSO on all systems

Even on RHEL7 + OSP5, there is an issue on TSO/GSO. So we need to ensure
that it's disable also on RHEL7/CentOS7 systems.

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
identity: disable trove by default

Trove (Database as a service) is still experimental and should be
disabled by default to avoid error with current default configuration.

This patchs does it by adding a new parameter trove_enabled (False by
default) and only create Keystone endpoint if this parameter is at True.

It also avoids to see the Database panel in Horizon by default.
Travis: add QA for Puppet 3.6, 3.7 and 3.7.1

Add more versions of Puppet in the QA process.
Merge pull request #621 from enovance/disable-trove

identity: disable trove by default
Merge pull request #618 from enovance/tso-rh

Disable TSO for all systems
Merge pull request #622 from enovance/travis-puppet

Travis: run QA on Puppet 3.{2,6,7}
Refactor all Neutron configuration

Refactorization from puppet-neutron:
* use neutron::agents::ml2::ovs in a new class: cloud::network::vswitch
* include this class automatically in network & hypervisors classes.
* allow some flexibility in agent configuration and open the class to
  eventual other drivers. Currently, only ML2 with OVS is supported.
* Cleanup cloud::network to avoid useless code.
* Refactorize provider networks usage.
* make cloud::network::controller plugin agnostic
* make cloud::network plugin flexible with ML2 by default
* Deprecation of somes parameters in cloud::network with a warning but
  no backward compatibility.
* Update unit tests.

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Merge pull request #619 from enovance/neutron-refacto

Refactor all Neutron configuration to be more flexible and support different backends
Allow to manage or not TSO issue

We need to allow some flexibility with TSO issue and allow the end-user
to disable the management of TSO.

Since TSO issue only affects GRE tunnels, when running VXLAN we should
be able to not manage TSO issue. So let's add a new parameter to manage
or not this feature.

Why not using facter to detect the kernel & using neutron flags to
detect the tunneling mode? Because we want to be sure that we have a
real flexibility and allow end-user to use a specific kernel (with a fix
or not) and make the choice to enable or not TSO/GSO.
Merge pull request #624 from enovance/tso-flexibility

Allow to manage or not TSO issue
Fix TSO lock file check when running the script

Correctly check if TSO is already started by testing the PID file
presence.
logging/agent.pp: Allow one to specify logrotate rule for td-agent

This commit allows one to specify a logrotate rule to manage logging
agent log.

Close #625
Merge pull request #629 from enovance/fix-tso-lock

Fix TSO lock file check when running the script
Merge pull request #627 from enovance/enhancement/625/spredzy

logging/agent.pp: Allow one to specify logrotate rule for td-agent