1 |
> For those interested, a new snapshot of the GSDS is available. Testing |
2 |
> and comments are still highly desirable. I know the docs are woefully |
3 |
> incomplete, but if there's any python folks that could sift through |
4 |
> the code, that would be extremely helpful. Also, comments regarding |
5 |
> design would be great. |
6 |
|
7 |
let me ask you a question - i went through a documentation of GSDS in |
8 |
order to find an answer but haven't succeed |
9 |
|
10 |
does GSDS have any kind of support for binary packages ? if yes, then |
11 |
how does it work ? |
12 |
|
13 |
i will deploy a number of gentoo servers in a near future and my plan |
14 |
(now) is: |
15 |
1. take 'master' machine - one required for each processor architecture |
16 |
to be supported; install them manually with all needed software |
17 |
2. tar/gzip / (with some filtering/cleaning beforehand of course) |
18 |
3. use this tar/gzip instead of an 'official' stage archive |
19 |
4. manually configure filesystems at the beginning; networking after the |
20 |
install process |
21 |
|
22 |
this has to be done binary, because of the speed |
23 |
|
24 |
on the other hand - what else can be automated in this deployment process: |
25 |
- pre-config stuff like filesystems, etc ... ? - the disk is already |
26 |
partitioned and will contain some data which has to be kept - doing it |
27 |
manually is no more then 5 minutes per server and less dangerous |
28 |
- network config ? - it is server environment with non-trivial |
29 |
networking structure (HA, backup NICs, etc ..) - auto-configuration is |
30 |
not possible |
31 |
|
32 |
well, if could you find some time, it would be great if you could |
33 |
explain me the basic advantages of GSDS over the above way of |
34 |
deployment; it would be very helpful |
35 |
|
36 |
thank you, |
37 |
martin |