Hi,
Redhat announced RHEL 5.1 on Nov 07, so hopefully CentOS 5.1 will be ready shortly. But I get kind of nervous of the arrival of 5.1.
My problem is: I have hundreds Centos 5.0 boxes just finished installation and I will continue to install and upgrade hundreds more in next few months. With the arrival of Centos 5.1, I don't like to reinstall them anymore but continuous upgrade instead -- if this is possible?
Currently I download the Centos 5.0 upgrade packages from mirror sites on Internet (.../centos/5/updates/{SRPMS,i386,x86_64}/...), with the arrival of Centos 5.1, are the existing Centos 5.0 update packages will be removed in honor of Centos 5.1 updates? or it will stay? And how about the Centos 5.1's default packages in distro?
Give an example here:
2.6.18-8.1.15 version kernel is the most recently updated kernel for Centos 5.0 distro, if the Centos 5.1 distro comes with 2.6.18-8.1.10000 kernel and in the first few weeks there are no kernel updates for 5.1, then how can I upgrade my kernel to 2.6.18-8.1.10000 naturally -- will the 2.6.18-8.1.10000 shows in the same update sources directories(.../centos/5/updates/{SRPMS,i386,x86_64/...)?
A similar question is: are the update diretories contains only updates for 5.1 distro, or both 5.0 and 5.1?
Any clarifications are greatly appreciated.
--Robinson
____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs
Robinson Tiemuqinke pisze:
Hi,
Redhat announced RHEL 5.1 on Nov 07, so hopefully CentOS 5.1 will be ready shortly. But I get kind of nervous of the arrival of 5.1.
My problem is: I have hundreds Centos 5.0 boxes just finished installation and I will continue to install and upgrade hundreds more in next few months. With the arrival of Centos 5.1, I don't like to reinstall them anymore but continuous upgrade instead -- if this is possible?
Currently I download the Centos 5.0 upgrade packages from mirror sites on Internet (.../centos/5/updates/{SRPMS,i386,x86_64}/...), with the arrival of Centos 5.1, are the existing Centos 5.0 update packages will be removed in honor of Centos 5.1 updates? or it will stay? And how about the Centos 5.1's default packages in distro?
Give an example here:
2.6.18-8.1.15 version kernel is the most recently updated kernel for Centos 5.0 distro, if the Centos 5.1 distro comes with 2.6.18-8.1.10000 kernel and in the first few weeks there are no kernel updates for 5.1, then how can I upgrade my kernel to 2.6.18-8.1.10000 naturally -- will the 2.6.18-8.1.10000 shows in the same update sources directories(.../centos/5/updates/{SRPMS,i386,x86_64/...)?
A similar question is: are the update diretories contains only updates for 5.1 distro, or both 5.0 and 5.1?
Any clarifications are greatly appreciated.
It's simply. All things from 5.0 to 5.1 will be done automatically via yum (as standard update) or in rare situation can be possibly depedency problem (when mixing different repo ?).
So don't worry. if you are really affraid - update only one box and test ... test ... then update the rest.
I must say. In Centos 4 world all updates from 1 to 2 to 3 ... to 5 were go in smooth way.
Regards,
Irens
--Robinson
____________________________________________________________________________________Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Wed, 2007-11-28 at 22:36 +0100, Jancio Wodnik wrote:
Robinson Tiemuqinke pisze:
<snip>
It's simply. All things from 5.0 to 5.1 will be done automatically via yum (as standard update) or in rare situation can be possibly depedency problem (when mixing different repo ?).
So don't worry. if you are really affraid - update only one box and test ... test ... then update the rest.
I must say. In Centos 4 world all updates from 1 to 2 to 3 ... to 5 were go in smooth way.
Umm... almost. IIRC, there were a couple issues (although not difficult to solve) when a yum update was involved. And something else too, but I don't recall for sure. Seamonkey?
Anyway, other than a couple minor things like that, plain old yum update seems to be reliable and you have very little to watch for.
To the OP: with 500+ machines(?), would you benefit from having a local repo that you could manage to be sure that all your nodes "sing from the same sheet of music"? The lists have advice on this if you need it.
Search the lists and you'll find the info.
Regards,
Irens
--Robinson
<snip sig stuff>
-- Bill
William L. Maltby wrote:
To the OP: with 500+ machines(?), would you benefit from having a local repo that you could manage to be sure that all your nodes "sing from the same sheet of music"? The lists have advice on this if you need it.
With Centos 3.x you could easily pull things through a caching proxy by setting http_proxy in the environment from the command like: http_proxy=myproxy.mydomain.com yum update. and any number of machines at a location would only have to download a needed file once (assuming your proxy is configured to cache large files). However, newer releases use a mirrorlist approach that makes each machine pick a different url, defeating the caching. I thought I saw something about 5.x having a way to restore the old way without being tied to a single repository, but I've forgotten it now.
--- Jancio Wodnik jancio_wodnik@wp.pl wrote:
Robinson Tiemuqinke pisze:
Currently I download the Centos 5.0 upgrade
packages
from mirror sites on Internet (.../centos/5/updates/{SRPMS,i386,x86_64}/...),
with
the arrival of Centos 5.1, are the existing Centos
5.0
update packages will be removed in honor of Centos
5.1
updates? or it will stay? And how about the Centos 5.1's default packages in distro?
Give an example here:
2.6.18-8.1.15 version kernel is the most recently updated kernel for Centos 5.0 distro, if the
Centos
5.1 distro comes with 2.6.18-8.1.10000 kernel and
in
the first few weeks there are no kernel updates
for
5.1, then how can I upgrade my kernel to 2.6.18-8.1.10000 naturally -- will the 2.6.18-8.1.10000 shows in the same update sources
directories(.../centos/5/updates/{SRPMS,i386,x86_64/...)?
A similar question is: are the update diretories contains only updates for 5.1 distro, or both 5.0
and
5.1?
Any clarifications are greatly appreciated.
It's simply. All things from 5.0 to 5.1 will be done automatically via yum (as standard update) or in rare situation can be possibly depedency problem (when mixing different repo ?).
So don't worry. if you are really affraid - update only one box and test ... test ... then update the rest.
I must say. In Centos 4 world all updates from 1 to 2 to 3 ... to 5 were go in smooth way.
Regards,
Irens
I have had my local 5.0 update repository (.../centos/5.0/updates/{SRPMS,i386,x86_64}/...) setup and used it for my 900+ boxes's daily upgrade already. The repository is synchronized with official Internet mirrors daily to keep it current.
My major concerns is: After the 5.1 is released, the update channel/directory (.../centos/5.1/updates/{SRPMS,i386,x86_64}/...) may change to contain only updates for 5.1 snapshot/release, not updates since 5.0. If so, then all my Centos 5.0 boxes will suffer.
I have the serious concern because most Centos Mirror sites on Internet ONLY keep the updates for latest release/snapshot, not holds updates since the base(3.0, 4.0, 5.0 etc) release. This seems like a big problem if we would like to install from base|initial release (3.0, 4.0, 5.0) continuously and then use a single up-to-date update/ repository to upgrade machines to current level.
For example, at Stanford's Centos 4 mirror site, only 4.5 is mirrored while all the other 4.0/4.1/4.2/4.3/4.4 are not. and in the updates/ directory only updates for 4.5 are kept there. If the same is true for all other sites honoring 5.0 series, then I think I will definitely get screwed If I tried to keep on using base 5.0 and daily synced updates/ (exactly the same) for upgrade.
Any mirror sites hold updates since base release? Or I have to keep on adding more repositories to yum's configuration? 5.0 distro, 5.0 updates, 5.1 distro, 5.1 updates, 5.2 distro, 5.2 updates. etc. If so, then it is too low-performanced and erro-prone.
Any one have experience on upgrade Centos 4 releases from 4.0 to 4.5 can shed a light on this?
Thanks a lot.
--Robinson
____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs
Robinson Tiemuqinke wrote:
My major concerns is: After the 5.1 is released, the update channel/directory (.../centos/5.1/updates/{SRPMS,i386,x86_64}/...) may change to contain only updates for 5.1 snapshot/release, not updates since 5.0. If so, then all my Centos 5.0 boxes will suffer.
afaik, the updates directory contains the latest updates to all packages that have been updated since the original .0 release.
clients update from .../centos/5/updates/... .../not centos/5.1/updates/... (or 4 vs 4.x, etc)
John R Pierce wrote:
afaik, the updates directory contains the latest updates to all packages that have been updated since the original .0 release.
Thats not true, the <rel>/updates/ dir will only contain updates released from the time that the <rel>/os/ was released. However, that is not an issue since yum does not consider repositories on their own, it merges all data into one set and then selects packages to update, therefore packages from the <rel>/os/ repository get included as well.
so, you really do want to stay with the /5/ release, in order to keep getting all the latest updates etc. and not use ( as you pointed out already ) the 5.1/ or 5.0/ directories.
- KB
--- Karanbir Singh mail-lists@karan.org wrote:
John R Pierce wrote:
afaik, the updates directory contains the latest
updates to all packages
that have been updated since the original .0
release.
Thats not true, the <rel>/updates/ dir will only contain updates released from the time that the <rel>/os/ was released. However, that is not an issue since yum does not consider repositories on their own, it merges all data into one set and then selects packages to update, therefore packages from the <rel>/os/ repository get included as well.
so, you really do want to stay with the /5/ release, in order to keep getting all the latest updates etc. and not use ( as you pointed out already ) the 5.1/ or 5.0/ directories.
- KB
The problem is whether there is a way to achieve the following:
Continue to install machines with Centos 5.0(!!) distro (not 5.1, 5.2, etc snapshots|subreleases), But have .../centos/5/updates/{SRPMS|i386|x86_64}/ repositories|directories which contains updates since 5.0 to current level. This way I only need to feed yum with two repositories: centos/5.0/os/ and centos/5/updates/ -- some time will have local custom repos as well, but that is another totally different topic.
Currently I can not do it, because on Internet Centos Mirror Sites, the centos/{4,5}/updates/ are in fact symbolic links to centos/{4,5}.<latest_update_snapshot_release>/updates/ and contains update RPMS ONLY SINCE the relase date {4,5}.}.<latest_update_snapshot_release>. But what I like to have is a accumulated updates repository since {4,5}.0 release date.
I could try to emulate the effect by synchronizing each update repository for previous subreleases, For example, for Centos 4 series, sync updates RPMS for 4.0, 4.1, 4.2, 4.3, and 4.4 into one local repository and feed it to yum.conf, then sync updates for 4.5 into another repository for yum, at last, feed the repository of 4.0 base os to yum as well. Totally yum has one base os 4.0 repo, two updates repos for possible??consistent initial installation and upgrade -- If it works, then there is no need to setup new kickstart/pxe for each subrelease after the latter is released.
Has any one done the above? If so, how is that working? or there is no need to do do it because there are accumulated updates repositories on Internet Mirror Sites to sync from? Or because this is impossible because each subrelease contains new versions of packages/tools not in any updates/ repositories??
Thanks a lot.
--Robinson
____________________________________________________________________________________ Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/
on 11/29/2007 2:20 PM Robinson Tiemuqinke spake the following:
--- Karanbir Singh mail-lists@karan.org wrote:
John R Pierce wrote:
afaik, the updates directory contains the latest
updates to all packages
that have been updated since the original .0
release.
Thats not true, the <rel>/updates/ dir will only contain updates released from the time that the <rel>/os/ was released. However, that is not an issue since yum does not consider repositories on their own, it merges all data into one set and then selects packages to update, therefore packages from the <rel>/os/ repository get included as well.
so, you really do want to stay with the /5/ release, in order to keep getting all the latest updates etc. and not use ( as you pointed out already ) the 5.1/ or 5.0/ directories.
- KB
The problem is whether there is a way to achieve the following:
Continue to install machines with Centos 5.0(!!) distro (not 5.1, 5.2, etc snapshots|subreleases), But have .../centos/5/updates/{SRPMS|i386|x86_64}/ repositories|directories which contains updates since 5.0 to current level. This way I only need to feed yum with two repositories: centos/5.0/os/ and centos/5/updates/ -- some time will have local custom repos as well, but that is another totally different topic.
Currently I can not do it, because on Internet Centos Mirror Sites, the centos/{4,5}/updates/ are in fact symbolic links to centos/{4,5}.<latest_update_snapshot_release>/updates/ and contains update RPMS ONLY SINCE the relase date {4,5}.}.<latest_update_snapshot_release>. But what I like to have is a accumulated updates repository since {4,5}.0 release date.
I could try to emulate the effect by synchronizing each update repository for previous subreleases, For example, for Centos 4 series, sync updates RPMS for 4.0, 4.1, 4.2, 4.3, and 4.4 into one local repository and feed it to yum.conf, then sync updates for 4.5 into another repository for yum, at last, feed the repository of 4.0 base os to yum as well. Totally yum has one base os 4.0 repo, two updates repos for possible??consistent initial installation and upgrade -- If it works, then there is no need to setup new kickstart/pxe for each subrelease after the latter is released.
Has any one done the above? If so, how is that working? or there is no need to do do it because there are accumulated updates repositories on Internet Mirror Sites to sync from? Or because this is impossible because each subrelease contains new versions of packages/tools not in any updates/ repositories??
Thanks a lot.
--Robinson
But doesn't yum only install the newest update package anyway? You will just take up space with updates you might not need unless you need to downgrade a package, and you can't do that with yum. If I right now install CentOS 4 from the 4.0 release CD's and yum update, I will basically have the same thing as if I installed from the 4.5 CD's and ran yum update. But the updates will take considerably longer. I am having trouble grasping your dilema. The biggest difference in sub-releases are the install time tools and kernels that may have been updated when the CD/DVD's are respun.
Robinson Tiemuqinke wrote:
The problem is whether there is a way to achieve the following:
Continue to install machines with Centos 5.0(!!) distro (not 5.1, 5.2, etc snapshots|subreleases), But have .../centos/5/updates/{SRPMS|i386|x86_64}/ repositories|directories which contains updates since 5.0 to current level. This way I only need to feed yum with two repositories: centos/5.0/os/ and centos/5/updates/ -- some time will have local custom repos as well, but that is another totally different topic.
If you install a Centos 4.0 now you can 'yum update' and you'll end up current with 4.5. I think this works because the [base] repository floats with the symlinks to point at one containing the updated versions of everything at the point release time. If you are talking about mirroring the contents you'll have to mirror the symlinked directory.
--- Les Mikesell lesmikesell@gmail.com wrote:
Robinson Tiemuqinke wrote:
The problem is whether there is a way to achieve
the
following:
Continue to install machines with Centos 5.0(!!) distro (not 5.1, 5.2, etc snapshots|subreleases),
But
have .../centos/5/updates/{SRPMS|i386|x86_64}/ repositories|directories which contains updates
since
5.0 to current level. This way I only need to feed
yum
with two repositories: centos/5.0/os/ and centos/5/updates/ -- some time will have local
custom
repos as well, but that is another totally
different
topic.
If you install a Centos 4.0 now you can 'yum update' and you'll end up current with 4.5. I think this works because the [base] repository floats with the symlinks to point at one containing the updated versions of everything at the point release time. If you are talking about mirroring the contents you'll have to mirror the symlinked directory.
-- Les Mikesell lesmikesell@gmail.com
If installed with 4.0, and run a 'yum upgrade' will end up with 4.5 -- then, what are the repos configured for yum? Are the repos the following and ONLY the following (excluding custom ones)?
1, 4.0 base OS distro 2, 4 base OS distro (symbolic link pointing to 4.5) 3, 4 updates (symbolic link pointing to .../4/updates/..., which means updates since 4.5 sub-release)
Is the above right? or you have even omitted #1 (4.0 base OS distro repo)? Thanks.
--Robinson
____________________________________________________________________________________ Get easy, one-click access to your favorites. Make Yahoo! your homepage. http://www.yahoo.com/r/hs
Robinson Tiemuqinke wrote:
Continue to install machines with Centos 5.0(!!) distro (not 5.1, 5.2, etc snapshots|subreleases), But have .../centos/5/updates/{SRPMS|i386|x86_64}/ repositories|directories which contains updates since 5.0 to current level. This way I only need to feed yum with two repositories: centos/5.0/os/ and centos/5/updates/ -- some time will have local custom repos as well, but that is another totally different topic.
in that case you will need to find the updates in the 5.1/os/ repo as well and put it yourself into the updates/ directory, which will be a waste of time, network bandwidth and resources. You are going to be much better off just installing 5.1 from the future and using that.
For the machines you have 5.0 on, just run yum against the 5.1/os/ and 5.1/updates/ repo, and they will also move to 5.1. Note, the [os] repo also needs to be from 5.1 and not from 5.0 when you run the yum update on the 5.0 installed machines. other wise you *will* loose updates.
Currently I can not do it, because on Internet Centos Mirror Sites, the centos/{4,5}/updates/ are in fact symbolic links to centos/{4,5}.<latest_update_snapshot_release>/updates/ and contains update RPMS ONLY SINCE the relase date {4,5}.}.<latest_update_snapshot_release>. But what I like to have is a accumulated updates repository since {4,5}.0 release date.
you are trying to solve the wrong problem. I suggest you take a few minutes and work out exactly how the /5/ and /4/ symbolic links are handled on the mirror.centos.org network, and setup something similar for yourself as well.
Has any one done the above? If so, how is that working? or there is no need to do do it because there
I dont know how you install the machines, but i think its a fair guess that just reimaging the install process with new installer images for each point release, will be a lot less work than what you are doing at the moment.
On Fri, Nov 30, 2007 at 01:02:59AM +0000, Karanbir Singh wrote:
Robinson Tiemuqinke wrote:
Continue to install machines with Centos 5.0(!!) distro (not 5.1, 5.2, etc snapshots|subreleases), But have .../centos/5/updates/{SRPMS|i386|x86_64}/ repositories|directories which contains updates since 5.0 to current level. This way I only need to feed yum with two repositories: centos/5.0/os/ and centos/5/updates/ -- some time will have local custom repos as well, but that is another totally different topic.
in that case you will need to find the updates in the 5.1/os/ repo as well and put it yourself into the updates/ directory, which will be a waste of time, network bandwidth and resources. You are going to be much better off just installing 5.1 from the future and using that.
For the machines you have 5.0 on, just run yum against the 5.1/os/ and 5.1/updates/ repo, and they will also move to 5.1. Note, the [os] repo also needs to be from 5.1 and not from 5.0 when you run the yum update on the 5.0 installed machines. other wise you *will* loose updates.
I'm coming in here kind of in the middle, but I find this discussion to be confusing... In the past I've always found that my centos/RHEL machines automagically updated themselves to the latest dot-release without me having to do anything other than run yum/up2date.
Are you saying here that a Centos 5 system WILL NOT automatically become 5.1 when the updates are pushed out? Or am I just totally confuzzled?
fred smith wrote:
I'm coming in here kind of in the middle, but I find this discussion to be confusing... In the past I've always found that my centos/RHEL machines automagically updated themselves to the latest dot-release without me having to do anything other than run yum/up2date.
Are you saying here that a Centos 5 system WILL NOT automatically become 5.1 when the updates are pushed out? Or am I just totally confuzzled?
a CentOS-5.0 machine, when yum updated, without changes to the yum configs will update to 5.1 and 5.2 when its released etc and keep with the latest released updates.
What Robinson is trying to do, or seems to be wanting to do, is to just install 5.0 and *not* update his main base OS repo to the newer one, and stick with 5.0 only. in that case, he is going to need to jump through a few hoops to keep with the updates.
Normal uses ( and I'd say pretty much everyone ) do not need to worry about this, since they dont do this sort of a thing :D
Robinson Tiemuqinke wrote:
--- Jancio Wodnik jancio_wodnik@wp.pl wrote:
Robinson Tiemuqinke pisze:
<snip>
I have had my local 5.0 update repository (.../centos/5.0/updates/{SRPMS,i386,x86_64}/...) setup and used it for my 900+ boxes's daily upgrade already. The repository is synchronized with official Internet mirrors daily to keep it current.
My major concerns is: After the 5.1 is released, the update channel/directory (.../centos/5.1/updates/{SRPMS,i386,x86_64}/...) may change to contain only updates for 5.1 snapshot/release, not updates since 5.0. If so, then all my Centos 5.0 boxes will suffer.
I have the serious concern because most Centos Mirror sites on Internet ONLY keep the updates for latest release/snapshot, not holds updates since the base(3.0, 4.0, 5.0 etc) release. This seems like a big problem if we would like to install from base|initial release (3.0, 4.0, 5.0) continuously and then use a single up-to-date update/ repository to upgrade machines to current level.
For example, at Stanford's Centos 4 mirror site, only 4.5 is mirrored while all the other 4.0/4.1/4.2/4.3/4.4 are not. and in the updates/ directory only updates for 4.5 are kept there. If the same is true for all other sites honoring 5.0 series, then I think I will definitely get screwed If I tried to keep on using base 5.0 and daily synced updates/ (exactly the same) for upgrade.
Any mirror sites hold updates since base release? Or I have to keep on adding more repositories to yum's configuration? 5.0 distro, 5.0 updates, 5.1 distro, 5.1 updates, 5.2 distro, 5.2 updates. etc. If so, then it is too low-performanced and erro-prone.
use 5 and make it a symlink to 5.0 ... on your mirror, move the symlink to 5.1 or 5.2 when the time comes ... and use 5 in your yum configs
Any one have experience on upgrade Centos 4 releases from 4.0 to 4.5 can shed a light on this?
Thanks a lot.
--Robinson
Well ... if you look, WE use a 5 and not a 5.0 or a 5.1 in our CentOS-Base.repo
5 initially contains 5.0 ... and will contain 5.1.
SO ... if you use the 5 and not 5.0 or 5.1 then you will be set.
We do remove 5.0 when we add 5.1 (and 5.0 goes to our vault ... at http://vault.centos.org/.
So ... if you sync down 5.0 ... I would sync down 5 and 5.0 and 5.1 and use 5 as the update source not 5.0 or 5.1. If you are using $releasever then you are already using 5 and not 5.0.
Then when we shift, it will be seemless (as long as you have Base and Updates both turned on).
We DO NOT put all updates since the beginning into updates, it is ONLY updates that to the CURRENT branch. However, base+updates of the current branch == all the latest RPMS, so a yum update against 5.1 base+updates from any other 5x will get you totally updated (once it is released and we have set 5.1 to the default).
On Wed, Nov 28, 2007 at 12:42:09PM -0800, Robinson Tiemuqinke alleged:
Hi,
Redhat announced RHEL 5.1 on Nov 07, so hopefully CentOS 5.1 will be ready shortly. But I get kind of nervous of the arrival of 5.1.
My problem is: I have hundreds Centos 5.0 boxes just finished installation and I will continue to install and upgrade hundreds more in next few months. With the arrival of Centos 5.1, I don't like to reinstall them anymore but continuous upgrade instead -- if this is possible?
Don't think of 5.0 and 5.1 as different distros. They are the same distro.
Think of it as a bunch of non-critical updates that were withheld from the regular update cycle, tested as a set, and released all at once with a new installer image. It is just an update, analogous to a Windows service pack.
Think of RHEL5 as the distro, evolving through time, and 5.1 as a well-tested snapshot of RHEL5 at a particular point in time.
A regular 'yum update' will bring in all of the new updates. There is no need to reinstall the OS.
-
fred smith -
Garrick Staples -
Jancio Wodnik -
John R Pierce -
Johnny Hughes -
Karanbir Singh -
Les Mikesell -
Robinson Tiemuqinke -
Scott Silva -
William L. Maltby