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…
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
===================================================================
#fedora-meeting-1: Server Working Group Weekly Meeting (2016-11-29)
===================================================================
Meeting started by sgallagh at 21:03:08 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-1/2016-11-29/server_workin…
.
Meeting summary
- ---------------
* roll call (sgallagh, 21:03:10)
* Agenda (sgallagh, 21:05:44)
* Fedora 25 Release (sgallagh, 21:11:00)
* Fedora Server 25 is released! Gratitude all around (sgallagh,
21:11:02)
* Some late-breaking SELinux issues have cropped up and need to be
looked into (sgallagh, 21:11:04)
* Fedora 26 Planning (sgallagh, 21:11:51)
* Role Design (sgallagh, 21:13:49)
* ACTION: dperpeet and jds2001 will discuss UX design for NFS role
with Cockpit designers (sgallagh, 21:36:55)
* Server SIG will have a check-in on NFS server on Dec. 13th after the
Cockpit sprint planning (sgallagh, 21:37:24)
* Open Floor (sgallagh, 21:40:06)
Meeting ended at 21:43:43 UTC.
Action Items
- ------------
* dperpeet and jds2001 will discuss UX design for NFS role with Cockpit
designers
Action Items, by person
- -----------------------
* dperpeet
* dperpeet and jds2001 will discuss UX design for NFS role with
Cockpit designers
* jds2001
* dperpeet and jds2001 will discuss UX design for NFS role with
Cockpit designers
* **UNASSIGNED**
* (none)
People Present (lines said)
- ---------------------------
* sgallagh (81)
* dperpeet (55)
* zodbot (16)
* adamw (7)
* jds2001 (5)
* vvaldez (5)
* smooge (4)
* dustymabe (3)
* mhayden (3)
* nirik (1)
* mjwolf (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
-----BEGIN PGP SIGNATURE-----
Version: Mailvelope v1.5.2
Comment: https://www.mailvelope.com
wkYEAREIABAFAlg99uwJEHolVWI2uqOjAACABwCgr1M3nCrihNWrw+nV99y6
QC8A518AoJ5XVqCRJ/4kACeOohx0HGDWlgXJ
=Bup6
-----END PGP SIGNATURE-----
I don't have anything specific, so I'll run an Open Floor meeting today. If you
have any particular topics to bring up, please let me know and I'll make sure we
have time for it.
Hi everybody,
as discussed in [1] email thread, we are starting the "Fedora
Prioritized bugs and issues process" [2]. The main goal is to identify
and make more visible bugs and issues which have critical impact on a
Fedora Edition or on a council-approved Fedora Objective.
We will start with our first evaluation meeting on Wednesday November
the 30th, 2016 at 15:00 UTC on #fedora-meeting IRC channel [3].
I will be happy if people interested in participation on the
evaluation will let me know, so we can setup the initial Evaluation
team.
[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
[2] https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_a…
[3] https://apps.fedoraproject.org/calendar/Fedora%20release/2016/11/28/#m5154
Regards,
Jan
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
Hey folks,
[This is slightly off-topic, but it's related to direction of using
redhat/fedora systems as servers, so I figured there may be interest here.]
At systemd.conf this year we met a bunch of people who were interested in
our (Facebook) work to backport rawhide's systemd to CentOS 7 (see our talk
https://www.youtube.com/watch?v=LhYd0S3qiMY) we've released the repo of specs
and diffs that make this possible here:
https://github.com/facebookincubator/rpm-backports
We hope to add more here over time (we're working on releasing initscripts
backports now). We keep this repo in sync with our internal tools, so as the
targeted software moves forward in rawhide, you should see the repo keep up.
Feel free to email me on or off list as appropriate if you have
questions/comments.
--
Phil Dibowitz phil(a)ipom.com
Open Source software and tech docs Insanity Palace of Metallica
http://www.phildev.net/http://www.ipom.com/
"Be who you are and say what you feel, because those who mind don't matter
and those who matter don't mind."
- Dr. Seuss
I'd like some feedback on a (very early) draft that I have of the
document for the NFS role definition (if you'd like edit access, just
shoot me an email):
https://docs.google.com/document/d/1jLyKsECdHdlKltmHGgf_-iOKj-hj4Qjbh5Zgm7a…
How I thought of this was to go from user stories, to technical
requirements, and finally to activities to meet those requirements.
The actor in all of the user stories in an inexperienced admin - are
there other actors that we need to be concerned with?
Totally open to feedback here - is this even on the right path?