Re: [Systemimager] [Sisuite-users] mkclientnetboot doesn't
Mark, Which version of systemimager do you use? Only version 3.X support this systemimager.conf) NET_BOOT_DEFAULT = local If you have 2.X version (it also works for 3.x). There is software for it: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz There is a good description available at: http://www.fysik.dtu.dk/CAMP/Niflheim/systemimager.html Mark Seger wrote: From my reading of the description of this on some web pages (the only local documentation is to run the command with -help, but I'm sure everyone already knows this) all I need to do is run the command mkclientnetboot -all-clients and whenever I do a brand new installation over the network, it will do a pxe boot/install. however, upon rebooting the client, it will NOT do the install agaig but rather boot off the hard drive. well, on my machine it does another install. I know the first installation worked because it exited cleanly and when I disabled network boot, the cleint booted a valid system from the hard drive. I suspect I may be doing things in the wrong order, but I have no idea what that order is. Specifically, I ran mkclientnetboot after I did the mkbootserver on the image server. Am I supposed to do anything on the image server after the client successfully installs? My reading was that you didn't have to. I even tried rebooting the server after issuing the mkclientnetboot (I know, this isn't microsoft) and that didn't help either. so close... -mark -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] [Sisuite-users] Network installations
Mark Seger wrote: Having been manually able to make the pieces work, sort of, I'd like to know HOW people actually use SI. Specifically, if I have a rack of systems I want to install a golden image on, I'd like to simply be able to set their bios to do a network install, power them up (I assume not all at once so I don't flood the image server) and after some point in time have runnable systems. Is this what other people do? That is the way to do it. The reason I ask is the once piece needed to make this work, doesn't. Specifically, if I set the NET_BOOT_OPTION in systemimager.conf to 'local' before doing the network installation, the systems install fine, and when I reboot them they try to boot off local disk, but they hang at the message telling me they're booting off the disk. Since there's really no detailed documentation on how all this works I'm left to conclude: - I'm doing something wrong - maybe it's a bug with redhat 9.0 - it's broken and doesn't really work There is also references to mkclientnetboot, but that's not really documented either and although I ran it I'm not sure what (if anything) it does... Did you also configure the PXE-network cards? You must enable local boot option (We have the Intel eepro100 cards). In the /tftpbooot/pxelinu.cfg there is also file named: syslinux.cfg.noboot I do not use this setup so the file maybe named something different. So if this doesn't work, how do people install a rack of systems? The machines I'm using allow you to interrupt the boot process with F12 to tell it to do a network boot, so I can leave the bios set to boot off disk before the network and all works fine, but that requires manual intervention with each machine which I'd think defeats the high level idea behind SI, especially if I want to install severl hundred (or thousand) images. Any and all comments would be appreciated. -mark -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] [Sisuite-users] Network installations
Mark Seger wrote: Bas van der Vlies wrote: Mark Seger wrote: Having been manually able to make the pieces work, sort of, I'd like to know HOW people actually use SI. Specifically, if I have a rack of systems I want to install a golden image on, I'd like to simply be able to set their bios to do a network install, power them up (I assume not all at once so I don't flood the image server) and after some point in time have runnable systems. Is this what other people do? That is the way to do it. The reason I ask is the once piece needed to make this work, doesn't. Specifically, if I set the NET_BOOT_OPTION in systemimager.conf to 'local' before doing the network installation, the systems install fine, and when I reboot them they try to boot off local disk, but they hang at the message telling me they're booting off the disk. Since there's really no detailed documentation on how all this works I'm left to conclude: - I'm doing something wrong - maybe it's a bug with redhat 9.0 - it's broken and doesn't really work There is also references to mkclientnetboot, but that's not really documented either and although I ran it I'm not sure what (if anything) it does... Did you also configure the PXE-network cards? You must enable local boot option (We have the Intel eepro100 cards). In the /tftpbooot/pxelinu.cfg there is also file named: syslinux.cfg.noboot Are you saying I have to make a configuration change to the network card itself? I have no idea how to do that, As for syslinux.cfg.noboot, I do have that on my system but also have no idea what to do with that either. Have you (or anyone) ever figured out what mkclientnetboot does and whether or not I even need to run it? If we start the machine and see the message from the ethernet card, we hit cntrl-s (eepro100). It is in the display message. Else you have to read the docs. There is a local boot option for our cards we can disable/enable it. For every succesfully installed node a file is placed in the /tftpboot/pxelinux.cfg/HEX_ADDRES_OF_THE_NODE with the contents of syslinux.cfg.noboot. This pxe configuration tells to boot from harddisk. I do not use this setup so the file maybe named something different. so what setup do you use? My own. I have posted the url and the documentation how to use it in an earlier mail to you. So if this doesn't work, how do people install a rack of systems? The machines I'm using allow you to interrupt the boot process with F12 to tell it to do a network boot, so I can leave the bios set to boot off disk before the network and all works fine, but that requires manual intervention with each machine which I'd think defeats the high level idea behind SI, especially if I want to install severl hundred (or thousand) images. Any and all comments would be appreciated. -mark -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] Re: [Sisuite-users] Building SI on RH9, using 2.4.21-pre3, for Dell 1750 target, with tg3 for Broadcomm
dann frazier wrote: On Wed, Oct 01, 2003 at 01:45:21PM -0700, [EMAIL PROTECTED] wrote: We were able to resolve this today -- we can now build and install SI flavors from a RH9 machine, for install on a Dell 1750 target with the Broadcomm network adaptor. The key is to migrate SI 3.0.1 to 2.4.21-pre3 first. I added the following patches to ./patches under our flavor build tree. These patches were extracted from RedHat's own kernel-2.4.20-8.src.rpm: patch-2.4.21-pre3.bz2 linux-2.4.20-tg3.patch (The interesting thing to note here is that the 2.4.20 kernel which ships with RH9 is actually 2.4.21-pre3, but they don't update the version string to say that...) I renamed these so that the pre3 patch ran first, before all other linux kernel patches, followed immediately by the tg3 patch. I then simply deleted any patches which conflicted later in the build (I think that xfs patches were the only thing that conflicted, and we aren't using xfs...). I also had to update linux.i386.config, since the above pre3 patch upgrades the kernel to 2.4.21-pre3. Cool. right now, i'd rather not update the kernel too drastically (i keep hoping 3.2.0 will happen soon). a standalone tg3 patch is definitely reasonable, but anything that breaks xfs makes me nervous. however, an alternate boot flavor is definitely a reasonable thing to do, especially for 3.0.1. if you want to build one, i'd be glad to host it. if its unclear how to do so, i can walk you through it. Can i download somewehere a kernel that support the new tg3 card or must i build my own? PS) Our linux systems use xfs ;-) -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Building SI on RH9, using 2.4.21-pre3, forDell 1750 target, with tg3 for Broadcomm
Kris, Thanks, the network card is now supported by the new kernel. I still have to build my own kernel en boel binaries because we need 'xfs' support. Kris Buytaert wrote: On Thu, 2003-10-23 at 13:24, Bas van der Vlies wrote: dann frazier wrote: On Thu, Oct 23, 2003 at 12:09:40PM +0200, Bas van der Vlies wrote: Can i download somewehere a kernel that support the new tg3 card or must i build my own? I just put my Quick and Dirty sollution available for download. http://howto.ipng.be/systemimager/ Maybe it works for you folks too. greetings. Kris the tg3 driver is in the latest 3.0.1 packages. couldn't tell ya if it supports the new tg3 card. PS) Our linux systems use xfs ;-) it does that too. I have the same problems as was mentioned in this email by Stephen G. Traugott. He has mentioned in his email that he updated the kernel to support the new tg3 with broadcom chipset. We at SARA have now also some new DELL machines with this card. WE can pxe boot them but if the kernel is loaded it does not support this network card ;-( We have the latest debian package for woody installed: 3.0.1-7 Is there is a newer version for debian available or has someone a updated kernel for me? PS) I use this line for the debian packages: deb http://download.systemimager.org/debian stable main -- Kris Buytaert [EMAIL PROTECTED] -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] Re: [Sisuite-users] Building SI on RH9, using 2.4.21-pre3, forDell 1750 target, with tg3 for Broadcomm
I have made a 2.4.22 kernel with a new boel_binaries.tar.gz that support xfs. The boel_binaries.tar,gz contains the modules for 2.4.20 and 2.4.22. So you can use the old systemimager kernel (2.4.20) and the new kernel (2.4.22). It also contains a modified root filesystem that supports dhcp option-155. This option specifies which install script we must use, eg: option option-155 uva_node; Use the 'uva_node' script to install the node. The package can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/systemimager_sara_boot.tar.gz -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * --- This SF.net email is sponsored by: The SF.net Donation Program. Do you like what SourceForge.net is doing for the Open Source Community? Make a contribution, and help us add new features and functionality. Click here: http://sourceforge.net/donate/ ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] [Sisuite-users] New images...
Ghe Rivero wrote: Hi, i admin some linux labs, with around 300 machines. The problem is that when i update a new image, i have to go to all the systems and update them manually. I have tried other solutions like dsh, but not all the machines are boot at the same time (they have dual boot, and somo users prefers Windows), so... Anybody has found a way to acompliesh with that?¿ I've in create a script in init.d that always that a machines boot up, execute de update command. Ghe Rivero We at SARA use cfengine (www.cfengine.org) for this. --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id149alloc_id66op=click ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] [Sisuite-users] clients hostname
Ghe Rivero wrote:
Hi people!
After install everything properly, i have a problem cause in the
clients installed, the hostname is properly given but not included in
the /etc/hosts. There is no DNS so some applications failed to start. Is
there any way to update /etc/hosts with the client hostname Thanks.
Ghe Rivero
I usually edit the master script file and include a function
'create_host_file':
create_hosts_file() {
cat /a/etc/hosts EOF
#
# Created by SystemImager
#
127.0.0.1 localhost
# First device eth0 (10.168.xxx.xxx)
#
$IPADDR $HOSTNAME
# Second device eth1 (192.168.xxx.xxx)
#
$IPADDR_USER$HOSTNAME_USER
# IP addresses other fileservers.
#
10.0.40.2nfs1-server
10.0.40.3nfs2-server
10.0.40.5nfs3-server
EOF
}
Hope this Helps
---
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click
___
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] Flamethrower connectivity test problem
We at SARA are currently switching to flamethrower setup. If we enable
flamethrower the conenctivity test is different then
with rsync, from /etc/init.d/rcS
# Ping test
ping_test() {
echo
echo ping_test
if [ ! -z $FLAMETHROWER_DIRECTORY_PORTBASE ]; then
PING_DESTINATION=$GATEWAY
HOST_TYPE=default gateway
else
PING_DESTINATION=$IMAGESERVER
fi
echo
echo Pinging your $HOST_TYPE to ensure we have network connectivity.
echo
My question is why?
Our flamethrower server is the same as our rsync-server. If we can ping
it then everything is oke. The other problem we have 2 network cards in
our machines:
- One for booting/sysadm stuff
- The other for the users
The user-lan has an default gateway specified as dhcp-option. This lan
is not up when we install an node. That the reason why we ran into this
problem. We have no gateway and the install will fail.
Regards
---
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
___
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Slow disk I/O during installation
Ole Holm Nielsen wrote: Thanks a lot to Bas for this excellent suggestion. Not being used to modifying the master scripts, could you kindly indicate the correct place in the script to put these extra commands ? A could place would be just before the rsync/flamethrower commands, just after mounting of the filesystems. -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] Re: [Sisuite-users] Slow disk I/O during installation
Ole Holm Nielsen wrote: Thanks a lot to Bas for this excellent suggestion. Not being used to modifying the master scripts, could you kindly indicate the correct place in the script to put these extra commands ? A could place would be just before the rsync/flamethrower commands, just after mounting of the filesystems. -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.4.3 - Added make_deb_pkg.sh utility to make an DEBIAN package - changed port number to 6611 for pxeconfigd. Webmin is using the 1 port number. This version can be downloaded 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. 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 file for 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: Bas van der Vlies [EMAIL PROTECTED] http://www.sara.nl for more info about SARA. --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] [Sisuite-users] SystemImager and Flamethrower
Mark Seger wrote: I've been wondering what people's general impressions are with flamethrower these days. I do remember about a year ago it sort of worked but was a little flakey. I also know things have gotten better. What I don't know if whether or not it's felt to be 'production worthy' yet. Are there any testimonials from satisfied users? We at SARA use is nowdays for our production cluster. We encountered a lot problems with installing and the configuration of the stuff. There where several bug in the software (eg udpcast). The bugs have now been fixed in the new versions. I do not know if systemimager and flamethrower use this new versions yet? Conclusion for us is that we did a lot of tweaking to make it work and use our versions of software (udpcast and busybox). Fixed some bugs in the /etc/init.d/functions of the ramdisk image. It was worth the work now we can install one or a lot of machines in the same time. --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] [Sisuite-users] Configuration Flexibility Question
Brian White wrote: I'm just starting to investigate SIS, so please bear with me if I don't grasp the entire thing just yet. Currently I'm using a home-brewed configuration management system. All of the install is done manually (yuck!) and then the CFILE program goes through and changes many configuration files to whatever is appropriate. My reading of SystemConfigurator has led me to believe that it can do basic configuration to handle network cards and the like, but doing more would involve writting a script to generate these files. Is that correct? I'd appreciate info or pointers to documentation on this. The way to this is install the node with systemimager/systemconfigurator. So the node is up and running. When the node boots then run your CFILE program to setup node the way you want. What i always do is install the node with systemimager/systemconfigurator. When this install is completed the node boots and one of my init.d scripts calls 'cfengine' (www.cfengine.org). This will finish the configuration of the node. --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] Re: [Sisuite-users] Flamethrower connectivity test problem]
Thus spake Bas van der Vlies ([EMAIL PROTECTED]):
We at SARA are currently switching to flamethrower setup. If we
enable flamethrower the conenctivity test is different then
with rsync, from /etc/init.d/rcS
# Ping test
ping_test() {
echo
echo ping_test
if [ ! -z $FLAMETHROWER_DIRECTORY_PORTBASE ]; then
PING_DESTINATION=$GATEWAY
HOST_TYPE=default gateway
else
PING_DESTINATION=$IMAGESERVER
fi
echo
echo Pinging your $HOST_TYPE to ensure we have network
connectivity.
echo
My question is why?
I honestly don't remember why, but it definitely looks like it was on
purpose.
It is fine for me ;-). Still strange that the check is different. Maybe
we have to do 2 ping tests if flamethrower is enabled. One to the
gateway and if this fails to the imageserver. Just a thought
Regards
--
--
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Servicesphone: +31 20 592 8012 *
* Kruislaan 415 fax:+31 20 6683167*
* 1098 SJ Amsterdam *
* *
_
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.4.4 - Updated documentation for xinetd support + example config - Added support for xinetd in the debian package scripts Implemented by: Ramon Bastiaans This version can be downloaded 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. 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 file for 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: Bas van der Vlies [EMAIL PROTECTED] http://www.sara.nl for more info about SARA. --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047alloc_id=10808op=click ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] Re: [Sisuite-users] need ide-scsi builtin
Jan Groenewald wrote: Hi On Tue, Sep 14, 2004 at 11:13:23AM +0200, Bas van der Vlies wrote: The ide-disk module is in systemimager release. You can load it in your systemimager install script. modprobe ide-scsi Maybe this does the trick. Unfortunately not. I put modpreobe ide-scsi right at the beginning of the autoinstall script. I get: insmod: /lib/modules/2.4.20-boel/: no such file or directory insmod: ide-scsi.o: no module found by that name This is the first thing I tried, which led me to the archives and the list. So, I see in the autoinstall script I can load modules, such as filesystems. But the ide-scsi is not there, and according to /usr/share/systemimager/boot/i386/standard/config it is not compiled in. (Strangely a vanilla 2.4.24 kernel allowed me module or not at all in make menuconfig, but not built in). However, looking at the insmod error message I see another problem. Why can the directory /lib/modules/2.4.20-boel/ not be found? Any ideas? boel_binaries.tar.gz is fetched via rsync during the install phase: - first kernel and root ramdisk - In the root ramdisk the boel_binaries.tar.gz is fetched and in this package contains all modules like ide-scsi.o - You must have an entry in the rsyncd.conf where you installed this package Hope ths Helps --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php ___ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] [Sisuite-users] website/release info question
Mark Seger wrote: As I missing something or is there no information on the SystemImager website that describes the features of various releases? Actually I did have a second thought and that was to go to sourceforge (though there's no pointer to it from SystemImager.org). Anyhow I didn't see any version descriptions here either. Is there somewhere to go and get this information? I guess the main reason I'm asking is because I've been happily running 3.1.8 for awhile now and haven't seen any need to upgrade. However, I'm getting ready to start playing with some 2.6 kernel based systems and am wondering where I'm going to get bitten especially with respect to grub and can't tell whether an upgrade will increase my pain or reduce it. 8-) In all seriousness, I've got those grub patches that have been happily working with 2.4 systems and don't know whether they'll work with newer versions of SI since I've patched Label.pm, Grub.pm and grub-install. I know the easy answer is to try it and see what will happen, which I will certainly do (and report back to this list if anyone cares) but I am also looking for some early warnings that might save me some time and trouble over the coming days. Mark, You do not have an 2.6 kernel for systemimager to install 2.6 kernel systems. We currently use systemimager 3.2 and we install 2.6 systems without any problems and we also uses grub for our 2.6 systems I do not know what is changed in Label.pm for systemimager 3.2, but you can always port your changes. --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] RE: [Sisuite-users] kernel problem
Peter Mueller wrote: I am also installaing dell 1850 with systemimager 3.2.3-6 on debian. I have no problem but i have to use the following statement in my systemimager master script: # JD/BvdV dell uses the megaraid controller 2 so load it, else # the install will fail # insmod megaraid2 Oh very interesting, it only loads with megaraid2? What about the updated e1000 driver needed by some Dells? Only had problems with the megaraid-driver for the poweredge 1850 servers. After inserting the insmod statement to the master.script we could install our cluster. --- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] [Sisuite-users] dhcp and systimager-server not on the same server
Marc Leforestier wrote: Hello I have 2 servers : - one with dhcpd and tftpd - one with systemimager-server I want to install image with pxe. The client get the files from tftp server and boot. The problem is that the client try to get boel_binaries.tar.gz from my dhcp server, not from the systemimager server and of course it does'nt work. Did you set option-140 in tou dhcp-config: # option-140 is the IP address of your SystemImager image server option option-140 192.168.16.3; Can you help me ? Thanks Marc ps: sorry for my poor english --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users ___ Systemimager mailing list [EMAIL PROTECTED] http://orwell.sara.nl/mailman/listinfo/systemimager --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] [Sisuite-users] dhcp and systimager-server not on the same server
Marc Leforestier wrote: Bas van der Vlies a écrit : Did you set option-140 in tou dhcp-config: # option-140 is the IP address of your SystemImager image server option option-140 192.168.16.3; That's it. Thanks ! It's working. No thanks I did'nt saw this option in the doc, where I can find more explanations ? Do not know. I think all options are listed in dhcp.conf stub file or something similiar. (mkdhcpserver). --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477alloc_id=16492op=click ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.6: - Added -r|--remove option. Now it is possible to remove the pxe boot file, eg: pxeconfig --remove dummy.sara.nl Works also for the other options. This version can be downloaded 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. 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 file for 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: Bas van der Vlies [EMAIL PROTECTED] http://www.sara.nl for more info about SARA. --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.6.2: - Fixed a bug in the non-interactive mode reported by and fixed by: Charles Galpin from defenderhosting.com This version can be downloaded 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. 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 file for 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: Bas van der Vlies [EMAIL PROTECTED] http://www.sara.nl for more info about SARA. --- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.6.3: - Added hostname lookup feature to hexls. If succes it will display the HEX address, ip-number, hostname, eg: C0A811DD = 192.168.17.221 = gb-r13n5.irc.sara.nl This version can be downloaded 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. 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 file for 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: Bas van der Vlies [EMAIL PROTECTED] http://www.sara.nl for more info about SARA. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities
0.6.4: - Fixed a bug in hexls with non resolving hostnames Reported by: Ole Holm Nielsen This version can be downloaded 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. 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 file for 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: Bas van der Vlies [EMAIL PROTECTED] http://www.sara.nl for more info about SARA. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] ANNOUNCE: New version of pxeconfig utilities (0.6.6)
0.6.6: - Fixed an error in postinst script for Debian. - Setup a wiki environment for documentation/tickets and source == This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Information, documentation and reporting bugs for the package: https://subtrac.sara.nl/oss/pxeconfig 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. 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: Bas van der Vlies pxeconfig at sara dot nl http://www.sara.nl for more info about SARA. -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - SF.net email is sponsored by: A Better Job is Waiting for You - Find it Now. Check out Slashdot's new job board. Browse through tons of technical jobs posted by companies looking to hire people just like you. http://jobs.slashdot.org/ ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] About the pxeconfig link on the systemimager site
pxeconfig_-_An_Alternate_to_Netbootmond can this be pointed to https://subtrac.sara.nl/oss/pxeconfig ? Because the source is old on the systemimager site and the documentation is also updated on this site. Regards -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] building debian packages
jef e wrote: Hi, I've built the latest version, 3.7.6, but would like to package it up for distribution to our client machines. My knowledge of building packages is very basic - I've packaged up a few kernel modules and such in the past, but nothing as complex as Systemimager. I know how to debianize the source, but with the multiple parts of this package, I am not quite sure what sorts of tweaks I need to make to the rules or contol (or any other) files to have the parts turned into proper .debs. I saw the install Howto on the Wiki, but didn't see anything relating to packaging. Any pointers will be greatly appreciated. Jef, In the svn tree there is a project systemimager-debian that contains the debian directories for 3.7.6: svn co svn://[EMAIL PROTECTED]/var/lib/svn/systemimager-debian/trunk systemimager-debian I am also planning to make the deb-package, but if you are finished i will be interested in you systemimager debs ;-) regards -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] building debian packages
jef e wrote: Bas van der Vlies wrote: Jef, In the svn tree there is a project systemimager-debian that contains the debian directories for 3.7.6: svn co svn://[EMAIL PROTECTED]/var/lib/svn/systemimager-debian/trunk systemimager-debian I am also planning to make the deb-package, but if you are finished i will be interested in you systemimager debs ;-) Bas, Thanks - I'll take a look and grab them. If they work, I'll let you know :-) Might take me a day or 3, as I also have some Solaris DST patching to take care of over here :( We will see. I am just installing etch with the old systemimager software and i mix of new. Just downgraded grub to the sarge version the grub in etch did not work for me. Just to inform you. (Just an FYI -- They are being built against Etch if that makes a difference) No at all ;-) -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] Old DHCP question
In the past i have ask for a new dhcp option, see: http://sourceforge.net/tracker/index.php?func=detailaid=476681group_id=259atid=350259 It about setting the host installation script via een dhcp option. Is this option still open for inclusion in systemimager release? If not no problem i will make my own boot image with this option ;-) Regards -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] systemimager debian trunk version conflict
Hello,
I am trying to build the debian trunk version and i get a conflict
when i want to install systemimager-boot-i386-standard:
{{{
Selecting previously deselected package systemimager-boot-i386-standard.
dpkg: regarding systemimager-boot-i386-standard_3.7.6-1_all.deb
containing systemimager-boot-i386-standard:
systemimager-boot-i386-standard conflicts with systemimager-server (=
3.6.4)
systemimager-server (version 3.7.6-1) is installed.
dpkg: error processing systemimager-boot-i386-standard_3.7.6-1_all.deb
(--install):
conflicting packages - not installing systemimager-boot-i386-standard
Errors were encountered while processing:
systemimager-boot-i386-standard_3.7.6-1_all.deb
}}}
There is an error in the control file. I
Package: systemimager-boot-i386-standard
Architecture: all
Recommends: systemimager-server
Conflicts: systemimager-bin-i386, systemimager-kernel-i386,
systemimager-initrd-i386, systemimager-boot-standard-i386,
systemimager-ssh-i386, systemimager-server ( 3.6.3),
systemimager-server (= 3.6.4)
I removed the (systemimager-server (= 3.6.4)) in the conflict line. The
same check is in ia64 package
Regards
--
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Servicesphone: +31 20 592 8012 *
* Kruislaan 415 fax:+31 20 6683167*
* 1098 SJ Amsterdam *
* *
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] building debian packages
I have build the deb packages and install them successfully on sarge/etch systems. I am now testing. I can put the debs on our ftp-server if somebody wants them. Regards -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] building debian packages
On Feb 19, 2007, at 6:47 PM, Simon Ruiz wrote: Hello! Would these run on Ubuntu 6.10 Edgy Eft? I've just gotten to the point where I can compile SystemImager from source, but if this package worked under Ubuntu I'd really appreciate all the benefits of NOT compiling from source. I don't know. We only have debian systems. I just tested the package and i have to rebuild the initrd.img with busybox. Because we got a lot of errors. Do you have a working standard initrd.img? I miss some libraries. From: [EMAIL PROTECTED] on behalf of Bas van der Vlies Sent: Mon 2/19/2007 9:09 AM To: sisuite-users@lists.sourceforge.net Subject: Re: [sisuite-users] building debian packages I have build the deb packages and install them successfully on sarge/etch systems. I am now testing. I can put the debs on our ftp-server if somebody wants them. Regards -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php? page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- --- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php? page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Bas van der Vlies [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Old DHCP question
Andrea Righi wrote: Bas van der Vlies wrote: In the past i have ask for a new dhcp option, see: http://sourceforge.net/tracker/index.php?func=detailaid=476681group_id=259atid=350259 It about setting the host installation script via een dhcp option. Is this option still open for inclusion in systemimager release? If not no problem i will make my own boot image with this option ;-) Regards I think you can use the installation parameter SCRIPTNAME to force the use or a single script name for a group of hosts (if I've understood well your problem): http://wiki.systemimager.org/index.php/Installation_Parameters#SCRIPTNAME.3Dscript Simply define it in etc/systemimager/pxelinux.cfg/syslinux.cfg and re-run si_mkclientnetboot... Andrea, Thanks for the hint and it is exactly what i needed. we use still a old systemimager setup with our own tweaks. I will rewrite our pxeconfig tool to use scriptname variable and get rid of our DHCP setting. Thanks -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] building debian packages
Jef Elliott wrote: Bas van der Vlies wrote: I have build the deb packages and install them successfully on sarge/etch systems. I am now testing. I can put the debs on our ftp-server if somebody wants them. I might be interested, but first, I'd like to know how you did it ;-) I saw your note about the conflicts in the control file, but I'm running across patch errors when I tried to use the SVN files as you suggested. It basically attempts to run a patch: --- ctcs-1.3.0pre4.orig/run 2001-11-06 15:40:40.0 -0600 +++ ctcs-1.3.0pre4/run 2002-09-22 15:23:36.0 -0500 But then sits and waits for input telling it which file to patch. Thing is, I have no idea :-) Any thoughts or tips? jef I do not apply the patches. As i can tell they are old patches for other systemimager releases ;-) Regards -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] building debian packages
jef e wrote: Bas van der Vlies wrote: I do not apply the patches. As i can tell they are old patches for other systemimager releases ;-) Regards ah - ok then :-) I took them out, but still run across this, still using the SVN version of the control file.. Use of uninitialized value in string eq at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655. dpkg-gencontrol -psystemimager-boot-i386-standard -ldebian/changelog -isp -Tdebian/systemimager-boot-i386-standard.substvars -Pdebian/systemimager-boot-i386-standard dpkg-gencontrol: error: package systemimager-boot-i386-standard not in control info dh_gencontrol: command returned error code 65280 make: *** [binary-arch] Error 1 Do you have an entry that I can borrow for my control file? :) jef Jef, Read the debian/rules file the control file is generated, eg: debian/rules control Makes the control file. Regards -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] building debian packages
On Feb 20, 2007, at 2:39 PM, Bas van der Vlies wrote: The debian packages are available at: ftp://ftp.sara.nl/pub/outgoing/systemimager I have only tested the release with rsync and i could reinstall a node. In the systemimager-server package are also the monitord and the bittorent init.d scripts. They belong in a separate package but for the moment it is oke. The main goal for us is to test the bittorent setup I just want to thanks the developers for version 3.7.6. We are upgrading from 3.2 and with the new version it is more configurable and easier to setup. The monitor software works as a charm and we are pleased with the bittorent functionality. Thanks -- Bas van der Vlies [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Imaging error.
Simon Ruiz wrote: Alright, So I've succesfully compiled SystemConfigurator 2.2.2 and SystemImager 3.7.6 (as per http://indianalinux.blogspot.com/2007/02/howto-install-systemimager-from-source.html), I've succesfully created an image from a golden client, and created a boot disc that seems to succesfully install said image onto another client. I then get chroot: cannot execute systemconfigurator: No such file or directory All I could find through Google for this was a suggestion to make sure I had recent version of SystemConfigurator, which I do have. Just to check did you install systemconfigurator on your golden client? Regards -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Network Adapter Fun!
On Mar 8, 2007, at 3:09 PM, Simon Ruiz wrote:
Replies below
From: [EMAIL PROTECTED] on behalf of
Andrea Righi
Sent: Wed 3/7/2007 2:48 PM
To: sisuite-users@lists.sourceforge.net
Subject: Re: [sisuite-users] Network Adapter Fun!
Simon Ruiz wrote:
As always, I'm working with Ubuntu 6.10 Edgy Eft on both the client
and server.
1) My main issue now seems to be that on reboot the computer that's
been newly re-imaged does not recognize the network. I have to go in
and manually activate the network adapter (no longer eth0, now it's
eth1). Does anyone else have experience with this type of thing and
how to fix it?
I'm not sure about this... but have you checked the file /etc/iftab in
your image?
Right on, so RMing /etc/iftab seems to take care of this issue.
Awesome! I figured it'd be something simple like that. Thanks!
2) Is there an append option for the autoinstallcd to make it reboot
or shutdown after being imaged? That beeping is nice for now, when
I'm imaging a client in the other room, but it won't be when I'm
imaging a few hundred computers in classrooms and leaving the process
running over the weekend.
...beeping hundreds of clients would be great! lol!
I would be amused, I just think the teachers might have a
conniption when they came in Monday morning. Heheh. I can't imagine
what it would sound like if all the workstations in every English
classroom just started beeping incessantly...
You can change the post install action running si_mkautoinstallscript
with --post-install reboot option. This will also re-create your
autoinstallscript, so be sure to make a copy if you changed it
manually.
Will this be overwritten when I update that image? It always wants
to re-create the autoinstall script.
3) My current configuration scheme is designed for use with Norton
Ghost which we were using until recently. It involves rc.local
checking at boot time whether the machine's macaddress corresponds to
that of the golden client, and if not then whether it's hostname is
nordx--image, if so then it runs an autoconfig script. The autoconfig
script wgets a comma-delimited plain-text file from an apache server,
searches through it for it's own MAC address and, using the identity
variables that it gets, changes its hostname, sets up its printer,
etc.
With SystemImager, I know there are all kinds of spiffy scripts that
get called during the installation process at different times and in
different circumstances, so I'm sure there's a better way to do this
autoconfiguration than what I'm doing. However, I can't seem to find
documentation of how they work at wiki.systemimager.org. Might the
documentation exist somewhere else for my perusal?
Do you mean post-install scripts? try to look in
/var/lib/systemimager/scripts/post-install/README.
And here you can find some examples:
http://svn.systemimager.org/listing.php?repname=systemimagerpath=%
2Ftrunk%2Fdoc%2Fexamples%2Fpost-install%2Frev=0sc=0
I'll try post a comment about pre/post install scripts on wiki ASAP.
Andrea,
I have just installed etch and excluded /rm '/etc/udev/rules.d/
z25_persistent-net.rules' from the image and then everything is oke.
But on some hosts we have more interfaces and then the recreation of
this file gives the wrong interface order. I mean when you boot it is
eth0 but when the kernel runs it can be eth1 and systemconfigurator
creates a entry for eth0. So the host is not reachable any more over
the net, see the link below for explanation:
http://www.debianhelp.co.uk/udev.htm
what i now want to do, and i do not have a script yet. Is in a post-
install script:
- Create the entry in ''/etc/udev/rules.d/z25_persistent-net.rules'
eg:
{{{
# PCI device 0x8086:0x1076 (e1000)
SUBSYSTEM==net, DRIVERS==?*, ATTRS{address}==00:13:72:53:2c:2d,
NAME=boot-net
}}}
- Create an entry,depends on IP-method, in /etc/network/interfaces
{{{
auto boot-net
iface boot-net inet dhcp
}}}
Regards
--
Bas van der Vlies
[EMAIL PROTECTED]
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Network Adapter Fun!
Andrea Righi wrote:
Bas van der Vlies wrote:
Andrea,
I hav ejust installed etch and exclude/rm
'/etc/udev/rules.d/z25_persistent-net.rules' from the image and then
everything from the image and then everything is oke. But on some hosts
we have more interfaces and then the recreation of this file gives the
wrong order. I mean when you boot it is eth0 but when the kernel runs it
can be eth1 and systemconfigurator creates a entry for eth0. So the hist
is not reachable any more over the net, see the link below for explanation:
http://www.debianhelp.co.uk/udev.htm
what i now want to do, and i have do not have a script yet. Is in a
post-install script:
- Create the entry in ''/etc/udev/rules.d/z25_persistent-net.rules'
eg:
{{{
# PCI device 0x8086:0x1076 (e1000)
SUBSYSTEM==net, DRIVERS==?*, ATTRS{address}==00:13:72:53:2c:2d,
NAME=boot-net
}}}
- Create an entry,depends on IP-method, in /etc/network/interfaces
{{{
auto boot-net
iface boot-net inet dhcp
}}}
But with UYOK, since the kernel is the same when you're installing and
when the clients are in production, it shouldn't be sufficient to simply
remove /etc/udev/rules.d/z25_persistent-net.rules from the image and run
/lib/udev/write_net_rules in a post-install script? obviously if you use
the standard BOEL this is not always true...
-Andrea
Andrea,
I use the standard kernel, boel and initrd from systemimager to
install a node . This setup runs systemconfigurator and generates the
network setup files.
So it depends on the standard systemimager setup how the ordening is.
Now we boot our own kernel with our own distribution and then the
ordering can be different that can not be solved by removing
'/etc/udev/rules.d/z25_persistent-net.rules' file. The way to make sure
it works is by using the method described by making 'labels'.
Or must i make my own kernel, initrd and boel for every different node
that has different hardware.
--
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Servicesphone: +31 20 592 8012 *
* Kruislaan 415 fax:+31 20 6683167*
* 1098 SJ Amsterdam *
* *
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] [Systemimager] Bittorrent Not Quite Working...
On Mar 27, 2007, at 7:02 PM, Simon Ruiz wrote: Andrew, Yeah, that's the first one I checked, and it was already installed, I believe by default. Version 3.4.2-6ubuntu3 (edgy). I thought maybe it was just a client, it is described as contains the tools which are used for console-only downloading. (Not to mention, it doesn't seem to be what systemimager is looking for.) So I grasped at straws with the library and the dev library + a recompile. Simón You must install version 4.0 or higher, the 3.4.2 version does not have the software to make torrents. Regards -- Bas van der Vlies [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] ANNOUNCE: New version of pxeconfig utilities (0.7.0)]
0.7.0: - Added default.memtest and default.flashqla as example how to use pxeconfig utilities for other purposes then for systemimager. - Added configure script (autoconf tools). - Replaced the debian build package system by a better one that uses the added configure script. It must now be easy to build also a rpm package. - Added a configuraton file pxeconfig.conf, eg to specify the location of pxe config directory. Closes ticket #3. - Removed the -d/--directory option for pxeconfig. It is replaced by the configuration file pxeconfig.conf (pxe_config_dir). == This version can be downloaded from: ftp://ftp.sara.nl/pub/outgoing/pxeconfig.tar.gz Information, documentation and reporting bugs for the package: https://subtrac.sara.nl/oss/pxeconfig 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. 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: Bas van der Vlies pxeconfig at sara dot nl http://www.sara.nl for more info about SARA. -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - SF.net email is sponsored by: A Better Job is Waiting for You - Find it Now. Check out Slashdot's new job board. Browse through tons of technical jobs posted by companies looking to hire people just like you. http://jobs.slashdot.org/ ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http
Re: [sisuite-users] Using SystemImager in a school environment
Thomas Krause wrote: 2.) It would be nice, if I could mark a client for reinstallation so that it will get a new image the next time it boots. However once the client has a new image, I want to automatically restart the client and unmark it on the server, so that it will not receive the update again after the restart. Is there already a way to signal the server when the client has finished its update or do I have to implement that myself (somehow) in the autoinstallscript. I can implement the (un)marking stuff by myself, I just need a way to run a script on the server when the client is finished. You have to setup netboot or the alternative for neboot: pxeconfig. See the systemimager wiki pages. -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] Question of bitttorrent and boel_binaries.tar.gz
Hello,
first i want to say thanks for the debian packages in the new version
:-D. Saves a lot of work!
In our cluster we have now mixed nodes i386 and x86_64. Now if we enabled
bittorrent then there is now flavor included as with eg rsync and the
installation will fail for X86_64 machines because the boel_binaries.tar.gz
is i386.
{{{
bittorrent_get_file ${TORRENTS_DIR}/${bittorrent_tarball}.torrent
${BOEL_BINARIES_DIR}
CMD=rsync -av ${IMAGESERVER}::boot/${ARCH}/${FLAVOR}/boel_binaries.tar.gz
${BOEL_BINARIES_DIR}
}}}
Is this a bug or feature?
--
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Servicesphone: +31 20 592 8012 *
* Kruislaan 415 fax:+31 20 6683167*
* 1098 SJ Amsterdam *
* *
-
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
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Question of bitttorrent and boel_binaries.tar.gz
Andrea Righi wrote:
Bas van der Vlies wrote:
Hello,
first i want to say thanks for the debian packages in the new version
:-D. Saves a lot of work!
In our cluster we have now mixed nodes i386 and x86_64. Now if we enabled
bittorrent then there is now flavor included as with eg rsync and the
installation will fail for X86_64 machines because the boel_binaries.tar.gz
is i386.
{{{
bittorrent_get_file ${TORRENTS_DIR}/${bittorrent_tarball}.torrent
${BOEL_BINARIES_DIR}
CMD=rsync -av ${IMAGESERVER}::boot/${ARCH}/${FLAVOR}/boel_binaries.tar.gz
${BOEL_BINARIES_DIR}
}}}
Is this a bug or feature?
Well.. I'd like to say that it's a feature, but it seems more a bug... :-)
That is quick!!
Anyway, the patch below (untested) should fix this problem.
I will test it. Is is also in svn?
-Andrea
---
Index: sbin/si_installbtimage
===
--- sbin/si_installbtimage (revision 4164)
+++ sbin/si_installbtimage (working copy)
@@ -170,24 +170,36 @@
my $ARCH = (uname())[4];
$ARCH =~ s/i.86/i386/;
-my $boel_binaries = $TARBALL_DIR/boel_binaries.tar.gz;
-print Preparing torrent file for BOEL binaries...\n;
-# Create the symbolic link into the image directory.
-symlink($config-autoinstall_boot_dir() . '/' . $ARCH .
-'/standard/boel_binaries.tar.gz', $boel_binaries)
-if (! -e $boel_binaries);
-# Make .torrent file.
-if ($maketorrent =~ btmakemetafile) {
-system $maketorrent $boel_binaries
http://$image_server:$tracker_port/announce --target
$TORRENT_DIR/boel_binaries.tar.gz.torrent;
+# Get all the available boel_binaries (for all the supported architectures).
+my @archs_dir;
+if (opendir(DIR, $config-autoinstall_boot_dir())) {
+ @archs_dir = grep {!/^\.$|^\.\.$/} readdir(DIR);
} else {
-system $maketorrent http://$image_server:$tracker_port/announce
$boel_binaries --target $TORRENT_DIR/boel_binaries.tar.gz.torrent;
+die(error: couldn't open . $config-autoinstall_boot_dir() . \n);
}
-if ($?) {
-die ERROR: cannot create BOEL binaries torrent file!\n;
+foreach my $arch (@archs_dir) {
+print Preparing torrent file for BOEL binaries for $arch...\n;
+my $boel_binaries = $config-autoinstall_boot_dir() . '/' . $arch .
+'/standard/boel_binaries.tar.gz';
+my $boel_binaries_link = ${TARBALL_DIR}/${arch}-boel_binaries.tar.gz;
+# Create a symlink into the image directory.
+if ((-e $boel_binaries) (! -e $boel_binaries_link)) {
+symlink($boel_binaries, $boel_binaries_link);
+}
+# Make .torrent file.
+if ($maketorrent =~ btmakemetafile) {
+system $maketorrent $boel_binaries_link
http://$image_server:$tracker_port/announce --target
$TORRENT_DIR/$arch-boel_binaries.tar.gz.torrent;
+} else {
+system $maketorrent http://$image_server:$tracker_port/announce
$boel_binaries_link --target $TORRENT_DIR/$arch-boel_binaries.tar.gz.torrent;
+}
+if ($?) {
+print STDERR ERROR: cannot create BOEL binaries torrent file for
$arch! skipping it.\n;
+next;
+}
+# symlink is required by old versions of BitTorrent.
+symlink($boel_binaries_link, $TORRENT_DIR . / .
basename($boel_binaries_link));
+print done.\n;
}
-# symlink is required by old versions of BitTorrent.
-symlink($boel_binaries, $TORRENT_DIR . / . basename($boel_binaries));
-print done.\n;
# Starting first image seeder.
print Starting first image server seeder...\n;
Index: initrd_source/skel/etc/init.d/functions
===
--- initrd_source/skel/etc/init.d/functions (revision 4164)
+++ initrd_source/skel/etc/init.d/functions (working copy)
@@ -652,11 +652,12 @@
# Download BOEL binaries from peers
bittorrent_tarball=boel_binaries.tar.gz
-logmsg Start downloading ${bittorrent_tarball} using bittorrent
+logmsg Start downloading ${bittorrent_tarball} (${ARCH}) using
bittorrent
logmsg
logmsg -- INFO: remember to start
/etc/init.d/systemimager-server-bittorrent on the image server!
logmsg
-bittorrent_get_file ${TORRENTS_DIR}/${bittorrent_tarball}.torrent
${BOEL_BINARIES_DIR}
+bittorrent_get_file
${TORRENTS_DIR}/${ARCH}-${bittorrent_tarball}.torrent ${BOEL_BINARIES_DIR}
+cd ${BOEL_BINARIES_DIR} mv ${ARCH}-${bittorrent_tarball}
${bittorrent_tarball}
unset bittorrent_tarball
elif [ ! -z $FLAMETHROWER_DIRECTORY_PORTBASE ]; then
--
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Servicesphone: +31 20 592 8012 *
* Kruislaan 415 fax:+31 20 6683167*
* 1098 SJ
[sisuite-users] Debian build
Hello,
I am trying to build the debian packages from the trunk version of
systemimager.
Here are some problems that i have encounterd:
- First the trunk version is 2.9.3. So i changed the debian/changelog
else we immediately get an error
- Second there is no manpage for si_installbtimage, debian/rules
mv $(CURDIR)/debian/$(PKG)-server/usr/share/man/man8/si_installbtimage.8.gz\
#$(CURDIR)/debian/$(PKG)-server-bittorrent/usr/share/man/man8
- The process of building the amd64
1) systemimager-boot-amd64-standard_3.9.2_all.deb
2) systemimager-initrd-template-amd64_3.9.2_all.deb
goes wrong because it tries to cd to amd64 directory. That is the
architecture for a debian packagem but the directory is named x86_64. I did
not rename the directory but i made an extra statement in debian/rules that
if architecture is amd64 then use COPY_ARCH=x86_64:
COPY_ARCH = $(shell if [ ${ARCH} == amd64 ]; then echo x86_64; else
echo ${ARCH}; fi)
So in the amd64 package the directories have the name x86_64. So we do have
to change a lot of scripts
I have attached the rules file that i use and worked for me ;-)
Also i changed all occurrences in debian/control file from x86_64 to amd64
else we also can not make the packages mentioned above
Regards
--
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Servicesphone: +31 20 592 8012 *
* Kruislaan 415 fax:+31 20 6683167*
* 1098 SJ Amsterdam *
* *
#!/usr/bin/make -f
# Sample debian/rules that uses debhelper.
# GNU copyright 1997 to 1999 by Joey Hess.
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
PKG = systemimager
VERSION = $(shell dpkg-parsechangelog | grep ^Version: | \
cut -d -f 2)
BUILD_DIR = .
UPSTREAM_TARBALL = $(PKG)_$(VERSION).tar.gz
ARCH = $(shell dpkg --print-architecture)
# HvB
COPY_ARCH = $(shell if [ ${ARCH} == amd64 ]; then echo x86_64; else echo
${ARCH}; fi)
BOOTPKG = $(PKG)-boot-$(ARCH)-standard
INITRD_TEMPLATE_PKG = $(PKG)-initrd-template-$(ARCH)
# for debhelper; we can't just say -N$(BOOTPKG) because that'd cause us to
# build empty boot packages for the other archs
NON_BOOT_PKGS := -p $(PKG)-client \
-p $(PKG)-common \
-p $(PKG)-doc \
-p $(PKG)-server \
-p $(PKG)-server-flamethrowerd \
-p $(PKG)-server-bittorrent
BOOTARCHS = alpha i386 ia64 parisc ppc64-iSeries ppc64-ps3 ppc64 ppc64ydl ppc
x86_64
PATCHES=$(sort $(shell find $(CURDIR)/patches -name *.patch))
configure: configure-stamp
configure-stamp:
dh_testdir
# Add here commands to configure the package.
[EMAIL PROTECTED] -n Extracting upstream tarball...
[EMAIL PROTECTED] xfj $(UPSTREAM_TARBALL)
[EMAIL PROTECTED] done.
[EMAIL PROTECTED] $(BUILD_DIR) \
# $(foreach patch, $(PATCHES), \
#echo -n Applying `basename $(patch)`... cat $(patch) | \
#patch -s -p1 echo done. ) /bin/true
touch configure-stamp
copy_changelog: $(BUILD_DIR)/changelog
$(BUILD_DIR)/changelog: $(BUILD_DIR)/CHANGE.LOG
cd $(BUILD_DIR) cp CHANGE.LOG changelog
build: build-arch build-indep
build-indep:cleandeb configure-stamp build-indep-stamp copy_changelog
build-indep-stamp:
# the pdf build reports a failure, but the result looks fine...
-$(MAKE) -C $(BUILD_DIR) docs USE_SGMLTOOLS=1
touch build-indep-stamp
build-arch: cleandeb configure-stamp build-arch-stamp copy_changelog
build-arch-stamp:
dh_testdir
$(MAKE) -C $(BUILD_DIR) binaries MKCRAMFS=/usr/sbin/mkcramfs
touch build-arch-stamp
test: build-arch-stamp
debian/control: debian/control.in debian/control.arch.in
# generate control file suitable for the boot package
# substvars don't seem to work, so we hack around it with sed.
sed -e 's/$${misc\:Package\-Arch}/$(ARCH)/g' \
debian/control.in debian/control
for arch in $(BOOTARCHS); do \
sed -e s/\$${misc\:Package\-Arch}/$$arch/g \
debian/control.arch.in debian/control; \
done
clean:
dh_testdir
dh_testroot
rm -f build-indep-stamp build-arch-stamp configure-stamp
# Add here commands to clean up after the build process.
#rm -rf $(BUILD_DIR)
cd $(CURDIR)/debian \
rm -rf $(PKG)-client $(PKG)-server $(PKG)-common $(PKG)-doc \
$(BOOTPKG) $(INITRD_TEMPLATE_PKG) \
$(PKG)-boot $(PKG)-server-flamethrowerd $(PKG)-server-bittorrent
rm -f debian/$(PKG
Re: [sisuite-users] Debian build
(working copy)
@@ -24,7 +24,7 @@
-p $(PKG)-server-flamethrowerd \
-p $(PKG)-server-bittorrent
-BOOTARCHS = alpha i386 ia64 parisc ppc64-iSeries ppc64-ps3 ppc64 ppc64ydl
ppc x86_64
+BOOTARCHS = alpha i386 ia64 parisc ppc64-iSeries ppc64-ps3 ppc64 ppc64ydl
ppc amd64
PATCHES=$(sort $(shell find $(CURDIR)/patches -name *.patch))
--- /dev/null 2007-04-17 07:20:02.0 +0200
+++ debian/systemimager-initrd-template-amd64-standard.postinst 2007-08-15
16:01:34.0 +0200
@@ -0,0 +1,8 @@
+#!/bin/sh
+
+ARCH=`uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e
s/sa110/arm/`
+INITRD_TEMPLATE_DIR=/usr/share/systemimager/boot/${ARCH}/standard/initrd_template
+
+cd ${INITRD_TEMPLATE_DIR}/dev MAKEDEV std tty1 tty2 tty3 tty4 tty5 tty6
+
+#DEBHELPER#
--- /dev/null 2007-04-17 07:20:02.0 +0200
+++ debian/systemimager-boot-amd64-standard.postinst2007-08-15
16:01:13.0 +0200
@@ -0,0 +1,8 @@
+#!/bin/sh
+if [ -e /tftpboot/kernel -o -e /tftpboot/initrd.img ]; then
+ echo
+ echo WARNING: remember to update the kernel and initrd.img in
/tftpboot!
+ echo
+fi
+
+#DEBHELPER#
-
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
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
--
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Servicesphone: +31 20 592 8012 *
* Kruislaan 415 fax:+31 20 6683167*
* 1098 SJ Amsterdam *
* *
-
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
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] [Systemimager] Debian build
Andrea Righi wrote: Bas van der Vlies wrote: Which the 3.9.3 ;-) version i get an error that the file is not there. Is it generated? Yes, it's generated by make manpages. Andrea the x86_64 is the name for Redhat and other distro's in Debian/Ubuntu the name is amd64 (some historical reasons and it is not only for amd but also for intel ;-) ). So i want to leaf the directories names the same for: * patH/systemimager/boot i386ia64x86_64 Sometimes you have setup a debian systemimager server and you want to install x86_64 redhat clients and amd64 debian clients with the standard boot images. They can both use the x86_64 directory. It depends on the client which architecture we must have. The simplest solution would be that we make a simlink: ln -s x86_64 amd64 Or we adjust the software that amd64 is equivalent to x86_64. This patch seems to introduce a new architecture for debian and that is not needed. OK, I understand now. Anyway, if the standard name in Debian/Ubuntu is amd64 I think we should use that for packaging and x86_64 for the systemimager directories (the contents of the package). A possible solution could be to define in debian/rules 2 different variables: ARCH = $(shell dpkg --print-architecture) UNAME_ARCH = $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e s/sa110/arm/) ARCH is the architecture that uses the Debian naming schema and UNAME_ARCH is the architecture seen by the kernel. See the following patch (uncompiled/untested and to be applied on-top-of the previous one). What do you think? That is almost the same as i proposed ;-) only it contains more architectures. It works :-). The only problem is that i still do not have the man page of si_installbtimage.8.gz. So i commented that line. Andrea i find the building process a bit awkward or i do not understand it. when i change the the debian/rules file in the toplevel of the trunk version it has no effect et all. Because the trunk version will first grab systemimage-$VERSION tarball and will untar this in the tmp directory. It will use the debian/rules file from that directory. But we can not do a make deb from that directory. So it will never use the adjustments. Is this on purpose or must i build the deb packages differently? Regards Thanks, -Andrea Index: debian/rules === --- debian/rules(revision 4182) +++ debian/rules(working copy) @@ -12,6 +12,8 @@ UPSTREAM_TARBALL = $(PKG)_$(VERSION).tar.gz ARCH = $(shell dpkg --print-architecture) +UNAME_ARCH = $(shell uname -m | sed -e s/i.86/i386/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e s/sa110/arm/) + BOOTPKG = $(PKG)-boot-$(ARCH)-standard INITRD_TEMPLATE_PKG = $(PKG)-initrd-template-$(ARCH) @@ -24,7 +26,7 @@ -p $(PKG)-server-flamethrowerd \ -p $(PKG)-server-bittorrent -BOOTARCHS = alpha i386 ia64 parisc ppc64-iSeries ppc64-ps3 ppc64 ppc64ydl ppc x86_64 +BOOTARCHS = alpha i386 ia64 parisc ppc64-iSeries ppc64-ps3 ppc64 ppc64ydl ppc amd64 PATCHES=$(sort $(shell find $(CURDIR)/patches -name *.patch)) @@ -109,7 +111,7 @@ # # systemimager-boot-$(ARCH)-standard.postinst # - cd $(CURDIR)/debian/$(BOOTPKG)/usr/share/systemimager/boot/$(ARCH)/standard/initrd_template/dev \ + cd $(CURDIR)/debian/$(BOOTPKG)/usr/share/systemimager/boot/$(UNAME_ARCH)/standard/initrd_template/dev \ rm -f tty1 \ rm -f tty2 \ rm -f tty3 \ @@ -120,9 +122,9 @@ rm -f null # Copy the needed files into the initrd_template package. - mkdir -p $(CURDIR)/debian/$(INITRD_TEMPLATE_PKG)/usr/share/systemimager/boot/$(ARCH)/standard - mv $(CURDIR)/debian/$(BOOTPKG)/usr/share/systemimager/boot/$(ARCH)/standard/initrd_template \ - $(CURDIR)/debian/$(INITRD_TEMPLATE_PKG)/usr/share/systemimager/boot/$(ARCH)/standard + mkdir -p $(CURDIR)/debian/$(INITRD_TEMPLATE_PKG)/usr/share/systemimager/boot/$(UNAME_ARCH)/standard + mv $(CURDIR)/debian/$(BOOTPKG)/usr/share/systemimager/boot/$(UNAME_ARCH)/standard/initrd_template \ + $(CURDIR)/debian/$(INITRD_TEMPLATE_PKG)/usr/share/systemimager/boot/$(UNAME_ARCH)/standard install-indep: build-indep dh_testdir -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam
[sisuite-users] ANNOUNCE: New version of pxeconfig utilities(1.0.0)
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 sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] ANNOUNCE: New version of pxeconfig utilities (1.0.0)
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. -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - 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 sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] [Sisuite-announce] SystemImager cluster map
On Feb 16, 2008, at 4:27 PM, Andrea Righi wrote: Hi all, I'd like to point to our new Google Maps like tool to keep track who's using SystemImager around the world: http://wiki.systemimager.org/cluster-register/cluster-map.php We're really interested in this kind of feedback and user experiences in general, so if you're using SystemImager in your organization, company, laboratory, school, etc., please, consider to register your cluster on the map. A big thank to Bernard that provided the cluster map code used for OSCAR (http://oscar.openclustergroup.org/cluster-map). There are some small changes respect to the OSCAR version in order to make it more suitable for SystemImager. And a big thank in advance to all the users that'll register their clusters on the map! -Andrea PS suggestions/bugs reporting about the cluster map interface are welcome as well. It is a nice feature to have the cluster map. I have a remark the interface expects one type of node for the whole cluster. At our site we have different nodes in the same cluster: - 1850 with 2 cpu's - 1950 with 2 quad cores To make it more complicated the memory is also different in the nodes ;-) -- Bas van der Vlies [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Sisuite-announce mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-announce - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] bittorrent problem
Maurice Libes wrote: hi to all Maurice # Tracker log file. BT_TRACKER_LOG=/var/log/systemimager/bittorrent-tracker.log # Interface used to seed files with bittorrent. BT_INTERFACES=eth0 BT_INTERFACE will do the trick (so remove the trailing s_ ;-) -- -- * * * Bas van der Vlies e-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Servicesphone: +31 20 592 8012 * * Kruislaan 415 fax:+31 20 6683167* * 1098 SJ Amsterdam * * * - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] ANNOUNCE: New version of pxeconfig/pxemenu utilities (2.0.0)
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
[sisuite-users] si_clusterconfig, si_psh
Hello,
I am just playing/trying this tools and a like them, but i have problem
with. I want to specify a range of hosts and my hostname also contains a
dash. So i can not specifiy:
--hosts gb-r1n1-gb-r1n20
maybe we can add add basename option for both commandline and xml file.
Just as reference in my project pxeconfig i solved it as example
* https://subtrac.rc.sara.nl/oss/pxeconfig/wiki/PxeUsage#hostrange
{{{
We want to make links for a range of hosts, eg node1 till node100, This can
be acomplished with these commands:
* pxeconfig --basename node --host-range 1-100 --filename
default.node_install
* pxeconfig --basename node --start 1 --end 100
Some sites have name their hosts, eg: node001 till node099. This can also
be acomplished in several ways:
* pxeconfig --basename node --equal-width --host-range 1-099
* pxeconfig --basename node --host-range 001-099
* pxeconfig --basename node --start 001 --end 099
rack(x) and node(y) specification ¶
We want make links for hosts with a naming schema(s) like this:
gb-rnumbernnumber
node-(number)-(number)
These examples will create links for node1, node2 and node3 in rack1, rack2
and rack3:
* pxeconfig --basename gb- -rack r1-r3 --node n1-n3 --filename
default.memtest
* pxeconfig --basename node --rack 1-3 --node 1-3 --filename default.memtest
When 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 --filename
default.memtest
will create links for hosts:
* gb-r01n01
* gb-r01n02
* gb-r02n01
* gb-r02n02
}}}
--
--
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Servicesphone: +31 20 592 8012 *
* Kruislaan 415 fax:+31 20 6683167*
* 1098 SJ Amsterdam *
* *
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] eth0 and eth1 reversed on clients- how toprevent that from happening?
On Sep 24, 2008, at 8:39 PM, Brodie, Kent wrote:
One simple method is instead of using the SystemImager kernel, use
UYOK kernel (which would essentially be your Red Hat kernel).
Barring
that, there should be a way to use udev to pin down which nic to use.
Hmmm. Using UYOK made NO difference. Bah. Maybe I'm having
a bad
day, I cannot find the info on udev you're referencing?
We have the same problem at our clusters (DELL 1950) with broadcom
network interfaces. We now use udev rules in combination with
biosdevname utility and give our network cards logical names instead
of eth0/eth1:
The problem is that for the BIOS eth0 is different then for the linux
kernel. That is why we use biosdevname.
We have Debian installed on our hosts.
This how we solve it in a post-install script:
{{{
create_persistent_ethernet_devices()
{
#BIOSDEVNAME=/usr/sbin/biosdevname
BIOSDEVNAME=`which biosdevname`
if [ ! -x $BIOSDEVNAME ]
then
echo NOT configuring ethernet devices, missing
program: $BIOSDEVNAME
exit 1
fi
PERSISTENT_NET_RULES=/etc/udev/rules.d/z25_persistent-net.rules
ADMIN_NETWORK=`$BIOSDEVNAME -i eth0`
USER_NETWORK=`$BIOSDEVNAME -i eth1`
IFCONFIG=ifconfig
ADMIN_MAC=`$IFCONFIG $ADMIN_NETWORK | grep HWaddr | awk
'{ print tolower($NF) }'`
USER_MAC=`$IFCONFIG $USER_NETWORK | grep HWaddr | awk
'{ print tolower($NF) }'`
# Write persistent network names
#
cat $PERSISTENT_NET_RULES EOF
# This file was automatically generated by the SYSTEMIMAGER (BvdV)
#
# program, probably run by the persistent-net-generator.rules rules
file.
#
# You can modify it, as long as you keep each rule on a single line.
# MAC addresses must be written in lowercase.
# PCI device 0x14e4:0x164c (bnx2)
SUBSYSTEM==net, DRIVERS==?*, ATTRS{address}==$ADMIN_MAC,
NAME=admin
# PCI device 0x14e4:0x164c (bnx2)
SUBSYSTEM==net, DRIVERS==?*, ATTRS{address}==$USER_MAC, NAME=gb2
EOF
}}}
systemimager network config:
{{{
two_interfaces()
{
systemconfigurator --confighw --confignet --stdin EOL || shellout
[NETWORK]
HOSTNAME = name
[INTERFACE0]
DEVICE = admin
TYPE = dhcp
[INTERFACE1]
DEVICE = gb2
TYPE = static
IPADDR = 10.0.0.1
NETMASK = 255.255.255.0
EOL
}
}}}
It is just an example!
regards,
--
Bas van der Vlies
[EMAIL PROTECTED]
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] eth0 and eth1 reversed on clients- how toprevent that from happening?
Bernard Li wrote: Thanks for this! It would be great if you can put this in our Wiki such that it can benefit users in the future: http://wiki.systemimager.org Cheers, Hi Bernard, I shall put this in the Wiki regards -- * Bas van der Vliese-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Services Amsterdam, The Netherlands * - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] recreate rsync_stubs
Paul Newman wrote: Hello. Our systemimager server root filesystem packed it in and I am having trouble getting a fresh install of the os and systemimager to find the /var/lib/systemimager images (these are on another drive which is fine). apparently uploading, deleting and renaming images scribbles in a file (or files) in the /etc/systemimager/rsync_stubs. I don't have a backup of this file. Is there a tool to regenerate the stubs file(s)? alternately, are there any docs on what the stub files look like (so I can recreate it/them)? I have looked in all the usual places. I have seen a couple of mailing list archive items which suggest that I may be looking for something like /etc/systemimager/rsync_stubs/40_some_image_name which would suggest that there would be a file per image (I have about 25 images in the repository). If anyone could post a sample I could probably regenerate what I need on my own. thanks, p Paul, You need at least a this file: 10header # # SystemImager # # $Id: 10header,v 1.3 2004/02/02 21:47:38 brianfinley Exp $ # # # # WARNING: # # This file is automatically generated by SystemImager, do not edit! # # Everything you add directly to this file will be lost the next # # time it is generated. See man mkrsyncd_conf for details on how # # to have local entries added each time this file is generated. # # # list = yes timeout = 600 dont compress = *.gz *.tgz *.zip *.Z *.ZIP *.bz2 *.deb *.rpm *.dbf uid = root gid = root use chroot = yes log file = /var/log/systemimager/rsyncd # # For additional security, modify and uncomment this line. See # man rsyncd.conf for details. # #hosts allow = 127.0.0.0/24 MY_NET/NETMASK MY_CLIENT/32 [boot] #path = /usr/share/systemimager/boot path = /data/systemimager/boot [overrides] #path = /var/lib/systemimager/overrides path = /data/systemimager/overrides [scripts] path = /data/systemimager/scripts [torrents] path = /data/systemimager/torrents The rest is simple, eg the image lisa_amd64: root# more 40lisa_amd64 [lisa_amd64] path=/data/systemimager/images/lisa_amd64 After creating the files run: /usr/sbin/si_mkrsyncd_conf Regards -- * Bas van der Vliese-mail: [EMAIL PROTECTED] * * SARA - Academic Computing Services Amsterdam, The Netherlands * - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] ANNOUNCE: New version of pxeconfig/pxemenu utilities (3.0.0)]
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 Vliese-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
Re: [sisuite-users] ANNOUNCE: New version of pxeconfig/pxemenu utilities (3.0.0)]
There was a SARA setup leftover in this version. This is now fixed in
version 3.0.1:
{{{
3.0.1:
* Import AdvancedParser instead of sara location.
Author: Maarten van Ingen (SARA)
}}}
Bas van der Vlies wrote:
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 Vliese-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
Re: [sisuite-users] FC12 / ext4 support?
On 09-07-10 23:57, Jeremy Enos wrote: Anyone try out SI on FC12 yet? Any chance ext4 is supported? I haven't embarked yet, but the time is nearing- just trying to gauge what I'm in for. thx- Jeremy Jermey, We at SARA have build a new kernel/initrd setup that supports ext4, grub2 and a lot more. We still uses the systemimager tools to get the image. Only we have build a new kernel/initrd. It supports the generated scripts by systemimager, but it also has a new syntax, see * https://subtrac.sara.nl/oss/sali On this page there ia also an attachment that can be downloaded. This is a kernel and initrd for X86_64/amd64. Regards -- * Bas van der Vliese-mail: b...@sara.nl * * SARA - Academic Computing Services Amsterdam, The Netherlands * -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] how to disable tmpfs staging?
On 20-07-10 23:09, Tristam MacDonald wrote:
On Tue, Jul 20, 2010 at 12:51 PM, Brian Elliott Finley
br...@thefinleys.com wrote:
Tristam,
Are you using ext4? If so, I bet that's why. I'm in the process of
adding support for ext4 and grub2, but its not there yet.
Right you are - I am imaging an ubuntu 10.04 box, so ext4 and grub2 by
default. I just tested switching to ext3, and the imaging appears to
be proceeding perfectly, so I will mess with downgrading grub in the
morning.
Thanks,
If you want ext4 and grub2 support. You can can grab the kernel/initrd from
https://subtrac.sara.nl/oss/sali to replace the kernel/initrd that your are
know using.
We us a post-installation script that determines if we must use grub1 or grub2:
{{{
# Author: Bas van der Vlies
# Date : 6 Sep 2007
# Desc. : This will setup the GRUB bootloader
#
# SVN INFO:
# $Id: 02all.bootloader 4683 2010-06-23 12:15:04Z bas $
# $URL:
https://subtrac.sara.nl/hpcv/svn/beowulf/trunk/systemimager/boot_scripts/post-install/02all.bootloader
$
# Get the Systemimager variables
. /tmp/post-install/variables.txt
echo setting up grub: running grub..
#
if [ -e /etc/default/grub ]
then
echo Using GRUB2 install method! :: $DISK0
echo grub-install --no-floppy $DISK0
grub-install --no-floppy $DISK0
echo grub-mkconfig -o /boot/grub/grub.cfg
echo This command can take while...
grub-mkconfig -o /boot/grub/grub.cfg
echo GRUB2 install done
else
echo Using Legacy GRUB install method!
grub --batch EOF
root (hd0,0)
setup (hd0)
EOF
echo setting up grub: done.
fi
exit 0
}}}
--
* Bas van der Vliese-mail: b...@sara.nl *
* SARA - Academic Computing Services Amsterdam, The Netherlands *
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] how to disable tmpfs staging?
On 21-07-10 12:52, Tristam MacDonald wrote:
On Wed, Jul 21, 2010 at 3:00 AM, Bas van der Vliesb...@sara.nl wrote:
If you want ext4 and grub2 support. You can can grab the kernel/initrd from
https://subtrac.sara.nl/oss/sali to replace the kernel/initrd that your are
know using.
I saw the SALI kernel and gave it a spin, but it seems to take a
different set of parameters, and I haven't been able to figure out
which parameter I am feeding wrong.
With the default systemimager configuration, it boots fine, rsyncs the
script directory successfully, and then errors out with 'couldn't find
script'. Any idea how I pass it the image/script name?
You have to supply the scriptname parameter ;-). Here is an example:
{{{
default rsync_squeeze
label shell
kernel sali/trunk/kernel
append vga=extended initrd=sali/trunk/initrd.img ramdisk_size=32768
root=/dev/ram MONITOR_SERVER=si_monitor MONITOR_CONSOLE=yes SSHD=y
tmpfs_size=5000M rw
label rsync_squeeze
kernel sali/trunk/kernel
append vga=extended initrd=sali/trunk/initrd.img ramdisk_size=131072
root=/dev/ram MONITOR_SERVER=si_monitor MONITOR_CONSOLE=yes PROTOCOL=rsync
tmpfs_size=2400M STAGING=/tmp GRUB2=yes SCRIPTNAME=amd64_squeeze_lisa.master rw
label rsync_lenny
kernel sali/trunk/kernel
append vga=extended initrd=sali/trunk/initrd.img ramdisk_size=131072
root=/dev/ram MONITOR_SERVER=si_monitor MONITOR_CONSOLE=yes PROTOCOL=rsync
tmpfs_size=2400M STAGING=/tmp SCRIPTNAME=amd64_lenny_lisa.master rw
label bittorent
kernel sali/trunk/kernel
append vga=extended initrd=sali/trunk/initrd.img ramdisk_size=131072
root=/dev/ram MONITOR_SERVER=si_monitor MONITOR_CONSOLE=yes
PROTOCOL=bittorrent tmpfs_size=2400M STAGING=/tmp GRUB2=yes
SCRIPTNAME=amd64_squeeze_lisa.master rw
}}}
--
* Bas van der Vliese-mail: b...@sara.nl *
* SARA - Academic Computing Services Amsterdam, The Netherlands *
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] how to disable tmpfs staging?
On 21-07-10 13:34, Bas van der Vlies wrote:
On 21-07-10 12:52, Tristam MacDonald wrote:
On Wed, Jul 21, 2010 at 3:00 AM, Bas van der Vliesb...@sara.nl wrote:
If you want ext4 and grub2 support. You can can grab the kernel/initrd from
https://subtrac.sara.nl/oss/sali to replace the kernel/initrd that your are
know using.
I saw the SALI kernel and gave it a spin, but it seems to take a
different set of parameters, and I haven't been able to figure out
which parameter I am feeding wrong.
With the default systemimager configuration, it boots fine, rsyncs the
script directory successfully, and then errors out with 'couldn't find
script'. Any idea how I pass it the image/script name?
You have to supply the scriptname parameter ;-). Here is an example:
{{{
default rsync_squeeze
label shell
kernel sali/trunk/kernel
append vga=extended initrd=sali/trunk/initrd.img ramdisk_size=32768
root=/dev/ram MONITOR_SERVER=si_monitor MONITOR_CONSOLE=yes SSHD=y
tmpfs_size=5000M rw
label rsync_squeeze
kernel sali/trunk/kernel
append vga=extended initrd=sali/trunk/initrd.img ramdisk_size=131072
root=/dev/ram MONITOR_SERVER=si_monitor MONITOR_CONSOLE=yes PROTOCOL=rsync
tmpfs_size=2400M STAGING=/tmp GRUB2=yes SCRIPTNAME=amd64_squeeze_lisa.master
rw
label rsync_lenny
kernel sali/trunk/kernel
append vga=extended initrd=sali/trunk/initrd.img ramdisk_size=131072
root=/dev/ram MONITOR_SERVER=si_monitor MONITOR_CONSOLE=yes PROTOCOL=rsync
tmpfs_size=2400M STAGING=/tmp SCRIPTNAME=amd64_lenny_lisa.master rw
label bittorent
kernel sali/trunk/kernel
append vga=extended initrd=sali/trunk/initrd.img ramdisk_size=131072
root=/dev/ram MONITOR_SERVER=si_monitor MONITOR_CONSOLE=yes
PROTOCOL=bittorrent tmpfs_size=2400M STAGING=/tmp GRUB2=yes
SCRIPTNAME=amd64_squeeze_lisa.master rw
}}}
There is also an example master script that use GRUB2. We expect a
partition for grub2, see:
* https://subtrac.sara.nl/oss/sali/browser/trunk/example/masterscript.new
ans search for grub2
--
* Bas van der Vliese-mail: b...@sara.nl *
* SARA - Academic Computing Services Amsterdam, The Netherlands *
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] how to disable tmpfs staging?
On 21 jul 2010, at 23:38, Tristam MacDonald wrote:
On Wed, Jul 21, 2010 at 11:14 AM, Tristam MacDonald
swiftco...@gmail.com wrote:
I am a little confused how the master scripts work.
Do I manually edit (having made a backup copy) my image-name.master
script to include those features, or is there a way to modify
systemimager to generate a master script which works like that?
Having assumed that I manually create the master script at this point,
I have been able to create something that gets most of the way. Still
working on getting a valid grub config in place post imaging.
In case someone else is trying to use Ubuntu 10.04 with the SALI
kernel in the future, take note of the following:
- Ubuntu does not use a separate grub partition by default, so you
need to make one
- Ubuntu identifies partitions by UUIDs by default, so edit your
/etc/fstab to use partition names instead
- Ubuntu uses UUIDs in grub by default, so disable that in /etc/default/grub
Thanks for the info. We currently using it on debian lenny and squeeze and
converted a systemimager scriptt by hand. And yes we use labels to identify
partitions. To use the grub2 setup we have decided to use a seperate
partition. currently there is no function to generate the fstab file.
Hopefully some useful info and explanations:
We have just one master script for all our differrent hosts/oses., eg:
* ln -s base/sara_install_2 amd64_lenny_lisa.master
* will install the amd64_lenny_lisa image
* Is not necessary
Your kernel must support 'CONFIG_EFI_PARTITION=y'. If this option is set then
you can use the grub2 setup. Put in your master.script
- set_disklabel $DISK0 gpt
instead of:
{{{
### BEGIN partition $DISK0 ###
logmsg Partitioning $DISK0...
logmsg Old partition table for $DISK0:
parted -s -- $DISK0 print
# Wipe the MBR (Master Boot Record) clean.
logmsg dd if=/dev/zero of=$DISK0 bs=512 count=1 || shellout
dd if=/dev/zero of=$DISK0 bs=512 count=1 || shellout
# Re-read the disk label.
logmsg blockdev --rereadpt $DISK0
blockdev --rereadpt $DISK0
# Create disk label. This ensures that all remnants of the old label, whatever
# type it was, are removed and that we're starting with a clean label.
logmsg parted -s -- $DISK0 mklabel msdos || shellout
parted -s -- $DISK0 mklabel msdos || shellout
}}}
==
Further in the script file you see these lines. This are the partitions
logmsg partition $DISK0 1024:ext2:/boot:boot 1:grub2 4096:swap::swap
0:xfs:/:root
partition $DISK0 1024:ext2:/boot:boot 1:grub2 4096:swap::swap
0:xfs:/:root || shellout
See for full explanation:
* https://subtrac.sara.nl/oss/sali/wiki/SaliUsage/Functions/partition
The first entry 1024:ext2:/boot:boot:
{{{
will create an ext2 partition of size 1024 MB mounted /boot and with label boot
}}}
Used to be this code in masterscript for one partition:
{{{
logmsg Creating partition ${DISK0}1.
START_MB=$END_OF_LAST_PRIMARY
END_MB=$(echo scale=3; ($START_MB + 1024) | bc)
logmsg parted -s -- $DISK0 mkpart primary $START_MB $END_MB || shellout
parted -s -- $DISK0 mkpart primary $START_MB $END_MB || shellout
END_OF_LAST_PRIMARY=$END_MB
logmsg mke2fs -q ${DISK0}1 || shellout
mke2fs -q ${DISK0}1 || shellout
logmsg tune2fs -L boot ${DISK0}1 || shellout`
tune2fs -L boot ${DISK0}1 || shellout`
logmsg mkdir -p /a/boot || shellout
mkdir -p /a/boot || shellout
logmsg mount ${DISK0}1 /a/boot -t ext2 -o rw || shellout
mount ${DISK0}1 /a/boot -t ext2 -o rw || shellout
}}}
--
Tristam MacDonald
http://swiftcoder.wordpress.com/
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
--
Bas van der Vlies
b...@sara.nl
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] How can I see the System Imager error message?
here for more details: http://p.sf.net/sfu/dev2dev-palm ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- * Bas van der Vliese-mail: b...@sara.nl * * SARA - Academic Computing Services Amsterdam, The Netherlands * -- The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] How can I see the System Imager error message?
On 5 aug 2010, at 20:29, Patrick Nolan wrote: Bas van der Vlies wrote: On 04-08-10 21:57, Patrick Nolan wrote: Tristam MacDonald wrote: On Tue, Aug 3, 2010 at 3:56 PM, Patrick Nolan patrick.no...@stanford.edumailto:patrick.no...@stanford.edu wrote: I tried capturing the boot messages by echoing them out a serial port. (The AMI BIOS allows that.) It works up to a point, but the output quits when the kernel boots. Did you also tell your *kernel* to output over the console? If my memory serves correctly, you need to add something like console=ttyS0,57600 to the APPEND line in your pxelinux.cfg/whatever. Aha! That did the trick. I'm constantly learning new things. Now I can get down to debugging. The relevant messages are below. This appears to confirm my suspicion that the kernel doesn't have the necessary ethernet driver (igb for Intel 82576 controller) in place. Is it necessary to compile a custom kernel, or can this be done by configuration? If the latter, is it an OSCAR configuration or a System Imager configuration? You can try the kernel/initrd from https://subtrac.sara.nl/oss/sali. It should support the old systemimager scripts. igb is supported by this setup. Thanks. It looks interesting. Unfortunately the web page says that it needs a kernel version 2.6.27 or higher. I'm working with Centos 5, which uses 2.6.18. I'm not prepared to deal with the problems of a custom kernel. Just to be clear. This requirement is only for the udev that sali uses. The sali kernel/initrd is only used for installation. It has nothing to do with your version of centos kernel. -- Bas van der Vlies b...@sara.nl -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SALI: ping failure?
Chris, We will check it out and i add some more debug info. What version of SALI do you use and if it bombs out what is in: * cat /tmp/variables.txt. regards On 25 sep 2010, at 16:14, Chris Pepper wrote: No, it's getting a lease. Otherwise it wouldn't be able to download the code and wouldn't be trying to ping IMAGESERVER, but I do see it in the log. Thanks, Chris On 9/25/10 6:57 AM, Dennis Stam wrote: Chris, On 2010-09-25 02:37, Chris Pepper wrote: No joy work with IMAGESERVER on the append line in /var/lib/tftpboot/pxelinux.cfg/default either. I think that your network interface is unable to retrieve a DHCP lease. Chris label sali kernel sali-kernel append load_ramdisk=1 prompt_ramdisk=0 initrd=/sali-initrd root=/dev/ram rw ramdisk_size=103819 IMAGESERVER=10.0.2.10 SCRIPTNAME=l01.201009.master On 9/24/10 1:06 PM, Chris Pepper wrote: Dennis, Thanks. It looks like I didn't have or need to specify IMAGESERVER last month for a different cluster. Is this a SALI change? No this is not a SALI change, you can set the variable IMAGESERVER in your pxe config or with your dhcp server. See page https://subtrac.sara.nl/oss/sali/wiki/SaliUsage/DhcpOptions. Also, I now see https://subtrac.sara.nl/oss/sali/browser/trunk/example/masterscript.new. Are you recommending that instead of patching the SI-generated script? Chris On 9/24/10 2:02 AM, Dennis Stam wrote: Chris, Yes it's embedded in the pxelinux. To be exact in function ping_test. Have you set the IMAGESERVER variable? Regards, Dennis On 2010-09-23 23:00, Chris Pepper wrote: I'm using SALI with SI 4.0.2, and it hangs up on ping syntax. I don't see the ping command in the master script SI generated -- is it embedded in pxelinux? Thanks, Chris 4fa6d21f5a6118777675aaf03a8b035f sali.tar.gz ping_test Pinging your IMAGESERVER PING ATTEMPT 1: Busybox v1.17.1 (2010-08-20 15:42:16 CEST) multi-call binary. Usage: ping [OPTIONS] HOST Send ICMP ECHO_REQUEST packets to network hosts Options: ... Killing off running processes. write_variables / # Your autoinstall has failed. -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Bas van der Vlies b...@sara.nlmailto:b...@sara.nl -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev
[sisuite-users] ANNOUNCE: New version of pxeconfig/pxemenu utilities (4.0.2)
4.0.2: * Improved error handeling for AdvanceParser.py Author: Dennis Stam * debian/postinst. Use /bin/echo instead of echo else wrong entry in /etc/services, closes #13 Author: Bodo MeiBner bodo at bodo-m dot de Applied by: Bas van der Vlies * debian/control. Fixed dependecies problems for pxeconfig package. Added inetd | xinetd, closes #14 Author: Bodo MeiBner bodo at bodo-m dot de Applied by: Bas van der Vlies * pxemenu has been updated. See: - INSTALL-pxemenu - README-pxemenu - Updates for SYSLINUX version 4.02. - Some obsolete menus (UBC,Ghost) have been removed. Author: Ole Holm Nielsen * Added support for hosts that only can use mac address for pxelinux configuration. This is used in environments where dynamic ip's are used. To enable this you must set in pxeconfig.conf: [DEFAULT] arp_command: /usr/sbin/arp -n You can use host labels as shortcuts. Edit pxelinux.conf and add for eg: [bas] mac_address: 00:19:b9:de:21:47 Now you can use: 'pxeconfig bas' instead of 'pxeconfig 00:19:b9:de:21:47' You can mix hostnames and mac-addresses on the command line 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 or sali. 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 or sali 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 Vliese-mail: b...@sara.nl * * SARA - Academic Computing Services Amsterdam, The Netherlands * -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Request for help: Fighting spam on wiki.systemimager.org
On 04-11-10 19:08, Bernard Li wrote: Hi all: Lately our Wiki page http://wiki.systemimager.org has been getting a lot of spam. I am reaching out to the community to see if anybody has experience in fighting spam on MediaWiki installations and also to see if anybody would like to volunteer to be moderator for the Wiki and to undo spam edits on sight. Please feel free to reply back to this thread and/or email me off list. Thanks! Bernard On our trac project we use askimet for active spam filtering. There is also a plugin for mediawiki: * http://www.mediawiki.org/wiki/Extension:AkismetKlik -- * Bas van der Vliese-mail: b...@sara.nl * * SARA - Academic Computing Services Amsterdam, The Netherlands * -- The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book Blueprint to a Billion shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Integration with xCAT?
On 13 dec 2010, at 23:09, Greg Mason wrote: We're switching from having a variety of system management tools to managing our hardware with xCAT. We're looking to upgrade to a newer version of SystemImager and to finally retire our current (old) SI box (It even has old in the hostname!). I'd like to have SystemImager and xCAT live peacefully together on the same network, using xCAT's commands to be able to remotely powercycle and automatically provision systems. I'm looking for a good resource to do this integration. Currently, SystemImager controls DHCP, but I'd like that control to be given to xCAT, with xCAT triggering a system to netboot the SI installer image. I am also looking to take optimizations from Twitter's Murder (https://github.com/lg/murder) and apply them to SI for blasting images out in a more efficient manner. I can start helping out with this once I have a newer SI install running. Greg, Due our environment we had to update the systemimager software. we have changed a lot. You can find a description and the updated software at: - htps://subtrac.sara.nl/oss/sali we have replaced at lot software component. Maybe it is useful for you -- Bas van der Vlies b...@sara.nl -- Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] rhel6 - ext4 support
On 29 jan 2011, at 00:07, david.livingst...@cn.ca wrote: Is there a timeframe to have ext4 support ? David there is an alternative for systemimager and it is available at https://subtrac.sara.nl/oss/sali. Maybe it is useful for you. It support ext4. We use this now to install our clusters at SARA. -- Bas van der Vlies b...@sara.nl -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Question about sali and lvm creation
What version of SALI do you use?, I recommend using 1.4.5. The latest version is now 1.4.7 ;-) -- * Bas van der Vliese-mail: b...@sara.nl * * SARA - Academic Computing Services Amsterdam, The Netherlands * smime.p7s Description: S/MIME Cryptographic Signature -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Question about sali and lvm creation
Which SALI version do you use? The line must be: PART0_STR=1024:ext2:/boot:boot 1:grub2 4096:swap::swap Note: 1:grub2 And pxe setting GRUB2=yes You must have the grub utilities installed. If this does not work can you post your install script We use a postinstall script to install grub 1 or 2: = # # SVN INFO: # $Id: 02all.bootloader 4683 2010-06-23 12:15:04Z bas $ # $URL: https://subtrac.sara.nl/hpcv/svn/beowulf/trunk/systemimager/boot_scripts/post-install/02all.bootloader $ # Get the Systemimager variables . /tmp/post-install/variables.txt echo setting up grub: running grub.. # if [ -e /etc/default/grub ] then echo Using GRUB2 install method! :: $DISK0 echo grub-install --no-floppy $DISK0 grub-install --no-floppy $DISK0 echo grub-mkconfig -o /boot/grub/grub.cfg echo This command can take while... grub-mkconfig -o /boot/grub/grub.cfg echo GRUB2 install done else echo Using Legacy GRUB install method! grub --batch EOF root (hd0,0) setup (hd0) EOF echo setting up grub: done. fi exit 0 From: Jérémie Tétillon [mailto:j.tetil...@e-merchant.com] Sent: dinsdag 20 december 2011 15:41 To: sisuite-users@lists.sourceforge.net Subject: Re: [sisuite-users] Question about sali and lvm creation Hi all, Thanks for the replies, i managed to create a lvm partition I have another problem, since i can't get grub to install .. error: cannot find a device for / (is /dev mounted?) here are my partition definition : partition $DISK0 1024:ext2:/boot:boot 1:grub_bios::grub 0:none::lvm it fails with the same error with a msdos or gpt label, with GRUB2=yes or GRUB2=no in my pxelinux.cfg Any ideas ? Le 09/11/2011 12:33, Jérémie Tétillon a écrit : Hello, We used systemimager for 4 years in my company and we decided to try sali as the old kernel/initrd doesn't work out with some of our servers. I'm trying to use the new master script and i can't figure out how to create a lvm partition Am i missing something ? is it even possible ? Any help would be nice -- Jérémie Tétillon Administrateur Systèmes et Réseaux E-Merchant Service IT / PIXMANIA Group 43 av. de la grande Armée 75116 Paris -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Jérémie Tétillon Administrateur Systèmes et Réseaux Tel: +33 1.45.01.42.44 j.tetil...@e-merchant.commailto:j.tetil...@e-merchant.com E-Merchant Service IT / PIXMANIA Group 43 av. de la grande Armée 75116 Paris -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Question about sali and lvm creation
. appdeveloper.intel.com/joinhttp://appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Jérémie Tétillon Administrateur Systèmes et Réseaux Tel: +33 1.45.01.42.44 j.tetil...@e-merchant.commailto:j.tetil...@e-merchant.com E-Merchant Service IT / PIXMANIA Group 43 av. de la grande Armée 75116 Paris -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/joinhttp://appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Bas van der Vlies b...@sara.nlmailto:b...@sara.nl -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Question about sali and lvm creation
___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Jérémie Tétillon Administrateur Systèmes et Réseaux Tel: +33 1.45.01.42.44 j.tetil...@e-merchant.commailto:j.tetil...@e-merchant.com E-Merchant Service IT / PIXMANIA Group 43 av. de la grande Armée 75116 Paris -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/joinhttp://appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Jérémie Tétillon Administrateur Systèmes et Réseaux Tel: +33 1.45.01.42.44 j.tetil...@e-merchant.commailto:j.tetil...@e-merchant.com E-Merchant Service IT / PIXMANIA Group 43 av. de la grande Armée 75116 Paris -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/joinhttp://appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Jérémie Tétillon Administrateur Systèmes et Réseaux Tel: +33 1.45.01.42.44 j.tetil...@e-merchant.commailto:j.tetil...@e-merchant.com E-Merchant Service IT / PIXMANIA Group 43 av. de la grande Armée 75116 Paris -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/joinhttp://appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Bas van der Vlies b...@sara.nlmailto:b...@sara.nl -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Question about sali and lvm creation
/sisuite-users -- Jérémie Tétillon Administrateur Systèmes et Réseaux Tel: +33 1.45.01.42.44 j.tetil...@e-merchant.commailto:j.tetil...@e-merchant.com E-Merchant Service IT / PIXMANIA Group 43 av. de la grande Armée 75116 Paris -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/joinhttp://appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Jérémie Tétillon Administrateur Systèmes et Réseaux Tel: +33 1.45.01.42.44 j.tetil...@e-merchant.commailto:j.tetil...@e-merchant.com E-Merchant Service IT / PIXMANIA Group 43 av. de la grande Armée 75116 Paris -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/joinhttp://appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Jérémie Tétillon Administrateur Systèmes et Réseaux Tel: +33 1.45.01.42.44 j.tetil...@e-merchant.commailto:j.tetil...@e-merchant.com E-Merchant Service IT / PIXMANIA Group 43 av. de la grande Armée 75116 Paris -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/joinhttp://appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Jérémie Tétillon Administrateur Systèmes et Réseaux Tel: +33 1.45.01.42.44 j.tetil...@e-merchant.commailto:j.tetil...@e-merchant.com E-Merchant Service IT / PIXMANIA Group 43 av. de la grande Armée 75116 Paris -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/joinhttp://appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Bas van der Vlies b...@sara.nlmailto:b...@sara.nl -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] si-suite site down?
On 8 feb. 2012, at 08:38, Büchmann Hydrodynamics wrote: Hi, I am considering to use si-suite on two new small clusters. However, presently, the web site (systemimager.org) seems to be down, and the codes (sf.net/projects/systemimager and sf.net/projects/sisuite) apparently have not been updated since July 2009. As I follow the mailing list, I know that there is still some activity there, but it still makes me wonder about the status of the project. To the untrained eye, the project seems stale. I realize that I do not really ask any questions here, but as I have used sisuite since around 2003, I needed to tell that I am reluctant to use it on a new cluster. This is not due to lack of functionality, but rather state of the official sites of the project. Please, do not hesitate to tell me that I got it all wrong: that the website is up again soon and that there is just no reason to update a code, which has been perfect since 2009. Best, Bjarne Büchmann Barrne, I know is not an answer about systemimager, but you can try SALI ( https://subtrac.sara.nl/oss/sali). It started as fork of systemimager to address some issues (grub2 support). -- Bas van der Vlies b...@sara.nl -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] si-suite site down?
On 02/10/2012 05:21 PM, Tristam MacDonald wrote: On Fri, Feb 10, 2012 at 9:56 AM, Jan Groenewald j...@aims.ac.za mailto:j...@aims.ac.za wrote: Can you perhaps describe more extensively the relation between systemimager and SALI and your best guess as to the future developments over the next few years? And perhaps a specific note on the current status in SI and SALI of grub2, ext4, and systemconfigurator? Regards, Jan Until the devs have time to weight in, I'll give you the perspective of someone using them on a daily basis: SALI is a drop-in replacement for the default systemimager boot image (kernel and initrd). It has fairly good support for grub2 and ext4, and a vastly simplified command set for writing system imager install scripts. The rest of the systemimager suite you use as before. We use systemimager + SALI to image a lab of Ubuntu 11.04 machines, which works pretty much out of the box. The only caveat is that neither component has support for Debian's new disk UUIDs, so monkeying with your /etc/fstab and grub config may be required. Tristam, Do you mean that the 'blkid` command is not supported in busybox or are you missing something else? For our installions we use LABEL functionality, but we must also generate our /etc/fstab file. It is on out to do list to generate the fstab file. -- * Bas van der Vliese-mail: b...@sara.nl * * SARA - Academic Computing Services Amsterdam, The Netherlands * smime.p7s Description: S/MIME Cryptographic Signature -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SALI stater help needed
On 02/24/2012 08:30 AM, Büchmann Hydrodynamics wrote:
Hi Bas,
On 23-02-2012 8:01, Bas van der Vlies wrote:
Hi Bjarne,
Thanks very much for the rapid answer.
snip
We will assist you to tty to get SALI working on your systems.
That is ver much appreciated. I trust it is OK that I ask a few
clarifying questions before continuing.
grub or grub2 is not part of SALI (kernel/initrd). It is in your
client image.
That explains a lot. So systemimager-based scripts will fail once we get
to that part.
So we do chroot (postinstall script) to install the grub/grub2
bootloader.
With postinstall you mean after the rsync parts - but before the
following node boot, right?
yes, see master script:
{{{
logmsg chroot_mount_system_fs
chroot_mount_system_fs
## Let's get the image
# TODO: rewrite this so we can use PROTOCOL instead of using BITTORRENT yes/no
logmsg getimage
getimage
#
# Post Install Scripts
#
run_post_install_scripts
}}}
And just to be sure. The method you describe is _not_ based on the
systemimager scripts, but rather on the scripts coming with SALI
(masterscript.new and friends?)
the postinstall script are the same as for systemimager. Same mechanism.
I am sure we will get back to the actual scripts used, but to get
started I need to get the plainer details right first. I have the
SystemImager v4.1.6 Manual, but I *really* need some simple explanation
on how to go from tehre to SALI. For example, if I recall correctly, I
need to modify dhcpd.conf compared to plain systemimager to get
tftpboot process to do as expected(?)
dhcpd.conf is for systemimager and sali the same. You can set the sali image
server in the dhcp.conf:
* https://subtrac.sara.nl/oss/sali/wiki/SaliUsage/DhcpOptions
or set it in the pxelinux.cfg file:
* IMAGESERVER=imageserver
I got the kernel and initrd for x86_64 (sali-x86_64.tar.gz). We run
CentOS kernel 2.6.32-220.el6.x86_64, so we should be OK with your udev
version etc.
Also, can get the svn sources, but it is not clear how much is needed.
Ok the SALI kernel/initrd is only used for installation. It has nothing to do with your image. We use it for debian, ubuntu, centos,
suse, .
In short SALI detects your hardware, parition your disk, get the image and does some post-installations scripts, eg install boot
loader). The post-installations script will be down in chrooted enviroment. The centos image. You can use all commands that you are
used to.
I know that I am talking about simple stuff here. But for the sake of my
sanity I need to get it right. If you provide informatuion, then I shall
be happy to assist in actual writing some of the according docs afterwards.
We will appreciate this. The docs must be updated ;-)
snip
Sorry for all the stupid questions,
Bjarne
--
Virtualization Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
--
* Bas van der Vliese-mail: b...@sara.nl *
* SARA - Academic Computing Services Amsterdam, The Netherlands *
smime.p7s
Description: S/MIME Cryptographic Signature
--
Virtualization Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Grub2 Support
On 03/01/2012 12:27 AM, Damian Montaldo wrote: Hi, I'm new to system imager (great work BTW) I'm stuck in the lack of grub2 support, trying to give a chance before drop it. I read that there is (or was) some work in progress in http://www.mail-archive.com/sisuite-users@lists.sourceforge.net/msg05187.html It's true? there is some work in progress? Because I can't find anything useful in the trunk. I read about SALI and then start using it but I found that there is no native support to grub2 neither (starting from a fresh SI and SALI installation, you have to write a post-install script) So, I start writing some patches to SALI and the si_mkclientnetboot script to give grub2 support from scratch but I can't find a mailing list or a way to suggest patches (they have only a trac system). Any idea or suggestion? Any light at the end of the tunnel? ;) Thanks! Damian, SALI is a trac project. The trac project has also a ticket system. You can create a ticket and attach the patch or just email to: * s...@sara.nl Just updated the wiki with the email address for tickets, thanks for reporting -- * Bas van der Vliese-mail: b...@sara.nl * * SARA - Academic Computing Services Amsterdam, The Netherlands * smime.p7s Description: S/MIME Cryptographic Signature -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] ANNOUNCE: New version of SALI (1.5.0)
.5.0
* Added example directory
Author Bas van der Vlies
* Enabled 'blkid' command in busybox
Author Bas van der Vlies
* Fixed log location for tty4
Author: Dennis Stam
* Since busybox 1.19.0 command length has been removed. Now using ${#VAR}
to get the length of the variable VAR.
Author: Dennis Stam
* Updated kernel version to 3.1.4
* Updated busybox to 1.19.4
* Updated aria2 to 1.14.2
* Updated curl to 7.23.1
* Updated e2fsprogs to 1.42
* Updated jfsutils to 1.1.15
* Updated openssh to 5.9p1
* Updated LVM to 2.2.02.88
* Updated parted to 3.0
* Updated rsync to 3.0.9
* Updated scrub to 2.4.1
* Always copy installation log to /root/sali.log
Author: Bas van der Vlies
* Fixed report_task for rsync
Author: Bas van der Vlies
* sali log file is : /var/log/sali.log
Author: Bas van der Vlies
* Monitoring now logs to MONITOR_SERVER and /var/log/monitor.log.
So we can monitor the process on the node via ssh
Author: Bas van der Vlies
* If VERBOSE_LEVEL is greater or equal then 256. Then the getimage
image routine will be verbose (tar, rsync)
Author: Bas van der Vlies
* Added some post-install examples for:
- grub/grub2
- pxeconfig
Author: Dennis Stam
* Added VMXNET3 network module for kernel
Author: Bas van der Vlies
* Added grub2_install function
Author: Bas van der Vlies
* Added reboot function. If monitor is enabled first send a status
message and the use the real reboot
Author: Bas van der Vlies Dennis Stam
* Added SALI_VERSION environment variable so we can check which
version we use.
Author: Bas van der Vlies Dennis Stam
* Added xmlrpc-c to monitor aria via the rpc functionality. This way
the progress way more reliable then grepping the stdout of aria2c.
Fixes ticket #36
Author: Dennis Stam
* When we are using bittorrent, print that the image is being unpacked
Author: Dennis Stam
==
The latest stable SALI is available from:
ftp://ftp.sara.nl/pub/sali/sali.tar.gz
Information, documentation and reporting bugs for the package:
https://subtrac.sara.nl/oss/sali
--
* Bas van der Vliese-mail: b...@sara.nl *
* SARA - Academic Computing Services Amsterdam, The Netherlands *
smime.p7s
Description: S/MIME Cryptographic Signature
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] sda vs sdb confusion on install
On 05/08/2012 04:08 PM, Fiumara, Gregory wrote:
On 5/8/12 8:34 AM, e...@buchmann.dke...@buchmann.dk wrote:
Is there any way to fix the device naming, such that scsi 1:0:0:0 is
sdb also when I install?
You're going to be hard-pressed to have device naming be consistent. I
believe the kernel under CentOS 6 probes devices depth-first rather than
the older breadth-first method. You can force this back by adding the
kernel boot option pci=bfsort, and maybe that will help.
I've personally had SAN devices show up as sda before, which led me to
remove all unnecessary modules from the SystemImager boot kernel.
Sometimes those virtual devices are virtually attached via USB. If so,
you could remove USB support. You could also alter your master script to
detect if the virtual drive is sda and automatically format sdb instead,
but eliminating unnecessary devices is probably the better solution.
We had the same problem with SAN and decide to added the BLACKLIST option for
SALI
{{{
BLACKLIST=kernel_modules
Specify which kernel modules must be blacklisted to prevent udev from loading
them.
Specify as: BLACKLIST=module_a;module_b;module_c
}}}
In our install script we use the the /dev/ names. In the install script we set a LABEL on the disk and use this LABEL in the
/etc/fstab so we are not depended on the /dev/ names anymore.
regards
--
* Bas van der Vliese-mail: b...@sara.nl *
* SARA - Academic Computing Services Amsterdam, The Netherlands *
smime.p7s
Description: S/MIME Cryptographic Signature
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] sda vs sdb confusion on install
Presently, we are not running SALI. The problem (last I looked - and I _did_ spend time on it) the SALI project were missing quite basic information on how to get started. Simple stuff like which packages to install and how to get them. At the time you did try to help me and pointed at which main script to use. But even more basic information were missing, so in the end I just gave up. I still don't enven know, if SALI is a modification to install on top of already-installed SI, or something I should install from the bottom up. Surely, it is more than a single main script. Bjarne we are in the process of updating the docs. There is now some basic installation info and how to get started and how the dependencies are with systemimager/systemconfigurator. It still is work in progress. but we are slowly getting there ;-) In our install script we use the the /dev/ names. In the install script we set a LABEL on the disk and use this LABEL in the /etc/fstab so we are not depended on the /dev/ names anymore. That, of course, is one way to go about it, and I will consider it. I am trying to keep the chenges from the auto-generated script from systemimager to a minimum, but that could be a bad decision. It is a choice and it is nice if you do not have to change the automatic generated installation scripts. regards -- * Bas van der Vliese-mail: b...@sara.nl * * SARA - Academic Computing Services Amsterdam, The Netherlands * smime.p7s Description: S/MIME Cryptographic Signature -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] RE : RE : Building SystemImager on CentOS 6.2? HELP
You can replace the SI kernel/initrd with the SALI kernel/initrd when booting SI clients, and even run your old SI .master installation scripts! Some minor tweaks to the .master script must be performed as documented in https://subtrac.sara.nl/oss/sali/wiki/SaliUsage/UsingYourOldInstallScript. It really works! Of course, the installed CentOS 6.x client still won't boot due to systemconfigurator :-( SALI has their own master scripts which are a lot simpler than the SI scripts, but I think SALI hasn't been ported to CentOS 6.x yet because 1) SALI still relies upon systemconfigurator, and 2) SALI doesn't seem to support LVM. Just some comments on SALI. We use the SALI kernel/initrd on Debian, Centos and SUSE Linux PowerPC. The development is mostly donein a Debian enviroment, Only when you want to make you own kernel/initrd you have to compile it from scratch. We do not use the systemimager-server tools anymore. They are replaced by the SALI server tools. they are noy documented yet :-( As for the systemconfigurator tools we have replaced them partially by functions in the `initrd` and postinst scripts. So we get rid of the systemconfigurator tools. We have some ideas howto replace them with other tools. As for LVM the SALI kernel/initrd support it. For now there are now functions for it to hide the complexity. So you must do the basic LVM commands in the master script. In conclusion, it seems to me that if you can make systemconfigurator work correctly on CentOS 6.x, then SI and/or SALI should work as well for installing clients that will be bootable. We have implemented a `grub2_install` functions or create a postinst script that will do it for you -- * Bas van der Vliese-mail: b...@sara.nl * * SARA - Academic Computing Services Amsterdam, The Netherlands * smime.p7s Description: S/MIME Cryptographic Signature -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] ANNOUNCE: New version of pxeconfig/pxemenu utilities (4.1.0)
4.1.0: * Added two new configuration options for pxeconfig.conf file: closes #17 - client_script_hook_add: The script that must be run when we create a pxeconfig file for a host(s). This option replaces client_script_hook. - client_script_hook_remove : The script that must be run when we remove a pxeconfig file for a host(s) Both options are useful for firewall setups. To open/close ports. Reported by: Ramon Bastiaans (SARA) Fixed by: 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 or sali. 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 or sali 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 Vliese-mail: b...@sara.nl * * SARA - Academic Computing Services Amsterdam, The Netherlands * -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users smime.p7s Description: S/MIME Cryptographic Signature -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] UYOK fails when loading hotplug
On 17 nov. 2012, at 09:57, Gerasimatos, Dimitrios V (343K) dimitrios.v.gerasima...@jpl.nasa.govmailto:dimitrios.v.gerasima...@jpl.nasa.gov wrote: I see some people splintered off to do SALI and there has not been an official release in forever. Even the web page took some time to come back up. Should I be cutting my losses and moving on? System Imager has been a great tool for me to use for years now… Dimitri i can only speak for SALI. We have been releasing SALI via freecode: * http://freecode.com/projects/sali (1.5.6) * still updating the docs via https://subtrac.sara.nl/oss/sali We use is to install our clusters. So it is still alive and support modern hardware. The only part that we did not cover yet is SystemConfigurator. We have made some simple shell script functions to implement disk partition. We steadily implement more shell functions and improve SALI. -- Bas van der Vlies mail: b...@sara.nlmailto:b...@sara.nl SARA - Academic Computing Services , Amsterdam, The Netherlands -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] RE : new centos-6.3 RPMS
The missing piece for SALI is systemconfigurator. we didn't port it and our perl knowledge is not that good. so an up to date systemconfigurator with SALI is an good combination. regards On 21 nov. 2012, at 15:17, E-Blokos in...@e-blokos.commailto:in...@e-blokos.com wrote: Hi, I think the best would be to fork sisuite and create a new project, as SALI did. Regards Franck - Original Message - From: LAHAYE Oliviermailto:olivier.lah...@cea.fr To: sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net Sent: Wednesday, November 21, 2012 3:37 AM Subject: [sisuite-users] RE : new centos-6.3 RPMS Hi, I've successfully deployed my oscar images with those rpms. But I needed some post install scripts in order to have the grub bootloader installed. I've posted the postinstall script as well did you used them? Can you post a description of the problem you encountered? I must admit I feel a little bit alone and feedback is welcome. I'd also be very happy if a developper could revew my patches and if ok commit them to the svn. Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR De : Jing CDL Sun [sj...@cn.ibm.commailto:sj...@cn.ibm.com] Date d'envoi : mercredi 21 novembre 2012 08:16 À : sisuite-users Objet : [sisuite-users] new centos-6.3 RPMS Hi Olivier, Thanks for this sharing! Have you cloning Centos-6.3 with these rpms successfully? I tried to use them for redhat6.3 cloning, bug failed... -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Bas van der Vlies mail: b...@sara.nlmailto:b...@sara.nl SARA - Academic Computing Services , Amsterdam, The Netherlands -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] new centos-6.3 RPMS
That is good news. On 21 nov. 2012, at 15:42, E-Blokos in...@e-blokos.commailto:in...@e-blokos.com wrote: I planned to patch systemconfigurator but for now I'm too busy with other jobs... - Original Message - From: Bas van der Vlies b...@sara.nlmailto:b...@sara.nl To: sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net Sent: Wednesday, November 21, 2012 9:29 AM Subject: Re: [sisuite-users] RE : new centos-6.3 RPMS The missing piece for SALI is systemconfigurator. we didn't port it and our perl knowledge is not that good. so an up to date systemconfigurator with SALI is an good combination. regards On 21 nov. 2012, at 15:17, E-Blokos in...@e-blokos.commailto:in...@e-blokos.commailto:in...@e-blokos.com wrote: Hi, I think the best would be to fork sisuite and create a new project, as SALI did. Regards Franck - Original Message - From: LAHAYE Oliviermailto:olivier.lah...@cea.fr To: sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net Sent: Wednesday, November 21, 2012 3:37 AM Subject: [sisuite-users] RE : new centos-6.3 RPMS Hi, I've successfully deployed my oscar images with those rpms. But I needed some post install scripts in order to have the grub bootloader installed. I've posted the postinstall script as well did you used them? Can you post a description of the problem you encountered? I must admit I feel a little bit alone and feedback is welcome. I'd also be very happy if a developper could revew my patches and if ok commit them to the svn. Cheers, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR De : Jing CDL Sun [sj...@cn.ibm.commailto:sj...@cn.ibm.commailto:sj...@cn.ibm.com] Date d'envoi : mercredi 21 novembre 2012 08:16 À : sisuite-users Objet : [sisuite-users] new centos-6.3 RPMS Hi Olivier, Thanks for this sharing! Have you cloning Centos-6.3 with these rpms successfully? I tried to use them for redhat6.3 cloning, bug failed... -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov___ sisuite-users mailing list sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Bas van der Vlies mail: b...@sara.nlmailto:b...@sara.nl SARA - Academic Computing Services , Amsterdam, The Netherlands -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Bas van der Vlies mail: b...@sara.nlmailto:b...@sara.nl SARA - Academic Computing Services , Amsterdam, The Netherlands -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov
Re: [sisuite-users] RE : [Sisuite-devel] New systemimager rpms for centos6 with ext4 support
On 17 dec. 2012, at 10:16, LAHAYE Olivier olivier.lah...@cea.fr wrote: This means that your disk is not recognized. Did you use my install scripts (especially the pre-install). http://olivier.lahaye1.free.fr/RPMS/extra/si_scripts.tar.bz2 It modprobs some modules in order to see disks. I don't know my the systemimager initrd fails to automaticaly do that (did not have time to look at the problem). if you did use the script, it means that you need to modify it to have more modules inserted. Or, if your hardware is too recent (not supported by provided default kernel), then you'll need to use your own kernel for the moment. I cannot upgrade easily the kernel to 3.X as it'll require to upgrade some utils too and therefore, it'll break build on RHEL6 as well. Indeed, the build will copy missing stuffs from /lib /lib64 and other places and thoses version are for a 2.6.x kernel, not a 3.X kernel. This is also the reason why build fails on CentOS5 cas the libs copied from system misses some symbols (too old). In order to safely upgrade systemimager to latest kernel, we need to modifiy the build process so it builds everything and link everything with it's material which is not fully the case for now. (it still copy stuffs from the build system root tree (convenient ugly dirty hack)). Oliver, That is why SALI is around. It is only a kernel/initrd with up to date utilities that does a better job in detecting which hardware. The only problem is that we do not have an up to date systemconfigurator of other tools that generate the auto install scripts, Brian also posted http://download.systemimager.org/pub/ssm/README. Jing could replace the default system imager kernel/initrd with the SALI one. regards -- Bas van der Vlies mail: b...@sara.nl SARA - Academic Computing Services , Amsterdam, The Netherlands -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] new centos-6.3 RPMS
Brian, My github account is: basvandervlies Dennis github account: dstam regards On 15 dec. 2012, at 18:52, Brian Elliott Finley br...@thefinleys.com wrote: Dennis, That sounds like a good path forward. Please send me github account names for you and Bas, and I'll add you to the SystemImager project. Cheers, -Brian On Tue, Nov 27, 2012 at 12:16 PM, Dennis Stam dennis.s...@sara.nl wrote: Hi Brian, Great news to make SALI into SystemImager. It's better for both teams to join forces because we want to accomplish the same goal. On 27 nov. 2012, at 18:10, Brian Elliott Finley br...@thefinleys.commailto:br...@thefinleys.com wrote: I've created the initial repo. Bas -- what do you need from me to move the code from SourceForce to github? Currently we started the development of version 1.6 and it's far from finished. So as initial import to the git we can use the branch 1.5. And probally the easiest way to migrate our source code to the SystemImager git repo is to fork your repo. From there we can import our branch 1.5 to the forked git repo. And finally send you a pull request? Regards, Dennis https://github.com/finley/systemimager Thanks! On Tue, Nov 27, 2012 at 11:04 AM, Brian Elliott Finley br...@thefinleys.commailto:br...@thefinleys.com wrote: I think a move to github would be a fine idea. As for the SystemConfigurator functionality, I'd like to use the SystemImager post-script functionality. It will allow us to - include simple scripts upstream, that could be used as-is for simple and common cases - these simple scripts could be easily customized by site admins, without having to know SystemImager internals - a simple script could be used to invoke puppet, chef, or SSM (Simple State Manager - http://download.systemimager.org/pub/ssm/README) Cheers, -Brian On Mon, Nov 26, 2012 at 5:28 AM, Bas van der Vlies b...@sara.nlmailto:b...@sara.nl wrote: Brian, The SALI vork was nescessary to support modern hardware. Your are right you can better have one source. SALI has implemented a new kernel/initrd and some shell functions, e.g. one for easy disk partition. We also replaced the system imager-server software. Currently we do not have a tool like systemconfigurator or automatically generate installation scripts. So we can definitely benefit from co-operation. My thought for replacing systemconfigurator are with shell commands or a system maintenance tool like CFengine, puppet , chef ,…. Can we move the code to github.comhttp://github.com/http://github.comhttp://github.com/. I think it easier to contribute and better suited if more people are involved. regards On 23 nov. 2012, at 19:10, Brian Elliott Finley br...@thefinleys.commailto:br...@thefinleys.commailto:br...@thefinleys.commailto:br...@thefinleys.com wrote: Sun, Olivier, Please send me your SourceForge usernames. I appreciate your efforts, and would like to grant you both commit privileges to the SVN repository, so that you can commit your patches directly. Bas, Franck, the same goes for you two if you wish. Regarding a fork, that is generally necessary because one does not have the ability to modify the upstream original. I will happily grant you this access, as I think it would be better for the community to improve the main code stream rather than to have a fork. I know that SALI has special circumstances that made a fork appropriate for them, at least previously, but I would also be happy to allow that fork to merge into the mainstream if SALI considers that desirable. Lastly, with regard to SystemConfigurator, it is no longer being maintained, and we should work to eliminate our dependency on it. With modern Linuxes this should be very feasible through the use of SystemImager postscripts for setup of boot manager (Grub) and networking (if desirable). All -- feel free to call me if you have any questions. Just bear in mind that I'm generally somewhere in GMT-5 through GMT-7. ;-) If unsure, start with a text message, or leave a voice mail if I don't answer right away, but I'll be glad to discuss. My mobile is 469.444.0167tel:469.444.0167. Cheers, -Brian On Wed, Nov 21, 2012 at 1:16 AM, Jing CDL Sun sj...@cn.ibm.commailto:sj...@cn.ibm.commailto:sj...@cn.ibm.commailto:sj...@cn.ibm.com wrote: Hi Olivier, Thanks for this sharing! Have you cloning Centos-6.3 with these rpms successfully? I tried to use them for redhat6.3 cloning, bug failed... -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov
Re: [sisuite-users] new centos-6.3 RPMS
Brian, I am a but swamped at the moment and the holiday season is nearby ;-). There are tools that convert from sourceforge to github: * https://github.com/nirvdrum/svn2git#readme What is the plan: * convert systemimager svn (all) to github. We have a lot of versions, tags and branches * Where will SALI fit in. There are a lot of changes in the SALI release. Do we replace the kernelinitrd build process? In SALI we also replaced the system imager server software. regards On 18 dec. 2012, at 00:45, Brian Finley br...@thefinleys.com wrote: You guys have been added! https://github.com/finley/systemimager If you can help by doing the initial import of SystemImager from SourceForge SVN, that would be great. Let me know if you need anything from me. Thanks, -Brian On 12/17/2012 03:42 AM, Bas van der Vlies wrote: Brian, My github account is: basvandervlies Dennis github account: dstam regards On 15 dec. 2012, at 18:52, Brian Elliott Finley br...@thefinleys.com wrote: Dennis, That sounds like a good path forward. Please send me github account names for you and Bas, and I'll add you to the SystemImager project. Cheers, -Brian On Tue, Nov 27, 2012 at 12:16 PM, Dennis Stam dennis.s...@sara.nl wrote: Hi Brian, Great news to make SALI into SystemImager. It's better for both teams to join forces because we want to accomplish the same goal. On 27 nov. 2012, at 18:10, Brian Elliott Finley br...@thefinleys.commailto:br...@thefinleys.com wrote: I've created the initial repo. Bas -- what do you need from me to move the code from SourceForce to github? Currently we started the development of version 1.6 and it's far from finished. So as initial import to the git we can use the branch 1.5. And probally the easiest way to migrate our source code to the SystemImager git repo is to fork your repo. From there we can import our branch 1.5 to the forked git repo. And finally send you a pull request? Regards, Dennis https://github.com/finley/systemimager Thanks! On Tue, Nov 27, 2012 at 11:04 AM, Brian Elliott Finley br...@thefinleys.commailto:br...@thefinleys.com wrote: I think a move to github would be a fine idea. As for the SystemConfigurator functionality, I'd like to use the SystemImager post-script functionality. It will allow us to - include simple scripts upstream, that could be used as-is for simple and common cases - these simple scripts could be easily customized by site admins, without having to know SystemImager internals - a simple script could be used to invoke puppet, chef, or SSM (Simple State Manager - http://download.systemimager.org/pub/ssm/README) Cheers, -Brian On Mon, Nov 26, 2012 at 5:28 AM, Bas van der Vlies b...@sara.nlmailto:b...@sara.nl wrote: Brian, The SALI vork was nescessary to support modern hardware. Your are right you can better have one source. SALI has implemented a new kernel/initrd and some shell functions, e.g. one for easy disk partition. We also replaced the system imager-server software. Currently we do not have a tool like systemconfigurator or automatically generate installation scripts. So we can definitely benefit from co-operation. My thought for replacing systemconfigurator are with shell commands or a system maintenance tool like CFengine, puppet , chef ,…. Can we move the code to github.comhttp://github.com/http://github.comhttp://github.com/. I think it easier to contribute and better suited if more people are involved. regards On 23 nov. 2012, at 19:10, Brian Elliott Finley br...@thefinleys.commailto:br...@thefinleys.commailto:br...@thefinleys.commailto:br...@thefinleys.com wrote: Sun, Olivier, Please send me your SourceForge usernames. I appreciate your efforts, and would like to grant you both commit privileges to the SVN repository, so that you can commit your patches directly. Bas, Franck, the same goes for you two if you wish. Regarding a fork, that is generally necessary because one does not have the ability to modify the upstream original. I will happily grant you this access, as I think it would be better for the community to improve the main code stream rather than to have a fork. I know that SALI has special circumstances that made a fork appropriate for them, at least previously, but I would also be happy to allow that fork to merge into the mainstream if SALI considers that desirable. Lastly, with regard to SystemConfigurator, it is no longer being maintained, and we should work to eliminate our dependency on it. With modern Linuxes this should be very feasible through the use of SystemImager postscripts for setup of boot manager (Grub) and networking (if desirable). All -- feel free to call me if you have any questions. Just bear in mind that I'm generally somewhere in GMT-5 through GMT-7. ;-) If unsure
Re: [sisuite-users] new centos-6.3 RPMS
Brian, On 18 dec. 2012, at 22:15, Brian Elliott Finley br...@thefinleys.com wrote: Bas, No problem. I actually went through a dry run with svn2git yesterday. ;-) I'll take care of the initial import. That is nice The Plan: * Yes, we'll pull all of SystemImager into github. fine for me * How do you recommend that we incorporate SALI? It could be done as: - a branch - a fork (git style) - a branch with the intent to merge (would need more discussion on this one -- just want to maintain general applicability) SALI consists of: * SALI server -- could be an alternative for system imager server. Does a lot things automatically (rsync/bittorrent) * SALI kernel/initrd is more up to date then system imager kernel/initrd. The only problem for now is that the autoinstall scripts that are made by systemconfigurator does not work anymore because we removed some functions that are removed in SALI, we could be made available again and ported to the new SALI functions. so we are backwards compatible. Else we have to maintain two versions of kernel/initrd. That is a waste of time. regards Cheers, -Brian On Tue, Dec 18, 2012 at 1:54 PM, Bas van der Vlies b...@sara.nl wrote: Brian, I am a but swamped at the moment and the holiday season is nearby ;-). There are tools that convert from sourceforge to github: * https://github.com/nirvdrum/svn2git#readme What is the plan: * convert systemimager svn (all) to github. We have a lot of versions, tags and branches * Where will SALI fit in. There are a lot of changes in the SALI release. Do we replace the kernelinitrd build process? In SALI we also replaced the system imager server software. regards On 18 dec. 2012, at 00:45, Brian Finley br...@thefinleys.com wrote: You guys have been added! https://github.com/finley/systemimager If you can help by doing the initial import of SystemImager from SourceForge SVN, that would be great. Let me know if you need anything from me. Thanks, -Brian On 12/17/2012 03:42 AM, Bas van der Vlies wrote: Brian, My github account is: basvandervlies Dennis github account: dstam regards On 15 dec. 2012, at 18:52, Brian Elliott Finley br...@thefinleys.com wrote: Dennis, That sounds like a good path forward. Please send me github account names for you and Bas, and I'll add you to the SystemImager project. Cheers, -Brian On Tue, Nov 27, 2012 at 12:16 PM, Dennis Stam dennis.s...@sara.nl wrote: Hi Brian, Great news to make SALI into SystemImager. It's better for both teams to join forces because we want to accomplish the same goal. On 27 nov. 2012, at 18:10, Brian Elliott Finley br...@thefinleys.commailto:br...@thefinleys.com wrote: I've created the initial repo. Bas -- what do you need from me to move the code from SourceForce to github? Currently we started the development of version 1.6 and it's far from finished. So as initial import to the git we can use the branch 1.5. And probally the easiest way to migrate our source code to the SystemImager git repo is to fork your repo. From there we can import our branch 1.5 to the forked git repo. And finally send you a pull request? Regards, Dennis https://github.com/finley/systemimager Thanks! On Tue, Nov 27, 2012 at 11:04 AM, Brian Elliott Finley br...@thefinleys.commailto:br...@thefinleys.com wrote: I think a move to github would be a fine idea. As for the SystemConfigurator functionality, I'd like to use the SystemImager post-script functionality. It will allow us to - include simple scripts upstream, that could be used as-is for simple and common cases - these simple scripts could be easily customized by site admins, without having to know SystemImager internals - a simple script could be used to invoke puppet, chef, or SSM (Simple State Manager - http://download.systemimager.org/pub/ssm/README) Cheers, -Brian On Mon, Nov 26, 2012 at 5:28 AM, Bas van der Vlies b...@sara.nlmailto:b...@sara.nl wrote: Brian, The SALI vork was nescessary to support modern hardware. Your are right you can better have one source. SALI has implemented a new kernel/initrd and some shell functions, e.g. one for easy disk partition. We also replaced the system imager-server software. Currently we do not have a tool like systemconfigurator or automatically generate installation scripts. So we can definitely benefit from co-operation. My thought for replacing systemconfigurator are with shell commands or a system maintenance tool like CFengine, puppet , chef ,…. Can we move the code to github.comhttp://github.com/http://github.comhttp://github.com/. I think it easier to contribute and better suited if more people are involved. regards On 23 nov. 2012, at 19:10, Brian Elliott
Re: [sisuite-users] Kernel-3.5.* support
Ok. We have a project called sail: oss.trac.surfsara.nl/sali. This is an kernel/initrd.img dat can detect most modern hardware and has support for GPT partitions tables and grub2. On 14 feb. 2013, at 13:54, DongInn Kim di...@cs.indiana.edu wrote: Hi, That is the kernel that my distro (ubuntu-12.10) uses. I have tried the kernel that systemimager generated but my client nodes could not boot up with it. (Note, I have not checked what version kernel is generated.) Regards, -- - DongInn On Feb 14, 2013, at 4:46 AM, Bas van der Vlies bas.vandervl...@surfsara.nl wrote: Do you need this kernel version for your hardware? Or is a 3.x version sufficient? On 12 feb. 2013, at 19:54, DongInn Kim di...@cs.indiana.edu wrote: Hi, Is there any chance to support kernel-3.5.* or such sometime soon? It seems that it could not boot up even with uyok. Any suggestions would be really appreciated. Regards, -- - DongInn -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users --- As of 1 January 2013, SARA has a new name: SURFsara. Bas van der Vlies | Operations, Support Development | SURFsara | Science Park 140 | 1098 XG Amsterdam | T +31 (0) 20 592 30 00 | bas.vandervl...@surfsara.nl | www.surfsara.nl | -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users --- As of 1 January 2013, SARA has a new name: SURFsara. Bas van der Vlies | Operations, Support Development | SURFsara | Science Park 140 | 1098 XG Amsterdam | T +31 (0) 20 592 30 00 | bas.vandervl...@surfsara.nl | www.surfsara.nl | -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Systemimager on Debian Wheezy
On 7 mei 2013, at 21:40, christopher barry cba...@rjmetrics.com wrote: On Thu, 2013-05-02 at 09:23 +1200, Andrej wrote: Chances are http://www.mail-archive.com/sisuite-users@lists.sourceforge.net/msg05546.html helps ... :) On 1 May 2013 23:58, Vanush Misha mi...@cs.nuim.ie wrote: Hi all, I've followed instructions in Olivier's and Yann's emails (http://sourceforge.net/mailarchive/message.php?msg_id=30699920 and http://sourceforge.net/mailarchive/message.php?msg_id=30669672), but now an attempt to install systemimager-server on a (Debian Wheezy server) with apt-get install systemimager-server fails with unmet dependencies: The following packages have unmet dependencies: systemimager-server : Depends: mkisofs but it is not installable Depends: systemconfigurator (= 2.2.11) but it is not installable (there are also some unmet Recommends). Before I break my server, does anyone know can I safely force the package in place? On a separate note: where can I get sources used to build systemimager-related .deb packages? Thanks, Misha I may have begun this thread a while back - hard to tell now, but I was instructed to pull debs from the OSCAR site. I too ran into a bunch of dependency issues. Seriously to the point of thinking about doing a new SI completely (well, to fit my needs anyway). Still don't have a working SI install (it's missing GRUB2 support anyway, so it's not all that useful to me anyway as it turns out) Anyone here want to work on a new SI with me? I see the following for Si2: * apache served kernel / fat initramfs via iPXE and http * cgi based system w/iPXE scripting that determines what image to load based on MAC * use udp-cast with streamed cpio and crc32 to verify integrity The fat initramfs will have all the tools needed to get more tools from the server via curl or wget. The server will house scripts to accomplish certain tasks that can be easily definable. the client will pull these and the definitions. The initramfs will just spin doing tasks, rather than switch_root. could even do emdebian as a small iscsi-based boot image rather than just a fat initramfs, although not sure what that would buy. Thoughts? Is it worth it, or is making SI work without hair pulling simpler? Honestly, I'm jonesin' to do the new one if anyone is into it. christopher, Did you look at SALI ( https://oss.trac.surfsara.nl/sali)? regards --- As of 1 January 2013, SARA has a new name: SURFsara. Bas van der Vlies | Operations, Support Development | SURFsara | Science Park 140 | 1098 XG Amsterdam | T +31 (0) 20 592 30 00 | bas.vandervl...@surfsara.nl | www.surfsara.nl | -- AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
