I ran these a few weeks ago.  I've attached my long and boring notes.



On Fri, Nov 04, 2005 at 10:06:16PM -0600, Jeremy Enos wrote:
> Anyone test the rpm based installation directions lately?  Downloads 
> seem to fail on about half of the packages.
> 
> http://www.systemimager.org/download/
> 
>    Jeremy
> 
> 
> 
> -------------------------------------------------------
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/sisuite-users

-- 

-ashley

Did you try poking at it with a stick?

________________________________________________________________________________
9/8/2005

Running systemimager-3.4.1 rpms on suse linux


________________________________________________________________________________
Note 11/07/2005:
I never got 3.4.1 to work.  primary reason was 3.4.1 does not support
creation of filesystems under linux LVM.  I also ran into problems
getting rsync across our internal firewall.  I tried to rebuild 3.4.1
from source to include ssh support, but I never finished the build.
I moved on to systemimager-3.5.3 instead.
________________________________________________________________________________



Things are different than in the sis docs page.  This needs updating bad:
http://www.systemimager.org/doc/html/x184.html



According to http://www.systemimager.org/download/
I install sis server as follows:
        
  RPM Based Distributions 1) Download the System Installation Suite "install"
  script and make it executable:
  
    cd /tmp
    wget http://sisuite.org/install
    chmod +x install
     
  
  2) Get a listing of available System Installation Suite packages:
  
    ./install --list
     
  
  3) Install the components of System Installation Suite that you need. Any
  System Installation Suite packages your selection depends on will also be
  downloaded and installed. In addition to any other components, you probably
  want to install at least one SystemImager "boot" package.
  
    ./install --verbose <package_one> <package_two> ...
     
  Note: Try "./install --help" to see other options.





Here is a package list for the whole SISuite:

#
# SIS Stable -- 2004.03.02
#
# $Id: stable.list,v 1.7 2005/06/06 18:52:20 brianfinley Exp $
#

# Base url is
# http://install.sisuite.org/sourceforge/

# Flamethrower
systemimager/flamethrower-0.1.6-1.noarch.rpm


systemconfig/systemconfigurator-2.2.2-1.noarch.rpm
systemconfig/perl-AppConfig-1.52-4.noarch.rpm


systemimager/systemimager-i386boot-standard-3.4.1-1.noarch.rpm 
/systemimager/systemimager-ia64boot-standard-3.4.1-1.noarch.rpm
systemimager/systemimager-common-3.4.1-1.noarch.rpm
systemimager/systemimager-server-3.4.1-1.noarch.rpm
systemimager/systemimager-client-3.4.1-1.noarch.rpm
systemimager/systemimager-flamethrower-3.4.1-1.noarch.rpm

# SystemInstaller
systeminstaller/systeminstaller-1.04-1.noarch.rpm
systeminstaller/systeminstaller-x11-1.04-1.noarch.rpm




________________________________________________________________________________
Installing server:



So here goes the install:

nimol:/tmp # wget http://sisuite.org/install
--10:55:17--  http://sisuite.org/install
           => `install'
Resolving sisuite.org... 66.35.250.210
Connecting to sisuite.org[66.35.250.210]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13,876 [text/plain]

100%[====================================>] 13,876        --.--K/s             

10:55:17 (837.61 KB/s) - `install' saved [13876/13876]

nimol:/tmp # chmod +x install

nimol:/tmp # ./install --list
Packages available for download and/or install:

  flamethrower
  perl-AppConfig
  perl-MLDBM
  systemconfigurator
  systemimager-client
  systemimager-common
  systemimager-flamethrower
  systemimager-i386boot-standard
  systemimager-server
  systeminstaller
  systeminstaller-x11

To install packages, do a:

  ./install --verbose PKG1 PKG2 ...

For example:

  ./install --verbose systemconfigurator perl-AppConfig





I'll install some of the prerequisits:

