server August 2022

server@lists.fedoraproject.org

12 participants
17 discussions

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

13 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 8

Federa 35 Server default editor
by Peter Boy 14 Mar '23

14 Mar '23

In Fedora 34 the default editor was nano, for Workstation and also for Server. In my latest default F35 Server installation I noticed vim-default-editor was installed. Did some good soul take pity and bring vim back to us or did something go wrong with my installation? Best Peter

8 25

Request for testing: Fedora 37 pre-Beta validation tests
by Adam Williamson 31 Aug '22

31 Aug '22

Hey folks! So we're in freeze for Fedora 37 Beta now, and the first go/no-go meeting should be on September 8. It would be really great if we can get the validation tests run now so we can find any remaining blocker bugs in good time to get them fixed. Right now the blocker list looks short, but there are definitely some tests that have not been run. You can use the testcase_stats view to find tests that need running: https://openqa.fedoraproject.org/testcase_stats/37/ For each validation test set (Base, Desktop etc.) it shows when each test was last performed. So you can easily look for Basic and Beta tests that have not yet been run. We need to run all of these. You can enter results using `relval report-results`, or edit the summary results page at https://fedoraproject.org/wiki/Test_Results:Current_Summary . That's a redirect link which will always point to the validation results page for the currently-nominated compose, which right now is 20220826.n.0. Sumantro will be running a validation 'test week' starting on Wednesday, so you can drop by the Fedora Test Day room on chat.fedoraproject.org to hang out with other testers and get any help you need in testing. See https://lists.fedoraproject.org/archives/list/test-announce@lists.fedorapro… for that announcement. Thanks folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

2 2

Re: [Fedocal] Reminder meeting : Fedora Server WG MISTAKE
by Peter Boy 30 Aug '22

30 Aug '22

> Am 30.08.2022 um 19:14 schrieb J Beard <jas_beard(a)hotmail.com>: > > I thought our meetings were the 1st and 3rd weeks in a month. Or did I miss understand? Yes, you are right! === Next meeting is Sept. 7 ==== === No meeting on August 31 ==== I’m sure having to stop the notification in federal, when I configured the calendar. But obviously something went wrong. Peter

1 0

[Fedocal] Reminder meeting : Fedora Server WG
by pboy＠fedoraproject.org 30 Aug '22

30 Aug '22

