| Defining the resources
Each of the resources represents an element that will either be installed, or used as a set of directions on how to install a client node. Resources are created and then allocated to an installing node to show which elements are to be used to customize each individual node. Create a resource using the mklimr command, as in:
mklimr -n mykernel -t kernel -d /boot/vmlinuz
A description for each individual resource follows:
- kernel -- the kernel that your node will use to boot with on its first boot from local harddrive. If you are doing an rpm install, and specify a kernel rpm in your list of rpms to install, you do not need a separate kernel resource. If you are doing an rpm install, and specify a kernel resource as well, the kernel resource will overlay the kernel specified via the rpm.
- map -- the kernel map that is associated with the kernel that you are installing on the client node. The map contains a list of addresses used if you need to debug the kernel.
- disk (disk partition table) -- The table that defines how to partition the local harddrive on the node. It also tells if the harddrive is scsi, ide or raid. Refer to the README.disk for further details. This is a required resource.
- file (file systems) -- represents each individual file system to be installed on your node, and should relate to entries in the disk partition table. Your file systems can either be local (ext2) or remote using NFS. If you use remote file systems, you must export them in /etc/exports. When creating file systems, if you are using the rpm installation method, use the -c option of the mklimr command so that LUI does not create tar files for the file system. LUI requires file resources for the root (/) and /boot file systems. You might want other file systems, like /home, /usr and /var, depending on your needs.
- rpm -- this resource represents a list of rpms to be installed on the client for an rpm install. LUI provides sample rpm lists, though you will likely want to tailor your own rpm list(s).
- source -- the source resource represents a file that will be copied from the server to the client during the client installation process. I put this in specifically for rpm install, for the /etc/shadow file, since not all files get created when installing from rpms. This resource is supported only for rpm install, and is optional, but you do need /etc/shadow if you expect to log into your node. Follow the example in sample.script2.
- ramdisk -- the ramdisk is a resource used for specialized booting, particularly when the kernel does not support scsi. The ramdisk (the initrd file) resource is optional, and should only be used if you know what it is, and need it to boot your client.
- exit (user exit) -- if you would like to run a customization script on the first boot of the node from its local harddrive, create a user exit resource. Note that the exit is run only on the first boot of the node, not on subsequent reboots. When your user exit gets control, the permanent file system has been mounted, and all services should be available.
- postinstall -- Postinstall is a script which runs on the client just before it unmounts its hard
drives at the end of the install. It will run under the client environment where /mnt is the
directory that is the client server root.
See the mklimr man page for more info on any of these resources.
|