On 01/23/2012 05:53 PM, Dave Allan wrote:
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
> [...]
I think this build problem is happening because you are using JDK 7,
which added a new method to the CommonDatasSource interface. You could
implement it, but I think it is better if you compile with JDK 6, as
that is the version that has been tested.
> 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.
Using VDSM with Debian is going to be difficult, I think, as it is quite
Fedora specific right now. With Fedora it shouldn't be very hard. What
are the specific problems that you are facing?