Unconditionally enable the FWaaS plugin

It just works, is not needing any additional deps,
and makes tempest pass rate higher.
Fix nova admin id detection

With the fix of admin_auth_url to be unversioned, this regressed
as the url no longer works. We need to use the public auth url
here anyway, so switch to that.
Merge pull request #107 from dirkmueller/fix_admin_edit

Fix nova admin id detection
Merge pull request #106 from dirkmueller/neutron_fwaas

Neutron fwaas
Add support Neutron LBaaS

This can be used to load balance or fail-over VIPs between
two VMs.
switch to using KeystoneHelper.keystone_settings

the new KeystoneHelper should take care of retrieving
service_user/service_password so we don't have to have a separate helper
for that in the neutron cookbook
Merge pull request #93 from mapleoin/keystone_settings

switch to using KeystoneHelper.keystone_settings
Enable deletion of namespaces for SUSE

SUSE has the necessary fixes included, and not deleting
namespaces causes significant performance loss for
tempest runs.
Merge pull request #108 from dirkmueller/release/stoney/master

Enable deletion of namespaces for SUSE
Merge pull request #80 from dirkmueller/neutron_lbaas

Add support Neutron LBaaS
Make sure network does come up correctly during reboot

OpenVSwitch when started during boot will automatically recreate bridges and
add the physical interfaces according to its configuration database. It will
however not automatically reassign the IP addresses from the physical interface
to the internal bridge port. As a result of this network connectivity on that
interface is lost.  This is especially problematic when the physical interface
that hosts the "admin" network (ususally eth0) is enslaved into one of the ovs
bridges (e.g. 'br-fixed' when using an openvswitch with the vlan driver). In
that case the node will loose connectivity to the admin node and the initial
chef-client, which would usually fix the IP assignments will fail.

By creating and enabling init scripts that transfer the IP addresses from the
physical (or bond) interfaces to the correct ovs bridge we make sure that the
node's network is working even before chef-client ran for the first time.

This should also help us to remove the requirement for a separate physical
interface for the "nova_fixed" network when using openvswitch with VLANs.
(See http://github.com/crowbar/barclamp-quantum/pull/113)

Addresses: https://bugzilla.novell.com/show_bug.cgi?id=825644