FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CentOS > CentOS

 
 
LinkBack Thread Tools
 
Old 05-10-2012, 05:36 AM
Gregory Machin
 
Default Allow updates but not upgrades

Hi.
At the moment it seems my machines just update to the latest current
release . I install a 6.0 machine and run yum update , and next thing
its 6.2 .

I have a requirement where I need machines to only upgrade to even
numbered sub releases eg: 6.0 , 6.2, 6.4 and only on my approval. But
will allow updates within a given release.

How can I achieve this ?

If I sync the repositories for eg: 6.0 , 6.2, 6.4 separately in
Spacewalk and only allow access to the ones I want to give access to,
would that work ?

Thanks

G
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-10-2012, 06:46 AM
Peter Kjellstr÷m
 
Default Allow updates but not upgrades

On Thursday 10 May 2012 17.36.07 Gregory Machin wrote:
> Hi.
> At the moment it seems my machines just update to the latest current
> release . I install a 6.0 machine and run yum update , and next thing
> its 6.2 .
>
> I have a requirement where I need machines to only upgrade to even
> numbered sub releases eg: 6.0 , 6.2, 6.4 and only on my approval. But
> will allow updates within a given release.

There is no provided functionality to do this, that is, CentOS doesn't
differentiate between what you call updates and upgrades.

> How can I achieve this ?

Normally (default yum config) a machine fetches it's packages from URL.../6/..
You can change this 6 to 6.x. That will prevent you from getting updates
belonging to 6.x+1 _but_ will have the negative side-effect of stopping to
work when 6.x+1 is released (6.x removed from normal mirrors).

Keeping you own repo (rsynced without --delete) may be the best idea (but
requires more work).

/Peter

> If I sync the repositories for eg: 6.0 , 6.2, 6.4 separately in
> Spacewalk and only allow access to the ones I want to give access to,
> would that work ?
>
> Thanks
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-10-2012, 06:55 AM
John R Pierce
 
Default Allow updates but not upgrades

On 05/09/12 10:36 PM, Gregory Machin wrote:
> I have a requirement where I need machines to only upgrade to even
> numbered sub releases eg: 6.0 , 6.2, 6.4 and only on my approval.

thats a rather strange requirement. 6.1 is 6.0 with updates rolled up.

a more sane requirement would be to only allow pre-tested updates, which
you'd do by testing the updates on a staging machine, then posting them
to your own internal yum repository which your production machines would
update from.

--
john r pierce N 37, W 122
santa cruz ca mid-left coast

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-10-2012, 08:58 AM
Johnny Hughes
 
Default Allow updates but not upgrades

On 05/10/2012 01:46 AM, Peter Kjellstr÷m wrote:
> On Thursday 10 May 2012 17.36.07 Gregory Machin wrote:
>> Hi.
>> At the moment it seems my machines just update to the latest current
>> release . I install a 6.0 machine and run yum update , and next thing
>> its 6.2 .
>>
>> I have a requirement where I need machines to only upgrade to even
>> numbered sub releases eg: 6.0 , 6.2, 6.4 and only on my approval. But
>> will allow updates within a given release.
> There is no provided functionality to do this, that is, CentOS doesn't
> differentiate between what you call updates and upgrades.

I want to point out that neither does Red Hat.

If you are on the RHEL 6 channel and if you run an update after you
install RHEL 6.0, you will be at RHEL 6.2.

6.0, 6.1, and 6.2 are really only point in time freezes of installation
media. They are not separate entities or versions. It is like Windows
and service packs. Windows 7 Service Pack 1 and Windows 7 Service Pack
2 are both Windows 7. Not many people want to freeze Windows 7 on
Service Pack 1 ... and Microsoft does not provide the ability for you to
freeze at that point. Nor does Red Hat provide the ability to freeze at
6.1 or 6.0.

As I said, minor releases are about install media, not the distro. The
Distribution is CentOS-6 it is not CentOS-6.1 or CentOS-6.2.

If you stay on 6.0 then you do not get security updates. 6.0 + updates
= 6.x (whatever that is at the time).

