/[vz-tools]/trunk/vz-clone.pl
This is repository of my old source code which isn't updated any more. Go to git.rot13.org for current projects!
ViewVC logotype

Log of /trunk/vz-clone.pl

Parent Directory Parent Directory | Revision Log Revision Log


Links to HEAD: (view) (annotate)
Sticky Revision:

Revision 27 - (view) (annotate) - [select for diffs]
Modified Thu Oct 4 23:42:24 2007 UTC (16 years, 6 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, 6 months ago) by dpavlin
File length: 4347 byte(s)
Diff to previous 25
clone lv are now always named vz-clone-10VEID and not
dependent on OpenVZ lv name

Revision 25 - (view) (annotate) - [select for diffs]
Modified Thu Oct 4 23:19:33 2007 UTC (16 years, 6 months ago) by dpavlin
File length: 4354 byte(s)
Diff to previous 24
new syntax: subcommands create, umount and destroy

Revision 24 - (view) (annotate) - [select for diffs]
Modified Thu Oct 4 18:54:41 2007 UTC (16 years, 6 months ago) by dpavlin
File length: 3651 byte(s)
Diff to previous 23
rsync know how to handle device and special files, ssync doesn't.
So it's out...

Revision 23 - (view) (annotate) - [select for diffs]
Modified Thu Oct 4 16:58:01 2007 UTC (16 years, 6 months ago) by dpavlin
File length: 3794 byte(s)
Diff to previous 22
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 22 - (view) (annotate) - [select for diffs]
Modified Thu Oct 4 13:19:26 2007 UTC (16 years, 6 months ago) by dpavlin
File length: 2342 byte(s)
Diff to previous 21
hint how to add NAT rule for cloned VE

Revision 21 - (view) (annotate) - [select for diffs]
Modified Thu Oct 4 13:12:08 2007 UTC (16 years, 6 months ago) by dpavlin
File length: 2263 byte(s)
Diff to previous 20
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.

Revision 20 - (view) (annotate) - [select for diffs]
Added Thu Oct 4 11:30:05 2007 UTC (16 years, 6 months ago) by dpavlin
File length: 903 byte(s)
a simple script to create clone of VE

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.

  Diffs between and
  Type of Diff should be a

  ViewVC Help
Powered by ViewVC 1.1.26