[sisuite-users] ANNOUNCE: New version of pxeconfig/pxemenu utilities (2.0.0)

2008-04-15 Thread Bas van der Vlies
2.0.0
  - Fixed a bug in -r/--remove option. Do not display
pxe filemame menu.
Author: Bas van der Vlies

  - pxeconfigd.xinetd in the example directory is created by
configure.
Implemented by : Bas van der Vlies  Ole Holm Nielsen

  - Fixed some spell errors
Author: Bas van der Vlies   Ole Holm Nielsen

  - Add new optione -w/--equal-width, eg:
 * pxeconfig -w --basename gb-r40n -s 9 -e 10 --filename default.install

Will create links to default.install for hosts:
 gb-r40n09
 gb-r40n10

Suggested by : Ole Holm Nielsen
Implemented by : Bas van der Vlies

  - Various bugs fixed with setting pxeconfig directory in pxeconfig.conf:
- Setting of the pxeconfig directory in config file did not have any effect
- Convert pxeconfig directory to realpath else os.chdir fails
Author: Bas van der Vlies

  - Fixed a bug in short option '-b' (basename) must have an argument.
Author: Bas van der Vlies

  - In analogue with systemimager we have the option:
 -H,--host-range number-number

It must be used in combinatiion with -b,--basebane, eg:
  pxeconfig --basename gb-r1n --host-range 1-2 -f default.memtest

will produce links to file default.memtest for these hosts
   - gb-r1n1
   - gb-r1n2

   If leading zeros are used, then host names will be padded with zeros.
  pxeconfig --basename gb-r1n --host-range 01-02 -f default.memtest

   will produce links to file default.memtest for these hosts
   - gb-r1n01
   - gb-r1n02

Suggested by : Ole Holm Nielsen
Implemented by : Bas van der Vlies

  - We do need the check for a C-compiler so remove it from the configure.in
and made a new configure
Author: Bas van der Vlies

  - Added -R,--rack and -N,--node option, eg:
  pxeconfig --basename gb- --rack r1-r2 --node n1-n2 -f default.memtest

  will produce links to file defaul.memtest for these hosts:
- gb-r1n1
- gb-r1n2
- gb-r2n1
- gb-r2n2

   If leading zeros are used, then rack and/or node names will be
padded with zeros, eg:
  pxeconfig --basename gb- --rack r01-r02 --node n01-n02 -f default.memtest

  will produce links to file defaul.memtest for these hosts:
- gb-r01n01
- gb-r01n02
- gb-r02n01
- gb-r02n02

Author: Bas van der Vlies

  - Added --dry-run mode
Author: Bas van der Vlies


=

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
  

Re: [sisuite-users] can not find .ROOTDEV /dev/ram under [BOOT]

2008-04-15 Thread Andrea Righi
Walter Tautz wrote:
 Thanks Andrea, I will endeavour to test it.
 
 When I run si_prepareclient --server x
 I get in /etc/systemconfig/systemconfig.conf:
 
 # more /etc/systemconfig/systemconfig.conf
 [BOOT]
 ROOTDEV = /dev/sda2
 BOOTDEV = /dev/sda
 DEFAULTBOOT = systemimager
 
 [KERNEL0]
 LABEL = systemimager
 PATH = /boot/vmlinuz-2.6.24-16-generic
 INITRD = /boot/initrd.img-2.6.24-16-generic
 APPEND =  ro single

This seems ok. Anyway, the problem was in the embedded
systemconfig.conf created by si_updateclient --autoinstall.

 
 where
 
 ii  systemimager-client   4.1.6
 Utilities for creating an image and upgradin
 ii  systemimager-common  4.1.6 Utilities
 and libraries common to both the s
 ii  systemimager-initrd-template-i386 4.1.6
 SystemImager initrd template for i386 client
 [EMAIL PROTECTED]:~# dpkg -l |grep systemonfigurator 
 2.2.12.svn716arighi   Unified Configuration API for Linux Installa

This should work.
 
 
 The image server has same version of systemconfigurator.
 
 Running on Ubuntu/i386/hardy
 
 walter
 
 ps. Thanks for looking into this! You're efforts are greatly appreciated.

Thanks,
-Andrea

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


