Diff for "Running/LXC"

Not logged in - Log In / Register

Differences between revisions 1 and 14 (spanning 13 versions)
Revision 1 as of 2010-05-24 23:55:17
Size: 1063
Editor: lifeless
Comment: create
Revision 14 as of 2011-06-21 23:41:55
Size: 2930
Editor: lifeless
Comment: more
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This page explains how to set up and run Launchpad (for development) inside a VM. ## page was copied from Running/VirtualMachine
This page explains how to set up and run Launchpad (for development) inside a LXC.
Line 5: Line 6:
Launchpad development setup makes numerous changes to your machine; its nice to be unaffected by those except when you are actually doing such development. Launchpad development setup makes significant changes to your machine; its nice to be unaffected by those except when you are actually doing such development.
Line 7: Line 8:
Also, launchpad has limitations on concurrent testing per-machine and so forth - multiple VM's can be used to work around this. Also, launchpad has some limitations on concurrent testing per-machine and so forth - multiple container's can be used to work around this.
Line 10: Line 11:
= Make a VM image = = Make a LXC =
Line 12: Line 13:
 1. Install KVM  1. Install lxc
Line 15: Line 16:
% sudo apt-get install virt-manager sudo apt-get install lxc
Line 18: Line 19:
 1. Work around Bug:800456
{{{
sudo apt-get install cgroup-bin
}}}

 1. Work around Bug:784093

{{{sudo dd of=/etc/cgconfig.conf << EOF
mount {
 cpu = /sys/fs//cgroup/cpu;
 cpuacct = /sys/fs/cgroup/cpu;
 devices = /sys/fs/cgroup/cpu;
 memory = /sys/fs/cgroup/cpu;
}
EOF
}}}

 1. Create a container
{{{
% sudo lxc-create -n lucid-test-lp -t lucid -f /etc/lxc/basic.conf
}}}
Line 32: Line 54:
 1. ssh -A <vm IP address> to connect to the VM. You can now follow the [[Getting|getting-started]] on LP instructions.  1. ssh -A <vm IP address> to connect to the VM.

 1. {{{bzr whoami "Your Name <your.email@example.com>"}}} to set your bzr identity in the VM.

 1. You can now follow the [[Getting|getting-started]] on LP instructions.

= References =

See also this email thread about [[https://lists.launchpad.net/launchpad-dev/msg03456.html|running Launchpad in a virtual machine]], and this [[https://lists.launchpad.net/launchpad-dev/msg03454.html|discussion of the differences]] between running in a [[Running/Schroot|chroot]] environment and running a VM. [[Running/RemoteAccess]] has a discussion for how you can configure the VM to allow the host machine to access the web pages, etc.

= Alternatively =

You can skip some manual steps of installing from an ISO using a command like this:

{{{
sudo ubuntu-vm-builder kvm lucid --domain vm --dest ~/vm/lp-dev \
 --hostname lp-dev \
 --mem 2048 --cpus 2 \
 --components main,universe,multiverse,restricted \
 --mirror http://10.113.3.35:3142/mirror.internode.on.net/pub/ubuntu/ubuntu \
 --libvirt qemu:///system \
 --debug -v \
 --ssh-user-key ~/.ssh/id_rsa.pub --ssh-key ~/.ssh/id_rsa.pub \
 --rootsize 24000 \
 --user $USER
}}}

After installation completes, it should show up in your virt-manager menu.

= In LXC =

It seems like it would be nice to run Launchpad in [[http://lxc.teegra.net/|LXC containers]]: they should be more efficient than a VM (especially with regard to memory and disk) but more isolated than a chroot. More testing or documentation is needed.

This page explains how to set up and run Launchpad (for development) inside a LXC.

Why?

Launchpad development setup makes significant changes to your machine; its nice to be unaffected by those except when you are actually doing such development.

Also, launchpad has some limitations on concurrent testing per-machine and so forth - multiple container's can be used to work around this.

Make a LXC

  1. Install lxc

sudo apt-get install lxc
  1. Work around 800456

sudo apt-get install cgroup-bin
  1. Work around 784093

{{{sudo dd of=/etc/cgconfig.conf << EOF mount {

  • cpu = /sys/fs//cgroup/cpu; cpuacct = /sys/fs/cgroup/cpu; devices = /sys/fs/cgroup/cpu; memory = /sys/fs/cgroup/cpu;

} EOF }}}

  1. Create a container

% sudo lxc-create -n lucid-test-lp -t lucid -f /etc/lxc/basic.conf
  1. Download the Lucid server ISO
  2. Run virt-manager.
  3. Double click on localhost(QEMU)
  4. click on the New virtual machine icon
  5. follow your nose here, using the ISO as the install media, and allocating no less than 2G of disk and 1G of memory. I suggest 4G if you can spare it.
  6. After its installed, connect to the image and install acpid and openssh-server

  7. Use ssh-copy-id to copy your public key into the VM.
  8. ssh -A <vm IP address> to connect to the VM.

  9. bzr whoami "Your Name <your.email@example.com>" to set your bzr identity in the VM.

  10. You can now follow the getting-started on LP instructions.

References

See also this email thread about running Launchpad in a virtual machine, and this discussion of the differences between running in a chroot environment and running a VM. Running/RemoteAccess has a discussion for how you can configure the VM to allow the host machine to access the web pages, etc.

Alternatively

You can skip some manual steps of installing from an ISO using a command like this:

sudo ubuntu-vm-builder  kvm lucid --domain vm --dest ~/vm/lp-dev \
 --hostname lp-dev \
 --mem 2048 --cpus 2 \
 --components main,universe,multiverse,restricted \
 --mirror http://10.113.3.35:3142/mirror.internode.on.net/pub/ubuntu/ubuntu \
 --libvirt qemu:///system \
 --debug -v \
 --ssh-user-key ~/.ssh/id_rsa.pub --ssh-key ~/.ssh/id_rsa.pub \
 --rootsize 24000 \
 --user $USER

After installation completes, it should show up in your virt-manager menu.

In LXC

It seems like it would be nice to run Launchpad in LXC containers: they should be more efficient than a VM (especially with regard to memory and disk) but more isolated than a chroot. More testing or documentation is needed.