[ovs-dev] [PATCH] openvswitch init script modifications for kvm and lxc hosts

Pasi Kärkkäinen pasik at iki.fi
Thu Dec 16 15:14:06 UTC 2010


On Thu, Dec 16, 2010 at 09:47:58AM -0500, Patrick Mullaney wrote:
> Hi Pasi,
> 
> Thanks for the link. I had actually read that before at one point.
> The confusion, having never run xenserver, was what "host OS" gets
> bundled with the xen hypervisor to form "XenServer"(something tells
> me its an rpm packaged linux :-) ). I am assuming its a custom linux.
> 

The "host OS" (=dom0) for XenServer/XCP is CentOS 5 based. 

> That said, if we want to support both kvm and xen out of one
> set of startup scripts, we need at least some of the changes I proposed.
> The other option is to have 2 sets of scripts and that would have its
> own downside :-).
> 

Yeah, traditional Xen (hypervisor only) uses either xm/xend or xl/libxl
toolstack, while XenServer/XCP uses xe/XAPI toolstack.

They're different toolstacks. XAPI is made for multi-host pools,
while xm/xend/xl are more for a single-host setups.

-- Pasi

> Thanks.
> 
> 
> On Thu, 2010-12-16 at 16:01 +0200, Pasi Kärkkäinen wrote:
> > On Wed, Dec 15, 2010 at 09:48:38PM -0500, Patrick Mullaney wrote:
> > > Hi Ben,
> > > 
> > > > There's some confusion here I think.  XenServer is a whole OS, just as
> > > > SuSE is.  As far as I know, no one carves out bits and pieces of
> > > > XenServer and installs them on top of other distributions.  (Maybe you
> > > > know differently?  I am no expert on this.)
> > > Actually, I'm not an expert here either. Its probably just my
> > > confusion of xen vs. xenserver.
> > > 
> > 
> > http://wiki.xen.org/xenwiki/XenCommonProblems#head-cb533d9953d9d4b0c1f23d968331f3a620209fc3
> > 
> > -- Pasi
> > 
> > > > 
> > > > So, assuming I'm right about that, then there may be no need for it on
> > > > SuSE, because admins want OVS to run if it is installed (as you say).
> > > > 
> > > > > > It doesn't make sense to install etc_init.d_openvswitch-xapi-update on
> > > > > > SuSE at all, since it will at most print an error message and exit with
> > > > > > status 1.  So it seems unnecessary to modify that file.
> > > > > 
> > > > > I can not package it, but on the chance that someone wanted to use suse
> > > > > and xenserver, it might be easier if it was just there. My changes were
> > > > > just about LSB compliance, other distros might care about this too.
> > > > 
> > > > Ah, OK.  Fine.
> > > > 
> > > > > Another approach might be to move basic startup into a separate common
> > > > > script area and then have the xenserver scripts deal with starting
> > > > > stuff specific to it. I don't have xenserver here and didn't watnt to
> > > > > break it on a first attempt. The nice part is I think this should
> > > > > work for both cases now.
> > > > 
> > > > That's a good idea too.
> > > > 
> > > > I haven't done that yet, but I've tweaked these patches to my liking and
> > > > I'll send them back out to you and the list in a minute.  I've retained
> > > > your authorship and sign-offs, and tried to note the changes that I made
> > > > in the proper format, but please do review the changes that I made to
> > > > ensure that they make sense.
> > > Cool - thanks. I'll check them over.
> > > 
> > > > 
> > > > Thanks,
> > > > 
> > > > Ben.
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > dev mailing list
> > > dev at openvswitch.org
> > > http://openvswitch.org/mailman/listinfo/dev_openvswitch.org
> 
> 




More information about the dev mailing list