SF-Foundries@Linux.com:: With Linux Clusters - Image is Everything!

getimage

Here is an example of me running the getimage command to pull an image from my GoldenClient to my ImageServer:

[root@imageserver]# getimage -golden my-golden-client -image web_server_image_v1

This program will get the "web_server_image_v1" system image from "my-golden-client"
making the assumption that all filesystems considered part
of the system image are using ext2, ext3, or reiserfs.

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

See "getimage -help" for command line options.

Continue? ([y]/n): y

Retrieving /etc/systemimager/mounted_filesystems from my-golden-client to check for mounted filesystems...
------------- my-golden-client mounted_filesystems RETRIEVAL PROGRESS -------------
receiving file list ... done
/var/spool/systemimager/images/web_server_image_v1/etc/systemimager/mounted_filesystems
wrote 132 bytes  read 294 bytes  852.00 bytes/sec
total size is 180  speedup is 0.42
------------- my-golden-client mounted_filesystems RETRIEVAL FINISHED -------------


Retrieving image web_server_image_v1 from my-golden-client
------------- web_server_image_v1 IMAGE RETRIEVAL PROGRESS -------------
receiving file list ... done
./
bin/
bin/mt -> /etc/alternatives/mt
bin/pidof -> ../sbin/killall5
bin/rbash -> bash
bin/sh -> bash
boot/
boot/lost+found/
cdrom/
dev/
dev/MAKEDEV -> /sbin/MAKEDEV
dev/agpgart
dev/atibm
dev/audio
dev/audio1
dev/audio2
dev/audio3
dev/audioctl
dev/aztcd0
dev/bpcd

[ ... etc, etc, etc ... ]

var/log/
var/log/exim/
var/log/ksymoops/
var/log/news/
var/run/
var/spool/
var/spool/cron/
var/spool/cron/atjobs/
var/state/
var/state/apt/
var/state/apt/lists/
var/state/logrotate/
var/tmp/
wrote 117490 bytes  read 134577117 bytes  413808.32 bytes/sec
total size is 134072667  speedup is 1.00
------------- web_server_image_v1 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) static_dhcp -- A DHCP server will assign the
     same static address each time to clients 
     installed with this image.  Also see the
     "makedhcpstatic" command.

2) dynamic_dhcp -- A DHCP server will assign IP
     addresses dynamically to clients installed
     with this image.  They may be assigned a
     different address each time.

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

4) 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]: 3
You have chosen method 3 for assigning IP addresses.

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