Status of the infrastructure project:

Name:

cipux-deploy-xen

Concept:

?RobertGlowienka, ?GerhardPrade

Participants:

ChristianKuelker

Programmers:

-

Status:

planning

Start:

2007-09-01

End:

-

Planned-release:

3.4.6

Alpha-release:

-

Beta-release:

-

Stable-release:

-

?TableOfContents

CipUX-Deploy-Xen

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

Specification

Specification are things we want to have.

Admin GUI

Server

Client

How it should works

Overview over small Debian based Xen Distros as Dom0

Distribution

Vers.

Proj start

aprox contrib.

stable?

URL

Comments

Debian Bootstrap Etch

seems to be working, but with problems

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)]

ToDo

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:

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:

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

Milestone 3

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

Milestone 4

Implementation

ToDo

Milestone 1

point

Remark

Assigned to

done

(1)

?RobertGlowienka

(2)

(3)

(4)

(4.1)

(5)

(6)

(7)

(8)

Milestone 2