vlans should come up after their device (bond, bridge, etc)

[Dan Prince]

I'm hitting an issue where a VLAN on top of a bridge doesn't work if the bridge isn't already configured first.

The example here doesn't yet work right: https://review.openstack.org/#/c/181999/

The bridges both come up fine... but the VLANs don't because they are started before bond1.

Subsequent runs of os-net-config also don't even try to start the VLAN because the configuration hadn't changed... (perhaps this is a separate bug)

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/182023

[OpenStack Infra (hudson-openstack)]

Change abandoned by Dan Sneddon (<email address hidden>) on branch: master
Review: https://review.openstack.org/182023
Reason: This isn't needed for now. We might revisit the interface ordering, but the problem we were trying to solve turned out to have a different solution.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/183171

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/183171
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=90f15e38f1e4d80b81f4fa1444dde717917ef8ad
Submitter: Jenkins
Branch: master

commit 90f15e38f1e4d80b81f4fa1444dde717917ef8ad
Author: Dan Prince <email address hidden>
Date: Thu May 14 14:58:10 2015 -0400

    ifcfg: don't set VLAN=yes if is an ovs_port

    When using the ifcfg provider vlans on bridges (or bonds)
    fail to startup correctly. This is because VLANs on an OVS
    bridge are configured as internal ports and these should not
    have the VLAN=yes or PHYSDEV ifcfg settings specified.

    Change-Id: Ieb743eda8f0a25cdaca43bdea767af26bf504f15
    Closes-bug: #1453904