[ovs-dev] [PATCH ] debian: Fix bringup seq for OVSPort type of vlan.

Gurucharan Shetty shettyg at nicira.com
Fri Oct 30 00:19:44 UTC 2015


> I do however understand your concern with the proposed fix.
> We are trying to stay agnostic to the underlay interface (eth, vlan,
> bond...) and let the kernel handle it. Otherwise the controller would
> have to be aware of the way each server connects to the underlay and that
> may not be uniform.

I think I did not understand what you mean above. Why is using the
Open vSwitch VLAN device instead of Linux VLAN device a problem again?

>
>> Or some
>> other way to do this.
>
>
> any suggestions?

I can't think of a something right of the top of my head. We have
similar dependency issues with NFS startup scripts and they don't have
a solution either.
Ubuntu 15.04 and later is moving towards systemd and this whole
'interfaces' integration and dependency issues needs to be re-visited.
So I am hesitant to work on a quick fix here, unless you think of
something.


>
>
>>
>>> ---
>>>   debian/openvswitch-switch.links | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/debian/openvswitch-switch.links
>>> b/debian/openvswitch-switch.links
>>> index cf58073..5c7b1f1 100644
>>> --- a/debian/openvswitch-switch.links
>>> +++ b/debian/openvswitch-switch.links
>>> @@ -1,2 +1,2 @@
>>>   usr/share/openvswitch/scripts/ifupdown.sh
>>> etc/network/if-post-down.d/openvswitch
>>> -usr/share/openvswitch/scripts/ifupdown.sh
>>> etc/network/if-pre-up.d/openvswitch
>>> +usr/share/openvswitch/scripts/ifupdown.sh
>>> etc/network/if-pre-up.d/z09_openvswitch
>>> --
>>> 1.9.1
>>>
>>> _______________________________________________
>>> dev mailing list
>>> dev at openvswitch.org
>>> http://openvswitch.org/mailman/listinfo/dev



More information about the dev mailing list