* Ansis Atteka (aatt...@nicira.com) wrote:
> On Thu, Mar 1, 2012 at 9:28 PM, Chris Wright <chr...@sous-sol.org> wrote:
> > insert_openvswitch_mod_if_required () {
> > - # If openvswitch_mod is already loaded then we're done.
> > - test -e /sys/module/openvswitch_mod && return 0
> > + # If @OVSKMOD@ is already loaded then we're done.
> > + test -e /sys/module/@OVSKMOD@ && return 0
> >
> From upgrade perspective: If the new user-space would want to use
> openvswitch.ko, but the old one was using openvswitch_mod.ko,
> then could we somehow make this part a little bit more intelligent,
> so that upgrade would be seamless and the user would not have to
> manually unload the old kernel module (see force-reload-kmod command)?
I think the debian packaged kmod will unload the module as part of
package update (package removal, specifically). The update will reload
it by the new name. The rhel packages might need some help there.
No issue for Fedora packages which will always have the new name.
ovs-ctl could check oldname as well as new name when unloading as part
of force reload.
> Although, I guess a system reboot would be anyway necessary if user
> upgraded from a linux kernel that does not have openvswitch module and
> the one that has. So it would be up to user to do both upgrades in one
> shot.
Not necesarily if we change the external module's name as well.
thanks,
-chris
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
