| 13 | | * the epkg encap package manager |
| 14 | | * all software on which bcfg2 depends |
| 15 | | * bcfg2 itself |
| 16 | | * ostiary to kick off bcfg2 client runs remotely |
| 17 | | * runit to run bcfg2 client as a periodic service with logging |
| 18 | | * all with site-specific configuration parameters, set at build time in a |
| | 13 | * The epkg encap package manager |
| | 14 | * All software on which bcfg2 depends |
| | 15 | * Bcfg2 itself |
| | 16 | * Ostiary to kick off bcfg2 client runs remotely |
| | 17 | * Runit to run bcfg2 client as a periodic service with logging |
| | 18 | * All with site-specific configuration parameters, set at build time in a |
| | 142 | Another useful way of running ostiary is to put the password in a text file |
| | 143 | (on the local filesystem with appropriate permissions) and then do: |
| | 144 | {{{ |
| | 145 | for HOST in $(bcfg2-query -u); do |
| | 146 | printf "$HOST: " |
| | 147 | ostclient -a $HOST:1711 -f 0 < file-with-password.txt |
| | 148 | sleep 1 |
| | 149 | done |
| | 150 | }}} |
| | 151 | This will run the ostiary command associated with the password in |
| | 152 | "file-with-password.txt" on all hosts bcfg2 thinks are up. The sleep |
| | 153 | delay is arbitrary and not really required, but can be useful if you |
| | 154 | are monitoring the bcfg2 server logs interactively for client connections. |
| | 155 | |
| 144 | | |
| 145 | | == Supported Platforms == |
| 146 | | Below is a table of platforms that have been successfully bootstrapped using |
| 147 | | this code. |
| 148 | | |
| 149 | | || OS || Vendor || Version || Arch || GCC || By || Bcfg2 || |
| 150 | | || AIX || IBM || 5.2 || POWER || 3.3.2 || dc || 0.8.5 || |
| 151 | | || AIX || IBM || 5.3 || POWER || 4.1.1 || dc || 0.8.5 || |
| 152 | | || GNU/Linux || Debian || Sarge || i386 || 3.3.5 || dc || 0.8.5 || |
| 153 | | || GNU/Linux || Debian || Etch || x86_64 || 4.1.2 || dc || 0.9.2 || |
| 154 | | || GNU/Linux || Debian || Sid || i386 || 4.1.2 || dc || 0.8.5 || |
| 155 | | || GNU/Linux || SuSE || SLES8 || i386 || 3.2.2 || dc || 0.8.5 || |
| 156 | | || GNU/Linux || SuSE || SLES10 || i386 || 4.1.0 || dc || 0.8.5 || |
| 157 | | || GNU/Linux || Ubuntu || Dapper || i386 || 4.0.3 || dc || 0.8.5 || |
| 158 | | |
| 159 | | dc: "Daniel Clark" <mailto:[email protected]> |
| 160 | | |
| 161 | | If you bootstrap a platform not listed above, please add a comment to: |
| 162 | | * http://trac.mcs.anl.gov/projects/bcfg2/ticket/74 |
| 163 | | so that platform can be added to the list. |
| 164 | | |
| 165 | | If you modified any of the files in this package to be able to bootstrap the |
| 166 | | new platform, please include either diffs or a tarball of your modified |
| 167 | | version in a new ticket so your changes can be incorporated into a new |
| 168 | | release. |
| 169 | | |
| 170 | | Any other notes, such as where you got the GNU binaries or any issues people |
| 171 | | should be aware of, would also be appreciated. |
| 172 | | |
| 173 | | You may want to scan all of the bootstrapped binaries and libraries with |
| 174 | | `ldd` (or equivalent) to make sure there are no dependencies on libraries |
| 175 | | other than those included with the base operating system and the libraries |
| 176 | | built as part of the bootstrap process. |
