* Stroehmann, James ([EMAIL PROTECTED]) [030903 09:14]: > > I guess I just wanted to make sure that I wasn't missing something, > > and it sounds as if I'm not -- it's not designed to work out of the > > box in this type of environment.
> Just a quick note, at my workplace we have had some conflict integrating > system imager into our environment as (clearly indicated in the doc) system > imager was designed as a cluster image server (i.e. 1 sis server for every > rack or group of racks). This is not system imagers fault, it is just > something that my company is not that familiar with. They see the system > imager server as a central point of contact for all of our linux systems > (500+), similar to a dns or mail server. Not sure exactly what my point is, > just wanted to point this out :) I agree, and have the same philosophy of "one" image server for the enterprise, but it's obviously not easy to accomplish. I'd like to add that I've found a work-around solution for my specific situation, using SSH port forwarding. Image server: 10.0.0.1 DMZ golden client: 192.168.1.2 DMZ machine to clone: 192.168.1.3 Problem: Image server can't get the golden client image because firewall rules don't allow rsync. Solution: From the image server, SSH to the golden client, and port forward the rsync port on the golden client, back to the image server: [EMAIL PROTECTED] ssh -L 873:localhost:873 192.168.1.2 Start another SSH session on the image server. Run getimage, but use "localhost", since it's really getting forwarded to the 192.168.1.2 golden client: [EMAIL PROTECTED] getimage -golden-client localhost -image <imagename> Problem: DMZ machine to be cloned can't pull image from image server (rsync), due to more firewall rules. Solution: From the image server, SSH to the golden client, and port forward the rsync port, so the machine to be cloned will be able to talk to the image server: [EMAIL PROTECTED] ssh -R 873:localhost:873 192.168.1.2 Once the new machine boots up, he will be able to rsync to 192.168.1.2:873, which will just be port fowarded through a SSH tunnell to 10.0.01:873. Hope that wasn't too confusing, but it does work pretty well. -J ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
