I got responses in IRC to my questions.
A very nice person - Mburns basically answered all my questions - I had
asked about SWRAID for the nodes too
As always i'm amazed how easy it is to get answers in the opensource world
Many thanks to everybody involved !
12:36] <mburns> morgan: support life: it's an open project so support is
just community support
[12:36] <mburns> i haven't heard anything around how we're going to handle
OS upgrades at this point
[12:37] <mburns> but i would think that each ovirt release will be on the
current versions of the different distros
[12:37] <mburns> morgan: regarding nodes, if you're using ovirt-node, then
it's fedora only currently
[12:38] <mburns> there is work being done to be able to create
clients/slaves on different distros, but not as part of the node project
[12:38] <mburns> though we'd love for people who know those distros to help
out creating variants of the node for each
[12:39] <-- ydary has left this server (Quit: Leaving.).
[12:39] <mburns> morgan: upgrading the node: the way the node is designed,
upgrades are fairly easy and non-destructive
[12:40] <mburns> the base image is dropped in and the configuration and
shared data aren't touched
[12:40] <mburns> morgan: no support for swraid in the node at this time
[12:41] <mburns> morgan: i don't think it's really needed either
[12:42] <mburns> there is minimal configuration to be made on the node, so
re-installation in the case of a lost disk is pretty simple
[12:42] <mburns> the bigger deal is the storage for your datacenters
[12:42] <mburns> and if you're using nfs/iscsi/fc, you definitely want raid
of some sort there
1. Do we have to use Fedora16 for the nodes ? Or can be build a node on any
2. If the node is also doing the storage (i.e LVM) - when we upgrade Ovirt
to the next version how will be keep the data ?
I'm trying to install the new oVirt packages on a fresh minimal
install of Fedora as described on http://www.ovirt.org/get-ovirt/.
I'm getting the following error when trying to run:
sudo yum install -y ovirt-engine
Error: Package: ovirt-engine-jboss-deps-3.0.0_0001-1.6.fc16.x86_64
Has anyone been successful in installing the ovirt-engine Fedora packages?
oVirt's setup procedure seems to insist reverse DNS records are present.
When running engine-setup interactively, you are able to override this,
but with automated installations it flat outs refuses to install:
[root@ovirt ~]# engine-setup --answer-file=answers
Welcome to oVirt Engine setup utility
The IP 192.168.88.102 does not hold a PTR record for the FQDN:
Failed handling answer file: Error reading parameter HOST_FQDN from
Kinda annoying requirment, when you only want to create a quick test setup.
Was wondering where it is actually using reverse DNS for?
> The biggest challenge is that pieces of the oVirt project require there
> to be persistent storage locally. For example, when you register a node
> with the engine, a manual step is required to approve the node. After
> this manual step, some certificates are copied locally into the node and
> stored. That way, the node can immediately identify itself with the
> engine and start working with no need to identify itself.
> To solve this problem, we need to either
> 1. remove the need to store stuff locally
> 2. provide some way to package up this config and store it somewhere,
> then retrieve on boot
> 3. embed some sort of key or certificate in the pxe image that allows
> the engine to know that this valid machine and automatically approve it.
Is there a method to pre-generate a set of certificates/configuration
files for a node?
It is not that hard to let the boot server serve the node-specific
configuration files as a cpio (initramfs) archive, based on the
MAC-address of the node.
The kernel supports having more than one initramfs file, and simply
combines the files from both archives.
I am looking at how I might go about importing a mixture of existing
VMs into oVirt.
There doesn't appear to be any obvious way of doing this so I am
assuming it should be done manually.
If I where to create a raw disk image of my existing KVM virtual
machines how would I then go about importing this?
I can see on a node running a VM that there are two files in the
images folder associated with it. These appear to be the disk image
and a meta file containing configuration options for the VM.
Would the best way to go about this be to create a VM with the options
I require in oVirt and power cycle it so these files are created then
replace the disk image with my one, preserving the file name (which I
assume is the VMID).