Changes between Version 8 and Version 9 of how-to/puppet/dev-env

Timestamp:

Dec 4, 2012, 2:55:18 PM (13 years ago)

Author:

Jamie McClelland

Comment:

--

how-to/puppet/dev-env

@@ -19 +19 @@
 }}}
 
-== Setting up your directory structure ==
+== Setting up your Virtual Machine ==
 
-Be sure you have at least 2GB of space available on your disk.
+Be sure you have at least 2GB of space available on your disk and the qemu-kvm package installed.
 
-Here's a sample directory layout:
-
- * confdir - put the MFPL git repo here (e.g. `git clone gitosis@git.mayfirst.org/mfpl/puppet confdir`)
-
- * images - download [/special/roach.qcow.gz roach.qcow.gz] into your images directory. Don't gunzip right away! Instead, make a backup copy (so you don't have to re-download it if you mess it up), then gunzip it. [0]
- {{{
-cp roach.qcow.gz roach.qcow.bak.gz; gunzip roach.qcow.gz
- }}}
-
- * modules - this is where I git checkout puppet modules from other puppet developers before adding them to our repository.
-
-== Launching your virtual image ==
-
-Be sure you have the qemu-kvm package installed.
+The Debian Wiki has [http://wiki.debian.org/QEMU#Installation useful directions for installing Debian on a KVM image]. Or, to get going even faster, you can [http://people.debian.org/~aurel32/qemu/ download pre-build Debian stable images].
 
 You can start your virtual image with:
@@ -92 +79 @@
 
 
-=== Using a copy-on-write image ===
-Alternately, one can create a copy-on-write image to save only the changes made when working with a "base" image. The syntax is:
-{{{
-qemu-img create -b <path to base image> -f <image format> <path to copy-on-write image>
-}}}
-For the roach image, this would be:
-{{{
-qemu-img create -b images/roach.qcow -f qcow2 images/roach-changes.qcow2
-}}}
-Then one would use "images/roach-changes.qcow2" as the value of the -hda parameter when starting the virtual image.
+