fix for Ubuntu six pip package, added to the crowbar.yml for
downloading the latest version via pip

Version upgrade is required, because for current
neutron-server required the six version above 1.4.2
metering_agent service name is fixed for Ubuntu.
Missing cache directory creation is added for Ubuntu.
Missing ml2 plugin directory creation is created for Ubuntu
Missing package name is added for Ubuntu installation process.
neutron-server run fix for Ubuntu.
fixup! neutron-server run fix for Ubuntu.
Use internal_auth for cross-service communication

At least in one case the access over public was flakey,
and we shouldn't do this in the first place.
Add optional crowbar-applied boolean attribute to schema

We add a crowbar applied attribute to mark the proposal as applied after
the chef run. This allows the UI to show that the current form of the
proposal has been 'applied' successfully (i.e. chef-client completed the
run w/ success) and that the proposal was not modified after that.

Update the proposal_schema_revision, so we can add the attribute to
schema for ('3rd party') barclamps that currently do not have it.

Refs: crowbar/crowbar#2044 (which adds this attribute to barclamps which
lack it), crowbar/barclamp-crowbar#1068 (which marks the proposals as
applied) and https://bugzilla.novell.com/show_bug.cgi?id=877486
Merge pull request #122 from bkutil/add_applied_attribute

Add optional crowbar-applied boolean attribute to schema
Merge pull request #121 from dirkmueller/master

Use internal_auth for cross-service communication
Switch LBaaS on by default

It also causes the Service provider plugin to be loaded, which
is used by various tempest tests. And it seems people forget
about enabling it before running tempest.
Strip trailing whitespace
Use secure password

We really want to protect this from accidental
guessing.
Merge pull request #116 from rhafer/roxy-merge

Merge latest ubuntu fixes from roxy
Merge pull request #124 from dirkmueller/security

Security
Merge pull request #123 from dirkmueller/master

Switch LBaaS on by default
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.