nimol:/tmp # rpm -q rsync perl-DBI perl-Tk  perl-XML-Simple
package rsync is not installed
package perl-DBI is not installed
package perl-Tk is not installed
package perl-XML-Simple is not installed
nimol:/tmp # yast2 --install rsync perl-DBI perl-Tk  perl-XML-Simple
nimol:/tmp # rpm -q rsync perl-DBI perl-Tk  perl-XML-Simple
rsync-2.6.3-7
perl-DBI-1.47-3
perl-Tk-800.024-431
perl-XML-Simple-2.12-3






After running ./install --help, I settled on this:

nimol:/tmp # ./install --verbose --directory /root/downloads/systemimager 
--download-only systemimager-client systemimager-common 
systemimager-i386boot-standard systemimager-server
Downloading: http://sisuite.org/tags/stable.list...done!
Downloading: 
http://install.sisuite.org/sourceforge/systemimager/systemimager-client-3.4.1-1.noarch.rpm...done!
Downloading: 
http://install.sisuite.org/sourceforge/systemimager/systemimager-common-3.4.1-1.noarch.rpm...done!
Downloading: 
http://install.sisuite.org/sourceforge/systemimager/systemimager-i386boot-standard-3.4.1-1.noarch.rpm
 ...done!
Downloading: 
http://install.sisuite.org/sourceforge/systemimager/systemimager-server-3.4.1-1.noarch.rpm...done!
################################################################################

 Thanks for using System Installation Suite.



nimol:~/downloads/systemimager # ll
total 5613
drwxr-xr-x  2 root root     288 Sep  9 11:31 .
drwxr-xr-x  3 root root     176 Sep  9 11:31 ..
-rw-r--r--  1 root root   54216 Apr 20 23:25 
systemimager-client-3.4.1-1.noarch.rpm
-rw-r--r--  1 root root   54918 Apr 20 23:08 
systemimager-common-3.4.1-1.noarch.rpm
-rw-r--r--  1 root root 5473230 Apr 20 23:11 
systemimager-i386boot-standard-3.4.1-1.noarch.rpm
-rw-r--r--  1 root root  150559 Apr 20 23:11 
systemimager-server-3.4.1-1.noarch.rpm


nimol:~/downloads/systemimager # rpm -ihv --test *
error: Failed dependencies:
        systemconfigurator is needed by systemimager-client-3.4.1-1
        perl-AppConfig is needed by systemimager-client-3.4.1-1
        mtools is needed by systemimager-client-3.4.1-1
        systemconfigurator is needed by systemimager-common-3.4.1-1
        perl-AppConfig is needed by systemimager-server-3.4.1-1
        dosfstools is needed by systemimager-server-3.4.1-1




I need to install systemconfigurator and perl-AppConfig:

nimol:~/downloads/systemimager # ./install --verbose --directory 
/root/downloads/systemimager --download-only systemconfigurator perl-AppConfig
Downloading: http://sisuite.org/tags/stable.list...done!
Downloading: 
http://install.sisuite.org/sourceforge/systemconfig/systemconfigurator-2.2.2-1.noarch.rpm...done!
Downloading: 
http://install.sisuite.org/sourceforge/systemconfig/perl-AppConfig-1.52-4.noarch.rpm...done!




Still a few failed dependancies.
nimol:~/downloads/systemimager # rpm -ihv --test *.rpm
error: Failed dependencies:
        mtools is needed by systemimager-client-3.4.1-1
        dosfstools is needed by systemimager-server-3.4.1-1


I installed these from SuSE rpms:

nimol:~/downloads/systemimager # yast2 --install mtools dosfstools
nimol:~/downloads/systemimager # rpm -ihv  *.rpm
Preparing...                ########################################### [100%]
   1:perl-AppConfig         ########################################### [ 17%]
   2:systemconfigurator     ########################################### [ 33%]
   3:systemimager-common    ########################################### [ 50%]
   4:systemimager-client    ########################################### [ 67%]
   5:systemimager-server    ########################################### [ 83%]
Shutting down xinetd:                                                done
Starting INET services. (xinetd)                                     done
systemimager-server-rsyncd  0:off  1:off  2:off  3:on   4:off  5:on   6:off
   6:systemimager-i386boot-s########################################### [100%]




OK, that worked!  here are the init scripts:

