Simon,

sorry for the late, I've been very busy in this week.... comments below...

Simon Ruiz wrote:
> 
> After finding out how old the official Ubuntu repository's package of
> systemimager is, I added the systemimager.org repository and
> installed those packages (they installed just fine, though I did have
> to disable to repository afterwards cause it tried to update some
> other things on my system) though systemconfigurator did not come
> have a newer version on that repository. I'm now running 3.6.2-2 on
> the server and the client.

3.6.2 is quite old... I would suggest to use 3.7.5, but maybe I already
said that...

> 
> RE: STATIC vs. DYNAMIC IPs
> 
> So, the way I understand it (which is admittedly not much), having
> Static IPs would allow the systemimager client to look up its
> hostname and autoinstall script from the server's /etc/hosts when
> doing an autoinstall, something that can't happen if we're using
> Dynamic IPs. Is there another way for the client to get this
> information? Am I completely missing the point, here?

Static IPs = the DHCP always assign the same addresses to the same
clients (there's a matching IP <=> mac address in dhcpd.conf).

Dynamic IPs = a pool of IPs is available for the clients. Each client
gets a random IP from the pool (not totally random... in general when a
client gets an IP it keeps it until the lease time elapses, so in
general after N reboots maybe some clients will have not their original
IP). This configuration is usually used in a lab of workstation, an
office, or in all the cases that you don't care about the binding of the
IPs and the real machines.

> 
> The main problem I have is that the documentation (and indeed the
> program itself) assumes that the implementer has complete control
> over the network and talks about everything from that point of view.
> My situation is a little unique in that I don't have control over the
> DHCP server, and I'm trying to figure out how that affects the way I
> should be reading the documentation.
> 
> RE: LOCAL.CFG and (DHCP Server == SystemImager Server) ASSUMPTION
> 
> So, we figured out (because it said so clearly on some error screen)
> that the main reason autoinstall hasn't worked for me yet is because
> the client doesn't know where the server is. It cannot access the
> local hard disk to read /local.cfg, so it assumes the DHCP server is
> the SystemImager server which is wrong.

If you have no control over the DHCP server you could try to use it only
to get a random IP to be able to reach the real image server. To do so
simply add all the image server informations in the kernel boot
parameters, I mean use si_mkautoinstallcd with --append "STRING" and add
in STRING the following options:

IMAGESERVER=<your_real_image_server>
IMAGENAME=<your_imagename>
LOG_SERVER=<your_log_server> if you want to use a syslogd server...
etc... (see http://wiki.systemimager.org/index.php/Installation_Parameters)

If you don't want to use the same IP of the installation for the
production, simply write a post-install script
(/var/lib/systemimager/scripts/post-install/README) to correctly setup
the network in the clients.


> 
> RE: SI_MKAUTOINSTALLDISKETTE
> 

si_mkautoinstalldiskette is no more supported, today it's very difficult
to put a kernel+initrd.img in 1.44MB... in the trunk I've added a new
command si_mkautoinstalldisk that can be used to create an autoinstall
usb pen. It will be avail in 3.7.6. For now use si_mkautoinstallcd, with
the parameters above.

For the machines that don't have a cd try to use si_mkautoinstalldisk
downolading it from the trunk http://svn.systemimager.org/, it's a
simple perl script...

Regards,
-Andrea

-------------------------------------------------------------------------
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.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to