18:00:22 <pboy> #startmeeting fedora-server
18:00:22 <zodbot> Meeting started Wed Dec 21 18:00:22 2022 UTC.
18:00:22 <zodbot> This meeting is logged and archived in a public location.
18:00:22 <zodbot> The chair is pboy. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
18:00:22 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:22 <zodbot> The meeting name has been set to 'fedora-server'
18:00:36 <pboy> #topic Welcome / roll call
18:00:45 <pboy> Welcome to our Server WG IRC meeting today!
18:00:55 <pboy> We'll give a few minutes for folks to show up
18:01:04 <pboy> Please, everybody who is lurking, say either .hello2 or .hello <fasname>
18:01:12 <pboy> I’ll post the agenda in a few minutes.
18:02:45 <jwhimpel> .hello2
18:02:46 <zodbot> jwhimpel: jwhimpel 'John Himpel' <john@jlhimpel.net>
18:03:03 <pboy> Hi John!
18:03:22 <jwhimpel> pboy: Good afternoon/evening to you
18:03:34 <cooltshirtguy> .hello2
18:03:34 <zodbot> cooltshirtguy: cooltshirtguy 'Jason Beard' <jas_beard@hotmail.com>
18:03:43 <pboy> It's evening here, 7 pm.  :-)
18:03:58 <pboy> Ho Jason
18:04:09 <pboy> We meet our quorum now. Great.
18:06:19 <copperi[m]> .hello copperi
18:06:20 <zodbot> copperi[m]: copperi 'Jan Kuparinen' <copper_fin@hotmail.com>
18:06:50 <pboy> Hi copperi!
18:06:58 <pboy> I think, we should start now.
18:07:09 <pboy> #topic Agenda
18:07:18 <pboy> #info 1. Follow up actions
18:07:26 <pboy> #info  2.  Using Ansible to install and configure Wildfly
18:07:33 <pboy> #info  3. Server WG work program for upcomming year
18:07:40 <pboy> #info  4.Open Floor
18:07:48 <pboy> Any additional topic / issue / comment ?
18:08:37 <pboy> I see none.
18:08:46 <pboy> #topic  1. Follow up actions
18:09:11 <pboy> We had still: eseyman and pboy will try hard to replicate and check the certificate issue in the next weeks
18:09:20 <pboy> I am still in debt to investigate the certificate problem with Wildfly.
18:09:26 <pboy> Big apology. I was just too full with different work. I hope for improvement.
18:09:47 <jwhimpel> Let me try another approach to solving my issue.
18:10:06 <pboy> I'll try hard to work on in in the first days of January.
18:10:06 <jwhimpel> I used to have a RHEL developer license, but I let it expire.
18:10:32 <pboy> jwhimpel Sounds good
18:10:36 <cooltshirtguy> I ran into a  "dict" issue with the playbook but just found a page to help fix it
18:10:59 <jwhimpel> If I reapply and am granted a RHEL developer license, I think I can use bugzilla on RHEL to ask questions.  Is that true.
18:11:42 <pboy> I suppose, but I'm not sure. Anyody around here who knows?
18:11:49 <cooltshirtguy> you can always renew your developer's license. I did mine a couple of months ago
18:12:18 <jwhimpel> The author of the blog entry I am following seems to have at one time headed the RedHat JBOSS team.  Perhaps someone here know how to contact her?
18:13:01 <jwhimpel> Her name is Farah Juma. (RH employee)
18:13:43 <eseyman> .hello2 eseyman
18:13:44 <zodbot> eseyman: eseyman 'Emmanuel Seyman' <emmanuel@seyman.fr>
18:14:01 <pboy> Hi eseyman!
18:14:12 <eseyman> sorry for the delay, folks. Traffic is pretty crazy today
18:14:13 <jwhimpel> I just need to figure out how to configure an ssl certificate in the wildfly.xml configuration file.  The syntax of the patch is shown, but where to apply the patch in wildfly.xml is not specified.
18:14:54 <eseyman> jwhimpel: yes, I too still need to look at your work
18:15:23 <pboy> Did you ask on our Fedora Java list?
18:15:38 <pboy> Some of the members are familiar with Wildfly.
18:15:44 <jwhimpel> If I can get by applying this patch, then I'm quite sure I can get wildfly up and running successfully and securely.
18:15:54 <pboy> One was to prepare a RPM, but gave up
18:16:18 <jwhimpel> I haven't tried pboy's suggestion, but will try asking on Java list later today.
18:17:25 <pboy> We have to people here who work with Wildfly. Unfortunately, they are quite busy.
18:17:47 <pboy> I'll try to contact them in January, wher they are back from Christmas leave
18:18:41 <pboy> I suppose, currently lost people are off
18:19:04 <pboy> So I think, we have to wait until 2nd half of January.
18:19:21 <pboy> lost -> most
18:19:23 <jwhimpel> There's a thread on groups.google.com/wildfly that says other people are also having issues getting ssl configured in wildfly 25.
18:19:43 <eseyman> jwhimpel: I should be able to take a look over the coming week when I am on vacation
18:20:42 <pboy> Hm, groups.google is non-public  members only
18:20:46 <cooltshirtguy> I'm just finishing up the install, then I'll see about the ssl
18:22:06 <pboy> I find the whole delay very unfortunate, especially that we have not been able to resolve this as a group so far.
18:22:14 <jwhimpel> coolshirtguy: Can you post on the mailing list, your issue with 'dict"?  I'll see what I can do to update my repo.
18:22:39 <cooltshirtguy> sure thing.
18:23:17 <ab> jwhimpel: bugzilla account does not require active RHEL developer license
18:23:17 <jwhimpel> I wonder if there are in fact many users of wildfly/jboss?  Perhaps I should look at the community versions of some of the commercial products?
18:23:41 <jwhimpel> s/commercial/other commercial/
18:24:12 <pboy> Wildfly / jBoss is one of the cash cows for RH, I think.
18:24:27 <pboy> There must be a solution.
18:24:36 <pboy> We have "just" to find.
18:25:27 <pboy> cooltshirtguy>
18:25:42 <pboy> cooltshirtguy  Will you start a thread on mailing list with your findings?
18:26:06 <cooltshirtguy> sure
18:26:33 <pboy> (Maybe sooner than I managed with our program discussion. :-).  )
18:27:21 <pboy> Anything else? Or should we proceed with next topic.
18:27:33 <jwhimpel> Let's move on
18:27:38 <eseyman> agreed
18:28:07 <pboy> #topic 3. Server WG work program for upcomming year
18:28:18 <pboy> #link https://pagure.io/fedora-server/boards/Works%20in%20progress
18:28:32 <pboy> Sorry for my late mail message.
18:28:57 <pboy> I didn't make it any sooner.
18:29:20 <eseyman> action eseyman take a look at the work program over the holidays
18:29:40 <pboy> #action eseyman take a look at the work program over the holidays
18:29:51 <pboy> (just for the log)
18:30:00 <eseyman> yes, that's better
18:30:35 <pboy> I suppose, the next step is to finally determine who will work on what.
18:30:57 <pboy> And than maybe to create a plan.
18:32:44 <pboy> I would like to continue working with the installation media after I have gained some experience with the VM.
18:33:01 <pboy> In addition to wildfly / Ansible
18:33:58 <pboy> Anyone else with specific plans?
18:34:20 <jwhimpel> I will continue to work on Ansible roles
18:34:29 <eseyman> I still want to focus on IM for the first half of 2023
18:35:28 <jwhimpel> eseyman: IM?
18:35:40 <eseyman> Identity Management
18:35:50 <pboy> #action jwhimpel will continue to work on Ansible roles
18:36:12 <jwhimpel> eseyman: Very good idea.
18:36:31 <cooltshirtguy> hehe idm
18:36:46 <pboy> #action eseyman wants to focus on Identity Management for the first half of 2023
18:36:49 <eseyman> I've seen both acronyms
18:37:28 <eseyman> along with IAM (identity and access management)
18:37:41 <cooltshirtguy> yea
18:38:25 <eseyman> what doesn't help is that IAM is a somewhat famous French rap band, which confuses a lot of people at first
18:38:45 <pboy> That's cool. :-)
18:40:16 <pboy> Anything else to bring up for this topic?
18:40:26 <pboy> Maybe we should give ourselves until January to discuss this on the Mailling list?
18:40:46 <cooltshirtguy> so we just pick something from the board to work on
18:41:09 <pboy> Basically yes.
18:41:19 <pboy> Of soemething complete new
18:41:25 <pboy> Of -Y Or
18:41:36 <pboy> (I need a new keyboard)
18:42:15 <cooltshirtguy> lol. okie dokie
18:42:15 <pboy> If it is something new, you should create an issue for it.
18:42:44 <pboy> Ok, so let's proceed with next topic.
18:43:02 <pboy> #topic 4. Open floor
18:43:27 <pboy> I have nothing at the moment.
18:45:01 <pboy> Obviously, nobody else has something.
18:45:17 <pboy> So we should close and start to prepare for Christmas?
18:46:02 <cooltshirtguy> sure thing
18:47:00 <eseyman> yes
18:47:35 <pboy> last thine: Will we cancel our first regular January meeting, January it is 4. ?
18:48:15 <pboy> I suppose, most of us are on holyday or still suffering from all the parties.
18:48:47 <pboy> Fo fest meeting would be January, 18.
18:49:03 <pboy> So first meeting ....
18:49:26 <cooltshirtguy> sounds good.
18:50:32 <pboy> #agreed January 18. will be the first meeting in 2023.
18:50:41 <eseyman> okay
18:51:02 <pboy> So, I wish everybody a happy Christmas and a good New Year.
18:51:15 <pboy> And meet you Janurary 18.
18:51:17 <pboy> again
18:51:33 <pboy> #endmeeting