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
> sisuite-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sisuite-users
--
Bas van der Vlies
b...@sara.nl
------------------------------------------------------------------------------
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
