Growing pains for Fedora CoreOS

Posted Jun 8, 2021 17:00 UTC (Tue) by geuder (subscriber, #62854)
In reply to: Growing pains for Fedora CoreOS by dustymabe
Parent article: Growing pains for Fedora CoreOS

> encouraging everyone to run `next` and `testing` on a percentage of their systems.

Good point.

However, we have (only) 2 instances, not 200. One is for production and one for testing (of our systems, not of FCOS). Running our testing system with a different version than the production system does not sound like a great idea. All test results would basically be possibly non-reproducable.

So we would need to run a 3rd one just for FCOS testing, a 50% overhead. And of course someone would need to check the instance at every update and run some test set. Which is a bit a against the idea of having automatic updates.

Well, no free lunch, I know...

Growing pains for Fedora CoreOS

Posted Jun 9, 2021 5:02 UTC (Wed) by raven667 (subscriber, #5198) [Link]

In this situation you'd be doing all your changes on the test system first, right? It's not that much of a departure as there would often be a difference between what is running in test and what is in prod, test can't guarantee repro of problems found in prod unless you reset it back to the versions used in prod. There is value in finding upgrade related problems in test first, but as you note the initial advice is probably targeted more toward admins with dozens or hundreds of systems where having a small cadre running bleeding edge code is relatively low risk to the overall system health. The quality benefits of going from prod-only to prod & qa to prod, qa & test to prod, qa, test & dev environments are diminishing while the cost increases but its the scalability of work that goes up the most which is mainly of benefit to larger organizations.