Fedora CoreOS Meeting Minutes 2020-02-26
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-26/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-26/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-26/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:30:50 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-26/fedora_core...
.
Meeting summary
---------------
* roll call (dustymabe, 16:30:54)
* Action items from last meeting (dustymabe, 16:33:58)
* cosa/mantle integration (dustymabe, 16:36:06)
* LINK: https://github.com/coreos/coreos-assembler/issues/163
(dustymabe, 16:36:19)
* we're evaluating merging the mantle repo into coreos-assembler as
the line between the two is blurring. With container linux going
away the need to have them sepearate is even less. See
https://github.com/coreos/coreos-assembler/issues/163 (dustymabe,
16:42:12)
* Request for usbguard package inclusion (dustymabe, 16:44:04)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/326
(dustymabe, 16:44:11)
* LINK: https://github.com/openSUSE/transactional-update#caveats is
basically all stuff rpm-ostree fixes (walters, 16:57:04)
* AGREED: usbguard fits into a category of small OS utility/daemon
that is not easy or desirable to containerize but is also not
something we immediately want to include in the host because if we
include every utility/daemon we end up with a kitchen sink OS. We'd
like to develop a framework for "reliable extensions" that we can
use to deliver usbguard and other utilities/daemons (dustymabe,
17:12:31)
* ACTION: dustymabe to create issue to discuss possibilities for a
"reliable extensions" framework (dustymabe, 17:12:58)
* Add factory reset capability (dustymabe, 17:13:47)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/399
(dustymabe, 17:13:51)
* all seem to be in agreement that factory reset would be nice to
have.. there are a few different options for how to go about doing
that. bgilbert will add them to ticket #399 (dustymabe, 17:31:57)
* open floor (dustymabe, 17:32:24)
* we did a new FCOS release for testing and stable starting today
(dustymabe, 17:33:21)
* we migrated our production fedora ostree repos into a netapp volume
to be accessed via various openshift projects that our teams will
use to do automated imports and prunes of OSTree commits for Fedora
CoreOS (dustymabe, 17:34:42)
Meeting ended at 17:37:06 UTC.
Action Items
------------
* dustymabe to create issue to discuss possibilities for a "reliable
extensions" framework
Action Items, by person
-----------------------
* dustymabe
* dustymabe to create issue to discuss possibilities for a "reliable
extensions" framework
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (89)
* bgilbert (45)
* jlebon (33)
* walters (29)
* zodbot (21)
* lorbus (9)
* jdoss (5)
* ksinny (5)
* cyberpear (4)
* darkmuggle (3)
* otaylor (2)
* miabbott (2)
* mnguyen_ (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 7 months
coreos-installer mount device pre-installation
by Joel Kessler
Hi there,
Another question. This time related to the installation of fedora coreos.
My current goal is to install a bare metal machine completely offline, meaning I would like to run:
> coreos-installer install /dev/nvme0n1 --image-file /mnt/insdev/fedora_coreos.raw.xz --ignition /mnt/insdev/ignition.ign
This works without a doubt when I manually pre-mount my installation device (live iso) like this:
> sudo mkdir /mnt/insdev
> sudo mount -t auto -v /dev/sdb1 /mnt/insdev
(And then the installer install command)
But in my scenario I would like to have this fully automated. Therefore I tried to execute the mkdir and mount command on the grub.cfg file level.
> linux /images/vmlinuz mitigations=auto,nosmt systemd.unified_cgroup_hierarchy=0 coreos.liveiso=fedora-coreos-31.20200113.3.1 rd.neednet=1 ip=dhcp ignition.firstboot ignition.platform.id=metal coreos.inst.ignition_url=/mnt/insdev/ignition.ign coreos.inst.install_dev=/dev/nvme0n1 coreos.inst.image_url=/mnt/insdev/fedora_coreos.raw.xz coreos.inst=yes coreos.inst.insecure
My assumption is that this mounting would be required to be run on the /vmlinuz. Is there any way to tell the kernel to mount this device automatically to my defined location, so I can achieve my goal?
In the end my installation process should look like this:
> Create iso (from official live iso)
> Add folder on usb stick
> Copy required install files in folder
> Boot from iso, which automatically triggers coreos install
3 years, 7 months
Filesystem which stays on reinstall on same physical device as the installation
by Joel Kessler
Hello there,
Question related to the file system setup of fcos.
I defined a partition within ignition on the install device.
disks:
- device: /dev/nvme0n1
wipe_table: false
partitions:
- label: DATA
start_mib: 0
number: 0
size_mib: 10240
As well as the filesystem:
filesystems:
- device: /dev/disk/by-partlabel/DATA
format: ext4
path: /mnt/data
wipe_filesystem: false
label: data
My goal would be that after the setup my disk looks like this:
The reason for putting my own partition in front of the system partitions, would be that if I re execute ignition on this device
the defined partition should not be erased and possible to expand with a new ignition file. The sysroot partition should get all the remaining space.
nvme0n1 259:0 0 238.5G 0 disk
|-nvme0n1p1 259:5 0 10G 0 part /mnt/data
|-nvme0n1p2 259:1 0 384M 0 part /boot
|-nvme0n1p3 259:2 0 127M 0 part /boot/efi
|-nvme0n1p4 259:3 0 1M 0 part
|-nvme0n1p5 259:4 0 225.8G 0 part /sysroot
But because of some it currently looks like this. When adding the filesystems as defined above my ignition will fail on first boot.
nvme0n1 259:0 0 238.5G 0 disk
|-nvme0n1p1 259:1 0 384M 0 part /boot
|-nvme0n1p2 259:2 0 127M 0 part /boot/efi
|-nvme0n1p3 259:3 0 1M 0 part
|-nvme0n1p4 259:4 0 2.1G 0 part /sysroot
`-nvme0n1p5 259:5 0 10G 0 part
If I would run it with just the disks defined I can run the ignition but the file system will be erased each time.
I tested it by manually adding the filesystem: sudo mount -t auto -v /dev/nvme0n1p5 /mnt/data
this will return an error and expects me to redo: mkfs.ext4 /dev/nvme0n1p5
Is there any way to define a partition which won't get lost after a re execution of ignition?
3 years, 7 months
Fedora CoreOS Meeting Minutes 2020-02-19
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-19/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-19/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-19/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:29:12 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-19/fedora_core...
.
Meeting summary
---------------
* roll call (dustymabe, 16:29:18)
* Action items from last meeting (dustymabe, 16:33:43)
* ACTION: dustymabe to work with x3mboy on FCOS infographic
(dustymabe, 16:34:07)
* dustymabe added discussion/use case notes to the wireguard tools
ticket:
https://github.com/coreos/fedora-coreos-tracker/issues/362#issuecomment-5...
(dustymabe, 16:35:15)
* Publish the initrd and rootfs images separately for PXE booting
(dustymabe, 16:37:15)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/390
(dustymabe, 16:37:28)
* F32 rebase tracker for changes discussion (dustymabe, 16:52:40)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/372
(dustymabe, 16:52:45)
* LINK: https://fedoraproject.org/wiki/Releases/32/ChangeSet
(dustymabe, 16:54:08)
* open floor (dustymabe, 17:09:41)
* we are really close to having automatic ostree commit import working
(dustymabe, 17:10:03)
Meeting ended at 17:16:53 UTC.
Action Items
------------
* dustymabe to work with x3mboy on FCOS infographic
Action Items, by person
-----------------------
* dustymabe
* dustymabe to work with x3mboy on FCOS infographic
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (76)
* jlebon (20)
* cyberpear (15)
* zodbot (11)
* walters (9)
* ksinny (5)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 7 months
Fedora CoreOS Meeting Minutes 2020-02-12
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-12/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-12/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-12/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:29:29 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-02-12/fedora_core...
.
Meeting summary
---------------
* roll call (dustymabe, 16:29:35)
* Action items from last meeting (dustymabe, 16:34:46)
* ACTION: dustymabe to work with x3mboy on FCOS infographic
(dustymabe, 16:35:25)
* dustymabe created #372 to discuss the f32 rebase and major changes
we'd like to make (dustymabe, 16:35:59)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/372
(dustymabe, 16:36:04)
* dustymaber opened a releng ticket to try to start a discussion about
making rust packaging experience better:
https://pagure.io/releng/issue/9229 (dustymabe, 16:36:40)
* LINK: https://pagure.io/releng/issue/9229 (dustymabe, 16:36:45)
* support for cgroupsv2 was added to containerd. the basics were added
to moby-engine recently. but there's still a bunch of things left to
implement (jlebon, 16:37:18)
* LINK: https://pagure.io/koji/issue/1998 (ignatenkobrain, 16:38:41)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/371
(cyberpear, 16:40:12)
* mnguyen_ emailed moby-engine maintainer for an update, but no
response yet (dustymabe, 16:40:57)
* cyberpear opened a ticket to discuss including fcct in the initramfs
#371 (dustymabe, 16:41:22)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/371
(dustymabe, 16:41:29)
* F32: should we switch to cgroups v2 (dustymabe, 16:42:28)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/373
(dustymabe, 16:42:33)
* AGREED: while the container ecosystem is maturing, both moby
(docker) and kubernetes aren't yet to a place where we're
comfortable moving to cgroups v2 by default for F32 based FCOS,
we'll consider again at a later time (dustymabe, 16:57:56)
* Include wireguard-tools package in FCOS (dustymabe, 16:58:25)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/362
(dustymabe, 16:58:32)
* ACTION: dusty to add agreed upon proposal to the ticket and also
some points from the discussion about use cases and what we prefer
as the "happy path" vs what we don't encourage users to do
(dustymabe, 17:38:40)
* open floor (dustymabe, 17:38:55)
* we have a new testing and stable release that are rolling out now
over the next few days, please let us know if you hit any issues
(dustymabe, 17:39:22)
Meeting ended at 17:40:27 UTC.
Action Items
------------
* dustymabe to work with x3mboy on FCOS infographic
* dusty to add agreed upon proposal to the ticket and also some points
from the discussion about use cases and what we prefer as the "happy
path" vs what we don't encourage users to do
Action Items, by person
-----------------------
* dustymabe
* dustymabe to work with x3mboy on FCOS infographic
* **UNASSIGNED**
* dusty to add agreed upon proposal to the ticket and also some points
from the discussion about use cases and what we prefer as the "happy
path" vs what we don't encourage users to do
People Present (lines said)
---------------------------
* dustymabe (113)
* kaeso[m] (23)
* jlebon (23)
* jdoss (15)
* zodbot (15)
* cyberpear (4)
* lorbus (4)
* ignatenkobrain (2)
* miabbott (2)
* mnguyen_ (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 7 months
