The maintenance cycle is frequent and requires a very small amount of work to
maintain (it's probably entirely automatable); and in exchange, I gain the
ability to state that we independently test upstream patches before applying
them.
Now, whether this is technically necessary is a point I'll happily concede.
Debian-Stable is so named because only very well tested, stable changes are
committed to it.
However, I manage OS's other than Debian (CentOS, Gentoo, Windows, etc), and it
seems logical to apply the same general process to every OS - as they are not
all so well tested before patches are released - than to have an exception for
Debian based solely on the fact that you and I have never had a problem
patching Debian.
Plus, having a local repository is very nice.
Best Regards
Nathan Eisenberg
Sr. Systems Administrator
Atlas Networks, LLC
support@xxxxxxxxxxxxxxxx
http://support.atlasnetworks.us/portal
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Thomas Goirand
Sent: Tuesday, June 09, 2009 10:16 PM
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Making system templates
Nathan Eisenberg wrote:
> My solution is very close to Thomas', except that I debootstrap from a local
> mirror which is updated only after the upstream packages are tested against
> common configurations.
>
> That way, I can use debootstrap to get my definition of 'current-stable',
> while simultaneously being reassured that the packages I am pulling down are
> of a version I have tested and verified to work. This is part of my upgrade
> cycle, so if I add a tenth machine to a cluster using the debootstrap method,
> I am pulling down the same version of packages as those already on the
> production machines
Having a package that changes behavior in the Stable version of Debian
shall NEVER happen. If so, then you can file a bug in the tracker. But I
never saw this happening over the last 5 years.
We simply use approx to do package download caching. This is really
enough, no need to manually create your own set of package. You are
being over paranoid here.
Thomas
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home