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…
Composer generates custom images suitable for deploying systems or
uploading to the cloud. It integrates into Cockpit as a frontend for Lorax
Composer.
Here are the release notes from version 0.2.0:
- Include ability to add a user to a blueprint
- Fix issue when blueprint contents include a package with more than one
arch
- Fix issue with loading contents in Export modal on Blueprints page
You can get Composer here:
https://github.com/weldr/welder-web/tree/0.2.0#cockpit-composer
Composer is available in Fedora 30:
https://bodhi.fedoraproject.org/updates/cockpit-composer-0.2.0-1.fc30
Or download the tarball here:
https://github.com/weldr/welder-web/releases/tag/0.2.0
Regards,
Jenn Giardino
Jenn Giardino
Senior Interaction Designer
User Experience Design Team
Red Hat, Inc.
1-919-716-5045
jgiardin(a)redhat.com
Dear all,
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 30
Beta Release Readiness meeting. This meeting will be held on Thursday,
2018-03-21 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the Beta
release of Fedora 30. Please note that this meeting will be held even
if the release is delayed at the Go/No-Go meeting on the same day two
hours earlier.
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
https://fedoraproject.org/wiki/Release_Readiness_Meetings.
View the meeting on Fedocal:
https://apps.fedoraproject.org/calendar/Fedora%20release/2019/3/21/#m9492
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
For a long time, the Fedora Server Edition has provided a fairly
lightweight default installation, but a fairly heavyweight DVD. This
is because we opted to include a lot of infrastructure-related content
on the disk, such as BIND, FreeIPA, MariaDB and PostgreSQL, among
others.
The reality these days is that this is probably more or less
unnecessary. There's no such thing as a server that is not connected
to a network and since we aren't shipping the entirety of the Fedora
package collection on this disk, inevitably anyone installing from it
is going to need to have access to package mirrors anyway.
So I'd like to propose that we get rid of nearly the entirety of the
<optionlist> section from comps.xml[1][2] and variants-fedora.xml[3].
The result will be a far smaller install DVD, less space wasted on the
mirrors (both for the DVD and the install tree) and very little
difference in user experience.
Arguments against this have historically been that having it all on
one disk is better for network-constrained environments to avoid
downloading content multiple times. Realistically, however, I think
this is generally going to be solved by local mirroring in most
real-world scenarios.
[1] https://pagure.io/fedora-comps/blob/master/f/comps-f30.xml.in
[2] With the exception of the "server-hardware-support" and
"guest-agents" which may be needed for proper installation, depending
on the hardware.
[3] https://pagure.io/pungi-fedora/blob/master/f/variants-fedora.xml