Agenda Items on 2024-02-21 18:00 ==UTC== meeting
by Peter Boy
The upcoming meeting will be held on
==========================================================================
Fedora Server MATRIX meeting Wednesday, Feb 21 18:00 ==UTC==
https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=c...
==========================================================================
Please, check your local time using date -d '2024-02-21 18:00UTC'
As a reminder
=============
We decided to continue our meetings on MATRIX!
Unfortunately I couldn't manage to adjust the link in the automated reminder in time. So the link to IRC there is WRONG!
The above link lets you choose which app to use: web browser, elements, and a lot of others, including some CLI tools, and redirects you to the meeting romm.
If you don't have a Matrix account yet, the easiest way is to start at https://chat.fedoraproject.org. Using the option Create Account this page guides you perfectly through the required steps.
It you already use Matrix, you may have to add Fedora-meeting to your to your rooms list. Select Fedora space in the left most column in element oder web browser (not the Fedora room in the adjacent column). In the main opens a quite long list of Fedora rooms, but most importent a search field, where you can look for 'meeting'.
==== Agenda ====
#link https://pagure.io/fedora-server/report/Meeting
To be able to discuss all topics on the agenda and to prevent us from repeatedly putting off topics that have not been dealt with, we should set time limits for the individual items on the agenda. If we need more time, we should continue on the mailing list.
=== 1. Follow up actions and announcements ===
=== 2. LVM2 default configuration change
#link https://bugzilla.redhat.com/show_bug.cgi?id=2258764
#link https://bugzilla.redhat.com/show_bug.cgi?id=2246871
#link https://bugzilla.redhat.com/show_bug.cgi?id=2247872
=== 3. Testing F40 ===
#link https://pagure.io/fedora-server/issue/125
We need to discuss
- the current state of tests
- evaluation of the change set regarding Server
- How to continue moving away from hackmd
=== Revisiting Server installation media naming convention
https://pagure.io/fedora-server/issue/126
=== 4. Our "story" for F40
https://pagure.io/fedora-server/issue/101
This includes a Server entry to the Release Notes!
=== 5. Work program and goals for F40/41 ===
Previous discussion: Fedora Server goal(s) for F39
#link https://pagure.io/fedora-server/issue/102
=== 7. Open Floor
For any additions or changes, please reply to this email.
For an overview about current tasks look at:
https://pagure.io/fedora-server/boards/Works%20in%20progress
===== Pending topics for the next meetings =====
=== Revisiting Fedora Server release criteria
#link https://pagure.io/fedora-server/issue/61
=== Using Ansible to install and configure Wildfly
#link https://pagure.io/fedora-server/issue/60
=== Review installation media
#link https://pagure.io/fedora-server/issue/88
=== F39 Work Project: Fedora Server on (ARM) SBC
#link https://pagure.io/fedora-server/issue/108
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
1 month, 3 weeks
Issue getting into Matrix
by John W. Himpel
When I follow the link https://chat.fedoraproject.org I input my FAS
name and password.
I get the following error message:
We couldn't log you in
This homeserver has hit its Monthly Active User limit.
Please contact your service administrator to continue using this
service.
Any suggestions?
2 months
HTTP Apache Web Server issue and bug unprocessed report
by Peter Boy
Hi folks,
We have a serious issue with the current Apache httpd package, which is an indispensable service for a server these days.
The issue is basically the default configuration as provided by the package:
- if you create just one server in den .conf directory, it results in a non-functional https configuration
- the configuration uses items, that are deprecated since version 2.4
- the default layout of the default configuration is currently not suitable
I wrote a bug report about it:
https://bugzilla.redhat.com/show_bug.cgi?id=2258121
Unfortunately we are experiencing a common Fedora problem, nobody responds to it and the bug reports are left unprocessed and pile up. And because none of the maintainers respond at all, we have now also missed all the deadlines for improving something for f40.
Technically an improvement is more than simple. It’s just a change in the configuration files, as far as I see.
Any idea how to proceed with this?
- Would someone take the bug report and check my analyses?
- Is there any way to bring this forward?
- Should we create a new https-server package which takes the binaries and provides an alternative configuration? Probably similar to default-editor-vim / default-editor-nano?
As it currently stands, we are in no way competitive with, for example, Debian or ArchLinux.
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
2 months, 1 week
Discussion of our 2024 work plan
by Peter Boy
As agreed, I have created a hackmd.io page with a proposal for our 2024 and then long-term work plan. We have to discuss and probably decide about it at our upcoming meeting. It seems important to me to appoint an assignee to watch over and organize the work.
https://hackmd.io/c3anuyPKQQy5ELmqXTOdRA
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
2 months, 1 week
Further procedure with F40 tests
by Peter Boy
Currently we have a list of test items on hackmd (https://hackmd.io/NtO4O9vRT3a71UMZMkceoA?both) for discussion and comments (and assign oneself to work on one or more of the tests!).
I would propose to leave that up to our next meeting and then transfer it to our issue repo and use it as a template for f41. And we should start to collect the results in a wiki page. I hope, everybody knows how to use the wiki.
Any other ideas?
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
2 months, 1 week
Testing f40
by Peter Boy
The latest version for testing is currently Rawhide 2024-02-10
See https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20240210.n....
Please, we need some more tester!
Local DVD Installation
======================
I noticed:
- The initial menu (with Install.. Test… ) the frame is completely offset to the right, not centered.
- Keyboard does not react or reacts very slowly to the Enter key to select an action before the default waiting time has elapsed
- Error messages appear when booting after the media test:
* [Firmware Bug]: TSC_DEADLINE disabled due to Errata: please update microcode to version 0x20 (or later)
* overlayfs: failed to resolve '/run/overlayfs': -2
Everything worked fine nevertheless, bug is at least ugly
- In the menu for selecting the country option, keyboard control initially works very slowly and without visual feedback as to which item is currently active. Mouse works fine.
- Bei Custom Partitionierung hält Anaconda nicht die Reihenfolge ein, in der die Partitionen erzeugt werden. Das führt zu Problemen, wenn man später die Partitionieren anpassen will / muss.
- The LVM /etc/lvm/devices/system.devices device file is obviously created correctly in connection with the installation and adapted to the target machine (in this case with the RAIDs). And is therefore present.
- Post installation tasks, everything worked well
These items are not severe issues but should get improved for a polished release.
Adding virtualization support
=============================
Everything went fine. But we get a lot of superfluous stuff installed, e.g. libwayland-server or spice-server and audio stuff.
I suppose, Cockpit is the culprit again, but have to check it in detail.
Instantiation of VMs
====================
Everything went fine. The LVM device file is correct, also probably not during instantiation, but part of the image. I have yet to check that.
Aarch64 SBC
===========
The installation issue on server host is still existing.
--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
PBoy(a)fedoraproject.org
Timezone: CET (UTC+1) / CEST (UTC+2)
Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast
2 months, 2 weeks