| 1 |
Alec Ten Harmsel <alec <at> alectenharmsel.com> writes: |
| 2 |
|
| 3 |
|
| 4 |
> Assuming that disks are formatted, a stage3 has been freshly extracted, |
| 5 |
> bossman is installed, and the role/config files are on a mounted |
| 6 |
> filesystem, it should be similar to the role below: |
| 7 |
|
| 8 |
I think the list needs to be expanded, generically first: |
| 9 |
/var/lib/portage/world |
| 10 |
/etc/* |
| 11 |
/usr/local/* |
| 12 |
|
| 13 |
just to name a few to clone a system. I'll work on a comprehensive list |
| 14 |
of require and optional. |
| 15 |
|
| 16 |
> Automating the bootstrapping of a node is reasonably complicted, even |
| 17 |
> harder on Gentoo than on RHEL. This is the type of thinking I want to |
| 18 |
> do, and I'm working on doing this with my CentOS box that runs ssh, |
| 19 |
> Jenkins, postgres, and Redmine. |
| 20 |
|
| 21 |
|
| 22 |
I'm going to work through the ansible gentoo install method previously |
| 23 |
outlined. Once I try that for new installs, it should be easy to add |
| 24 |
what robust workstaion has added since it was installed, as the second step |
| 25 |
in the process. That way, part A of the install is a raw/virgin install |
| 26 |
on new (wiped) hardware. part B would be to upgrade that virgin install |
| 27 |
to basically be a clone of an existing workstation. This all requires |
| 28 |
similar if not identical hardware, which is a common occurrence in |
| 29 |
large installation environment. |
Archives