Re: [sisuite-users] RE : RE : support newer kernels in systemimager?

2014-06-06 Thread David Livingstone 
Olivier - Just getting back into this ... are these the latest ?
Thanks

From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr]
Sent: Friday, January 24, 2014 4:21 AM
To: sisuite-users@lists.sourceforge.net
Subject: [sisuite-users] RE : RE : support newer kernels in systemimager?


Hi David, thanks a lot for your support :-)

The latest beta packages are versionned with 4.3.0-0.16. This releases now 
builds with perl files installed in INSTALDIRS=vendor (no more use lib 
/usr/lib/systemimager needed).
This version includes the si_monitortk thread warning fix.
It is available here: http://svn.oscar.openclustergroup.org/repos/unstable/

The package has been built for rhel-6, debian-6, fedora-17

For the future, as I said, I'm looking forward for any info/doc/script on how 
to build such a thing:
http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : David Livingstone [david.livingst...@cn.ca]
Date d'envoi : jeudi 23 janvier 2014 21:24
À : 
sisuite-users@lists.sourceforge.net<mailto:sisuite-users@lists.sourceforge.net>
Objet : Re: [sisuite-users] RE : support newer kernels in systemimager?
Olivier - 2. Definitely sounds like the way to go ...

From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr]
Sent: Thursday, January 23, 2014 3:00 AM
To: 
sisuite-users@lists.sourceforge.net<mailto:sisuite-users@lists.sourceforge.net>
Subject: [sisuite-users] RE : support newer kernels in systemimager?

Hi,

Sorry for not participating often here, I'm extremely buzy working on releasing 
a new stable OSCAR cluster release that will support many distros.

Though, I'm still working on SystemImager. (just fixed si_monitortk thread 
warning)

The current git should support kernels from 2.4 to 3.99 if it ever exists.
We have built beta release here:
http://svn.oscar.openclustergroup.org/repos/unstable/

For more info, here is my analysis of the current situation and what I'd like 
to achieve:

Problem of the current release is that it fails to build template initrd and 
kernel on newer distros (like fedora-18+). The problem is that template initrd 
is based on udev when newer kernels needs latest udev version and build 
mechanism is not yet designed to build udev without systemd from systemd source 
tree.

IMHO, the way to generate templates is not compatible anymore with the variety 
of distros and kernel version. rhel6 is using a 2.6, while other distros are 
using kernel 3.x
Building latest kernel and lvm on an old system (rhel6) using installed system 
kernel includes leads to build failures or runtime crash.

2 solutions for the future:

1/ have different build tree for each distro with apropriate kernel => means 
old distro won't be supported on recent hardware . typically, our vanilla 
kernel-2.6 supports far less hardware that patched rhel-6 shipped kernel. => 
bad idea and very difficult to maintain.

2/ drop the idea to build our kernel and initrd from scratch and instead build 
the initrd using dracut. Big benefits:
   a/ we support the same hardware as the linux vendor. even with old kernel.
   b/ building the rpm is far more faster
   c/ far more stable. no more lvm built for kernel 3.10 using kernel 2.6 build 
host system includes.
UYOK would still be possible for users having hardware that is not supported by 
their linux vendor, but for the majority of cases, the templates would be far 
sufficient.

Unfortunately, I'm still searching a doc that tells how to build a non basic 
initrd.
Our case is similar to 
http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img

=> If someone can point me to a page that explains how this image is built, 
that would be AWESOME.

It uses systemd and udev for loading hardware drivers and minimal services like 
network and so. Basicaly it havs everything we need.
Then we would just have to add needed binaries (lvm tools, ...) from installed 
system and (build)our specific stuffs like flamethrower client or bittorent 
client and replace stage2 loader with our rcS and voila! (cleaner, faster, 
higher ...;- )

Best regards.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : Jan Groenewald [j...@aims.ac.za]
Date d'envoi : lundi 20 janvier 2014 07:38
À : 
sisuite-users@lists.sourceforge.net<mailto:sisuite-users@lists.sourceforge.net>
Objet : Re: [sisuite-users] support newer kernels in systemimager?
Hi
This file

0 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#dpkg -S 
UseYourOwnKernel.pm
systemimager-common: /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm
Checks the kernel version and throws an error for newer kernels. This patch 
allows me to use some 3.X kernels

1 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#cat 
UseYourOwnKernel.pm.patch

