[Spacewalk-list] question about new spacewalk 0.7 setup

Michiel van Es michiele at info.nl
Thu Dec 17 09:49:04 UTC 2009


Perhaps stupid, but do you have an CentoS 5 example what I would fill in 
on the Create software channel?

Kind regards,

Michiel

-------- Original Message --------
Subject: Re: [Spacewalk-list] question about new spacewalk 0.7 setup
From: Michiel van Es <michiele at info.nl>
To: Alexandros Soumplis <soumplis at ekt.gr>
Date: 12/17/2009 10:36 AM

> Hi Alexandros,
>
> is it possible to push the whole CentOS 5 repository in 1 channel like I
> did with reposync and spacewalk?
>
> For example this is the default CentOS 5 x86_64 repo file
> (CentOS-Base.repo) :
>
> [base]
> name=CentOS-$releasever - Base
> mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
> #baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
>
> #released updates
> [updates]
> name=CentOS-$releasever - Updates
> mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates
> #baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
>
> #packages used/produced in the build but not released
> [addons]
> name=CentOS-$releasever - Addons
> mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=addons
> #baseurl=http://mirror.centos.org/centos/$releasever/addons/$basearch/
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
>
> #additional packages that may be useful
> [extras]
> name=CentOS-$releasever - Extras
> mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras
> #baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
> gpgcheck=1
> gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5
>
>
> Instead of all diffirent channels I would like to push these diffirent
> repo's in 1 channel (because it is the default on all systems/clients)
>
> Then I would make a seperate channel voor Epel and RPMforge.
>
> Kind regards,
>
> Michiel
>
> -------- Original Message --------
> Subject: Re: [Spacewalk-list] question about new spacewalk 0.7 setup
> From: Alexandros Soumplis<soumplis at ekt.gr>
> To: Michiel van Es<Michiele at info.nl>
> Date: 12/17/2009 10:24 AM
>
>> You use the spacewalk-repo-sync on your scripts (if for some reasong you
>> still prefer the good old method).
>> Else you go through the WebUI to you Channels ->  Manage Software
>> Channels ->  "Choose your channel" and
>> in there you will find a new section "Associated Yum Repository" where
>> you enter the repository url, the channel label
>> and you check the option "sync repo".
>>
>> Hope this helps.
>>
>>
>> On 17/12/2009 11:11 πμ, Michiel van Es wrote:
>>> Hi,
>>>
>>> hahah yes that was stupid from me, but it is the old server which is
>>> deprecated and not available through the internet ;)
>>> I read you can use:
>>>
>>> 'In Spacewalk 0.7 you can use new tool spacewalk-repo-sync instead of
>>> reposync + rhnpush:
>>>
>>> spacewalk-repo-sync -c centos5 --url
>>> http://isoredirect.centos.org/centos/5/os/i386/ --type=yum --label
>>> centos5
>>> '
>>>
>>> How are you doing it through taskomatic?
>>>
>>> -------- Original Message --------
>>> Subject: Re: [Spacewalk-list] question about new spacewalk 0.7 setup
>>> From: Alexandros Soumplis<soumplis at ekt.gr>
>>> To: spacewalk-list at redhat.com<spacewalk-list at redhat.com>
>>> Date: 12/17/2009 10:06 AM
>>>
>>>> Hello!
>>>>
>>>> AFAIK at least from version 0.6 you do not have to run a seperate
>>>> reposync script. You can synchronize your repos through the WebUI by
>>>> scheduling a taskomatic task.
>>>>
>>>> Alexandros
>>>>
>>>> P.S Maybe you should change you rhnpush password as you've exposed it to
>>>> the Internet :-)
>>>>
>>>>
>>>> On 17/12/2009 10:52 πμ, Michiel van Es wrote:
>>>>> ANYONE? ;)
>>>>>
>>>>> Kind regards,
>>>>>
>>>>> Michiel
>>>>>
>>>>> -------- Original Message --------
>>>>> Subject: [Spacewalk-list] question about new spacewalk 0.7 setup
>>>>> From: Michiel van Es<michiele at info.nl>
>>>>> To: spacewalk-list at redhat.com<spacewalk-list at redhat.com>
>>>>> Date: 12/16/2009 01:42 PM
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> We installed a new spacewalk 0.7 server.
>>>>>> We want to move from an old 0.3 upgraded to 0.6 spacewalk server to
>>>>>> this
>>>>>> new 0.7 server.
>>>>>>
>>>>>> I want to review my reposync script to pull the yum packages and the
>>>>>> rhnpush scripts I use.
>>>>>>
>>>>>> For reposync I use:
>>>>>>
>>>>>> ### Updates for Centos 4
>>>>>> echo "Starting a reposync for CentOS4_updates at `date`">>
>>>>>> $REPOSYNCLOG
>>>>>> echo "">>  $REPOSYNCLOG
>>>>>> reposync -c /etc/yum.repos.d/reposync_repo/CentOS4.repo -n -p
>>>>>> $REPODIR/CentOS4 --repoid=CentOS4-updates
>>>>>>
>>>>>> echo "Starting a reposync for CentOS4_centosplus at `date`">>
>>>>>> $REPOSYNCLOG
>>>>>> echo "">>  $REPOSYNCLOG
>>>>>> reposync -c /etc/yum.repos.d/reposync_repo/CentOS4.repo -n -p
>>>>>> $REPODIR/CentOS4 --repoid=CentOS4-centosplus
>>>>>>
>>>>>> echo "Starting a reposync for CentOS4_base at `date`">>  $REPOSYNCLOG
>>>>>> echo "">>  $REPOSYNCLOG
>>>>>> reposync -c /etc/yum.repos.d/reposync_repo/CentOS4.repo -n -p
>>>>>> $REPODIR/CentOS4 --repoid=CentOS4-base
>>>>>>
>>>>>> echo "Starting a reposync for CentOS4_centosplus at `date`">>
>>>>>> $REPOSYNCLOG
>>>>>> echo "">>  $REPOSYNCLOG
>>>>>> reposync -c /etc/yum.repos.d/reposync_repo/CentOS4.repo -n -p
>>>>>> $REPODIR/CentOS4 --repoid=CentOS4-extras
>>>>>>
>>>>>> echo "Starting a reposync for epel CentOS 4 at `date`">>  $REPOSYNCLOG
>>>>>> echo "">>  $REPOSYNCLOG
>>>>>> reposync -c /etc/yum.repos.d/reposync_repo/epel4.repo -n -p
>>>>>> $REPODIR/EPEL4REPO --repoid=epel4
>>>>>>
>>>>>> ########## CentOS 5
>>>>>>
>>>>>> echo "Starting a reposync for CentOS5 base at `date`">>  $REPOSYNCLOG
>>>>>> echo "">>  $REPOSYNCLOG
>>>>>> reposync -n -p $REPODIR/CentOS5 --repoid=base
>>>>>>
>>>>>> echo "Starting a reposync for CentOS5 addons at `date`">>  $REPOSYNCLOG
>>>>>> echo "">>  $REPOSYNCLOG
>>>>>> reposync -n -p $REPODIR/CentOS5 --repoid=addons
>>>>>>
>>>>>> echo "Starting a reposync for CentOS5 extras at `date`">>  $REPOSYNCLOG
>>>>>> echo "">>  $REPOSYNCLOG
>>>>>> reposync -n -p $REPODIR/CentOS5 --repoid=extras
>>>>>>
>>>>>> echo "Starting a reposync for CentOS5 updates at `date`">>
>>>>>> $REPOSYNCLOG
>>>>>> echo "">>  $REPOSYNCLOG
>>>>>> reposync -n -p $REPODIR/CentOS5 --repoid=updates
>>>>>> #
>>>>>> ### extra 32 bit repo's
>>>>>> #
>>>>>> echo "Starting a reposync for RPMForge CentOS 5 at `date`">>
>>>>>> $REPOSYNCLOG
>>>>>> echo "">>  $REPOSYNCLOG
>>>>>> reposync -c /etc/yum.repos.d/reposync_repo/rpmforge5.repo -n -p
>>>>>> $REPODIR/RPMFORGE5 --repoid=rpmforge5
>>>>>>
>>>>>> echo "Starting the rhnpush now">>  $REPOSYNCLOG
>>>>>> /root/scripts/rhnpush.sh
>>>>>>
>>>>>>
>>>>>>
>>>>>> For rhnpush I use:
>>>>>>
>>>>>> ####################################
>>>>>> RHNPUSHLOG="/var/log/rhnpush.log"
>>>>>> REPODIR="/repodata/repositories"
>>>>>>
>>>>>> ### Updates for Centos 5
>>>>>> echo "Starting a reposync for CentOS5_base at `date`">>  $RHNPUSHLOG
>>>>>> echo "">>  $RHNPUSHLOG
>>>>>> rhnpush --force --tolerant --username=upadmin --password=upload007
>>>>>> --channel=centos5 --server=http://localhost/APP
>>>>>> --dir=$REPODIR/CentOS5/base/CentOS/
>>>>>>
>>>>>> echo "Starting a reposync for CentOS5_addons at `date`">>  $RHNPUSHLOG
>>>>>> echo "">>  $RHNPUSHLOG
>>>>>> rhnpush --force --tolerant --username=upadmin --password=upload007
>>>>>> --channel=centos5 --server=http://localhost/APP
>>>>>> --dir=$REPODIR/CentOS5/addons/CentOS/
>>>>>>
>>>>>> echo "Starting a reposync for CentOS5_extras at `date`">>  $RHNPUSHLOG
>>>>>> echo "">>  $RHNPUSHLOG
>>>>>> rhnpush --force --tolerant --username=upadmin --password=upload007
>>>>>> --channel=centos5 --server=http://localhost/APP
>>>>>> --dir=$REPODIR/CentOS5/extras/RPMS/
>>>>>>
>>>>>> echo "Starting a reposync for CentOS5_updates at `date`">>  $RHNPUSHLOG
>>>>>> echo "">>  $RHNPUSHLOG
>>>>>> rhnpush --force --tolerant --username=upadmin --password=upload007
>>>>>> --channel=centos5 --server=http://localhost/APP
>>>>>> --dir=$REPODIR/CentOS5/updates/RPMS/
>>>>>>
>>>>>> echo "Starting a reposync for RPMFORGE5 at `date`">>  $RHNPUSHLOG
>>>>>> echo "">>  $RHNPUSHLOG
>>>>>> rhnpush --force --tolerant --username=upadmin --password=upload007
>>>>>> --channel=rpmforge5 --server=http://localhost/APP
>>>>>> --dir=$REPODIR/RPMFORGE5/rpmforge5/RPMS/
>>>>>>
>>>>>> echo "Starting a reposync for RPMFORGE4 at `date`">>  $RHNPUSHLOG
>>>>>> echo "">>  $RHNPUSHLOG
>>>>>> rhnpush --force --tolerant --username=upadmin --password=upload007
>>>>>> --channel=rpmforge4 --server=http://localhost/APP
>>>>>> --dir=$REPODIR/RPMFORGE4/rpmforge4/RPMS/
>>>>>>
>>>>>> echo "Starting a reposync for EPEL FOR CENTOS5 at `date`">>
>>>>>> $RHNPUSHLOG
>>>>>> echo "">>  $RHNPUSHLOG
>>>>>> rhnpush --force --tolerant --username=upadmin --password=upload007
>>>>>> --channel=epelrepo --server=http://localhost/APP
>>>>>> --dir=$REPODIR/EPELREPO/epel/
>>>>>>
>>>>>>
>>>>>> Are these the correct methods to pull the yum repo's and push them
>>>>>> (with
>>>>>> force!) in the Spacewalk server?
>>>>>>
>>>>>> I would like to share your thought on my scripts and methods..:)
>>>>>>
>>>>>> Kind regards,
>>>>>>
>>>>>> Michiel
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>>> --
>>>> Soumplis Alexandros
>>>> Systems Engineer
>>>> National Documentation Center /N.H.R.F.
>>>> Information Systems Department
>>>> 48, Vas. Constantinou Av.
>>>> 116 35 Athens, Greece
>>>> phone:+30 210 7273984  fax:+30 210 7252223
>>>> email:soumplis at ekt.gr
>>>> http://www.ekt.gr
>>>>
>>>>
>>>> --------------------------------------------------------------------
>>>> This email is digitally signed by EKT in order to ensure its
>>>> integrity and authenticity. EKT participates in the HARICA Public
>>>> Key Infrastructure, the Certification Authority of GRNET. You can
>>>> install the HARICA root certificate athttp://www.harica.gr/trust.php
>>>> ---------------------------------------------------------------------
>>>>
>>
>> --
>> Soumplis Alexandros
>> Systems Engineer
>> National Documentation Center /N.H.R.F.
>> Information Systems Department
>> 48, Vas. Constantinou Av.
>> 116 35 Athens, Greece
>> phone: +30 210 7273984  fax: +30 210 7252223
>> email:soumplis at ekt.gr
>> http://www.ekt.gr
>>
>>
>> --------------------------------------------------------------------
>> This email is digitally signed by EKT in order to ensure its
>> integrity and authenticity. EKT participates in the HARICA Public
>> Key Infrastructure, the Certification Authority of GRNET. You can
>> install the HARICA root certificate athttp://www.harica.gr/trust.php
>> ---------------------------------------------------------------------
>>
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list




More information about the Spacewalk-list mailing list