From Fedora Project Wiki
(moved back to FeaturePageIncomplete)
 
(3 intermediate revisions by 2 users not shown)
Line 50: Line 50:
== Dependencies ==
== Dependencies ==
Aside from the Xen ocaml bindings, these would be leaf packages.  
Aside from the Xen ocaml bindings, these would be leaf packages.  
None. <!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->


== Contingency Plan ==
== Contingency Plan ==
Line 67: Line 67:




[[Category:FeatureReadyForWrangler]]
[[Category:FeaturePageIncomplete]]
<!-- When your feature page is completed and ready for review -->
<!-- When your feature page is completed and ready for review -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Latest revision as of 20:56, 26 April 2012


XAPI

Summary

The Xen API toolstack

Owner

Current status

  • Targeted release: Fedora 17
  • Last updated: 2012-01-23
  • Percentage of completion: 40%

Detailed Description

XAPI is the Xen API toolstack that is used to interact with the Xen hypervisor for enterprise-grade, easily scalable virtualization

Benefit to Fedora

This project provides a number of benefits. First of all, it will provide Xen users with the option of using the same API and toolstack that XCP and XenServer provide. It will give early adopters the chance to try out new changes to the XenAPI before they get released in new XCP and XenServer versions. And because we will have ported all of our toolstack to build on Fedora, it’s now much, much easier to build our tools outside of an SDK VM.

Scope

This will involve rebuilding the xen packages to include the ocaml bindings. The balance of the work is largely packaging of a number of tools.

How To Test

  1. yum install xapi
  2. interact with the Xen API to control the hypervisor


Dependencies

Aside from the Xen ocaml bindings, these would be leaf packages.

Contingency Plan

We'd try and get into Fedora 18

Documentation

Upstream documentation is available at xen.org

Release Notes

The Xen API toolstack is now available for installation on Fedora for interaction with the Xen hypervisor.

Comments and Discussion