configuring...
Harlan Stenn <[email protected]>
| Newsgroups | gmane.comp.sysutils.ark.devel |
|---|---|
| Message-ID | <[email protected]> |
I'd like to find a way to massively simplify ARK configuration. I'm interested in this because I'm still spending way too much time trying to figure out how to get this thing going. I'd like to be able to configure my team(s) by providing: - a way to specify the "covered" hosts - - /etc/hosts? - - DNS? - - something else? - a way to specify the ARK-specific directories I'm thinking about using autogen to do this, at least at first. Any ideas? While we're on the subject, I'm wondering how the ark-built software for a particular architecture gets deployed(?) on each machine. Is it: - built on each machine? - installed from a shared build tree? If the latter, I'm thinking that it might make sense in some environments to do the "official" building of software to an NFS-shared area (for example), and then hosts can deploy from that area if they want local copies of the packages, or NFS (for example) mount the packages if they are relatively diskless machines. Going further, I'm thinking that perhaps the sidai style of teams need not be the 1 way to do everything, but could handle "choices" when appropriate. H