Differences between revisions 8 and 10 (spanning 2 versions)
Revision 8 as of 2007-11-26 18:21:47
Size: 6400
Comment: add links
Revision 10 as of 2009-03-16 03:29:39
Size: 6469
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from DebianEdu/CipUX/Feature/Deploy/Xen
Line 15: Line 16:
[[TableOfContents]] <<TableOfContents>>
Line 56: Line 57:
|| eisXen/eisfair beta5 || || || || || [http://www.eisxen.org (1)] ||first test with OptiPlex 745 failed. needed more test.||
||Xenoppix KNOPPIX5.1.1||3.0.4||2005-09-13|| || || [http://unit.aist.go.jp/itri/knoppix/xen/index-en.html (1)] || ||
||FAI|| || || || || [http://fai-cluster.de (1)] [http://www.informatik.uni-koeln.de/fai (2)] || ||
|| eisXen/eisfair beta5 || || || || || [[http://www.eisxen.org|(1)]] ||first test with OptiPlex 745 failed. needed more test.||
||Xenoppix KNOPPIX5.1.1||3.0.4||2005-09-13|| || || [[http://unit.aist.go.jp/itri/knoppix/xen/index-en.html|(1)]] || ||
||FAI|| || || || || [[http://fai-cluster.de|(1)]] [[http://www.informatik.uni-koeln.de/fai|(2)]] || ||
Line 151: Line 152:
[[PageList(regex:(CipUX/Feature/Deploy/Xen/[^/]*$))]] <<PageList(regex:(CipUX/Feature/Deploy/Xen/[^/]*$))>>
Line 155: Line 156:
[[PageList(regex:(?:(?!Deploy/).......|^.{0,7})Xen)]] <<PageList(regex:(?:(?!Deploy/).......|^.{0,7})Xen)>>

Status of the infrastructure project:




?RobertGlowienka, ?GerhardPrade




















The Idea of the Deploy/Xen concept is to deply various systems over Xen.


Specification are things we want to have.

Admin GUI

  • Client OS can be choosen for each client
  • Client OS can be choosen per room


  • Deploys Xen to Clients
  • Deploys Xen Images to Clients


  • Boots Xen
  • Xen boots User OS

How it should works

  • Boot first Linux with Xen-Support
  • Inside Xen-Subdomain started Windows
    • Support of remote deploy different OS
      • Linux
      • Win98
      • WinXP Prof
      • Vista ?
  • Restore over LVM-Snapshot

Overview over small Debian based Xen Distros as Dom0



Proj start

aprox contrib.




Debian Bootstrap Etch

seems to be working, but with problems

eisXen/eisfair beta5


first test with ?OptiPlex 745 failed. needed more test.

Xenoppix KNOPPIX5.1.1





(1) (2)


Milestone 1

To be sure that the desired OS works smooth and reliable inside Xen, we have to test with a proof of concept that it does. This proof of concept should be preserved in a small step through guide. No CipuX is needed at this point.

To archive this we:

  • (1) set up a client with Debian: etch or sid and the actual Xen package as dom0 without LVM (2) install a guest OS, domU inside a plain HD image not LVM at moment. (3) install some heavy software inside this OS (4) Performance Test: make simple performance test (4.1) write protocol about RAM consumption (5) User Test: if possible make a user test: ask a user to work for a short time with this system (6) Uptime Test: let this system be up for some days. (7) Finish the step by step guide (8) Then (this is very important) one or two other people should rebuild such client to see if this works with different client hardware but the same Debian versions and packages.

Guide: http://wiki.debian.org/DebianEdu/CipUX/Feature/Deploy/Xen/ServerGuide

Milestone 2

After we are sure that every OS we want works inside Xen, we know the version of Xen we have to take and the server requirement. Then the next step is to clone this image after joining a domain. The goal is to find a method as a proof of concept for cloning a Xen image without the need of rejoining the domain.

For Linux we make sure:

  • That we can reach the file server: NFS, Samba server.

For Win we make the following (with writing a protocol to be verified by others):

  • we join a PDC domain with image A
    • with SAMBA server (with and without Active Directory support)
  • we make sure that we can access the shares
  • we make sure that we can log in
  • we shut down the Xen instance and clone the image, now we have A and B.
  • we prepare a second client.
  • we start image A on the first client and image B on the second
  • we try to login as different and as the same user and make a protocol of the results.
  • If this didn't succeed, we have to find a way.

Milestone 3

We should make a discussion about the results of proof of concept 1 and 2 and choose the following:

  • Guest OS Linux
  • Guest OS Win
  • Version of Xen
  • Xen Linux Distribution of the Client
  • Deploy mechanism: Deploy Distribution: example FAI, ...
  • Framework of configuration: what value has to be configured and how.
  • RPC commands needed
  • Things and mechanism, we would like to remote control on the client OS.

Milestone 4



Milestone 1



Assigned to












Milestone 2

Other Debian Wiki Xen resources