nyuuzyou/wikis huggingface dataset:
Archived/Ubuntu XAPI Toolstack Improvements Spec

=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
Category:XAPI Developers
Category:Ubuntu
Category:Archived
Category:Development Process
Archived/Wiki Community/Migration Instructions from Old to New Xen Wiki

This document shows instructions on how to migrate Wiki pages from the old Xen Wiki to the new Xen Wiki.
= Basic Workflow =
The following steps describe the basic flow of 
* Pick a page that you want to migrate from this spreadsheet. Note that filters may have been set on the sheet: you may need to modify these to find the docs you want to migrate. Also note that anyone with the link to the spreadsheet can edit if, if they are logged into Google Docs. Be careful with the sheet.
* Find page source at Old Raw Pages and copy the content into the page
* Create a new page: make sure you use exactly the same name as the old page, otherwise links to the page will break. Note that it is OK to replace _ with a blank character in names as Mediawiki interprets thejm in the same way.
* Copy content from old-wiki-converted by finding the right text file and copying the content into the page you just created.
* Add page categories at the bottom of the page: columns D-H of this spreadsheet contains hints on what categories have been suggested. The following table contains descriptions of the categories. 
* Preview and Save: preview the page and check for issues. See Common Migration Issues and What to do when there are issues
* Mark the page as migrated by adding Yes to column B (Migrated) of this spreadsheet
== Renaming Pages ==
It is OK to rename new wiki pages to make the Wiki more usable. If you do, make sure that you create the page with the original name. After the page has been created and saved, rename it. That way a redirect is created and links to pages with the old page name will not be broken.
= If there are Issues =
If you find issues with a page do one of the following:
* Fix the page
* Mark the page with one of the following templates at the top of the page
:{{Needs_Formatting|Whatever needs done}} 
:{{Needs_Additions|Whatever needs to be added}}
More information on markers can be found at Managing Pages via Templates.
= Common Migration Issues =
== Mangled Characters ==
Something like â€œblock tapâ€ should really read "block tap".
== Indentation ==
Indentation in conjunction with * <pre>...</pre> are frequently wrong. In most cases
:::<pre>...</pre>
::::<pre>...</pre>
Or a similar code will do the trick and created an indented format block.
== Missing Images ==
Images are not copied. They need to be saved and then added to MediaWiki.
== Missing Attachments ==
Other attachments are not copied. They need to be saved and then added to MediaWiki. But note that some types of attachments such as executables that could be added to the old wiki, cannot be added to MediaWiki.
Category:Community
Category:Archived
Archived/XCI Project

__NOTOC__
== Project Status ==
This project is in incubation and has recently not had much traction. Thus we decided to archive the project.
== Xen Client Initiative Project ==
The purpose of the Xen Client Initiative (XCI) is to align currently disparate activities within the Xen.org community for a Xen client hypervisor: agreeing on architecture, co-ordinating development, and accelerating the availability of a Xen hypervisor client. The ultimate goal of the project is to define a standard framework for supporting service domain virtual appliances on client devices. This would encompass packaging, installation and configuration of service domains (likely building on the concepts in DMTF OVF), but also define APIs for enabling a service domain to control and inspect/modify VMs under its control, and to interpose itself in their IO paths. 
The XCI Project has four working groups looking at different aspects of the overall project (each working group has its own page in the Wiki):
* Hypervisor Core
* VM Services
* Domain 0
* Hypervisor Services Framework
All questions about the XCI project should be directed to community.manager@xen.org.
Category:XCI
Category:Project
Category:Archived
Archived/XCP 1.6 test instructions