nimol:~/downloads/systemimager # find /etc/init.d/ -mtime -1 -ls
drwxr-xr-x  11 root     root  2680 Sep  9 16:09 /etc/init.d/
drwxr-xr-x   2 root     root  1400 Sep  9 16:09 /etc/init.d/rc3.d
lrwxrwxrwx   1 root     root    29 Sep  9 16:09 
/etc/init.d/rc3.d/S08systemimager-server-rsyncd -> ../systemimager-server-rsyncd
lrwxrwxrwx   1 root     root    29 Sep  9 16:09 
/etc/init.d/rc3.d/K14systemimager-server-rsyncd -> ../systemimager-server-rsyncd
drwxr-xr-x   2 root     root  1576 Sep  9 16:09 /etc/init.d/rc5.d
lrwxrwxrwx   1 root     root    29 Sep  9 16:09 
/etc/init.d/rc5.d/S08systemimager-server-rsyncd -> ../systemimager-server-rsyncd
lrwxrwxrwx   1 root     root    29 Sep  9 16:09 
/etc/init.d/rc5.d/K14systemimager-server-rsyncd -> ../systemimager-server-rsyncd
-rw-r--r--   1 root     root  1352 Sep  9 16:09 /etc/init.d/.depend.boot
-rw-r--r--   1 root     root  1818 Sep  9 16:09 /etc/init.d/.depend.stop
-rw-r--r--   1 root     root  1780 Sep  9 16:09 /etc/init.d/.depend.start



I added my own suse stile rc hook:

nimol:~ # ln -s /etc/init.d/systemimager-server-rsyncd 
/usr/sbin/rcsystemimager-server-rsyncd



And we are good:

nimol:~ # rcsystemimager-server-rsyncd status
Usage: r-server-rsyncd {start|stop|restart|force-reload}
nimol:~ # rcsystemimager-server-rsyncd start
Starting rsync daemon for systemimager: rsync.

root     10705  0.0  0.1   3356  1100 ?        Ss   16:19   0:00 /usr/bin/rsync 
--daemon --config=/etc/systemimager/rsyncd.conf

tcp        0      0 0.0.0.0:873             0.0.0.0:*               LISTEN      
0          26403      10705/rsync         








________________________________________________________________________________
Installing client:



now for a client        venus


venus:~/downloads # mkdir systemimager
venus:~/downloads # cd systemimager
venus:~/downloads/systemimager # wget http://sisuite.org/install
--17:27:44--  http://sisuite.org/install
           => `install'
Resolving sisuite.org... 66.35.250.210
Connecting to sisuite.org|66.35.250.210|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 13,876 [text/plain]

100%[====================================>] 13,876        --.--K/s             

17:27:44 (2.24 MB/s) - `install' saved [13,876/13,876]

venus:~/downloads/systemimager # chmod +x install 
venus:~/downloads/systemimager # ./install  --verbose --directory 
/root/downloads/systemimager --download-only systemconfigurator perl-AppConfig 
systemimager-common systemimager-client
Downloading: http://sisuite.org/tags/stable.list...done!
Downloading: 
http://install.sisuite.org/sourceforge/systemconfig/systemconfigurator-2.2.2-1.noarch.rpm...done!
Downloading: 
http://install.sisuite.org/sourceforge/systemconfig/perl-AppConfig-1.52-4.noarch.rpm...done!
Downloading: 
http://install.sisuite.org/sourceforge/systemimager/systemimager-common-3.4.1-1.noarch.rpm...done!
Downloading: 
http://install.sisuite.org/sourceforge/systemimager/systemimager-client-3.4.1-1.noarch.rpm...done!



venus:~/downloads/systemimager # rpm -ihv --test *.rpm 
Preparing...                ########################################### [100%]
venus:~/downloads/systemimager # rpm -ihv  *.rpm 
Preparing...                ########################################### [100%]
   1:perl-AppConfig         ########################################### [ 25%]
   2:systemconfigurator     ########################################### [ 50%]
   3:systemimager-common    ########################################### [ 75%]
   4:systemimager-client    ########################################### [100%]

