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

Glennie, Jonathan - 0443 - MITLL jrglenni at ll.mit.edu
Thu May 1 20:37:35 UTC 2014


Cool, that’s one of the possibilities I was thinking about.  Glad to know it will work, thanks for confirming!  

 

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Thomas Foster
Sent: Thursday, May 01, 2014 4:29 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Automatically Registering VM Clones as SPacewalk Clients

 

If you are not using puppet, then the way we have it is setup activationkeys that have all of the channels that I want my systems to have when they bootup.  You can then run the rhnreg_ks command to register your server using a rc.local script that removes itself after running the registration..then send the output of the command to yourself for testing.  The activationkeys are pretty smooth.

 

On Thu, May 1, 2014 at 4:24 PM, Thomas Foster <thomas.foster80 at gmail.com> wrote:

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/7cffab91/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5410 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20140501/7cffab91/attachment.p7s>


More information about the Spacewalk-list mailing list