# 20220504_Fedora-CoreOS-Virtual-Meeting location: https://meet.google.com/meo-enbb-rur?hs=224 ### Agenda #### Roll Call Add your name and involvement/interest in FCOS here: - Aashish Radhakrishnan - aaradhak@redhat.com - FCOS/RHCOS team at Red Hat - Micah Abbott - miabbott@redhat.com - CoreOS at RedHat - Dusty Mabe - dusty@dustymabe.com - FCOS/RHCOS team(s) at Red Hat - Luca Bruno - lucab@redhat.com - CoreOS at RedHat - Renata Ravanelli - rravanel@redhat.com - FCOS/RHCOS team - Jonathan Lebon - jonathan@jlebon.com - FCOS/RHCOS team at Red Hat - Jason Brooks jbrooks@redhat.com - Red Hat OSPO - Marc Pusey - fifofonix@gmail.com - Columbia University - Brian Tomlinson - btomlins@redhat.com - Principal Architect at Red Hat - Saqib Ali - saqali@redhat.com - CoreOS at RedHat #### INFO #### Action items from [last meeting](https://meetbot-raw.fedoraproject.org/fedora-meeting-1/2022-04-27/fedora_coreos_meeting.2022-04-27-16.30.txt) No action items from last meeting! #### Automated Fedora CoreOS 35 for Raspberry Pi 4(B)/400 Brian Tomlinson will join us to discuss his project that automated bringup on the Raspberry Pi 4. This was originally shared with the community in a [discussion forum post](https://discussion.fedoraproject.org/t/automated-fedora-coreos-35-for-raspberry-pi-4-b-400/38359). See also: - https://github.com/darthlukan/ignition-configs - https://microshift.io/docs/getting-started/ Link on how to package layer via Ignition: - https://docs.fedoraproject.org/en-US/fedora-coreos/os-extensions/ #### Continued Discussion About nmstate link: https://github.com/coreos/fedora-coreos-tracker/issues/1175 #### coreos autoinstall creates huge number of xfs allocation groups link: https://github.com/coreos/fedora-coreos-tracker/issues/1183 - CW: doubt we are going to get any XFS changes upstream to fix this problem - CW: proposal to autodetect this and correct it automatically by reprovisioning the rootfs - DM: should we autodetect or just put something in the MOTD? - LB: MOTD warnings don't scale well typically, and not everyone is looking - LB: if the workflow is coreos-installer then we could warn the user - JL: the machine is still functional, it's just not optimal EDIT: in some cases the machine can't mount the FS at all - JL: if we somehow detect that we can't reprovision the rootfs we should continue and not fail boot - CW: should we potentially create a /var partition by default for disks that are larger than a certain size - LB: we could grow the root filesystem but not past the amount that would cause the degradation described by this issue - LB: should XFS tools fail if the user asks it to grow to an amount that will lead to this #### Any other topics? [SELinux Policy Modifications Again](https://github.com/coreos/fedora-coreos-tracker/issues/701) [Develop strategy around organization and naming for our containers in quay.io](https://github.com/coreos/fedora-coreos-tracker/issues/1171) #### Open Floor