These are the server rpms installed:
systemimager-i386boot-standard-3.4.1-1        Fri Sep  9 16:09:45 2005
systemimager-server-3.4.1-1                   Fri Sep  9 16:09:44 2005
systemimager-common-3.4.1-1                   Fri Sep  9 16:09:44 2005
systemimager-client-3.4.1-1                   Fri Sep  9 16:09:44 2005
systemconfigurator-2.2.2-1                    Fri Sep  9 16:09:43 2005
perl-AppConfig-1.52-4                         Fri Sep  9 16:09:43 2005






________________________________________________________________________________
prepare the client:

venus:~ # si_prepareclient --server 128.48.111.106

Welcome to the SystemImager si_prepareclient command.  This command may modify
the following files to prepare your golden client for having its image 
retrieved by the imageserver.  It will also create the /etc/systemimager 
directory and fill it with information about your golden client.  All modified
files will be backed up with the .before_systemimager-3.4.1 extension.

 /etc/services:
   This file defines the port numbers used by certain software on your system.
   Entries for rsync will be added if necessary.

 /tmp/rsyncd.conf.29790:
   This is a temporary configuration file that rsync needs on your golden client
   in order to make your filesystem available to your SystemImager server.

 inetd configuration:
   SystemImager needs to run rsync as a standalone daemon on your golden client
   until it's image is retrieved by your SystemImager server.  If rsyncd is 
   configured to run as a service started by inetd, it will be temporarily
   disabled, and any running rsync daemons or commands will be stopped.  Then,
   an rsync daemon will be started using the temporary configuration file
   mentioned above.
   
See "si_prepareclient --help" for command line options.

Continue? (y/[n]): y


*********************************** WARNING *********************************** 
This utility starts an rsync daemon that makes all of your files accessible
by anyone who can connect to the rsync port of this machine.  This is the 
case until you reboot, or kill the 'rsync --daemon' process by hand.  By 
default, once you use si_getimage to retrieve this image on your imageserver, 
these contents will become accessible to anyone who can connect to the rsync 
port on your imageserver.  See rsyncd.conf(5) for details on restricting 
access to these files on the imageserver.  See the systemimager-ssh package
for a more secure method of making images available to clients.
*********************************** WARNING *********************************** 

Continue? (y/[n]): y


Using "sfdisk" to gather information about disk:
    /dev/sda

Starting or re-starting rsync as a daemon.....
done!

This client is ready to have its image retrieved.  You must now run 
the "si_getimage" command on your imageserver.








________________________________________________________________________________
Get the client image to the server:


nimol:~ # si_getimage --golden-client venus.ucop.edu --image 
shibboleth-dev_venus.ucop.edu --directory /images0/

This program will get the "shibboleth-dev_venus.ucop.edu" system image from 
"venus.ucop.edu"
making the assumption that all filesystems considered part
of the system image are using ext2, ext3, jfs, FAT, reiserfs, or xfs.

This program will not get /proc, NFS, or other filesystems
not mentioned above.

*********************************** WARNING *********************************** 
All files retrieved from a golden client are, by default, made accessible to 
anyone who can connect to the rsync port of this machine.  See rsyncd.conf(5)
for details on restricting access to these files on the imageserver.  See the
systemimager-ssh package for a more secure (but less effecient) method of 
making images available to clients.
*********************************** WARNING *********************************** 

See "si_getimage --help" for command line options.

Continue? ([y]/n): y
  

An image named "shibboleth-dev_venus.ucop.edu" already exists...
Update existing image? ([y]/n): 

Retrieving /etc/systemimager/mounted_filesystems from venus.ucop.edu to check 
for mounted filesystems...
------------- venus.ucop.edu mounted_filesystems RETRIEVAL PROGRESS 
-------------

nimol:~ # rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(242)
No packets ariving at venus.  Try again tomorrow.


I suspect rsync is denied into the dmz from 134 by our firewall.  
Perhaps I can use rsync over ssh to bypass the firewall restrictions.







________________________________________________________________________________
Buildin systemimager with the ssh extention.
(I never got this to work)


