Difference between revisions of "Xen Document Days/TODO"

From Xen
(Updated docs for transition to git: Move)
m (In progress (just need to double check whether finished))
Line 23: Line 23:
 
* {{Comment|[[User:Lars.kurth|Lars.kurth]] 08:02, 25 September 2012 (UTC):}} See [[XCP Overview]] & [[XCP Release Features]] - these need a little bit more work
 
* {{Comment|[[User:Lars.kurth|Lars.kurth]] 08:02, 25 September 2012 (UTC):}} See [[XCP Overview]] & [[XCP Release Features]] - these need a little bit more work
  
 +
==== Update docs for transition to git ====
 +
 +
We are planning to switch the primary Xen repositories to git at some point, a bunch of documentation will necessarily require updating.
 +
 +
* [[Submitting Xen Patches]]
 +
* [[Compiling Xen From Source]]
 +
* Presumably numerous other places...
 +
* {{Comment|[[User:Lars.kurth|Lars.kurth]] 13:46, 29 January 2013 (UTC):}} [[Submitting_Xen_Patches_with_Git]] has been created
 +
* {{Comment|[[User:Lars.kurth|Lars.kurth]] 13:46, 29 January 2013 (UTC):}} [[:Category:Developers]] links to both documents
 +
* Not sure this has been entirely completed. Probably needs to be linked better and made accessible
  
 
<hr>
 
<hr>
 +
 
=== Easy tasks for Beginners ===
 
=== Easy tasks for Beginners ===
 
You may weant to read [[Help:Contents|Wiki Help]] if you do not have an account.
 
You may weant to read [[Help:Contents|Wiki Help]] if you do not have an account.

Revision as of 13:46, 29 January 2013

Go back to Xen Document Days

Requested Documentation

Icon Info.png Feel free to comment on items using the following convention:
* {{Comment|~~~~:}} your comment

Feel free to add new workitems using the following convention:

==== Workitem ===
~~~~: work-item description


In progress (just need to double check whether finished)

A Xen Performance Tuning Guide

Better XCP Overview Documentation

Update docs for transition to git

We are planning to switch the primary Xen repositories to git at some point, a bunch of documentation will necessarily require updating.


Easy tasks for Beginners

You may weant to read Wiki Help if you do not have an account.

Migrate useful blog posts to wiki

Sift through blog.xen.org and copy useful posts to wiki. This will mainly be a reformatting exercise. Before you copy an article, perform a search on the wiki (headline or key word) to see whether the post exists already. If in doubt, ask on the IRC channel.

Fix articles that need attention

Review Categorization

Pages With Comments or Improvement Suggestions

Missing Pages

Pictogram voting comment 15px.png Lars.kurth 16:48, 28 January 2013 (UTC): There is something wrong with the language templates, essentially spamming the wanted pages. Do ignore these instructions until fixed.

  • Special:WantedPages - You can find missing pages by going to this link. There are several courses of actoin that can be taken:
    • The page is needed : Add {{TODO|With a comment}} to the top of the page
    • The page is not needed : Remove the reference to the page (follow the link in the bracket besides the page)
    • Note that the list of Wanted pages contains lots of needed translations and categories, which you can ignore
    • If in doubt, ask for help on the IRC channel

Xen : Open work items

Document release signing keys and fingerprints etc

We should publish the key ids and fingerprints somewhere.

UEFI Secure Boot

Write a document on how to sign the xen binary for UEFI Secure Boot. Potential reference here: Dealing With Secure Boot

Manpages for xe command

Write manpages for xe and it's 361 subcommands.

Xen PV Architecture Documentation

Something like a SDM for Xen PV "processors".

Add pages to Category:Paravirtualised Architecture

Describe the different ways, and necessary components, to create PVs using xl