Re: [sisuite-users] RE : RE : support newer kernels in systemimager?

2014-01-24 Thread David Livingstone 
Olivier - Thanks ! I will download and give it a try. Please keep me in the 
loop. BTW I am off to Red Hat Summit this year in San Francisco ...

David

From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr]
Sent: Friday, January 24, 2014 4:21 AM
To: sisuite-users@lists.sourceforge.net
Subject: [sisuite-users] RE : RE : support newer kernels in systemimager?


Hi David, thanks a lot for your support :-)

The latest beta packages are versionned with 4.3.0-0.16. This releases now 
builds with perl files installed in INSTALDIRS=vendor (no more use lib 
/usr/lib/systemimager needed).
This version includes the si_monitortk thread warning fix.
It is available here: http://svn.oscar.openclustergroup.org/repos/unstable/

The package has been built for rhel-6, debian-6, fedora-17

For the future, as I said, I'm looking forward for any info/doc/script on how 
to build such a thing:
http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : David Livingstone [david.livingst...@cn.ca]
Date d'envoi : jeudi 23 janvier 2014 21:24
À : 
sisuite-users@lists.sourceforge.net<mailto:sisuite-users@lists.sourceforge.net>
Objet : Re: [sisuite-users] RE : support newer kernels in systemimager?
Olivier - 2. Definitely sounds like the way to go ...

From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr]
Sent: Thursday, January 23, 2014 3:00 AM
To: 
sisuite-users@lists.sourceforge.net<mailto:sisuite-users@lists.sourceforge.net>
Subject: [sisuite-users] RE : support newer kernels in systemimager?

Hi,

Sorry for not participating often here, I'm extremely buzy working on releasing 
a new stable OSCAR cluster release that will support many distros.

Though, I'm still working on SystemImager. (just fixed si_monitortk thread 
warning)

The current git should support kernels from 2.4 to 3.99 if it ever exists.
We have built beta release here:
http://svn.oscar.openclustergroup.org/repos/unstable/

For more info, here is my analysis of the current situation and what I'd like 
to achieve:

Problem of the current release is that it fails to build template initrd and 
kernel on newer distros (like fedora-18+). The problem is that template initrd 
is based on udev when newer kernels needs latest udev version and build 
mechanism is not yet designed to build udev without systemd from systemd source 
tree.

IMHO, the way to generate templates is not compatible anymore with the variety 
of distros and kernel version. rhel6 is using a 2.6, while other distros are 
using kernel 3.x
Building latest kernel and lvm on an old system (rhel6) using installed system 
kernel includes leads to build failures or runtime crash.

2 solutions for the future:

1/ have different build tree for each distro with apropriate kernel => means 
old distro won't be supported on recent hardware . typically, our vanilla 
kernel-2.6 supports far less hardware that patched rhel-6 shipped kernel. => 
bad idea and very difficult to maintain.

2/ drop the idea to build our kernel and initrd from scratch and instead build 
the initrd using dracut. Big benefits:
   a/ we support the same hardware as the linux vendor. even with old kernel.
   b/ building the rpm is far more faster
   c/ far more stable. no more lvm built for kernel 3.10 using kernel 2.6 build 
host system includes.
UYOK would still be possible for users having hardware that is not supported by 
their linux vendor, but for the majority of cases, the templates would be far 
sufficient.

Unfortunately, I'm still searching a doc that tells how to build a non basic 
initrd.
Our case is similar to 
http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img

=> If someone can point me to a page that explains how this image is built, 
that would be AWESOME.

It uses systemd and udev for loading hardware drivers and minimal services like 
network and so. Basicaly it havs everything we need.
Then we would just have to add needed binaries (lvm tools, ...) from installed 
system and (build)our specific stuffs like flamethrower client or bittorent 
client and replace stage2 loader with our rcS and voila! (cleaner, faster, 
higher ...;- )

Best regards.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : Jan Groenewald [j...@aims.ac.za]
Date d'envoi : lundi 20 janvier 2014 07:38
À : 
sisuite-users@lists.sourceforge.net<mailto:sisuite-users@lists.sourceforge.net>
Objet : Re: [sisuite-users] support newer kernels in systemimager?
Hi
This file

0 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#dpkg -S 
UseYourOwnKernel.pm
systemimager-common: /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm
Checks the kernel version and throws an error for newer kernels. This patch 
allows me to use some 3.X ker