= What needs to be tested =
XCP 1.6 has a number of new features, as well as better integration with the latest version of Citrix's XenCenter. Please download the ISO and try it out. Here are some things we would like people to test:
== Storage XenMotion ==
Storage XenMotion (or SXM for short) provides a way to move a VM's disks between SRs, while the VM is running. You can do things like move a VM's disks from local storage to shared storage while the VM is running, move a VM between different hosts with no shared storage at all (from local storage on one host to local storage on the other host), or even migrate a VM between pools. To read more about how SXM works, see Storage XenMotion. The online help for SXM is available by running 'xe help vm-migrate' and 'xe help vdi-pool-migrate' in dom0.
== XenCenter integration ==
XenCenter integration with XCP has been improved. You can test this by downloading XenCenter from the Citrix XenServer downloads page.
== Windows PV drivers ==
Try installing a Windows VM, installing the PV drivers on it, and then performing lifecycle operations such as suspend/resume and migrate. Storage XenMotion will also work with Windows VMs.
== Upgrading from XCP 1.1 and XCP 1.5 Beta ==
We expect this to work, but the XenCenter rolling pool upgrade feature is currently untested with XCP.
UPDATE: There was an issue with upgrading from previous versions of XCP to the first beta release of XCP 1.6. This issue has been resolved in the latest beta release (see )
Upgrading from XCP 1.1 directly to XCP 1.6: This works, but you need to add the keys PLATFORM_VERSION=1.1.0 and PLATFORM_NAME=XCP to your /etc/xensource-inventory file before attempting the upgrade.
== Integrations with cloud orchestration stacks and other projects ==
We expect these to work, but we have not tested all 3rd party XCP integrations. Also some documentation related to integrations may need to be updated
* Apache CloudStack
* OpenNebula
* OpenStack
* Other
= Getting the beta =
XCP 1.6 Beta can be downloaded from the XCP Downloads page. You can burn the ISO to a CD and install it on physical hardware, or you can test it out as a virtual machine, either on a hypervisor like VirtualBox, or on XCP 1.6 itself. If you install XCP in a VM, you will only be able to start PV guests, since nested HVM doesn't work yet.
= Reporting Bugs and Issues =
* Report any bugs / missing functionality / unexpected results to the xen-api mailing list.
* Please put [XCP-1.6-BETA] in the subject line.
* Make sure to follow the guidelines on Reporting Bugs against Xen.
Thanks for testing XCP!
Category:Users
Category:Developers
Category:XCP
Category:Test Day
Category:Archived
Archived/XCP Roadmap

= XCP Release Timeline =
For previous releases see: XCP_Release_History
Here is a rough guide to future releases.
== XCP 1.5 ==
Status: Permanent Beta 
Last updated: 14th February 2012 
Next status update due: Unknown
XCP 1.5 is version-compatible with XenServer 6.0. It's the first XCP release to be based on Xen 4.1. We have some internal work to do both on our build system and xapi before we can release XCP 1.5, but after we complete this work it will be much easier for us to release stable versions of XCP along with XenServer stable releases. This means that after these changes, there won't be any more long delays between XCP stable releases and XenServer releases.
Features that will likely make it into XCP 1.5:
* Xen hypervisor 4.1
* vSwitch is the default networking stack
* Ubuntu guest support
* Debian Squeeze guest support (32b/64bit)
* Updated RHEL 6.0 support
* Experimental SLES 10 SP4 support
* Experimental Solaris guest support
* Active-Passive NIC Bonding Support for vSwitch
* Rolling Pool Upgrade improvements
== XCP 1.6 ==
=== Current status ===
* Status: Beta 2 released 
* Last updated: 8 Oct 2012 
* Next status update due: End of October 
Current known issues with Beta 2:
# Boot from CD splash screen shows "Citrix XenServer" (minor, in progress)
# Rolling pool upgrade from 1.5 doesn't allow VM migration from 1.5 host to 1.6 host (blocker, in progress)
# Performance issue with XenCenter connected (blocker, code complete)
=== Timeline for release ===
* Beta 1: 1 Oct 
* Beta 2: 8 Oct (fixed upgrade functionality) 
* Test day: 9 Oct 
* Beta 3: TBA
* Final release: 24 Oct TBA
See this e-mail thread for more info on the beta 3 and final release date.
=== Feature summary ===
XCP 1.6 is version-compatible with XenServer 6.1
Features include:
* Storage XenMotion (cross pool live migration and live VDI migration)
* Enhanced guest support: Ubuntu 12.04, CentOS/REL 6.2, Windows 8
* Updates: Xen 4.1.2, 2.6.32.43, CentOS 5.7
* Open vSwitch 1.4.2
* LACP bonding
* Performance and scalability improvements
** Ability to pin Dom0 vCPU
** Up to 4 VM starts can now be concurrent
* IPv6 support (experimental)
== XCP 2.0 ==
Status: Planning/Design 
Last updated: 2nd August 2012 
Next status update due: End of September
Features likely to be included:
* Xen 4.2, Linux 3.x, CentOS 6.x
* First steps towards Dom0 disaggregation
= Possible features for future XCP releases =
==== Cloud ====
* Cross-pool VM.migrate / VM.copy coming in 1.6
* IPV6 support coming in 1.6
* "Shard" the pool metadata db
* ceph and libvirt: see the Ceph and libvirt technology preview
==== Appliances ====
* v4v for non-IP inter-domain comms
* Detect pending updates for appliances
==== Performance and Scalability ====
* Expose NUMA topology via XenAPI
* Stubdoms for intensive ops (eg VM export)
* XCP storage driver domains
==== Robustness ====
* Enable Xen Security Modules
* Pvgrub (or pygrub in helper domain)
Category:XCP
Category:Archived
Archived/XCP Wishlist

