Don't write the "bridge_mappings" setting when using gre tunnels

It's unneeded and breaks the openvswitch agent's automatic creation of the
br-tunnel bridge. This allows us to cleanup the common_agent recipe a little
bit as we don't need to create the ovs-bridge there anymore.
Cleanup: Remove creation of br-int

With https://bugs.launchpad.net/neutron/+bug/1328076 fixed in icehouse we don't
need to manually create the integration bridge anymore. Neutron will do that
automatically.
Merge pull request #125 from rhafer/br-int

Cleanup: Remove creation of br-int
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
Remove alert about ovs-vlan requirement

With ovs-bridge IPs being assigned during boot, before the first chef-client
run, it should now be possible to use the same physcial interface for the admin
and nova_fixed networks even with the openvswitch+vlan setup.
Merge pull request #109 from rhafer/ovs-usurp

Make sure network does come up correctly during reboot
Merge pull request #119 from rhafer/br-tunnel-autocreate

Don't write the "bridge_mappings" setting when using gre tunnels
Fix check of ha enablement of l3 agent

When neutron-server and nova-compute are deployed on the same host (non-HA),
while neutron-l3 is deployed on separate machines in a HA cluster the check as
it was before the fix would falsely assume HA mode for the openvswitch-agent on
the compute nodes. As a result the agent is not started there.

Fixes: https://bugzilla.novell.com/show_bug.cgi?id=885832
Merge pull request #126 from rhafer/l3-ha-check

Fix check of ha enablement of l3 agent