[prev in list] [next in list] [prev in thread] [next in thread]
List: cobbler
Subject: Re: [cobbler] best practices for updating major distro release on systems?
From: Matt Luettgen <mattluettgen () gmail ! com>
Date: 2015-01-16 20:10:32
Message-ID: CAK3MLqJfiJCmOVG1sKN_h6nQZmjGLcLEGLGV72-peEO2T78Azw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Establish a base profile. Apply changes to the profile and the systems will
inherit it. You can override the changes at the system level of cobbler for
exceptions.
On Jan 16, 2015 11:35 AM, "Robert Jacobson" <Robert.C.Jacobson@nasa.gov>
wrote:
>
> I'm using cobbler-2.6.5-9.1 on RHEL 6.6 (yes I know this is not the
> latest release; I hope it's not relevant in this context).
>
> What's the best way to create distros and repositories so that deployed
> systems are always pointed to the "lastest" base and updates?
>
> The problem I'm trying to solve is how to upgrade already-deployed
> systems to the latest release. The problem I have is this, e.g.:
>
> 1. Imported distro centos65-x86_64
> a. defined "updates" repository to <some
> server>/centos/6/updates/x86_64/
>
> 2. System is deployed using CentOS 6.5. cobbler.config automatically
> configures yum:
> a) core-0 to ks_mirror/centos65-x86_64
> b) updates to repo_mirror/centos6-updates
>
> The above works fine until CentOS 6.6 comes out. At some point (I
> haven't figured out when -- does anyone know?), the "updates" repository
> for CentOS will only work correctly for CentOS 6.6 systems. CentOS 6.5
> system updates are majorly broken at this point -- It will see new
> updates for packages that are installed, but often the dependencies are
> for new packages in the CentOS 6.6 base. The CentOS 6.5 machine can't
> see the packages and therefore can't resolve dependencies.
>
> What I've been doing is:
>
> 1. Import distro centos66-x86_64 to cobbler
> 2. On each client system, update yum config to point core-0 to
> ks_mirror/centos66-x86_64.
> "yum update" at this point will upgrade from CentOS 6.5 to 6.6.
>
> If what I'm doing is the "right/best" way, fine -- I'm just wondering if
> there is a better way to organize this so updates don't break on
> existing systems and I don't have to touch every client system when its
> time to upgrade.
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Robert Jacobson Robert.C.Jacobson@nasa.gov
> Lead System Admin Solar Dynamics Observatory (SDO)
> Bldg 14, E222 (301) 286-1591
>
> _______________________________________________
> cobbler mailing list
> cobbler@lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/cobbler
>
[Attachment #5 (text/html)]
<p dir="ltr">Establish a base profile. Apply changes to the profile and the systems \
will inherit it. You can override the changes at the system level of cobbler for \
exceptions.</p> <div class="gmail_quote">On Jan 16, 2015 11:35 AM, "Robert \
Jacobson" <<a \
href="mailto:Robert.C.Jacobson@nasa.gov">Robert.C.Jacobson@nasa.gov</a>> wrote:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br> I'm using \
cobbler-2.6.5-9.1 on RHEL 6.6 (yes I know this is not the<br> latest release; I hope \
it's not relevant in this context).<br> <br>
What's the best way to create distros and repositories so that deployed<br>
systems are always pointed to the "lastest" base and updates?<br>
<br>
The problem I'm trying to solve is how to upgrade already-deployed<br>
systems to the latest release. The problem I have is this, e.g.:<br>
<br>
1. Imported distro centos65-x86_64<br>
a. defined "updates" repository to <some<br>
server>/centos/6/updates/x86_64/<br>
<br>
2. System is deployed using CentOS 6.5. cobbler.config automatically<br>
configures yum:<br>
a) core-0 to ks_mirror/centos65-x86_64<br>
b) updates to repo_mirror/centos6-updates<br>
<br>
The above works fine until CentOS 6.6 comes out. At some point (I<br>
haven't figured out when -- does anyone know?), the "updates" \
repository<br> for CentOS will only work correctly for CentOS 6.6 systems. CentOS \
6.5<br> system updates are majorly broken at this point -- It will see new<br>
updates for packages that are installed, but often the dependencies are<br>
for new packages in the CentOS 6.6 base. The CentOS 6.5 machine can't<br>
see the packages and therefore can't resolve dependencies.<br>
<br>
What I've been doing is:<br>
<br>
1. Import distro centos66-x86_64 to cobbler<br>
2. On each client system, update yum config to point core-0 to<br>
ks_mirror/centos66-x86_64.<br>
"yum update" at this point will upgrade from CentOS 6.5 to \
6.6.<br> <br>
If what I'm doing is the "right/best" way, fine -- I'm just \
wondering if<br> there is a better way to organize this so updates don't break \
on<br> existing systems and I don't have to touch every client system when \
its<br> time to upgrade.<br>
<br>
--<br>
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<br>
Robert Jacobson <a \
href="mailto:Robert.C.Jacobson@nasa.gov">Robert.C.Jacobson@nasa.gov</a><br> Lead \
System Admin Solar Dynamics Observatory (SDO)<br> Bldg 14, E222 \
<a href="tel:%28301%29%20286-1591" value="+13012861591">(301) 286-1591</a><br> <br>
_______________________________________________<br>
cobbler mailing list<br>
<a href="mailto:cobbler@lists.fedorahosted.org">cobbler@lists.fedorahosted.org</a><br>
<a href="https://lists.fedorahosted.org/mailman/listinfo/cobbler" \
target="_blank">https://lists.fedorahosted.org/mailman/listinfo/cobbler</a><br> \
</blockquote></div>
[Attachment #6 (text/plain)]
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/cobbler
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic