On Wed, Feb 24, 2021, at 9:19 AM, Tadej Janež wrote:
>
> This is the thing that is probably hurting users the most. They have a
> working F33 cloud instance and after systemd is upgraded, the instance
> will *probably* (i.e. if users didn't configure DNS themselves and
> relied on cloud-init) be heavily broken, i.e. DNS resolution not
> working.
For Fedora CoreOS one of our principles is that the system is identical across bare metal and cloud; we force bare metal system installs into extra provisioning ("install" is "dd image to disk") in order to make sure that Ignition and everything involved runs in a uniform fashion. There's no cloud-init vs kickstart vs something else.
We use NetworkManager across the board for the same reason.
And, we also have unified CI that tests the entire OS image (ostree commit) as a single unit before shipping out updates to everyone. And we also do "staged rollouts" so that if we did encounter a problem like this, we can stop the rollout so not everyone would get hit.
We also have automatic updates on by default - we couldn't do that without the above.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