the download page says:

         SSH Support (optional)
        
        Mandrake, Redhat, SuSE, and other RPM Based Distributions
        
        Due to unresolved crypto distribution concerns, RPM based users must
        currently build their own systemimager-ssh package. Simply download the
        systemimager-source tarball to your imageserver, unpack it, and execute
        the following command:
        
          make WITH_SSH=1 install_ssh_tarball
   




wget 
http://internap.dl.sourceforge.net/sourceforge/systemimager/systemimager-3.4.1.tar.bz2
wget 
http://internap.dl.sourceforge.net/sourceforge/systemimager/systemimager-3.4.1.tar.bz2.sign

nimol:~/build # tar jxvf ../downloads/systemimager/systemimager-3.4.1.tar.bz2




Building from source

remove rpms:

nimol:~/build/systemimager-3.4.1 # rpm -e --test systemimager-server 
perl-AppConfig systemconfigurator systemimager-common systemimager-client 
systemimager-i386boot-standard
nimol:~/build/systemimager-3.4.1 # rpm -e systemimager-server perl-AppConfig 
systemconfigurator systemimager-common systemimager-client 
systemimager-i386boot-standard
Stopping rsync daemon for systemimager: rsync.
systemimager-server-rsyncd  0:off  1:off  2:off  3:off  4:off  5:off  6:off


The README file says:

   Building and/or Installing SystemImager from Source
   -----------------------------------------------------------------------------
   SystemImager should now build on most any distribution, as well as work
   on any
   distribution.  If you must build SystemImager yourself, here are a few
   tips:
   
       o Refer to the Makefile for details.
       o Makefile targets you are probably most interested in:
   
           all
           install_client_all
           install_server_all
           install_boel_binaries_tarball
           install_initrd
   
       o For a list of all possible Makefile targets, you can try this command:
   
           make show_targets



nimol:~/build/systemimager-3.4.1 # make WITH_SSH=1 install_server_all
openssh 
make -C /root/build/systemimager-3.4.1/doc/man
TOPDIR=/root/build/systemimager-3.4.1
make[1]: Entering directory `/root/build/systemimager-3.4.1/doc/man'
docbook2man si_addclients.sgml
make[1]: docbook2man: Command not found
make[1]: *** [si_addclients.8] Error 127
make[1]: Leaving directory `/root/build/systemimager-3.4.1/doc/man'
make: *** [manpages] Error 2


nimol:~/build/systemimager-3.4.1 # yast2 --install docbook-utils
Docbook-utils brought in a shitload of other packages

docbook-utils-0.6.14-67                       Sat Sep 10 10:59:30 2005
docbook-dsssl-stylesheets-1.79-3              Sat Sep 10 10:59:28 2005
jadetex-3.13-222                              Sat Sep 10 10:59:26 2005
te_latex-3.0-13                               Sat Sep 10 10:58:10 2005
tetex-3.0-13                                  Sat Sep 10 10:57:53 2005
latex-ucs-20040703-3                          Sat Sep 10 10:57:11 2005
perl-SGMLS-1.03ii-384                         Sat Sep 10 10:57:09 2005
gd-2.0.32-6                                   Sat Sep 10 10:57:08 2005
ghostscript-x11-8.15rc1-16                    Sat Sep 10 10:45:03 2005
ghostscript-library-8.15rc1-16                Sat Sep 10 10:45:02 2005
xaw3d-1.5E-224                                Sat Sep 10 10:44:57 2005
libgimpprint-4.2.7-28                         Sat Sep 10 10:44:56 2005
hplip-hpijs-0.8.8-10                          Sat Sep 10 10:44:54 2005
ghostscript-fonts-std-8.15rc1-16              Sat Sep 10 10:44:53 2005
openjade-1.3.2-211                            Sat Sep 10 10:31:25 2005
opensp-1.5.1-80                               Sat Sep 10 10:29:25 2005
docbook_3-3.1-598                             Sat Sep 10 10:26:38 2005
docbook_4-4.4-3                               Sat Sep 10 10:26:00 2005
xmlcharent-0.3-256                            Sat Sep 10 10:25:59 2005
iso_ent-2000.11.03-658                        Sat Sep 10 10:25:58 2005
sgml-skel-0.6-265                             Sat Sep 10 10:25:57 2005

