Most of them areoutdated, but provide historical design context.
They arenotuser documentation and should not be treated as such.
Documentation is available here.
oVirt appliance will be a raw disk or an ova file that you can import to your existing virtual machine manager and boot it with a complete pre installed oVirt setup.
The first step will be to create an image with the correct functionality, in a second step the correct delivery format will be choosen. The latter might be currently blocked by the missing functionality in the build tools.
- Name: Fabian Deutsch (fabiand)
- Email: email@example.com
- Tracker https://bugzilla.redhat.com/show_bug.cgi?id=1053435
- Gitweb: http://gerrit.ovirt.org/gitweb?p=ovirt-appliance.git
Builds are stable, built daily, and based on latest oVirt 3.6 packages.
The last 3.5 build is still available, and master builds are available too.
- The appliance will be created using the livemedia-creator - later probably using image-factory.
- Reasoning behind this is, that these tools are maintained and support different platforms.
- The platform will be either Fedora or CentOS.
- Fedora for now.
- Engine installed and partially preconfigured
- It’s not built using livemedia-creator, sysprep’ed and sparsify’ed because libvirt is not working nicely on jenkins
Use / Test
- FQDN which can be resolved on your local network
To use the appliance proceed as follows:
- Download the ova image above
- Either use the ova in combination with hosted-engine or extract the ova image
- When the image is booted
- When the assistant comes up, set a root password
- Login as root
- Start the Engine configuration using:
engine-setup --offline --config-append=ovirt-engine-answers
- Answer the remaining questions, take care to use a FQDN which is resolvable on your network