| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
RE: [Xen-users] Making system templates
Certainly it's hard to claim that any one way is always 'best'. Ultimately,
being closer to current is generally better than being further away from it -
not that this is exactly news to anyone.
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
Thank You,
Nathan Eisenberg
Sr. Systems Administrator
Atlas Networks, LLC
Atlas Networks is an Atlas Accelerator Company
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of David Morris
Sent: Monday, June 08, 2009 7:29 PM
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Making system templates
> -----Original Message-----
> From: Thomas Goirand [mailto:thomas@xxxxxxxxxx]
> Sent: Monday, June 08, 2009 6:37 PM
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] Making system templates
>
> David Morris wrote:
> >
> >
> >> -----Original Message-----
> >> From: Thomas Goirand [mailto:thomas@xxxxxxxxxx]
> >> Sent: Monday, June 08, 2009 2:15 PM
> >> Cc: xen-users@xxxxxxxxxxxxxxxxxxx
> >> Subject: Re: [Xen-users] Making system templates
> >>
> >> The best way ever is... to NOT use templates or images.
> >> Templates gets outdated, and soon have loads of package to
> upgrade.
> >> The best way (whenever possible, this is not always the
> case) is to
> >> use tools to pull and setup packages out of FTP repositories.
> >
> > That is not always true ... Templates provide stability in terms of
> > the environment. It is often desireable to reproduce consistent
> > configurations so as to avoid unexpected changes.
>
> Oh, you are the first guy I met that is telling me that
> Debian evolves too fast then! :)
Too fast or too slow ... Unexpected changes introduced into an
environment can cause grief. I'm only challenging the assertion that
"The best way" is to create each new machine on the fly. Whether or not
it is best depends on organizational needs.
>
> I supposed by the way that you have noticed we support both types...
>
> 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
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home