Automated Imaging Process Options



Hello all, looking for some ideas and feedback from the pool of
sysadmins out there. :)

We have a scenario where developers are making use of blade centers on
which they want to run multiple operating systems on their blades and
switch out these OS'es as-needed (and fairly often).

Currently they are able to use a solution like Symantec's Ghost Console
where they log into a central Ghost server and can tell a connected
client (one of the blades) to re-image itself with whichever flavor of
Windows they desire. The machine auto-reboots and re-ghosts itself and
does some post-install configuration too.

This is great as it lets the developers do this themselves and is
basically hands-off for us.

However, there is no Ghost Client for Linux and so as the developers
start throwing RHEL and SLES into the mix, the Ghost Console no longer
is a viable solution.

Another admin here came up with a script and batch file solution that
essentially modifies the boot.ini and grub files when a script is run
telling it to re-ghost itself on reboot. Images are stored locally on
a hidden partition. This works well enough but requires significant
lead-up setup time and obviously the developers have to run a script or
batch file instead of a nice GUI (which is acceptable I guess).

I'm wondering if there are better solutions out there and/or how some
of you are dealign with this type of scenario.

SystemImager would be great, except that it doesn't appear to support
Windows...

We've also considered clustering the balde centers and running many
vmware guests (or Xen perhaps?) making it easy to just start and stop
whichever guest the developer needed.

I'm goign to bug Symantec about creating a Linux client for their
console product, but don't have any hope that this will be completed
soon.

Any sort of ideas would be appreciated. I'd rather not recreate work
if necessary and would be more than happy to contribute to an existing
project that might come close to meeting our needs.

TIA as always
Ray

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



Relevant Pages

  • Re: Remote debugging
    ... this scenario hardly ever works. ... Even if you get to the stage where everyone can debug on the server, only one person can debug at a time, and the system slows to an absolute crawl making it impossible for other developers to work. ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Longtime VMS system manager/programmer available
    ... doing end user software. ... for this kind of scenario. ... play with computers in my spare time. ... guess the majority of developers of serious opensource projects have IT ...
    (comp.os.vms)
  • RE: VSS/InterDev Integration Problems - Please Help!
    ... too many times in the past - having our developers admin rights to our dev box: ... Our scenario: Our anonymous user id in IIS is a network account ... Somebody replace it with a user id of a developer instead of a generic user account just for anonymous logon ...
    (microsoft.public.vstudio.sourcesafe)