[xen-tools] Re: Multiple role scripts ..

[C.J. Adams-Collier]

On 9/24/07, Steve Kemp <steve at steve.org.uk> wrote:
> On Sun Sep 23, 2007 at 20:57:48 -0700, C.J. Adams-Collier wrote:

>   Even a minimal os install would be 100Mb, or so.  I'd suggest
>  just adding a call to install with debootstrap.

I didn't mean a *working* OS.  I meant something that would allow
xen-create-image to complete its run with a $? == 0 status.  I bet we
can fit this in 10M.  But still, increasing the distribution by 10M is
not an optimal situation.

>   --install-method=debootstrap --install-source=http://us.debian...

I disagree.  In order to create a testable situation, we need a
control environment.

http://en.wikipedia.org/wiki/Scientific_control

debootstrap will potentially generate a different filesystem every
time it is run.  If we have a tarball that we populate, we can create
a controlled situation that we can test against.  Not to mention,
debootstrap creates *many* more files than are strictly necessary for
xen-create-image to successfully run.

it *is* important to have a test case for debootstrap as well, of
course.  I don't think we should use the live debian servers for this,
however.  In order to create a control, we should take a snapshot of
the mirror and strip it down to only those .deb files required for
debootstrap to complete successfully.  We should use this control
mirror as the argument to --install-source.  This is still not
strictly a control situation, however, since the version of
debootstrap on the builder's machine may vary.

> > We could then collect the contents of t/data/images/testhost using
> > File::Find and then compare the results with t/data/MANIFEST.
>
>   Agreed.
>
> Steve
> --

C.J.

-- 
moo.