[Spacewalk-list] Registering Offline servers to Spacewalk

Mon Jun 15 17:19:31 UTC 2015

sorry for the delayed response
the reason i mentioned a kickstart script is if you create one that
includes the spacewalk client and EPEL repos you will see in the beginning
of the kickstart script the lines where the URL's for those channels that
anaconda is using, and they are essentially yum repos. you can use those
URLs with the yum command to install the spacewalk client
I usually create a set of disabled repos for them under /etc/yum.repos.d
with no gpg check and enable them via the yum command during the install.

On Mon, Jun 15, 2015 at 11:58 AM, Kalchik, Jeffery <JDKalchik at landolakes.com
> wrote:

>  Good morning.
>
>
>
> It’s been a few years since I registered servers that were not originally
> built within Spacewalk (or Satellite.)  I’d suspect that the rpm & yum
> commands you list in #1 are at least a good start.
>
>
>
> For the bootstrap script, see Admin/Spacewalk Configuration/Bootstrap
> Script in the web console.  It’ll end up named bootstrap.sh or some such.
> client_config_update.py is part of the bootstrap tools.
>
>
>
> Jeff Kalchik
>
> Systems Engineering
>
> Land O’Lakes
>
>
>
> *From:* spacewalk-list-bounces at redhat.com [mailto:
> spacewalk-list-bounces at redhat.com] *On Behalf Of *Jason Calafiore
> *Sent:* Friday, June 12, 2015 10:34 AM
>
> *To:* spacewalk-list at redhat.com
> *Subject:* Re: [Spacewalk-list] Registering Offline servers to Spacewalk
>
>
>
> Hi Jeff,
>
>  Thanks for the help. I just wanted to clarify a few things
>
>
>
> 1. When you say install "Spacewalk client tools & Libraries first", does
> that mean the following steps?
>
>
>
> rpm -Uvh
> http://yum.spacewalkproject.org/2.3-client/RHEL/7/x86_64/spacewalk-client-repo-2.3-2.el7.noarch.rpm
>
>
>
> rpm -Uvh
> http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
>
>
>
> yum install rhn-client-tools rhn-check rhn-setup rhnsd m2crypto
> yum-rhn-plugin
>
>
>
> 2.  I did find the bootstrap script
> /var/www/html/pub/bootstrap/client_config_update.py is this it? If so this
> is run after the steps above?
>
>
>
> 3. This method still seems to involve creating a local yum repo on the
> spacewalk server to serve out the packages for offline servers. As a result
> I'll need to still login to a machine and create a .repo file on the remote
> server that needs to be registered. Isn't there any way to automate
> registration of servers with a script? It surprising spacewalk doesn't have
> an easier way to handle this.
>
>
>
> 4. Once I register the remote servers, will i be able to update the
> spacewalk client packages provided they are subscribed to the spacewalk
> channel?
>
>
>
>
>
> Thank you,
>
> Jason
>
>
>
>
>
>
> ________________________________________________________________________________________________________
>
> Good morning, Jason, et al.
>
>
>
> To register an existing server, you’ll need to install the Spacewalk
> client tools & libraries first.  That’ll extend the capabilities of yum (or
> the appropriate update manager,) to communicate with a Spacewalk service.
> Once that’s done, you’ll need to run /usr/sbin/rhn_register,
> /usr/sbin/rhnreg_ks or the bootstrap script (bootstrap runs rhnreg_ks
> internally.)
>
>
>
> The registration script normally gets generated into
> /var/www/html/pub/bootstrap.
>
>
>
> The bootstrap script does perform some other activities, such as a full
> system update (through yum, zypper, etc.,) downloading SSL certs, and so
> forth.  You might want to run it, you also might want to manually register
> your clients, depending on your local requirements.
>
>
>
> Jeff Kalchik
>
> Systems Engineering
>
> Land O’Lakes
>
>
>
> *From:* spacewalk-list-bounces at redhat.com [
> mailto:spacewalk-list-bounces at redhat.com
> <spacewalk-list-bounces at redhat.com>] *On Behalf Of *Jason Calafiore
> *Sent:* Thursday, June 11, 2015 7:55 AM
> *To:* spacewalk-list at redhat.com
> *Subject:* Re: [Spacewalk-list] Registering Offline servers to Spacewalk
>
>
>
> Hi Marino,
>
>  I have add the spacewalk repo as a child for my base channels, but I am
> dealing with the initial implementation of spacewalk in
> my existing environment, so I don't understand how kickstart would be
> applicable.
>
>
>
> Can you explain a little more about the registration script? Where is it
> exactly and how could i modify it as you are suggesting to register
> existing servers?
>
>
> Thank you,
>
> Jason
>
>
>
> _______________________________________________________________
>
> I always include the spacewalk clients in a child repo of my base channels
> then include it in my kickstarts. Then I can view the kickstart and pick
> out the URI‎ yum has an option to install using an adhock yumrepo. Also you
> may not be aware of this but spacewalk generates a boilerplate registration
> script for you in the public directory for apache you can use as a template
> to modify into your own custom registration script.
>
> Additionally yum and the rpm command can install packages over a network
> by specifying the URI as the package name.
>
>
>
> *From: *Jason Calafiore
>
> *Sent: *Wednesday, June 10, 2015 17:51
>
> *To: *spacewalk-list at redhat.com
>
> *Reply To: *spacewalk-list at redhat.com
>
> *Subject: *[Spacewalk-list] Registering Offline servers to Spacewalk
>
>
>
> Hi All,
>
>  I am trying to figure out a an easy to register servers that are already
> created and offline without have to reach out to the internet to get the
> necessary packages.
>
>
>
> The only way I could do this was to do the following below by creating a
> yum repo with the necessary packages and then on a client server configure
> a .repo file that get the necessary packages.
>
>
>
> Is there any easier way to do this? I would think spacewalk would have an
> easy way to register clients especially offline servers. I had asked this
> before and someone suggested a scripts on github, but couldn't figure it
> out.
>
>
>
> Thanks,
>
> Jason
>
>
>
> Create Local Repo on the spacewalk Server
>
>
>
> mkdir /var/www/html/pub/spacewalk-client
>
>
>
> cd /var/www/html/pub/spacewalk-client
>
>
>
> repotrack -a x86_64 -p /var/www/html/pub/spacewalk-client rhn-client-tools
> rhn-check rhn-setup rhnsd m2crypto yum-rhn-plugin
>
>
>
> rm *i686* -f
>
>
>
> wget
> http://yum.spacewalkproject.org/2.3-client/RHEL/7/x86_64/spacewalk-client-repo-2.3-2.el7.noarch.rpm
>
> wget http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
>
>
>
> creapterepo /var/www/html/pub/spacewalk-client
>
>
>
>
>
> Register Server to Spacewalk
>
>
>
> vi/etc/yum.repos.d/spacewalk-local.repo
>
>
>
> [spacewalk-local-install-repo]
>
> name=Spacewalk Client Install
>
> baseurl=http://spacewalk-server.com/pub/spacewalk-client
>
> gpgcheck=0
>
> gpgkey=
>
> enabled=1
>
>
>
> Disable other repos in /yum.repos.d
>
>
>
> yum install rhn-client-tools rhn-check rhn-setup rhnsd m2crypto
> yum-rhn-plugin
>
>
>
> # rpm -Uvh
> http://spacewalk-server.com/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm
> <http://ghslspacewalk.ds.src.bah.com/pub/rhn-org-trusted-ssl-cert-1.0-1.noarch.rpm>
>
>
>
>
>
>
>
>   rhnreg_ks --serverUrl=https://spacewalk-server.com/XMLRPC
> --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
> --activationkey=1-centos-server-7
> <https://spacewalk-server.com/XMLRPC--sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT--activationkey=1-centos-server-7>
>
>
>
> This message may contain confidential material from Land O'Lakes, Inc. (or
> its subsidiary) for the sole use of the intended recipient(s) and may not
> be reviewed, disclosed, copied, distributed or used by anyone other than
> the intended recipient(s). If you are not the intended recipient, please
> contact the sender by reply email and delete all copies of this message.
>   This message may contain confidential material from Land O'Lakes, Inc.
> (or its subsidiary) for the sole use of the intended recipient(s) and may
> not be reviewed, disclosed, copied, distributed or used by anyone other
> than the intended recipient(s). If you are not the intended recipient,
> please contact the sender by reply email and delete all copies of this
> message.
>
> _______________________________________________
> 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/20150615/33fe3879/attachment.htm>