Again, for everyone's convenience, a brief summary of our IRC meeting right here.
For greater details see meetbot Summary: https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-02-... Full log: https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-02-...
Topics discussed:
=== Follow up actions === #info Late change proposal cockpit file-sharing update submitted
=== Current status of Fedora Server User Docs Update === We still suffer from missing reviews and missing reviewer for some new docs. The Backlog is 8 docs waiting for (re)publishing, some meanwhile already 8 weeks.
AGREED: Regarding doc: Assume that "no complaints == no issues" and just publish today.
=== Using Ansible to install and configure Wildfly === John Himpel (jwhimpel) managed to create an Ansible configuration script to get wildfly running with a nginx reverse-proxy in front of it (stand-alone mode). It’s not accessible from the internet due to network issues.
Next step agreed upon: establish an accessible version. pboy will assist jwhimpel.
To be noted: jwhimple’s efforts are the first of our 5 technical work projects that have reached a runnable status.
=== Review current Fedora Server Technical Specification ===
We have agreed do define a set of „provided services“ as an replacement for server roles. Examples are PostgreSQL, IPA (both already there), Web Service, Application server (Wildfly), DHCP, DNS, Mail, etc. Support should/will be provided by Ansible reflecting the general Fedora Server infrastructure (e.g. file system rationale).
A question to be pursued further is what function the dbus API should have had for/in the server roles at the time.
Agreed: pboy and eseyman will create a first draft of an updated technical specification as discussed until today. Next discussion in about 4 weeks.