[ovs-git] Open vSwitch: debian: force-reload-kmod while package upgrading. (master)

dev at openvswitch.org dev at openvswitch.org
Tue Apr 23 16:21:04 UTC 2013

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Open vSwitch".

The branch, master has been updated
       via  19cbf2b8a49d18eb8a8047c3b03953e6e9f0116f (commit)
       via  ff23db30f98a53d8f96c429a3441d6a678c731fd (commit)
      from  0f5edef014cc4ca701dab6006e9f59d24adad266 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 19cbf2b8a49d18eb8a8047c3b03953e6e9f0116f
Diffs: http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=19cbf2b8a49d18eb8a8047c3b03953e6e9f0116f
Author: Gurucharan Shetty <gshetty at nicira.com>
debian: force-reload-kmod while package upgrading.
Currently, when we upgrade openvswitch packages, we do a restart
of userspace daemons automatically. This does not replace the
kernel module.

But almost everytime, we want to use the new kernel module
that comes with the new version. This means that we need to
manually do a "force-reload-kmod". This step, reloads the
kernel module and also restarts the userspace daemons. This gives
us a total of two restarts of userspace daemons. This is quite
expensive in a hypervisor with hundreds of VMs sending real traffic.
This also hurts the controller as it gets two reconnections in a short
amount of time.

With this patch, during a package upgrade, if the kernel module
on disk is different than the one that is loaded, we will
automatically do a force-reload-kmod while openvswitch-switch
is installed. If not, we will just do a "restart" like before.

One can install the kernel package first and then install the userspace
packages in 2 separate steps to enforce a single 'force-reload-kmod'.

If anyone wants to just restart the userspace package instead of
force-reload-kmod, they can set the value of OVS_FORCE_RELOAD_KMOD=no
while installing the package.
Ex: OVS_FORCE_RELOAD_KMOD=no dpkg -i openvswitch-switch*

Signed-off-by: Gurucharan Shetty <gshetty at nicira.com>

commit ff23db30f98a53d8f96c429a3441d6a678c731fd
Diffs: http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=ff23db30f98a53d8f96c429a3441d6a678c731fd
Author: Gurucharan Shetty <gshetty at nicira.com>
INSTALL.Debian: Update instructions related to package ordering.
If we install the userspace packages first, without a kernel module
present in the correct path, we get an error because package install
automatically tries to start the userspace daemons and we look for
a kernel module to load.

Installing a kernel module package first and then following it by
userspace package sounds like the correct way to do it. This change
in ordering helps my next commit.

Signed-off-by: Gurucharan Shetty <gshetty at nicira.com>


Summary of changes:
 INSTALL.Debian                     |   12 ++++++------
 debian/openvswitch-switch.init     |   31 ++++++++++++++++++++++++++++---
 debian/openvswitch-switch.postinst |    7 ++++---
 utilities/ovs-lib.in               |    4 ++++
 4 files changed, 42 insertions(+), 12 deletions(-)

Open vSwitch

More information about the git mailing list