WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

RE: [Xen-API] XenAPI, xapi toolstack, XendAPI, XL

To: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-API] XenAPI, xapi toolstack, XendAPI, XL
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Tue, 17 Aug 2010 00:03:27 +0400
Delivery-date: Mon, 16 Aug 2010 13:03:26 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:in-reply-to :references:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=ovo+cZSbmffnXLsvC+L7LkjGfYx58pMHVhH1BJQYkCo=; b=YR8r9/Alh9c6TLySwllzw5pSs1+37EOgKUvpDSneT3aZvS97yQBZji+mQ3vmmM3yx2 bkStkWNeWPbiX2yDgzG/aB4Zp35Z0933CMR/G6UEnXQkTBqWpParN4rNJseLPXBk8piv C4WBs8u1DKaLegj/tmjy9UIRW9uo8tYXtfDNY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=R0r+bxQaO+XVd5clcFga/SAdVsvKLmmLO8shLY0+OupNGlXC8ghJyzSRg8GOWYxTf3 3n2D1SLVdHf6Dx34GeJ2oKOwiYXt9N7mXADnxsDlHrBTCFwtSZ0uY46WpQPmeCbqMt4N VMP8kMrhdnI959UtOOeMOMnGiTGJIfYqfpggg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <81A73678E76EA642801C8F2E4823AD2180818B3CC1@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <1281975741.22948.43.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <81A73678E76EA642801C8F2E4823AD2180818B3CC1@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thank you very much! It really helps.

I added this text to xen wiki:
http://wiki.xensource.com/xenwiki/API_History


В Пнд, 16/08/2010 в 17:52 +0100, Dave Scott пишет:
> In the beginning was "xend" (the daemon) and "xm" (the CLI) both
> written in python, which communicated over an s-expression protocol.
> * Next there was a desire to improve the protocol and also to switch
> from s-expressions to something based on XMLRPC. The "XenAPI" is the
> name for this new protocol.
> * The "XenAPI" was implemented both in "xend" (python) and in
> "xapi" (ocaml) (although "xapi" wasn't open-source back then). Note
> that "xapi" doesn't share any code with "xend": it talks to xenstore,
> makes hypercalls etc directly.
> * The version of the "XenAPI" implemented by "xend" and "xapi" have
> diverged: for example "xapi" is more focused on managing pools of
> hosts while "xend" is more of a single host service.
> * The XCI (Xen Client Initiative) people also created a toolstack,
> called "xenvm" (ocaml)
> * Next there was a desire to share more code between all toolstacks,
> to prevent confusion and accidental reimplementation. The library with
> the common code is called "libxl"
> * Next there was a desire to create a "minimal" toolstack for testing
> "libxl": this is called "xl"
> 
> So:
> 
> Toolstacks: xend (python); xapi (ocaml); xenvm (ocaml); xl (C)
> Protocols: original xend s-expressions; XenAPI (XMLRPC)
> Libraries: libxl 


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

<Prev in Thread] Current Thread [Next in Thread>