Closed mbenkmann closed 9 years ago
From matthias...@gmail.com on April 30, 2013 07:03:56
Labels: Milestone-4
From matthias...@gmail.com on April 30, 2013 07:31:36
Testing confirms all of my initial expectations. The functionality described above are the only things gosa-si-client does on a server. Even things like reboot and halt are disabled on LHM servers.
From matthias...@gmail.com on April 30, 2013 12:40:57
gosa-si-client is not even needed to store logfiles for fai -N softupdate, because the log files are created in /var/log/fai/localhost/ directly by the update process. There's no need to transfer them.
From matthias...@gmail.com on April 30, 2013 12:42:49
Progress information also does not seem to be available when updating a server.
In conclusion: Now that [general]/new-config-hook is implemented, gosa-si-client is no longer needed on the server.
Status: Done
From matthias...@gmail.com on April 29, 2013 08:22:08
What does gosa-si-client do ON A SERVER:
The only feature I can think of that would need to be moved to go-susi for the startup case is the creation of /etc/ldap/... files, which I think are currently created by gosa-si-client.
During idle time I don't think gosa-si-client is doing anything useful.
During softupdate the client sends progress information to the server and at the end it probably also sends the fai log files.
Original issue: http://code.google.com/p/go-susi/issues/detail?id=119