1 |
Currently Catalyst2 supports most of the functionality that you require. |
2 |
Catalyst is *NOT* designed to run from our livecd at the moment because |
3 |
it needs a few things the livecd structure doesnt support at the moment. |
4 |
First it would require the seed stage + snapshot to be on the tree or be |
5 |
downloaded via the network. Since the downloaded seed/snapshot is in |
6 |
the order of 200Mb this would require about 200Mb of ram just to hold |
7 |
those files since the cdrom is read-only. These files cant go into the |
8 |
chroot dir on the harddrive as catalyst makes great effort to make sure |
9 |
these directories are clean before it runs. |
10 |
Also we dont plan on adding partitioning support/filesystem creation |
11 |
support to catalyst anytime soon. We dont want to overwrite anyones |
12 |
filesystems and with this tool the chances are just to large at the |
13 |
moment to do the wrong thing. |
14 |
|
15 |
But you should be able to do this with catalyst 2. |
16 |
|
17 |
create a new stage4 tarball. This tarball will contain the kernel(s) |
18 |
initrds and any other system files. the fsscript part of the |
19 |
stage4 spec will allow a scripted post install script that will |
20 |
allow automation of steps normally performed during an install. |
21 |
There is also an overlay option that will allow additional |
22 |
directories and files to be copied into the chroot before it is |
23 |
tarred up. |
24 |
|
25 |
The install process would be as you already have in place. |
26 |
A script that you create and place on your livecd. |
27 |
|
28 |
It will create the partitions and filesystems, get the stage4 |
29 |
tarball from somewhere on the network via ftp/wget/scp and untar it |
30 |
into your newly created filesystems. modify the fstab to match your |
31 |
disk layout. rerun your bootloader software to laydown a mbr and |
32 |
then reboot. |
33 |
|
34 |
I hope this helps, |
35 |
Eric |
36 |
|
37 |
On 22:58 Sun 15 May , Toon Verstraelen wrote: |
38 |
> Hi, |
39 |
> |
40 |
> I've been playing with catalyst for the last few days and it was great |
41 |
> fun. I've created a livecd that partitions and formats /dev/hda of a |
42 |
> cluster node automatically and then downloads a complete image from the |
43 |
> file server and untars it. grub is also automatically installed. The |
44 |
> image was a created in a chrooted environment on the server following |
45 |
> the installation handbook. |
46 |
> |
47 |
> Is it a good idea to create a sort of stage4 spec for catalyst that does |
48 |
> the installation of the node image (in the chrooted environment on the |
49 |
> server) automatically? Although this would be a complicated spec, in my |
50 |
> case the benefit would be huge for creating production quality node |
51 |
> images. I'm interested in doing a bit of catalyst-development to achieve |
52 |
> this, but how do I get started? |
53 |
> |
54 |
> Other benefits of such a stage4 spec could be: |
55 |
> * unattended install of a gentoo system from a livecd |
56 |
> * it could be used by an installer tool that interrogates the user |
57 |
> about all possible installation options, then creates the |
58 |
> corresponding stage4 spec and runs catalyst to do the job. |
59 |
> * A wide set of predefined configurations on the livecd so that |
60 |
> absolute noobs could install a gentoo in different flavors. |
61 |
> * Instead of creating a complicated howto about setting up a |
62 |
> ...-server, one could just publish the stage4 spec with post |
63 |
> installation scripts and/or configuration files. |
64 |
> The reader of the howto can get started much easier and by changing |
65 |
> the spec he can customize the installation of such a specialized |
66 |
> server to his own needs. |
67 |
> |
68 |
> Any comments are welcome. I just collected a few thoughts here. |
69 |
> |
70 |
> greetings, |
71 |
> |
72 |
> Toon |
73 |
> -- |
74 |
> gentoo-catalyst@g.o mailing list |
75 |
> |
76 |
> |