Some additional remarks
just for convenience: KAMI911 wildfly:
https://github.com/KAMI911/ansible-role-wildfly-configuration
Unfortunately, documentation is a bit on the sparse side.
One topic we have to address is installation location.
Fedora Server’s default partitioning is separation of system and data. Therefore, Fedora
Server default partitioning allocates only max. 15 G for system and leaves the rest of a
volume group free /unallocated. With an RPM package, one would do as Tomcat does, for
example, and link the webapps directory to /var/something as provided by FSH. With an
installation of the binary package this might be difficult.
I found another GitHub Wildfly installation project: serdar/jcliff
(
https://github.com/bserdar/jcliff) It combines ansible with a Java program (Jcliff) that
facilitates configuration of Wildfly and especially orchestration / installation of web
applications (third party project:
https://github.com/ansible-middleware/3trains-cluster-demo) /installation and
configuration of database drivers (a separate project,
https://github.com/ansible-middleware/wildfly-jdbc-driver ), all of them using jcliff.
Peter
Am 12.08.2021 um 21:23 schrieb John W. Himpel
<john(a)jlhimpel.net>:
All,
At our last Server WG meeting, I volunteered to write-up requirements for installing
wildfly. Unfortunately, some
health issues last weekend got in the way, but everything seems back to normal now.
I managed to locate an ansible role on github by KAMI911 called ansible-role-wildfly. It
comes reasonably close to what
I would envision the Server WG to publish and support. It is helping me to formulate a
list of requirements.
ansible-role-wildfly supports an older version of wildfly and doesn't play too well
with systemd. But it has a lot of
good things that do work.
I am in the process of trying to support the most recent version of wildfly and to
properly interface with systemd. If
I am lucky, it should be able to support simultaneous installations of different version
of wildfly. I also need to
strip out the installation of the java JDK from this role and put that into it's own
role.
All my previous experience with JEE servers has been with WebSphere and WebLogic.
Wildfly uses a very different java
classloading system. So when I finish my work from above, I will try to use one of
RedHat tutorials to write, build,
deploy and test the wildfly setup.
I am not familiar with the Continuous Integration setup on github. The
ansible-role-wildfly has several directories
full of configuration and testing stuff to interface with CI on github. Perhaps when I
finish my work, someone else can
implement the CI stuff.
I will try to publish a basic requirements document for Server crafted and supported
roles either sometime next week or
the following week.
That's all for now.
_______________________________________________
server mailing list -- server(a)lists.fedoraproject.org
To unsubscribe send an email to server-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure