Hi DongInn,
Cool to see you again; Thanks for your compliment :-)
I've updated several package since yesterday:
opkg-blcr-1.0.2-1.noarch.rpm
blcr-modules_2.6.32_279.el6.x86_64-0.8.4-2.x86_64.rpm
opkg-munge-1.0.4-1.noarch.rpm
opkg-munge-server-1.0.4-1.noarch.rpm
opkg-munge-client-1.0.4-1.noarch.rpm
opkg-torque-2.1.17-1.noarch.rpm
opkg-torque-server-2.1.17-1.noarch.rpm
opkg-torque-client-2.1.17-1.noarch.rpm
openmpi-switcher-modulefile-1.6.3-2.el6.noarch.rpm
I'm sorry with so much updates, but I'm fighting bugs one by one and I'll GET
ALL OF THEM ;-) (at least the most obvious ones ;-))
More seriously, I understand your point on the deployment solution, but before
I need to fix many issues that are revealed by step 8 in fact. For example,
some services are not enabled and running on nodes and step 7 fails sometimes
without error and some services are left unconfigured. Such things will lead to
many user requests, and since I'm in the code with a clear view, I'd prefer
finish most issues.
(for non crutial issues, I add the issue to my todolist. For example, the
openmpi-siwthc-module-file fails to detect the blcr lib because it checks for
/usr/lib64/libcr.so instead of /usr/lib64/libcr.so.0. I just added .0 the the
check code for the moment and added to my todo list to improve the libcr
detection routine.
I'm updated the systemimager 4.2.0-0.92 rpm which should work better than
nothing. For sure, I'll work on the git repo of systemimager soon to have it
work with more recent kernel and most important have an udev that actually load
the required modules. (the issue is that the current systemimager fails to load
modules because udev needs the full modprobe binary and is incompatible with
the busybox binary. (the git code already have that, unfortunately, udev fails
to compile because it uses system kernel headers instead of systemimager
compiled kernel headers. for example it includes input.h which includes
linux/input.h. IMHO, I'll copy all the systemimcludes in the systemimager build
tree before doing installs and add the -I option that will uses those includes.
it's dirty, but should work.
Best regards.
PS: I've also uploaded a few things in the download directory:
blcr-0.8.4-2.src.rpm
openmpi-switcher-modulefile-1.6.3-2.el6.src.rpm
Olivier.
--
Olivier LAHAYE
CEA DRT/LIST/DCSI/DIR
________________________________
De : DongInn Kim [di...@cs.indiana.edu]
Date d'envoi : mercredi 27 février 2013 16:56
À : oscar-users@lists.sourceforge.net
Objet : Re: [Oscar-users] RE : RE :OSCAR on CentOS-6: how to test.(Warning,
experimental) WAS:Re: OSCAR on CentOS-6: bootstrap successfull using online
repository.
Hi,
It seems that the new repository and trunk version codes work fine with CentOS
6.3 X86_64. :-) I have not fully gone through the deployment steps because I do
not have the test client nodes but I believe that it would work. I have
actually deployed my image on ubuntu 12.04 a few weeks ago. (I spent several
weeks in making the right initrd image.)
I do not really care about the step 7 and step 8 in oscar_wizard because the
cluster is deployed with my image and I have all the tools to manage them as I
wish.
Usually I spend most times in deploying my oscar image to the client nodes
because there are several issues of configuring the SIS image.
- hard to inject the missing kernel module to the generated initrd image (e.g.,
especially network kernel module is not loaded and a client node can not get
the oscar image after pxeboot).
- the firmware place where a kernel module look at is not correct
- ext4 fs is not supported
- a file with the hexdecimal file name representing the client's IP address is
not automatically generated on /tftpboot/pxelinux.cfg/ as soon as a client node
is imaged. If the hexdecimal file is generated, the client node whose IP
address is related to the hexdecimal would not be re-imaged when it is rebooted.
I know that this is not a pure oscar issue but more like the SIS issues.
If we want to make OSCAR more reliable and useful, I think we'd better spend
more time on the deployment solutions but not too much on the particular OSCAR
packages.
Once we have a solid deployment solutions, we can expand anything as we wish.
Thanks Olivier for his hard work.
BTW, would it work if i update the OSCAR repository only with your opkg-munge?
Regards,
--
- DongInn
On Feb 27, 2013, at 8:04 AM, LAHAYE Olivier
<olivier.lah...@cea.fr<mailto:olivier.lah...@cea.fr>> wrote:
Cool,
I've found a problem in the opkg-munge-* packages. I've just updated it.
(V1.0.3) Please use that if possible. If not, just before step 7 do a service
munge start on the head and on all nodes.
I'm currently checking that it's now ok. (it's a wired voodoo problem... munge
is one of the easiest thing to configure and the one that gave me most
problems... I need holidays ;-))
PS: don't forget to fix you /var/lib/systemimager/scripts/*.master line 190 if
it has been generated with pre 4.2.0-0.92 version.
Best regards,
Olivier.
--
Olivier LAHAYE
CEA DRT/LIST/DCSI/DIR
________________________________
De : Costel Seitan [csei...@slb.com<mailto:csei...@slb.com>]
Date d'envoi : mercredi 27 février 2013 13:48
À : LAHAYE Olivier
Cc: oscar-users@lists.sourceforge.net<mailto:oscar-users@lists.sourceforge.net>
Objet : RE: RE :OSCAR on CentOS-6: how to test.(Warning, experimental) WAS:Re:
OSCAR on CentOS-6: bootstrap successfull using online repository.
Hi Olivier,
I updated my packages with yum and even installed munge packages. Now
the right version of system imager is installed.
I see the official repo has been updated with your last packages built on
yesterday so I used that one.
I will transfer the last pre- and post-install scripts to
/var/lib/systemimager/scripts/ and then
try again the Oscar wizard.
I will check the dhcpd.conf as you recommended.
Thank you for your help,
Kind regards,
Costel SEITAN
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Oscar-users mailing list
Oscar-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-users
