[Spacewalk-list] Automatically Registering VM Clones as SPacewalk Clients

[Thomas Foster]

Are you using puppet?


On Thu, May 1, 2014 at 4:16 PM, Glennie, Jonathan - 0443 - MITLL <
jrglenni at ll.mit.edu> wrote:

> Hello All-
>
>
>
> My apologies if this has been covered somewhere before, but I’m trying to
> determine the best method of automating spacewalk client registration in a
> virtual environment and surprisingly enough I haven’t found much.  Right
> now, we are using VMware CentOS 6 templates as base images for client
> machines.  We have a handful of scripts set up to automate other tasks such
> as hostname/IP changes, but I’m not sure the best way to handle spacewalk
> registration.  Has anyone set this up before that may have some experiences
> to share?
>
>
>
> I don’t think we want to go down the road of using kickstart as most of
> the configuration we need is already done on the template, unless there is
> a “light” way of using it to run simple post install scripts?  And I’m
> pretty sure we can’t register the template to spacewalk otherwise we would
> have to deal with duplicate systems showing up in the inventory, or at
> least I think we would.  I’m leaning towards using a template with the
> necessary packages installed but not registered to spacewalk, with a script
> in rc.local which will check to see if the machine is registered to
> spacewalk (not sure how yet) and then run the rhnreg command if not.
> Thoughts anyone?
>
>
>
> Thanks in advance,
>
> -Jon
>
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20140501/f997e380/attachment.htm>