Choice of Toolstacks: Difference between revisions

From Xen
Jump to navigationJump to search
(Remove much obsolete stuff about XCP and misguided encouragement to use it)
No edit summary
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
One really great feature of the Xen Project hypervisor is that there are several choices of toolstacks that can be used to manage it. Before the introduction of libxenlight, there was a complicated and inefficient toolstack situation. The issue was that xend, xapi, libvirt, etc. all needed to manage many common low-level operations, which led to code duplication, inefficiences, bugs, and wasted effort (e.g fixing the same bug in all of the toolstacks). Further, the default toolstack at the time (xend) was difficult to understand, modify, and extend.
One really great feature of the Xen Project hypervisor is that there are several choices of toolstacks that can be used to manage it. Before the introduction of libxenlight, there was a complicated and inefficient toolstack situation. The issue was that xend, xapi, libvirt, etc. all needed to manage many common low-level operations, which led to code duplication, inefficiences, bugs, and wasted effort (e.g fixing the same bug in all of the toolstacks). Further, the default toolstack at the time (xend) was difficult to understand, modify, and extend.


[[File:ToolStacks.png|500px]]
[[File:ToolStacks.png|800x190px]]


Each toolstack exposes an API, which will run different tools. The figure below gives a very brief overview over the choices you have, which commercial products use which stack and examples of hosting vendors using specific APIs.
Each toolstack exposes an API, which will run different tools. The figure below gives a very brief overview over the choices you have, which commercial products use which stack and examples of hosting vendors using specific APIs.
Line 17: Line 17:
=== Also see ===
=== Also see ===
* [[Xen_Man_Pages|Man Pages (including pages for XL)]]
* [[Xen_Man_Pages|Man Pages (including pages for XL)]]
* [[Libxl_event_API_improvements|Libxl improvements (in Xen 4.2)]]
* Stefano's libxenlight [[http://vimeo.com/12307386 video]] and [[http://www.slideshare.net/xen_com_mgr/xen-summit-amd2010v3 slides]] at Xen Summit NA 2010.
* Stefano's libxenlight [[http://vimeo.com/12307386 video]] and [[http://www.slideshare.net/xen_com_mgr/xen-summit-amd2010v3 slides]] at Xen Summit NA 2010.


Line 28: Line 27:
[[XL|xl]] is a lightweight command line toolstack built using libxenlight. [[XL|xl]] is shipped along with Xen and is the default toolstack as of Xen Project 4.1.
[[XL|xl]] is a lightweight command line toolstack built using libxenlight. [[XL|xl]] is shipped along with Xen and is the default toolstack as of Xen Project 4.1.


[[XL|xl]] was designed to be backwards compatible with the '''xm''' CLI for xend.
[[XL|xl]] was designed to be backwards compatible with the '''xm''' CLI for xend. It provides a straightforward command line interface to Xen's facilities for guest creation and management.


'''Also see:'''
'''Also see:'''
Line 40: Line 39:
===XAPI / XE ===
===XAPI / XE ===


The Xen Project management API ([[XAPI|xapi]]) is the default toolstack for [http://www.xenserver.org/ XenServer]. It is also used in some installations of [[:Category:CloudStack|CloudStack]].
The Xen Project management API ([[XAPI|xapi]]) is the default toolstack for [http://www.xenserver.org/ XenServer] and [https://xcp-ng.org/ XCP-ng]. It is also used in some installations of [[:Category:CloudStack|CloudStack]].

It has Free Software licence. The now-abandoned [[:Category:XCP|XCP]] project was an attempt to provide a community-developed, Open Source style distribution of XAPI which would be available in distros.
It has Free Software licence. The now-abandoned [[:Category:XCP|XCP]] project was an attempt to provide a community-developed, Open Source style distribution of XAPI which would be available in distros.


Line 79: Line 77:
|-
|-
!CLI tool
!CLI tool
![[xl]]
![[XL]]
![[XCP Command Line Interface|xe]]
![[XCP Command Line Interface|xe]]
!virsh
!virsh
![[xm]]
![[XM]]
|}
|}


Line 88: Line 86:


''Note: xm has been removed in Xen 4.5.''
''Note: xm has been removed in Xen 4.5.''

==Toolstack Feature Comparison==

