Archived/Ubuntu XAPI Toolstack Improvements Spec: Difference between revisions
Lars.kurth (talk | contribs) |
Lars.kurth (talk | contribs) No edit summary |
||
(2 intermediate revisions by the same user not shown) | |||
Line 44: | Line 44: | ||
TBD |
TBD |
||
[[Category:Developers]] |
[[Category:XAPI Developers]] |
||
⚫ | |||
[[Category:Ubuntu]] |
[[Category:Ubuntu]] |
||
⚫ | |||
[[Category:Development Process]] |
[[Category:Development Process]] |
Latest revision as of 13:20, 5 August 2019
Summary
The XAPI Toolstack is an open source, server and cloud virtualization platform which provides a rich management API on top of the Xen hypervisor. The purpose of this blueprint is to discuss improvements to the Ubuntu XAPI Toolstack that we wish to make during the Q-series development cycle. We would also like to discuss ideas for improving the interaction between the XAPI Toolstack and other Cloud and Server managment interfaces, such as OpenStack, CloudStack, and Juju.
Rationale
Now that the XAPI Toolstack is part of Ubuntu, we need to ensure that we continue to improve the feature set and quality of our software in Ubuntu. This blueprint comprises of three main objectives:
- Updating the Debian/Ubuntu packages to the same version of software that will be released in XCP 1.6/XenServer 6.1.
- Determining how to incorporate the architectural changes we're making in XCP into the XAPI Toolstack Ubuntu packages (see dom0 disagregation).
- Doing integration work with other projects, such as Juju, Puppet and Ceph.
User stories
We'll flesh out these user stories as we get a better idea of what improvement projects we'd like to work on during the Q-series development cycle.
- (Story about using Juju with XAPI Toolstack)
- (Story about creating driver domains, say for using ZFS, with the XAPI Toolstack)
- (Story about developing OpenStack on Ubuntu, Xen, and the XAPI Toolstack)
- (Story about provisioning Ubuntu/XAPI Toolstack servers with Puppet)
Assumptions
None at the moment.
Design
Please see the Project Kronos Spec from the Precise UDS for a design discussion.
Implementation
To be decided once we finalise the user stories.
Test/Demo Plan
To be decided once we finalise the implementation.
Unresolved issues
BoF agenda and discussion
Release Note
TBD