[sisuite-users] RE : RE : support newer kernels in systemimager?

2014-01-24 Thread LAHAYE Olivier 

Hi David, thanks a lot for your support :-)

The latest beta packages are versionned with 4.3.0-0.16. This releases now 
builds with perl files installed in INSTALDIRS=vendor (no more use lib 
/usr/lib/systemimager needed).
This version includes the si_monitortk thread warning fix.
It is available here: http://svn.oscar.openclustergroup.org/repos/unstable/

The package has been built for rhel-6, debian-6, fedora-17

For the future, as I said, I'm looking forward for any info/doc/script on how 
to build such a thing:
http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : David Livingstone [david.livingst...@cn.ca]
Date d'envoi : jeudi 23 janvier 2014 21:24
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] RE : support newer kernels in systemimager?

Olivier – 2. Definitely sounds like the way to go …

From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr]
Sent: Thursday, January 23, 2014 3:00 AM
To: sisuite-users@lists.sourceforge.net
Subject: [sisuite-users] RE : support newer kernels in systemimager?

Hi,

Sorry for not participating often here, I'm extremely buzy working on releasing 
a new stable OSCAR cluster release that will support many distros.

Though, I'm still working on SystemImager. (just fixed si_monitortk thread 
warning)

The current git should support kernels from 2.4 to 3.99 if it ever exists.
We have built beta release here:
http://svn.oscar.openclustergroup.org/repos/unstable/

For more info, here is my analysis of the current situation and what I'd like 
to achieve:

Problem of the current release is that it fails to build template initrd and 
kernel on newer distros (like fedora-18+). The problem is that template initrd 
is based on udev when newer kernels needs latest udev version and build 
mechanism is not yet designed to build udev without systemd from systemd source 
tree.

IMHO, the way to generate templates is not compatible anymore with the variety 
of distros and kernel version. rhel6 is using a 2.6, while other distros are 
using kernel 3.x
Building latest kernel and lvm on an old system (rhel6) using installed system 
kernel includes leads to build failures or runtime crash.

2 solutions for the future:

1/ have different build tree for each distro with apropriate kernel => means 
old distro won't be supported on recent hardware . typically, our vanilla 
kernel-2.6 supports far less hardware that patched rhel-6 shipped kernel. => 
bad idea and very difficult to maintain.

2/ drop the idea to build our kernel and initrd from scratch and instead build 
the initrd using dracut. Big benefits:
   a/ we support the same hardware as the linux vendor. even with old kernel.
   b/ building the rpm is far more faster
   c/ far more stable. no more lvm built for kernel 3.10 using kernel 2.6 build 
host system includes.
UYOK would still be possible for users having hardware that is not supported by 
their linux vendor, but for the majority of cases, the templates would be far 
sufficient.

Unfortunately, I'm still searching a doc that tells how to build a non basic 
initrd.
Our case is similar to 
http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img

=> If someone can point me to a page that explains how this image is built, 
that would be AWESOME.

It uses systemd and udev for loading hardware drivers and minimal services like 
network and so. Basicaly it havs everything we need.
Then we would just have to add needed binaries (lvm tools, ...) from installed 
system and (build)our specific stuffs like flamethrower client or bittorent 
client and replace stage2 loader with our rcS and voila! (cleaner, faster, 
higher ...;- )

Best regards.

--
   Olivier LAHAYE
   CEA DRT/LIST/DIR

De : Jan Groenewald [j...@aims.ac.za]
Date d'envoi : lundi 20 janvier 2014 07:38
À : 
sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] support newer kernels in systemimager?
Hi
This file

0 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#dpkg -S 
UseYourOwnKernel.pm
systemimager-common: /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm
Checks the kernel version and throws an error for newer kernels. This patch 
allows me to use some 3.X kernels

1 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#cat 
UseYourOwnKernel.pm.patch
--- UseYourOwnKernel.pm.orig2012-05-30 17:05:54.899344781 +0200
+++ UseYourOwnKernel.pm 2013-02-18 08:30:56.251862480 +0200
@@ -460,11 +460,12 @@
 #   2.4.19-mantis-2002.11.20 (root@mantis) #6 Tue Nov 19 
15:15:43 CST 2002
 #   2.6.7-1-686 
(dilin...@toaster.hq.voxel.net) #1 Thu 
Jul 8 05:36:53 EDT 2004
 #   2.6.22.5-31-default (geeko@build