You can subscribe to this list here.
| 2006 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Dror H. <Dro...@ql...> - 2007-02-15 13:46:46
|
Hello all, =20 =20 We are happy to announce Matt Rechenburg as the new project manager for the openQRM project. =20 Please welcome him at his new position ! =20 The openQRM team. |
|
From: matt <ma...@ql...> - 2006-02-08 10:40:32
|
Hi again Isha,
ok, from what i can see there seems to be a lot modules
in the 2.6.9-1.667smp kernel you are using.
The initrd for the boot-image is created dynamically
during "qrm-boot-image create ..". It always reserves
some free space on the initrd for eventually additional
tools being added later (e.g. for iscsi).
The check for the final initrd size is done in the qrm-boot-image
script itself -> it checks for > 32mb because this is the maximal
ramdisk size configured in the nodes pxe-config files
( [your-base-dir]/qrm/tftpboot/pxelinux.cfg/[mac-address] or default )
In your case this check detects "just a few bytes" more than allowed.
For now i would recommend to you to edit the qrm-boot-image script,
find the line :
QRM_INITRD_SIZE=$(( QRM_INITRD_SIZE + 16000 ))
and comment it out to
#QRM_INITRD_SIZE=$(( QRM_INITRD_SIZE + 16000 ))
This should make the the size-check return fine and will not cause
and problems (i think) because the resulting initrd size will
still be less than the 32mb.
btw: the next release will have a fix for that.
The number of modules copied to the intird was decreased.
Many thanks for your feedback !
Will re-check especially against the fedora core 4 distribution.
all the best,
Matt
isha b wrote:
> Hi Matt,
>
> Thanks a lot ..
>
> Below is the output for the command, qrm/bin/qrm-boot-image create -k
> `uname -r` -b qrm -y qrm
>
> [root@OpenQRM /]# /usr/qrm/bin/qrm-boot-image create -k `uname -r` -b
> qrm -y qrm
>
> Creating boot-image qrm from kernel version 2.6.9-1.667smp
>
> Copying kernelfile /boot/vmlinuz-2.6.9-1.667smp
>
> Copying the System.map /boot/System.map-2.6.9-1.667smp
>
> Creating modules package from /lib/modules/2.6.9-1.667smp
>
> Found nfs.ko module and will use it
>
> Found lockd.ko module and will use it
>
> found sunrpc.ko module and will use it
>
> Found ext3.ko module and will use it
>
> Found jbd.ko module and will use it
>
> Found reiserfs.ko module and will use it
>
> Found crc32c.ko module and will use it
>
> Found libcrc32c.ko module and will use it
>
> Found loop.ko module and will use it
>
> unzipping the initrd-template
>
> copying linuxrc + qrm-files to the initrd
>
> checking initrd-size
>
> Could not create initrd! File-size limit for exceeds! (32316 Kb requested)
>
> ERROR: Could not create the boot-image
>
> [root@OpenQRM /]#
>
>
>
>
>
> I have tried to increase the initrd size under .Conf but it doesn't help.
>
>
>
>
>
> Meantime I will trying to add the Linux client using the second
> option you given.
>
>
>
> Thanks n Regards,
>
> Isha
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 2/8/06, *matt* <ma...@ql... <mailto:ma...@ql...>> wrote:
>
> Hi Isha,
>
> the openQRM installation creates a default boot-image
> from the kernel running on the server. This boot-image
> is then used to remote-boot linux-clients by pxe.
> Such booted nodes will automatically have the openQRM
> client software running by a special boot-services mechanism.
>
> In case you got an error message for the default-boot-image
> creation could you please run :
>
> [your-basedir]/qrm/bin/qrm-boot-image create -k `uname -r` -b qrm
> -y qrm
>
> and send the output ?
>
> There is also the option to add the openQRM client software
> to local booted (linux-) nodes. It is called "easy-migration"
> and you can find the related programs in :
> [your-base-dir]/qrm/bin/easymigration/easymigration.tgz
> Untar this on a local booted system and run the script
> in /usr/qrm/bin/easymigration/qrm-configure-node-monitor.
> This will add the openQRM client software to the system
> and register the node in the server.
>
> hope it helps,
>
> Matt
>
>
> isha b wrote:
>
> > Hi all
> >
> >
> > I have installed OpenQRM on Fedora core 4 distribution. But while
> > installing OpenQRM recieved error mesage about image size too large
> > and unable to create boot image. But from /usr/qrm/etc/init.d I am
> > able to start QRM server by running ./qrm-server start. As a
> result I
> > am able to add windows clients and QRM webpage displays the same.
> >
> >
> > Problem : I didn't find any client software for unix ( linux /
> solaris
> > etc ) clients . Does anybody know how to add unix clients to
> OpenQRM
> > server ?
> >
> > Thanks in Advance
> > Isha
>
>
>
> --
> www.openQRM.org <http://www.openQRM.org>
> - Keeps your Data-Center Up and Running
>
>
>
--
www.openQRM.org
- Keeps your Data-Center Up and Running
|
|
From: matt <ma...@ql...> - 2006-02-08 09:57:25
|
Hi Isha, the openQRM installation creates a default boot-image from the kernel running on the server. This boot-image is then used to remote-boot linux-clients by pxe. Such booted nodes will automatically have the openQRM client software running by a special boot-services mechanism. In case you got an error message for the default-boot-image creation could you please run : [your-basedir]/qrm/bin/qrm-boot-image create -k `uname -r` -b qrm -y qrm and send the output ? There is also the option to add the openQRM client software to local booted (linux-) nodes. It is called "easy-migration" and you can find the related programs in : [your-base-dir]/qrm/bin/easymigration/easymigration.tgz Untar this on a local booted system and run the script in /usr/qrm/bin/easymigration/qrm-configure-node-monitor. This will add the openQRM client software to the system and register the node in the server. hope it helps, Matt isha b wrote: > Hi all > > > I have installed OpenQRM on Fedora core 4 distribution. But while > installing OpenQRM recieved error mesage about image size too large > and unable to create boot image. But from /usr/qrm/etc/init.d I am > able to start QRM server by running ./qrm-server start. As a result I > am able to add windows clients and QRM webpage displays the same. > > > Problem : I didn't find any client software for unix ( linux / solaris > etc ) clients . Does anybody know how to add unix clients to OpenQRM > server ? > > Thanks in Advance > Isha -- www.openQRM.org - Keeps your Data-Center Up and Running |
|
From: isha b <is...@gm...> - 2006-02-08 06:27:11
|
Hi all I have installed OpenQRM on Fedora core 4 distribution. But while installin= g OpenQRM recieved error mesage about image size too large and unable to create boot image. But from /usr/qrm/etc/init.d I am able to start QRM server by running ./qrm-server start. As a result I am able to add windows clients and QRM webpage displays the same. Problem : I didn't find any client software for unix ( linux / solaris etc = ) clients . Does anybody know how to add unix clients to OpenQRM server ? Thanks in Advance Isha |