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…
Folks!
At our last meeting, we decided to launch our user survey on December 10 and to let it run until February 18. We thus take into account the low level of attention over Christmas and the turn of the year, and also the chance to increase attention through FOSDEM on February 1 and 2.
Thanks to @mowest and @jwf, the survey is already available in the Fedora lime survey space.
https://fedoraproject.limequery.com/fedora-server-f41
Now the 'clock is ticking'. I ask everyone to check whether it corresponds to the draft, whether there are still errors to be corrected, or whether something should be added. We have to make a final decision at our meeting next Wednesday, December 4.
@mowest: JWF suggested that we use a ticket to contact the design team about a poster. Please, could you as our poll specialist as well as design expert, take this into your proven hands? (See my Matrix post in Server room)
Best
Peter
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
Again, for everyone's convenience, a brief summary of our IRC meeting right here.
== Essentials ==
AGREED pboy writes the draft of a document that describes our test strategy.
We will discuss the draft on mailing list before we decide on one if the next meetings.
For details see:
https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-2024/
--
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
Now another attempt at a summary
What to manually test
=====================
A) regular QA tests
------------------
1. "Default boot and install“ tests on „USB“ and optimally „DVD“
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
Currently it is divided into 2 tests: DVD (or local) and Netboot
But we have 4 ways per boot procedure
- local interactive
- local remote (via VNC)
- local automatic (via key file on OEMDRV USB)
- remote automatic
How do we want to deal with this?
There are some tests about Anaconda and VNC automatically. Do they work on hardware?
2. Additionally: running the install test with arm-imange-installer
There should already be a topic for this anywhere.
3. IPA Tests:
https://fedoraproject.org/wiki/QA:Testcase_freeipa_replication_advanced
B) Specific server-related special cases
————————————————————
1. "maybe we should test more storage operations post-install“
Integral part of our installation during post-installation is the expansion / addition of LVs
We may review the current tests regarding Custom storage configuration when we discuss to expand the current server related release criteria.
2. Another topic may be Virtualization, where we adopt a functioning internal network (virbr0) for internally protected communication and services such as database and IPA and including internal DNS (split DNS via systems-resolved, currently doesn’t work anyway).
We should postpone this for our discussion about adding server specific services according to our updated technical specifications.
C) Possible effects of individual changes specifically on Server
"A domain-specific review of the changes is a good idea“
Changeset available at
https://fedoraproject.org/wiki/Releases/{relnum}/ChangeSet <https://fedoraproject.org/wiki/Releases/%7Brelnum%7D/ChangeSet>
We should manage this with a tracking issue for each new release.
How to organize manual testing
==============================
1. In the medium term, the current server-specific page
https://fedoraproject.org/wiki/Test_Results:Fedora_41_RC_1.3_Server
should be supplemented and tailored more clearly to servers.
a) The download list filtered by Server
b) The subtitle „Key“ might be better expressed by „Examples how to fill in the results“
c) The section „Test Matrix“ should expanded by a table of links to the manual test cases that are Server related (currently it can be misinterpreted as „everything is done“ (by coconut).
2. In the medium term we should introduce a „test week“. That would include the manual tests and the review of the docs. (As an example see coreos test week).
--
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
There is an issue with Postgresql when updating to F41.
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org…
PostgreSQL is one of our two central services that are tested automatically. And as far as I know we did miss the above issue. There is no release note entry either.
How could this happen? Do we need to extend the PostgreSQL tests? Or have I missed something?
--
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