Developer Installation Instructions

This document is intended to get developers quickly up and running with oVirt. It covers the development version of the oVirt appliance, which can only be used to work on the backend and web UI front-end. It cannot be used to manage physical hosts; if you want to manage physical hosts, you must install the bundled version of the appliance, using the instructions here. Nevertheless, the developer version is the fastest and most painless way to get oVirt up and running.

Throughout this document, we give commands to type at a shell prompt. By convention, if a command is meant to be run by a non-privileged user, we will precede it with a $ prompt. If a command is meant to be run by the root user, we will precede it with a #.

Pre-requisites

There a just a few prerequisites to getting the developer version running:

A machine that supports hardware virtualization. We will run a few KVM guests to simulate a production environment. This machine will be referred to as the "host machine" throughout the rest of the document. If you are familiar with different kinds of virtualization, you could use Qemu guests or Xen guests, but that is not covered here and the rest of this document will assume hardware virtualization.
Fedora 9 installed on the host machine with latest updates, kvm, libvirt, virt-manager and virt-viewer.
The Fedora 9 installation tree or boot ISO

Installation

Please read these directions entirely before you start; there are a couple of steps that are slightly different from a normal installation.

Using the pre-built appliance image
Please follow the instructions at Download page
Using GIT source repository
This procedure, recommended for developers modifying oVirt, uses pungi to create a local repository of required Fedora RPMs (<1GB) making subsequent rebuilds faster.
In your oVirt source repository clone
```
# ./build-all.sh -ac -d 
```
and proceed to step 3 below.
Using Fedora installation tree or boot ISO
1. Download create-wui-appliance.sh script onto the host machine.
2. Run this script as root; you can use pre-built appliance image or build the appliance from scratch if you point it at the location of your Fedora installation tree or boot ISO
  - Using Fedora installation tree (without boot ISO) NOTE replace download.fedora.redhat.com URL with your local mirror
```
# bash wui-appliance-create-wui-appliance.sh \
-t http://download.fedora.redhat.com/pub/fedora/linux/releases/9/Fedora/i386/os/ \
-k http://ovirt.org/download/wui-rel-i386.ks -v
```
    or
```
# bash wui-appliance-create-wui-appliance.sh \
-t http://download.fedora.redhat.com/pub/fedora/linux/releases/9/Fedora/x86_64/os/ \
-k http://ovirt.org/download/wui-rel-x86_64.ks -v
```
  - Using Fedora boot ISO
```
# bash wui-appliance-create-wui-appliance.sh -i /tmp/boot.iso -v
```
    virt-viewer screen pops up and when you see the boot screen, make sure to hit <Tab>, and then append ks=http://ovirt.org/download/wui-rel-x86_64.ks ksdevice=eth0 (for x86_64) or ks=http://ovirt.org/download/wui-rel-i386.ks ksdevice=eth0 (for i386) to the boot line.
3. After installation has finished, the guest should be rebooted to perform first-run setup. At the end of the boot process, you will see a message saying "Starting ovirt-dev-wui-first-run:". This command will take a while to finish, and is completely normal.
4. At this point, your appliance should be ready. Now, you can bring up the main oVirt screen by running firefox on the guest (here you'll need the root password, which is ovirt):
```
# ssh -fY root@192.168.50.2 firefox -no-remote
```
  To connect to the console of a virtual machine running on a managed node use:
```
# ssh -fY root@192.168.50.2 virt-viewer -c qemu+tcp://node3.priv.ovirt.org/system VM_NAME
```

Assuming all of the above worked, congratulations! You now have a working oVirt development setup. The next step is to start up some fake managed nodes. These will actually be additional KVM guests on the same host machine, but they will act as if they were separate physical nodes. Right now, you can use up to 3 fake managed nodes, named node3, node4, and node5. In order to use them, you just need to start the node in question:

# virsh start node3