server February 2021

server@lists.fedoraproject.org

15 participants
20 discussions

Is there a chance to get these 2 selinux bugs finally resolved for F34?
by Peter Boy 27 Feb '21

27 Feb '21

Question to our Fedora Server QA experts. There are 2 annoying selinux bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1900869 https://bugzilla.redhat.com/show_bug.cgi?id=1900888 They prevent the automatic start of systemd-nspawn containers. A distinguishing feature of Server is universality and adaptability to local requirements. Hence the support of not only one mainstream container solution, but also alternatives (and especially annoying, with Debian selinux it works). You can work around these bugs easily following the usual SELinux troubleshooting procedure. You have to add 5 or 6 rules. I guess troubleshooting can't be that time-consuming and complex. Especially since the tests for F34 are running anyway? Not giving up hope Peter

4 5

Update member list
by John W. Himpel 26 Feb '21

26 Feb '21

All, I tried to Log In to the wiki to update my page using my FAS credentials. However, it keeps responding "Fatal error authenticating user". Are there additional credential required? Thanks. name: John Himpel fas: jwhimpel

2 1

Update member list
by Peter Boy 26 Feb '21

26 Feb '21

I just updated the member list of Server WG according to the IRC yesterday (2021-02-17, https://meetbot.fedoraproject.org/fedora-meeting/2021-02-17/fedora-server.2…) Please check if everything is OK. Each member should create at least a minimal wiki page with contact details. A link to the Fedora Project Wiki is automatically generated by the wiki template. The following automatically generated links still end up in the void: https://fedoraproject.org/wiki/User:Abbra https://fedoraproject.org/wiki/User:Jwhimpel https://fedoraproject.org/wiki/User:Sghosh https://fedoraproject.org/wiki/User:Astra

2 1

Re: Fedora Server Documentation
by Peter Boy 25 Feb '21

25 Feb '21

> Am 25.02.2021 um 18:07 schrieb Jan K <copper_fin(a)hotmail.com>: > > I recently did some technical reviews on quick-docs, one for apache, should those docs be linked to the wiki page? (That is first that came to mind, loads of info and docs exists). Yes, Web server is a definitely a service/application which is installed on Fedora Server. I think, we should not reinvent the wheel, so we should link from Server documentation to quick docs in this case. We should note down what and where existing information is stored to get an overview and don’t do „reinvention“ accidentally. > Do you have a link to the meeting mentioned ? The links are on our Wiki Page (https://fedoraproject.org/wiki/Server) at the bottom. Most of the ideas came out of the December meeting. Please remember, the docu-wiki page is not for documentation itself, but to support the organisation of work. Please, feel free to join the team and add ideas to the page (such as collecting documentation already available elsewhere in Fedora universe).

1 0

Fedora Server Documentation
by Peter Boy 25 Feb '21

25 Feb '21

I started a documentation page as part of our wiki to collect ideas and compose a working plan (https://fedoraproject.org/wiki/Server/Documentation). Besides authoring, a number of other skills and contributions are necessary to make it get off the ground: (technical) reviewers, proof readers, administrators for build pipeline, etc. Please check what you could contribute. There were a lot of ideas at the last IRC meetings.

2 1

Call for Agenda Items on 2020-03-03 18:00 UTC meeting
by Stephen John Smoogen 25 Feb '21

25 Feb '21

Hi I am wanting to get an agenda for next week's meeting. Currently I have 1. Welcome All 2. Agenda 3. Status Reboot Server Working Group 4. Introduce Dusty Mabe from Cloud Group 5. Work needed for Fedora 34 beta 6. PRD Update 1.5 round of discussion 7. Documentation update. 8. Open Floor 9. Close -- Stephen J Smoogen.

2 1

mailing list ownership
by Dan Horák 25 Feb '21

25 Feb '21

Hi, with the new efforts to restart the Server WG/SIG it would make sense to move the ownership for this mailing list to someone active in the new WG/SIG. Me with Stephen Gallagher are the current owners, so if you could come up with a new name, I can add that person as owner (and remove myself). Thanks, Dan

3 3

F33 systemd-resolved not working friendly with libvirt virbr0
by Peter Boy 25 Feb '21

25 Feb '21

I'm testing update my servers from F32 to F33. Situation is: Fedora Server running several Fedora VMs. VMs and host are using libvirt default network via virbr0 for internal private data exchange. A second public bridge provides external connectivity. On virbr0 the DNS service is activated so host and VMs can find each other via name instead IPs. In F32 I used NetworkManagers dnsmasq plugin to forward internal request (names ending .lan) to libvirt dnsmasq on virbr0 / 192.169.122.1 and everything else to our public DNS. With F33 I'm to use systemd-resolved which is dns-split capable. The F33 VMs, which have 2 fixed interfaces eht0 (public) and eth1 (private), everything works out of the box without a hitch. On the F33 Server I had to add two entries to /etc/systemd/resolved.conf: DNS=192.168.122.1%virbr0#example.lan ## (.lan = private domain) Domains=example.lan ## search domain, appended to names w/o a dot After a reboot it only works after I restart systemd-resolved. Otherwise it fails to resolve internal names / addresses. My "trusted search engine" showed some discussion but no solution (at least I couldn't identify one). Any help much appreciated. Peter What I did: [...]# reboot [...]# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 .... 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 ... //external interface 3: vbr3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 ... // external routin bridge (brouter) 4: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8000 qdisc noqueue state UP group default qlen 1000 ... // internal bridge 5: virbr0-nic: <BROADCAST,MULTICAST> mtu 8000 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 ... // virtual interface host to virbr0, no IP addres of its own 6: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master vbr3s0 state UNKNOWN group default qlen 1000 ... // virtual public interface VM 7: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8000 qdisc fq_codel master virbr0 state UNKNOWN group default qlen 1000 ... // virtual private interface VM [...]# resolvectl domain Global: example.lan Link 2 (enp3s0): example.com ~. Link 3 (vbr3s0): Link 4 (virbr0): Link 5 (virbr0-nic): Link 6 (vnet0): Link 7 (vnet1): [...]# resolvectl dns Global: Link 2 (enp3s0): 213.133.98.98 213.133.99.99 2a01:4f8:0:1::add:1010 2a01:4f8:0:1::add:9999. ## our external name server Link 3 (vbr3s0): Link 4 (virbr0): ## no sign of libvirt dnsmasq server Link 5 (virbr0-nic): Link 6 (vnet0): Link 7 (vnet1): [...]# resolvectl query vm vm: aaa.bbb.ccc.dd -- link: enp3s0 ## /external name, instead internal 2a01:aaa:bbb:ccc::4 -- link: enp3s0 (vm.example.com) [...]# resolvectl query vm.example.lan vm.example.lan: resolve call failed: 'vm.example.lan' not found When I restart systemd-resolved: [...]# systemctl restart systemd-resolved [...]# resolvectl domain Global: example.lan Link 2 (enp3s0): example.com ~. Link 3 (vbr3s0): Link 4 (virbr0): Link 5 (virbr0-nic): Link 6 (vnet0): Link 7 (vnet1): ## everything as before, nothing changed [...]# resolvectl dns Global: Link 2 (enp3s0): 213.133.98.98 213.133.99.99 2a01:4f8:0:1::add:1010 2a01:4f8:0:1::add:9999. ## our external name server Link 3 (vbr3s0): Link 4 (virbr0): Link 5 (virbr0-nic): Link 6 (vnet0): Link 7 (vnet1): ## everthing as before, nothing changed here, too [...]# resolvectl query vm vm: 192.168.122.87 -- link: virbr0 (vm.example.lan) ## different, internal address as expected [...]# resolvectl query vm.example.lan vm.example.lan: 192.168.122.87 -- link: virbr0. ## internal address, as expected.

2 2

Cockpit 238 released
by Katerina Koukiou 18 Feb '21

18 Feb '21

Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from Cockpit version 238: https://cockpit-project.org/blog/cockpit-238.html Summary: - Updates: List outdated software that needs a restart - Web server: Preserve permissions of administrator-provided certificates - System: Performance page shows busiest CPU cores - Machines: Machines: VM disk creation supports a custom path You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 238 is available in Fedora 32, 33 and 34: https://bodhi.fedoraproject.org/updates/FEDORA-2021-f98214dae5 https://bodhi.fedoraproject.org/updates/FEDORA-2021-bf4a30e37d https://bodhi.fedoraproject.org/updates/FEDORA-2021-db6f42b9df Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/238 Take care, Katerina

1 0

Info about IRC meeting 2021-02-17 and work to be done
by Peter Boy 18 Feb '21

18 Feb '21

Again, for all of us lazy people, I'll briefly summarise the most important topics of the IRC discussions right here. For greater details see meetbot Summary: https://meetbot.fedoraproject.org/fedora-meeting/2021-02-17/fedora-server.2… Log: https://meetbot.fedoraproject.org/fedora-meeting/2021-02-17/fedora-server.2… 1. Status Reboot Server Working Group According to voting on ticket #6 and #9 we have the following new members: @langdon Langdon White @abbra Alexander Bokovoy @salimma Michel Alexandre Salim @astra David Kaufmann @jwhimpel John Himpel @sghosh Subhendu Ghosh @jbwillia Ben Williams @x3mboy Eduard Lucena @pboy Peter Boy @nb Nick Bebout (In order of ticket entries). Ngompa became a member some time ago but wiki page was not updated (testified by sgallagh) and is now added as well. Agreed: chair (pboy) will update wiki. (a) chair term Agreed: WG sticks to it, the chair is determined for each of the next meetings. (b) nolonger active members Agreed: chair (pboy) will make contact and ask (c) Additional memberships Unfortunately skipped accidentally. Must be discussed at the next meeting. (d) SIG pages The relationship between SIG and WG is being discussed in various ways. Currently, "Team" is being discussed throughout Fedora as a new formation (bcotton). Agreed: Mark as outdated for the time being and archive content. Pboy will modify. 2. Work programme for the coming year Agreed: * Build up new documentation („Server Box“ on docs.fedoraproject.org) * Explore opportunities for cooperation with Cloud * revisiting defaults... filesystem/partitioning 3. PRD Update Running out of time, Postponed to next meeting Next Meeting: Wednesday, 3 March 2021, 18:00 UTC(!) chair: smooge NOTE: I already update wiki member list. Please check! I preliminarily removed mjwolf, no FAS account anymore, no mail address known. Please review as well.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

server February 2021