Hypervisor Support - Virtual Guest Image Versioning

[ray]

I am specifically looking at the Xen hypervisor but it may have broader
applicability.

I am in a personal workstation environment using Xen as a hypervisor
managing a half dozen guest operating systems.  I am planning on one of
those to be an Apache/SVN server.  There will be a variety of
repositories.  I am considering how I may implement a repository to
track the versioning of guest images.  I would like to keep version
histories of the different guests; experimental perturbations, upgrades,
etc.  I like the SVN version graph and I am wondering about how much I
can add notes to clarify the differences.  Additionally, update the
notes when in retrospect, more information is needed for historical
entries.

Since the binaries are large, I will probably need to extend the storage
to a slower, cheaper media for the older versions.  I want to keep fast
response for new entries.  I am wondering how I might have the best of
both worlds and still be able to pull up a full historical graph.

I plan to use SVN both locally and over the Internet for personal use
only; I am looking for comments/cogestions on setting up for this
service.

I would really like to hear comments and suggestions on implementing
Apache/SVN on such a hosted service and any about overall system
configuration.

ray

Re: Hypervisor Support - Virtual Guest Image Versioning

[Thorsten Schöning]

Guten Tag r...@aarden.us,
am Montag, 12. Dezember 2011 um 01:50 schrieben Sie:

> I am considering how I may implement a repository to
> track the versioning of guest images.  I would like to keep version
> histories of the different guests; experimental perturbations, upgrades,
> etc.  I like the SVN version graph and I am wondering about how much I
> can add notes to clarify the differences.  Additionally, update the
> notes when in retrospect, more information is needed for historical
> entries.

You are able to add one log message per commit, but this can be of any
size you want. Altering this log message afterwards must be configured
separately because per default log messages are immutable.

> Since the binaries are large, I will probably need to extend the storage
> to a slower, cheaper media for the older versions.  I want to keep fast
> response for new entries.  I am wondering how I might have the best of
> both worlds and still be able to pull up a full historical graph.

What's the size of your images? Subversion produces diffs for every
committed file and I don't think it's fun to generate diffs for files
with some GB in size. Your images will change practically on every use
of your guest OS, too.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon.030-2 1001-310
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow