Neutron ovs plugin should not require vswitch::ovs

I don't see any reason openvswitch components should be required on the same
machine than the neutron ovs *plugin*. It is definitely required for the
neutron ovs *agent* though.

Change-Id: I1d7128f8a79d788b48af4acf504d48a19e8fe12b
Add FWaaS service plugin

Configure fwaas_driver.ini to support FWaaS service plugin.

implement blueprint fwaas-support
Change-Id: I3b92f6045ef56f6a7215323ac8595acb460026d7
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Add VPNaaS service support

VPNaaS is a new service in Neutron (Havana release).
This patchs aims to support default driver (OpenSwan) by installing
packages & configuring vpn_agent.ini.

implement blueprint vpnaas-support
Change-Id: I7f8a3fbc1b175eb0ea3a8868a04ea648c2b8f1b2
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Add Neutron service_plugins support

In Havana, Neutron has now "service insertion" used
by some networking services as plugins.

This patchs aims to provide this new feature and also configure:
- FWaaS (Firewall)
- LBaaS (Load-Balancing)
- VPNaaS (Virtual Private Network)

implement blueprint fwaas-support
implement blueprint vpnaas-support

Change-Id: I07d85d8d1832af8bf9cb27346b3c096f5e5aa183
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
Merge "Add VPNaaS service support"
Perform redhat specific configuration for cisco plugin

Fix to ensure the plugin.ini has link to cisco_plugins.ini when
enabled. Updated tests as well to account for the same.

Change-Id: Id269db88042625a3d7f12540d07c5033d06e160a
Preparing neutron (quantum) for 2.2.0 release.

Updated version in Modulefile.
Added release notes to README.md.

Change-Id: I9755c26f6dd374612f15376db6de7e4782bb278b
Upstream changed default quota_driver

For Neutron Havana-rc2, the default quota_driver has been changed
to a more sensible value. Also, Horizon (and possible others) now
expects this quota_driver and will show errors if set otherwise.

See also the upstream bug and change:
https://bugs.launchpad.net/neutron/+bug/1189671
https://review.openstack.org/#/c/50378/

Change-Id: I47bd2fe8aa29614f1eaf15b9a2063883bb17d0e6
Scrap nonsense provider setting requirements

Currently, if any provider setting is defined, it's enforced that
the other settings are defined as well. This is wrong and in some
cases even contradicts with Neutron.

Different settings need to be either present or absent depending on
the various network types. It would be a huge overkill to validate
all the possible combinations, particularly since relying on
Neutron to do the proper checks is good enough.

Change-Id: I36ad13da6d796d79e5d0050a13f1766455b478be
Fix file permissions on examples/neutron.pp

The examples/neutron.pp file had mode 755 when it should have 644.

Change-Id: Ic5c5483cf616547deecf63ec9fa725b8c9ff4794
Merge "Fix file permissions on examples/neutron.pp"
params.pp: Rename client_package_name to client_package, and correctly define it

Leaving this unset leads to problematic consequences if another
module does the same, as both would alias the package to nil.

node bob {
  include heat::client
  include neutron::client
}

Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Puppet::Parser::AST::Resource failed with error ArgumentError:
Cannot alias Package[python-neutronclient] to [nil] at
/etc/puppet/modules/neutron/manifests/client.pp:20; resource
["Package", nil] already declared at
/etc/puppet/modules/heat/manifests/client.pp:17 at
/etc/puppet/modules/neutron/manifests/client.pp:20 on node bob
Warning: Not using cache on failed catalog Error: Could not retrieve
catalog; skipping run

Companion change in puppet-heat: Ib0ae86d7ff406039f4b361a65c2e092d2a321a77

Change-Id: I63266ca8faa807b8aef051b319a06fa323757ceb
Merge "params.pp: Rename client_package_name to client_package, and correctly define it"
Ensure keystone endpoint set before service starts

As neutron-server is mostly useless without having the keystone
service+endpoint set, in the case where both keystone and
neutron-server are on the same machine, this patch adds a soft
dependency to ensure that the keystone catalog includes neutron

This has a knock on effect of fixing openstack::provisioner, which
would sometimes try to create neutron networks, the type for which
soft depends on neutron-server, without there being an endpoint
set in the keystone catalog

Change-Id: I658e1b3e2c448b9a7da9e013c4e105b9ec824893
Merge pull request #1 from stackforge/master

Update to upstream