This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-users] Making system templates

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Making system templates
From: Nathan Eisenberg <nathan@xxxxxxxxxxxxxxxx>
Date: Wed, 10 Jun 2009 10:16:13 -0700
Accept-language: en-US
Acceptlanguage: en-US
Delivery-date: Wed, 10 Jun 2009 10:17:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A2F419E.20800@xxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4A2D2246.2070607@xxxxxxxxxxxxxx> <4A2D7F46.7070108@xxxxxxxxxx><76BB7F270C366D47AA79851BB0B39D810299D44A@xxxxxxxxxxxxxxxxxx> <4A2DBCC9.4060902@xxxxxxxxxx> <76BB7F270C366D47AA79851BB0B39D810299D468@xxxxxxxxxxxxxxxxxx> <11B064048F34FD4094CBA16FC04BE2196033AFCE@ex01> <4A2F419E.20800@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcnpiqBNsLh+8aLjQ2u7poMSGYCoNgAYzaNQ
Thread-topic: [Xen-users] Making system templates
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 

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

-----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.


Xen-users mailing list

Xen-users mailing list