From: LAHAYE O. <oli...@ce...> - 2019-09-16 15:34:44
|
Hi, a small message about major enhancements on the way. * The imaging logging mechanism has been completely rewritten (and works perfectly on non-systemd distro and systemd based distro. Now, the imager is able to catch all messages from kernel, imaging logic or stdout+stderr. This means that all output from scripts can be caught. This also mean that when issuing a command in a script that interact with hardware, the kernel messages will be displayed and eventually the stdout/stderr if not redirected elsewhere. (this will also catch possible systemimager bugs 😉) * Thanks to the above, now, the install log is retrieved in real time on the server (can be disabled in cas you need massive deployment and are afraid of network load impact on the image server). Benefit: if the client is on a NATed network, you’re still able to view in real time the imager log output. * The deployment monitor (si_monitor + si_monitortk) are about to disappear. The replacement will be: * A command line tool to list clients and/or client install logs * A realtime web interface (EventSource based). The benefit is that you can view imager logs in real time even if you don’t have an X-Window server. A simple modern web browser on any OS will do the job. (si_monitortk is now a live web page). Moreover, you can open more than one console at a time. And you can see logs even if the client has finished it’s install or is rebooting (provided logs are stored on the image server). For now, the proof of concept is running. I need to write nice HTML5 + nice stylesheets and a few other things. * I’ll try to add a client EventSource (using socat in imager) as fallback when no log is on the server ( old behavior: connect to client to see logs ) (not tested and not for now) Once all the above will be working, I’ll do a build for centos-7 / centos-6 and maybe few other rpm+dracut based distro (suse, fedora, …) (a new systemimager-webgui package will be added) -- Olivier LAHAYE CEA Saclay |