[sisuite-users] RE : RE : RE : new centos-6.3 RPMS
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...@thefinleys.com] Date d'envoi : mardi 18 décembre 2012 19:31 À : sisuite-users@lists.sourceforge.net 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 olivier.lah...@cea.frmailto:olivier.lah...@cea.fr 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...@thefinleys.commailto:br...@thefinleys.com] Date d'envoi : samedi 15 décembre 2012 18:49 À : sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net 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 olivier.lah...@cea.frmailto:olivier.lah...@cea.fr 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...@thefinleys.commailto:br...@thefinleys.com] Date d'envoi : vendredi 23 novembre 2012 19:10 À : sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net 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
[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 : david.livingst...@cn.ca [david.livingst...@cn.ca]
Date d'envoi : mercredi 19 décembre 2012 00:09
À : sisuite-users@lists.sourceforge.net
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: david.livingst...@cn.ca
- Forwarded by David Livingstone/LIVING03/CNR/CA on 2012/12/18 16:00 -
From: David Livingstone/LIVING03/CNR/CA
To: sisuite-users@lists.sourceforge.net
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://h2.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 ) .
[sisuite-users] RE : RE : RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support
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.ibm.com]
Date d'envoi : jeudi 27 décembre 2012 08:51
À : LAHAYE Olivier
Cc: sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
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 olivier.lah...@cea.fr
2012/12/18 17:03
To
Jing CDL Sun/China/IBM@IBMCN,
cc
sisuite-de...@lists.sourceforge.net
sisuite-de...@lists.sourceforge.net, sisuite-users@lists.sourceforge.net
sisuite-users@lists.sourceforge.net
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.ibm.com]
Date d'envoi : mardi 18 décembre 2012 06:35
À : LAHAYE Olivier
Cc: sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
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 olivier.lah...@cea.fr
2012/12/17 17:16
To
Jing CDL Sun/China/IBM@IBMCN,
cc
sisuite-de...@lists.sourceforge.net
sisuite-de...@lists.sourceforge.net, sisuite-users@lists.sourceforge.net
sisuite-users@lists.sourceforge.net
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.ibm.com]
Date d'envoi : lundi 17 décembre 2012 07:42
À : LAHAYE Olivier
Cc: sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
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 olivier.lah...@cea.fr
2012/12/13 22:47
To
sisuite-users@lists.sourceforge.net
sisuite-users@lists.sourceforge.net,
cc
sisuite-de...@lists.sourceforge.net
Re: [sisuite-users] RE : Which version ?
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 -- 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 sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
