On Sat, Jul 27, 2013 at 6:05 AM, Fabio Erculiani <[email protected]> wrote:
> Some time ago I was also thinking about writing a test framework for
> testing live images through kvm.
> Of course I didn't manage to find time to try to arrange something in
> the end, but the idea is still popping up in my mind every now and
> then.

Feel free to adapt:
https://github.com/rich0/rich0-gentoo-bootstrap

FYI - I plan to update it slightly today - I'm actually running 4
builds right now, eliminating some config-file cruft that is left over
from earlier failures, and adding a little more due to a new one.

More often than not I run into a little surprise every time I run it,
either due to regressions, or due to the stage3 being so old that half
the system needs to be updated.  Newer stage3s would certainly help.
So, if we add a QA step to stage3 publication we should try to keep up
the pace, otherwise we'll create just as many problems for new users
having to use old stage3s as we'll solve.

Those scripts could benefit from re-factoring (oh, and it wouldn't
hurt for me to credit Dowd and Associates again who created them).
Some thoughts:
1.  I added the plugin framework but never moved some of the default
packages into a plugin.  That would be an easy improvement to improve
utility.
2.  All of the EC2 logic itself could be moved into appropriate
functions, and then the script could be made configurable for EC2 vs
KVM vs whatever.   The bootstrap logic itself would work fine in an
architecture once /mnt/gentoo is setup.

I wouldn't necessarily mind volunteering to keep up with it, but if
I'm going to be running these weekly I'll probably ask for
reimbursement for EC2 expenses (I use spot instances so it isn't too
much, but all that CPU still adds up as well as storage costs while
I'm debugging things).  If we're willing to pay for the storage
(fairly nominal) I could also work on publishing a list of up-to-date
EC2 images (they're a byproduct of this stuff anyway so I just need to
publish them when they work).

Rich

Reply via email to