https://wiki.fai-project.org/api.php?action=feedcontributions&user=Eartoast&feedformat=atomFAIWiki - User contributions [en]2024-03-28T09:54:19ZUser contributionsMediaWiki 1.39.5https://wiki.fai-project.org/index.php?title=Fai-updater&diff=3680Fai-updater2023-05-29T09:54:46Z<p>Eartoast: /* Fai-updater in its basic mode */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
https://user-images.githubusercontent.com/516503/241696679-6e4227d8-9069-408c-8063-0401c44a6bc0.png<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
https://github.com/glaweh/fai-updater/assets/516503/df17f8d1-ba7f-476f-8536-2d8f7eceb656<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
<nowiki><br />
Usage: ./bin/fai-updater-ncurses [options] <@netgroup|host [...]><br />
<br />
Help Options:<br />
-h, --help display this help message<br />
--version print version information<br />
<br />
Application Options:<br />
-o, --ordered ordered mode: don't randomize order of hosts<br />
-s, --simultaneous <NUM> run updates on NUM hosts simultanously<br />
(default: 4)<br />
-n, --dryrun dryrun mode: use a dummy-script instead of<br />
really contacting the clients<br />
</nowiki><br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3679Fai-updater2023-05-29T09:52:41Z<p>Eartoast: /* Fai-updater in its basic mode */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[[Image:https://user-images.githubusercontent.com/516503/241696679-6e4227d8-9069-408c-8063-0401c44a6bc0.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
https://github.com/glaweh/fai-updater/assets/516503/df17f8d1-ba7f-476f-8536-2d8f7eceb656<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
<nowiki><br />
Usage: ./bin/fai-updater-ncurses [options] <@netgroup|host [...]><br />
<br />
Help Options:<br />
-h, --help display this help message<br />
--version print version information<br />
<br />
Application Options:<br />
-o, --ordered ordered mode: don't randomize order of hosts<br />
-s, --simultaneous <NUM> run updates on NUM hosts simultanously<br />
(default: 4)<br />
-n, --dryrun dryrun mode: use a dummy-script instead of<br />
really contacting the clients<br />
</nowiki><br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3678Fai-updater2023-05-29T09:52:00Z<p>Eartoast: /* Fai-updater with an open logfile viewer */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
https://user-images.githubusercontent.com/516503/241696679-6e4227d8-9069-408c-8063-0401c44a6bc0.png<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
https://github.com/glaweh/fai-updater/assets/516503/df17f8d1-ba7f-476f-8536-2d8f7eceb656<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
<nowiki><br />
Usage: ./bin/fai-updater-ncurses [options] <@netgroup|host [...]><br />
<br />
Help Options:<br />
-h, --help display this help message<br />
--version print version information<br />
<br />
Application Options:<br />
-o, --ordered ordered mode: don't randomize order of hosts<br />
-s, --simultaneous <NUM> run updates on NUM hosts simultanously<br />
(default: 4)<br />
-n, --dryrun dryrun mode: use a dummy-script instead of<br />
really contacting the clients<br />
</nowiki><br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3677Fai-updater2023-05-29T09:51:03Z<p>Eartoast: /* Fai-updater in its basic mode */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
https://user-images.githubusercontent.com/516503/241696679-6e4227d8-9069-408c-8063-0401c44a6bc0.png<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
<nowiki><br />
Usage: ./bin/fai-updater-ncurses [options] <@netgroup|host [...]><br />
<br />
Help Options:<br />
-h, --help display this help message<br />
--version print version information<br />
<br />
Application Options:<br />
-o, --ordered ordered mode: don't randomize order of hosts<br />
-s, --simultaneous <NUM> run updates on NUM hosts simultanously<br />
(default: 4)<br />
-n, --dryrun dryrun mode: use a dummy-script instead of<br />
really contacting the clients<br />
</nowiki><br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3676Fai-updater2023-05-29T09:50:08Z<p>Eartoast: /* Fai-updater in its basic mode */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[Image:https://user-images.githubusercontent.com/516503/241696679-6e4227d8-9069-408c-8063-0401c44a6bc0.png]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
<nowiki><br />
Usage: ./bin/fai-updater-ncurses [options] <@netgroup|host [...]><br />
<br />
Help Options:<br />
-h, --help display this help message<br />
--version print version information<br />
<br />
Application Options:<br />
-o, --ordered ordered mode: don't randomize order of hosts<br />
-s, --simultaneous <NUM> run updates on NUM hosts simultanously<br />
(default: 4)<br />
-n, --dryrun dryrun mode: use a dummy-script instead of<br />
really contacting the clients<br />
</nowiki><br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3675Fai-updater2023-05-29T09:49:04Z<p>Eartoast: /* Fai-updater in its basic mode */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
https://user-images.githubusercontent.com/516503/241696679-6e4227d8-9069-408c-8063-0401c44a6bc0.png<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
<nowiki><br />
Usage: ./bin/fai-updater-ncurses [options] <@netgroup|host [...]><br />
<br />
Help Options:<br />
-h, --help display this help message<br />
--version print version information<br />
<br />
Application Options:<br />
-o, --ordered ordered mode: don't randomize order of hosts<br />
-s, --simultaneous <NUM> run updates on NUM hosts simultanously<br />
(default: 4)<br />
-n, --dryrun dryrun mode: use a dummy-script instead of<br />
really contacting the clients<br />
</nowiki><br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3674Fai-updater2023-05-29T09:47:19Z<p>Eartoast: /* Fai-updater in its basic mode */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[Image:https://user-images.githubusercontent.com/516503/241696679-6e4227d8-9069-408c-8063-0401c44a6bc0.png<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
<nowiki><br />
Usage: ./bin/fai-updater-ncurses [options] <@netgroup|host [...]><br />
<br />
Help Options:<br />
-h, --help display this help message<br />
--version print version information<br />
<br />
Application Options:<br />
-o, --ordered ordered mode: don't randomize order of hosts<br />
-s, --simultaneous <NUM> run updates on NUM hosts simultanously<br />
(default: 4)<br />
-n, --dryrun dryrun mode: use a dummy-script instead of<br />
really contacting the clients<br />
</nowiki><br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3673Fai-updater2023-05-29T09:43:01Z<p>Eartoast: /* Fai-updater in its basic mode */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
<img src="https://user-images.githubusercontent.com/516503/241696679-6e4227d8-9069-408c-8063-0401c44a6bc0.png" alt="fai-updater" style="max-width: 100%;"><br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
<nowiki><br />
Usage: ./bin/fai-updater-ncurses [options] <@netgroup|host [...]><br />
<br />
Help Options:<br />
-h, --help display this help message<br />
--version print version information<br />
<br />
Application Options:<br />
-o, --ordered ordered mode: don't randomize order of hosts<br />
-s, --simultaneous <NUM> run updates on NUM hosts simultanously<br />
(default: 4)<br />
-n, --dryrun dryrun mode: use a dummy-script instead of<br />
really contacting the clients<br />
</nowiki><br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3672Fai-updater2023-05-29T09:32:29Z<p>Eartoast: /* Fai-updater in its basic mode */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[[Image:https://github.com/glaweh/fai-updater/assets/516503/6e4227d8-9069-408c-8063-0401c44a6bc0]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
<nowiki><br />
Usage: ./bin/fai-updater-ncurses [options] <@netgroup|host [...]><br />
<br />
Help Options:<br />
-h, --help display this help message<br />
--version print version information<br />
<br />
Application Options:<br />
-o, --ordered ordered mode: don't randomize order of hosts<br />
-s, --simultaneous <NUM> run updates on NUM hosts simultanously<br />
(default: 4)<br />
-n, --dryrun dryrun mode: use a dummy-script instead of<br />
really contacting the clients<br />
</nowiki><br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3671Fai-updater2023-05-29T08:22:42Z<p>Eartoast: /* Command line options */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[[Image:Fai-updater.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
<nowiki><br />
Usage: ./bin/fai-updater-ncurses [options] <@netgroup|host [...]><br />
<br />
Help Options:<br />
-h, --help display this help message<br />
--version print version information<br />
<br />
Application Options:<br />
-o, --ordered ordered mode: don't randomize order of hosts<br />
-s, --simultaneous <NUM> run updates on NUM hosts simultanously<br />
(default: 4)<br />
-n, --dryrun dryrun mode: use a dummy-script instead of<br />
really contacting the clients<br />
</nowiki><br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3670Fai-updater2023-05-29T08:19:24Z<p>Eartoast: /* Command line options */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[[Image:Fai-updater.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options === <br />
Usage: ./bin/fai-updater-ncurses [options] <@netgroup|host [...]><br />
<br />
Help Options:<br />
-h, --help display this help message<br />
--version print version information<br />
<br />
Application Options:<br />
-o, --ordered ordered mode: don't randomize order of hosts<br />
-s, --simultaneous <NUM> run updates on NUM hosts simultanously<br />
(default: 4)<br />
-n, --dryrun dryrun mode: use a dummy-script instead of<br />
really contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3669Fai-updater2023-05-29T08:17:19Z<p>Eartoast: /* Download */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[[Image:Fai-updater.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
<br />
https://github.com/glaweh/fai-updater<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3668Fai-updater2023-05-29T08:15:51Z<p>Eartoast: /* Install */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[[Image:Fai-updater.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
[[media:fai-updater-20060321.tgz]]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just run<br />
<br />
git clone https://github.com/glaweh/fai-updater.git<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=3667Fai-updater2023-05-29T08:02:24Z<p>Eartoast: /* Screenshots */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''left'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the last three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[[Image:Fai-updater.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
[[media:fai-updater-20060321.tgz]]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org><br />
<br />
<br />
[[Category:Howto]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=DeveloperWorkshopAugust2008&diff=2770DeveloperWorkshopAugust20082008-07-18T12:36:27Z<p>Eartoast: my boss agreed... so i am coming to essen :)</p>
<hr />
<div>= General Information =<br />
We would like the participants to read the [[DevWorkshopGuidelines]] first, then you can add yourself to the list of interested participants below.<br />
<br />
= Date =<br />
'''8th to 10th of August 2008''' at the Linuxhotel in Essen, Germany.<br />
<br />
= Location =<br />
Linuxhotel in Essen ([http://www.linuxhotel.de/anreise.html Travel info, Anreise])<br />
<br />
See http://www.linuxhotel.de/community.html for generic information on community events at this location (only in German language)<br />
<br />
= Sleeping, Eating, Drinking =<br />
<br />
Sleeping in the hotel, breakfast, coffee flatrate and drinks are included in the low fee we have to pay. We have to organize lunch and dinner on our own. Normally we manage to pay everything with the money from our sponsors, so you do not have to pay anything.<br />
<br />
= Cost/Sponsorship =<br />
Due to german tax laws, the Linuxhotel is not allowed anymore to give the location away for free.<br />
They have to charge some money:<br />
<br />
* If n=number of persons, overall amount of money needed: n * 60<br />
<br />
Additional money is needed for food and travel sponsorship<br />
<br />
'''We're looking for sponsors from now on, so far we have an agreement with these companies:'''<br />
<br />
* http://www.linux-ag.com<br />
<br />
<br />
== TODO: ask other sponsors==<br />
Potentially the ones from last time:<br />
* http://www.b1systems.de<br />
* http://www.lt-ec.de<br />
* Linux Solution Park Hamburg<br />
<br />
= Participants/Registration =<br />
Add your name here if you intedn to participate, and for planning purposes, also mail to henning(et)sprang[dodd]de.<br />
<br />
Please don't forget to let us know some contact data, especially in case you don't read the -devel Mailing list. <br />
'''In case of travel sponsorship required, please add a guess of your travel costs.'''<br />
<br />
<br />
== Definitively ==<br />
* Thomas Lange<br />
* Henning Sprang<br />
* Henning Glawe<br />
<br />
== Maybe: ==<br />
You won't come maybe - you'll come for sure, isn't it? :)<br />
<br />
Michael Tautschnig (I will try hard to attend, just don't know about the schedules for August yet)<br />
<br />
= Communication =<br />
We can talk on the usual IRC Channel and using the linux-fai-devel<br />
mailing list.<br />
<br />
* Mailing list for announcement: https://listi.jpberlin.de/mailman/listinfo/fai-dev-workshop<br />
<br />
Please subscribe to it if you are an (interested) participant.<br />
Import information about the event will be communicated there.<br />
<br />
= Agenda (1. Vorschlag) =<br />
<br />
==== Freitag ==== <br />
<br />
* Aufbau des Netzwerk<br />
* Bug squashing hour bis alle da sind, Mrfai sucht Hilfe fuer Bugs<br />
* Wenn alle da sind: Vorstellungsrunde, Agenda genauer festlegen<br />
* Read access von /dev/beer<br />
* Define things that need to be worked on with high priority for the Lenny release<br />
<br />
<br />
==== Samstag ==== <br />
<br />
* Work on things for Lenny release<br />
* Meeting: Was haben wir erreicht?<br />
<br />
==== Sonntag ==== <br />
<br />
* Work on things for Lenny release<br />
* Meeting: Was haben wir erreicht - was fehlt noch?<br />
<br />
<br />
== topic proposals for discussion and work ==<br />
In this section, you can enter proposals for topics to work on, and things to discuss. Please add your name and maybe contact information, if you are not well known to your proposals in case of occuring questions.<br />
<br />
People interested in a topic should enter their name in the section of this topic to show their interest.<br />
<br />
You can mark your topic with (D) or (W) to make clear it's a (D)iscussion or (W)ork topic.<br />
<br />
* Once again: Further work on a simple FAI gui (ldap-independent/storage-agnostic and easy to install) - see [[GUIConcept]] (W) --[[User:Lazyboy|lazyboy]]<br />
* Once more: setup_harddisks (W) --[[User:Michael|michael]], Mrfai, [[User:Lazyboy|lazyboy]]<br />
* include XEN examples? (D) (does this makes sense without using XEN kernel in FAI examples?) -- [[User:Lazyboy|lazyboy]]<br />
* Get the bug-count down to 0 (W) --[[User:Michael|michael]]<br />
<br />
== Timeline ==<br />
Moderator: Henning Sprang will be responsible to take care that we (roughly)keep in line with the agenda. Talk to him if you see the need for spontaneous changes in the course of the workshop.<br />
<br />
<br />
In general we will have:<br />
<br />
* Starting meeting - people introduce themselves, tell about their interests to work on, workgroups are built, final schedule outlined<br />
* In the middle: Discussion about general ideas for the further FAI development<br />
* End: Discussion about progress made on the work topics - what did we reach - what will happen with the topics not done yet, how will the workgroups continue working on them</div>Eartoasthttps://wiki.fai-project.org/index.php?title=DeveloperWorkshopAugust2008&diff=2769DeveloperWorkshopAugust20082008-07-16T15:05:43Z<p>Eartoast: /* Maybe: */</p>
<hr />
<div>= General Information =<br />
We would like the participants to read the [[DevWorkshopGuidelines]] first, then you can add yourself to the list of interested participants below.<br />
<br />
= Date =<br />
'''8th to 10th of August 2008''' at the Linuxhotel in Essen, Germany.<br />
<br />
= Location =<br />
Linuxhotel in Essen ([http://www.linuxhotel.de/anreise.html Travel info, Anreise])<br />
<br />
See http://www.linuxhotel.de/community.html for generic information on community events at this location (only in German language)<br />
<br />
= Sleeping, Eating, Drinking =<br />
<br />
Sleeping in the hotel, breakfast, coffee flatrate and drinks are included in the low fee we have to pay. We have to organize lunch and dinner on our own. Normally we manage to pay everything with the money from our sponsors, so you do not have to pay anything.<br />
<br />
= Cost/Sponsorship =<br />
Due to german tax laws, the Linuxhotel is not allowed anymore to give the location away for free.<br />
They have to charge some money:<br />
<br />
* If n=number of persons, overall amount of money needed: n * 60<br />
<br />
Additional money is needed for food and travel sponsorship<br />
<br />
'''We're looking for sponsors from now on, so far we have an agreement with these companies:'''<br />
<br />
* http://www.linux-ag.com<br />
<br />
<br />
== TODO: ask other sponsors==<br />
Potentially the ones from last time:<br />
* http://www.b1systems.de<br />
* http://www.lt-ec.de<br />
* Linux Solution Park Hamburg<br />
<br />
= Participants/Registration =<br />
Add your name here if you intedn to participate, and for planning purposes, also mail to henning(et)sprang[dodd]de.<br />
<br />
Please don't forget to let us know some contact data, especially in case you don't read the -devel Mailing list. <br />
'''In case of travel sponsorship required, please add a guess of your travel costs.'''<br />
<br />
<br />
== Definitively ==<br />
* Thomas Lange<br />
* Henning Sprang<br />
<br />
== Maybe: ==<br />
You won't come maybe - you'll come for sure, isn't it? :)<br />
<br />
Michael Tautschnig (I will try hard to attend, just don't know about the schedules for August yet)<br />
Henning Glawe (I just filled out the "Dienstreiseantrag", hopefully I will get permission and funds)<br />
<br />
= Communication =<br />
We can talk on the usual IRC Channel and using the linux-fai-devel<br />
mailing list.<br />
<br />
* Mailing list for announcement: https://listi.jpberlin.de/mailman/listinfo/fai-dev-workshop<br />
<br />
Please subscribe to it if you are an (interested) participant.<br />
Import information about the event will be communicated there.<br />
<br />
= Agenda (1. Vorschlag) =<br />
<br />
==== Freitag ==== <br />
<br />
* Aufbau des Netzwerk<br />
* Bug squashing hour bis alle da sind, Mrfai sucht Hilfe fuer Bugs<br />
* Wenn alle da sind: Vorstellungsrunde, Agenda genauer festlegen<br />
* Read access von /dev/beer<br />
* Define things that need to be worked on with high priority for the Lenny release<br />
<br />
<br />
==== Samstag ==== <br />
<br />
* Work on things for Lenny release<br />
* Meeting: Was haben wir erreicht?<br />
<br />
==== Sonntag ==== <br />
<br />
* Work on things for Lenny release<br />
* Meeting: Was haben wir erreicht - was fehlt noch?<br />
<br />
<br />
== topic proposals for discussion and work ==<br />
In this section, you can enter proposals for topics to work on, and things to discuss. Please add your name and maybe contact information, if you are not well known to your proposals in case of occuring questions.<br />
<br />
People interested in a topic should enter their name in the section of this topic to show their interest.<br />
<br />
You can mark your topic with (D) or (W) to make clear it's a (D)iscussion or (W)ork topic.<br />
<br />
* Once again: Further work on a simple FAI gui (ldap-independent/storage-agnostic and easy to install) - see [[GUIConcept]] (W) --[[User:Lazyboy|lazyboy]]<br />
* Once more: setup_harddisks (W) --[[User:Michael|michael]], Mrfai, [[User:Lazyboy|lazyboy]]<br />
* include XEN examples? (D) (does this makes sense without using XEN kernel in FAI examples?) -- [[User:Lazyboy|lazyboy]]<br />
* Get the bug-count down to 0 (W) --[[User:Michael|michael]]<br />
<br />
== Timeline ==<br />
Moderator: Henning Sprang will be responsible to take care that we (roughly)keep in line with the agenda. Talk to him if you see the need for spontaneous changes in the course of the workshop.<br />
<br />
<br />
In general we will have:<br />
<br />
* Starting meeting - people introduce themselves, tell about their interests to work on, workgroups are built, final schedule outlined<br />
* In the middle: Discussion about general ideas for the further FAI development<br />
* End: Discussion about progress made on the work topics - what did we reach - what will happen with the topics not done yet, how will the workgroups continue working on them</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=996Fai-updater2006-03-29T10:22:39Z<p>Eartoast: /* Download */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two. Note: they were done using fai-updater's dry-run mode,<br />
which does not touch the hosts, but feeds fai-updater with random log snippets instead to test the<br />
updaters log parser.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''right'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column from the right), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the first three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[[Image:Fai-updater.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download the FAI updater from here:<br />
[[media:fai-updater-20060321.tgz]]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=447Fai-updater2006-03-29T10:20:17Z<p>Eartoast: /* Download */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two. Note: they were done using fai-updater's dry-run mode,<br />
which does not touch the hosts, but feeds fai-updater with random log snippets instead to test the<br />
updaters log parser.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''right'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column from the right), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the first three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[[Image:Fai-updater.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
Until I figure out how to upload a tarball to the wiki, you can download <br />
fai-updater from<br />
[http://www.physik.fu-berlin.de/~glaweh/pfai/fai-updater-20060321.tar.gz]<br />
[[File:fai-updater-20060321.tgz]]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=File:Fai-updater-20060321.tgz&diff=972File:Fai-updater-20060321.tgz2006-03-29T10:18:15Z<p>Eartoast: fai-updater version 20060321</p>
<hr />
<div>fai-updater version 20060321</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=446Fai-updater2006-03-22T10:48:40Z<p>Eartoast: /* Screenshots */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two. Note: they were done using fai-updater's dry-run mode,<br />
which does not touch the hosts, but feeds fai-updater with random log snippets instead to test the<br />
updaters log parser.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''right'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column from the right), the first "waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the first three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[[Image:Fai-updater.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
Until I figure out how to upload a tarball to the wiki, you can download <br />
fai-updater from<br />
[http://www.physik.fu-berlin.de/~glaweh/pfai/fai-updater-20060321.tar.gz]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=430Fai-updater2006-03-22T10:48:02Z<p>Eartoast: /* Screenshots */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
Everybody likes screenshots, so here are two. Note: they were done using fai-updater's dry-run mode,<br />
which does not touch the hosts, but feeds fai-updater with random log snippets instead to test the<br />
updaters log parser.<br />
<br />
General logic is the following:<br />
* clients are put into the "waiting" queue (the ''right'' column), by default in randomized order<br />
* as soon as a slot in the "running" queue gets free (the second column from the right), the first<br />
"waiting" client gets updated/put into the "running" status and stays there until the update task finished<br />
* Depending on the outcome, the client is sorted in one of the first three columns:<br />
** Unreachable: the host was unreachable or the fai softupdate could not be started there<br />
** Error: the updater detected an error during the update (basically, it parses for the error string produced<br />
by a logcheck script such as hooks/savelog.LAST in the simple example)<br />
** Success: the update finished and no error was detected<br />
==== Fai-updater in its basic mode ====<br />
[[Image:Fai-updater.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
Until I figure out how to upload a tarball to the wiki, you can download <br />
fai-updater from<br />
[http://www.physik.fu-berlin.de/~glaweh/pfai/fai-updater-20060321.tar.gz]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=429Fai-updater2006-03-22T10:31:55Z<p>Eartoast: /* Fai-updater with an open logfile viewer */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
==== Fai-updater in its basic mode ====<br />
[[Image:Fai-updater.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[[Image:fai-updater-viewer.png]]<br />
<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
Until I figure out how to upload a tarball to the wiki, you can download <br />
fai-updater from<br />
[http://www.physik.fu-berlin.de/~glaweh/pfai/fai-updater-20060321.tar.gz]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=428Fai-updater2006-03-22T10:31:37Z<p>Eartoast: /* Fai-updater in its basic mode */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
==== Fai-updater in its basic mode ====<br />
[[Image:Fai-updater.png]]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[Image:fai-updater-viewer.png]<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
Until I figure out how to upload a tarball to the wiki, you can download <br />
fai-updater from<br />
[http://www.physik.fu-berlin.de/~glaweh/pfai/fai-updater-20060321.tar.gz]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=427Fai-updater2006-03-22T10:30:23Z<p>Eartoast: /* Fai-updater in its basic mode */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
==== Fai-updater in its basic mode ====<br />
[Image:Fai-updater.png]<br />
<br />
==== Fai-updater with an open logfile viewer ====<br />
[Image:fai-updater-viewer.png]<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
Until I figure out how to upload a tarball to the wiki, you can download <br />
fai-updater from<br />
[http://www.physik.fu-berlin.de/~glaweh/pfai/fai-updater-20060321.tar.gz]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=426Fai-updater2006-03-22T10:29:41Z<p>Eartoast: added screenshots</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== Screenshots ===<br />
==== Fai-updater in its basic mode ====<br />
[Image:fai-updater.png]<br />
==== Fai-updater with an open logfile viewer ====<br />
[Image:fai-updater-viewer.png]<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
Until I figure out how to upload a tarball to the wiki, you can download <br />
fai-updater from<br />
[http://www.physik.fu-berlin.de/~glaweh/pfai/fai-updater-20060321.tar.gz]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=File:Fai-updater.png&diff=998File:Fai-updater.png2006-03-22T10:24:17Z<p>Eartoast: fai-updater screenshot, disabled viewer</p>
<hr />
<div>fai-updater screenshot, disabled viewer</div>Eartoasthttps://wiki.fai-project.org/index.php?title=File:Fai-updater-viewer.png&diff=997File:Fai-updater-viewer.png2006-03-22T10:12:40Z<p>Eartoast: screenshot of fai-updater with enabled viewer window</p>
<hr />
<div>screenshot of fai-updater with enabled viewer window</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=425Fai-updater2006-03-21T18:47:29Z<p>Eartoast: /* Download */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
Until I figure out how to upload a tarball to the wiki, you can download <br />
fai-updater from<br />
[http://www.physik.fu-berlin.de/~glaweh/pfai/fai-updater-20060321.tar.gz]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=424Fai-updater2006-03-21T18:47:14Z<p>Eartoast: /* Download */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
Until I figure out how to upload a tarball to the wiki, you can download <br />
fai-updater from<br />
[http://www.physik.fu-berlin.de/~glaweh/pfai/fai-updater-20060321.tar.gz|here]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Main_Page&diff=449Main Page2006-03-21T18:45:16Z<p>Eartoast: /* documentation and examples */</p>
<hr />
<div>Hello and welcome to the FAI wiki.<br />
<br />
This is a public wiki for [http://www.informatik.uni-koeln.de/fai/ FAI - Fully Automatic Installation] - a tool for automatic installation of Debian and other Linux Distributions.<br />
It's a place for users and developers of FAI to share information. If you have some information on FAI to share, see the page [[wiki registration]] - you need to write a mail, because we can't handle the spam otherwise. Also, please read [[editing rules]].<br />
<br />
== getting FAI ==<br />
if you want the latest and greatest version:<br />
* download it from: http://www.informatik.uni-koeln.de/fai/download/<br />
* add this to your /etc/apt/sources.list: <br />
<pre>deb http://www.informatik.uni-koeln.de/fai/ download/</pre><br />
* install it within debian sid<br />
<br />
== documentation and examples ==<br />
* Main documentation for FAI is the fai guide: Either in [http://www.informatik.uni-koeln.de/fai/fai-guide.html/ english], [http://www.informatik.uni-koeln.de/fai/fai-guide-fr/ french], [http://pc.debian.ro/fai/ romanian]<br />
* [http://www.informatik.uni-koeln.de/fai/ FAI Homepage]<br />
* [[Resources]] - there are some information resources about FAI available &quot;out there&quot;, as well as some unofficial developer branches, that are handled somewhere else until that code is incoporated in the FAI main Branch - and we want to point to them.<br />
* [[Wishlist]] (for those users that can't use the debian bts for reporting a bug of type wishlist and for developers who want to know what users wish) <br />
* [[reporting bugs]] and also maybe find fixes for problems that you might encounter when using FAI.<br />
* [[example classes]] and [[helper scripts]] - classes and small code contributions that are not (already) part of the FAI distribution<br />
* tips and tricks - other hints for users by users that are not exactly written in code like the above - general advice, configuration hints<br />
** smaller [[tips and tricks]]<br />
** Install Ubuntu and other distributions with FAI by using [[FAI multi-distribution]]<br />
** [[Using gpg-authenticated debian-archives]]<br />
** [[Using FAI to set up XEN domains]]<br />
** [http://faiwiki.informatik.uni-koeln.de/index.php/User:Svamberg/Software_RAID Software-RAID with mdadm]<br />
** [http://www.informatik.uni-koeln.de/fai/download/developers/setup_harddisks patched version of setup_harddisks]: Code refactoring, LVM/RAID support and POD manual page: Copyright (c) 2003, Sam Vilain]<br />
** [http://www.linuxma.com/fai_raid/ LVM & RAID]<br />
** [http://faiwiki.informatik.uni-koeln.de/index.php/User:Svamberg/Logs_to_mail FAI-Logs via Mail]<br />
** [http://faiwiki.informatik.uni-koeln.de/index.php/User:Svamberg/Making_documentation Creating class-based documentaion]<br />
** [[Using_customized_kernels_with_FAI]]<br />
** [[Fai-updater|Perform FAI softupdates on many machines at the same time]]<br />
* [[Success Stories]] - who is using FAI, how and why - and, when available pictures of the machines installed with FAI :)<br />
* [http://www.informatik.uni-koeln.de/fai/q-answers User reports] by filling out the [http://www.informatik.uni-koeln.de/fai/questionnaire FAI questionnaire] (TODO: create a webform for this)<br />
* [[user FAQ]] ( from questions in the mailing list and on IRC freenode #fai) - We took the contents of the old and somewhat unmaintained [http://faifaq.andrew.net.au/cache/index.html fai faqmatic] to this wiki to have all information more centralized. Please use the Wiki from now on.<br />
* [[linux-fai mailing list infos]] (Netiquette, how to subscribe and use)<br />
* this wiki needs a [[Logo]]<br />
<br />
* [http://www.debian-administration.org/articles/240 a short tutorial on www.debian-administration.org]<br />
* [http://jijo.free.net.ph/files/talks/20050914-linuxworld2005.pdf a talk on fai and debian]<br />
<br />
== Developer information ==<br />
Stuff for people interested in helping with FAI: [[Developers information]]<br />
<br />
== Wiki Information ==<br />
* [[FAIWiki:About | About this Wiki]] - info on this wiki<br />
* [[help for editing]] (mainly mediawiki documentation links)<br />
* [[editing rules]] - some ideas that make collaborative work here easier<br />
* practice wiki writing [[practice wiki writing|here]]</div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=423Fai-updater2006-03-21T18:41:06Z<p>Eartoast: /* Some comments on the code */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download fai-updater from<br />
[http://www.physik.fu-berlin.de/~glaweh/pfai/fai-updater-20060321.tar.gz]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh (at) debian (dot) org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=421Fai-updater2006-03-21T18:39:23Z<p>Eartoast: /* Download */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download fai-updater from<br />
[http://www.physik.fu-berlin.de/~glaweh/pfai/fai-updater-20060321.tar.gz]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh@debian.org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=420Fai-updater2006-03-21T18:34:08Z<p>Eartoast: </p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Download ===<br />
You can download fai-updater from the faiwiki: <br />
[[file:fai-updater-20060321.tar.gz]]<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh@debian.org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=419Fai-updater2006-03-21T18:29:54Z<p>Eartoast: /* Connecting to the clients */</p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh@debian.org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=418Fai-updater2006-03-21T18:29:14Z<p>Eartoast: </p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==<br />
=== License ===<br />
I put this code under the GPLv2<br />
<br />
=== Required packages ===<br />
for the frontend, you need the Curses::UI perl module, in Debian you get<br />
it via<br />
<br />
apt-get install libcurses-ui-perl<br />
<br />
On the client side, fai-client is needed and of course a FAI configuration<br />
which is update-safe.<br />
<br />
=== Install ===<br />
Just unpack the tarball.<br />
<br />
=== Command line options ===<br />
updater-curses [options] <netgroup|-H host1,host2,...><br />
--help display this help message<br />
--version print version<br />
-o ordered mode: don't randomize order of hosts<br />
-s <number> number of updates running simultanously<br />
-n dryrun mode: use a dummy-script instead of really <br />
contacting the clients<br />
<br />
=== Connecting to the clients ===<br />
A script using ssh is included, but of course you can edit it to match <br />
your own needs.<br />
To be able to connect to the clients using the provided libexec/faiupdate, <br />
you need to have some way to access them via ssh as root without entering<br />
a password.<br />
A solution for this is to install a matching file as <br />
/root/.ssh/authorized_keys, start ssh-agent and load the private key <br />
into it _before_ starting fai-updater.<br />
Another, but from a security point of view dangerous, possibility is to<br />
use a passphrase-less ssh private key into the account under which you run <br />
fai-updater.<br />
<br />
=== Some comments on the code ===<br />
<br />
I know the code is quite rough, as though I tried programming cleanly, a<br />
lot of hacks have slipped in, and I don't have the time to clean up the<br />
code right now due to my diploma thesis' deadline ;)<br />
<br />
If you have any questions or suggestions, feel free to write me.<br />
<br />
Henning Glawe <glaweh@debian.org></div>Eartoasthttps://wiki.fai-project.org/index.php?title=Fai-updater&diff=417Fai-updater2006-03-21T18:21:14Z<p>Eartoast: </p>
<hr />
<div>== fai-updater - run and supervise softupdates on many machines at the same time ==</div>Eartoasthttps://wiki.fai-project.org/index.php?title=User:Eartoast&diff=995User:Eartoast2006-03-21T18:20:14Z<p>Eartoast: </p>
<hr />
<div>Henning Glawe - [http://www.physik.fu-berlin.de/~glaweh]<br />
<br />
I have written a utility called [[fai-updater]] for doing softupdates on many machines in parallel</div>Eartoasthttps://wiki.fai-project.org/index.php?title=User:Eartoast&diff=416User:Eartoast2006-03-21T18:14:00Z<p>Eartoast: </p>
<hr />
<div>Henning Glawe - [http://www.physik.fu-berlin.de/~glaweh]</div>Eartoast