server June 2022

server@lists.fedoraproject.org

10 participants
12 discussions

Docs - NFS Server
by Jason Beard 28 Jun '22

28 Jun '22

Greetings. In regard to the NFS Docs below is a rough installation procedure for NFS Server. The cockpit NFS should come later this week. While creating this rough installation guide I think it would be easier to update the doc site instead of cut and pasting it several times into email. We can just send out emails saying they are updates. There might be a mechanism in place on the docs web site that does it already. I have no problem doing it that way so long i have access to update the docs page. Let me know. Here's the rough out line for NFS server from command line. -------------------------------- NFS Server Install Network File Server, or NFS for short, is a client and server file system. NFS versions NFSv2 - 32 bit files sizes and offsets, udp, no longer used. NFSv3 - 64 bit files sizes and offsets, improved write performance, supports asynchronous, requires rpcbind to be running. NFSv4 - no longer requires rpcbind, performance improvements, security improvements, introduces stateful protocol 4.1 - added support for clustered server deployments, added ability for scalable parallel access, multipathing, pNFS. 4.2 - server side improvements (server side clone and copy), security updates, added features ti pNFS. Recommend NFSv4.x as it only requires UDP or TCP port 2049 to be open. This makes it easier when needing to connect through a firewall. Planning: Make sure to have a static hostname and IP set for the NFS server. *Note A static IP isn't required but the DHCP server should have the ability to update DNS or connectivity issues will happen. It's preferred to set a static hostname and IP. It's recommended to use a separate disk or file system for shares. This will ensure that you don't fill up your Operating System file systems. Installing: Config Files: Most Used /etc/nfs.conf /etc/exports Others /etc/exports.d /etc/gssproxy/24-nfs-server.conf /etc/modprobe.d/lockd.conf /etc/nfsmount.conf /etc/request-key.d/id_resolver.conf Steps to Install 1. Make sure the OS is up to date. (reboot if necessary before continuing on) sudo dnf update 2. Install the software needed. sudo dnf install nfs-utils 3. Start the server. sudo systemctl enable nfs-server --now 4. Confirm its running. sudo systemctl status nfs-server 5. Make sure to add the appropriate services/ports to the firewall. This one is needed for all NFS versions. sudo firewall-cmd --add-service=nfs These are needed to support NFSv3. sudo firewall-cmd --add-service=mountd sudo firewall-cmd --add-service=rpc-bind Save the firewall configuration so it persistent across reboots. sudo firewall-cmd --runtime-to-permanent 6. Setup a directory to share. mkdir /share/share1 chmod -R 755 /share/share1 7. Add the directory to /etc/exports This is were you setup the share for access and any options you want to use. sudo vi /etc/exports # any editor will do Example: /share/share1 client.example.com(rw,no_root_squash) *Note* The /etc/exports file has a specific format. <export> <host><options> 8. After updating /etc/exports run the exportfs to make it available. exportfs -av # -a export or unexport all directories # -v verbose 9. To display the epxorts run exportfs with a different option. exportfs -s Server is ready. Now setup the client. 1. Make sure the OS is up to date. (reboot if necessary before continuing on) sudo dnf update 2. Install the software needed. sudo dnf install nfs-utils 3. See if the sever can mount it. (If using NFSv3 you can showmount -e nfsserver.example.com but it requires rpcbind) mount -t nfs nfsserver.example.com:/share/share1 /mnt *If the command comes back with no errors its mounted. *You can check by running mount with no options. mount cd /mnt touch file # ls file 4. You can see the mount options with just by running mount. mount | grep mnt nfsserver.example.com:/share/share1 on /mnt type nfs4 (rw,relatime,vers=4.2,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.0.0.1,local_lock=none,addr=10.0.0.2) *Note* When Fedora Server is the NFS server it defaults to NFSv4.2.

1 0

Cockpit 272 released
by Matej Marusak 23 Jun '22

23 Jun '22

Hi all, as my pilot duty dictates, I am happy to announce that there is a new Cockpit release! Here are release notes from Cockpit 272: https://cockpit-project.org/blog/cockpit-272.html Users can now edit firewall services and favorite systemd units! And we are one step closer in regards to the dark theme! Have a nice day! MM -- Matej Marušák Associate Manager Red Hat <https://www.redhat.com> <https://red.ht/sig>

1 0

INFO: Server VM change approved
by Peter Boy 22 Jun '22

22 Jun '22

Just for information: FESCo approved our change proposal for F37 to provide a Server VM distributable. https://pagure.io/fesco/issue/2807 https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… ================================================================================= Our next IRC meeting will be on the 1st Wednesday of July, which is July 6, 2022. So we have a 3 weeks gap between our meetings again due to calendar peculiarities =================================================================================

1 0

Short info about yesterday's IRC meeting (2022-06-15)
by Peter Boy 16 Jun '22

16 Jun '22

1 0

[Fedocal] Reminder meeting : Fedora Server WG
by pboy＠fedoraproject.org 14 Jun '22

14 Jun '22

Dear all, You are kindly invited to the meeting: Fedora Server WG on 2022-06-15 from 17:00:00 to 18: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/10244/

1 0

Call for agenda Items on 2022-06-15 17:00 ==UTC== meeting
by Peter Boy 13 Jun '22

13 Jun '22

