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…
Hello all,
Cockpit is the modern Linux admin interface. We release regularly. Here
are the release notes:
https://cockpit-project.org/blog/cockpit-306.html
Summary:
- Kdump: Add Ansible/shell automation
- OSTree: Redesign, with new features
- Machines: Change “Add disk” default behavior
- Podman: Delete intermediate images
You can get Cockpit here:
http://cockpit-project.org/running.html
The new releases are available in Fedora 38 and 39.
Take care,
Martin Pitt
The upcoming meeting will be held on
===========================================================
Fedora Server IRC meeting Wednesday, Nov 15 18:00 ==UTC==
irc.libera.chat #fedora-meeting
===========================================================
Please, check your local time using date -d '2023-11-15 18:00UTC'
REMEMBER:
With winter time, we have now fallen back to 18:00 UTC.
In local time, it's back to the way it was in the last few months.
==== 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 ===
2. === Fedora release 39 - State of Server media and Download Web page === 15 mins max
#link https://fedoraproject.org/server/download
3. === Fedora Server release and quality criteria ===
#link https://pagure.io/fedora-server/issue/63
#link https://pagure.io/fedora-server/issue/61
4. === Work program and goals for F40 ===
#link https://pagure.io/fedora-server/issue/102
#link https://pagure.io/fedora-server/issue/101
5. === 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
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
--
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
Hey folks! Just a heads up that Rawhide Server installs are broken in
today's Rawhide compose (and any custom install using xfs). This is
because a new version of xfsprogs went into Rawhide and grub2 cannot
detect filesystems made with it:
https://bugzilla.redhat.com/show_bug.cgi?id=2247926
I've identified the patches needed in grub2, but I can't patch it
myself as I'm not on the list of people who can build packages that
need to be Secure Boot signed, and anyway, working on the grub2 package
is a bit of a nightmare for non-maintainers due to the whole "hundreds
of patches that are pulled from an alternative upstream git repo"
thing.
I've requested xfsprogs be untagged for now:
https://pagure.io/releng/issue/11763
so if that gets done, things should work again after the next compose.
Unfortunately openQA didn't catch this because we don't test xfs
installs on updates :( Maybe I'll have to add a test somehow.
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net
As with the latest release candidate (rc 1.5) from today we have still an issue with the ARM SBC / RPi image.
* The RPi image needs a nomodeset fix on the arm-imange-installer comandline, otherwise it boots with a black screen
* Afterwards you can’t manage the storage because LVM is broken.
* All my Rockchip based devices (RockPro64, Rock Pi 4, Roc-3399-pc) can’t boot at all, because the broken LVM prevents the U-Boot files to get copied onto the SD card. The same will be true for all other devices besides RPi, too, that need U-Boot files to be able to boot
See details in the bug reports:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2246871https://bugzilla.redhat.com/show_bug.cgi?id=2244305
There are ways around that
* You can fix that by manually deleting the content of /etc/lvm/devices, which is currently not documented anywhere and probably not a location, an admin should mess with. An RPi would then work as far as I know. For all other devices this doesn’t work without additional steps.
* You get the other devices booting which have a workable *and* compatible SPI U-Boot installed and can substitute the U-Boot files otherwise be copied to the SD card by arm-image-installer. And then use the before mentioned fix.
* Fedora provides for some devices a SPI module which should work (I didn’t test that). But it is a real challenge to install those the Fedora way (https://nullr0ute.com/2021/05/fedora-on-the-pinebook-pro/) and a real adventure if you have a non-US keyboard.
* Some devices are supported by non-Fedora software, e.g. tow-boot (https://tow-boot.org <https://tow-boot.org/>). You can install the SPI very comfortable and the current version can also boot the Fedora image without Fedora U-Boot files.
In the latter 3 cases you would additionally have to fix the LVM image.
The question is, how to proceed with that situation.
a) I suggested to make the bug a release blocker.
b) Others objected, because there is a workaround available.
In case of b)
Do we really want to publish a broken image along with the other media as a regular release?
Alternatively, we might
- Publish it separately well below our regular media as kind of "technical sneak preview“
- Skip F39 for ARM SBC and continue to distribute the F38 image
- rely to third party software, e.g. tow-boot for devices it supports
- Other ideas?
We should discuss this today at the meeting.
--
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
The upcoming meeting will be held on
===========================================================
Fedora Server IRC meeting Wednesday, Nov 01 17:00 ==UTC==
irc.libera.chat #fedora-meeting
===========================================================
Please, check your local time using date -d '2023-11-01 17:00UTC'
REMEMBER:
For European members it is 1 hour earlier at local time !!!
Next meeting we will fall back to 18:00 UTC so it is the
same for everybody in local time!
And sorry for the late agenda. I was busy with testing the rc.
==== 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. === Fedora release 39 rc current state and how to continue === 15 mins max
See my earlier mail today:
Current state of F39 Fedora Server Edition for ARM SBCs / RaspberryPi
https://bugzilla.redhat.com/show_bug.cgi?id=2244305https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2246871
Goal:
- Deciding about the next steps
3. === Package fail2ban orphaned === 10 mins
No ticket yet.
That's part of our default post-install procedure.
4. === Work Project: Using Ansible to install and configure Wildfly === 20 mins
#link https://pagure.io/fedora-server/issue/60
5. === F39/40 Work Project: Fedora Server in a virtualized runtime environment === 20 mins
#link https://pagure.io/fedora-server/issue/110
Topics to discuss: How to collect information
- The feedback from the community so far
#link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or…
6. === 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
--
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