server February 2024

server@lists.fedoraproject.org

8 participants
15 discussions

Proposal: Changes to Fedora Server default partitioning scheme
by Stephen Gallagher 12 Dec '24

12 Dec '24

The following proposal comes out of the discussion at this weeks Server SIG meeting[1] Fedora Server will have: * / (root) will be a minimum of 2 GiB and a maximum of 15 GiB * SWAP will continue to be calculated automatically based on available RAM on the system * All unused space will be assigned to a volume group and available to be assigned to new partitions or extend existing partitions. * Anaconda will continue to handle the appropriate EFI and /boot settings We also discussed during the meeting whether we should have a separate /var partition by default, but the general sense was that we might be better served by developing a mechanism to allow partitions to be split from existing mount points, which would be more flexible going forward. As we did not have quorum in the meeting by the point we got to this proposal, I'm taking it to the list for discussion and votes. For the record, the current behavior of the partitioning scheme is for / to be given up to 50 GiB of space and then any remaining space after that is assigned to a separate /home partition. [1] https://meetbot.fedoraproject.org/fedora-meeting-1/2016-03-15/serversig.201…

4 7

Fix arm-image-installer adjustment
by Peter Boy 05 Mar '24

05 Mar '24

Pwhalen has provided a fix for the arm-image-installer issue. The fix also contains a correction of the LVM devices file. See Bug: https://bugzilla.redhat.com/show_bug.cgi?id=2265422 Feedback at https://bodhi.fedoraproject.org/updates/FEDORA-2024-5b91f30bca I tested it here with one of my ARM devices and a Fedora 39 Server installation and it works perfectly now again. Would be helpful if someone else would test it, too, and provide feedback. Thanks. -- 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 1

Agenda Items on 2024-02-21 18:00 ==UTC== meeting
by Peter Boy 04 Mar '24

04 Mar '24

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]=cha… ========================================================================== 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

2 2

2024-02-26 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson 23 Feb '24

23 Feb '24

# F40 Blocker Review meeting # Date: 2024-02-26 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for another blocker review meeting. We have 7 proposed blockers and 4 proposed freeze exception for Beta, and 5 proposed blockers for Final. The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. I'll be on vacation on Monday, so Frantisek Zatloukal will be running the meeting, thanks Franta! If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

Issue getting into Matrix
by John W. Himpel 20 Feb '24

20 Feb '24

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 1

[Fedocal] Reminder meeting : Fedora Server WG
by pboy＠fedoraproject.org 19 Feb '24

19 Feb '24

Dear all, You are kindly invited to the meeting: Fedora Server WG on 2024-02-21 from 18:00:00 to 19:00:00 UTC At fedora-meeting(a)irc.libera.chat The meeting will be about: Standing meeting of the Fedora Server Edition Working Group More information available at: [https://pagure.io/fedora-server/report/Meeting](https://pagure.io/fedora-se… Source: https://calendar.fedoraproject.org//meeting/10709/

1 0

2024-02-19 @ 17:00 UTC - Fedora 40 Blocker Review Meeting
by Adam Williamson 16 Feb '24

16 Feb '24

# F40 Blocker Review meeting # Date: 2024-02-19 # Time: 17:00 UTC # Location: https://matrix.to/#/#blocker-review:fedoraproject.org?web-instance[element.… Hi folks! It's time for another blocker review meeting. We have 6 proposed blockers and 1 proposed freeze exception for Beta, and 4 proposed blockers for Final. The meeting will be on Matrix, as we're trying to move to more modern systems and the meeting bot is working on Matrix now. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing. If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you'll see links labeled "Vote!" next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. https://pagure.io/fedora-qa/blocker-review has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn't a clear outcome in the ticket voting yet. **THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!** We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F40 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you on Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org https://www.happyassassin.net

1 0

HTTP Apache Web Server issue and bug unprocessed report
by Peter Boy 15 Feb '24

15 Feb '24

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

3 7

Discussion of our 2024 work plan
by Peter Boy 13 Feb '24

13 Feb '24

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

1 0

Further procedure with F40 tests
by Peter Boy 13 Feb '24

13 Feb '24

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

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server February 2024