If you want to test the updates before you deploy them (not an unwise
thing to do), then you need to maintain separate repositories where you
dump tested RPMs in and update your machines from that.

The bottom line is, CentOS supports only CentOS-6 (or CentOS-5) ... if
you want something different than that, you need to build your own
repositories out of our packages.

>
>> How can I achieve this ?
> Normally (default yum config) a machine fetches it's packages from URL.../6/..
> You can change this 6 to 6.x. That will prevent you from getting updates
> belonging to 6.x+1 _but_ will have the negative side-effect of stopping to
> work when 6.x+1 is released (6.x removed from normal mirrors).
>
> Keeping you own repo (rsynced without --delete) may be the best idea (but
> requires more work).
>
>> If I sync the repositories for eg: 6.0 , 6.2, 6.4 separately in
>> Spacewalk and only allow access to the ones I want to give access to,
>> would that work ?
>>


_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-10-2012, 09:49 AM
Peter Kjellstr÷m
 
Default Allow updates but not upgrades

On Thursday 10 May 2012 03.58.17 Johnny Hughes wrote:
> On 05/10/2012 01:46 AM, Peter Kjellstr÷m wrote:
> > On Thursday 10 May 2012 17.36.07 Gregory Machin wrote:
> >> Hi.
> >> At the moment it seems my machines just update to the latest current
> >> release . I install a 6.0 machine and run yum update , and next thing
> >> its 6.2 .
> >>
> >> I have a requirement where I need machines to only upgrade to even
> >> numbered sub releases eg: 6.0 , 6.2, 6.4 and only on my approval. But
> >> will allow updates within a given release.
> >
> > There is no provided functionality to do this, that is, CentOS doesn't
> > differentiate between what you call updates and upgrades.
>
> I want to point out that neither does Red Hat.
>
> If you are on the RHEL 6 channel and if you run an update after you
> install RHEL 6.0, you will be at RHEL 6.2.
>
> 6.0, 6.1, and 6.2 are really only point in time freezes of installation
> media. They are not separate entities or versions.

To be fair that's not entierly true. At those points in time updates are more
numerous and higher impact (new kernel -131 -> -220 last time, driver updates,
some new tech. etc.).

/Peter_____________________________________________ __
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-10-2012, 09:58 AM
Johnny Hughes
 
Default Allow updates but not upgrades

On 05/10/2012 04:49 AM, Peter Kjellstr÷m wrote:
> On Thursday 10 May 2012 03.58.17 Johnny Hughes wrote:
>> On 05/10/2012 01:46 AM, Peter Kjellstr÷m wrote:
>>> On Thursday 10 May 2012 17.36.07 Gregory Machin wrote:
>>>> Hi.
>>>> At the moment it seems my machines just update to the latest current
>>>> release . I install a 6.0 machine and run yum update , and next thing
>>>> its 6.2 .
>>>>
>>>> I have a requirement where I need machines to only upgrade to even
>>>> numbered sub releases eg: 6.0 , 6.2, 6.4 and only on my approval. But
>>>> will allow updates within a given release.
>>> There is no provided functionality to do this, that is, CentOS doesn't
>>> differentiate between what you call updates and upgrades.
>> I want to point out that neither does Red Hat.
>>
>> If you are on the RHEL 6 channel and if you run an update after you
>> install RHEL 6.0, you will be at RHEL 6.2.
>>
>> 6.0, 6.1, and 6.2 are really only point in time freezes of installation
>> media. They are not separate entities or versions.
> To be fair that's not entierly true. At those points in time updates are more
> numerous and higher impact (new kernel -131 -> -220 last time, driver updates,
> some new tech. etc.).

Sure, and people can and should test things before deployment.

But what I said is true ... there is no real mechanism to do this in Red
Hat either, other than to buy a RHN satellite server (or create your own
RHEL yum repos) and populate those separately with tested RPMS
yourself. If you run updates when subscribed to RHN, it works just like
running updates in CentOS ... you get all or nothing unless you take
actions manually to prevent it.

There are several solutions to be able to make that happen ... manual
repos yourself, mrepo, spacewalk, etc.



