# 20211006_Fedora-CoreOS-Virtual-Meeting location: https://meet.google.com/cgh-oxhd-axg ### Agenda #### Roll Call Add your name and involvement/interest in FCOS here: - Dusty Mabe - dusty@dustymabe.com - FCOS/RHCOS team at Red Hat - Benjamin Gilbert - bgilbert@redhat.com - FCOS/RHCOS team at Red Hat - Robert Volkmann (ConSol Software GmbH) - Jan Kuparinen - copperi@fedoraproject.org - Jaime Magiera (University of Michigan) - Luca Bruno - lucab@redhat.com - Timothée Ravier - FCOS/RHCOS team at Red Hat - Harshal Patil - harpatil@redhat.com - OpenShift Core Node team at Red Hat - Jonathan Lebon - jonathan@jlebon.com - FCOS/RHCOS team at Red Hat - Renata Ravanelli - rravanel@redhat.com - FCOS/RHCOS team at Red Hat - Micah Abbott - miabbott@redhat.com - FCOS/RHCOS team at Red Hat - Marc Pusey (Columbia University) - Christian Glombek - OpenShift/OKD at Red Hat - Blaise Pabon #### Action items from last meeting - dustymabe to talk to sumantro to try to get FCOS testing on the week of oct 11 - **update**: test day/week has been moved to the week of oct 11 - dustymabe to schedule some time on Monday to identify docs test cases and prepare for F35 test day - **update**: we had a strategy session on Monday - notes in: https://hackmd.io/CCPFamtAQC6GA6hY7NDhFA - lorbus and jlebon to reach out to the containers team to discuss what cri-o versions will be supported and how at the modular level to pull it off (context: https://github.com/coreos/fedora-coreos-tracker/issues/767) - **update**: https://github.com/coreos/fedora-coreos-tracker/issues/767#issuecomment-934448876 - jlebon to add some design details to the proposal in the ticket (#676) and also reach out to dghubble to see if this can be handled in typhoon - **update**: dghubble seemed OK with the stamp file idea and we just need to nail down the exact details for migration - see https://github.com/coreos/fedora-coreos-tracker/issues/676#issuecomment-930505707 and following #### upstream k8s node e2e testing with FCOS - link: https://github.com/coreos/fedora-coreos-tracker/issues/984 - Notes: - harshal works for the openshift node team - another team known as RHCOS within openshift (downstream of FCOS) - goal is to make sure upstream kubelet works with RHCOS/FCOS all the time - other CI infra managed by google is focused on Ubunutu and Container Optimized OS - asked if we could support another runtime (cri-o) - had to choose an OS for this and FCOS was closest to RHCOS and available in GCP - goal is to have tests that fail on FCOS be release blocking - https://testgrid.k8s.io/sig-node-cri-o#ci-crio-cgroupv1-node-e2e-conformance - https://testgrid.k8s.io/sig-node-cri-o#ci-crio-cgroupv2-node-e2e-conformance - https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-node/crio.yaml - https://github.com/cri-o/cri-o/blob/main/scripts/node_e2e_installer - they are currently "release informing" status and eventually become release blocking - currently using latest FCOS stable for these tests (via GCP image family) - jlebon: where are pulling cri-o from? - cri-o gets pulled from a specific upstream commit - google's test infra for k8s will SSH into the node to set it up for CI testing - thus, ignition is used for minor provisioning. SSH used for all else - lucab: do the FCOS machines have zincati auto-updates enabled by default? - node test is about 20-25m; does not appear to be disabled - **TODO**: disable auto-updates on the nodes - jlebon: could we run the cri-o tests on the FCOS config repo? i.e. test each change to FCOS - yes; would be one VM per k8s version. may need to massage some of the tests to work outside of the google infra. - dustymabe: any specific issues on FCOS that has impacted the cri-o tests? - nothing specific to FCOS; more generic issues related to running on something that's not Google's OS - #### Devconf.cz CFP - link: https://github.com/coreos/fedora-coreos-tracker/issues/988 - Notes: - Christian: will submit a talk for OKD to devconf.cz #### Re-visit Fedora CoreOS Goals - link: https://hackmd.io/h3qv7mn4RDKd_n50ANdqxw #### Open Floor - fifofonix: you are doing great work and we are using it successfully at Columbia 🎉 - challenges around getting Nvidia driver support in FCOS for ML/AI workloads - need better access to kernel-headers, deps for building - dusty says you should be able to pull headers/source for any kernel build from koji - fedora doesn't always rebuild the kernel-headers when the kernel package itself is rebuilt - jaimelm: helpful to get the walkthrough of coreos-assembler 🎉 - dusty suggests improving the upstream on-boarding docs/tutorials - blaise: fedora is where i go to find out how to do things right 🎉