[Piuparts-devel] piatti xen setup

[Holger Levsen]

Hi,

On Tuesday 25 September 2007 06:56, Lucas Nussbaum wrote:
> Looking at this with a bigger scale: the usual process for finding and
> fixing QA bugs is:
> (1) run a test over a lot of packages, to get a list of packages that
> fail
> (2) analyze the results, and file bugs
> (3) find out what's wrong, and fix the bug
>
> Step (1) is the easy part. So I think that the most interesting parts
> are (2) and (3). That is, make it easy for every DD to run piuparts on
> his package. It would be nice, for example, if a DD could create a
> domU (or a vserver) without asking anyone, get root access inside the
> domU/vserver, test his package, and then kill the vserver/domU.

That's exactly what this plan is about :)

> Also, if it's possible to do this, you get (1) for free, since anyone
> could use his vserver/domU to run piuparts over the whole archive.

Exactly.

I choose xen for this, for some reasons:

1.) I know vservers and want to learn xen :) (and there is no similar tool 
like xen-shell for vservers)
2.) I want to use lvm snapshots with xen (this is also possible vservers) and 
there is a bugreport with patch (#421801) for piupars implementing this.
3.) a system with it's own kernel (xen) is a bit closer to a real system than 
one without (vserver), thus allowing to test more stuff

Any reasons to additionally have vservers available? If there are no 
compelling reasons I would stick with xen only, to have a simpler setup...


regards,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20070925/df24c7df/attachment-0001.pgp