On Fri, May 28, 2021, at 5:43 AM, Neal Gompa wrote:
Part of the point of the different working groups was to handle the
different use-cases *well* at their own pace. The CoreOS Working Group
is *explicitly* excluded and frankly unlikely to ever switch because
Colin believes
I am not CoreOS, I'm an engineer working on it.
that Btrfs is only suitable for "pet" workloads[1]
That's not what my blog said. One of the sub-headers is "BTRFS is good for
"pet" systems". There's no word "only" there - you inserted
that.
On this topic though, if Fedora CoreOS didn't exist, this proposal to change Cloud
would be significantly more consequential. The defaults *really matter* here in
particular, even more than Workstation. But, I think because CoreOS does exist, this
change matters less.
One big advantage CoreOS has is Ignition, which allows provisioning filesystems in the
initramfs, including the root partition. It works today to boot up a stock Fedora CoreOS
AMI, OpenStack qcow2 etc. and provide an Ignition config that changes it:
https://docs.fedoraproject.org/en-US/fedora-coreos/storage/#_reconfigurin...
And it works to use btrfs too! Just s/ext4/btrfs/ in the first example. (And that *exact
same* Ignition config also works for bare metal)
That's not true of cloud-init based systems - instead of e.g. you wanted to use
xfs/ext4 for a high performance database-like workload, in cloud you'd need to attach
a separate instance volume or so for `/var/lib/$whatever` (That said separate volumes can
actually be a better approach anyways, it depends). Some traditional Cloud image users
won't notice this or care (just like Workstation users) but others definitely will.