Raised by mail by Matthias Blankenhaus (who is prepared to take the lead, but needs help): This document would describe the different ways, and necessary components that each way requires, to create PVs using xl. Right now there are at least the following cases:

  • loopbacked vhds
    • single partition format
    • disk format
  • qemu backed vhds
    • qcow / qcow2
  • LVS backed image

This is not a complete list. Also the mileage of each case differs depending on the kernel features enabled in dom0/domu and also depending on the Xen version. Furthermore, certain format require additional infrastructure like the tap device.

All in all, this a complex topic that needs clarification. Doing this based on the lowest common denominator, xl, would clarify many things. In addition, baseline performance data on all of the above would help a great deal. Matthias volunteered to run the majority of needed perf tests

A Xen Security Guide

The different options in Xen for Security, trade-offs, how to set them up, how to test Xen for security and how to optimize for different scenarios

  • Pictogram voting comment 15px.png Lars.kurth 09:48, 27 March 2012 (UTC): Category:Security contains some security related docs
  • Pictogram voting comment 15px.png Lars.kurth 11:01, 4 April 2012 (UTC): It would be good if we could document a) XSM, b) Introspection API, c) Xen and SELinux in Dom0, d) Memory Access API (introduced in 4.1)
  • User Docs that where migrating content would make sense and update such as (we can attach PDF's to the wiki now for starters, or we can use a conversion tool
  • Pictogram voting comment 15px.png Lars.kurth 15:59, 19 September 2012 (UTC): Some good articles came out of XenSummit NA (these can be built upon). Got funding to document XSM; contract in place, but contractor is currently ill.

Review and Update: xenpm usage recommendations

There is Xen power management and Xenpm command which may all be outdated. These should probably be reviewed and updated.

HOWTO : using xm trigger to poweroff or firing off NMIs

Howto on using xm trigger to poweroff or firing off NMIs.

HOWTO : How to Set Up Nested Virtualization

See this thread

HOWTO: Chain pypxeboot and pygrub

How to chain pypxeboot and pygrub

  • Pictogram voting comment 15px.png Lars.kurth 10:35, 27 March 2012 (UTC): Is pypxeboot popular at all?
  • Pictogram voting comment 15px.png Fheigl: I added that. It is somewhat common, OVM 2 and OVM 3 rely on it for PXE installs. I'm not sure if xenpvnetboot is the same, or works. The use case is "you want to use the same installation server for Xen VMs and phys. servers. You want to be able to reinstall them based on PXE reply.
  • Pictogram voting comment 15px.png Fheigl: There is documentation for pypxeboot, but there is no (afaik) documentation for how pygrub is used as a fallback loader. We wasted many days just to get some hack that can't even load a newer kernel. Which sucks, in the end you spend more time/money making PV PXE boot work than you save by using virtualized servers.
  • Pictogram voting comment 15px.png Fheigl: How could it be popular given the state of documentation. <= Key issue to the left of this sentence.
  • Pictogram voting comment 15px.png Lars.kurth 16:03, 19 September 2012 (UTC): wondering whether this video contains what is needed

XCP : Open work items

XCP Beginners Guide

Pictogram voting comment 15px.png Lars.kurth 15:32, 28 January 2013 (UTC): We are missing the equivalent of the Xen Beginners Guide for XCP.

Make titles of XCP and XAPI documentation consistent

Pictogram voting comment 15px.png Lars.kurth 13:09, 28 January 2013 (UTC): Often XCP related docs do not have XCP in the title, this makes it hard to find XCP related documents in titles. This is really hurting XCP users. Maybe this needs to be followed through in page categorisation also. Here is my proposal:

  • XCP related user documents should start with XCP:
  • Design documents - these are design documents should probably be labelled Component-Name:, e.g. XAPI:, etc.
  • Pictogram voting comment 15px.png Lars.kurth 16:36, 28 January 2013 (UTC): Would need to take the next item into account. In other words using XCP:..., XCP:XAPI:..., etc. would make more sense and would allow implementing namespaces later.

Also see:

Visually distinguish Xen, XCP and Community Documentation better

Pictogram voting comment 15px.png Lars.kurth 15:32, 28 January 2013 (UTC): Users are getting confused when looking at wiki pages. If there was a visual way to distinguish Xen, XCP and Other content better, this would help. We could use colors and skinning when it comes to various elements, as well as masocts/logos:

  • For example: Help:Contents has a different feel (and colour scheme)
  • This could be replicated in trail boxes and other elements
  • We can also use mascots (note we don't have an XCP mascot)

But first, I need to investigate what is possible.

Pictogram voting comment 15px.png Lars.kurth 16:14, 28 January 2013 (UTC): Looks as if the only way this can be done is via Custom Namespaces. The only way to do this properly is to

  • Have different namespaces for Xen, XCP, ... and Community stuff and keep all the common stuff in Xen
  • The name spaces could then be styled differently, for example the Help namespace includes the ns-12 style into the body attributes, whereas the Main (default) namespace uses the ns-14 style.
  • Custom namespaces can be created by changing the config and are linked to custom styles
  • The styles are then defined in MediaWiki:Common.css

Implications of using custom namespaces:

  • Search: Pages in a custom namespace do not show up in default search results. So if we had a custom XCP namespace, it would mean that search results for XCP would not show up. One would need to go to Advanced Search and select XCP
  • Rename: Renaming pages is possible and as straightforward as renaming pages
  • Xen Namespace: The Xen namespace exists already, this may need to be renamed
  • Categories and Namespaces: Categories cross namespaces. In other words, Category:XXX would go across all namespaces. As an example, see Category:Wiki_Management

Developer Docs

Docs that need attention or are missing

  • Make XAPI docs (built from source) available on xen.org
  • PVOPS portal on xen.org - Konrad volunteered
  • some more xenstore docs (i.e. recent python bindings that were sent to the -users list
  • Using libxenstat python bindings (imo they're broken)
  • More PV protocol docs (see recent patches to blkif.h for example)
  • Document xenstore paths used by guests and toolstack etc

Done Recently

Better Statements on Compatibility

There seems to be some confusion in the wider Linxu community about XL/XM compatibility. Maybe some specific questions in an FAQ/the release notes. Also migration compatibility comes up often. Any articles related to compatibility should be listed in Category:Compatibility, which I am willing to clean up.

  • Pictogram voting comment 15px.png Anthony 14:33, 26 November 2012 (UTC): I add a bunch of pages to the category, and add few link in the category to upgrade from xend to xl.
  • Pictogram voting comment 15px.png Anthony 17:19, 26 November 2012 (UTC): I also redirect XL in Xen 4.2 to XL as they had both the same content minus few things.
  • Pictogram voting comment 15px.png Lars.kurth 12:48, 22 January 2013 (UTC): Is this done?
  • Pictogram voting comment 15px.png Ijc 16:39, 25 January 2013 (UTC): I think we also need to cover compatibility confusion about 3.x vs 4.x.
  • Pictogram voting comment 15px.png Ijc 15:03, 28 January 2013 (UTC): I've added Xen Version Compatibility and a link from Xen FAW Compatibility. I think this is probably done for now?

Security related docs

George Dunlap: Revamped Driver_Domain and Securing_Xen

cpupools intro / howto

George Dunlap: See Cpupools_Howto

Clear up Xen TODO List

Document Policy on Maintenance Releases

Which releases are supported, for how long. Owners. As well as a mechanism for individuals (or vendors) to take ownership of older releases (as is the case for Xen 3.4).

Document {deb,rpm,tar}-pkg targets in kernel

Mainline_Linux_Kernel_Configs talks about the obsolete and Debian specific make-kpkg tool. Should reference the kernels own foo-pkg targets instead.

  • Pictogram voting comment 15px.png Ijc 12:12, 28 January 2013 (UTC): Done. Made a bunch of other cleanups too.