I suppose one question is whether it makes sense to discontinue embedding the imager in our Dracut-generated image and just use the systemimager image whole.
The whole sans-reboot I presume is kexec. I formerly tried that and it produced some less than ideal results hopping between disparate distribution provided kernels, but that was years ago. Of course let me know if I’m wrong and it’s more along the lines of having the imager donor system more aligned with the deployment target. From: Olivier Lahaye <olivier.laha...@free.fr> Sent: Wednesday, October 24, 2018 4:29 AM To: xcat-user@lists.sourceforge.net Subject: [External] [xcat-user] Brand new systemimager (beta) Hi, I’m the main active developper for systemimager and saw some questions about it in this mailing list. 1st of all, the new systemimager has nothing to do with the old one regarding the imager which is now generated using dracut and has a GUI based on Plymouth (optional when running) See https://github.com/finley/SystemImager/wiki The quick start guide and screenshot sections are the only one that are up to date. You’ll notice that now, systemimager is able to deploy and run the os without a single reboot! The currently supported OS are RHEL/CentOS 6 and 7, Fedora 27, 28, Upcomming 29 and OpenSUSE 42.3 and newer. It could/should work on deb distros if I had time to do packaging and if dracut can be installed aside initramfstools without conflicts. It is planned and will work on all deb distros that have dracut and Plymouth package. I have no date for availability as it depends on my spare time. (Feel free to join if you have deb packaging and rpm spec knowledge to port it to Debian dir structure (mainly dependency helpers to port from rpm to deb)) Regards, — Olivier Lahaye
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
