[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] FW: [PATCH 1/4] Addition of XenAPI support to libvirt



On Tue, Mar 23, 2010 at 01:21:55PM +0000, Ewan Mellor wrote:
> On Tue, Mar 23, 2010 at 12:43:09PM +0000, Pasi Kärkkäinen wrote:
> 
> > On Fri, Feb 19, 2010 at 03:56:56PM +0100, Daniel Veillard wrote:
> > > 
> > > >   Similary libcurl i looked at in configure.ac for ESX, this need
> > > > to be modified to be checked more generally and the LIBCURL_*
> > > > variables need to be used here too.
> > > > 
> > > > -> I didn't quite understand the libcurl part you mentioned. I too noticed that ESX has
> > > > a piece of code in configure.ac to set the libcurl flags, do you want me to do add a similar
> > > > bit of code in configure.ac for XenAPI that defines LIBCURL flags and then add in my Makefile.am?
> > > 
> > >   the code to look for libcurl in configure.ac is currently only
> > > activated if esx support is on. It must be run if either esx or xen-api
> > > are selected, the ESX portion need to be modified accordingly, and 
> > > your parts and Makefiles patches too.
> > > 
> > 
> > Hmm.. is XenAPI the correct name? At least earlier it was used to refer to the 
> > xend stuff in the traditional Xen.
> > 
> > 'XAPI' name has been used for the newer XenServer/XCP xapi/xe stuff? 
> 
> xapi is the name of the daemon in XenServer/XCP.  The API itself is called
> XenAPI, and yes, there is a implementation in xend too.  XenAPI is the correct
> name, because it's the API that we're meeting, not a specific implementation
> of it.
> 

Thanks for clearing that up!

-- Pasi


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]