server March 2023

server@lists.fedoraproject.org

13 participants
18 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

F38 servers will auto-suspend if GNOME is installed
by Kamil Paral 29 Mar '23

29 Mar '23

GNOME developers enabled auto-suspend by default, even when on AC power, after 15 minutes of inactivity. I just tested that this will also affect Fedora Server, if you install GNOME packages manually, and boot into the graphical.target. I don't know how rare or common this scenario is, but I want to highlight this change. If Server WG thinks this is a problematic change for the Fedora Server user base, please start making noise about it now, because we're only 1 month from F38 Final release :-) Cheers, Kamil Fedora QA

6 13

Re: The nvme-cli package & the Fedora Server DVD on-media repositories
by Peter Boy 23 Mar '23

23 Mar '23

> Am 23.03.2023 um 13:17 schrieb mkolman(a)redhat.com: > > On Wed, 2023-03-22 at 16:15 +0100, Peter Boy wrote: >> >> >>> Am 22.03.2023 um 12:59 schrieb mkolman(a)redhat.com: >>> >>> Hi! >>> >>> Recently we have been looking at this bug, currently reported on >>> Anaconda: >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=2178508 >>> >>> "missing packages:nvme-cli during the installation of Fedora 38 Server >>> Beta" >>> >>> In short, what happens is that starting with Blivet (the storage >>> library used by the Anaconda installer) 3.7.0 the nvme-cli tool will be >>> proposed for installation when NVME hardware is detected at >>> installation time. >>> >>> This effectively boils down to the nvme-cli package being added to the >>> installation RPM transaction. >>> >>> This works correctly on netinst images, as the nvme-cli package is >>> available from the Fedora online repositories. But it fails on the F38 >>> Server DVD image, as nvme-cli is *not* present in the on-media >>> repositories. >>> >>> My question is - how are the DVD image repositories defined ? How can >>> the nvme-cli package be added to them ? >> >> >> As Stephen Smoogen already noted, the DVD as well as the net install pull in packages as defined in the comps files as he noted. >> >> If the net install includes the file but the DVD not, then the cause is most likely a dependency issue. DVD and NET installation handle dependencies differently. Net installation includes all types of dependencies, but DVD installation does not. If I remember correctly, weak dependencies are not taken into account. See https://pagure.io/fedora-server/issue/32 > In this case the dependency is dynamically generated at runtime - if Blivet find the right NVME hardware on the target system, it will request the nvme-cli package to be installed. For this to work, the nvme-cli package needs to be present on the DVD image repos. So to fully solve this issue, I think we will have to somehow hardwire the package to be included in the DVD repos, as regular "static" dependencies are not directly in play here. OK, that’s a different issue. Looking around to find a suitable location in the server kickstart files, I found the following in comps: (pagure.io/fedora-comps - f38) comps-f38.xml.in: Note: The anaconda-tools group lists packages that anaconda might comps-f38.xml.in: anaconda environment. If a package is needed in anaconda's runtime comps-f38.xml.in: environment it should be listed as a dependency of the anaconda comps-f38.xml.in: <id>anaconda-tools</id> comps-f38.xml.in: <packagereq type="mandatory">kdump-anaconda-addon</packagereq> comps-f38.xml.in: <id>critical-path-anaconda</id> comps-f38.xml.in: <_name>Critical Path (anaconda)</_name> comps-f38.xml.in: <_description>A set of packages that provide the Critical Path functionality for installing Fedora with anaconda</_description> comps-f38.xml.in: <packagereq type="mandatory">anaconda</packagereq> comps-f38.xml.in: See https://github.com/rhinstaller/anaconda/commit/a475dd0194df7abf0453786fc014… Did you already add the nvme-cli package to the anaconda-tools? As I understand, that way the package would become part of the Anaconda runtime and included in the installation medium. That might be a better way as to include it into the files to be installed on every Fedora Server to be created, regardless whether it is needed. >> >> It is best to ask Stephen Gallagher of Server WG. He also solved a similar problem with Cockpit previously at the time in minutes, without causing collateral damage (as others did, unfortunately). I'll put him into CC. >> >> >> >> >> >> -- >> 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 >> Java developer and enthusiast >> _______________________________________________

1 0

Cockpit 288, cockpit-machines 286, and cockpit-podman 65 released
by Katerina Koukiou 23 Mar '23

23 Mar '23