__NOTOC__
== Wishlist ==
The following items are features or work items to be implemented in future XCP releases
== Architectural Improvements ==
* Spring 2011 plan: XCP Platform Evolution Plan
== Other Wishlist Items ==
Description
Handling guest tools in appliances
An API for disk deltas
XCP Installer upgrades the distribution
OCFS 2 SM backend
Guest RPC mechanism
Convenient HTTP GET URL for consoles
Extend ocamldebug to support multiple threads
XenDbg - Xen Debugger support
Xen/XCP kernel/userland packages for Debian Ubuntu RHEL
Move HTTP server into a separate process
Pool master in a VM
Improve SR-IOV support
Automated pool configuration
Better error handling
Better parameterization of xapi
Extra external authentication plugins
Pool split
Better iSCSI multipathing
pxe boot xcp using a stateless ramdisk root
Expose new xen features
Database rollback
Procedure to remove database fields
Domain management daemon
Upgrade pool hosts in any order
Helper VMs
GlusterFS SR backend
Category:Archived
Category:XAPI Devel
Archived/XDDS/May2021

== When and Where ? ==
=== Virtual, May 25-28 ===
XDDS 2021 was virtual, hosted on BigBlueButton
== Session Notes and related pages ==
== Topics to Discuss, Code, Work on, ... at the Hackathon ==
=== Instructions ===
=== Topics ===
Please add topics you want to discuss in this section as described above
Category:Project
Category:Community
Category:Events
Archived/Xapi Project Roadmap

This roadmap is a list of high-level releases related to the Xapi Project. Xapi development itself will follow a two-week sprint cycle, inside of a quarterly "train" cycle (trains are like sprints-of-sprints). Each sprint may accomplish individual bug fixes and new features, while with each train we will attempt to introduce larger, more meaningful sets of features.
At the end of every sprint, we'll bump the micro version number of the xen-api source repo, and will update the changelog with bug fixes and new features. Every quarter, at the end of each train, we'll bump the minor version to indicate the large new feature sets which should by then be stable. Sprints and trains themselves will be named for the calendar week on which they finish; sprints will begin on a Wednesday and end on a Tuesday.
We will populate this roadmap with information on upcoming sprint finish dates, and upcoming train finish dates, with a short explanation of the things we wish to accomplish in each.
Milestone 	Date 	Notes/comments
XCP toolstack in Ubuntu Precise	2012.04.12	Ubuntu Precise released this day with xcp-xapi-1.3.2
XCP 1.6 	2012.11.26	Xen Cloud Platform ISO stable release (parallels XenServer 6.1)
XCP toolstack in Debian Wheezy 	2013.05.04	Debian Wheezy released this day with xcp-xapi-1.3.2
Xapi Project Sprint wk26 	2013.06.25	xenopsd-on-libxl, xcp-rrdd improvements, xenostats improvements, xapi-in-CentOS work
XenServer 6.2/XCP ISO release 	2013.06.26	Next release of XenServer (this supercedes XCP ISO)
Xapi Project Sprint wk28 	2013.07.09	Bug fixes, XAC, xapi+centos packaging, vGPU, networking improvements
Xapi Project Sprint wk30 	2013.07.23	Bug fixes, XAC, build system improvements, xapi disagregatoin
Xapi Project Sprint wk32 	2013.08.06	Bug fixes, XAC, build system improvements, xapi disagregatoin
Train 13T40 	2013.10.01	"Fusion" (Ceph storage, upstream qemu), CentOS RPM packaging
Category:Archived
Category:XAPI Devel
Category:XAPI Sprints
Archived/XenTest/KeyToColumns

__NOTOC__
= Key =
; Test : the test case to be run.
 NB: a single test case can have many tests, e.g., as in LTP.
; Description : what part of Xen is being tested
; Upstream : URL or other locator for the test source code
; Parameters : how the test should be run
; Criteria : how to determine if the test passed or failed
; Votes : how many people agree that this test (in some form) should be used
; Variables : when running the test, items to vary to improve the quality of the testing.
 NB: when the term 'domU' is used as a variable, it means the 'domain of all possible domU's' -- paravirtual, fully virtual, different OSs, and combinations of them, too, and not just a single domU.
