On Wed, Apr 22, 2015 at 2:18 AM, Thomas Graf <tg...@noironetworks.com> wrote:
> On 04/21/15 at 08:48pm, Alex Wang wrote: > > > > > > and how do you restore them later? > > > This looks like a dup of: > > > http://openvswitch.org/pipermail/dev/2015-April/054378.html > > > > > > > > Thx for the reminder, this is a duplicate... not aware of the patch~ > > > > For the restoration, when ovs is restarted, it will read ovsdb config in > > (cond.db) and recreate all bridges+tunnel ports. When creating the > tunnel > > ports, the vport-* modules will be reloaded automatically. So, we do not > > actually need to explicitly reload the vport-* modules. > > I've been told that it is not entirely uncommon to disable > autoloading of kernel modules and only allow loading of them > through a particular well controlled security context. Such > environments may rely on the principle that the vports are in > fact already loaded when ovs-ctl returns. > Thx for the explanation~! I'll take a note of this~ Thanks, Alex Wang, _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
