> You totally missed the problem, so I try to explain again.
>
> The problem is that the ovs-vswitchd is started much too late in the boot
> process (in runlevel 2),
> so it is not available when debian starts the networking setup at boot time
> (started early in rulevel S).
>
> is that more clear now?
That was my understanding the first time around too. All I see you
trying to do is creating a bridge with a single port and assigning IP
address to it. So I am not sure why it matters if ovs-vswitchd starts
late. Once it starts, the startup script should look at the
/etc/network/interfaces file and create the bridge. And since you say
that your interfaces file works during non boot up phase, your
configuration must be correct.
So you will have to debug more and tell me why it is not working for
you. The most recent change done to this front is
--- a/debian/openvswitch-switch.init
+++ b/debian/openvswitch-switch.init
@@ -31,6 +31,7 @@
test -e /etc/default/openvswitch-switch && . /etc/default/openvswitch-switch
network_interfaces () {
+ [ -z "${RUNLEVEL}" ] && return
INTERFACES="/etc/network/interfaces"
[ -e "${INTERFACES}" ] || return
bridges=`awk '{ if ($1 == "allow-ovs") { print $2; } }' "${INTERFACES}"`
You can undo that change in your startup script and tell if that works
(I do not have a debian machine handy to test. It works fine on a
Ubuntu12.04)
>
>
>
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
