Hi! On Sunday 07 October 2007 13:10, Qian Feng wrote: > Thank you very much! > I should build image for x86_64 first in my headnode, after that copy all > i386 rpms to /tftpboot/oscar/distro/centos-4.5-i386 and build image for i386 > with the i386 rpmlist. Is that what you mean?
You should have i386 and x86_64 repositories in /tftpboot/distro/centos-4.5-i386 and /tftpboot/distro/centos-4.5-x86_64, as well as in /tftpboot/oscar/rhel-4-i386 and /tftpboot/oscar/rhel-4-x86_64. Also you should have the /tftpboot/oscar/common-rpms repository set up. Then you go normally with the install. When you reach the "build oscar image" step, you will have the choice to build one centos-4.5-i386 or a centos-4.5-x86_64 image. Build both. Then define your nodes and assign them to the corresponding images. > what is the last paragraph of your response mean? when the nodes are booted, > is it possible that the node load incorrect image, such as x86_64 image for > a i386 node ? will the headnode detect the architecture of computer node > automatically and transfer the right image to it ? In some detail: cd /tftpboot cp /usr/share/systemimager/boot/i386/standard/initrd.img install-initrd-i386.img cp /usr/share/systemimager/boot/i386/standard/kernel install-kernel-i386 cp /usr/share/systemimager/boot/x86_64/standard/initrd.img install-initrd-x86_64.img cp /usr/share/systemimager/boot/x86_64/standard/kernel install-kernel-x86_64 Now create /tftpboot/install-i386 with the content: #--- install-i386 --- DEFAULT systemimager DISPLAY message.txt PROMPT 1 TIMEOUT 50 LABEL systemimager KERNEL install-kernel-i386 # adapt the IP address in the line below to that of your master node APPEND vga=extended initrd=install-initrd-i386.img root=/dev/ram noexec=off MONITOR_SERVER=192.168.120.4 MONITOR_CONSOLE=yes ramdisk_blocksize=1024 Also create /tftpboot/install-x86_64 with the content: #--- install-x86_64 --- DEFAULT systemimager DISPLAY message.txt PROMPT 1 TIMEOUT 50 LABEL systemimager KERNEL install-kernel-x86_64 # adapt the IP address in the line below to that of your master node APPEND vga=extended initrd=install-initrd-x86_64.img root=/dev/ram noexec=off MONITOR_SERVER=192.168.120.4 MONITOR_CONSOLE=yes ramdisk_blocksize=1024 Install on the master node the "netbootmgr" package. This is actually done automatically. But it would make sense to take the updated one from our trunk svn repository (svn co https://svn.oscar.openclustergroup.org/svn/oscar/trunk/packages/netbootmgr/distro/common-rpms) and update it on the master node (rpm -Uhv netbootmgr-1.7-1.noarch.rpm). Now edit the /etc/netbootmgr.conf file and modify the MENU lines. Add something like: MENU Install_32bit:install-i386 MENU Install_64bit:install-x86_64 MENU Localboot:localboot After you've defined the nodes and have assigned them to IP addresses and images, start netbootmgr. In the GUI change the "next boot action" of the 32 bit nodes to "Install_32bit". And that of the 64 bit nodes to "Install_64bit". Leave the netbootmgr GUI open. Start the nodes and watch them install. When they are done with the install they should actually automatically switch to "Localboot". Done. I'm not sure whether the "test cluster setup" step will work, especially the MPI tests could make trouble with the mixed setup you have. Regards, Erich ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Oscar-users mailing list Oscar-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-users