Hi! Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes: https://cockpit-project.org/blog/cockpit-288.html Summary: - Accounts: Show shell and home directory on detail page - Accounts: Custom user ID during account creation - Overview: Support additional timeservers with chronyd - Metrics: Show longer time span by default - Storage: Mounting filesystems at boot time - Machines: Create VM based on cloud image and start it later - API removal: Remove cockpit.dbus.publish() and .meta() You can get Cockpit here: http://cockpit-project.org/running.html The new releases are available in Fedora 37 and 38, see the links in the blog post. Enjoy the rest of the day, Katerina

1 0

F38 dnf modules isn't going to be functional
by Sumantro Mukherjee 16 Mar '23

16 Mar '23

DNF5 test day is running and we have figured that dnf modules command is being worked on. The functionality can be tracked [0] and this is targeted to be complete in F39. If users, have modules enabled in F37 and upgrade to F38, things will be fine. However, fresh installs or installations which wanna play with modules in F38 won't be able to do that. DNF team suggests a workaround how to modify modules without using any tool - modify files in /etc/dnf/modules.d. if you want to reset nodejs module you can use rm /etc/dnf/modules.d/nodejs If this is a problematic thing, we should communicate this to the users. [0] https://github.com/rpm-software-management/dnf5/issues/146 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

2 1

Re: F38 dnf modules isn't going to be functional
by Peter Robinson 16 Mar '23

16 Mar '23

On Wed, Mar 15, 2023 at 2:20 PM Frantisek Zatloukal <fzatlouk(a)redhat.com> wrote: > But that's microdnf, not the current default dnf. I don't think microdnf > was used by default in any of our blocking spins/images. > We ship microdnf in the arm minimal image due to issues with dnf and memory usage[1] and it's used quite widely on devices like the Raspberry Pi Zero2W. The Minimal image is blocking. https://bugzilla.redhat.com/show_bug.cgi?id=1907030 > On Wed, Mar 15, 2023 at 1:44 PM Sumantro Mukherjee <sumukher(a)redhat.com> > wrote: > >> >> >> On Wed, Mar 15, 2023 at 2:09 PM Frantisek Zatloukal <fzatlouk(a)redhat.com> >> wrote: >> >>> But the dnf > dnf5 switch will happen in F39, not F38, so that shouldn't >>> be an issue that it's not supported in DNF 5, no? >>> >> >> I checked and it says F38 as target release >> https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf >> >> >>> >>> On Wed, Mar 15, 2023 at 8:32 AM Sumantro Mukherjee <sumukher(a)redhat.com> >>> wrote: >>> >>>> DNF5 test day is running and we have figured that dnf modules command >>>> is being worked on. >>>> The functionality can be tracked [0] and this is targeted to be >>>> complete in F39. >>>> If users, have modules enabled in F37 and upgrade to F38, things will >>>> be fine. >>>> However, fresh installs or installations which wanna play with modules >>>> in F38 won't be >>>> able to do that. >>>> >>>> DNF team suggests a workaround how to modify modules without using any >>>> tool - modify files in /etc/dnf/modules.d. if you want to reset nodejs >>>> module you can use rm /etc/dnf/modules.d/nodejs >>>> >>>> If this is a problematic thing, we should communicate this to the users. >>>> >>>> [0] https://github.com/rpm-software-management/dnf5/issues/146 >>>> >>>> -- >>>> //sumantro >>>> Fedora QE >>>> TRIED AND PERSONALLY TESTED, ERGO TRUSTED >>>> _______________________________________________ >>>> test mailing list -- test(a)lists.fedoraproject.org >>>> To unsubscribe send an email to test-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/test@lists.fedoraproject.org >>>> Do not reply to spam, report it: >>>> https://pagure.io/fedora-infrastructure/new_issue >>>> >>> >>> >>> -- >>> >>> Best regards / S pozdravem, >>> >>> František Zatloukal >>> Senior Quality Engineer >>> Red Hat >>> _______________________________________________ >>> test mailing list -- test(a)lists.fedoraproject.org >>> To unsubscribe send an email to test-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/test@lists.fedoraproject.org >>> Do not reply to spam, report it: >>> https://pagure.io/fedora-infrastructure/new_issue >>> >> >> >> -- >> //sumantro >> Fedora QE >> TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted> >> _______________________________________________ >> test mailing list -- test(a)lists.fedoraproject.org >> To unsubscribe send an email to test-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/test@lists.fedoraproject.org >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> > > > -- > > Best regards / S pozdravem, > > František Zatloukal > Senior Quality Engineer > Red Hat > _______________________________________________ > test mailing list -- test(a)lists.fedoraproject.org > To unsubscribe send an email to test-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/test@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >

2 2

Re: F38 dnf modules isn't going to be functional
by Lukas Ruzicka 16 Mar '23

16 Mar '23

On Wed, Mar 15, 2023 at 3:20 PM Frantisek Zatloukal <fzatlouk(a)redhat.com> wrote: > But that's microdnf, not the current default dnf. I don't think microdnf > was used by default in any of our blocking spins/images. > Totally correct. Thanks for the clarification.

1 0

Our most important features for the new web page
by Peter Boy 15 Mar '23

15 Mar '23

The current draft: https://fedora.gitlab.io/websites-apps/fedora-websites/fedora-websites-3.0/… Discussion about development https://discussion.fedoraproject.org/t/fedora-server-front-page-revamp-look… We have to check and discuss * The graphical representations * The wording of the mission statements * specific properties in the Fedora universe * specific properties in relation to other distributions > - - - - - - - - - - - < According for various discussions and our PRD (Product Requirement Document) our central intentions are: (a) =Flexibility= and =customizable=, can be =tailored to the specific needs= of the local admin / customer / owner (Universalitiy and Flexibility are the main difference to CoreOS and IoT) "provides a ... flexible, and universally-adaptable base for the everyday provisioning of services and applications by organizations and individuals, "Deploy the services you need under your own control, and customized to your own requirements" "A great variety of available software, ... opens up a wide range of possibilities for flexibility in building a server according to the specific needs and wishes of a customer or end-user. A platform for deploying containerized applications supporting multiple container technologies, among which **the system administrator can choose according to custom requirements**. (b) ==Stable but nevertheless latest technology== "Fedora Server provides a stable ... based on the latest technology and is available quickly after the upstream releases. "Fedora Server provides a stable foundation, with balanced resource utilization, yet delivering the latest technologies giving administrators every day exposure to the latest tooling as soon as it is usable" (c) A platform for important infrastructure tasks and basic services (DNS, DHCP, FreeIPA, and others) A platform for various important, dedicated server applications (file/storage server, database server, user-developed web applications, etc.) (d) =Security= "enterprise-grade security, resulting in carefully pre-configured releases, offering uncompromising security without extensive configuration work by system administrators. Security-minded: secure by design - extending into TPM support, disk encryption enablement (e) Admin friendly easy update and upgrade to next release without re-installation (f) For developers: " implementation of the latest server technology for exploring and evaluating." " Developers find an excellent development environment for the next generation server as well as application software with the latest software versions available. "

1 0

Re: F38 dnf modules isn't going to be functional
by Sumantro Mukherjee 15 Mar '23

15 Mar '23

On Wed, Mar 15, 2023 at 2:09 PM Frantisek Zatloukal <fzatlouk(a)redhat.com> wrote: > But the dnf > dnf5 switch will happen in F39, not F38, so that shouldn't > be an issue that it's not supported in DNF 5, no? > I checked and it says F38 as target release https://fedoraproject.org/wiki/Changes/MajorUpgradeOfMicrodnf > > On Wed, Mar 15, 2023 at 8:32 AM Sumantro Mukherjee <sumukher(a)redhat.com> > wrote: > >> DNF5 test day is running and we have figured that dnf modules command >> is being worked on. >> The functionality can be tracked [0] and this is targeted to be complete >> in F39. >> If users, have modules enabled in F37 and upgrade to F38, things will be >> fine. >> However, fresh installs or installations which wanna play with modules >> in F38 won't be >> able to do that. >> >> DNF team suggests a workaround how to modify modules without using any >> tool - modify files in /etc/dnf/modules.d. if you want to reset nodejs >> module you can use rm /etc/dnf/modules.d/nodejs >> >> If this is a problematic thing, we should communicate this to the users. >> >> [0] https://github.com/rpm-software-management/dnf5/issues/146 >> >> -- >> //sumantro >> Fedora QE >> TRIED AND PERSONALLY TESTED, ERGO TRUSTED >> _______________________________________________ >> test mailing list -- test(a)lists.fedoraproject.org >> To unsubscribe send an email to test-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/test@lists.fedoraproject.org >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue >> > > > -- > > Best regards / S pozdravem, > > František Zatloukal > Senior Quality Engineer > Red Hat > _______________________________________________ > test mailing list -- test(a)lists.fedoraproject.org > To unsubscribe send an email to test-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/test@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>

1 0

[Fedocal] Reminder meeting : Fedora Server WG
by pboy＠fedoraproject.org 15 Mar '23

15 Mar '23

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

3 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server March 2023