next error it wants patch
nimol:~/build/systemimager-3.4.1 # yast2 --install patch

next gcc:
nimol:~/build/systemimager-3.4.1 # yast2 --install gcc




Nevermind!







________________________________________________________________________________
10/13/2005

Trying from scratch. Server and Client are on same subnet this time.


Installing client:

gemini:~ # mkdir ~/downloads
gemini:~ # scp -r [EMAIL PROTECTED]:~/downloads/sis-packages ~/downloads/
Password: 
systemimager-common-3.4.1-1.noarch.rpm        100%   54KB  53.6KB/s   00:00    
systemconfigurator-2.2.2-1.noarch.rpm         100%   94KB  94.0KB/s   00:00    
stable.list                                   100% 1272     1.2KB/s   00:00    
systemimager-client-3.4.1-1.noarch.rpm        100%   53KB  53.0KB/s   00:00    
install                                       100%   14KB  13.6KB/s   00:00    
perl-AppConfig-1.52-4.noarch.rpm              100%   59KB  58.6KB/s   00:00    

gemini:~ # rpm -ihv --test downloads/sis-packages/*.rpm
gemini:~ # yast2 --install mtools
gemini:~ # rpm -ihv downloads/sis-packages/*.rpm
Preparing...                ########################################### [100%]
   1:perl-AppConfig         ########################################### [ 25%]
   2:systemconfigurator     ########################################### [ 50%]
   3:systemimager-common    ########################################### [ 75%]
   4:systemimager-client    ########################################### [100%]

gemini:~ # host penny
penny.ucop.edu has address 128.48.101.222
gemini:~ # si_prepareclient --server  128.48.101.222

Continue? (y/[n]): y
Continue? (y/[n]): y

Using "sfdisk" to gather information about disk:
    /dev/sda

Starting or re-starting rsync as a daemon.....
done!

This client is ready to have its image retrieved.  You must now run 
the "si_getimage" command on your imageserver.


gemini:~ # vi /etc/sysconfig/SuSEfirewall2
gemini:~ # grep TRUSTED /etc/sysconfig/SuSEfirewall2
FW_TRUSTED_NETS="128.48.102.106,tcp,1501 128.48.101.222,tcp,873"
gemini:~ # rcSuSEfirewall2 reload




________________________________________________________________________________
getting image to server:

Horray! this worked.


penny:~ # si_getimage --golden-client gemini.ucop.edu --image 
base_install.sles9 --directory /images0

sent 481837 bytes  received 712971067 bytes  8544346.16 bytes/sec
total size is 886478082  speedup is 1.24
rsync error: some files could not be transferred (code 23) at main.c(1158)
------------- base_install.sles9 IMAGE RETRIEVAL FINISHED -------------

Press <Enter> to continue...



IP Address Assignment
---------------------

There are four ways to assign IP addresses to the client systems on an
ongoing basis:

1) DHCP
   ----------------------------------------------------------------
   A DHCP server will assign IP addresses to clients installed with
   this image.  They may be assigned a different address each time.
   If you want to use DHCP, but must ensure that your clients
   receive the same IP address each time, see "man si_mkdhcpstatic".

2) STATIC
   ----------------------------------------------------------------
   The IP address the client uses during autoinstall will be
   permanently assigned to that client.

3) REPLICANT
   ----------------------------------------------------------------
   Don't mess with the network settings in this image.  I'm using
   it as a backup and quick restore mechanism for a single machine.

Which method do you prefer? [1]: 2
You have chosen method 2 for assigning IP addresses.

Are you satisfied? ([y]/n): y
Would you like to run the "si_addclients" utility now? (y/[n]): n
penny:~ # 





Defeat!!

I can't use it.  The autoinstall script created by si_prepareclient does not
provide commands for creation of linux LVM volume groups or logical volumes.
This is a requirement for UCOP.


Reply via email to