The bootstrap script installs some basic packages so the client is able to login to spacewalk. For SLES there is an "installation repo" under "/var/www/html/pub/repositories" that is used to install these packages.
Am 16.06.2015 10:42 nachm. schrieb Jason Calafiore <[email protected]>: > > Hi All, > > I still find we have not reached a solution to register a large group of > existing servers to Spacewalk easily. I would think there must be some easier > method than creating the yum repo, installing the packages and use the > bootstrap scripts. > > > I noticed if i just run the bootstrap.sh without installing the packages it > shows up in Spacewalk. I was wondering is it possible to use the bootstrap > script and then push out the required yum packages through spacewalk? Or has > someone found an easier way to register existing offline clients? > > > Thank you, > > Jason > > > > > From: [email protected] > [mailto:[email protected]] On Behalf Of Kalchik, Jeffery > Sent: Friday, June 12, 2015 9:42 AM > To: [email protected] > Subject: [External] Re: [Spacewalk-list] Registering Offline servers to > Spacewalk > > > > 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: [email protected] > [mailto:[email protected]] On Behalf Of Jason Calafiore > Sent: Thursday, June 11, 2015 7:55 AM > To: [email protected] > 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: [email protected] > > Reply To: [email protected] > > 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 > > > > > > > > rhnreg_ks --serverUrl=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. _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