{|class="prettytable" style="text-align: left;" valign="top"
!style="width: 70%;"| '''Features'''
!style="width: 10%;"| '''xl'''
!style="width: 10%;"| '''xapi'''
!style="width: 10%;"| '''libvirt'''
|-
|Purpose-built for Xen
|{{Tick}}
|{{Tick}}
|{{NotDone}}
|-
|Basic VM Operations
|{{Tick}}
|{{Tick}}
|{{Tick}}
|-
|Managed Domains
|{{NotDone}}
|{{Tick}}
|{{Tick}}
|-
|Live Migration
|{{Tick}}
|{{Tick}}
|{{Tick}}
|-
|PCI Passthrough
|{{Tick}}
|{{Tick}}
|{{Tick}}
|-
|Host Pools
|{{NotDone}}
|{{Tick}}
|{{NotDone}}
|-
|Flexible, Advanced Storage Types
|{{NotDone}}
|{{Tick}}
|{{NotDone}}
|-
|Built-in advanced performance monitoring ([[XAPI_RRDs|RRDs]])
|{{NotDone}}
|{{Tick}}
|{{NotDone}}
|-
|Host Plugins ([[XAPI_Host_Plugins|XAPI]])
|{{NotDone}}
|{{Tick}}
|{{NotDone}}
|}


==Summary==
==Summary==

Latest revision as of 18:39, 5 November 2018

One really great feature of the Xen Project hypervisor is that there are several choices of toolstacks that can be used to manage it. Before the introduction of libxenlight, there was a complicated and inefficient toolstack situation. The issue was that xend, xapi, libvirt, etc. all needed to manage many common low-level operations, which led to code duplication, inefficiences, bugs, and wasted effort (e.g fixing the same bug in all of the toolstacks). Further, the default toolstack at the time (xend) was difficult to understand, modify, and extend.

ToolStacks.png

Each toolstack exposes an API, which will run different tools. The figure below gives a very brief overview over the choices you have, which commercial products use which stack and examples of hosting vendors using specific APIs.

Libxenlight (libxl)

Libxenlight is a small lower-level library, written in C. It is simple to understand; and easy to modify, and extend. Libxl is (or will be) shared by all Xen Project toolstacks. It was created to provide a simple and robust API for all the toolstacks to use (instead all of the toolstacks each implementing this common functionality). It was also created to be a common codebase to do Xen operations.

libxl Design Principles

  • Implement mechanisms, not policies
  • Stateless
  • Hide xenstore, libxenctrl, and libxenguest from higher levels
  • Be as simple as possible

Also see

Choice of Toolstacks

This section describes the various toolstacks (and the console that is used to run it).

Default / XL

xl is a lightweight command line toolstack built using libxenlight. xl is shipped along with Xen and is the default toolstack as of Xen Project 4.1.

xl was designed to be backwards compatible with the xm CLI for xend. It provides a straightforward command line interface to Xen's facilities for guest creation and management.

Also see:

XAPI / XE

The Xen Project management API (xapi) is the default toolstack for XenServer and XCP-ng. It is also used in some installations of CloudStack. It has Free Software licence. The now-abandoned XCP project was an attempt to provide a community-developed, Open Source style distribution of XAPI which would be available in distros.

libvirt / VIRSH

Libvirt is a virtualization API/toolkit used to manage various virtualization technologies. Originally designed to interface with xm, there is a libxenlight port of libvirt.

Also see:

Default / XEND (Deprecated in Xen 4.1; Removed in 4.5)

XEND is the previous toolstack and continues to be included as part of the Xen source releases. However as of Xen 4.1 XEND is now deprecated and will likely be removed in a future release. It is recommended that new deployments use one of the other toolstacks discussed above.

xl was designed to be command line compatible with the xm CLI to xend and this should provide the easiest upgrade path.

Also See

Command Line Interface (CLI) Tools

The table shows the command line tools to use with each of the toolstacks.

Toolstack xl XAPI libvirt xend
CLI tool XL xe virsh XM

Note: xl does not have a toolstack/cli split since the toolstack is the cli. Hence it appears under both headings.

Note: xm has been removed in Xen 4.5.

Summary

The power and flexibility of the management of Xen Project is an important feature. Users have a choice to use xl, XAPI, libvirt, or another toolstack to manage their Xen system(s).

  • xl is very lightweight and is a great choice for develpers or users who are most comfortable with Unix like CLI tools.
  • XAPI is a powerful toolstack that provides domain life-cycle management, pool-awareness (multiple Xen systems added to a central logical pool), and many other advanced features available with Xen Project software.
  • libvirt is a generalized virtualization layer for managing various virtualization technlogies with a common toolkit (or toolstack).
Retrieved from "https://wiki.xenproject.org/index.php?title=Choice_of_Toolstacks&oldid=19064"