_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-10-2012, 12:49 PM
Dennis Jacobfeuerborn
 
Default Allow updates but not upgrades

On 05/10/2012 08:55 AM, John R Pierce wrote:
> On 05/09/12 10:36 PM, Gregory Machin wrote:
>> I have a requirement where I need machines to only upgrade to even
>> numbered sub releases eg: 6.0 , 6.2, 6.4 and only on my approval.
>
> thats a rather strange requirement. 6.1 is 6.0 with updates rolled up.
>
> a more sane requirement would be to only allow pre-tested updates, which
> you'd do by testing the updates on a staging machine, then posting them
> to your own internal yum repository which your production machines would
> update from.
>

This requirement sounds suspiciously like it was made for software that
uses the "even numer = stable release, odd number = development release"
versioning method. Since that doesn't apply here the requirement doesn't
make sense.

Regards,
Dennis
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-10-2012, 12:52 PM
Les Mikesell
 
Default Allow updates but not upgrades

On Thu, May 10, 2012 at 4:58 AM, Johnny Hughes <johnny@centos.org> wrote:
>
> There are several solutions to be able to make that happen ... manual
> repos yourself, mrepo, spacewalk, etc.
>

All of those that I've investigated make you manage copies of packages
locally which seems like overkill when you aren't changing them
locally. Is there any solution that simply lets you tell yum not to
install any updates newer than the latest one you've tested? Or more
cumbersome but still less so than maintaining repos - a way to have
yum duplicate the package/versions that are on your test machines
across a set of others?

--
Les Mikesell
lesmikesell@gmail.com
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-10-2012, 01:02 PM
Johnny Hughes
 
Default Allow updates but not upgrades

On 05/10/2012 07:52 AM, Les Mikesell wrote:
> On Thu, May 10, 2012 at 4:58 AM, Johnny Hughes <johnny@centos.org> wrote:
>> There are several solutions to be able to make that happen ... manual
>> repos yourself, mrepo, spacewalk, etc.
>>
> All of those that I've investigated make you manage copies of packages
> locally which seems like overkill when you aren't changing them
> locally. Is there any solution that simply lets you tell yum not to
> install any updates newer than the latest one you've tested? Or more
> cumbersome but still less so than maintaining repos - a way to have
> yum duplicate the package/versions that are on your test machines
> across a set of others?
>

No ... yum is designed to install software from repositories. If you
want to install a subset of a repository, then you need make a new
repository that is a subset of the said repository.

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 
Old 05-10-2012, 02:06 PM
Alfred von Campe
 
Default Allow updates but not upgrades

On May 10, 2012, at 1:36, Gregory Machin wrote:

> I have a requirement where I need machines to only upgrade to even
> numbered sub releases eg: 6.0 , 6.2, 6.4 and only on my approval. But
> will allow updates within a given release.

Others have debated the usefulness of this requirement, so I won't address this here.

> How can I achieve this ?

You can easily achieve this by keeping a local mirror of the CentOS repository. I have a cron job every night that does something like this (I update the version manually whenever there is a new CentOS point release):

rsync --archive --delete --partial --stats --verbose
--exclude="alpha" --exclude="ia64" --exclude="ppc" --exclude="s390*"
$CENTOSRSYNCREPO/6.2 /local/www/html/CentOS

I also have a symlink from (in the current case) 6 to 6.2:

ls -l /local/www/html/CentOS/
lrwxrwxrwx 1 root root 3 Dec 23 09:17 6 -> 6.2
drwxrwxr-x 10 342 342 4096 Dec 21 06:37 6.2

Finally, I modify the yum repo config files to point to my mirror (this is just a small snippet from /etc/yum.repos.d/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/
baseurl=http://centosmirror.XXX.com/CentOS/$releasever/os/$basearch/

So all my servers and desktops update from my local mirror and I control when I move the symlink to point to the next release. You can achieve what you want in this way as well.

Alfred

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
 

Thread Tools




All times are GMT. The time now is 01:24 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ę2007 - 2008, www.linux-archive.org