Re: [Xen-API] Which Xen API

[shreyas pandya <pandyashreyas1@xxxxxxxxx>]

Thanks Shuklin (and Matthias for asking this question) this information 
was very usefull.
The notion of these different management tools for xen was very naive in 
my mind
Also I want to know where the source code of these are maintained and 
where are they
located in filesystem in XCP installation

-thanks in advance


On 07/13/2011 05:32 PM, George Shuklin wrote:
> There is some fog around terms.
>
> See:
>
> xl - is low-level management system for xen (within single host). It 
> allows to do some minimal operations, but used by more complicated 
> components like xapi, so it's better not touch xl without prior thoughts.
> xapi - an pool (cloud, heh) management system, allowing to do 
> migration, storage and  network management for virtual machines and so 
> on. It's name of component, not an 'API-name'.
> XenAPI - is protocol specification. AFAIK XenAPI is supported by xend 
> and xapi with minor difference around 'pool' conception.
> xe - command line tool for xapi management
> XenCenter/OpenXenManager - GUI tools for xapi management (for 
> enterprise only, not very suited for ISP).
> libvirt - RedHat-driven library (and shell) to control different 
> virtualization systems in same way. Right now RH run away to KVM, so 
> libvirt is not best choice.
> If you wish to control XCP pool by your own software (ISP things or 
> batch operations control), you must use XenAPI. But I hear some guys 
> use a system ('xe arguments'); call.
> XenAPI is well described and allow to do about 99% of needed tasks 
> (there is a little troubles with automatic installation, but they are 
> outside the XenAPI scope).
> On 13.07.2011 08:19, Matthias Blankenhaus wrote:
> > Hello !
> >
> > I am getting into Xen and I am a bit overwhelmed about the competing 
> > offerings in the MGMT-API area.  I understand that xend (xm) is going 
> > away some time and that XL is the latest and greatest.  However, then 
> > we have of course XenAPI aka XAPI which seemed to be widely used.  I 
> > am trying to decide against which API I should code.  I was unable to 
> > get the XEN driver working for the latest libvirt, yet another 
> > contender.
> > Your input is much appreciated.
> >
> > Thanx,
> > Matthias
> _______________________________________________
> xen-api mailing list
> xen-api@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xen-api
_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api