This is repository of my old source code which isn't updated any more. Go to git.rot13.org for current projects!
Log of /trunk/vz-clone.pl
Parent Directory
| Revision Log
Revision
31 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Thu Oct 11 19:28:27 2007 UTC
(16 years, 8 months ago)
by
dpavlin
File length: 4656 byte(s)
Diff to
previous 30
,
to
selected 27
delete files on cloned VE which no longer exist on master to create perfect copy
Revision
28 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Fri Oct 5 00:28:43 2007 UTC
(16 years, 8 months ago)
by
dpavlin
File length: 4634 byte(s)
Diff to
previous 27
rsync directly to mounted directory insted through mount --bind
Revision
27 -
(
view)
(
annotate)
-
[selected]
Modified
Thu Oct 4 23:42:24 2007 UTC
(16 years, 8 months ago)
by
dpavlin
File length: 4632 byte(s)
Diff to
previous 26
variable to skip snapshot usage,
fixed logic which machine to vzctl stop on create/destroy
Revision
26 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Thu Oct 4 23:23:20 2007 UTC
(16 years, 8 months ago)
by
dpavlin
File length: 4347 byte(s)
Diff to
previous 25
,
to
selected 27
clone lv are now always named vz-clone-10VEID and not
dependent on OpenVZ lv name
Revision
23 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Thu Oct 4 16:58:01 2007 UTC
(16 years, 8 months ago)
by
dpavlin
File length: 3794 byte(s)
Diff to
previous 22
,
to
selected 27
Create new logical volume for each clone of virtual machine.
That allows snapshots to actually works, because otherwise,
we would have to write content twice:
1. new cloned copy on disk
2. in snapshot (so that we see "old" copy)
This requires snapshot partition at least as big as filesystem
of cloned machine. It also slows down cloning.
The root of the problem is usage of vg logical volume both as source
(which we want to have snapshot of to achieve consistent copy)
and destination for new cloned fs. Creating new logical volume per
VE cloned allows easy management and update also.
But, this might be optional (and there is fallback in the codei
if there is no lvm for vz data) if we want to create another
persistant clone (TODO).
If possible, we will try to use ssync binary (which sadly
isn't packaged for Debian) because it's much faster than
rsync.
Revision
21 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Thu Oct 4 13:12:08 2007 UTC
(16 years, 8 months ago)
by
dpavlin
File length: 2263 byte(s)
Diff to
previous 20
,
to
selected 27
prepare and use temporary lvm snapshot while coping data,
annotate changed configuration variables,
new VE will have prefix 10 and first octet of IP adress 10.
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
enter a numeric revision.