| 1 |
On Tue, Oct 12, 2010 at 04:44:08PM -0400, Richard Freeman wrote: |
| 2 |
> Maybe a "stage4" that is basically the handbook with some default |
| 3 |
> choices made could help here - pick a syslog, crond, dhcpcd, etc. |
| 4 |
What I have for infra unfortunately won't be much use outside of infra. |
| 5 |
1. wget a script to the machine |
| 6 |
2. Set hostname |
| 7 |
2. Run phase1 script manually |
| 8 |
2.0. Zero entire disk (optional) |
| 9 |
2.1. partition setup (sfdisk/gdisk/mdadm/LVM inputs) |
| 10 |
2.2. mkfs |
| 11 |
2.3. mount |
| 12 |
2.4. Grabs the infra stage4 tarball |
| 13 |
2.5. Unpack stage4 to new partitions |
| 14 |
3. phase1 script runs the second-phase install script from inside the |
| 15 |
chroot, which does: |
| 16 |
3.1. Loads a portage snapshot (w/ custom exclude rules) |
| 17 |
3.2. Upgrades portage (we use ~arch portage-2.1 on an otherwise stable |
| 18 |
system) |
| 19 |
3.3. 5 passes of cfengine install work: |
| 20 |
3.4. cfengine pass1: Copy down rest of cfengine config, set up client key |
| 21 |
3.5. cfengine pass2: Copy down files for system, includes pre-compiled |
| 22 |
kernels, modules. |
| 23 |
3.6. (create our make.conf via merging segments) |
| 24 |
3.7. cfengine pass3: install+update packages |
| 25 |
3.8. (apply all config updates) |
| 26 |
3.9. cfengine pass4: apply custom configs |
| 27 |
3.10. cfengine pass5: final check for install/update/configs |
| 28 |
3.11. (verify MBR) |
| 29 |
3.12. check and/or set root password |
| 30 |
4. Manual verification if desired |
| 31 |
5. Manual trigger of reboot |
| 32 |
|
| 33 |
Contents of infra stage4 tarball: |
| 34 |
- stage3 hardened multilib x86/amd64/ppc64 |
| 35 |
- cfengine bootstrap segment in /var/cfengine/, includes key for master server |
| 36 |
- /etc/localtime as UTC |
| 37 |
- bunch of scripts for phase2 of install |
| 38 |
|
| 39 |
As for time consumption: |
| 40 |
- For a new machine at an existing location, about 30 minutes to write |
| 41 |
the install configs. |
| 42 |
- For a totally new location, and extra 30 minutes for writing install |
| 43 |
config. |
| 44 |
- phase1 runtime, not including disk zeroing is 2-5 minutes. |
| 45 |
- phase2 runtime varies depending on CPU speed and what config we're |
| 46 |
putting on machine, but I'd say 2-3 hours is average, and we use very |
| 47 |
little in the way of binpkgs. |
| 48 |
|
| 49 |
-- |
| 50 |
Robin Hugh Johnson |
| 51 |
Gentoo Linux: Developer, Trustee & Infrastructure Lead |
| 52 |
E-Mail : robbat2@g.o |
| 53 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives