[Spacewalk-list] Trying not to reinvent the wheel.....

[Paul Robert Marino]

Glen


Bernhard gave you the correct answer regardless of you using kickstarts or not.

The system creates yum repo files for each channel incase you want to
use them in a kickstart http://$c_server/ks/dist/
child/<channel-label>/<distribution-label>

For example my server has a repo called http://<my host
FQDN>/ks/dist/child/scientific-6.3-x86_64-epel/SCI-linux-6.3-x86_64
and the parent channel is this http://<my host
FQDN>/ks/dist/SCI-linux-6.3-x86_64


That said you will not be able to see any errata info via this method
so this is not an advisable method for use in production. you are best
off using copying the bootstrap script in /var/www/html/pub and
customizing it to your needs and properly registering the clients.

for example my procidure for registering pre-existing Centos 5 servers is
"
wget http://<my host FQDN>/pub/bootstrap/bootstrap-sl5.sh
chmod 700 ./bootstrap-sl5.sh
bootstrap-sl5.sh
"


It's that simple to do it right.

On Mon, Sep 22, 2014 at 5:55 AM, Waldirio Manhães Pinheiro
<waldirio at gmail.com> wrote:
> Hello friends, good morning
>
> About the first question you can create child channel and keep this uptodate
> (centos-65-x86_64-up for example), this child channel will be responsible to
> keep your servers/workstations up to date.
>
> Ps.: for sure you have best practice, dev, homolog (will test in your tests
> machine) and prod environments (production servers).
>
> Let me know if make sense or not.
>
> B'regards
> Waldirio
>
> Em 17/09/2014 16:37, "Avi Miller" <avi.miller at oracle.com> escreveu:
>
>> Hey,
>>
>> On 18 Sep 2014, at 1:14 am, Glen Collins <glenc2004 at comcast.net> wrote:
>>
>> > 1) Is there a way to download the yum updates so I can connect a newly
>> > installed rhel/centos/oracle linux system to spacewalk using the existing
>> > channels?
>>
>> If there is, I haven't found it either. :) I create a Spacewalk client
>> repository in /var/www/html/pub on the Spacewalk server (with a .repo file
>> as well) and modify the bootstrap-ol.sh script to:
>>
>> 1. Create a repo file
>> 2. Upgrade the client
>> 3. Register with Spacewalk
>> 4. Delete the repo file
>>
>> That's the only way I could find to do it. Essentially, the Spacewalk
>> client repo doesn't need to be up-to-date either, it just needs to allow
>> registration. Once the server is registered, the usual Spacewalk-driven
>> update system takes over.
>>
>> Cheers,
>> Avi
>>
>> --
>> Oracle <http://www.oracle.com>
>> Avi Miller | Product Management Director | +61 (3) 8616 3496
>> Oracle Linux and Virtualization
>> 417 St Kilda Road, Melbourne, Victoria 3004 Australia
>>
>>
>> _______________________________________________
>> Spacewalk-list mailing list
>> Spacewalk-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list