[3] | 1 | PXE-utilities |
---|
| 2 | ------------- |
---|
| 3 | |
---|
[9] | 4 | This is a release of the SARA package of utilities that we use to boot |
---|
| 5 | our nodes with PXE-enabled network cards. This was developed because we |
---|
| 6 | always want to use the PXE-enabled network card as our first boot device. |
---|
[10] | 7 | With pxelinux, which is a derivative of syslinux, you can specify with a PXE |
---|
| 8 | configuration file how the node must boot. This configuration is placed in, |
---|
| 9 | e.g. '/tftpboot/pxelinux.cfg' directory. |
---|
[3] | 10 | |
---|
[106] | 11 | The PXE-menu tools are used to control the booting of networked computers |
---|
| 12 | directly from the computer's console at the BIOS level before any operating |
---|
| 13 | system has been loaded. This is extremely useful for diagnostic purposes, |
---|
| 14 | or for selecting an operating system installation method, of an individual |
---|
| 15 | computer. For further information please read the files README-pxemenu and |
---|
| 16 | INSTALL-pxemenu. |
---|
| 17 | |
---|
[3] | 18 | In our setup we have a default setup. The default setup is to boot from |
---|
[11] | 19 | harddisk. When a node boots it fetches the default configuration file and the |
---|
[3] | 20 | configuration file tells the node to boot from the harddisk. This setup |
---|
[199] | 21 | is used for nodes that have already been installed by systemimager or sali |
---|
[3] | 22 | |
---|
[9] | 23 | At SARA we have developed the following strategy how to install a fresh node. |
---|
[3] | 24 | |
---|
| 25 | 1) The ip-address in our setup is known for the new node. So |
---|
| 26 | we make a link in the '/tftpboot/pxelinux.cfg' directory to a |
---|
| 27 | pxe config file which tells that it has to fetch the kernel en |
---|
| 28 | root filesystem from our bootserver, eg: |
---|
| 29 | 0A000A02 ---> default.node_install (10.0.10.2) |
---|
| 30 | |
---|
[199] | 31 | 2) The client starts and uses the systemimager or sali software to install |
---|
[3] | 32 | the node. The last line of installation script connects to a |
---|
| 33 | daemon on the bootserver. This daemon will remove the PXE config file |
---|
| 34 | for this node. |
---|
| 35 | |
---|
| 36 | 3) The node reboots and will use the default pxe config file which will |
---|
| 37 | instruct the node to boot from harddisk. |
---|
| 38 | |
---|
| 39 | This release contains the following utilities: |
---|
| 40 | |
---|
| 41 | pxeconfigd) |
---|
| 42 | This is daemon that removes the pxe configuration file of a node. |
---|
| 43 | |
---|
| 44 | pxeconfig) |
---|
[22] | 45 | With this program we can specify which pxe config file |
---|
[3] | 46 | a node or nodes must use. This utility will create the links |
---|
| 47 | in '/tftpboot/pxelinux.cfg' |
---|
| 48 | |
---|
| 49 | hexls) |
---|
[9] | 50 | Is a utility that diplays a directory, and, if in this directory |
---|
| 51 | contains HEX files, it will convert them to IP-numbers. |
---|
[3] | 52 | |
---|
[9] | 53 | All these utilities are written in Python. |
---|
[3] | 54 | |
---|
[33] | 55 | |
---|
[95] | 56 | For more info about the Packag and installation: |
---|
| 57 | https://subtrac.sara.nl/oss/pxeconfig |
---|