Dear all, You are kindly invited to the meeting: Fedora Server WG on 2022-08-31 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 More information available at: [https://pagure.io/fedora-server/report/Meeting](https://pagure.io/fedora-se… Source: https://calendar.fedoraproject.org//meeting/10304/

2 1

Heads-up / for discussion: dnf not working with 1G of RAM or less
by Adam Williamson 29 Aug '22

29 Aug '22

Hey folks! I apologize for the wide distribution, but this seemed like a bug it'd be appropriate to get a wide range of input on. There's a bug that was proposed as an F37 Beta blocker: https://bugzilla.redhat.com/show_bug.cgi?id=1907030 it's quite an old bug, but up until recently, the summary was apparently accurate - dnf would run out of memory with 512M of RAM, but was OK with 1G. However, as of quite recently, on F36 at least (not sure if anyone's explicitly tested F37), dnf operations are commonly failing on VMs/containers with 1G of RAM due to running out of RAM and getting OOM-killed. There's some discussion in the bug about what might be causing this and potential ways to resolve it, and please do dig into/contribute to that if you can, but the other question here I guess is: how much do we care about this? How bad is it that you can't reliably run dnf operations on top of a minimal Fedora environment with 1G of RAM? This obviously has some overlap with our stated hardware requirements, so here they are for the record: https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/welcome/Ha… that specifies 2GB as the minimum memory for "the default installation", by which I think it's referring to a default Workstation install, though this should be clarified. But then there's a "Low memory installations" boxout, which suggests that "users with less than 768MB of system memory may have better results performing a minimal install and adding to it afterward", which kinda is recommending that people do exactly the thing that doesn't work (do a minimal install then use dnf on it), and implying it'll work. After some consideration I don't think it makes sense to take this bug as an F37 blocker, since it already affects F36, and that's what I'll be suggesting at the next blocker review meeting. However, it does seem a perfect candidate for prioritized bug status, and I've nominated it for that. I guess if folks can chime in with thoughts here and/or in the bug report, maybe a consensus will emerge on just how big of an issue this is (and how likely it is to get fixed). There will presumably be a FESCo ticket related to prioritized bug status too. Thanks folks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

3 2

2022-08-29 @ 16:00 UTC - Fedora 37 Blocker Review Meeting
by Adam Williamson 27 Aug '22

27 Aug '22

# F36 Blocker Review meeting # Date: 2022-08-29 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.libera.chat Hi folks! We have 4 proposed Beta blockers and13 proposed Final blockers to review, so let's have a review meeting. 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 F36 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 Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Help with structured data
by موسوعة 3D 26 Aug '22

26 Aug '22

There are some problems with the applications' structured data code. Can anyone help me, knowing that it looks right in Google and doesn't show up in search Website link https://bramj3d.com/

1 0

Configure Wildfly for ssl has problems on my host
by John W. Himpel 18 Aug '22

18 Aug '22

All, In order to determine if the issue is something in my localhost or in the instructions, I have made available a project in gitlab containing my ansible playbook. The url for https access s/b: https://gitlab.com/jwhimpel/wildfly-ansible.git . The url for ssh access s/b: git@gitlab.com:jwhimpel/wildfly-ansible.git . You will need to go into inventories/testing/host_vars and modify the subordinate directory to the fdqn of the ansible target host. Inside the newly renamed directory, you will need to add userid and passwords in vars.yml. A shell script to run the playbook is provided. I am trying to configure wildfly to use ssl via the instructions found at: https://developer.jboss.org/people/fjuma/blog/2018/08/31/obtaining-certific… It's the Obtain a certificate from Let's Encrypt command to jboss-sh.cli that errors out for me. PS: You will need to run the jboss-cli.sh command as root to gain access to the wildfly instance. I've looked in: audit.log journal wildfly logs In the wildfly logs are generic error messages but that's not enough for me to figure out what went wrong with certbot trying to get the certificates. If you can or cannot get the jboss-sh.cli commands to work properly, please let me know via the list. Bonus points if you can point me to the source code for jboss-cli.sh so that I can see how the command and options passed to certbot are generated. Thanks. PS: I'm a noob at gitlab, so if you have issues, let me know and I'll see what I can do to resolve them. John Himpel

1 0

Brief information about yesterday's server WG meeting
by Peter Boy 18 Aug '22

18 Aug '22

Again, for everyone's convenience, a brief summary of our IRC meeting right here. For greater details see meetbot == Summary: == https://meetbot.fedoraproject.org/fedora-meeting/2022-08-17/fedora-server.2… == Full log: == https://meetbot.fedoraproject.org/fedora-meeting/2022-08-17/fedora-server.2… Topics discussed: === Follow up actions === DONE pboy will create a next version of the techn. spec. containing our agreements on July 20. Link: • https://docs.fedoraproject.org/en-US/server-working-group/docs/server-techn… (See next Topic) No further open actions. === Final decision about an updated Fedora Server Technical Specification === Link: https://pagure.io/fedora-server/issue/58 It was consensus, that the document is not immutable and thus change be changed later if ideas for improvements surface later. Therefore, a decision now and start with the next tasks. agreed: WG agrees about the techn.spec. in the current version, with alt. 1 for section 1.2 and editorial adaptations as discussed today. === Using Ansible to install and configure Wildfly === #link https://pagure.io/fedora-server/issue/60 This is a key component of our "Supported by Ansible“-project (Server Roles), which has taken a back seat to everyday issues for far too long. jwhimpel has developed a playbook where currently there is still a problem with Letsencrypt certificates to be fixed. Action: jwhimpel will provide access to the playbook on GitHub so we can re-play the installation and test it. ==== PLEASE NOTE: NEXT MEETING Sept. 7, 2022. ==== Due to calendar displacements, we have 5 Wednesdays again in August, so our 2-week rhythm is out of sync again. It implies: The next meeting is **in 3 weeks**! =========================================================== NEXT MEETING: September 7, 2022 - #fedora-meeting 17:00 UTC (3 weeks ahead instead of 2) ===========================================================

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server August 2022