1.0.0
- List of pxeconfig files are now sorted alphabetically
- Use GNU getopt. This means that option and non-option arguments may be
intermixed.
- hexls now sorts its output
Suggested by : Ole Holm Nielsen
Implemented by : Bas van der Vlies
- hexls now also display link info for hex files shorter dan 8 characters.
Some hex files can point to a subnet IP adddress
Suggested by : Ole Holm Nielsen
Implemented by : Bas van der Vlies
- Added -b/--basename option. This is for host with a common prefix, eg:
pxeconfig --basename gb-r40n --start 1 --end 2 --filename default.install
Will create links to default.install for hosts:
gb-r40n1
gb-r40n2
Implemented by: Bas van der Vlies
- Added pxe-menu tools:
"""
The PXE-menu tools are used to control the booting of networked computers
directly from the computer's console at the BIOS level before any operating
system has been loaded. This is extremely useful for diagnostic purposes,
or for selecting an operating system installation method, of an individual
computer. For further information please read the files README-pxemenu and
INSTALL-pxemenu.
"""
Implemented by: Ole Holm Nielsen
Here is the README:
=====================================================================
PXE-utilities
-------------
This is a release of the SARA package of utilities that we use to boot
our nodes with PXE-enabled network cards. This was developed because we
always want to use the PXE-enabled network card as our first boot
device. With pxelinux, which is a derivative of syslinux, you can
specify with a PXE configuration file how the node must boot. This
configuration is placed in, e.g. '/tftpboot/pxelinux.cfg' directory.
The PXE-menu tools are used to control the booting of networked computers
directly from the computer's console at the BIOS level before any operating
system has been loaded. This is extremely useful for diagnostic purposes,
or for selecting an operating system installation method, of an individual
computer. For further information please read the files README-pxemenu and
INSTALL-pxemenu.
In our setup we have a default setup. The default setup is to boot from
harddisk. When a node boots it fetches the default configuration file
and the configuration file tells the node to boot from the harddisk.
This setup is used for nodes that have already been installed by
systemimager.
At SARA we have developed the following strategy how to install a fresh
node.
1) The ip-address in our setup is known for the new node. So
we make a link in the '/tftpboot/pxelinux.cfg' directory to a
pxe config file which tells that it has to fetch the kernel en
root filesystem from our bootserver, eg:
0A000A02 ---> default.node_install (10.0.10.2)
2) The client starts and uses the systemimager software to install
the node. The last line of installation script connects to a
daemon on the bootserver. This daemon will remove the PXE config
filefor this node.
3) The node reboots and will use the default pxe config file which
will instruct the node to boot from harddisk.
This release contains the following utilities:
pxeconfigd)
This is daemon that removes the pxe configuration file of a node.
pxeconfig)
With this program we can specify which pxe config file
a node or nodes must use. This utility will create the links
in '/tftpboot/pxelinux.cfg'
hexls)
Is a utility that diplays a directory, and, if in this directory
contains HEX files, it will convert them to IP-numbers.
All these utilities are written in Python.
Comments or Suggestions mail them to:
pxeconfig at sara dot nl
http://www.sara.nl for more info about SARA.
-------------------------------------------------------------------------
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/
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
