You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(9) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(10) |
Feb
(2) |
Mar
(3) |
Apr
(2) |
May
(3) |
Jun
(50) |
Jul
(41) |
Aug
(76) |
Sep
(125) |
Oct
(83) |
Nov
(89) |
Dec
(32) |
2004 |
Jan
(78) |
Feb
(82) |
Mar
(129) |
Apr
(72) |
May
(110) |
Jun
(70) |
Jul
(76) |
Aug
(64) |
Sep
(41) |
Oct
(51) |
Nov
(36) |
Dec
(34) |
2005 |
Jan
(77) |
Feb
(57) |
Mar
(38) |
Apr
(26) |
May
(55) |
Jun
(68) |
Jul
(99) |
Aug
(80) |
Sep
(82) |
Oct
(141) |
Nov
(137) |
Dec
(51) |
2006 |
Jan
(133) |
Feb
(33) |
Mar
(156) |
Apr
(104) |
May
(88) |
Jun
(128) |
Jul
(110) |
Aug
(129) |
Sep
(74) |
Oct
(144) |
Nov
(127) |
Dec
(51) |
2007 |
Jan
(140) |
Feb
(140) |
Mar
(100) |
Apr
(42) |
May
(34) |
Jun
(13) |
Jul
(46) |
Aug
(46) |
Sep
(46) |
Oct
(42) |
Nov
(125) |
Dec
(23) |
2008 |
Jan
(15) |
Feb
(77) |
Mar
(57) |
Apr
(68) |
May
(48) |
Jun
(22) |
Jul
(54) |
Aug
(83) |
Sep
(41) |
Oct
(8) |
Nov
(37) |
Dec
(47) |
2009 |
Jan
(13) |
Feb
(11) |
Mar
(14) |
Apr
(55) |
May
(31) |
Jun
(18) |
Jul
(27) |
Aug
(17) |
Sep
(13) |
Oct
(39) |
Nov
(21) |
Dec
(16) |
2010 |
Jan
(10) |
Feb
(5) |
Mar
(15) |
Apr
(4) |
May
(9) |
Jun
(7) |
Jul
(20) |
Aug
(35) |
Sep
(37) |
Oct
(6) |
Nov
(12) |
Dec
(7) |
2011 |
Jan
(9) |
Feb
(6) |
Mar
(9) |
Apr
(78) |
May
(13) |
Jun
(6) |
Jul
(29) |
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(5) |
Dec
(12) |
2012 |
Jan
(1) |
Feb
(24) |
Mar
(12) |
Apr
(7) |
May
(12) |
Jun
(19) |
Jul
(8) |
Aug
(2) |
Sep
|
Oct
|
Nov
(35) |
Dec
(30) |
2013 |
Jan
(11) |
Feb
(13) |
Mar
(15) |
Apr
(18) |
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(2) |
2014 |
Jan
(23) |
Feb
(4) |
Mar
(11) |
Apr
(1) |
May
|
Jun
(1) |
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
(6) |
Feb
|
Mar
|
Apr
(1) |
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(2) |
Jun
(7) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
(3) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(2) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
(6) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(4) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(6) |
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: <dav...@cn...> - 2013-01-16 22:38:46
|
Olivier, Thanks. So far I have installed the rpm's on a dl380G7 with rhel6.3 x86_64 and both prepared the image(uyok) and retrieved from a similar server with the server packages loaded.Next step will be to test load the image on another server using both the standard and uyok ( I'm a little gun shy tryingto load back to the same server incase there are problems). I also re-applied the changes I've itemized below for the same reasons - btw the change below to rcS(start udev BEFORE load_my_modules) might address why you had similar problems ie needing the pre-install script to load the modules). - David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: Dav...@cn... From: LAHAYE Olivier <oli...@ce...> To: "sis...@li..." <sis...@li...> Date: 2013/01/07 02:05 Subject: [sisuite-users] RE : Which version ? Hi, You can try the 4.3.0-0.1svn version, it worked for me. You'll need pre and post-install scripts available here: http://olivier.lahaye1.free.fr/RPMS/extra/ Cheers, -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR De : dav...@cn... [dav...@cn...] Date d'envoi : mercredi 19 décembre 2012 00:09 À : sis...@li... Objet : [sisuite-users] Which version ? I have been using a modified version of 4.1.99.svn4556_bli-1 to load my i386 rhel6.x servers as described below. I am now looking at imaging similar machines but now with the x86_64 version of rhel6.3 so I need like initrd_template( and boot_standard if it works) packages. What versions should I be trying ? http://olivier.lahaye1.free.fr/RPMS/noarch/ ?? Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: Dav...@cn... ----- Forwarded by David Livingstone/LIVING03/CNR/CA on 2012/12/18 16:00 ----- From: David Livingstone/LIVING03/CNR/CA To: sis...@li... Date: 2012/03/29 09:41 Subject: Loading RHEL 6.2 using 4.1.99.svn4556_bli-1 Using systemimager 4.1.99.svn4556_bli-1(ext4 enabled version) I have successfully imaged a RHEL 6.2 image to HP DL380G7 hardware(p410 array controllers). I was considering using SALI however for RHEL6.x grub2 is not an issue and ext4 support is included in 4.1.99.svn4556_bli-1. The setup I was imaging is a Proliant DL380G7 server with two p410 controllers(p401i and p410) with raid1 for root/boot/swap on the p410i and raid5 for /data on the p410. The system is running the latest RHEL 6.2. The attempted to image the system in two ways: 1. standard kernel 2. uyok 1. standard kernel I eventually got this to work but only after major modifications to the install script and manually setting up grub. The major issue here is that the default kernel uses the cciss driver and device naming(ex /dev/cciss/c0d0p2) and the RHEL6.x uses the hpsa driver(scsi naming ex /dev/sda). See http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02677069/c02677069.pdf . In general RHEL 5.x and before uses the cciss driver and RHEL6.x uses the hpsa when possible. I presume the standard kernel could be built with the hpsa module and some version logic applied to resolve this. 2. uyok This worked successfully after making some changes to address : - Needed modules(ie hpsa) as symbolic links under /lib/modules/(uname -r) ex [root@scdev ~]# ls -al /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko 0 lrwxrwxrwx 1 root root 50 Mar 5 04:05 /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko -> /lib/modules/2.6.32-71.el6.i686/extra/hpsa/hpsa.ko [root@scdev ~]# This results in the modules not being copied correctly in the generated initrd. I resolved this by modifying the UseYourOwnKernel.pm rsync invocations to copy the resultant files(the L rather then the l option. I include the diff below. - Numerous /lib/firmware files were missing in the initrd. By default the bnx2 nic driver(driver for the four nic's on the motherboard) as well as others in the RHEL6.2 kernel request firmware which is missing in the uyok initrd. I got this to work by : - modifying UseYourOwnKernel.pm to copy /lib/firmware to the initrd. Unfortunately this copies all of firmware as I couldn't figure out how to dynamically copy what was needed. - modified rcS under the std template to start udev BEFORE the modules are inserted. - rcS : start udev before loading modules. - under the std template : /usr/share/systemimager/boot/i386/standard/initrd_template/etc/init.d/rcS - The ramdisk_size must be set high enough to accept the larger initrd. - I had to si_cpimage as part of testing and noted that for yuok the kernel and initrd.img files are not copied. They had to be copied manually. Notes : When creating the image initially I also had to change si_prepareclient to use parted rather then sfdisk. I believe a bug was submitted on this a long time ago which was never applied. parted supports gpt partitions and sfdisk does not. [root@nasmtl sbin]# diff si_prepareclient si_prepareclient.orig.4.1.99.svn4556_bli 969,971c969,971 < # if($arch eq "i386") { < # $preferred_tool = 'sfdisk'; < # } --- > if($arch eq "i386") { > $preferred_tool = 'sfdisk'; > } - Diff for UseYourOwnKernel.pm [root@nasmtl SystemImager]# diff UseYourOwnKernel.pm UseYourOwnKernel.pm.orig 152c152 < $cmd = qq(rsync -aL --exclude=build --exclude=source ) . --- > $cmd = qq(rsync -a --exclude=build --exclude=source ) . 159c159 < $cmd = qq(rsync -aLR $module $staging_dir); --- > $cmd = qq(rsync -aR $module $staging_dir); 223,225d222 < # < # Copy /lib/firmware file to initrd < # 227,233d223 < if (-d "/lib/firmware") { < # copy entire firmware tree to new initrd. < $cmd = qq(rsync -aLR /lib/firmware $staging_dir); < !system( $cmd ) or die( "Couldn't $cmd." ); < < } < - Diff for rcS : [root@nasmtl init.d]# diff rcS rcS.orig 45,47d44 < # Start udev BEFORE load_my_modules so the modules can load firmware if needed. < start_udevd < 49a47,48 > start_udevd > David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: Dav...@cn... ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 _______________________________________________ sisuite-users mailing list sis...@li... https://lists.sourceforge.net/lists/listinfo/sisuite-users |
From: LAHAYE O. <oli...@ce...> - 2013-01-15 12:29:32
|
Hi Ole, I think that this is fixed now in http://olivier.lahaye1.free.fr/RPMS/noarch/ The RPMS have the same version but are new (4.3.0-0.2), so you need to reinstall those with rpm -Uvh --force systemimager-*rpm I've checked the inird.img and the templates and all the lvm commands are now present. Please, tell me it it works as I cannot test for the moment. Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________________ De : Ole Holm Nielsen [Ole...@fy...] Date d'envoi : vendredi 11 janvier 2013 13:12 À : sis...@li... Cc: LAHAYE Olivier Objet : New systemimager rpms for centos6: Missing lvm2 Hi Olivier, I'm testing your latest systemimager 4.3 RPMs dated 08-Jan-2013 from http://olivier.lahaye1.free.fr/RPMS/noarch/. I've generated PXE boot files in the client's /etc/systemimager/boot/* using si_prepareclient. However, my CentOS 6.3 clients have been installed with LVM disk partitions, so the SI master scripts wants to execute various LVM commands from the lvm2 RPM package. Unfortunately it seems that the lvm2 package is missing from the SI initrd.img, so the SI client install crashes with the error: pvcreate: not found Question: Can you add the lvm2 package to SI's building of initrd.img? Thanks, Ole -- Ole Holm Nielsen Department of Physics, Technical University of Denmark |
From: LAHAYE O. <oli...@ce...> - 2013-01-11 13:36:27
|
Thanks for the info, I was not using lvm, so I didn't notice. I'll give a look. Best regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________________ De : Ole Holm Nielsen [Ole...@fy...] Date d'envoi : vendredi 11 janvier 2013 13:12 À : sis...@li... Cc: LAHAYE Olivier Objet : New systemimager rpms for centos6: Missing lvm2 Hi Olivier, I'm testing your latest systemimager 4.3 RPMs dated 08-Jan-2013 from http://olivier.lahaye1.free.fr/RPMS/noarch/. I've generated PXE boot files in the client's /etc/systemimager/boot/* using si_prepareclient. However, my CentOS 6.3 clients have been installed with LVM disk partitions, so the SI master scripts wants to execute various LVM commands from the lvm2 RPM package. Unfortunately it seems that the lvm2 package is missing from the SI initrd.img, so the SI client install crashes with the error: pvcreate: not found Question: Can you add the lvm2 package to SI's building of initrd.img? Thanks, Ole -- Ole Holm Nielsen Department of Physics, Technical University of Denmark |
From: Ole H. N. <Ole...@fy...> - 2013-01-11 12:12:20
|
Hi Olivier, I'm testing your latest systemimager 4.3 RPMs dated 08-Jan-2013 from http://olivier.lahaye1.free.fr/RPMS/noarch/. I've generated PXE boot files in the client's /etc/systemimager/boot/* using si_prepareclient. However, my CentOS 6.3 clients have been installed with LVM disk partitions, so the SI master scripts wants to execute various LVM commands from the lvm2 RPM package. Unfortunately it seems that the lvm2 package is missing from the SI initrd.img, so the SI client install crashes with the error: pvcreate: not found Question: Can you add the lvm2 package to SI's building of initrd.img? Thanks, Ole -- Ole Holm Nielsen Department of Physics, Technical University of Denmark |
From: Ole H. N. <Ole...@fy...> - 2013-01-07 13:29:22
|
Dear Olivier, Regarding the SVN version, can you kindly give explicit UNIX commands for downloading from SVN? I do not know the location of the mentioned SVN repository. Thanks a lot, Ole On 01/07/2013 10:04 AM, LAHAYE Olivier wrote: > Hi, > > You can try the 4.3.0-0.1svn version, it worked for me. You'll need pre > and post-install scripts available here: > http://olivier.lahaye1.free.fr/RPMS/extra/ -- Ole Holm Nielsen Department of Physics, Technical University of Denmark |
From: LAHAYE O. <oli...@ce...> - 2013-01-07 10:34:38
|
You're perfectly right, a big mistake from my part. I replaced 'Disk' by "$DISK0" in my script (in order to avoid grepping 2 lines as the new parted now outputs Disk flags), but forgot to replace the simple quotes in the script. Fixed in the svn, but maybe it should also be fixed in the git repos? (I've never used git and need time to learn it) Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________ De : Jing CDL Sun [sj...@cn...] Date d'envoi : jeudi 27 décembre 2012 08:51 À : LAHAYE Olivier Cc: sis...@li...; sis...@li... Objet : RE : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Olivier, Have you updated the line "DISK_SIZE=`LC_ALL=C parted -s $DISK0 unit MB print | egrep '$DISK0' | awk '{print $NF}' | sed 's/MB//' `" in the .master script? I found it can not work in build 4.2.0-0.91svn4568 for redhat6.3. I think it should be "DISK_SIZE=`parted -s $DISK0 unit MB print | egrep "$DISK0" | awk '{print $NF}' | sed 's/MB//' `", use "" instead of '' around $DISK0, so shell can translate it. I tested this fix, it can work. Thx. Jing LAHAYE Olivier <oli...@ce...> 2012/12/18 17:03 To Jing CDL Sun/China/IBM@IBMCN, cc "sis...@li..." <sis...@li...>, "sis...@li..." <sis...@li...> Subject RE : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Jing, You're perfectly right, the ext4 problem was related to default initrd. The build did not enable the ext4 module. It's fixed in last build. Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________ De : Jing CDL Sun [sj...@cn...] Date d'envoi : mardi 18 décembre 2012 06:35 À : LAHAYE Olivier Cc: sis...@li...; sis...@li... Objet : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Thx for the reply. When I used your build with 4.2.0-0.9svn4568, I did not run into this problem, so I'm thinking maybe this is not a missing module problem? When you said 4.2.0-0.91svn4568 fixed the ext4 missing problem, did you mean the default initrd? because it seems 4.2.0-0.9svn4568 worked fine for me without the ext4 issue. Yes, I did not use the systemimager default kernel and initrd, instead, I'm using my own kernel/initrd got from my golder client, it's rhel6.3, so I think it should work fine, right? LAHAYE Olivier <oli...@ce...> 2012/12/17 17:16 To Jing CDL Sun/China/IBM@IBMCN, cc "sis...@li..." <sis...@li...>, "sis...@li..." <sis...@li...> Subject RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support This means that your disk is not recognized. Did you use my install scripts (especially the pre-install). http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2 It modprobs some modules in order to see disks. I don't know my the systemimager initrd fails to automaticaly do that (did not have time to look at the problem). if you did use the script, it means that you need to modify it to have more modules inserted. Or, if your hardware is too recent (not supported by provided default kernel), then you'll need to use your own kernel for the moment. I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build will copy missing stuffs from /lib /lib64 and other places and thoses version are for a 2.6.x kernel, not a 3.X kernel. This is also the reason why build fails on CentOS5 cas the libs copied from system misses some symbols (too old). In order to safely upgrade systemimager to latest kernel, we need to modifiy the build process so it builds everything and link everything with it's material which is not fully the case for now. (it still copy stuffs from the build system root tree (convenient ugly dirty hack)). Hope this helps, Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________ De : Jing CDL Sun [sj...@cn...] Date d'envoi : lundi 17 décembre 2012 07:42 À : LAHAYE Olivier Cc: sis...@li...; sis...@li... Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Hi, I just tested these new rpms, but found the issues below, the install broken. Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel gpt || shellout Dec 17 14:42:36 x3550m4n02 kernel: sda: unknown partition table Thx. Jing LAHAYE Olivier <oli...@ce...> 2012/12/13 22:47 To "sis...@li..." <sis...@li...>, cc "sis...@li..." <sis...@li...> Subject [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Dear all, Here are my fixed systemimager rpms for centos-6.3 Now, the ext4 filesystem is fixed (the module was missing in the initrd image) I've tested this on recent hardware and it worked like a charm. Thoses RPMS are for testing purpose RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch SRPMS: http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm PS: Keep in mind that you need postinstall scripts (already posted here) to setup grub, network and other stuffs as systemconfiguratior is unable to handle latest linux technologies. Best regards, Olivier -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d_______________________________________________ sisuite-devel mailing list sis...@li... https://lists.sourceforge.net/lists/listinfo/sisuite-devel |
From: LAHAYE O. <oli...@ce...> - 2013-01-07 09:04:41
|
Hi, You can try the 4.3.0-0.1svn version, it worked for me. You'll need pre and post-install scripts available here: http://olivier.lahaye1.free.fr/RPMS/extra/ Cheers, -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________ De : dav...@cn... [dav...@cn...] Date d'envoi : mercredi 19 décembre 2012 00:09 À : sis...@li... Objet : [sisuite-users] Which version ? I have been using a modified version of 4.1.99.svn4556_bli-1 to load my i386 rhel6.x servers as described below. I am now looking at imaging similar machines but now with the x86_64 version of rhel6.3 so I need like initrd_template( and boot_standard if it works) packages. What versions should I be trying ? http://olivier.lahaye1.free.fr/RPMS/noarch/ ?? Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: Dav...@cn... ----- Forwarded by David Livingstone/LIVING03/CNR/CA on 2012/12/18 16:00 ----- From: David Livingstone/LIVING03/CNR/CA To: sis...@li... Date: 2012/03/29 09:41 Subject: Loading RHEL 6.2 using 4.1.99.svn4556_bli-1 ________________________________ Using systemimager 4.1.99.svn4556_bli-1(ext4 enabled version) I have successfully imaged a RHEL 6.2 image to HP DL380G7 hardware(p410 array controllers). I was considering using SALI however for RHEL6.x grub2 is not an issue and ext4 support is included in 4.1.99.svn4556_bli-1. The setup I was imaging is a Proliant DL380G7 server with two p410 controllers(p401i and p410) with raid1 for root/boot/swap on the p410i and raid5 for /data on the p410. The system is running the latest RHEL 6.2. The attempted to image the system in two ways: 1. standard kernel 2. uyok 1. standard kernel I eventually got this to work but only after major modifications to the install script and manually setting up grub. The major issue here is that the default kernel uses the cciss driver and device naming(ex /dev/cciss/c0d0p2) and the RHEL6.x uses the hpsa driver(scsi naming ex /dev/sda). See http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02677069/c02677069.pdf . In general RHEL 5.x and before uses the cciss driver and RHEL6.x uses the hpsa when possible. I presume the standard kernel could be built with the hpsa module and some version logic applied to resolve this. 2. uyok This worked successfully after making some changes to address : - Needed modules(ie hpsa) as symbolic links under /lib/modules/(uname -r) ex [root@scdev ~]# ls -al /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko 0 lrwxrwxrwx 1 root root 50 Mar 5 04:05 /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko -> /lib/modules/2.6.32-71.el6.i686/extra/hpsa/hpsa.ko [root@scdev ~]# This results in the modules not being copied correctly in the generated initrd. I resolved this by modifying the UseYourOwnKernel.pm rsync invocations to copy the resultant files(the L rather then the l option. I include the diff below. - Numerous /lib/firmware files were missing in the initrd. By default the bnx2 nic driver(driver for the four nic's on the motherboard) as well as others in the RHEL6.2 kernel request firmware which is missing in the uyok initrd. I got this to work by : - modifying UseYourOwnKernel.pm to copy /lib/firmware to the initrd. Unfortunately this copies all of firmware as I couldn't figure out how to dynamically copy what was needed. - modified rcS under the std template to start udev BEFORE the modules are inserted. - rcS : start udev before loading modules. - under the std template : /usr/share/systemimager/boot/i386/standard/initrd_template/etc/init.d/rcS - The ramdisk_size must be set high enough to accept the larger initrd. - I had to si_cpimage as part of testing and noted that for yuok the kernel and initrd.img files are not copied. They had to be copied manually. Notes : When creating the image initially I also had to change si_prepareclient to use parted rather then sfdisk. I believe a bug was submitted on this a long time ago which was never applied. parted supports gpt partitions and sfdisk does not. [root@nasmtl sbin]# diff si_prepareclient si_prepareclient.orig.4.1.99.svn4556_bli 969,971c969,971 < # if($arch eq "i386") { < # $preferred_tool = 'sfdisk'; < # } --- > if($arch eq "i386") { > $preferred_tool = 'sfdisk'; > } - Diff for UseYourOwnKernel.pm [root@nasmtl SystemImager]# diff UseYourOwnKernel.pm UseYourOwnKernel.pm.orig 152c152 < $cmd = qq(rsync -aL --exclude=build --exclude=source ) . --- > $cmd = qq(rsync -a --exclude=build --exclude=source ) . 159c159 < $cmd = qq(rsync -aLR $module $staging_dir); --- > $cmd = qq(rsync -aR $module $staging_dir); 223,225d222 < # < # Copy /lib/firmware file to initrd < # 227,233d223 < if (-d "/lib/firmware") { < # copy entire firmware tree to new initrd. < $cmd = qq(rsync -aLR /lib/firmware $staging_dir); < !system( $cmd ) or die( "Couldn't $cmd." ); < < } < - Diff for rcS : [root@nasmtl init.d]# diff rcS rcS.orig 45,47d44 < # Start udev BEFORE load_my_modules so the modules can load firmware if needed. < start_udevd < 49a47,48 > start_udevd > David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: Dav...@cn... |
From: LAHAYE O. <oli...@ce...> - 2013-01-07 09:01:52
|
Hi, Thanks for this :-) And Happy new year to you. I've never used git, I hope I'll be able to find a quick start guide and newbee guide ;-) Cheers, -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________ De : Brian Elliott Finley [br...@th...] Date d'envoi : mardi 18 décembre 2012 19:31 À : sis...@li... Objet : Re: [sisuite-users] RE : RE : new centos-6.3 RPMS Olivier -- I've added you to github now too. Cheers, -Brian On Tue, Dec 18, 2012 at 10:01 AM, LAHAYE Olivier <oli...@ce...<mailto:oli...@ce...>> wrote: Hi, Brian, thanks for the svn access, it's cool now that I don't have to maintain tons of patches ;-) My github account is olahaye74. I've commited my modifications to the svn and tested a build and.... it worked :-) I should say, it built ;-) So now, as the version is 4.3.0 in the devel tree, the rpm version will be 4.3.0-0.x (4.3.0-1 when a release will be created). rpms available here http://olivier.lahaye1.free.fr/RPMS/noarch/ srpms available here http://olivier.lahaye1.free.fr/SRPMS/ Note that they should behave the same as v 4.2.0-0.91svn4568 as the current status is that I've commited the patch into the svn tree and updated the spec file to reflect that there is no more patches + minor modifications. Hopefully I did not miss anything in the process. :-) The i386initrd_template and i386boot-standard and currently being build, unfortunately, I'm on vaccation tonight and will only be back on january 7th, if the build process is not finished when I'll have to leave, I'll hybernate my VM and let the build finish later. Best regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________ De : Brian Elliott Finley [br...@th...<mailto:br...@th...>] Date d'envoi : samedi 15 décembre 2012 18:49 À : sis...@li...<mailto:sis...@li...> Objet : Re: [sisuite-users] RE : new centos-6.3 RPMS Contributors, I have added Olivier to the SystemImager project on SourceForge, but I'd like to add each of you who want to contribute to the SystemImager project on GitHub too, as that's where it will all be moving. If you don't have an account yet, no big -- just go to https://github.com and create one. Then send me an email with your account name, and I'll get you added. Thanks! -Brian On Thu, Nov 29, 2012 at 3:56 AM, LAHAYE Olivier <oli...@ce...<mailto:oli...@ce...>> wrote: Hi Brian, My sourceforge username is "olahaye74" (Olivier LAHAYE) (74 is because there was plenty of olivier.lahaye in France ;-)) I'm very glad to participate. In the meantime, I must let you know that I'm not extremely skilled in perl/python and such. I've modified systemimager so it can deploy oscar on centos6. The RPMS I've released are ok on centos6, but I've discovered that they can't build on centos5. In fact, the build system (initrd) after compiling some package does complete the initrd by copying missing libs from the build host system. Unfortunately, this behaviour breaks things as we have some binaries linked with libs that are too far in versions to be compatible (missing simbols). What I want to say is that I'm a little bit afraid to make modifications that could break the whole stuff because my developper skills are not extreme (I'm sysadmin in 1st place). Also I've never participated in such a project and thus I'm not familiar with how such modifications can go to the svn. (and I don't want to break things) For example, I've had to upgrade a component, and to change the build script so it makes install instead of copying the resulting binaries as the new version uses libtool and the old copying method was copying the wrapper instead of the lib itself. This change had an impact to the centos5 compatibility. I mean, my modification let the thing build on centos6, but in the meantime, centos5 became incompatible... In the end, right now, my rpms cant be build on centos5, though, they can deploy any OS. This means that the deploy server must be centos6. Best resgards. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________ De : Brian Elliott Finley [br...@th...<mailto:br...@th...>] Date d'envoi : vendredi 23 novembre 2012 19:10 À : sis...@li...<mailto:sis...@li...> Objet : Re: [sisuite-users] new centos-6.3 RPMS Sun, Olivier, Please send me your SourceForge usernames. I appreciate your efforts, and would like to grant you both commit privileges to the SVN repository, so that you can commit your patches directly. Bas, Franck, the same goes for you two if you wish. Regarding a fork, that is generally necessary because one does not have the ability to modify the upstream original. I will happily grant you this access, as I think it would be better for the community to improve the main code stream rather than to have a fork. I know that SALI has special circumstances that made a fork appropriate for them, at least previously, but I would also be happy to allow that fork to merge into the mainstream if SALI considers that desirable. Lastly, with regard to SystemConfigurator, it is no longer being maintained, and we should work to eliminate our dependency on it. With modern Linuxes this should be very feasible through the use of SystemImager postscripts for setup of boot manager (Grub) and networking (if desirable). All -- feel free to call me if you have any questions. Just bear in mind that I'm generally somewhere in GMT-5 through GMT-7. ;-) If unsure, start with a text message, or leave a voice mail if I don't answer right away, but I'll be glad to discuss. My mobile is 469.444.0167<tel:469.444.0167>. Cheers, -Brian On Wed, Nov 21, 2012 at 1:16 AM, Jing CDL Sun <sj...@cn...<mailto:sj...@cn...>> wrote: Hi Olivier, Thanks for this sharing! Have you cloning Centos-6.3 with these rpms successfully? I tried to use them for redhat6.3 cloning, bug failed... ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ sisuite-users mailing list sis...@li...<mailto:sis...@li...> https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Brian Elliott Finley Mobile: 469.444.0167<tel:469.444.0167> ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: VERIFY Test and improve your parallel project with help from experts and peers. http://goparallel.sourceforge.net _______________________________________________ sisuite-users mailing list sis...@li...<mailto:sis...@li...> https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Brian Elliott Finley Mobile: 469.444.0167<tel:469.444.0167> ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ sisuite-users mailing list sis...@li...<mailto:sis...@li...> https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Brian Elliott Finley Mobile: 469.444.0167 |
From: Sachio I. <siw...@ca...> - 2012-12-27 09:09:16
|
I am out of the office until 07/01/2013. Note: This is an automated response to your message "sisuite-users Digest, Vol 72, Issue 10" sent on 12/27/2012 2:52:22. This is the only notification you will receive while this person is away. |
From: Jing C. S. <sj...@cn...> - 2012-12-27 07:52:21
|
Olivier, Have you updated the line "DISK_SIZE=`LC_ALL=C parted -s $DISK0 unit MB print | egrep '$DISK0' | awk '{print $NF}' | sed 's/MB//' `" in the .master script? I found it can not work in build 4.2.0-0.91svn4568 for redhat6.3. I think it should be "DISK_SIZE=`parted -s $DISK0 unit MB print | egrep "$DISK0" | awk '{print $NF}' | sed 's/MB//' `", use "" instead of '' around $DISK0, so shell can translate it. I tested this fix, it can work. Thx. Jing LAHAYE Olivier <oli...@ce...> 2012/12/18 17:03 To Jing CDL Sun/China/IBM@IBMCN, cc "sis...@li..." <sis...@li...>, "sis...@li..." <sis...@li...> Subject RE : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Jing, You're perfectly right, the ext4 problem was related to default initrd. The build did not enable the ext4 module. It's fixed in last build. Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR De : Jing CDL Sun [sj...@cn...] Date d'envoi : mardi 18 décembre 2012 06:35 À : LAHAYE Olivier Cc: sis...@li...; sis...@li... Objet : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Thx for the reply. When I used your build with 4.2.0-0.9svn4568, I did not run into this problem, so I'm thinking maybe this is not a missing module problem? When you said 4.2.0-0.91svn4568 fixed the ext4 missing problem, did you mean the default initrd? because it seems 4.2.0-0.9svn4568 worked fine for me without the ext4 issue. Yes, I did not use the systemimager default kernel and initrd, instead, I'm using my own kernel/initrd got from my golder client, it's rhel6.3, so I think it should work fine, right? LAHAYE Olivier <oli...@ce...> 2012/12/17 17:16 To Jing CDL Sun/China/IBM@IBMCN, cc "sis...@li..." <sis...@li...>, "sis...@li..." <sis...@li...> Subject RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support This means that your disk is not recognized. Did you use my install scripts (especially the pre-install). http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2 It modprobs some modules in order to see disks. I don't know my the systemimager initrd fails to automaticaly do that (did not have time to look at the problem). if you did use the script, it means that you need to modify it to have more modules inserted. Or, if your hardware is too recent (not supported by provided default kernel), then you'll need to use your own kernel for the moment. I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build will copy missing stuffs from /lib /lib64 and other places and thoses version are for a 2.6.x kernel, not a 3.X kernel. This is also the reason why build fails on CentOS5 cas the libs copied from system misses some symbols (too old). In order to safely upgrade systemimager to latest kernel, we need to modifiy the build process so it builds everything and link everything with it's material which is not fully the case for now. (it still copy stuffs from the build system root tree (convenient ugly dirty hack)). Hope this helps, Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR De : Jing CDL Sun [sj...@cn...] Date d'envoi : lundi 17 décembre 2012 07:42 À : LAHAYE Olivier Cc: sis...@li...; sis...@li... Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Hi, I just tested these new rpms, but found the issues below, the install broken. Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel gpt || shellout Dec 17 14:42:36 x3550m4n02 kernel: sda: unknown partition table Thx. Jing LAHAYE Olivier <oli...@ce...> 2012/12/13 22:47 To "sis...@li..." <sis...@li...>, cc "sis...@li..." <sis...@li...> Subject [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Dear all, Here are my fixed systemimager rpms for centos-6.3 Now, the ext4 filesystem is fixed (the module was missing in the initrd image) I've tested this on recent hardware and it worked like a charm. Thoses RPMS are for testing purpose RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch SRPMS: http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm PS: Keep in mind that you need postinstall scripts (already posted here) to setup grub, network and other stuffs as systemconfiguratior is unable to handle latest linux technologies. Best regards, Olivier -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ sisuite-devel mailing list sis...@li... https://lists.sourceforge.net/lists/listinfo/sisuite-devel |
From: DongInn K. <di...@cs...> - 2012-12-24 21:01:33
|
Hi, I tried to deploy a system image with ubuntu-12.04 (precise) and the host machine has the "Broadcom Corporation NetXtreme II BCM57800 10 Gigabit Ethernet" network card. I used UYOK and it failed to load up the network firmware while going through initrd . The network kernel module: bnx2x Its firmware is: bnx2x-e2-7.0.29.0.fw It seems that it could not find the firmware in initrd and I modified the UYOK initrd image file to include the firmware file in /lib/firmware/bnx2x/bnx2x-e2-7.0.29.0.fw. > root@cutter-m:~/tmp2# ls -al lib/firmware/bnx2x/ > total 620 > drwxr-xr-x 2 root root 4096 Dec 24 11:56 . > drwxr-xr-x 6 root root 4096 Dec 24 11:56 .. > -rw-r--r-- 1 root root 161368 Apr 12 2012 bnx2x-e1-7.0.29.0.fw > -rw-r--r-- 1 root root 168680 Apr 12 2012 bnx2x-e1h-7.0.29.0.fw > -rw-r--r-- 1 root root 289848 Apr 12 2012 bnx2x-e2-7.0.29.0.fw > root@cutter-m:~/tmp2# Even though the firmware seems to be the right place, the network card can not be up (i.e., fail to run "ifconfig eth0 up"). Note, the bnx2x kernel module is loaded properly regardless of the existence of the firmware. Can anyone please help me to fix the firmware issue? http://www.crest.iu.edu/~dikim/images/firmware_screen.png Regards, -- - DongInn |
From: Brian E. F. <br...@th...> - 2012-12-20 00:07:39
|
As a follow-up -- the SourceForge repository will remain read-only (and may eventually go away). All future commits should be pushed to the GitHub repo. Thanks! -Brian On Wed, Dec 19, 2012 at 6:05 PM, Brian Elliott Finley <br...@th...>wrote: > It is done: > > https://github.com/finley/SystemImager > > > > > On Wed, Dec 19, 2012 at 1:37 PM, Brian Elliott Finley < > br...@th...> wrote: > >> All, >> >> I have started the process to re-locate the SystemImager code repository >> from SourceForge to GitHub. >> >> Code contributors -- the SourceForge SVN repository should now be treated >> as read-only, and I've modified the permissions accordingly. >> >> I'll send out a reply to this message when the re-location is complete >> (should be later today). >> >> Cheers, -Brian >> >> >> -- >> Brian Elliott Finley >> Mobile: 469.444.0167 > > > > > -- > Brian Elliott Finley > Mobile: 469.444.0167 > -- Brian Elliott Finley Mobile: 469.444.0167 |
From: Brian E. F. <br...@th...> - 2012-12-20 00:05:53
|
It is done: https://github.com/finley/SystemImager On Wed, Dec 19, 2012 at 1:37 PM, Brian Elliott Finley <br...@th...>wrote: > All, > > I have started the process to re-locate the SystemImager code repository > from SourceForge to GitHub. > > Code contributors -- the SourceForge SVN repository should now be treated > as read-only, and I've modified the permissions accordingly. > > I'll send out a reply to this message when the re-location is complete > (should be later today). > > Cheers, -Brian > > > -- > Brian Elliott Finley > Mobile: 469.444.0167 -- Brian Elliott Finley Mobile: 469.444.0167 |
From: Brian E. F. <br...@th...> - 2012-12-19 19:38:05
|
All, I have started the process to re-locate the SystemImager code repository from SourceForge to GitHub. Code contributors -- the SourceForge SVN repository should now be treated as read-only, and I've modified the permissions accordingly. I'll send out a reply to this message when the re-location is complete (should be later today). Cheers, -Brian -- Brian Elliott Finley Mobile: 469.444.0167 |
From: Bas v. d. V. <ba...@sa...> - 2012-12-19 12:32:11
|
Brian, On 18 dec. 2012, at 22:15, Brian Elliott Finley <br...@th...> wrote: > Bas, > > No problem. I actually went through a dry run with svn2git yesterday. ;-) I'll take care of the initial import. > That is nice > The Plan: > * Yes, we'll pull all of SystemImager into github. fine for me > * How do you recommend that we incorporate SALI? > > It could be done as: > - a branch > - a fork (git style) > - a branch with the intent to merge > (would need more discussion on this one -- just want to maintain general applicability) > SALI consists of: * SALI server --> could be an alternative for system imager server. Does a lot things automatically (rsync/bittorrent) * SALI kernel/initrd is more up to date then system imager kernel/initrd. The only problem for now is that the autoinstall scripts that are made by systemconfigurator does not work anymore because we removed some functions that are removed in SALI, we could be made available again and ported to the new SALI functions. so we are backwards compatible. Else we have to maintain two versions of kernel/initrd. That is a waste of time. regards > > Cheers, -Brian > > > > On Tue, Dec 18, 2012 at 1:54 PM, Bas van der Vlies <ba...@sa...> wrote: > Brian, > > I am a but swamped at the moment and the holiday season is nearby ;-). There are tools that convert from sourceforge to github: > * https://github.com/nirvdrum/svn2git#readme > > What is the plan: > * convert systemimager svn (all) to github. We have a lot of versions, tags and branches > * Where will SALI fit in. There are a lot of changes in the SALI release. Do we replace the kernelinitrd build process? In SALI we also replaced the system imager server software. > > regards > > On 18 dec. 2012, at 00:45, Brian Finley <br...@th...> wrote: > > > You guys have been added! > > > > https://github.com/finley/systemimager > > > > If you can help by doing the initial import of SystemImager from SourceForge SVN, that would be great. Let me know if you need anything from me. > > > > Thanks, -Brian > > > > > > > > On 12/17/2012 03:42 AM, Bas van der Vlies wrote: > >> Brian, > >> > >> > >> My github account is: basvandervlies > >> Dennis github account: dstam > >> > >> > >> regards > >> > >> On 15 dec. 2012, at 18:52, Brian Elliott Finley <br...@th...> wrote: > >> > >>> Dennis, > >>> > >>> That sounds like a good path forward. Please send me github account names for you and Bas, and I'll add you to the SystemImager project. > >>> > >>> Cheers, -Brian > >>> > >>> > >>> > >>> On Tue, Nov 27, 2012 at 12:16 PM, Dennis Stam <Den...@sa...> wrote: > >>> Hi Brian, > >>> > >>> Great news to make SALI into SystemImager. It's better for both teams to join forces because we want to accomplish the same goal. > >>> > >>> On 27 nov. 2012, at 18:10, Brian Elliott Finley <br...@th...<mailto:br...@th...>> wrote: > >>> > >>> I've created the initial repo. Bas -- what do you need from me to move the code from SourceForce to github? > >>> > >>> Currently we started the development of version 1.6 and it's far from finished. So as initial import to the git we can use the branch 1.5. > >>> > >>> And probally the easiest way to migrate our source code to the SystemImager git repo is to fork your repo. From there we can import our branch 1.5 to the forked git repo. And finally send you a pull request? > >>> > >>> Regards, > >>> > >>> Dennis > >>> > >>> > >>> https://github.com/finley/systemimager > >>> > >>> Thanks! > >>> > >>> > >>> On Tue, Nov 27, 2012 at 11:04 AM, Brian Elliott Finley <br...@th...<mailto:br...@th...>> wrote: > >>> I think a move to github would be a fine idea. > >>> > >>> As for the SystemConfigurator functionality, I'd like to use the SystemImager post-script functionality. It will allow us to > >>> - include simple scripts upstream, that could be used as-is for simple and common cases > >>> - these simple scripts could be easily customized by site admins, without having to know SystemImager internals > >>> - a simple script could be used to invoke puppet, chef, or SSM (Simple State Manager - http://download.systemimager.org/pub/ssm/README) > >>> > >>> Cheers, -Brian > >>> > >>> > >>> > >>> On Mon, Nov 26, 2012 at 5:28 AM, Bas van der Vlies <ba...@sa...<mailto:ba...@sa...>> wrote: > >>> Brian, > >>> > >>> The SALI vork was nescessary to support modern hardware. Your are right you can better have one source. SALI has implemented a new kernel/initrd and some shell functions, e.g. one for easy disk partition. We also replaced the system imager-server software. > >>> > >>> Currently we do not have a tool like systemconfigurator or automatically generate installation scripts. So we can definitely benefit from co-operation. My thought for replacing systemconfigurator are with shell commands or a system maintenance tool like CFengine, puppet , chef ,…. > >>> > >>> Can we move the code to github.com<http://github.com/><http://github.com<http://github.com/>>. I think it easier to contribute and better suited if more people are involved. > >>> > >>> regards > >>> > >>> > >>> On 23 nov. 2012, at 19:10, Brian Elliott Finley <br...@th...<mailto:br...@th...><mailto:br...@th...<mailto:br...@th...>>> wrote: > >>> > >>> Sun, Olivier, > >>> > >>> Please send me your SourceForge usernames. I appreciate your efforts, and would like to grant you both commit privileges to the SVN repository, so that you can commit your patches directly. > >>> > >>> Bas, Franck, the same goes for you two if you wish. > >>> > >>> > >>> Regarding a fork, that is generally necessary because one does not have the ability to modify the upstream original. I will happily grant you this access, as I think it would be better for the community to improve the main code stream rather than to have a fork. I know that SALI has special circumstances that made a fork appropriate for them, at least previously, but I would also be happy to allow that fork to merge into the mainstream if SALI considers that desirable. > >>> > >>> > >>> Lastly, with regard to SystemConfigurator, it is no longer being maintained, and we should work to eliminate our dependency on it. With modern Linuxes this should be very feasible through the use of SystemImager postscripts for setup of boot manager (Grub) and networking (if desirable). > >>> > >>> > >>> All -- feel free to call me if you have any questions. Just bear in mind that I'm generally somewhere in GMT-5 through GMT-7. ;-) If unsure, start with a text message, or leave a voice mail if I don't answer right away, but I'll be glad to discuss. My mobile is 469.444.0167<tel:469.444.0167>. > >>> > >>> > >>> Cheers, -Brian > >>> > >>> > >>> > >>> > >>> > >>> On Wed, Nov 21, 2012 at 1:16 AM, Jing CDL Sun <sj...@cn...<mailto:sj...@cn...><mailto:sj...@cn...<mailto:sj...@cn...>>> wrote: > >>> Hi Olivier, > >>> > >>> Thanks for this sharing! > >>> > >>> Have you cloning Centos-6.3 with these rpms successfully? I tried to use them for redhat6.3 cloning, bug failed... > >>> > >>> ------------------------------------------------------------------------------ > >>> Monitor your physical, virtual and cloud infrastructure from a single > >>> web console. Get in-depth insight into apps, servers, databases, vmware, > >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. > >>> Pricing starts from $795 for 25 servers or applications! > >>> http://p.sf.net/sfu/zoho_dev2dev_nov > >>> _______________________________________________ > >>> sisuite-users mailing list > >>> sis...@li...<mailto:sis...@li...><mailto:sis...@li...<mailto:sis...@li...>> > >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users > >>> > >>> > >>> > >>> > >>> -- > >>> Brian Elliott Finley > >>> Mobile: 469.444.0167<tel:469.444.0167> > >>> ------------------------------------------------------------------------------ > >>> Monitor your physical, virtual and cloud infrastructure from a single > >>> web console. Get in-depth insight into apps, servers, databases, vmware, > >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. > >>> Pricing starts from $795 for 25 servers or applications! > >>> http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________ > >>> sisuite-users<http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________sisuite-users> mailing list > >>> sis...@li...<mailto:sis...@li...> > >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users > >>> > >>> -- > >>> Bas van der Vlies > >>> mail: ba...@sa...<mailto:ba...@sa...><mailto:ba...@sa...<mailto:ba...@sa...>> > >>> SARA - Academic Computing Services , Amsterdam, The Netherlands > >>> > >>> > >>> ------------------------------------------------------------------------------ > >>> Monitor your physical, virtual and cloud infrastructure from a single > >>> web console. Get in-depth insight into apps, servers, databases, vmware, > >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. > >>> Pricing starts from $795 for 25 servers or applications! > >>> http://p.sf.net/sfu/zoho_dev2dev_nov > >>> _______________________________________________ > >>> sisuite-users mailing list > >>> sis...@li...<mailto:sis...@li...> > >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users > >>> > >>> > >>> > >>> -- > >>> Brian Elliott Finley > >>> Mobile: 469.444.0167<tel:469.444.0167> > >>> > >>> > >>> > >>> -- > >>> Brian Elliott Finley > >>> Mobile: 469.444.0167 > >>> ------------------------------------------------------------------------------ > >>> Monitor your physical, virtual and cloud infrastructure from a single > >>> web console. Get in-depth insight into apps, servers, databases, vmware, > >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. > >>> Pricing starts from $795 for 25 servers or applications! > >>> http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________ > >>> sisuite-users mailing list > >>> sis...@li... > >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users > >>> > >>> > >>> ------------------------------------------------------------------------------ > >>> Monitor your physical, virtual and cloud infrastructure from a single > >>> web console. Get in-depth insight into apps, servers, databases, vmware, > >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. > >>> Pricing starts from $795 for 25 servers or applications! > >>> http://p.sf.net/sfu/zoho_dev2dev_nov > >>> _______________________________________________ > >>> sisuite-users mailing list > >>> sis...@li... > >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users > >>> > >>> > >>> > >>> -- > >>> Brian Elliott Finley > >>> Mobile: 469.444.0167 > >> > > > > -- > > Brian Elliott Finley > > Mobile: 469.444.0167 > > -- > Bas van der Vlies > mail: ba...@sa... > SARA - Academic Computing Services , Amsterdam, The Netherlands > > > > > -- > Brian Elliott Finley > Mobile: 469.444.0167 -- Bas van der Vlies mail: ba...@sa... SARA - Academic Computing Services , Amsterdam, The Netherlands |
From: <dav...@cn...> - 2012-12-18 23:24:36
|
I have been using a modified version of 4.1.99.svn4556_bli-1 to load my i386 rhel6.x servers as described below. I am now looking at imaging similar machines but now with the x86_64 version of rhel6.3 so I need like initrd_template( and boot_standard if it works) packages. What versions should I be trying ? http://olivier.lahaye1.free.fr/RPMS/noarch/ ?? Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: Dav...@cn... ----- Forwarded by David Livingstone/LIVING03/CNR/CA on 2012/12/18 16:00 ----- From: David Livingstone/LIVING03/CNR/CA To: sis...@li... Date: 2012/03/29 09:41 Subject: Loading RHEL 6.2 using 4.1.99.svn4556_bli-1 Using systemimager 4.1.99.svn4556_bli-1(ext4 enabled version) I have successfully imaged a RHEL 6.2 image to HP DL380G7 hardware(p410 array controllers). I was considering using SALI however for RHEL6.x grub2 is not an issue and ext4 support is included in 4.1.99.svn4556_bli-1. The setup I was imaging is a Proliant DL380G7 server with two p410 controllers(p401i and p410) with raid1 for root/boot/swap on the p410i and raid5 for /data on the p410. The system is running the latest RHEL 6.2. The attempted to image the system in two ways: 1. standard kernel 2. uyok 1. standard kernel I eventually got this to work but only after major modifications to the install script and manually setting up grub. The major issue here is that the default kernel uses the cciss driver and device naming(ex /dev/cciss/c0d0p2) and the RHEL6.x uses the hpsa driver(scsi naming ex /dev/sda). See http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02677069/c02677069.pdf . In general RHEL 5.x and before uses the cciss driver and RHEL6.x uses the hpsa when possible. I presume the standard kernel could be built with the hpsa module and some version logic applied to resolve this. 2. uyok This worked successfully after making some changes to address : - Needed modules(ie hpsa) as symbolic links under /lib/modules/(uname -r) ex [root@scdev ~]# ls -al /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko 0 lrwxrwxrwx 1 root root 50 Mar 5 04:05 /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko -> /lib/modules/2.6.32-71.el6.i686/extra/hpsa/hpsa.ko [root@scdev ~]# This results in the modules not being copied correctly in the generated initrd. I resolved this by modifying the UseYourOwnKernel.pm rsync invocations to copy the resultant files(the L rather then the l option. I include the diff below. - Numerous /lib/firmware files were missing in the initrd. By default the bnx2 nic driver(driver for the four nic's on the motherboard) as well as others in the RHEL6.2 kernel request firmware which is missing in the uyok initrd. I got this to work by : - modifying UseYourOwnKernel.pm to copy /lib/firmware to the initrd. Unfortunately this copies all of firmware as I couldn't figure out how to dynamically copy what was needed. - modified rcS under the std template to start udev BEFORE the modules are inserted. - rcS : start udev before loading modules. - under the std template : /usr/share/systemimager/boot/i386/standard/initrd_template/etc/init.d/rcS - The ramdisk_size must be set high enough to accept the larger initrd. - I had to si_cpimage as part of testing and noted that for yuok the kernel and initrd.img files are not copied. They had to be copied manually. Notes : When creating the image initially I also had to change si_prepareclient to use parted rather then sfdisk. I believe a bug was submitted on this a long time ago which was never applied. parted supports gpt partitions and sfdisk does not. [root@nasmtl sbin]# diff si_prepareclient si_prepareclient.orig.4.1.99.svn4556_bli 969,971c969,971 < # if($arch eq "i386") { < # $preferred_tool = 'sfdisk'; < # } --- > if($arch eq "i386") { > $preferred_tool = 'sfdisk'; > } - Diff for UseYourOwnKernel.pm [root@nasmtl SystemImager]# diff UseYourOwnKernel.pm UseYourOwnKernel.pm.orig 152c152 < $cmd = qq(rsync -aL --exclude=build --exclude=source ) . --- > $cmd = qq(rsync -a --exclude=build --exclude=source ) . 159c159 < $cmd = qq(rsync -aLR $module $staging_dir); --- > $cmd = qq(rsync -aR $module $staging_dir); 223,225d222 < # < # Copy /lib/firmware file to initrd < # 227,233d223 < if (-d "/lib/firmware") { < # copy entire firmware tree to new initrd. < $cmd = qq(rsync -aLR /lib/firmware $staging_dir); < !system( $cmd ) or die( "Couldn't $cmd." ); < < } < - Diff for rcS : [root@nasmtl init.d]# diff rcS rcS.orig 45,47d44 < # Start udev BEFORE load_my_modules so the modules can load firmware if needed. < start_udevd < 49a47,48 > start_udevd > David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: Dav...@cn... |
From: Brian E. F. <br...@th...> - 2012-12-18 21:15:33
|
Bas, No problem. I actually went through a dry run with svn2git yesterday. ;-) I'll take care of the initial import. The Plan: * Yes, we'll pull all of SystemImager into github. * How do you recommend that we incorporate SALI? It could be done as: - a branch - a fork (git style) - a branch with the intent to merge (would need more discussion on this one -- just want to maintain general applicability) Cheers, -Brian On Tue, Dec 18, 2012 at 1:54 PM, Bas van der Vlies <ba...@sa...> wrote: > Brian, > > I am a but swamped at the moment and the holiday season is nearby ;-). > There are tools that convert from sourceforge to github: > * https://github.com/nirvdrum/svn2git#readme > > What is the plan: > * convert systemimager svn (all) to github. We have a lot of versions, > tags and branches > * Where will SALI fit in. There are a lot of changes in the SALI > release. Do we replace the kernelinitrd build process? In SALI we also > replaced the system imager server software. > > regards > > On 18 dec. 2012, at 00:45, Brian Finley <br...@th...> wrote: > > > You guys have been added! > > > > https://github.com/finley/systemimager > > > > If you can help by doing the initial import of SystemImager from > SourceForge SVN, that would be great. Let me know if you need anything > from me. > > > > Thanks, -Brian > > > > > > > > On 12/17/2012 03:42 AM, Bas van der Vlies wrote: > >> Brian, > >> > >> > >> My github account is: basvandervlies > >> Dennis github account: dstam > >> > >> > >> regards > >> > >> On 15 dec. 2012, at 18:52, Brian Elliott Finley <br...@th...> > wrote: > >> > >>> Dennis, > >>> > >>> That sounds like a good path forward. Please send me github account > names for you and Bas, and I'll add you to the SystemImager project. > >>> > >>> Cheers, -Brian > >>> > >>> > >>> > >>> On Tue, Nov 27, 2012 at 12:16 PM, Dennis Stam <Den...@sa...> > wrote: > >>> Hi Brian, > >>> > >>> Great news to make SALI into SystemImager. It's better for both teams > to join forces because we want to accomplish the same goal. > >>> > >>> On 27 nov. 2012, at 18:10, Brian Elliott Finley <br...@th... > <mailto:br...@th...>> wrote: > >>> > >>> I've created the initial repo. Bas -- what do you need from me to > move the code from SourceForce to github? > >>> > >>> Currently we started the development of version 1.6 and it's far from > finished. So as initial import to the git we can use the branch 1.5. > >>> > >>> And probally the easiest way to migrate our source code to the > SystemImager git repo is to fork your repo. From there we can import our > branch 1.5 to the forked git repo. And finally send you a pull request? > >>> > >>> Regards, > >>> > >>> Dennis > >>> > >>> > >>> https://github.com/finley/systemimager > >>> > >>> Thanks! > >>> > >>> > >>> On Tue, Nov 27, 2012 at 11:04 AM, Brian Elliott Finley < > br...@th...<mailto:br...@th...>> wrote: > >>> I think a move to github would be a fine idea. > >>> > >>> As for the SystemConfigurator functionality, I'd like to use the > SystemImager post-script functionality. It will allow us to > >>> - include simple scripts upstream, that could be used as-is for > simple and common cases > >>> - these simple scripts could be easily customized by site admins, > without having to know SystemImager internals > >>> - a simple script could be used to invoke puppet, chef, or SSM > (Simple State Manager - http://download.systemimager.org/pub/ssm/README) > >>> > >>> Cheers, -Brian > >>> > >>> > >>> > >>> On Mon, Nov 26, 2012 at 5:28 AM, Bas van der Vlies <ba...@sa... > <mailto:ba...@sa...>> wrote: > >>> Brian, > >>> > >>> The SALI vork was nescessary to support modern hardware. Your are > right you can better have one source. SALI has implemented a new > kernel/initrd and some shell functions, e.g. one for easy disk partition. > We also replaced the system imager-server software. > >>> > >>> Currently we do not have a tool like systemconfigurator or > automatically generate installation scripts. So we can definitely benefit > from co-operation. My thought for replacing systemconfigurator are with > shell commands or a system maintenance tool like CFengine, puppet , chef ,…. > >>> > >>> Can we move the code to github.com<http://github.com/>< > http://github.com<http://github.com/>>. I think it easier to contribute > and better suited if more people are involved. > >>> > >>> regards > >>> > >>> > >>> On 23 nov. 2012, at 19:10, Brian Elliott Finley <br...@th... > <mailto:br...@th...><mailto:br...@th...<mailto: > br...@th...>>> wrote: > >>> > >>> Sun, Olivier, > >>> > >>> Please send me your SourceForge usernames. I appreciate your efforts, > and would like to grant you both commit privileges to the SVN repository, > so that you can commit your patches directly. > >>> > >>> Bas, Franck, the same goes for you two if you wish. > >>> > >>> > >>> Regarding a fork, that is generally necessary because one does not > have the ability to modify the upstream original. I will happily grant you > this access, as I think it would be better for the community to improve the > main code stream rather than to have a fork. I know that SALI has special > circumstances that made a fork appropriate for them, at least previously, > but I would also be happy to allow that fork to merge into the mainstream > if SALI considers that desirable. > >>> > >>> > >>> Lastly, with regard to SystemConfigurator, it is no longer being > maintained, and we should work to eliminate our dependency on it. With > modern Linuxes this should be very feasible through the use of SystemImager > postscripts for setup of boot manager (Grub) and networking (if desirable). > >>> > >>> > >>> All -- feel free to call me if you have any questions. Just bear in > mind that I'm generally somewhere in GMT-5 through GMT-7. ;-) If unsure, > start with a text message, or leave a voice mail if I don't answer right > away, but I'll be glad to discuss. My mobile is 469.444.0167<tel: > 469.444.0167>. > >>> > >>> > >>> Cheers, -Brian > >>> > >>> > >>> > >>> > >>> > >>> On Wed, Nov 21, 2012 at 1:16 AM, Jing CDL Sun <sj...@cn... > <mailto:sj...@cn...><mailto:sj...@cn...<mailto:sj...@cn...>>> > wrote: > >>> Hi Olivier, > >>> > >>> Thanks for this sharing! > >>> > >>> Have you cloning Centos-6.3 with these rpms successfully? I tried to > use them for redhat6.3 cloning, bug failed... > >>> > >>> > ------------------------------------------------------------------------------ > >>> Monitor your physical, virtual and cloud infrastructure from a single > >>> web console. Get in-depth insight into apps, servers, databases, > vmware, > >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. > >>> Pricing starts from $795 for 25 servers or applications! > >>> http://p.sf.net/sfu/zoho_dev2dev_nov > >>> _______________________________________________ > >>> sisuite-users mailing list > >>> sis...@li...<mailto: > sis...@li...><mailto: > sis...@li...<mailto: > sis...@li...>> > >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users > >>> > >>> > >>> > >>> > >>> -- > >>> Brian Elliott Finley > >>> Mobile: 469.444.0167<tel:469.444.0167> > >>> > ------------------------------------------------------------------------------ > >>> Monitor your physical, virtual and cloud infrastructure from a single > >>> web console. Get in-depth insight into apps, servers, databases, > vmware, > >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. > >>> Pricing starts from $795 for 25 servers or applications! > >>> > http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________ > >>> sisuite-users< > http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________sisuite-users> > mailing list > >>> sis...@li...<mailto: > sis...@li...> > >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users > >>> > >>> -- > >>> Bas van der Vlies > >>> mail: ba...@sa...<mailto:ba...@sa...><mailto:ba...@sa...<mailto: > ba...@sa...>> > >>> SARA - Academic Computing Services , Amsterdam, The Netherlands > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> Monitor your physical, virtual and cloud infrastructure from a single > >>> web console. Get in-depth insight into apps, servers, databases, > vmware, > >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. > >>> Pricing starts from $795 for 25 servers or applications! > >>> http://p.sf.net/sfu/zoho_dev2dev_nov > >>> _______________________________________________ > >>> sisuite-users mailing list > >>> sis...@li...<mailto: > sis...@li...> > >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users > >>> > >>> > >>> > >>> -- > >>> Brian Elliott Finley > >>> Mobile: 469.444.0167<tel:469.444.0167> > >>> > >>> > >>> > >>> -- > >>> Brian Elliott Finley > >>> Mobile: 469.444.0167 > >>> > ------------------------------------------------------------------------------ > >>> Monitor your physical, virtual and cloud infrastructure from a single > >>> web console. Get in-depth insight into apps, servers, databases, > vmware, > >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. > >>> Pricing starts from $795 for 25 servers or applications! > >>> > http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________ > >>> sisuite-users mailing list > >>> sis...@li... > >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> Monitor your physical, virtual and cloud infrastructure from a single > >>> web console. Get in-depth insight into apps, servers, databases, > vmware, > >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. > >>> Pricing starts from $795 for 25 servers or applications! > >>> http://p.sf.net/sfu/zoho_dev2dev_nov > >>> _______________________________________________ > >>> sisuite-users mailing list > >>> sis...@li... > >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users > >>> > >>> > >>> > >>> -- > >>> Brian Elliott Finley > >>> Mobile: 469.444.0167 > >> > > > > -- > > Brian Elliott Finley > > Mobile: 469.444.0167 > > -- > Bas van der Vlies > mail: ba...@sa... > SARA - Academic Computing Services , Amsterdam, The Netherlands > > -- Brian Elliott Finley Mobile: 469.444.0167 |
From: Bas v. d. V. <ba...@sa...> - 2012-12-18 19:54:14
|
Brian, I am a but swamped at the moment and the holiday season is nearby ;-). There are tools that convert from sourceforge to github: * https://github.com/nirvdrum/svn2git#readme What is the plan: * convert systemimager svn (all) to github. We have a lot of versions, tags and branches * Where will SALI fit in. There are a lot of changes in the SALI release. Do we replace the kernelinitrd build process? In SALI we also replaced the system imager server software. regards On 18 dec. 2012, at 00:45, Brian Finley <br...@th...> wrote: > You guys have been added! > > https://github.com/finley/systemimager > > If you can help by doing the initial import of SystemImager from SourceForge SVN, that would be great. Let me know if you need anything from me. > > Thanks, -Brian > > > > On 12/17/2012 03:42 AM, Bas van der Vlies wrote: >> Brian, >> >> >> My github account is: basvandervlies >> Dennis github account: dstam >> >> >> regards >> >> On 15 dec. 2012, at 18:52, Brian Elliott Finley <br...@th...> wrote: >> >>> Dennis, >>> >>> That sounds like a good path forward. Please send me github account names for you and Bas, and I'll add you to the SystemImager project. >>> >>> Cheers, -Brian >>> >>> >>> >>> On Tue, Nov 27, 2012 at 12:16 PM, Dennis Stam <Den...@sa...> wrote: >>> Hi Brian, >>> >>> Great news to make SALI into SystemImager. It's better for both teams to join forces because we want to accomplish the same goal. >>> >>> On 27 nov. 2012, at 18:10, Brian Elliott Finley <br...@th...<mailto:br...@th...>> wrote: >>> >>> I've created the initial repo. Bas -- what do you need from me to move the code from SourceForce to github? >>> >>> Currently we started the development of version 1.6 and it's far from finished. So as initial import to the git we can use the branch 1.5. >>> >>> And probally the easiest way to migrate our source code to the SystemImager git repo is to fork your repo. From there we can import our branch 1.5 to the forked git repo. And finally send you a pull request? >>> >>> Regards, >>> >>> Dennis >>> >>> >>> https://github.com/finley/systemimager >>> >>> Thanks! >>> >>> >>> On Tue, Nov 27, 2012 at 11:04 AM, Brian Elliott Finley <br...@th...<mailto:br...@th...>> wrote: >>> I think a move to github would be a fine idea. >>> >>> As for the SystemConfigurator functionality, I'd like to use the SystemImager post-script functionality. It will allow us to >>> - include simple scripts upstream, that could be used as-is for simple and common cases >>> - these simple scripts could be easily customized by site admins, without having to know SystemImager internals >>> - a simple script could be used to invoke puppet, chef, or SSM (Simple State Manager - http://download.systemimager.org/pub/ssm/README) >>> >>> Cheers, -Brian >>> >>> >>> >>> On Mon, Nov 26, 2012 at 5:28 AM, Bas van der Vlies <ba...@sa...<mailto:ba...@sa...>> wrote: >>> Brian, >>> >>> The SALI vork was nescessary to support modern hardware. Your are right you can better have one source. SALI has implemented a new kernel/initrd and some shell functions, e.g. one for easy disk partition. We also replaced the system imager-server software. >>> >>> Currently we do not have a tool like systemconfigurator or automatically generate installation scripts. So we can definitely benefit from co-operation. My thought for replacing systemconfigurator are with shell commands or a system maintenance tool like CFengine, puppet , chef ,…. >>> >>> Can we move the code to github.com<http://github.com/><http://github.com<http://github.com/>>. I think it easier to contribute and better suited if more people are involved. >>> >>> regards >>> >>> >>> On 23 nov. 2012, at 19:10, Brian Elliott Finley <br...@th...<mailto:br...@th...><mailto:br...@th...<mailto:br...@th...>>> wrote: >>> >>> Sun, Olivier, >>> >>> Please send me your SourceForge usernames. I appreciate your efforts, and would like to grant you both commit privileges to the SVN repository, so that you can commit your patches directly. >>> >>> Bas, Franck, the same goes for you two if you wish. >>> >>> >>> Regarding a fork, that is generally necessary because one does not have the ability to modify the upstream original. I will happily grant you this access, as I think it would be better for the community to improve the main code stream rather than to have a fork. I know that SALI has special circumstances that made a fork appropriate for them, at least previously, but I would also be happy to allow that fork to merge into the mainstream if SALI considers that desirable. >>> >>> >>> Lastly, with regard to SystemConfigurator, it is no longer being maintained, and we should work to eliminate our dependency on it. With modern Linuxes this should be very feasible through the use of SystemImager postscripts for setup of boot manager (Grub) and networking (if desirable). >>> >>> >>> All -- feel free to call me if you have any questions. Just bear in mind that I'm generally somewhere in GMT-5 through GMT-7. ;-) If unsure, start with a text message, or leave a voice mail if I don't answer right away, but I'll be glad to discuss. My mobile is 469.444.0167<tel:469.444.0167>. >>> >>> >>> Cheers, -Brian >>> >>> >>> >>> >>> >>> On Wed, Nov 21, 2012 at 1:16 AM, Jing CDL Sun <sj...@cn...<mailto:sj...@cn...><mailto:sj...@cn...<mailto:sj...@cn...>>> wrote: >>> Hi Olivier, >>> >>> Thanks for this sharing! >>> >>> Have you cloning Centos-6.3 with these rpms successfully? I tried to use them for redhat6.3 cloning, bug failed... >>> >>> ------------------------------------------------------------------------------ >>> Monitor your physical, virtual and cloud infrastructure from a single >>> web console. Get in-depth insight into apps, servers, databases, vmware, >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >>> Pricing starts from $795 for 25 servers or applications! >>> http://p.sf.net/sfu/zoho_dev2dev_nov >>> _______________________________________________ >>> sisuite-users mailing list >>> sis...@li...<mailto:sis...@li...><mailto:sis...@li...<mailto:sis...@li...>> >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users >>> >>> >>> >>> >>> -- >>> Brian Elliott Finley >>> Mobile: 469.444.0167<tel:469.444.0167> >>> ------------------------------------------------------------------------------ >>> Monitor your physical, virtual and cloud infrastructure from a single >>> web console. Get in-depth insight into apps, servers, databases, vmware, >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >>> Pricing starts from $795 for 25 servers or applications! >>> http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________ >>> sisuite-users<http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________sisuite-users> mailing list >>> sis...@li...<mailto:sis...@li...> >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users >>> >>> -- >>> Bas van der Vlies >>> mail: ba...@sa...<mailto:ba...@sa...><mailto:ba...@sa...<mailto:ba...@sa...>> >>> SARA - Academic Computing Services , Amsterdam, The Netherlands >>> >>> >>> ------------------------------------------------------------------------------ >>> Monitor your physical, virtual and cloud infrastructure from a single >>> web console. Get in-depth insight into apps, servers, databases, vmware, >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >>> Pricing starts from $795 for 25 servers or applications! >>> http://p.sf.net/sfu/zoho_dev2dev_nov >>> _______________________________________________ >>> sisuite-users mailing list >>> sis...@li...<mailto:sis...@li...> >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users >>> >>> >>> >>> -- >>> Brian Elliott Finley >>> Mobile: 469.444.0167<tel:469.444.0167> >>> >>> >>> >>> -- >>> Brian Elliott Finley >>> Mobile: 469.444.0167 >>> ------------------------------------------------------------------------------ >>> Monitor your physical, virtual and cloud infrastructure from a single >>> web console. Get in-depth insight into apps, servers, databases, vmware, >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >>> Pricing starts from $795 for 25 servers or applications! >>> http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________ >>> sisuite-users mailing list >>> sis...@li... >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users >>> >>> >>> ------------------------------------------------------------------------------ >>> Monitor your physical, virtual and cloud infrastructure from a single >>> web console. Get in-depth insight into apps, servers, databases, vmware, >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >>> Pricing starts from $795 for 25 servers or applications! >>> http://p.sf.net/sfu/zoho_dev2dev_nov >>> _______________________________________________ >>> sisuite-users mailing list >>> sis...@li... >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users >>> >>> >>> >>> -- >>> Brian Elliott Finley >>> Mobile: 469.444.0167 >> > > -- > Brian Elliott Finley > Mobile: 469.444.0167 -- Bas van der Vlies mail: ba...@sa... SARA - Academic Computing Services , Amsterdam, The Netherlands |
From: Brian E. F. <br...@th...> - 2012-12-18 18:31:30
|
Olivier -- I've added you to github now too. Cheers, -Brian On Tue, Dec 18, 2012 at 10:01 AM, LAHAYE Olivier <oli...@ce...>wrote: > > Hi, > > Brian, thanks for the svn access, it's cool now that I don't have to > maintain tons of patches ;-) > My github account is olahaye74. > > I've commited my modifications to the svn and tested a build and.... it > worked :-) I should say, it built ;-) > So now, as the version is 4.3.0 in the devel tree, the rpm version will be > 4.3.0-0.x > (4.3.0-1 when a release will be created). > > rpms available here http://olivier.lahaye1.free.fr/RPMS/noarch/ > srpms available here http://olivier.lahaye1.free.fr/SRPMS/ > > Note that they should behave the same as v 4.2.0-0.91svn4568 as the > current status is that I've commited the patch into the svn tree and > updated the spec file to reflect that there is no more patches + minor > modifications. > Hopefully I did not miss anything in the process. :-) > > The i386initrd_template and i386boot-standard and currently being build, > unfortunately, I'm on vaccation tonight and will only be back on january > 7th, if the build process is not finished when I'll have to leave, I'll > hybernate my VM and let the build finish later. > > Best regards, > > Olivier. > > > -- > Olivier LAHAYE > CEA DRT/LIST/DCSI/DIR > ------------------------------ > *De :* Brian Elliott Finley [br...@th...] > *Date d'envoi :* samedi 15 décembre 2012 18:49 > *À :* sis...@li... > *Objet :* Re: [sisuite-users] RE : new centos-6.3 RPMS > > Contributors, > > I have added Olivier to the SystemImager project on SourceForge, but I'd > like to add each of you who want to contribute to the SystemImager project > on GitHub too, as that's where it will all be moving. > > If you don't have an account yet, no big -- just go to https://github.comand create one. Then send me an email with your account name, and I'll get > you added. > > Thanks! > > -Brian > > > On Thu, Nov 29, 2012 at 3:56 AM, LAHAYE Olivier <oli...@ce...>wrote: > >> Hi Brian, >> >> My sourceforge username is "olahaye74" (Olivier LAHAYE) (74 is because >> there was plenty of olivier.lahaye in France ;-)) >> >> I'm very glad to participate. In the meantime, I must let you know that >> I'm not extremely skilled in perl/python and such. I've modified >> systemimager so it can deploy oscar on centos6. The RPMS I've released are >> ok on centos6, but I've discovered that they can't build on centos5. In >> fact, the build system (initrd) after compiling some package does complete >> the initrd by copying missing libs from the build host system. >> Unfortunately, this behaviour breaks things as we have some binaries linked >> with libs that are too far in versions to be compatible (missing simbols). >> >> What I want to say is that I'm a little bit afraid to make modifications >> that could break the whole stuff because my developper skills are not >> extreme (I'm sysadmin in 1st place). >> >> Also I've never participated in such a project and thus I'm not familiar >> with how such modifications can go to the svn. (and I don't want to break >> things) >> >> For example, I've had to upgrade a component, and to change the build >> script so it makes install instead of copying the resulting binaries as the >> new version uses libtool and the old copying method was copying the wrapper >> instead of the lib itself. This change had an impact to the centos5 >> compatibility. I mean, my modification let the thing build on centos6, but >> in the meantime, centos5 became incompatible... >> >> In the end, right now, my rpms cant be build on centos5, though, they can >> deploy any OS. This means that the deploy server must be centos6. >> >> Best resgards. >> >> >> >> -- >> Olivier LAHAYE >> CEA DRT/LIST/DCSI/DIR >> ------------------------------ >> *De :* Brian Elliott Finley [br...@th...] >> *Date d'envoi :* vendredi 23 novembre 2012 19:10 >> *À :* sis...@li... >> *Objet :* Re: [sisuite-users] new centos-6.3 RPMS >> >> Sun, Olivier, >> >> Please send me your SourceForge usernames. I appreciate your efforts, >> and would like to grant you both commit privileges to the SVN repository, >> so that you can commit your patches directly. >> >> Bas, Franck, the same goes for you two if you wish. >> >> >> Regarding a fork, that is generally necessary because one does not have >> the ability to modify the upstream original. I will happily grant you this >> access, as I think it would be better for the community to improve the main >> code stream rather than to have a fork. I know that SALI has special >> circumstances that made a fork appropriate for them, at least previously, >> but I would also be happy to allow that fork to merge into the mainstream >> if SALI considers that desirable. >> >> >> Lastly, with regard to SystemConfigurator, it is no longer being >> maintained, and we should work to eliminate our dependency on it. With >> modern Linuxes this should be very feasible through the use of SystemImager >> postscripts for setup of boot manager (Grub) and networking (if desirable). >> >> >> All -- feel free to call me if you have any questions. Just bear in mind >> that I'm generally somewhere in GMT-5 through GMT-7. ;-) If unsure, start >> with a text message, or leave a voice mail if I don't answer right away, >> but I'll be glad to discuss. My mobile is 469.444.0167. >> >> >> Cheers, -Brian >> >> >> >> >> >> On Wed, Nov 21, 2012 at 1:16 AM, Jing CDL Sun <sj...@cn...> wrote: >> >>> Hi Olivier, >>> >>> Thanks for this sharing! >>> >>> Have you cloning Centos-6.3 with these rpms successfully? I tried to use >>> them for redhat6.3 cloning, bug failed... >>> >>> >>> ------------------------------------------------------------------------------ >>> Monitor your physical, virtual and cloud infrastructure from a single >>> web console. Get in-depth insight into apps, servers, databases, vmware, >>> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >>> Pricing starts from $795 for 25 servers or applications! >>> http://p.sf.net/sfu/zoho_dev2dev_nov >>> _______________________________________________ >>> sisuite-users mailing list >>> sis...@li... >>> https://lists.sourceforge.net/lists/listinfo/sisuite-users >>> >>> >> >> >> -- >> Brian Elliott Finley >> Mobile: 469.444.0167 >> >> >> ------------------------------------------------------------------------------ >> Keep yourself connected to Go Parallel: >> VERIFY Test and improve your parallel project with help from experts >> and peers. http://goparallel.sourceforge.net >> _______________________________________________ >> sisuite-users mailing list >> sis...@li... >> https://lists.sourceforge.net/lists/listinfo/sisuite-users >> >> > > > -- > Brian Elliott Finley > Mobile: 469.444.0167 > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > sisuite-users mailing list > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > > -- Brian Elliott Finley Mobile: 469.444.0167 |
From: LAHAYE O. <oli...@ce...> - 2012-12-18 16:01:45
|
Hi, Brian, thanks for the svn access, it's cool now that I don't have to maintain tons of patches ;-) My github account is olahaye74. I've commited my modifications to the svn and tested a build and.... it worked :-) I should say, it built ;-) So now, as the version is 4.3.0 in the devel tree, the rpm version will be 4.3.0-0.x (4.3.0-1 when a release will be created). rpms available here http://olivier.lahaye1.free.fr/RPMS/noarch/ srpms available here http://olivier.lahaye1.free.fr/SRPMS/ Note that they should behave the same as v 4.2.0-0.91svn4568 as the current status is that I've commited the patch into the svn tree and updated the spec file to reflect that there is no more patches + minor modifications. Hopefully I did not miss anything in the process. :-) The i386initrd_template and i386boot-standard and currently being build, unfortunately, I'm on vaccation tonight and will only be back on january 7th, if the build process is not finished when I'll have to leave, I'll hybernate my VM and let the build finish later. Best regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________ De : Brian Elliott Finley [br...@th...] Date d'envoi : samedi 15 décembre 2012 18:49 À : sis...@li... Objet : Re: [sisuite-users] RE : new centos-6.3 RPMS Contributors, I have added Olivier to the SystemImager project on SourceForge, but I'd like to add each of you who want to contribute to the SystemImager project on GitHub too, as that's where it will all be moving. If you don't have an account yet, no big -- just go to https://github.com and create one. Then send me an email with your account name, and I'll get you added. Thanks! -Brian On Thu, Nov 29, 2012 at 3:56 AM, LAHAYE Olivier <oli...@ce...<mailto:oli...@ce...>> wrote: Hi Brian, My sourceforge username is "olahaye74" (Olivier LAHAYE) (74 is because there was plenty of olivier.lahaye in France ;-)) I'm very glad to participate. In the meantime, I must let you know that I'm not extremely skilled in perl/python and such. I've modified systemimager so it can deploy oscar on centos6. The RPMS I've released are ok on centos6, but I've discovered that they can't build on centos5. In fact, the build system (initrd) after compiling some package does complete the initrd by copying missing libs from the build host system. Unfortunately, this behaviour breaks things as we have some binaries linked with libs that are too far in versions to be compatible (missing simbols). What I want to say is that I'm a little bit afraid to make modifications that could break the whole stuff because my developper skills are not extreme (I'm sysadmin in 1st place). Also I've never participated in such a project and thus I'm not familiar with how such modifications can go to the svn. (and I don't want to break things) For example, I've had to upgrade a component, and to change the build script so it makes install instead of copying the resulting binaries as the new version uses libtool and the old copying method was copying the wrapper instead of the lib itself. This change had an impact to the centos5 compatibility. I mean, my modification let the thing build on centos6, but in the meantime, centos5 became incompatible... In the end, right now, my rpms cant be build on centos5, though, they can deploy any OS. This means that the deploy server must be centos6. Best resgards. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________ De : Brian Elliott Finley [br...@th...<mailto:br...@th...>] Date d'envoi : vendredi 23 novembre 2012 19:10 À : sis...@li...<mailto:sis...@li...> Objet : Re: [sisuite-users] new centos-6.3 RPMS Sun, Olivier, Please send me your SourceForge usernames. I appreciate your efforts, and would like to grant you both commit privileges to the SVN repository, so that you can commit your patches directly. Bas, Franck, the same goes for you two if you wish. Regarding a fork, that is generally necessary because one does not have the ability to modify the upstream original. I will happily grant you this access, as I think it would be better for the community to improve the main code stream rather than to have a fork. I know that SALI has special circumstances that made a fork appropriate for them, at least previously, but I would also be happy to allow that fork to merge into the mainstream if SALI considers that desirable. Lastly, with regard to SystemConfigurator, it is no longer being maintained, and we should work to eliminate our dependency on it. With modern Linuxes this should be very feasible through the use of SystemImager postscripts for setup of boot manager (Grub) and networking (if desirable). All -- feel free to call me if you have any questions. Just bear in mind that I'm generally somewhere in GMT-5 through GMT-7. ;-) If unsure, start with a text message, or leave a voice mail if I don't answer right away, but I'll be glad to discuss. My mobile is 469.444.0167<tel:469.444.0167>. Cheers, -Brian On Wed, Nov 21, 2012 at 1:16 AM, Jing CDL Sun <sj...@cn...<mailto:sj...@cn...>> wrote: Hi Olivier, Thanks for this sharing! Have you cloning Centos-6.3 with these rpms successfully? I tried to use them for redhat6.3 cloning, bug failed... ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ sisuite-users mailing list sis...@li...<mailto:sis...@li...> https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Brian Elliott Finley Mobile: 469.444.0167<tel:469.444.0167> ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: VERIFY Test and improve your parallel project with help from experts and peers. http://goparallel.sourceforge.net _______________________________________________ sisuite-users mailing list sis...@li...<mailto:sis...@li...> https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Brian Elliott Finley Mobile: 469.444.0167 |
From: LAHAYE O. <oli...@ce...> - 2012-12-18 09:03:31
|
Jing, You're perfectly right, the ext4 problem was related to default initrd. The build did not enable the ext4 module. It's fixed in last build. Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________ De : Jing CDL Sun [sj...@cn...] Date d'envoi : mardi 18 décembre 2012 06:35 À : LAHAYE Olivier Cc: sis...@li...; sis...@li... Objet : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Thx for the reply. When I used your build with 4.2.0-0.9svn4568, I did not run into this problem, so I'm thinking maybe this is not a missing module problem? When you said 4.2.0-0.91svn4568 fixed the ext4 missing problem, did you mean the default initrd? because it seems 4.2.0-0.9svn4568 worked fine for me without the ext4 issue. Yes, I did not use the systemimager default kernel and initrd, instead, I'm using my own kernel/initrd got from my golder client, it's rhel6.3, so I think it should work fine, right? LAHAYE Olivier <oli...@ce...> 2012/12/17 17:16 To Jing CDL Sun/China/IBM@IBMCN, cc "sis...@li..." <sis...@li...>, "sis...@li..." <sis...@li...> Subject RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support This means that your disk is not recognized. Did you use my install scripts (especially the pre-install). http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2 It modprobs some modules in order to see disks. I don't know my the systemimager initrd fails to automaticaly do that (did not have time to look at the problem). if you did use the script, it means that you need to modify it to have more modules inserted. Or, if your hardware is too recent (not supported by provided default kernel), then you'll need to use your own kernel for the moment. I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build will copy missing stuffs from /lib /lib64 and other places and thoses version are for a 2.6.x kernel, not a 3.X kernel. This is also the reason why build fails on CentOS5 cas the libs copied from system misses some symbols (too old). In order to safely upgrade systemimager to latest kernel, we need to modifiy the build process so it builds everything and link everything with it's material which is not fully the case for now. (it still copy stuffs from the build system root tree (convenient ugly dirty hack)). Hope this helps, Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________ De : Jing CDL Sun [sj...@cn...] Date d'envoi : lundi 17 décembre 2012 07:42 À : LAHAYE Olivier Cc: sis...@li...; sis...@li... Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Hi, I just tested these new rpms, but found the issues below, the install broken. Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel gpt || shellout Dec 17 14:42:36 x3550m4n02 kernel: sda: unknown partition table Thx. Jing LAHAYE Olivier <oli...@ce...> 2012/12/13 22:47 To "sis...@li..." <sis...@li...>, cc "sis...@li..." <sis...@li...> Subject [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Dear all, Here are my fixed systemimager rpms for centos-6.3 Now, the ext4 filesystem is fixed (the module was missing in the initrd image) I've tested this on recent hardware and it worked like a charm. Thoses RPMS are for testing purpose RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch SRPMS: http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm PS: Keep in mind that you need postinstall scripts (already posted here) to setup grub, network and other stuffs as systemconfiguratior is unable to handle latest linux technologies. Best regards, Olivier -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d_______________________________________________ sisuite-devel mailing list sis...@li... https://lists.sourceforge.net/lists/listinfo/sisuite-devel |
From: Jing C. S. <sj...@cn...> - 2012-12-18 05:36:00
|
Thx for the reply. When I used your build with 4.2.0-0.9svn4568, I did not run into this problem, so I'm thinking maybe this is not a missing module problem? When you said 4.2.0-0.91svn4568 fixed the ext4 missing problem, did you mean the default initrd? because it seems 4.2.0-0.9svn4568 worked fine for me without the ext4 issue. Yes, I did not use the systemimager default kernel and initrd, instead, I'm using my own kernel/initrd got from my golder client, it's rhel6.3, so I think it should work fine, right? LAHAYE Olivier <oli...@ce...> 2012/12/17 17:16 To Jing CDL Sun/China/IBM@IBMCN, cc "sis...@li..." <sis...@li...>, "sis...@li..." <sis...@li...> Subject RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support This means that your disk is not recognized. Did you use my install scripts (especially the pre-install). http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2 It modprobs some modules in order to see disks. I don't know my the systemimager initrd fails to automaticaly do that (did not have time to look at the problem). if you did use the script, it means that you need to modify it to have more modules inserted. Or, if your hardware is too recent (not supported by provided default kernel), then you'll need to use your own kernel for the moment. I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build will copy missing stuffs from /lib /lib64 and other places and thoses version are for a 2.6.x kernel, not a 3.X kernel. This is also the reason why build fails on CentOS5 cas the libs copied from system misses some symbols (too old). In order to safely upgrade systemimager to latest kernel, we need to modifiy the build process so it builds everything and link everything with it's material which is not fully the case for now. (it still copy stuffs from the build system root tree (convenient ugly dirty hack)). Hope this helps, Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR De : Jing CDL Sun [sj...@cn...] Date d'envoi : lundi 17 décembre 2012 07:42 À : LAHAYE Olivier Cc: sis...@li...; sis...@li... Objet : Re: [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Hi, I just tested these new rpms, but found the issues below, the install broken. Dec 17 14:42:36 x3550m4n02 logger: logger: parted -s -- /dev/sda mklabel gpt || shellout Dec 17 14:42:36 x3550m4n02 kernel: sda: unknown partition table Thx. Jing LAHAYE Olivier <oli...@ce...> 2012/12/13 22:47 To "sis...@li..." <sis...@li...>, cc "sis...@li..." <sis...@li...> Subject [Sisuite-devel] New systemimager rpms for centos6 with ext4 support Dear all, Here are my fixed systemimager rpms for centos-6.3 Now, the ext4 filesystem is fixed (the module was missing in the initrd image) I've tested this on recent hardware and it worked like a charm. Thoses RPMS are for testing purpose RPMS: http://olivier.lahaye1.free.fr/RPMS/noarch SRPMS: http://olivier.lahaye1.free.fr/SRPMS/systemimager-4.2.0-0.91svn4568.el6.src.rpm PS: Keep in mind that you need postinstall scripts (already posted here) to setup grub, network and other stuffs as systemconfiguratior is unable to handle latest linux technologies. Best regards, Olivier -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ sisuite-devel mailing list sis...@li... https://lists.sourceforge.net/lists/listinfo/sisuite-devel |
From: Brian F. <br...@th...> - 2012-12-18 00:16:11
|
You guys have been added! https://github.com/finley/systemimager If you can help by doing the initial import of SystemImager from SourceForge SVN, that would be great. Let me know if you need anything from me. Thanks, -Brian On 12/17/2012 03:42 AM, Bas van der Vlies wrote: > Brian, > > > My github account is: basvandervlies > Dennis github account: dstam > > > regards > > On 15 dec. 2012, at 18:52, Brian Elliott Finley <br...@th...> wrote: > >> Dennis, >> >> That sounds like a good path forward. Please send me github account names for you and Bas, and I'll add you to the SystemImager project. >> >> Cheers, -Brian >> >> >> >> On Tue, Nov 27, 2012 at 12:16 PM, Dennis Stam <Den...@sa...> wrote: >> Hi Brian, >> >> Great news to make SALI into SystemImager. It's better for both teams to join forces because we want to accomplish the same goal. >> >> On 27 nov. 2012, at 18:10, Brian Elliott Finley <br...@th...<mailto:br...@th...>> wrote: >> >> I've created the initial repo. Bas -- what do you need from me to move the code from SourceForce to github? >> >> Currently we started the development of version 1.6 and it's far from finished. So as initial import to the git we can use the branch 1.5. >> >> And probally the easiest way to migrate our source code to the SystemImager git repo is to fork your repo. From there we can import our branch 1.5 to the forked git repo. And finally send you a pull request? >> >> Regards, >> >> Dennis >> >> >> https://github.com/finley/systemimager >> >> Thanks! >> >> >> On Tue, Nov 27, 2012 at 11:04 AM, Brian Elliott Finley <br...@th...<mailto:br...@th...>> wrote: >> I think a move to github would be a fine idea. >> >> As for the SystemConfigurator functionality, I'd like to use the SystemImager post-script functionality. It will allow us to >> - include simple scripts upstream, that could be used as-is for simple and common cases >> - these simple scripts could be easily customized by site admins, without having to know SystemImager internals >> - a simple script could be used to invoke puppet, chef, or SSM (Simple State Manager - http://download.systemimager.org/pub/ssm/README) >> >> Cheers, -Brian >> >> >> >> On Mon, Nov 26, 2012 at 5:28 AM, Bas van der Vlies <ba...@sa...<mailto:ba...@sa...>> wrote: >> Brian, >> >> The SALI vork was nescessary to support modern hardware. Your are right you can better have one source. SALI has implemented a new kernel/initrd and some shell functions, e.g. one for easy disk partition. We also replaced the system imager-server software. >> >> Currently we do not have a tool like systemconfigurator or automatically generate installation scripts. So we can definitely benefit from co-operation. My thought for replacing systemconfigurator are with shell commands or a system maintenance tool like CFengine, puppet , chef ,…. >> >> Can we move the code to github.com<http://github.com/><http://github.com<http://github.com/>>. I think it easier to contribute and better suited if more people are involved. >> >> regards >> >> >> On 23 nov. 2012, at 19:10, Brian Elliott Finley <br...@th...<mailto:br...@th...><mailto:br...@th...<mailto:br...@th...>>> wrote: >> >> Sun, Olivier, >> >> Please send me your SourceForge usernames. I appreciate your efforts, and would like to grant you both commit privileges to the SVN repository, so that you can commit your patches directly. >> >> Bas, Franck, the same goes for you two if you wish. >> >> >> Regarding a fork, that is generally necessary because one does not have the ability to modify the upstream original. I will happily grant you this access, as I think it would be better for the community to improve the main code stream rather than to have a fork. I know that SALI has special circumstances that made a fork appropriate for them, at least previously, but I would also be happy to allow that fork to merge into the mainstream if SALI considers that desirable. >> >> >> Lastly, with regard to SystemConfigurator, it is no longer being maintained, and we should work to eliminate our dependency on it. With modern Linuxes this should be very feasible through the use of SystemImager postscripts for setup of boot manager (Grub) and networking (if desirable). >> >> >> All -- feel free to call me if you have any questions. Just bear in mind that I'm generally somewhere in GMT-5 through GMT-7. ;-) If unsure, start with a text message, or leave a voice mail if I don't answer right away, but I'll be glad to discuss. My mobile is 469.444.0167<tel:469.444.0167>. >> >> >> Cheers, -Brian >> >> >> >> >> >> On Wed, Nov 21, 2012 at 1:16 AM, Jing CDL Sun <sj...@cn...<mailto:sj...@cn...><mailto:sj...@cn...<mailto:sj...@cn...>>> wrote: >> Hi Olivier, >> >> Thanks for this sharing! >> >> Have you cloning Centos-6.3 with these rpms successfully? I tried to use them for redhat6.3 cloning, bug failed... >> >> ------------------------------------------------------------------------------ >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov >> _______________________________________________ >> sisuite-users mailing list >> sis...@li...<mailto:sis...@li...><mailto:sis...@li...<mailto:sis...@li...>> >> https://lists.sourceforge.net/lists/listinfo/sisuite-users >> >> >> >> >> -- >> Brian Elliott Finley >> Mobile: 469.444.0167<tel:469.444.0167> >> ------------------------------------------------------------------------------ >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________ >> sisuite-users<http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________sisuite-users> mailing list >> sis...@li...<mailto:sis...@li...> >> https://lists.sourceforge.net/lists/listinfo/sisuite-users >> >> -- >> Bas van der Vlies >> mail: ba...@sa...<mailto:ba...@sa...><mailto:ba...@sa...<mailto:ba...@sa...>> >> SARA - Academic Computing Services , Amsterdam, The Netherlands >> >> >> ------------------------------------------------------------------------------ >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov >> _______________________________________________ >> sisuite-users mailing list >> sis...@li...<mailto:sis...@li...> >> https://lists.sourceforge.net/lists/listinfo/sisuite-users >> >> >> >> -- >> Brian Elliott Finley >> Mobile: 469.444.0167<tel:469.444.0167> >> >> >> >> -- >> Brian Elliott Finley >> Mobile: 469.444.0167 >> ------------------------------------------------------------------------------ >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov_______________________________________________ >> sisuite-users mailing list >> sis...@li... >> https://lists.sourceforge.net/lists/listinfo/sisuite-users >> >> >> ------------------------------------------------------------------------------ >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov >> _______________________________________________ >> sisuite-users mailing list >> sis...@li... >> https://lists.sourceforge.net/lists/listinfo/sisuite-users >> >> >> >> -- >> Brian Elliott Finley >> Mobile: 469.444.0167 > -- Brian Elliott Finley Mobile: 469.444.0167 |
From: LAHAYE O. <oli...@ce...> - 2012-12-17 15:00:31
|
Ole, you're perfectly right, Looking at https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/pdf/Package_Manifest/Red_Hat_Enterprise_Linux-6-Package_Manifest-en-US.pdf I see none of the required packages. Wow, this is realy wired. no static libc in RHEL6?. So no way to create a static binary from RHEL6? Regarding the spec file from http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/glibc-2.12-1.80.el6_3.6.src.rpm , the static package should be built. Did redhat removed it by hand? Regarding device-mapper-devel, the package is created from http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/lvm2-2.02.72-8.el6_0.4.src.rpm => Same as above? did redhat removed the package? And, as you said, the gperf package has an src.rpm.but no binary and not in the list of rhel6 packages..... As for the real requirements, I think they are all required unfortunately:(though maybe I'm wrong and maybe we could modify source to avoid those requirements; honestly I can't tell for now) 1/ GPERF: ./initrd_source/build_dir/lib/modules/2.6.34.1-boel_v4.3.0/build/scripts/kconfig/Makefile:# The following requires flex/bison/gperf 2/ DEVICE-MAPPER-DEVEL: ./autoconf/configure.ac:AC_CHECK_HEADERS([libdevmapper.h],[have_libdevmapper=yes]) 3/ GLIBS-STATIC: ./build_dir/lib/modules/2.6.34.1-boel_v4.3.0/build/kernel/exit.c: * implemented by calling sys_wait4() from libc.a. I'm confident that if you rpmbuild --rebuild the missing packages (glibc, lvm2 and gperf), you should obtain the missing packages. I understand that it's not a perfect situation, but for now I'm afraid that it's the way to go. Maybe redhat has other optional repositories available? Looking at the packages list, only 3 static packages. maybe all static packages are on a specific repository? Or maybe redhat has removed most of them because of that: http://www.linuxtopia.org/online_books/rhel6/rhel_6_developer_guide/rhel_6_developer_lib.compatibility.static.html (I'm sorry, I don't even have a single redhat system since V4 as I had poor experience with support and things like this one, though I can easily understand that rhel is mandatory for you) hope this helps a little bit. Best regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR ________________________________________ De : Ole Holm Nielsen [Ole...@fy...] Date d'envoi : lundi 17 décembre 2012 14:51 À : sis...@li... Cc: LAHAYE Olivier Objet : Re: RE : [sisuite-users] RE : New systemimager rpms for centos6 with ext4 support Hi Olivier, > This is wired and I'm using standard distro CentOS-6 which is said to be a full RHEL-6 clone. In theory yes, but it seems there are differences!! I looked up the missing packages in the Red Hat Network (RHN): > Don't you have the following packages? (they should be part of RHEL6) > - gperf-3.0.3-9.1.el6.x86_64 gperf is in CentOS 6.3, but NOT in RHEL 6.3! Strangely, Red Hat does have the source RPM in http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/ but there are no binary RPMs from RHN. > - glibc-static-2.12-1.80.el6_3.6.x86_64 glibc-static is in CentOS 6.3, but NOT in RHEL 5 or 6! > - device-mapper-devel-1.02.74-10.el6_3.3.x86_64 device-mapper-devel is in CentOS 6.3, but NOT in RHEL 5 or 6! Unfortunately these differences are *not* documented in http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.3. I wonder if anyone can explain why CentOS decided to build these packages? I assume that you *really* need these packages for SystemImager? It would be better for RHEL6 sites if they could be omitted. If we must install these packages on RHEL6, I propose that documentation should be written referring people to the RPM downloads from CentOS mirrors. Thanks, Ole -- Ole Holm Nielsen Department of Physics, Technical University of Denmark |
From: Ole H. N. <Ole...@fy...> - 2012-12-17 13:52:00
|
Hi Olivier, > This is wired and I'm using standard distro CentOS-6 which is said to be a full RHEL-6 clone. In theory yes, but it seems there are differences!! I looked up the missing packages in the Red Hat Network (RHN): > Don't you have the following packages? (they should be part of RHEL6) > - gperf-3.0.3-9.1.el6.x86_64 gperf is in CentOS 6.3, but NOT in RHEL 6.3! Strangely, Red Hat does have the source RPM in http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/os/SRPMS/ but there are no binary RPMs from RHN. > - glibc-static-2.12-1.80.el6_3.6.x86_64 glibc-static is in CentOS 6.3, but NOT in RHEL 5 or 6! > - device-mapper-devel-1.02.74-10.el6_3.3.x86_64 device-mapper-devel is in CentOS 6.3, but NOT in RHEL 5 or 6! Unfortunately these differences are *not* documented in http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.3. I wonder if anyone can explain why CentOS decided to build these packages? I assume that you *really* need these packages for SystemImager? It would be better for RHEL6 sites if they could be omitted. If we must install these packages on RHEL6, I propose that documentation should be written referring people to the RPM downloads from CentOS mirrors. Thanks, Ole -- Ole Holm Nielsen Department of Physics, Technical University of Denmark |