3.0.0:
 * Added the AdvancedParser module created by Dennis Stam (SARA). This
   removed a lot of obsolete code and command line options. The new version
   is not compatible with the previous one.
   Author: Bas van der Vlies & Dennis Stam

 * New directory structure, added src directory.
   Author: Bas van der Vlies

 * Pxeconfig is now a python module and can be used inside python programs.
   Author: Bas van der Vlies

 * Added python setup method to support the new behaviour

=== Usage Example ===
Usage: pxeconfig [-f,--filename <name>] <hosts>

Specifying hostnames:
   To specify a range use the [] to indicate a range,
   a couple of examples:

   The first five nodes of rack 16
          - gb-r16n[1-5]

   The first five nodes and node 12 and 18 of rack 16 to 20
      - gb-r[16-20]n[1-5,12,18]

   The first five nodes de in rack 16 with padding enabled
          - gb-r[16]n[01-5]

The ranges ([]) are not only limited to numbers, letters can also be used.


=====================================================================

For more info about the package see the pxeconfig homepage:
   * https://subtrac.sara.nl/oss/pxeconfig

You can download the latest release from:
* ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz


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.


Comments or Suggestions mail them to:
pxeconfig at sara dot nl
http://www.sara.nl for more info about SARA.


-- 
********************************************************************
*  Bas van der Vlies                    e-mail: b...@sara.nl       *
*  SARA - Academic Computing Services   Amsterdam, The Netherlands *
********************************************************************

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to