You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
(28) |
Jun
(27) |
Jul
(27) |
Aug
(54) |
Sep
(72) |
Oct
(30) |
Nov
(9) |
Dec
(15) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(16) |
Feb
(44) |
Mar
(3) |
Apr
(23) |
May
(17) |
Jun
(95) |
Jul
(78) |
Aug
(57) |
Sep
(95) |
Oct
(75) |
Nov
(44) |
Dec
(54) |
2004 |
Jan
(141) |
Feb
(25) |
Mar
(39) |
Apr
(49) |
May
(17) |
Jun
(59) |
Jul
(26) |
Aug
(21) |
Sep
(12) |
Oct
(22) |
Nov
(8) |
Dec
(35) |
2005 |
Jan
(72) |
Feb
(28) |
Mar
(49) |
Apr
(27) |
May
(43) |
Jun
(21) |
Jul
(119) |
Aug
(15) |
Sep
(10) |
Oct
(11) |
Nov
(31) |
Dec
(162) |
2006 |
Jan
(82) |
Feb
(28) |
Mar
(97) |
Apr
(144) |
May
(96) |
Jun
(88) |
Jul
(131) |
Aug
(90) |
Sep
(59) |
Oct
(47) |
Nov
(48) |
Dec
(28) |
2007 |
Jan
(45) |
Feb
(71) |
Mar
(97) |
Apr
(49) |
May
(74) |
Jun
(33) |
Jul
(14) |
Aug
(74) |
Sep
(14) |
Oct
(59) |
Nov
(35) |
Dec
(59) |
2008 |
Jan
(6) |
Feb
(13) |
Mar
(1) |
Apr
(1) |
May
(9) |
Jun
(1) |
Jul
(14) |
Aug
(4) |
Sep
(4) |
Oct
|
Nov
(11) |
Dec
(1) |
2009 |
Jan
(10) |
Feb
(13) |
Mar
(4) |
Apr
(2) |
May
|
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(4) |
Nov
(6) |
Dec
(2) |
2010 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
|
2011 |
Jan
(4) |
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(8) |
2013 |
Jan
(7) |
Feb
(1) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
(5) |
Jun
(5) |
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
(2) |
2018 |
Jan
|
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
2020 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: LAHAYE O. <oli...@ce...> - 2022-06-23 20:53:06
|
Hi, RHEL-9 (thru AlmaLinux-9 build) support added. Packages available here: http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/rhel-9-x86_64 Quick Start Guide available here: https://github.com/finley/SystemImager/wiki/QuickStartGuide -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2022-06-20 07:37:52
|
Hi, Small notice to inform that New SystemImager builds are available. Now Debian builds are available here: http://olivier.lahaye1.free.fr/OSCAR/repos/ Quick start guide available here as usual: https://github.com/finley/SystemImager/wiki/QuickStartGuide Cheers, Olivier. -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2022-06-16 09:29:08
|
Hi, Small notice to inform that new SystemImager build has been made available for the following distributions: * AlmaLinux-8 (and all RHEL-8 compatible distros) * CentOS-7 * Debian-10 (amd64) * Debian-11 (amd64) * Open SuSE-15 As You can see, Debian is finally supported again. As usual, this is a “work in progress”. Rsync transfer method works fine and most command as well. The web interface replaces the old tk monitor interface, though the web console is ultra slow and needs rewrite (click wait response when the brower ask to stop waiting for the page rendering). It a take a few minutes. This problem will be fixed later. The repositories have moved here: http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/ The Quick Start Guide has been updated and is available here: https://github.com/finley/SystemImager/wiki/QuickStartGuide Happy deployments. -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2021-10-22 18:23:57
|
Hi, Small notice about SystemImager progress. After a long long time, Debian is back in supported distros! Debian 10 and 11 build are done. Debian 10 imager was tested successfully a few minutes ago. Debian 11 to be tested soon. A few glitches needs to be fixed, but Debian is definitely back. (Plymouth GUI not showing up (textmode ok), some locales missing, a few commands missing (dmidecode, …)) (As a consequence, OSCAR Cluster for Debian will be back again soon). Cheers, -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2021-09-29 15:49:16
|
Hi all, Small notice to tell that SystemImager-NG is still progressing. * Can be installed on UEFI system and imaged from UEFI PXE * Supports systemd-boot (basic stuff) * Make sure /etc/default/grub and /etc/system-id are specific to installed system * Supports for external drivers (e.g. megaraid_sas with old hardware support enabled) * Supports for initramfs with native NetworkManager (default since RHEL-8.3) * Had many bug fixes and imager code hardening. Packaging for RHEL-8 is now done using AlmaLinux-8 instead of CentOS-8 I’ll do some tests for CentOS-7, AlmaLinux-8, OpenSuse-13 and release rpms for RHEL-7 like, RHEL-8 like, SuSE-13 like. Packaging for Debian like is not ready, sorry, I have no time for that now. (though, there are chance that a make install DESTDIR=/usr may work somehow (don’t do that on something that is not a test system as result is unknown)) Regards, Olivier. -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2020-05-25 17:57:21
|
Hi every one, I hope all of you are fine during this Covid crisis. Development of the new SystemImager was not stopped, and after days of hacking, finding bugs in Plymouth and in distro packaging, I’ve finally succeeded in porting SystemImager (next gen) to CentOS-8.1 and to openSUSE-Leap 15.2) There is still lot of work before final stable release, but this release is already functional (I use it to deploy my CentOS-8 OSCAR Cluster). Reminder: this SystemImager supports: * CentOS-6 to CentOS-8.1, openSUSE Leap 12.2 (maybe other openSUSE and most Fedora distros) * UEFI Bios * UEFI grub2 installation (clover and reFind not yet supported but hooks in code are present) * All storage devices and filesystems supported by distro vendor * Raid, lvm, raid+lvm, … * No need for a main script (disk detection, partitioning, formatting, mounting, bootloader install, … is handled by SystemImager logic). Mainscript is still supported (if you want to setup a mountpoint, some nfs stuffs, or any other things not handled by SystemImager logic) * Web console * Imager graphical GUI based on plymouth * … Builds will be soon available here: http://www.usablesecurity.net/OSCAR/repos/unstable/ Quick start guide here: https://github.com/finley/SystemImager/wiki/QuickStartGuide Sorry, no up to date Debian/ubuntu packaging. SystemImager should be buildable for those distros provided dracut and dracut-network can be installed aside initramfs-tools (./configure; make install DESTDIR=/usr. WARNING, doing so will “pollute your system”, thouth other DESTDIR have not been tested and I doubt they are functional especially for web stuffs) but regarding packaging, a lot of work is still needed (mainly dependencies that needs to be backported) Happy testing. PS: if you rebuild your initrd, the result will not work on openSUSE-15.2: * dracut module 35network-legacy fails to run initqueue/online hook if network is brought up with dhcp: Imager fails in initqueue mainloop with timeout because online hook is never run. * PlymouthGUI won’t show up on qemu / bochs / … due to a bad openSUSE patch that tries to manage DRM devices while it shouldn’t anymore. -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2020-03-12 12:59:49
|
Hi, Small notice about systemimager (next gen) development status. Git tree is here: https://github.com/finley/SystemImager/tree/SystemImager-NG This version is based on dracut to generate the initrd imager, on Plymouth for a graphical install console and http for remote management (the web interface replaces remote X11 display for si_monitortk and other graphical tools) Current git tree have support for CentOS-6 to CentOS-8.0 (CentOS-8.1 soon (major changes in dracut-network)), openSUSE-42.3 and recent fedora (didn’t tested 32 and rawhide) Current status of the imager: * Plymouth console GUI doesn’t work anymore on CentOS-8.1 (SIGABRT). Need investigation * Dracut initqueue/online hook that start the main imaging process is not triggered by new 35network-manager module in CentOS-8.1. Fix already in dracut git and reported to CentOS team. My build system is patched as a temporary work around. * Log dispatcher fails to display messages on console on CentOS-8.1: need investigation. * Need to test rsync over ssh (in get and push) * Need to add reading ssh key from removable media * After stable release: need to add more xmit plugin for image deployment like bittorent, nfs, … Current status of the webgui: * Systemimager parameter configuration works fine * Systemimager diagnostic works fine * Systemimager client listing works fine * SystemImager client live console works but has big performances issues (need to migrate from web table to web grid objects) * SystemImager DHCP editor need to be written * SystemImager netbootmgr need to be written * SystemImager cluster editor need to be written * SystemImager web session need to be written * SystemImager web image management need to be written (maybe released after 1st stable as the si_getimage is working) Once I think we have a useable development version, I publish builds here: http://www.usablesecurity.net/OSCAR/repos/unstable/ For example, if you want to test CentOS-8 version: just do: Rpm -Uvh http://www.usablesecurity.net/OSCAR/repos/unstable/rhel-8-x86_64/oscar-release-6.1.3-0.20191216.el8.noarch.rpm Best regards, -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2019-12-19 18:58:13
|
Dear developers and curious testers, A new build of SystemImager is available for CentOS-6, CentOS-7, CentOS-8 and openSUSE-42 (build 20191219) Soon available here: http://www.usablesecurity.net/OSCAR/repos/unstable/ (Available for 7 days here: ftp://ftp.cea.fr/incoming/y2k01/OSCAR/repos/unstable/) This build has the new logging mechanism and a web interface with main menu, client list and web live console(s), system checks and systemimager configuration panel. Note: the 3 icons at bottom of the main menu are not yet implemented (stubs for now). The Quick start guide is updated and reflect current build. https://github.com/finley/SystemImager/wiki/QuickStartGuide Happy testing. -- Olivier LAHAYE CEA Saclay |
From: LAHAYE O. <oli...@ce...> - 2019-11-20 17:40:44
|
Hi, A Small notice about SystemImager v5 pre status: Development is still going well, though no release date yet. What’s new since last test builds. 1/ Support for CentOS-8 / RHEL-8 Added. 2/ WebGUI. A brand new web based GUI has been added: * Any modern browser (this excludes internet explorer and old edge browsers) can be used to manage SystemImager components. No more X-Display requirement! * It replaces si_monitortk (this tool was written in perl using perl-Tk for the user interface and was obsolete). * It lists all clients in real time with status update. * You can view install console in realtime or offline after installation. (multiple consoles can be seen at a time) * Thus: no more dependancies on perl-Tk, perl-TkTextANSIColor. * It replaces netbootmgr (this tool was written in perl using perl-Qt which doesn’t build on recent distros) * You’ll be able to choose local/network boot for each client. And in a near future, you should be able to edit systemimager options if I find an easy way to present this on a web page. * Thus: no more dependency on perl-Qt * DHCP configuration. * This will be a page where you’ll be able to configure some ISC DHCP options before configure file is generated by the server. (not yet designed). It’ll achieve similar goas as si_mkdhcpstatic with some smart guess and ability to append some DHCP “constants” that are not handled by SystemImager (switches, networked-kvm, ipmi, other servers, …) * Cluster editor: * A Page to help you create the cluster.txt file that defines cluster topology, client groups and associated images. This file is optional, but if present it is used by imager to chose image or scripts from groupname for example. * A health report page that will list running services, configuration problems, deployment statistics, available images, … * A Configuration page where you can configure most if not all SystemImager parameters (a replacement of /etc/systemimager/systemimager.conf with far more options) 3/ New logging mechanism that is able to grab system messages (you’ll see if a kernel module crashes) and stdout/stderr in pre/main/post-install scripts. Some screenshots of the web interface can be seen here: https://github.com/finley/SystemImager/wiki/QuickStartGuide Below, the new main menu: [cid:image001.png@01D59FD1.F668EB30] I’ll try to do a build in one or two weeks. Regards, Olivier. -- Olivier LAHAYE CEA Saclay |
From: LAHAYE O. <oli...@ce...> - 2019-10-10 17:24:01
|
SystemImager builds fine on CentOS-8 x86_64. (ntfs and btrfs not supported due to dropped support by RHEL-8) Now The live web console replacing si_monitortk is working fine. Filtering is also available to hide some less important logs like system messages, debug, details, notices, stderr or stdout in scripts. What needs to be done before a test build: * Web: client lists (easy) * Web: netbootmgr integration * Web: autoscroll console if last log line is visible * Web: session access code * Web: add systemimager-webgui packaging * Server: replace si_monitord with new monitord * Server event: stop push event if imaging is finished * Code cleanup. Note: tested ok on the following configs: Mac: safari Mac: chrome Windows: chrome Fails on Windows IE and Edge (no support for server event apparently) [cid:image001.png@01D57FA0.35F018C0] -- Olivier LAHAYE |
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 |
From: LAHAYE O. <oli...@ce...> - 2019-07-05 15:35:08
|
Hi, A new SystemImager build is available 4.9.0-0.20190705git See https://github.com/finley/SystemImager/wiki/QuickStartGuide for Installation and Migration guide from v4.1.6 and earlier. (make sure it is 20190705 build when installing; sometime, web cache show older build) Basically, new features are: * Now, SystemImager is able to configure network (man systemimager.network-config). If config file is missing, systemimager will just configure the PXE booted interface. * Fixed many small issues * Now imager log will list imager version, kernel version and distro flavor in logs. * Directboot now works fine on both centos-7 and centos-6. Happy testing. -- Olivier LAHAYE CEA Saclay |
From: LAHAYE O. <oli...@ce...> - 2019-07-04 07:28:06
|
Dear users and developers, SystemImager is in heavy development right now, but as I’m alone on this development, progress is slower than I wish. Some features are hard to maintain in term of OS compatibility and one of them is the remote console (using si_monitortk and clicking on a host being deployed) This console depends on an ANSI Color Tk text widget I need to package and that may not be maintained in the future. I also have a problem with refresh that hangs depending on netcat/nc/ncat versions that use different console switches. For now, the remote console has the following problems: * Can’t see the console log of a NATed client being imaged * Can’t see the console log if the client imaging is finished * Can’t see multiple consoles at a time * Can’t filter logs (select only errors or only warnings for example) * Logs stays on client and needs to be transferred by hand if one want to share it * Based on perl/Tk with depedancy to TkTermANSIColor that is not packaged in distros * Has problems with some ncat versions (nc, ncat multiple versions, netcat) (sockets timeout, hangs if input timeout (filesystem init too long, …) * Requires an X display to start si_monitortk * Requires to connect to image server to start si_monitortk IMHO, a really cool feature would be to add a web interface to image server with the following features: * Hosts statuses (si_monitortk main window replacement) * Console log (with page auto-refresh for update) * Info page with general setup * HTML Online Doc * PXE config * More? I think XSL and PHP would be the most timeline stable languages to create the web interface (other are constantly upgrading and obsoleting features and need port every 2 years or so with tons of libraries with v0.0.1 versions that die and become incompatible quickly) /var/lib/systemimager/clients.xml which contains the client informations is in xml format, thus xsl is well suited to transform it to HTML… Regarding the log storage daemon, I don’t know what would be the best, but as systemimagers is mainly based on perl and bash, I support perl would be the language of choice as bash would depend on nc/ncat/netcat that I want to avoid at any cost as behavior is inconsistent across distros and versions. What do you think? Ideas and/or help is welcome 😊 Cheers, Olivier. -- Olivier LAHAYE SystemImager v5 active developer. |
From: LAHAYE O. <oli...@ce...> - 2019-05-21 12:21:44
|
Hi, A new build has been released for centos-6 and centos-7. The new feature is that now, the network is setup by imaged from the network layout configuration file. This means that you don’t need a post-install script to setup the imaged client network. The quick start guide has been updated here: https://github.com/finley/SystemImager/wiki/QuickStartGuide Note: that the old repository has been replaced by a new one listed in the quick start guide. Happy testing. -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2019-04-05 15:19:50
|
Small update (4.9.0-0.20190405git.el7) with minor fixes. Peerdns and ipv6_peerdns have been moved from ip and ip6 tags to dns tag. The example file has been updated to reflexct this. Network configuration donc still to be written. Cmdline parameter for a specific config file: si.network-conf=<name>.xml SystemImager can guess file if name is the hostname, base hostname, imagename or groupname Example: https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/doc/examples/net-config.xml Format is still subject to change. To check validity of network configuration: si_lint –network-config=net-config.xml (don’t put full path; si_lint will look into /Var/lib/systemimager/scripts/network-configs/) si_lint is also able to validate disks-layout. (option --disks-layout=<name>.xml Regards, -- Olivier LAHAYE CEA Saclay |
From: LAHAYE O. <oli...@ce...> - 2019-04-02 15:40:43
|
Hi, Small message to inform the community that a new systemimager build (4.9.0-0.20190402git) introduce a major enhancement: the client network configuration. This configuration supports most common network usages: * Ipv4/ipv6 support (ipv6 support is basic) * Ethernet and Infiniband device support * Aliases support (still not loading on NetworkManager controlled interfaces) * Bonding support Doc not yet written but a fairly complete example is available here: https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/doc/examples/net-config.xml All available options are described here: https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/lib/dracut/modules.d/51systemimager/network-config.xsd Your network configuration file should be placed in /var/lib/systemimager/scripts/network-configs/ on the image server and be named in the same way disks layout (.xml extention is optional). (example: imagename.xml or hostname.xml or default.xml ….) To validate your network configuration (before trying to image your client) just type the following command (on the image server): si_lint –network-config=myimage.xml where myimage.xml is your network configuration file. (don’t provide full path) There are still issues with aliases and NetworkManager (not loaded), but aside that everything seems working. Happy testing. -- Olivier LAHAYE CID & ASSI - DRT Saclay |
From: LAHAYE O. <oli...@ce...> - 2019-03-21 16:41:59
|
Today build add a new server command: si_lint. This command aims to check the client configuration (disks layout, config file, ….) The aim is to check everything before trying to image a client and discover a client configuration problem. As of today, only disks layout check is available: si_lint --disks-layout=<layoutfile.xml> * Layout file is searched in /var/lib/systemimager/scripts/disks-layout/ or si_lint --disks-layout=*.xml * This will check all disks layout This new build also include preliminary support for imaged client network configuration (not enabled yet) This build is only available for centos7. (build for other systems will be done next week or so) The Quick start guide has also been updated. It is available here: https://github.com/finley/SystemImager/wiki/QuickStartGuide Happy testing. -- Olivier LAHAYE CEA Saclay |
From: LAHAYE O. <oli...@ce...> - 2019-03-20 18:11:24
|
Hi, A new systemimager build (4.9.0-0.20190320git.el7) is available for centos-7 / rhel-7 distro. Source: https://github.com/finley/SystemImager/tree/initrd-from-imageserver-and-dont-package-initrd Those who want to test can install it. See quick start guide here: https://github.com/finley/SystemImager/wiki/QuickStartGuide for download/install/setup/usage. New in this build (not sorted by importance): * Systemimager-client package. Now you can do si_prepareclient whitout needing to install systemimager-server * Systemimager-doc package is splitted from main package so you don’t have to install it on all your cluster nodes for example. This also reflect Debian packaging. * Debian package vailable but still incomplete (don’t use them yet) * More imager breakpoints (si systemimager.cmdline(7) manual) * systemimager-monitor-rebooted script is now installed by imager. Postinstall script is not needed anymore. * New bootloader section in disk-layout.xml file * See example here: https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/doc/examples/disk-layout-complex.xml * Bootloader is now installed as described in disk layout file (no more post install script required, only installed on designated disks) * Support for EFI bootloader added (rEFInd) * Disks-layout validation using xsd (a si_lint command (to be written) will help checking all systemimager configurations) * In the mean time you can check your disk layout file validity using the following command: * xmlstarlet val --err --xsd /usr/lib/dracut/modules.d/51systemimager/disks-layout.xsd /var/lib/systemimager/scripts/disks-layouts/<your disk layout.xml> * si_mkbootserver now supports systemd * si_mkbootserver now creates a GFX menu with cool systemimager background image (--vesamenu=y|n). (only available on systemd systems). * brand new very smart partitioning code with optimized aligment and sizes rounded to next aligment to avoid gaps between partitions. This smart partitioning is able to create ‘*’ sized partition between 2 fixed size partitions thans to xsl recursive processing. * Smart fstab generator. Line= parameter is ignored. * Enhanced partition flags (efi, PART spécific GUID (linux swap, EFI system partition, …)) * Many many many bugfixes thanks to David Livingstone patience and heavy testing. Now I’m working on the following stuffs: * Network configuration (xml file; example: https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/doc/examples/net-config.xml * Cleanup manuals. Move autoinstallscript.conf to systemimager.disks-layout for example * si_lint command to check if client is ready for installation (all configurations files are valid, …) * update bootloader section in disk layout file for better EFI options/configuration. * Finish Debian packaging (update file list, dependances and post install scripts) Happy testing. -- Olivier LAHAYE CEA Saclay |
From: LAHAYE O. <oli...@ce...> - 2018-11-28 17:22:37
|
Hi, Package for latest systemimager (v4.9.0) are available on OSCAR debian 8 repo here: http://svn.oscar.openclustergroup.org/repos/unstable/debian-8-x86_64/ There are untested yet and are likely not working well. (need to see if Dracut is not too much broken; fixed i18n broken module, but there may be others) The package content, the dependencies and most commands are working. What is untested is the initrd.img (the imager part) This is for thoses who are adventurous. Now working on Debian 9 packaging port. Then I’ll do tests. Cheers, -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2018-11-28 09:28:51
|
Debian packaging on its way! (built in docker container) Need to work on dependencies, but most stuffs are in place. === deb packages for systemimager === -rw-r--r-- 1 root root 61782546 Nov 28 09:21 /root/SystemImager/tmp/systemimager-boot-amd64-standard_4.9.0_all.deb -rw-r--r-- 1 root root 34844 Nov 28 09:20 /root/SystemImager/tmp/systemimager-client_4.9.0_all.deb -rw-r--r-- 1 root root 44436 Nov 28 09:20 /root/SystemImager/tmp/systemimager-common_4.9.0_all.deb -rw-r--r-- 1 root root 849970 Nov 28 09:20 /root/SystemImager/tmp/systemimager-doc_4.9.0_all.deb -rw-r--r-- 1 root root 16110 Nov 28 09:20 /root/SystemImager/tmp/systemimager-initrd-template_4.9.0_all.deb -rw-r--r-- 1 root root 18784 Nov 28 09:20 /root/SystemImager/tmp/systemimager-server-bittorrent_4.9.0_all.deb -rw-r--r-- 1 root root 14606 Nov 28 09:20 /root/SystemImager/tmp/systemimager-server-flamethrowerd_4.9.0_all.deb -rw-r--r-- 1 root root 174974 Nov 28 09:20 /root/SystemImager/tmp/systemimager-server_4.9.0_all.deb ===================================== -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2018-04-03 13:12:53
|
1st time in history: Install a system and run it without rebooting in between! Now, it is not needed to reboot anymore after having imaged a node. If imager (initramfs) is running a kernel that has it's modules in the image (same version), then we just finish booting (mount /sysroot and swap-root and finish boot process just like if we had booted from scratch). See SystemImager in action here: http://olivier.lahaye1.free.fr/SystemImager/Videos/20180403_SystemImager_directboot.webm Note: - This install is using lvm over software raid (partitions); a somewhat complex disk layout - The network error at the end is because I have a postinstall script that sets up an infiniband interface that is not present in my qemu VM (so this is expected). Aside that everything works perfectly (including standard network). Now backporting this feature to CentOS-6 (tested Ok on CentOS-7, should work on Fedora-27 and OpenSuSE-42.3 (will test later)) -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2018-03-22 08:48:29
|
I forgot to add few points. If you want to use a main install script (let say for setting IMAGENAME or POST_ACTION, the skeleton can be found in /etc/systemimager/autoinstallscript.template the most important thing is that it must contain the comment: # script_version:2 This is to avoid running old script with disk partitionning and other stuffs that couyld break systemimager dracut logic. A basic script can be: ----------8<----------8<----------8<----------8<----------8<----------8<---------- #!/bin/sh # script_version:2 # My sample script # . /lib/systemimager-lib.sh # load write_variables() function and some log message functions IMAGENAME=oscar_image loginfo "Set IMAGENAME=oscar_image" write_variables # updates /tmp/variables.txt with new IMAGENAME # end of main script ----------8<----------8<----------8<----------8<----------8<----------8<---------- For the cmdline parameters, here is what I'm using: si.image-server=10.0.1.1 si.config=testconfig.conf ramdisk_blocksize=1024 ramdisk_size=128000 acpi=no noapic ip=dhcp dns=10.0.1.1 rd.vconsole.keymap=fr vga=791 splash si.debug And my 10.0.1.1:/var/lib/systemimager/scripts/config/testconfig.conf file: ----------8<----------8<----------8<----------8<----------8<----------8<---------- MAGENAME=testimage MONITOR_SERVER=10.0.1.1 #MONITOR_PORT=8181 MONITOR_CONSOLE=yes SKIP_LOCAL_CFG=y DEBUG=yes # SCRIPTNAME=testimage.master # DL_PROTOCOL=rsync SIS_POST_ACTION=shell ----------8<----------8<----------8<----------8<----------8<----------8<---------- Menu entry in my /var/lib/tftpboot/pxelinux.cfg/default ----------8<----------8<----------8<----------8<----------8<----------8<---------- LABEL systemimager MENU LABEL ^S - Install a new Node KERNEL sis_kernel APPEND initrd=sis_initrd.img root=/dev/ram si.image-server=10.0.1.1 si.config=testconfig.conf ramdisk_blocksize=1024 ramdisk_size=128000 ip=dhcp dns=10.0.1.1 rd.vconsole.keymap=fr vga=791 splash acpi=no noapic ----------8<----------8<----------8<----------8<----------8<----------8<---------- -- Olivier LAHAYE CEA DRT/LIST/DIR ________________________________ De : LAHAYE Olivier Envoyé : mercredi 21 mars 2018 18:12 À : sis...@li...; sis...@li... Objet : [PROVENANCE INTERNET] [sisuite-users] SystemImager next generation BIG progress: CentOS-6 and Open SuSE-42.3 support! Systemimager is still progressing a lot! New change since last announce: - Support for CentOS-6 (finaly!) - Support for Open SuSE-42.3 - Support For CentOS-7 - Support for Fedora-27 - Install script is not mandatory any-more (big change). You can still add one though. deployment process is the following: pre-install / format disks / mount partitions / run main install script / download/install image / install overrides / create config (mdadm, lvm, fstab, initramfs, ...) / bootloader / post install - many cmdline parameters to control systemimager imaging process (no more option 140 DHCP parameters to configure (still supported)). parameters can be set at multiple places (DHCP, local.cfg, PXE-cmdline, /var/lib/systemimager/scripts/configs/<name>.conf) - disk layout is set in xml format and stored in /var/lib/systemimager/scripts/disks-layouts/<name>.xml this permits to have a single image deployed to different nodes with different disks. No more one image per disk layout. - Now protocols are splitted in dracut sub modules (systemimager-xmit) * For now, only rsync works. * Planned: systemimager-xmit-docker: build your image on a docker server (must be complete), install it on deployed hardware! systemimager-xmit-flamethrower systemimager-xmit-nfs: mount your image tree thru NFS and rsync locally from NFS mount point systemimager-xmit-rsync: as usual systemimager-xmit-ssh: using scp systemimager-xmit-template: a template file for adding more protocols systemimager-xmit-torrent: torrent deployment - SSH tunnel is not considered any-more a protocol for systemimager image deployment. SSH tunnel is something running aside like a network layer. It was used for rsync, but IMHO could also be used for other protocols like NFS, docker, ... - systemimager parameters (set as shell variables in local.cfg or /var/lib/systemimager/scripts/configs/<name>.conf or set as cmdline parameter in PXE) are the following: - si.debug / $DEBUG: values: y|n => Enable debug messages - si.config / $SIS_CONFIG: name of file containing config (uses less cmdline). File is stored in /var/lib/systemimager/scripts/configs/. Name is given without its PATH - si.image-name / $IMAGENAME: name of the image (looks for imagename|imagename.master) - si.script-name / $SCRIPTNAME: name of main script (looks for scriptname|scriptname.sh|scriptname.master) - si.disk-layout / $DISKS_LAYOUT: name of file containing disks layout in xml format (see man autoinstallscript.conf for now) (looks for filename|filename.xml) - si.dl-protocol / $DL_PROTOCOL: protocolname as seen in dracut module systemimager-xmit-<protocol name>.sh. defaults to rsync except if other parameter let think otherwise. - si.monitor-server / $MONITOR_SERVER: name or ip for monitor server - si.monitor-port / $MONITOR_PORT: monitor server port (defaults to 8181. min:100, max:32000) - si.monitor-console / $MONITOR_CONSOLE: y|n|0|1|yes|no (enable/disable log reported to monitor console) - si.skip-local-cfg / SKIP_LOCAL_CFG: y|n|0|1|yes|no (default:n) if yes, try to read local.cfg from old disks or floppy (USB planed of course but not yet implemented) - si.image-server / $IMAGESERVER: name or ip for the image server - si.log-server-port / $LOG_SERVER_PORT: the log server port (default is 514, min:100, max:32000) - si.ssh-client / $SSH: y|n|0|1|yes|no (dfault "n"). - si.ssh-download-url / $SSH_DOWNLOAD_URL: ssh download URL => sets DL_PROTOCOL to "ssh" - si.ssh-server / $SSHD: y|n|0|1|yes|no (enable / disable sshd access while imaging) (default "n") - si.flamethrower-directory-portbase: $FLAMETHROWER_DIRECTORY_PORTBASE: path - si.tmpfs-staging / $TMPFS_STAGING: path to staging dir. - si.term / $TERM: terminal type to use. defaults to "linux" - si.selinux-relabel / $SEL_RELABEL: y-n|0|1|yes|no: Request a SELinux files relabel after imaging disks - si.post-action / $SIS_POST_ACTION: what to do after imaging. defaults to reboot. Possible values: kexec, shell, reboot, shutdown, poweroff (and soon continue) continue will boot the imaged system without reboot. This is possible as initramfs is simply mounting OS filesystems in /sysroot and calls swaproot. We are in the same situatiuon after imaging. We only need to check that imaging kernel (uname -r) has modules available in /sysroot/lib/modules/$(uname -r)/, then we exit the dracut hook initqueue and dracut finishes the boot for us. - Parameters in DHCP are still possible and supported even in wickedd-dhcp4 dhcp client in SuSE distros. - option-140: IMAGESERVER - option-141: LOG_SERVER_PORT - option-142: SSH_DOWNLOAD_URL - option-143: FLAMETHROWER_DIRECTORY_PORTBASE - option-144: TMPFS_STAGING IMPORTANT: - si_mkautoinstallscript is DEPRECATED and shouldn't be used (useless though) - disk layout has changed. main scripts are now stored in /var/lib/systemimager/scripts/main-install (not /var/lib/systemimager/scripts) This looks like: /var/lib/systemimager/scripts/cluster.txt # created by si_clusterconfig from /etc/systemimager/cluster.xml /var/lib/systemimager/scripts/configs/*.conf /var/lib/systemimager/scripts/disks-layouts/*.xml /var/lib/systemimager/scripts/hosts /var/lib/systemimager/scripts/main-install/*.{,sh,master} /var/lib/systemimager/scripts/post-install/*.sh /var/lib/systemimager/scripts/pre-install/*.sh Packages should be released soon for testing for the 4 distros annouced. Next: - support for continueboot after imaging - *.deb packaging (hopefully if I don't hit dracut conflict with initramfs, seems fixed by now) (need a lot of work (major package rewrite and need to compute deps for all perl (automatic for rpm)) All stuffs in initrd-from-imageserver-and-dont-package-initrd form systemimager git how to build yourself: git clone -b initrd-from-imageserver-and-dont-package-initrd https://github.com/finley/SystemImager.git cd systemImager make source_tarball rpmbuild -tb tmp/systemimager-4.5.0.tar.gz yum|dnf|zypper install <list of built package except flamethrower and bittorrent one> Happy testing. PS: Please report any issues. -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2018-03-21 17:13:02
|
Systemimager is still progressing a lot! New change since last announce: - Support for CentOS-6 (finaly!) - Support for Open SuSE-42.3 - Support For CentOS-7 - Support for Fedora-27 - Install script is not mandatory any-more (big change). You can still add one though. deployment process is the following: pre-install / format disks / mount partitions / run main install script / download/install image / install overrides / create config (mdadm, lvm, fstab, initramfs, ...) / bootloader / post install - many cmdline parameters to control systemimager imaging process (no more option 140 DHCP parameters to configure (still supported)). parameters can be set at multiple places (DHCP, local.cfg, PXE-cmdline, /var/lib/systemimager/scripts/configs/<name>.conf) - disk layout is set in xml format and stored in /var/lib/systemimager/scripts/disks-layouts/<name>.xml this permits to have a single image deployed to different nodes with different disks. No more one image per disk layout. - Now protocols are splitted in dracut sub modules (systemimager-xmit) * For now, only rsync works. * Planned: systemimager-xmit-docker: build your image on a docker server (must be complete), install it on deployed hardware! systemimager-xmit-flamethrower systemimager-xmit-nfs: mount your image tree thru NFS and rsync locally from NFS mount point systemimager-xmit-rsync: as usual systemimager-xmit-ssh: using scp systemimager-xmit-template: a template file for adding more protocols systemimager-xmit-torrent: torrent deployment - SSH tunnel is not considered any-more a protocol for systemimager image deployment. SSH tunnel is something running aside like a network layer. It was used for rsync, but IMHO could also be used for other protocols like NFS, docker, ... - systemimager parameters (set as shell variables in local.cfg or /var/lib/systemimager/scripts/configs/<name>.conf or set as cmdline parameter in PXE) are the following: - si.debug / $DEBUG: values: y|n => Enable debug messages - si.config / $SIS_CONFIG: name of file containing config (uses less cmdline). File is stored in /var/lib/systemimager/scripts/configs/. Name is given without its PATH - si.image-name / $IMAGENAME: name of the image (looks for imagename|imagename.master) - si.script-name / $SCRIPTNAME: name of main script (looks for scriptname|scriptname.sh|scriptname.master) - si.disk-layout / $DISKS_LAYOUT: name of file containing disks layout in xml format (see man autoinstallscript.conf for now) (looks for filename|filename.xml) - si.dl-protocol / $DL_PROTOCOL: protocolname as seen in dracut module systemimager-xmit-<protocol name>.sh. defaults to rsync except if other parameter let think otherwise. - si.monitor-server / $MONITOR_SERVER: name or ip for monitor server - si.monitor-port / $MONITOR_PORT: monitor server port (defaults to 8181. min:100, max:32000) - si.monitor-console / $MONITOR_CONSOLE: y|n|0|1|yes|no (enable/disable log reported to monitor console) - si.skip-local-cfg / SKIP_LOCAL_CFG: y|n|0|1|yes|no (default:n) if yes, try to read local.cfg from old disks or floppy (USB planed of course but not yet implemented) - si.image-server / $IMAGESERVER: name or ip for the image server - si.log-server-port / $LOG_SERVER_PORT: the log server port (default is 514, min:100, max:32000) - si.ssh-client / $SSH: y|n|0|1|yes|no (dfault "n"). - si.ssh-download-url / $SSH_DOWNLOAD_URL: ssh download URL => sets DL_PROTOCOL to "ssh" - si.ssh-server / $SSHD: y|n|0|1|yes|no (enable / disable sshd access while imaging) (default "n") - si.flamethrower-directory-portbase: $FLAMETHROWER_DIRECTORY_PORTBASE: path - si.tmpfs-staging / $TMPFS_STAGING: path to staging dir. - si.term / $TERM: terminal type to use. defaults to "linux" - si.selinux-relabel / $SEL_RELABEL: y-n|0|1|yes|no: Request a SELinux files relabel after imaging disks - si.post-action / $SIS_POST_ACTION: what to do after imaging. defaults to reboot. Possible values: kexec, shell, reboot, shutdown, poweroff (and soon continue) continue will boot the imaged system without reboot. This is possible as initramfs is simply mounting OS filesystems in /sysroot and calls swaproot. We are in the same situatiuon after imaging. We only need to check that imaging kernel (uname -r) has modules available in /sysroot/lib/modules/$(uname -r)/, then we exit the dracut hook initqueue and dracut finishes the boot for us. - Parameters in DHCP are still possible and supported even in wickedd-dhcp4 dhcp client in SuSE distros. - option-140: IMAGESERVER - option-141: LOG_SERVER_PORT - option-142: SSH_DOWNLOAD_URL - option-143: FLAMETHROWER_DIRECTORY_PORTBASE - option-144: TMPFS_STAGING IMPORTANT: - si_mkautoinstallscript is DEPRECATED and shouldn't be used (useless though) - disk layout has changed. main scripts are now stored in /var/lib/systemimager/scripts/main-install (not /var/lib/systemimager/scripts) This looks like: /var/lib/systemimager/scripts/cluster.txt # created by si_clusterconfig from /etc/systemimager/cluster.xml /var/lib/systemimager/scripts/configs/*.conf /var/lib/systemimager/scripts/disks-layouts/*.xml /var/lib/systemimager/scripts/hosts /var/lib/systemimager/scripts/main-install/*.{,sh,master} /var/lib/systemimager/scripts/post-install/*.sh /var/lib/systemimager/scripts/pre-install/*.sh Packages should be released soon for testing for the 4 distros annouced. Next: - support for continueboot after imaging - *.deb packaging (hopefully if I don't hit dracut conflict with initramfs, seems fixed by now) (need a lot of work (major package rewrite and need to compute deps for all perl (automatic for rpm)) All stuffs in initrd-from-imageserver-and-dont-package-initrd form systemimager git how to build yourself: git clone -b initrd-from-imageserver-and-dont-package-initrd https://github.com/finley/SystemImager.git cd systemImager make source_tarball rpmbuild -tb tmp/systemimager-4.5.0.tar.gz yum|dnf|zypper install <list of built package except flamethrower and bittorrent one> Happy testing. PS: Please report any issues. -- Olivier LAHAYE |
From: LAHAYE O. <oli...@ce...> - 2018-02-08 18:52:13
|
Dear all, systemimager is still progressing a lot. 1/ now, installscript is not responsible anymore to create the filesystems raids, lvm and such. An simple autoinstallscript.conf file named <imagename|hostname|scriptname>.xml located in/var/lib/systemimager/disks-layouts/ will give description of what you want to the dracut logic. This means that you can have a single image deployed to multiple nodes with different disks. 2/ now, installscript is not responsible anymore to install the image. The logic is in dracut module. The script is ran after disks are initialized but before image is laid down to disk. then the post install scripts are ran. This permit to mount some extra stufs for example that are not in disk layout xml file. This main script will become optional. Minimum requirement will be disk layout and image. Often post install will be used. Pre-install and main install will be used rarely IMHO. /var/lib/systemimager will be lifted to be more clean. It will become: - /var/lib/systemimager/<something>/hosts - /var/lib/systemimager/<something>/pre-install - /var/lib/systemimager/<something>/main-install - /var/lib/systemimager/<something>/post-install - /var/lib/systemimager/<something>/disks-layouts something is now called scripts, but it's more than that so it'll change for something more concistent. Expect a working release in less than a month. -- Olivier LAHAYE CEA DRT/LIST/DIR |
From: LAHAYE O. <oli...@ce...> - 2018-02-01 16:48:34
|
Now autoinstallscript.conf (disk layout/raid/lvm/mounts) will not be stored in <image_dir>:/etc/systemimager/autoinstallscript.conf This will allow to have the same image used for nodes with different disks. The file will be parsed and processed during install before running main install script (using xmlstarlet from within dracut logic). Partitionning code: finished raid volumes creation code: finished lvm creation code: not yet done (a matter of days) mount filesystems code: not yet done (a matter of days) Chronology should be (once network is up in the initramfs booting) - run préinstall scripts - prepare disk and mount it - run autoinstall main script - run post install scripts Not yet sure but main script may disapear and be replaced with some dracut logic (init transfert protocol, download and extract if needed the image) - user: pre install will let the user manipulate disks before it is touched and maybe do some other stuffs - dracut: disk are then processed as described in the autoinstallscript.conf (will have a better name) and mounted - dracut: transfert protocol is initialised - dracut: image is downloaded and extracted if needed - dracut: network config is setup in the image (not yet working and maybe done before postinstall? not yet decided. For now I'm using postinstall script for that) - user: postinstall scripts are run - dracut: bootloader is installed - dracut: end action (shell, reboot, wait, beep, ...) (continue boot without rebooting should even be possible if modules for running kernel (the one used for imaging) are present in the imaged disk (/sysroot/lib/modules/$(uname -r)/ is present) Cheers, -- Olivier LAHAYE CEA DRT/LIST/DIR |