[sisuite-users] Unrecognised option: ForceArray ... from si_mkclientnetboot?

2008-04-15 Thread Yu Chen
Hi,

When I am runing si_mkclientnetboot --netboot --clients test, I got this 
error:

[netboot] using the kernel and initrd.img for architecture: i386
[netboot] using the flavor: standard
Unrecognised option: ForceArray at 
/usr/lib/systemimager/perl/SystemImager/HostRange.pm line 103

I have googled and searched archive with no results. I have changed 
ForceArray to forcearray, which seems passed this error, but gave the 
following error instead:

Not an ARRAY reference at 
/usr/lib/systemimager/perl/SystemImager/HostRange.pm line 127.

Wondering if anybody can give some advices.

My systeim information:
RHEL AS 3, systemimager 4.0.2, perl 5.8.0

Thanks in advance.

CY


===
Yu Chen
Howard Hughes Medical Institute
Chemistry Building, Rm 182
University of Maryland at Baltimore County
1000 Hilltop Circle
Baltimore, MD 21250

phone:  (410)455-1728 (primary)
(410)455-6347 (secondary)
fax:(410)455-1174
email:  [EMAIL PROTECTED]
===

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [sisuite-users] Unrecognised option: ForceArray ... from si_mkclientnetboot?

2008-04-15 Thread Andrea Righi
Yu Chen wrote:
 Hi,
 
 When I am runing si_mkclientnetboot --netboot --clients test, I got this 
 error:
 
 [netboot] using the kernel and initrd.img for architecture: i386
 [netboot] using the flavor: standard
 Unrecognised option: ForceArray at 
 /usr/lib/systemimager/perl/SystemImager/HostRange.pm line 103
 
 I have googled and searched archive with no results. I have changed 
 ForceArray to forcearray, which seems passed this error, but gave the 
 following error instead:
 
 Not an ARRAY reference at 
 /usr/lib/systemimager/perl/SystemImager/HostRange.pm line 127.
 
 Wondering if anybody can give some advices.
 
 My systeim information:
 RHEL AS 3, systemimager 4.0.2, perl 5.8.0
 
 Thanks in advance.
 
 CY

Which version of XML::Simple are you using?

Check the changelog to see if your version supports the forcearray option:
http://search.cpan.org/src/GRANTM/XML-Simple-2.18/Changes

Otherwise, you need to update this perl module.

-Andrea

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users


Re: [sisuite-users] Unrecognised option: ForceArray ... from si_mkclientnetboot?

2008-04-15 Thread Yu Chen
 When I am runing si_mkclientnetboot --netboot --clients test, I got this
 error:

 [netboot] using the kernel and initrd.img for architecture: i386
 [netboot] using the flavor: standard
 Unrecognised option: ForceArray at
 /usr/lib/systemimager/perl/SystemImager/HostRange.pm line 103

 I have googled and searched archive with no results. I have changed
 ForceArray to forcearray, which seems passed this error, but gave the
 following error instead:

 Not an ARRAY reference at
 /usr/lib/systemimager/perl/SystemImager/HostRange.pm line 127.

 Wondering if anybody can give some advices.

 My systeim information:
 RHEL AS 3, systemimager 4.0.2, perl 5.8.0

 Thanks in advance.

 CY

 Which version of XML::Simple are you using?

 Check the changelog to see if your version supports the forcearray option:
 http://search.cpan.org/src/GRANTM/XML-Simple-2.18/Changes

 Otherwise, you need to update this perl module.

Thank you Andrea, you pointed me to the right direction. I have two perl 
installed, one installed manully, one installed from rpm. The XML-Simple 
in the manully installed one not working, but got found first, so ...

Thanks!

Chen


 -Andrea

 -
 This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
 Don't miss this year's exciting event. There's still time to save $100.
 Use priority code J8TL2D2.
 http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
 ___
 sisuite-users mailing list
 sisuite-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/sisuite-users



===
Yu Chen
Howard Hughes Medical Institute
Chemistry Building, Rm 182
University of Maryland at Baltimore County
1000 Hilltop Circle
Baltimore, MD 21250

phone:  (410)455-1728 (primary)
(410)455-6347 (secondary)
fax:(410)455-1174
email:  [EMAIL PROTECTED]
===

-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users