; Status : can be either proposed, implying the test is under consideration by the community for inclusion as part of a 'standard' suite, or accepted should the community agree to include the test, or to be written if the test doesn't even exist but would be a good idea, if accepted
; Results : pointers to any current results for the test
= Links =
* XenTest
* XenTest/FunctionalTests
* XenTest/RegressionTests
* XenTest/PerformanceTests
* XenTest/StressTests
Category:Developers
Category:Xen
Category:Development Process
Category:Archived
Archived/XenTest/PerformanceTests

__NOTOC__
= Performance Test Matrix =
Test 	Description 	Upstream 	Parameters 	Criteria 	Variables 	Votes	Status
Apache Benchmark (ab) 	tests Apache server behavior 	 	use native, dom0, domUs as servers, use dom0 to test domU as server, test http and https	dom0 < native + 10%, domU < native + 20%	PCPUs, VCPUs, driver domains, scheduler 	1 	proposed
Bonnie++ 1.0.3 	 	 	 	dom0 < native + 10%, domU < native + 20%	PCPUs, VCPUs, driver domains, scheduler 	3 	proposed
dbench/tbench 	 	 	 	dom0 < native + 10%, domU < native + 20%	dom0, domU, PCPUs, VCPUs, RAM, driver domains 	1 	proposed
Domain Migration 	how long does it take to migrate from/to localhost? a remote host on a quiet network? 	 	 	down time < 1 second 	domUs, PCPUs, VCPUs, RAM, scheduler 	1 	to be written
hdparm 	simple disk I/O performance 	 	hdparm -tT /dev/root 	dom0 < native + 10%, domU < native + 20%	driver domains 	1 	proposed
IOZone3 191 	 	 	 	dom0 < native + 10%, domU < native + 20%	PCPUs, VCPUs, driver domains, scheduler 	2 	proposed
Linux Kernel Compile (2.6.16 source)	Compile the Linux kernel; provides broad brush pass/fail on whether Linux is behaving 	 	default config file 	dom0 < native + 10%, domU < native + 20%	dom0, domU, distro, backing store, PCPUs, VCPUs, driver domains	4 	proposed
LMbench 3.0-a5 	 	 	 	dom0 < native + 10%, domU < native + 20%	PCPUs, VCPUs, driver domains, scheduler 	2 	proposed
netperf 	network performance 	 	 	dom0 < native + 10%, domU < native + 20%	dom0, domU, PCPUs, VCPUs, RAM, driver domains 	2 	proposed
spew 	simple disk I/O performance 	 	spew --raw -d -i 6 -v -b 256k 1g /tmp/$$.bigfile >/tmp/$$ 2>&1 	dom0 < native + 10%, domU < native + 20%	driver domains 	2 	proposed
sysbench 0.4.7 	modular, cross-platform and multi-threaded benchmark tool for evaluating OS parameters that are important for a system running a database under intensive load	http://sysbench.sourceforge.net/	 	dom0 < native + 10%, domU < native + 20%	PCPUs, VCPUs, RAM, scheduler 	2 	proposed
UnixBench 4.1.0 	 	 	 	dom0 < native + 10%, domU < native + 20%	PCPUs, VCPUs, RAM, scheduler 	3 	proposed
wget 	simple network performance 	 	wget -o /tmp/$$ -O /dev/null http://somewhere/linux-2.6.16.tar.bz2 	dom0 < native + 10%, domU < native + 20%	driver domains 	1 	proposed
= Links =
* XenTest/KeyToColumns
* XenTest
* XenTest/FunctionalTests
* XenTest/RegressionTests
* XenTest/StressTests
Category:Developers
Category:Xen
Category:Development Process
Category:Archived
Archived/XenTest/RegressionTests

__NOTOC__
= Regression Test Matrix =
NOTE: all tests should be run on both paravirtual and fully virtual guest domains.
Test 	Description 	Upstream 	Parameters 	Criteria 	Variables 	Votes	Status
SPECweb99 	NB: it is not clear we can actually use this test. Publishing results is restricted; hence, we may only be able to compare results and discuss the difference. Not having source available freely is also restrictive.	http://www.spec.org	 	results within +/- 5% of previous release 	use agreed upon values 	2 	proposed
Xen Functional Tests 	see XenTest/FunctionalTests 	n/a 	use agreed upon values 	all results are the same or better than the previous release	use agreed upon values 	1 	proposed
Xen Performance Tests	see XenTest/PerformanceTests 	n/a 	use agreed upon values 	all results within +/- 5% of previous release 	use agreed upon values 	1 	proposed
Xen Stress Tests 	see XenTest/StressTests 	n/a 	use agreed upon values 	all results within +/- 5% of previous release 	use agreed upon values 	1 	proposed
xm create VTI 	xm sporadically reports it cannot allocate memory for a VTI 	bugzilla 736 	create VTI domain, after it is up, destroy it. redo this for several times	command always works 	use 2G memory for VTI domain	2 	to be written (?)
= Links =
* XenTest/KeyToColumns
* XenTest
* XenTest/FunctionalTests
* XenTest/PerformanceTests
* XenTest/StressTests
Category:Developers
Category:Xen
Category:Development Process
Category:Archived
Archived/XenTest/StressTests

