How the main process communicates during the point where you move one
running server to another. That part... not quite sure what is going
on with that.
virt-clone is an awesome little command that I just discovered
(oops!). The absurdity I was doing before I figured that out was more
then a little crazy.
I need to figure out how to backup the xen images. My base OS images
are all 8 gigs a piece. This means:
or bizarre would work if I started tossing 8 gig images in them. No
possibility for deltas. I can re-clone to drop history when I need it
(though I suspect that the new bzng feature to lose history might
work). Distributed revision systems, for being distributed, do not
cluster well. This seems like a fatal problem if you start tracking
anything big in them....
have been looking for an excuse to abuse the ATA over Ethernet
specification for a while.
take a look at how it sends and receives data since I am not sure how
well it would take the hit of having 8gigs of data pushed through it.
I sat and listened through a talk at OSCON about the topic of Xen
image storage. The solution the fellow spoke about was pretty
homegrown (which is... well where we are at at the moment). I find
friends just copying around DVD images and creating directory
databases (aka naming conventions) to track this stuff.