Allow to disable TSO on L3 agent nodes

When running Linux kernel 3.14, TSO/GRO could be enabled on compute
nodes to improve performances.

To improve north-south performances, this feature is needed on Neutron
L3 agent nodes.

This patch add TSO management for Neutron L3 agent and also
change the behavor for previous patch in ensuring that we use a kernel
>= 3.14 for both hypervisor & compute nodes.

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Merge pull request #610 from enovance/tso-controllers

Allow to disable TSO on L3 agent nodes
Check if VTX is enabled on hypervisor nodes

VTX is required when using KVM as hypervisor on compute nodes.

When the fact will be merged upstream, the lib/facter/vtx.rb file will be
dropped to use the one from facter-core.

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Merge pull request #611 from enovance/vtx-check

Check if VTX is enabled on hypervisor nodes
keepalived: allow vrrp traffic on a dedicated interface

Signed-off-by: Dimitri Savineau <dimitri.savineau@enovance.com>
Merge pull request #558 from dsavineau/enhancement/550

keepalived: allow vrrp traffic on a dedicated interface
Update with last Puppet references

- Update refs of OpenStack modules
- Add puppet-openstacklib which is a new dependency
- Update telemetry classes and specs to support the new git ref

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

Update with last Puppet references
loadbalancer: Allow user to bind multiple public/private ips

Currently, a deployer can only bind on the loadbalancer 1 ip per
network (be it public, internal, admin, etc...).
If a deployer wants to bind to the ipv6 and ipv4 at the same time he
couldn't. This patch aims to fix that.
Merge pull request #552 from enovance/bind_ipv4_ipv6_haproxy

loadbalancer: Allow user to bind multiple public/private ips
Revert "Update with last Puppet references"

Temporary revert, some puppet issues need to be fixed.
This reverts commit 3b65c41e483f7e3381e842eb27b3ef5f5fb81296.
Revert "loadbalancer: Allow user to bind multiple public/private ips"

Error to compile the catalog:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: member(): Requires array to work with at
/etc/puppet/modules/cloud/manifests/loadbalancer.pp:262 on node
os-ci-test10
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

The patch is going to be reverted and redone by spredzy.
This reverts commit 78397ab2406c66f76614b91672e5b2320f6cdfab.

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
loadbalancer: Allow user to bind multiple public/private ips

Currently, a deployer can only bind on the loadbalancer 1 ip per
network (be it public, internal, admin, etc...).
If a deployer wants to bind to the ipv6 and ipv4 at the same time he
couldn't. This patch aims to fix that.
Merge pull request #614 from enovance/bind_ipv4_ipv6_haproxy

loadbalancer: Allow user to bind multiple public/private ips
install: Automatization of the install-server

This commit aims to make it possible to automate the install server.
It allows the automatization of the following pieces :

  * The Jenkins Server
  * The Puppet Master Server
  * The PuppetDB server