<div dir="ltr">Are you using puppet?</div><div class="gmail_extra"> <div class="gmail_quote">On Thu, May 1, 2014 at 4:16 PM, Glennie, Jonathan - 0443 - MITLL <<a href="mailto:jrglenni@ll.mit.edu" target="_blank">jrglenni@ll.mit.edu</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div>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 </div></div> _______________________________________________ Spacewalk-list mailing list <a href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a> </blockquote></div> </div>