Next: Run mk-sysimage
Up: Installation
Previous: Dependencies and requirements
Contents
Preparing the master image
Before any nodes can be booted, a `master image' must be created that will be
shared across all nodes of the cluster. A filesystem image,
normally an installation of some Linux distribution, must be copied into an
NFS-exportable directory to serve as the image of the cluster.
Creating the master image from an installed linux machine is a
simple process, although it can take some time to copy such a large
volume of data. The copy-rootfs script (section
6.3) automates the details of copying a root
filesystem from the local machine, or from a
remote machine with an ssh daemon running.
After it has been prepared, this master image will serve as the
root filesystem for all cluster nodes. Copies are used on diskful
nodes, and the image itself is NFS mounted read-only on diskless
nodes.
Procedure 2 Create a root image
- Method 1: Creating an image from the local machine
-
This will copy the root filesystem of the local machine into
/var/lib/oneSIS/image
# copy-rootfs -l /var/lib/oneSIS/image
- Method 2: Creating an image from a remote machine
-
For a remote machine named rook, this will copy the root filesystem
of the remote machine into /var/lib/oneSIS/image, excluding the remote
/home directory.
# copy-rootfs -r rook -e /home /var/lib/oneSIS/image
Note: If it wasn't installed on the remote machine, oneSIS will need to
be installed in the image. In the oneSIS source directory, run
# cd oneSIS-2.0rc10
# prefix=/var/lib/oneSIS/image make install
Also note: If the local machine and the image use different versions of
Perl, it may be necessary to chroot into the image before installing oneSIS.
This will ensure that the oneSIS perl module is installed under the right
directory in /usr/lib/perl.
# cp -a oneSIS-2.0rc10 /var/lib/oneSIS/image/usr/local/src
# chroot /var/lib/oneSIS/image
# cd /usr/local/src/oneSIS-2.0rc10
# make install
# exit
- Warning: Check /dev in the image
for existence of device files
-
If /dev of the machine
the image was copied from is not static (ie: managed by udev
or devfs), it will not get copied over. You may need to
manually copy /dev into your image. This will be fixed in a
future release.
Although diskful machines can mount their local root filesystems in
read-write mode, for the sake of uniformity it is preferred that the
nodes be treated as if they were diskless and mount the root
filesystem read-only, especially if they are intended to serve the
image to more diskless nodes. Any necessary filesystem alterations
can be made in the master image, and synchronizing diskful nodes
with the master image is accomplished easily with the
sync-node script (section 6.6).
Subsections
Next: Run mk-sysimage
Up: Installation
Previous: Dependencies and requirements
Contents
root
2005-06-19