11:46 a.m.
Hi all,
Today I tried running engine on my Fedora 21 laptop. I tried two
approaches for deploying jboss: using the ovirt-jboss-as package, and
by downloading and unpacking jboss-7.1.1 into /usr/share as I have
done in the past. engine-setup runs without errors but when I try to
start engine the application does not seem to deploy in jboss and
there are no errors reported (engine.log is empty).
Is there a reasonable expectation that I should be able to get this
working on F21 or am I wasting my time? Does anyone have any ideas
on how I can resolve the startup issues?
See logs attached...
--
Adam Litke
1:18 p.m.
----- Original Message -----
Which Java version did you try to use it with?
Did you have a look at [1]? In short: won't be, wait for f22.
[1] http://www.ovirt.org/Features/Fedora_21_Support
--
Didi
1:30 p.m.
On 29/01/15 16:18 -0500, Yedidyah Bar David wrote:
java-1.8.0-openjdk-1.8.0.31-3.b13.fc21.x86_64
Did you have a look at [1]? In short: won't be, wait for f22.
Yeah, didn't see much documentation of specific issues and the tracker
bug looks pretty clean as far as general engine usability goes.
--
Adam Litke
1:49 p.m.
----- Original Message -----
Thanks for trying this, Adam, as I've been thinking of upgrading to F21
very soon.
Asking people to wait for Fedora 22 is not user-friendly and IMHO not good
for the project. When 20 came out, it worked out of the box (with the
--jboss-home caveat.)
I'll try this out this weekend and report back.
Sandro, if you can offer any help, that would be great.
Greg
2:53 p.m.
----- Original Message -----
AFAIK our code and/or jboss 7.1 are not compatible with java 1.8.
It might work with openjdk 1.7, if one is shipped in f21 or installed using some other
means.
Sandro, if you can offer any help, that would be great.
As you can see from the wiki [1] and the links from it (to other wiki pages
and bugzilla bugs), Sandro is already tracking this.
Obviously, the proper solution will be that some Java developers will fix ovirt
to work with java 1.8 and with wildfly. Not sure what this means in practice.
openjdk 1.7 is soon eol, so even if it works, we'll eventually have to bite the
bullet and migrate.
I am replying mostly because I guess Sandro will not read email until Monday...
[1] http://www.ovirt.org/Features/Fedora_21_Support
--
Didi
10:56 p.m.
Il 29/01/2015 22:30, Adam Litke ha scritto:
Everything should be installable right now in F21 but jboss-as 7.1 doesn't work with
java 1.8.
We'll need to move to wildfly or backport java7 in order to make it working.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
4:55 a.m.
On 02/02/2015 07:56 AM, Sandro Bonazzola wrote:
Alternatively, if it is for development purposes only, you may want to
consider using JBoss EAP 6.x instead of JBoss AS 7.1.1. The root cause
of the incompatibility has been fixed there (and in WildFly):
https://issues.jboss.org/browse/WFLY-2057
You can get JBoss EAP from here:
http://www.jboss.org/products/eap/download
Then you can unzip it to your favorite directory and use it during
installation of oVirt Engine:
# engine-setup --jboss-home=/whatever/jboss-eap-6.3
It should work well with Java 8. If it doesn't work it is good to know,
as we will need to fix it eventually.
--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
1:20 a.m.
On 02/03/2015 12:28 AM, Adam Litke wrote:
I work with F21 currently by installing Oracle jdk 7 rpm (download from
oracle site)
then use 2 env variables to make ovirt work with it:
export OVIRT_ENGINE_JAVA_HOME=/usr/java/jdk1.7.0.75
export OVIRT_ENGINE_JAVA_HOME_FORCE=1
and use the regular jboss-as-7.1.1 from tar.gz
the only problem found currently is with creating the engin.p12 key
during setup [1]
the workaround is to copy any other working engin.p12 from previous
setup you had
the engine.p12 file is under etc/pki/ovirt-engine/keys/engine.p12
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1193776
1:07 a.m.
Il 02/02/2015 13:55, Juan Hernández ha scritto:
Juan, can you package EAP 6.4 beta from above link for testing on 3.6/master as you did
for AS?
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
1:45 a.m.
On 02/16/2015 10:07 AM, Sandro Bonazzola wrote:
The use of the binaries available there is subject to the "JBoss
Developer Program" subscription agreement:
http://www.jboss.org/faq
I am not a lawyer, but my understanding is that if we re-distribute
those binaries we would be in violation of the agreement. So even if
technically packaging those binaries is a piece of cake, I think that we
can't re-distribute them.
--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
1:57 a.m.
Il 16/02/2015 10:45, Juan Hernández ha scritto:
Ok, what about packaging building from sources?
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
2:26 a.m.
On 02/16/2015 10:57 AM, Sandro Bonazzola wrote:
The sources of JBoss EAP are available in ftp.redhat.com, like any Red
Hat sources. But building them is nearly impossible, because the EAP
sources depend on versions of other components that aren't available in
maven central or any other public maven repository. You can manage to
find the required versions of the sources of those components, but it
would be a huge task.
--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.
3759
days inactive
3779
days old
16 comments
7 participants
participants (7)
-
Adam Litke -
Barak Azulay -
Greg Sheremeta -
Juan Hernández -
Roy Golan -
Sandro Bonazzola -
Yedidyah Bar David