You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(9) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(10) |
Feb
(2) |
Mar
(3) |
Apr
(2) |
May
(3) |
Jun
(50) |
Jul
(41) |
Aug
(76) |
Sep
(125) |
Oct
(83) |
Nov
(89) |
Dec
(32) |
2004 |
Jan
(78) |
Feb
(82) |
Mar
(129) |
Apr
(72) |
May
(110) |
Jun
(70) |
Jul
(76) |
Aug
(64) |
Sep
(41) |
Oct
(51) |
Nov
(36) |
Dec
(34) |
2005 |
Jan
(77) |
Feb
(57) |
Mar
(38) |
Apr
(26) |
May
(55) |
Jun
(68) |
Jul
(99) |
Aug
(80) |
Sep
(82) |
Oct
(141) |
Nov
(137) |
Dec
(51) |
2006 |
Jan
(133) |
Feb
(33) |
Mar
(156) |
Apr
(104) |
May
(88) |
Jun
(128) |
Jul
(110) |
Aug
(129) |
Sep
(74) |
Oct
(144) |
Nov
(127) |
Dec
(51) |
2007 |
Jan
(140) |
Feb
(140) |
Mar
(100) |
Apr
(42) |
May
(34) |
Jun
(13) |
Jul
(46) |
Aug
(46) |
Sep
(46) |
Oct
(42) |
Nov
(125) |
Dec
(23) |
2008 |
Jan
(15) |
Feb
(77) |
Mar
(57) |
Apr
(68) |
May
(48) |
Jun
(22) |
Jul
(54) |
Aug
(83) |
Sep
(41) |
Oct
(8) |
Nov
(37) |
Dec
(47) |
2009 |
Jan
(13) |
Feb
(11) |
Mar
(14) |
Apr
(55) |
May
(31) |
Jun
(18) |
Jul
(27) |
Aug
(17) |
Sep
(13) |
Oct
(39) |
Nov
(21) |
Dec
(16) |
2010 |
Jan
(10) |
Feb
(5) |
Mar
(15) |
Apr
(4) |
May
(9) |
Jun
(7) |
Jul
(20) |
Aug
(35) |
Sep
(37) |
Oct
(6) |
Nov
(12) |
Dec
(7) |
2011 |
Jan
(9) |
Feb
(6) |
Mar
(9) |
Apr
(78) |
May
(13) |
Jun
(6) |
Jul
(29) |
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(5) |
Dec
(12) |
2012 |
Jan
(1) |
Feb
(24) |
Mar
(12) |
Apr
(7) |
May
(12) |
Jun
(19) |
Jul
(8) |
Aug
(2) |
Sep
|
Oct
|
Nov
(35) |
Dec
(30) |
2013 |
Jan
(11) |
Feb
(13) |
Mar
(15) |
Apr
(18) |
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(2) |
2014 |
Jan
(23) |
Feb
(4) |
Mar
(11) |
Apr
(1) |
May
|
Jun
(1) |
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
(6) |
Feb
|
Mar
|
Apr
(1) |
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(2) |
Jun
(7) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
(3) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(2) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
(6) |
Apr
(1) |
May
(1) |
Jun
|
Jul
(4) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(6) |
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Büchmann H. <en...@bu...> - 2012-03-26 08:41:54
|
Just answering my own post, as I found a solution. The HP servers (Proliant SL390s G7) apparently were unhappy about the default localboot configuration, which is: <code> DEFAULT localhost LABEL localhost LOCALBOOT 0 </code> The solution lies in the argument to "LOCALBOOT", and changing it to "-1" works, so that the pxe config file reads: <code> DEFAULT localhost LABEL localhost LOCALBOOT -1 </code> This is likely an issue with the HP BIOS. Best, Bjarne On 20-03-2012 10:15, Büchmann Hydrodynamics wrote: > Hi, > > I am setting up a clustter with System Imager (pre-release of v4.2, i.e. > 4.1.99). The nodes are HP ProLiant SL390s G7 (half-width servers, eight > at a time in a common enclosure). We are running CentOS 6.2 (still > pretty vanilla). > > So far I got the system-configurator part seemingly OK, I can get an > image, and net-boot to distribute it to a new host. > However, on the following boot (pxe: localboot) the node dies with a red > screen of death (Illegal Opcode). Just before that happens, the console > states that it will boot from local hard disk. I am not sure what happens. > > The node has only a single local (internal) hard disk, so the problem > should not be related to SAN/NFS/NAS-disks, or to HP disk arrays etc. > > If I change the boot order (in BIOS) on the node to be hard disk before > PXE/net, then the ndoe boots happily from the disk, so it seems like the > imaging and grub-install was done OK. (I have also been checking the > system prior the the boot, by adding a "shellout" to the installation > script). Can the PXE/Localboot be misinterpreted by the node (HP > server)? What files should I check (/etc/dhcp/dhcpd.conf and > /tftpboot/pxelinux.cfg/{default,IPHEX} > > I have noted that there are a single thread on opcode problems on > sisuite-users back from 2010, and the reply from Kris Buytaert may be > related, but I am still not sure what to do. The idea of changing BIOS > (twice) to get an updated image does not really seem like a pretty solution. > > All help is welcome. > > Bjarne > > > ------------------------------------------------------------------------------ > 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 > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > |
From: Brian F. <br...@th...> - 2012-03-24 17:20:45
|
FYI... -------- Original Message -------- Subject: Re: [CI Ticketing System #18923] Please reset hung server: systemimager.ci.uchicago.edu Date: Sat, 24 Mar 2012 11:56:29 -0500 From: Brian Finley <br...@th...> To: su...@ci... CC: Andrea Righi <rig...@gm...>, Bernard Li <be...@va...> Thank you. I am currently planning to re-locate this content, so I may have just moved up my time-frame. ;-) I'll come by to retrieve the machine in April, and will get hold of you in advance to let you know when I'll be on-site. Thanks, David -Brian On 03/23/2012 03:44 PM, David Forero wrote: > On Fri Mar 23 15:12:46 2012, br...@th... wrote: >> It's still non-responsive: >> >> % ping -c 1 systemimager.ci.uchicago.edu >> PING systemimager.ci.uchicago.edu (128.135.125.209) 56(84) bytes of >> data. >> >> --- systemimager.ci.uchicago.edu ping statistics --- >> 1 packets transmitted, 0 received, 100% packet loss, time 10000ms >> >> >> Are any of the lights on? Can you try disconnecting, then re- >> connecting >> the power? > > Yes. I tried all those things. As I said, the machine displayed nothing on the > console. I suspect something serious may have happened to the machine. > > > -- > > David Forero > System Administrator > Computation Institute > University of Chicago > 773-834-4102 > -- Brian Elliott Finley Mobile: 469.444.0167 |
From: Büchmann H. <en...@bu...> - 2012-03-20 09:15:36
|
Hi, I am setting up a clustter with System Imager (pre-release of v4.2, i.e. 4.1.99). The nodes are HP ProLiant SL390s G7 (half-width servers, eight at a time in a common enclosure). We are running CentOS 6.2 (still pretty vanilla). So far I got the system-configurator part seemingly OK, I can get an image, and net-boot to distribute it to a new host. However, on the following boot (pxe: localboot) the node dies with a red screen of death (Illegal Opcode). Just before that happens, the console states that it will boot from local hard disk. I am not sure what happens. The node has only a single local (internal) hard disk, so the problem should not be related to SAN/NFS/NAS-disks, or to HP disk arrays etc. If I change the boot order (in BIOS) on the node to be hard disk before PXE/net, then the ndoe boots happily from the disk, so it seems like the imaging and grub-install was done OK. (I have also been checking the system prior the the boot, by adding a "shellout" to the installation script). Can the PXE/Localboot be misinterpreted by the node (HP server)? What files should I check (/etc/dhcp/dhcpd.conf and /tftpboot/pxelinux.cfg/{default,IPHEX} I have noted that there are a single thread on opcode problems on sisuite-users back from 2010, and the reply from Kris Buytaert may be related, but I am still not sure what to do. The idea of changing BIOS (twice) to get an updated image does not really seem like a pretty solution. All help is welcome. Bjarne |
From: Bas v. d. V. <ba...@sa...> - 2012-03-19 08:37:13
|
.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 Vlies e-mail: ba...@sa... * * SARA - Academic Computing Services Amsterdam, The Netherlands * ******************************************************************** |
From: Damian M. <dam...@gm...> - 2012-03-01 18:30:27
|
On Thu, Mar 1, 2012 at 12:15 PM, Damian Montaldo <dam...@gm...> wrote: > I'll try the SALI trac system and submit a ticket looking forward to > use grub2 from scratch. I wrote a ticket starting with 2 patches https://subtrac.sara.nl/oss/sali/ticket/35 Thanks. |
From: Damian M. <dam...@gm...> - 2012-03-01 15:15:44
|
On Thu, Mar 1, 2012 at 5:28 AM, Bas van der Vlies <ba...@sa...> wrote: > 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/sis...@li.../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: > * sa...@sa... > > Just updated the wiki with the email address for tickets, thanks for > reporting > > > -- > ******************************************************************** > * Bas van der Vlies e-mail: ba...@sa... * > * SARA - Academic Computing Services Amsterdam, The Netherlands * > ******************************************************************** Thanks for the info. And in SI there is some work in progress? Or I just drop it and use SALI? I know that it isn't only the grub2 support because for example you have a new kernel. I'll try the SALI trac system and submit a ticket looking forward to use grub2 from scratch. By the way, to use grub2 I have to write a post-install script right? I read that in one of your emails: http://www.mail-archive.com/sis...@li.../msg05486.html "I will add our grub2 post install script to our functions, So more people can use it." Thanks again for your help. |
From: Bas v. d. V. <ba...@sa...> - 2012-03-01 08:28:32
|
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/sis...@li.../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: * sa...@sa... Just updated the wiki with the email address for tickets, thanks for reporting -- ******************************************************************** * Bas van der Vlies e-mail: ba...@sa... * * SARA - Academic Computing Services Amsterdam, The Netherlands * ******************************************************************** |
From: Damian M. <dam...@gm...> - 2012-02-29 23:28:22
|
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/sis...@li.../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! |
From: Igor S. <sl...@ma...> - 2012-02-29 17:33:47
|
I plan to use a software raid and I'm don't sure that clonezilla would helps me Regards, Igor ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ From: rde...@pr... To: sl...@ma... Date: 20:21:33, 02.29.2012 Subject: Re: [sisuite-users] image on dvdrom ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ >>The main point of systemimager is to use the network. >> >> If you're looking for disk-based cloning, CloneZilla or a similar >> project may be more your speed. >> >> -R >> >> On 2/29/2012 4:10 AM, Igor Sobinov wrote: >> > Hello >> > I found that system imager is a great tool for linux deploy, but I need >> > to konw, is any way to put image that I need to install to boot DVD >> > disk, and not to use network for image rsync? >> > >> > Bye, Igor >> > >> >> -- >> Robby Desmond >> BiblioVault Operations Assistant >> University of Chicago Press >> http://www.bibliovault.org/ >> ph: 773-834-2387 >> cell: 773-458-0959 >> rde...@pr... >> >> |
From: Robby D. <rde...@pr...> - 2012-02-29 16:49:20
|
The main point of systemimager is to use the network. If you're looking for disk-based cloning, CloneZilla or a similar project may be more your speed. -R On 2/29/2012 4:10 AM, Igor Sobinov wrote: > Hello > I found that system imager is a great tool for linux deploy, but I need > to konw, is any way to put image that I need to install to boot DVD > disk, and not to use network for image rsync? > > Bye, Igor > -- Robby Desmond BiblioVault Operations Assistant University of Chicago Press http://www.bibliovault.org/ ph: 773-834-2387 cell: 773-458-0959 rde...@pr... |
From: Igor S. <sl...@ma...> - 2012-02-29 10:10:42
|
Hello I found that system imager is a great tool for linux deploy, but I need to konw, is any way to put image that I need to install to boot DVD disk, and not to use network for image rsync? Bye, Igor |
From: Bas v. d. V. <ba...@sa...> - 2012-02-24 09:33:41
|
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 > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users -- ******************************************************************** * Bas van der Vlies e-mail: ba...@sa... * * SARA - Academic Computing Services Amsterdam, The Netherlands * ******************************************************************** |
From: Büchmann H. <en...@bu...> - 2012-02-24 07:29:21
|
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? 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?) 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(?) 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. 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. <snip> Sorry for all the stupid questions, Bjarne |
From: Bas v. d. V. <ba...@sa...> - 2012-02-23 19:01:32
|
Hi Bjarne, We will assist you to tty to get SALI working on your systems. grub or grub2 is not part of SALI (kernel/initrd). It is in your client image. So we do chroot (postinstall script) to install the grub/grub2 bootloader. We use the following pxeconfig file. So you could ssh to installation node: {{{ default rsync 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 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 }}} PS) If you use grub then delete the GRUB2=yes from the line I must update the masterscript.new. But is still a good starting point for implementing SALI If something goes wrong you can ssh to the node: * default root password is: SaliRoot I only set the network parameters with systemconfigurator in a postinst script (systemconfigurator must be installed in the image). In a feature release we will make shell functions for this or something else. 01all.network one_interface() { systemconfigurator --confighw --confignet --stdin <<EOL [NETWORK] HOSTNAME = $DEFAULT_HOSTNAME [INTERFACE0] DEVICE = eth0 TYPE = dhcp EOL } For grub/grub2 we use this postinst script. {{{ 02all.bootloader Author: Bas van der Vlies # Date : 6 Sep 2007 # Desc. : This will setup the GRUB bootloader # # SVN INFO: # $Id$ # $URL$ # 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 }}} On 23 feb. 2012, at 13:32, Büchmann Hydrodynamics wrote: > Hi, > > We would very much like to try out SALI to install nodes on two small > clusters. Hardware is HP servers with intel Xeon Nehalem based CPUs. We > have installed frontends and a single node with CentOS 6. > > We have tried to use SystemImager scripts, but so far the effort has > stranded on missing boot strappers (grub/grub2) in the busybox (I > presume). Also, an expected command "discover" was not found. We have > successfully taken an image, and we can distribute the image to a new > node up to and including transfering files. Disk partitioning seems to > work, although (as I have seen before with systemimager) some partitions > may not end on a cylinder. But after testing for systemconfigurator > (found as 2.2.11) things starts to go amiss: > First there is a complaint "NETWORK_HOSTNAME expects an argument at line 2" > Then initrd is detected and set up as type "Initrd::RH". This should be > OK, since we run CentOS - a RHEL clone. Also the vmlinuz kernel seems to > be detected OK. > There is complaint that /proc/cpuinfo doesn't exist, and problems with > copy of /proc/mounts. > It seems to figure out that it should use Grub, but it does not work > out, and the final error is: > > Error: None of the following bootloaders were successfully setup on your > system: ... > > :: An error has occured, ... > > and the process stops. > In Busybox I find no /sbin/grub* commands, which could explain the > problem. I have grub in the transferred node image (/a/sbin/grub*), but > that is a different story. Also, the "discover" command is not found. > > I am pretty sure that we use the SALI kernel and initrd. tftpboot seems > to work also, but there are likely more than a single thing wrong. > > I don't know, if I should keep to try having the system-imager scripts > as the basis, or if I should try to switch to full-fledged SALI. I > should like to try the latter, but I don't see much of "Howto", "Get > started" or "FAQ" on the SALI page. I don't mind to have to fill in some > of that info eventually, but I simply don't know where to start to get > the things together. > > I am not a novice with regard to linux system administration, but I do > not have extensive experience with systemimager or how the inner parts > of kernel/initrd.img works. > > All help is welcome! > > Bjarne Büchmann > MSc, PhD. > > > ------------------------------------------------------------------------------ > 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 > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Bas van der Vlies ba...@sa... |
From: Büchmann H. <en...@bu...> - 2012-02-23 13:03:20
|
Hi, We would very much like to try out SALI to install nodes on two small clusters. Hardware is HP servers with intel Xeon Nehalem based CPUs. We have installed frontends and a single node with CentOS 6. We have tried to use SystemImager scripts, but so far the effort has stranded on missing boot strappers (grub/grub2) in the busybox (I presume). Also, an expected command "discover" was not found. We have successfully taken an image, and we can distribute the image to a new node up to and including transfering files. Disk partitioning seems to work, although (as I have seen before with systemimager) some partitions may not end on a cylinder. But after testing for systemconfigurator (found as 2.2.11) things starts to go amiss: First there is a complaint "NETWORK_HOSTNAME expects an argument at line 2" Then initrd is detected and set up as type "Initrd::RH". This should be OK, since we run CentOS - a RHEL clone. Also the vmlinuz kernel seems to be detected OK. There is complaint that /proc/cpuinfo doesn't exist, and problems with copy of /proc/mounts. It seems to figure out that it should use Grub, but it does not work out, and the final error is: Error: None of the following bootloaders were successfully setup on your system: ... :: An error has occured, ... and the process stops. In Busybox I find no /sbin/grub* commands, which could explain the problem. I have grub in the transferred node image (/a/sbin/grub*), but that is a different story. Also, the "discover" command is not found. I am pretty sure that we use the SALI kernel and initrd. tftpboot seems to work also, but there are likely more than a single thing wrong. I don't know, if I should keep to try having the system-imager scripts as the basis, or if I should try to switch to full-fledged SALI. I should like to try the latter, but I don't see much of "Howto", "Get started" or "FAQ" on the SALI page. I don't mind to have to fill in some of that info eventually, but I simply don't know where to start to get the things together. I am not a novice with regard to linux system administration, but I do not have extensive experience with systemimager or how the inner parts of kernel/initrd.img works. All help is welcome! Bjarne Büchmann MSc, PhD. |
From: Tristam M. <swi...@gm...> - 2012-02-16 20:45:10
|
On Wed, Feb 15, 2012 at 3:54 AM, Bas van der Vlies <ba...@sa...> wrote: > On 02/14/2012 08:57 PM, Tristam MacDonald wrote: > >> Has anyone tried using SALI to boot a VM instance running under WMWare's >> ESXi? >> > > Which virtual network device did you choose? I just googled something and > you can select the e1000 driver. The "VMware VMXNET3 Ethernet driver" is > not currently enabled in our setup. I will enable it i build a new version > of SALI > Ah, thank you. I must have glossed over network adapter selection when creating the VM - the e1000 driver does indeed do the trick. -- Tristam MacDonald |
From: Bas v. d. V. <ba...@sa...> - 2012-02-15 08:54:18
|
On 02/14/2012 08:57 PM, Tristam MacDonald wrote: > Has anyone tried using SALI to boot a VM instance running under WMWare's ESXi? > > I'm getting the following output when the boot process fails, and I assume it has something to do with SALI not recognising the > particular virtual ethernet adapter: > > s/tart_network/ > /IP Address not set with pre-boot settings./ > / > / > /Param DEVICE not set, guesing interface/ > / > / > /DHCP configuration failed/ > / > / > /Killing off running processes./ > > > And once at the recovery prompt, ifconfig won't show/manipulate any devices except lo. > > -- Tristam, Which virtual network device did you choose? I just googled something and you can select the e1000 driver. The "VMware VMXNET3 Ethernet driver" is not currently enabled in our setup. I will enable it i build a new version of SALI regards > Tristam MacDonald > System Administrator, Suffolk University Math & CS Department -- ******************************************************************** * Bas van der Vlies e-mail: ba...@sa... * * SARA - Academic Computing Services Amsterdam, The Netherlands * ******************************************************************** |
From: Tristam M. <swi...@gm...> - 2012-02-14 19:57:24
|
Has anyone tried using SALI to boot a VM instance running under WMWare's ESXi? I'm getting the following output when the boot process fails, and I assume it has something to do with SALI not recognising the particular virtual ethernet adapter: s*tart_network* *IP Address not set with pre-boot settings.* * * *Param DEVICE not set, guesing interface* * * *DHCP configuration failed* * * *Killing off running processes.* And once at the recovery prompt, ifconfig won't show/manipulate any devices except lo. -- Tristam MacDonald System Administrator, Suffolk University Math & CS Department |
From: Tristam M. <swi...@gm...> - 2012-02-14 03:49:30
|
On Mon, Feb 13, 2012 at 9:21 PM, Glauber Eller Martins < gla...@gm...> wrote: > Is it not only uncomment the line #GRUB_DISABLE_LINUX_UUID=true > on /etc/default/grub ? > In Ubuntu 10.10 and earlier, yes. In 11.04 they seem to have broken the option - or rather, it disables grub requiring UUIDs, but grub-update still generates configuration files containing UUIDs. I don't recall the exact specifics of disabling grub's UUIDs (although I have them written down somewhere). But most people at the time were just manually editing their grub files. -- Tristam MacDonald System Administrator, Suffolk University Math & CS Department http://swiftcoder.wordpress.com/ |
From: Glauber E. M. <gla...@gm...> - 2012-02-14 02:21:21
|
Is it not only uncomment the line #GRUB_DISABLE_LINUX_UUID=true on /etc/default/grub ? On Mon, Feb 13, 2012 at 3:21 PM, Tristam MacDonald <swi...@gm...>wrote: > On Mon, Feb 13, 2012 at 5:55 AM, Bas van der Vlies <ba...@sa...> wrote: > >> 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. > > > To be honest, I never tried to generate the fstab, since switching the > fstab over to old-fashioned device references is trivial. > > The grub2 config is a whole lot more troublesome, and it's very poorly > documented how to write a non-UUID grub config without manually overwriting > the output of update-grub. > > -- > Tristam MacDonald > System Administrator, Suffolk University Math & CS Department > http://swiftcoder.wordpress.com/ > > > ------------------------------------------------------------------------------ > 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 > sis...@li... > https://lists.sourceforge.net/lists/listinfo/sisuite-users > > -- Glauber Eller Martins |
From: Tristam M. <swi...@gm...> - 2012-02-13 17:21:23
|
On Mon, Feb 13, 2012 at 5:55 AM, Bas van der Vlies <ba...@sa...> wrote: > 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. To be honest, I never tried to generate the fstab, since switching the fstab over to old-fashioned device references is trivial. The grub2 config is a whole lot more troublesome, and it's very poorly documented how to write a non-UUID grub config without manually overwriting the output of update-grub. -- Tristam MacDonald System Administrator, Suffolk University Math & CS Department http://swiftcoder.wordpress.com/ |
From: Bas v. d. V. <ba...@sa...> - 2012-02-13 10:55:14
|
On 02/10/2012 05:21 PM, Tristam MacDonald wrote: > On Fri, Feb 10, 2012 at 9:56 AM, Jan Groenewald <ja...@ai... > <mailto:ja...@ai...>> 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 Vlies e-mail: ba...@sa... * * SARA - Academic Computing Services Amsterdam, The Netherlands * ******************************************************************** |
From: Tristam M. <swi...@gm...> - 2012-02-10 16:21:19
|
On Fri, Feb 10, 2012 at 9:56 AM, Jan Groenewald <ja...@ai...> 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 MacDonald System Administrator, Suffolk University Math & CS Department |
From: Jan G. <ja...@ai...> - 2012-02-10 16:01:52
|
Hi Brian, On 9 February 2012 00:11, Brian E Finley <br...@th...> wrote: > As for the project, it has been pretty stable, but I would recommend > taking a look st SALI, as Bas mentioned. > First off, thanks for the great Free Software. System Administrators are generalists, but if I am at all a one-trick pony, that trick is just using systemimager ;) Like the previous author I have been using systemimager since 2003 and some colleagues have migrated to other imaging projects citing the stagnation of systemimager. I still use systemimager, but for my Ubuntu 11.04 installs I change to grub1, and have to edit master scripts and one or two systemimager commands as the master is ext4 and the clients ext3. Also the systemconfigurator version is an SVN version from 2 years ago that the maintainer sent me, and I edit the master script to remove --runboot; and manually run grubfix.sh (my script) after the imaging. Some (long) time back I read on the mailing list that systemimager maintainers use Ubuntu themselves, and so would soon feel the pain of grub and ext4, and would be working on these. 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 -- .~. /V\ Jan Groenewald /( )\ www.aims.ac.za ^^-^^ |
From: Büchmann H. <en...@bu...> - 2012-02-09 07:19:08
|
Thanks very much, Brian. We will take SALI for a spin - and I look forward to see systemimager.org again. Best, Bjarne Büchmann On 08-02-2012 11:11, Brian E Finley wrote: > All, > > The site had an issue and is temporarily down, but I'm working to get that resolved (server hung and it's remote hosted). I made contact with the local admins today, so I'm hoping to see it online shortly. Then I'll be looking to relocate it to Dallas (where I now live). > > As for the project, it has been pretty stable, but I would recommend taking a look st SALI, as Bas mentioned. > > Also, xCAT can work with SystemImager. xCAT had integrated SystemImager support back in v1.x, but it wasn't brought forward in the v2 re-write. However, it is still doable. > > Cheers, -Brian > > > Brian E Finley > 469.444.0167 > |