On Mon, Jan 23, 2012 at 12:02:05PM +0100, Christian Parpart wrote:

Hi all,

as suggested in a prior mail, I was now trying out oVirt - however, on
a non-Redhat/Debian system -
and ran into huge issues primary due to the lag of information / documenation.

So here my assumptions:
* oVirt is a web application based on JBoss application server.
* VDSM is an agent to run on every hypervisor (or also VM?)
* nothing else needed? (despite jboss, java-jdk-1.6, python-2.7, maven-2.2)

I tried following the install-from-source guides for oVirt and failed at
a compilation error.

# cd $OVIRT_ENGINE_SRCDIR
# make
[.....]
[INFO] Compiling 186 source files to
/opt/ovirt/src/ovirt-engine/backend/manager/modules/dal/target/classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
/opt/ovirt/src/ovirt-engine/backend/manager/modules/dal/src/main/java/org/ovirt/engine/core/dal/dbbroker/PGHack.java:[9,7]
error: PGHack is not abstract and does not override abstract method
getParentLogger() in CommonDataSource
[...]

There are no remote branches nor tags that looked like "stable" that I
could test on, too.

So finally (the not favoured version), I tried putting a Fedora 16
netinstall into a KVM on my hypervisor-test-node
and installed everything in there, again, following some guide from
the upstream site.

Since it did not compile anything, the install worked well, but I
could not add my hypervisor node
as a host, in fact, it complained about some tools not being able to
be installed.

What tools? VDSM? how am I supposed to "cleanly" install it if not as
promoted on the install guide? :(

In the end, I am having nothing working, feeling a little bit sad
about the possibly wasted time, so I hope you guys can give me a
hint on how to deal with VDSM (if that's what I am missing here) and
how to deal with the compile error when installing from source.

Hi Christian,

I am not primarily an ovirt guy, so I hope I am not steering you wrong
here, but since I was the one who made the suggestion that you try
ovirt, I'll take a swag at it.  oVirt requires that KVM be operational
on the node, so you may be running up against that requirement if you
aren't running nested virt.  I have gotten a VM to work as a node, but
I did have to make it nested, and my experience with nested KVM is
that it still has some rough edges.

I have cc'd the ovirt users list as I do not have the experience to
help you debug the build failure.

Dave

Best regards,
Christian Parpart.

_______________________________________________
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users