Why it's so bad idea? I know, that in case of vswitchd going down, we'll
loose our config, but starting up all vifs after hard reboot is also
very big problem for us.
What you would suggest than?
On 09/19/2014 04:59 PM, Ben Pfaff wrote:
On Fri, Sep 19, 2014 at 04:24:38PM +0200, Pawe?? Szczepaniak wrote:
I wanted to disable starting ovsdb-server on our debian servers, as
we don't need it and it can cause problems after hard reboot.
We use it with LACP, configured in /etc/network/interfaces. On
machine we have also installed XEN, which is creatig vifs for each
guest. Problem appear after hard reboot, when all vifs from db are
created and we cannot start domUs, because we cannot create vif for
it.
Currently I simply remove conf.db on start, so when it starts,
create a new file and fill it, but it's not cleanest solution. We
would like to get rid of ovsdb-server running after
openvswitch-switch, but I was unable to track down method for it.
It's a bad idea not to run ovsdb-server.
--
Paweł Szczepaniak
System Administration
InnoGames GmbH
Friesenstraße 13 - 20097 Hamburg - Germany
Tel +49 40 7889335-0
Fax +49 40 7889335-22
Managing Directors: Hendrik Klindworth, Eike Klindworth, Michael Zillmer
VAT-ID: DE264068907 Amtsgericht Hamburg, HRB 108973
http://www.innogames.com – pawel.szczepan...@innogames.com
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