The meeting date ========================================================= Fedora Server IRC meeting Wednesday, June 15 17:00 ==UTC== irc.libera.chat #fedora-meeting ========================================================= Please, check your local time using date -d '2022-06-15 17:00UTC' The agenda includes so far: == Agenda == https://pagure.io/fedora-server/report/Meeting 1. = Follow up actions = 2. = Further processing of GPT as default partitioning switch = We have currently no issue for this topic. Mail list thread: #link https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… Goal: Agreement on the further course of action 3. = Test planning for Fedora 37 = We have currently no issue for this topic. Proposal: We should aim for a test week with Fedora QA and make this a permanent practice for the next releases. 4. = How to proceed with Cockpit File Sharing module (continued)= #link https://pagure.io/fedora-server/issue/86 Last meeting our time was up. As discussed I created 2 documentation stub regarding the NFS part that we needs to complete https://docs.stg.fedoraproject.org/en-US/fedora-server/service-filesharing-… https://docs.stg.fedoraproject.org/en-US/fedora-server/service-filesharing-… 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 Vor an overview about previous meetings: https://docs.fedoraproject.org/en-US/server-working-group/wg-minutes-curren…

1 0

Current status GPT default and sw raid
by Peter Boy 11 Jun '22

11 Jun '22

Hi, some topics to consider / discuss: (a) I performed some testing with F36 and found: SW raid on MBR works fine, in a raid 1 I could put off either of the disks and the system booted fine. SW raid on GPT doesn’t work as already stated. There is a bug report for it. So nothing to do at the moment. (b) I performed some testing with F36 and UEFI boot and SW raid. It doesn’t work as we already guessed. For a user, the error is similar to the one with GPT and Biosboot. I will create a test description as an issue for this. Based on our experience with the GPT discussion, it would make sense to also create a Bugzilla entry at the same time. Do we want to do that now, or rather wait until the GPT/biosboot problem is solved, in order not to risk even more confusion after all? (c) We had some discussion to create a universal boot configuration combining GPT/biosboot and PGT/uefi. I think, it is too late to make the move for F37 anyway. But do we want do discuss that topic now for F38 or do we want to wait until the aforementioned issues are resolved and discuss it together with the planned review of our installation media (see #88 https://pagure.io/fedora-server/issue/88)? I would like to discuss the latter 2 topics now and find an agreement how to proceed. And then we should do our best to proceed together as agreed. Best Peter

1 0

do you use systemd's forward-sealing feature?
by Matthew Miller 08 Jun '22

08 Jun '22

This thread will be of interest! https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

Short info about today's IRC meeting (2022-06-01)
by Peter Boy 06 Jun '22

06 Jun '22

Again, for everyone's convenience, a brief summary of our IRC meeting right here. For greater details see meetbot == Summary: == https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-06… == Full log: == https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-06… Topics discussed: === Follow up actions === DONE: Post on devel list thread F37 proposed change to GPT as default partitioning schema about the regression regarding software raid installations. DONE: Created an issue containing 2 test cases for biosboot GPT software raid installations https://pagure.io/fedora-server/issue/87 DONE: created a stub of NFS server installation and Cockpit for administration ONGOING: Created Change proposal to add Server VM is still processing ONGOING: Discussion about changes around the default hostname configuration ONGOING: Review of the dnsmasq documentation by eseyman === Change proposal about GPT as default partitioning for bios boot === Discussion: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.or… FESCo has accepted the Change Proposal without discussion. We now have the problem of preserving our users from harm unfortunately done intentionally or, at best, negligently by some of our own members who are owners of the Change Proposal. Unfortunately, the perpetrators do now not care how harm can be averted from our users with Release 37 and do not even bother to attend the meeting on this topic to find a suitable resolution if the issue. Stephen Gallagher started a process to qualify the Anaconda software raid bug as a blocker to the GPT Change Proposal. If accepted by QA as a blocker, it will have to be fixed (or the Change reverted) in order to ship Fedora. This would be a perfect and constructive solution. Agreed: Server WG agrees with sgallagh’s suggestion to block the GPT change until the Anaconda issue is resolved and considers it as most essential. === Planning for Fedora 37: Additional changes to discuss? (continued) === For part of the discussion we have a new tracking issue: #88. It summarizes all the individual measures that we have discussed for improvement and entail an adjustment of the installation media. Agreed: Issue #88 is postponed to F38, due to current tasks and limited resources. === How to proceed with Cockpit File Sharing module NFS part === Due to the elapsed time further preparatory discussion via e-mail.

5 11

GPT Partitioning
by Peter Boy 03 Jun '22

03 Jun '22

Last meeting we discussed whether we should change to GPT as default partitioning. Now some of our members have submitted a change proposal to make GPT the default partitioning for new installations. I think this is actually long overdue, yet better communication among us would actually be nice as well. https://fedoraproject.org/wiki/Changes/GPTforBIOSbyDefault I don’t know if there is a potential problem. Some time ago, if I remember correctly it was Neil who wrote in a discussion about storage that a software RAID is no longer possible, because - so my memory - the biosboot partition is not replicable over multiple disks. So if the previous boot disk fails, you can't just boot from another disk. I never checked it and didn’t read the technical specification. And all our server have hardware raid. So, does anybody knows about it in detail? Peter

6 19

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server June 2022