Article Index

You will then be asked questions about the firewall. Make sure it is enabled and select the services that your want to allow to pass though (we chose http and ssh). In the "allow traffic from window" click eth1 and eth2. The firewall will consider these secure networks and let everything pass. (These interfaces are the internal cluster networks).

Once you finish up a few more questions, (use grub as your boot loader), Fedora should be installing on your master node. Again, assistance with Fedora installations can be found on various places in the Internet or from some of the hefty reference books. Now it is time to take a look at Sidebar Three.

Sidebar Three: Fedora will not boot, now what?
If you are using the same hardware as described in chapter one, there is a good chance FC2 will install, but when you boot it will die. Welcome to the &*#$* edge. The problem has to do with the video card driver. Here is how to fix it for now. Later we will update things and get X running properly.

When the system boots, and you see the Grub screen, press "e" (edit) and move to the line (use cursor keys):

kernel /boot/vmlinuz-2.6.5-1.358 ro root=/dev/md0 rhgb quiet
Backspace and remove the text rhgb quiet and replace it with single. Hit Enter, then "b" for boot. The system will then come up in single user mode. Edit the file "/etc/inittab" and change the line id:5:initdefault to id:3:initdefault. Next, edit the file /etc/grub.conf and remove the rhgb quiet from the "kernel" line. Save the file and reboot. The system should now come up in text mode and you can get on with the installation.

Getting What You Need Warewulf uses yum for many aspects of the cluster administration and installation. Some think yum is rpm done the right way. In any case, it is a powerful tool and saves a lot of problems when installing packages.

Warewulf is a very good cluster system for a number of reasons. One of them is that it creates a ramdisk that installs a vastly cut down version of the master node operating system. (Note: a ramdisk is a chunk of memory that has a file system created on it as though it were a hard disk). The size of the ramdisk really depends upon what is needed on the compute nodes, but the one that gets created for this cluster is about 60 MB in size.

Warewulf creates a file system that holds what is to be installed on the compute nodes. This file system, called the Virtual Node File System (VNFS), contains all of the files that Warewulf needs to place in the ramdisk on the compute nodes. Once Warewulf is installed on the master node you will see the VNFS in the directory /vnfs/default.

To build the VNFS, Warewulf may need access to the rpms from FC2. You can either use the Internet to fetch these files or you can load them into master node. In the later case, you will have to download all of the rpm's from the CDROM's onto the master node hard drive. If you installed from a DVD then you can either use the single DVD or the Internet. In any case, yum will need access to a FC2 rpm repository.

If you used CDROM's to install FC2 and your machine is not on the Internet (with a broadband connection), you will need to copy the contents of all CDROM's to a directory on the hard drive. Remember if you are connected to the Internet, this step is not required. First make a local directory to store the rpm's.

% mkdir /usr/src/RPM_LOCAL
Then insert disk 1 into the drive and run the following commands.
% mount /mnt/cdrom
% cp /mnt/cdrom/Fedora/RPMS/*.rpm /usr/src/RPM_LOCAL
% umount /mnt/cdrom

Once the machine is done copying the rpm's, remove disk 1. Repeat these last 3 commands for disks 2, 3, and 4. Then you modify the file /etc/yum.conf to reflect the location of the yum repositories (we haven't created them yet, but we will). The two entries in the file, base and updates-released should look like,

[base]
name=....
baseurl=file:///usr/src/RPM_LOCAL

[updates-released]
name=...
baseurl=file:///usr/src/RPM_LOCAL
If you have the master node connected the Internet, then you don't need to copy everything on the hard drive. The yum.conf file will have the appropriate entries to find the FC2 files.

If you don't have your master node on the network but installed from a DVD, then edit the file /etc/yum.conf so that the base and updates-released entries look like the following (make sure it is mounted when running yum):

[base]
name=....
baseurl=/mnt/cdrom/Fedora/RPMS

[updates-released]
name=...
baseurl=/mnt/cdrom/Fedora/RPMS
If your master node is connected the Internet, then you don't need to copy everything on the hard drive or use the FC2 DVD. The /etc/yum.conf file will have the appropriate entries to find the FC2 files.

Capturing the Warewulf

Now let's go get the Warewulf files from the Internet. Go to the following URL in your web browser (or use wget if you can not start a browser), and grab the following file:

warewulf-2.2.4-2.src.rpm
Then go to the following URL and grab the following file:
perl-Term-Screen-1.02-3.caos.src.rpm
Then go to the following URL and get the file,
dev-minimal-3.3.8-4.caos.i386.rpm
Put the files, warewulf-2.2.4-1 and perl-Term-Screen-1.02-2.caos.src.rpm into the directory /usr/src/redhat/SRPMS. Put the file dev-minimal-3.3.8-4.caos.i386.rpm into the directory, /usr/src/redhat/RPMS/i386.

Next, go to the directory, /usr/src/redhat/SRPMS and run the following commands,

% rpmbuild --rebuild warewulf-2.2.4-1.src.rpm
% rpmbuild --rebuild perl-Term-Screen-1.02-2.caos.src.rpm
These commands build the rpm's that Warewulf will need for installation.

We should be about ready to go, but first we need to create a yum repository for the Warewulf files so that we can easily install them. Run the following command as root,

% yum-arch -z /usr/src/redhat/RPMS

Next we need to let yum know where to find the new files. In the file /etc/yum.conf we need to yum where the Warewulf repository is located. After the entries for [updates-released] we will add an entry that looks the following:

[warewulf]
name=warewulf
baseurl=file:///usr/src/redhat/RPMS/

One last thing. If you copied the FC2 rpm's to your hard drive, you will have to build the yum repository for it. Just run the following command as root.

% yum-arch -z /usr/src/RPM_LOCAL

You have no rights to post comments

Search

Login And Newsletter

Create an account to access exclusive content, comment on articles, and receive our newsletters.

Feedburner


This work is licensed under CC BY-NC-SA 4.0

©2005-2023 Copyright Seagrove LLC, Some rights reserved. Except where otherwise noted, this site is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International. The Cluster Monkey Logo and Monkey Character are Trademarks of Seagrove LLC.