Automation across physical servers / VMWare

Mertens, Bram mertensb at mazdaeur.com
Thu Dec 8 07:18:03 UTC 2011


>


Mazda Motor Logistics Europe NV, Blaasveldstraat 162, B-2830 Willebroek
VAT BE 0406.024.281, RPR Mechelen, ING  310-0092504-52, IBAN : BE64 3100 0925 0452, SWIFT : BBRUBEBB

-----Original Message-----
> From: redhat-list-bounces at redhat.com [mailto:redhat-list-
> bounces at redhat.com] On Behalf Of Chaim Rieger
> Sent: woensdag 7 december 2011 19:22
> To: General Red Hat Linux discussion list
> Subject: Re: Automation across physical servers / VMWare
>
> On 12/7/2011 10:02 AM, Daniel Tate wrote:
> > We have the need to roll out many servers in a short amount of time,
> > each with about 8 additional, server specific tools on it.   What
> > would be the simplest way to do this?  Kickstart would be OK, but if
> > there's something a LITTLE faster but not so complicated it would take
> > a week to learn, that would be preferable.  We're going to have 4
> > configs - RHEL5 32 and 64 bit (Vendor Reqs)
> >
> I do not think that vmware is the correct tool for this
>
> you can setup a template driven image library and then deploy them based
> on preconditions. but not using vmware,
>
> with vmware you can clone your golden image, but thats about it.

We've recently started using VMWare's LabManager and this allows the creation of templates with a customization script that's run automatically after the template is deployed.

In our test environment I use the post install script to register the machines automatically to our satellite.

Another approach would be similar to what mark suggested: build a minimal server with kickstart but then install whatever else is needed through different channels, custom built RPM packages with deps to whatever you need installed etc.

Or - but unless you have something set up already this won't fit your time requirements - use a tool like cfengine.

Regards

Bram




More information about the redhat-list mailing list