Currently the engine runs inside JBoss AS 7.1.1, which was released back in 2012 and didn't get any update since then. It has given good service, but it is time to update to WildFly 8, specially in order to unlock the potential of using CDI in all the components of the engine. This update won't require big changes to most of the code, except in the following areas: 1. In the RESTAPI, where we are using some internal Resteasy classes. Those have mostly been solved already, replacing the internal Resteasy classes with standard ones. 2. In the script and configuration files used to start the application server. I think that we can do this for the 3.6 release.
The following patch contains the changes needed in the script and configuration files used to start the application server: http://gerrit.ovirt.org/21413 It is currently work in progress, but it is already usable.
For RPM distributions where WildFly 8 isn't packaged we will need to package it or provide a simple re-packaging of the .zip distribution, like we currently do with JBoss AS 7: http://gerrit.ovirt.org/30223
Created attachment 919244 [details] Patch to work around Hibernate Validtor bug HV-861 Currently Hibernate Validator has a bug that prevents deployment of the backend: https://hibernate.atlassian.net/browse/HV-861 In order to work this around I had to apply the attached patch and rebuild it.
Note that once the Hibernate Validator bug is fixed, the version included in WildFly has to be updated, and that won't be backported, so it won't happen before WildFly 8.3: https://issues.jboss.org/browse/WFLY-4280
Wildfly builder job created: http://jenkins.ovirt.org/search/?q=ovirt-engine-wildfly
Currently the plan is to support that in 3.6.0, making sure it doesn't break compatibility, while still supporting EAP. Research required on that. Assigning to Martin to do this research, hoping the result won't require delaying this.
(In reply to Oved Ourfali from comment #6) > Currently the plan is to support that in 3.6.0, making sure it doesn't break > compatibility, while still supporting EAP. Research required on that. > Assigning to Martin to do this research, hoping the result won't require > delaying this. what about the bug mentioned in comment #4? how is that handled?
(In reply to Roy Golan from comment #7) > (In reply to Oved Ourfali from comment #6) > > Currently the plan is to support that in 3.6.0, making sure it doesn't break > > compatibility, while still supporting EAP. Research required on that. > > Assigning to Martin to do this research, hoping the result won't require > > delaying this. > > what about the bug mentioned in comment #4? how is that handled? Probably adding a module with the updated version, and ship it.
the module is hibernate-validator and is has its own dependency tree. that will create a very broken dep tree for that RPM. the intention is to pack jboss for ovirt?
(In reply to Roy Golan from comment #9) > the module is hibernate-validator and is has its own dependency tree. that > will create a very broken dep tree for that RPM. the intention is to pack > jboss for ovirt? No. We are testing it now. I guess Martin will let us know what he found and we'll proceed from there.
The following Undertow issue may block this: AJP connector discards anything after the first ";" in the request URL https://issues.jboss.org/browse/UNDERTOW-477
Stuart Douglas <stuart.w.douglas> updated the status of jira UNDERTOW-477 to Resolved
Martin, apparently this was solved in version 1.1.4.Final of Undertow, so you may want to try that version and, if it works, include it in the overlay package.
ovirt-3.6.0-3 release
oVirt 3.6.0 has been released, closing current release