Configure plugins by name

To configure core plugin or service plugins, instead of using class
names, simpler names can also be used.

Example:
service_plugins = router, firewall, lbaas
core_plugins = linuxbridge

It is a new feature brought in Icehouse (thanks to stevedor): http://git.io/QfyiLw
Bringing it into puppet-neutron simplifies the parameters use for end-user.

Change-Id: Ib96cc8ea67e89c37226ee6b9d1ae811fa1507672
Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
ensure linuxbridge dependency is installed on RHEL

Package['neutron-plugin-linuxbridge'] is defined in
plugins/linuxbridge.pp but is missing in agents/linuxbridge.pp.

If agents::linuxbridge is used directly, the package is not defined.
This changes fixes the situation on RHEL.

The problem has already been fixed for OVS in
changeset Iedf8a607915f65b7a8cf7af99749b9b65cba7bd9

Change-Id: Ic4e15825e4f2d1f2ce2c34d2fdb01c8f6b19d491
Merge "Configure plugins by name"
Fix improper test for tunnel_types param

When VXLAN support was added to the ovs agent manifest, a new
parameter called tunnel_types was also added with the default
value being an empty array.  However, later in the code there's
an if loop that tests truth--and an empty array returns true.
This causes a line of the form:

tunnel_types =

to show up in /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
if the default value is used, which causes OVS to refuse to start.
This patch corrects the problem by properly testing the array.

Change-Id: I06ad6249ab7803676e49c026b4692f06ade269ed
Closes-Bug: #1281684