[Spacewalk-list] How can my CentOS 6.5 be up to date?

Thu Nov 6 19:41:08 UTC 2014

Enjoy!

;-)

______________
Atenciosamente
Waldirio
msn: waldirio at gmail.com
Skype: waldirio
Site: www.waldirio.com.br
Blog: blog.waldirio.com.br
LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646
PGP: www.waldirio.com.br/public.html

On Thu, Nov 6, 2014 at 5:33 PM, Daryl Rose <rosede12 at gmail.com> wrote:

> Waldirio,
>
> I believe that is how I now have this setup.
>
> I have a CentOS 6.5 Channel setup and under it, I have two repositories
> setup, 6.5 Base and 6.5 update.
>
> Now that I have the update repository setup, the client that I'm setting
> up now show's that there are 128 packages that need to be updated.
>
> Thank you Waldirio and everyone else who responded for helping me get this
> setup correctly.
>
> Daryl
>
>
>
> On Thu, Nov 6, 2014 at 12:29 PM, Waldirio Manhães Pinheiro <
> waldirio at gmail.com> wrote:
>
>> Daryl
>>
>> You can do like this
>>
>> ####
>> Repo
>> repo: repo_centos6.5
>> url: http://mirror.globo.com/centos/6.5/os/x86_64/
>>
>> Channel
>> base channel: centos6.5_x86-64_base
>> ####
>>
>> After this you will create a child channel
>>
>> ####
>> Repo
>> repo: repo_centos6.5_update
>> url: http://mirror.globo.com/centos/6.5/updates/x86_64/
>>
>> Channel
>> base channel: centos6.5_x86-64_base
>> child channel label: centos6.5_x86-64_update
>> ####
>>
>> So you will create your environment like example above to all channels
>> you want in your server, but the best practice is, to your clients, you
>> need a controlled environment, so you will clone your base channels to
>> freezed channels, for example, to your development channels, you can create
>> like bellow
>>
>> dev_centos6.5_x86-64
>>   |-- dev_centos6.5_x86-64_update
>>   | ....
>>   | -- dev_epel_6_x86-64
>>   | -- dev_vmware_6_x86-64
>>
>> remember, base channel will receive update all days (if you define this
>> update frequency, in your freezed channel, you will define when will be
>> updated, sure after some tests like, your application will run normally
>> after update gcc or kernel, anyway, you have to test before apply in your
>> production environment.
>>
>> More 0,50 cents, you may create base channels like:
>>
>> prod_<base channel name>                 # Production environment
>> homolog_<base channel name>           # Homolog environment
>> dev_<base channel name>                  # Development environment
>>
>> Let me know if was clear the explanation.
>>
>> Take Care
>>
>>
>> ______________
>> Atenciosamente
>> Waldirio
>> msn: waldirio at gmail.com
>> Skype: waldirio
>> Site: www.waldirio.com.br
>> Blog: blog.waldirio.com.br
>> LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646
>> PGP: www.waldirio.com.br/public.html
>>
>> On Thu, Nov 6, 2014 at 3:15 PM, Daryl Rose <rosede12 at gmail.com> wrote:
>>
>>> Waldirio,
>>>
>>> Thank you for the information, but I'm still a bit confused on how to
>>> configure the channel and repositories.
>>>
>>> If I read your post correctly, I should create a CentOS 6.5 channel with
>>> a CentOS 6.5
>>> Base repository with a 6.5 update child repository?  Is that correct?
>>>
>>> Thank you.
>>>
>>> Daryl
>>>
>>>
>>> On Thu, Nov 6, 2014 at 10:49 AM, Waldirio Manhães Pinheiro <
>>> waldirio at gmail.com> wrote:
>>>
>>>> Daryl
>>>>
>>>> I sent a email to list last month about it (
>>>> https://www.redhat.com/archives/spacewalk-list/2014-October/msg00222.html),
>>>> take a look, the idea is the same.
>>>>
>>>> Tell me if is ok to you, about understanding, case not, I can create a
>>>> post about it in my blog.
>>>>
>>>> B'Regards
>>>>
>>>> ______________
>>>> Atenciosamente
>>>> Waldirio
>>>> msn: waldirio at gmail.com
>>>> Skype: waldirio
>>>> Site: www.waldirio.com.br
>>>> Blog: blog.waldirio.com.br
>>>> LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646
>>>> PGP: www.waldirio.com.br/public.html
>>>>
>>>> On Thu, Nov 6, 2014 at 2:16 PM, Daryl Rose <rosede12 at gmail.com> wrote:
>>>>
>>>>> Amedeo,
>>>>>
>>>>> For the 6.5 base I used the URL path:
>>>>>
>>>>> http://mirror.centos.org/centos-6/6.5/os/x86_64/
>>>>>
>>>>> I am in the process of adding an update channel, and I am using URL:
>>>>>
>>>>> http://mirror.centos.org/centos-6/6.5/updates/x86_64/
>>>>>
>>>>> Are these not correct?  Should I use only
>>>>> http://mirror.centos.org/centos/6?
>>>>>
>>>>> The documentation leaves a lot to be desired and doesn't provide an
>>>>> example of setting up the repository channel.  I found a YouTube video of a
>>>>> guy setting up a Spacewalk channel and repository.  He used the first URL
>>>>> that I posted.  Is using http://mirror.centos.org/centos/6  a better
>>>>> method?
>>>>>
>>>>> Any and all suggestions made are greatly appreciated.
>>>>>
>>>>> Thank you.
>>>>>
>>>>> Daryl
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Nov 6, 2014 at 9:59 AM, Amedeo Salvati <amedeo at oscert.net>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> @daryl
>>>>>> did you use relative path for specifically centos 6.5 like:
>>>>>>
>>>>>> /mirrors/CentOS/6.5
>>>>>>
>>>>>> or you use generic 6 version? like:
>>>>>>
>>>>>> /mirrors/CentOS/6
>>>>>>
>>>>>> both for base and updates, because centos repos when release new
>>>>>> minor release will empty updates directory on the last one
>>>>>>
>>>>>> best regards
>>>>>> a
>>>>>>
>>>>>> Da: spacewalk-list-bounces at redhat.com
>>>>>> A: spacewalk-list at redhat.com
>>>>>> Cc:
>>>>>> Data: Thu, 6 Nov 2014 16:44:25 +0100
>>>>>> Oggetto: Re: [Spacewalk-list] How can my CentOS 6.5 be up to date?
>>>>>>
>>>>>> > Daryl Rose wrote:
>>>>>> > % I just recently installed Spacewalk on a CentOS 6.6 server. I
>>>>>> created a
>>>>>> > % 6.5 channel and repository and I just stood up a CentOS 6.5
>>>>>> client server
>>>>>> > % and registered it on to the Spacewalk server.
>>>>>> > %
>>>>>> > % When I initially stood up the 6.5 client, I looked to see how
>>>>>> many how many
>>>>>> > % updated packages it needed by doing a "yum update". It needed 264
>>>>>> > % packages, however, I DID NOT perform the update. Just looking. I
>>>>>> then
>>>>>> > % registered the 6.5 client with the Spacewalk server and checked
>>>>>> to see if
>>>>>> > % it was up to date or not. Spacewalk is telling me that the client
>>>>>> is
>>>>>> > % up-to-date. This is not accurate, why?
>>>>>> >
>>>>>> > So you have CentOS 6.5 client registered to CentOS 6.5 channel in
>>>>>> Spacewalk.
>>>>>> > And Spacewalk UI says it's up-to-date. Why do you think it isn't
>>>>>> accurate?
>>>>>> >
>>>>>> > If you don't have 6.6 packages in Spacewalk then it can hardly know
>>>>>> about updates.
>>>>>> >
>>>>>> > % Thanks.
>>>>>> > %
>>>>>> > % Daryl
>>>>>> >
>>>>>> > Regards,
>>>>>> >
>>>>>> > --
>>>>>> > Michael Mráka
>>>>>> > Satellite Engineering, Red Hat
>>>>>> >
>>>>>> > _______________________________________________
>>>>>> > 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
>>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>
>
> _______________________________________________
> 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/20141106/19abe346/attachment.htm>