server August 2021

server@lists.fedoraproject.org

9 participants
15 discussions

[Fedocal] Reminder meeting : Fedora Server WG
by michel＠michel-slm.name 31 Aug '21

31 Aug '21

Dear all, You are kindly invited to the meeting: Fedora Server WG on 2021-09-01 from 17:00:00 to 18:00:00 UTC At fedora-meeting(a)irc.libera.chat The meeting will be about: Standing meeting of the Fedora Server working group See [mailing list](https://lists.fedoraproject.org/archives/list/server@lists.fedoraproj… for agenda Local time information (via [uitime](https://github.com/james-antill/uitime)) ❯ ./uitime --width 48 --short US/Pacific,US/Eastern,Europe/Berlin '2021-07-07 17:00 UTC' ================ Day: Wednesday ================ 2021-07-07 10:00 PDT --> US/Pacific <-- 2021-07-07 13:00 EDT US/Eastern 2021-07-07 17:00 UTC UTC 2021-07-07 19:00 CEST Europe/Berlin More information available at: [https://fedoraproject.org/wiki/Server](https://fedoraproject.org/wiki/Serve… Source: https://calendar.fedoraproject.org//meeting/10017/

1 0

Call for agenda Items on 2021-09-01 17:00 ==UTC== meeting
by Peter Boy 27 Aug '21

27 Aug '21

Our next IRC meeting is scheduled for =============================================================== Fedora Server IRC meeting Wednesday, September 01 17:00 ==UTC== irc.libera.chat #fedora-meeting =============================================================== Currently I'm aware of the following agenda items == Agenda == 1. Follow up actions 2. Max size arm-32 exceeded, install media blocked 3. Facilitated deployment of key services by combining rpm and Ansible 4. Open Floor Please, check if there are additional topics to be dealt with. Ad 1. INFO: Long running open actions / agreed Wednesday, July 21, 2021 • ACTION: langdon to file a ticket with qe team to ask for a test day for libvirt STATUS: Followup in progress Wednesday, July 07, 2021 • ACTION: Eighth_Doctor tries to find someone run a test compose with recommendations STATUS:OPEN • AGREED: Eighth_Doctor, nirik and langdon will look for a solution to the compose question Wednesday, April 28, 2021 • ACTION: : Eighth_Doctor checks the size of an install image including all recommends. Ad 2: See https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… Ad 3: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or…

1 0

guest agent step in the installer
by Łukasz Posadowski 26 Aug '21

26 Aug '21

Hello. Recently someone told me, that he expected a guest agent installed by default on Fedora Server. There is an option in the software selection, but maybe it could be more exposed. Like this: https://wiki.baszarek.pl/lib/exe/fetch.php?media=guest.jpg I'm checking how anaconda module is structured. I think guest addition can be auto-detected, based on lscpu, or similar program. thanks -- Łukasz Posadowski

2 1

Some guideline for installing services on Fedora Server from WG provided ansible roles
by John W. Himpel 23 Aug '21

23 Aug '21

All, I am putting this out there as a strawman for discussion purposes. It does reflect my current efforts to install Wildfly which is not available via rpm. Comments and criticisms are welcome: I would propose the following: 1. Ansible Repository. 1. The Fedora Server Working Group create and maintain a repository of Ansible playbooks to download and install various applications that are specifically aimed at the server community. 2. Investigate possible use of ansible-galaxy. 2. The playbooks should use Fedora provided rpms for applications and their components wherever possible. 3. The use of ansible roles is strongly encouraged. 4. In the case of certain java applications, downloading of sources/binaries/jars from trusted repositories (i.e. wildfly.org, mvnrepository.com, etc) inside of Ansible playbooks be allowed when Fedora rpms are not available. 5. In accordance with Fedora Open Source policy, only software with Fedora approved licenses may be downloaded. 6. Unless dictated by Fedora policy, the playbook should install non-rpm artifacts under the /opt directory. 7. Where possible, services should be controlled via systemd. 8. Playbooks should be developed to install, configure, start, stop, enable, disable, open firewall, close firewall and remove (with or without application data) an application or service. 9. Applications with many add-ons, extensions or cooperating services should have each add-on, extension or cooperating service managed in a separate playbook. Use case: 1. Wildfly 1. Install the most recent LTS version of java from rpm. 2. Download the most recent LTS wildfly application from https://download/jboss.org. 3. Install the new wildfly application binaries. 1. under the /opt directory (directory structure TBD). 2. versioned to allow for simultaneous versions being installed. 4. Make any necessary modifications to the configuration files. 5. The following could be one playbook with multiple “tags”. 1. Install any necessary service/timer/etc files used by systemd to manage the application. 2. Remove any necessary service/timer/etc files used by systemd to manage the application. 3. Start the application via systemd. 4. Enable the application via systemd. 5. Stop the application via systemd. 6. Disable the application via systemd. 7. Mask the application via systemd. 8. Unmask the application via systemd. 6. The following could be one playbook with multiple “tags”. 1. Define service to be managed by firewalld. 2. Open ports for the service via firewalld. 3. Close ports for the service via firewalld. 7. Allow for standalone and domain versions of wildfly 8. CI to verify starting of a working instance of Wildfly 9. Simplify user documentation: 1. Ansible installation 2. Ansible inventory configuration 3. Required changes in vars and default directories I did a few searches and found an ansible playbook on github called KAMI911/ansible-role-wildfly. Ansible-role-wildfly is currently architected to run on either RedHat Enterprise Linux (v6 & v7). It also uses Java 8 instead of Java 11 (current LTS of java) and it uses wildfly v20.0.1 and the current version of wildfly is 24.0.1. It does not fully support systemd. Since Fedora 34 is newer than RHEL v6 & v7, it is my uninformed opinion the playbook needs some work to eliminate some of the no-longer-supported features of Wildfly and RHEL. Fortunately all of these things are fixable. Ansible-role-wildfly is licensed under the terms of the MIT / BSD, so it is freely redistributable with Fedora. Ansible-role-wildfly also contains tasks and configuration that allow for Continuous Integration testing. I’ve never attempted that before, so I will leave evaluation of that functionality to someone better qualified than I. After some modifications to the playbook, I have installed a wildfly “standalone” instance on a Fedora 34 Server (netinstall). Almost all of the changes that I have made so far, are to allow wildfly to run under the control of systemd. Wildfly will start. All my experience with JEE is based upon WebLogic and/or WebSphere. Unfortunately, my web app is configured to run under Weblogic, and would need considerable work to migrate to Wildfly. During the next week or so, I will attempt go get a proof-of-concept application deployed and running. I could use assistance from someone familiar with configuring Wildfly to advise me about a good way to configure Wildfly for a very basic setup and what configuration of older functionality can be removed from the playbook.

2 2

Federa Server Edition armhfp installation iso issue
by Peter Boy 21 Aug '21

21 Aug '21

There is a bug against the Federa Server Edition armhfp installation iso see https://bugzilla.redhat.com/show_bug.cgi?id=1963007 The F35 build exceeds the current max size of 700 mb (by about 20 mb) There are obviously 2 options: (a) reduce the size by removing some packages (b) Determine a new max size Unfortunately I’m not familiar with Fedora build process. According to my work with aarch64 server iso the arm build is a splendid materialization of the current concept of Fedora Server Edition. Therefore, I'm hesitant to remove packages. I would also have no idea which ones could be dispensable. Therefore, from a user/admin perspective, I would opt to set 750 as the new maximum size. But I don't oversee the technical side. So I ask our technically savvy members to take up the cause. I’ll ask on the arm list, too. Unfortunately, there is now a longer delay because I was not aware that this is a matter of the server WG and I was considered a contact. We should now try to get clarification as quickly as possible.

3 4

Short info about today's IRC meeting (2021-08-18)
by Peter Boy 18 Aug '21

18 Aug '21

Again, for all of us lazy people, a brief summary right here. For greater details see meetbot Summary: https://meetbot.fedoraproject.org/fedora-meeting/2021-08-18/fedora-server.2… Full log: https://meetbot.fedoraproject.org/fedora-meeting/2021-08-18/fedora-server.2… Topics discussed: === Follow up actions === 1. TASK: Server docs: Our pages got published today on docs start page. All regarding actions closed now. 2. TASK: Ansible/Wildfly (2021-08-04) ACTION: jwhimpel will write a first draft how to handle the wildfly example case for discussion next meeting. Status DONE 3. TASK: Synchronize Server full install and net install iso images (ticket 32&48) STATUS:still open, info needed 4. TASK: ACTION: pboyHB opens a thread about work projects on the mailing list STATUS:DONE Further discussion this meeting. 5. TASK: ACTION: file a ticket with qe team to ask for a test day for libvirt; STATUS:DONE Follow up: #agreed: langdon will follow up on test day === Facilitated deployment of key services by combining rpm and Ansible === Discussed: * Proper location for data separated from system data * Requirement to create a Server Ansible Galaxy AGREED: The WG members will review the suggestions jwhimpel posted on the M/L and provide feedback until next meeting in 2 weeks see: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… === Work Planning Update === AGREED: The WG agrees on work objectives at https://fedoraproject.org/wiki/Server, "Currently Ongoing Work Projects." (2021-08-04) === Next Meeting === Wednesday Sept. 1, 2021 17:00 UTC Planned topics so far: a. Follow up actions b. Continuation Facilitated deployment of key services by combining rpm and Ansible, use case Wildfly

1 0

Hooray! Server documentation got published.
by Peter Boy 18 Aug '21

18 Aug '21

As it turned out at our IRC meeting today, thanks to pbokoc our server documentation is now linked on the start page! Suddenly everything went very fast. Many many thanks to pbokoc! https://docs.fedoraproject.org/en-US/docs/ The descriptive text is different. Probably our text was too long for the page design after all. This can certainly be improved over time. But the most important part is now achieved. After finishing the renewal of the PRD, this is the second major goal we have achieved together. Cheers! Peter

1 0

Fwd: Re: Installing wildfly
by John W. Himpel 18 Aug '21

18 Aug '21

Forwarding to the list so it does not get lost. Peter, I've see that too. But I haven't had time to study it in any detail. After I finish up some more work on KAMI911/ansible-role-wildfly-configuration, I will attempt to accomplish the same task with Jcliff. John On Wed, 2021-08-18 at 16:31 +0200, Peter Boy wrote: > 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 >

1 0

Installing wildfly
by John W. Himpel 18 Aug '21

18 Aug '21

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.

2 1

Agenda Items on 2021-08-18 17:00 ==UTC== meeting
by Peter Boy 18 Aug '21

18 Aug '21

Hi all, Our next IRC meeting will take place ============================================================ Fedora Server IRC meeting Wednesday, August 18 17:00 ==UTC== irc.libera.chat #fedora-meeting ============================================================ == Agenda == 1. Follow up actions 2. Facilitated deployment of key services by combining rpm and Ansible 3. Work planning update 4. Open Floor === Ad 1: === TASK: Server docs: (2021-07-21) AGREED: : pboy will wait until next week Wednesday and. than ask if we can anything do to make it happen. Status DONE TASK: Ansible/Wildfly (2021-08-04) ACTION: jwhimpel will write a first draft how to handle the wildfly example case for discussion next meeting. STATUS:DONE TASK: Synchronize Server full install and net install iso images (ticket 32&48) STATUS:OPEN TASK: ACTION: pboyHB opens a thread about work projects on the mailing list STATUS:DONE (sie top 3) TASK: ACTION: langdon to file a ticket with qe team to ask for a test day for libvirt; STATUS:DONE. Results? === Ad 2: === See latest proposal first draft by jwhimpel: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… Various related information: (a) mail from jwhimpel: Use Cases for server-ansible-roles https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… (b) Fedora Server Wiki page: https://fedoraproject.org/wiki/Server/Using_Ansible === Ad 3:=== We decided some time ago to have a discussion on the mailing list: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or…

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server August 2021