__NOTOC__
= Stress Test Matrix =
Test 	Description 	Upstream 	Parameters 	Criteria 	Variables 	List Votes	Status
crashme 2.4 	test the robustness of an operating environment using a technique of "Random Input" response analysis 	http://people.delphiforums.com/gjc/crashme.html	crashme +2000 666 100 01:00:00 2 	at no time does a domain crash 	dom0, domU, RAM, PCPUs, VCPUs, file system 	2 	proposed
Large Memory A 	can Xen handle massive amounts of RAM? 	 	largest amount of RAM possible, as many guests as possibe 	agreed upon mininum values that must work 	dom0, domU, RAM, PCPUs, VCPUs, file system 	1 	to be written
Large Memory B 	can Xen handle massive amounts of RAM? 	 	largest amount of RAM possible, one guest that consumes everything	agreed upon mininum values that must work 	dom0, domU, RAM, PCPUs, VCPUs, file system 	1 	to be written
NFS 	NFS stress tests 	 	 	agreed upon mininum values that must work 	dom0, domU, RAM, PCPUs, VCPUs, file system, driver domains	1 	to be written (?)
OpenSolaris domU	run PV and HVM OpenSolaris guests 	 	use agreed upon disk image 	OpenSoloaris boots, one can log in, and run simple commands	PCPUs, VCPUs, RAM 	1 	proposed
Plan 9 domU 	run PV and HVM Plan 9 guests 	 	use agreed upon disk image 	Plan 9 boots, one can log in, and run simple commands 	PCPUs, VCPUs, RAM 	1 	proposed
SPECcpu2000 	NB: it is not clear we can actually use this test. Publishing results is restricted; hence, we may only be able to compare results and discuss the difference. Not having source available freely is also restrictive.	http://www.spec.org 	 	results within +/- 5% of previous release 	use agreed upon values 	1 	proposed
SPECjbb 	NB: it is not clear we can actually use this test. Publishing results is restricted; hence, we may only be able to compare results and discuss the difference. Not having source available freely is also restrictive.	http://www.spec.org 	 	results within +/- 5% of previous release 	use agreed upon values 	2 	proposed
ttcp 1.12 	times the transmission and reception of data between two systems using the UDP or TCP protocols 	http://linux.maruhn.com/sec/ttcp.html 	 	at no time does a domain crash 	dom0, domU, RAM, PCPUs, VCPUs, file system 	2 	proposed
= Links =
* XenTest/KeyToColumns
* XenTest
* XenTest/FunctionalTests
* XenTest/RegressionTests
* XenTest/PerformanceTests
Category:Developers
Category:Xen
Category:Development Process
Category:Archived
Archived/Xen Development Projects

__TOC__
This page lists various Xen related development projects that can be picked up by anyone! If you're interesting in hacking Xen this is the place to start! Ready for the challenge?
To work on a project:
* Find a project that looks interesting (or a bug if you want to start with something simple)
* Send an email to xen-devel mailinglist and let us know you started working on a specific project.
* Post your ideas, questions, RFCs to xen-devel sooner than later so you can get comments and feedback.
* Send patches to xen-devel early for review so you can get feedback and be sure you're going into correct direction.
* Your work should be based on xen-unstable development tree, if it's Xen and/or tools related. After your patch has been merged to xen-unstable it can be backported to stable branches (Xen 4.2, Xen 4.1, etc).
* Your kernel related patches should be based on upstream kernel.org Linux git tree (latest version).
xen-devel mailinglist subscription and archives: http://lists.xensource.com/mailman/listinfo/xen-devel
Before to submit patches, please look at Submitting Xen Patches wiki page.
If you have new ideas, suggestions or development plans let us know and we'll update this list!
== List of projects ==
=== Domain support ===
=== Hypervisor ===
=== Userspace Tools ===
=== Mirage and XAPI projects ===
There are separate wiki pages about XCP and XAPI related projects. Make sure you check these out aswell!
* XAPI developer guide: XAPI Developer Guide
== Quick links to changelogs of the various Xen related repositories/trees ==
Please see XenRepositories wiki page!
Category:Archived
Category:Xen
Category:Xen 4.4
Category:PVOPS
Category:Developers
Category:Index
Category:Project
Category:Transient