Unpopular opinion: CentOS switching to Stream is not a bad thing at all.

When you wanted to run Openstack on CentOS in 2015, you needed to enable fedoraproject.org/wiki/EPEL to even begin an install. The first thing that did was literally replace every single package in the install.
That was, because CentOS at that time was literally making Debian Stale look young.

And we see similar problems with Ubuntu LTS, fwiw. LTS comes out every 2 years, and that's kind of ok-ish, but it lasts 5 years, which is nonsensical.

It was not, in the past. So what changed?
Software Development.

We have been moving to a platform based development approach, leveraging the wins from DevOps.

"Kris, that's corporate bullshit."

It's not, though. Let me spell it out in plain for you.
People these days do not program in an editor, with a compiler.

They use Github or Gitlab, with many integrations, and a local IDE. They commit to a VCS (the VCS, it's spelled git), and trigger a bunch of things.
Typechecks, reformatters, tests, but also code quality metrics and security scanners.

Starting a new programming language in 2020 is not as easy as it was in the past, because you do not only need a language, but also a JetBrains product, SonarQube support, gitlab-ci.yaml's…
We have come to rely on an entire ecosystem of tooling to make our developers faster, and to enforce uniform standards across the group. And that is a good thing.

We also have come to rely on tooling to enable collaboration, and structured discussion about code.
At the production end of that platform, we have made our base operating systems largely immutable - just enough infrastructure to run docker or k8s, and set up the actual production code in movable and removable units, containers.
Building these units is automated, and produces reproducible artifacts as part of a CD pipeline and repositories. We can roll forward and backwards, provided we manage state appropriately.
This - containers and VMs, also immutable, and runtime config, also versioned and injected using appropriate mechanisms - made everything single user and single tenant.
Side Note: sudo-curl-bash doesn't matter as much as everybody make it to be, because inside your container there is likely only one user, anyway.

We use other, better mechanisms that UIDs for separation these days.
That in turn enables us to architect systems from building blocks.

So your Wifi Control Plane system uses three Java processes and one Mongodb. Docker it into one container, or provide a helm chart or docker-compose with four for better scalability and maintenance.
So your gitlab deploy uses a Postgres, a Redis, and a dozen other components. Fine, deploy it as an Omnibus container or a K8s deploy yaml, and now you get a dozen components running.
So Jitsi is a Prosody, three to five Java components and even more stuff? Fine, deploy a single docker-compose.yaml and it assembles itself almost automatically.
On almost any Linux distro as a substrate.

Exactly. The actual distro does hardly matter at all, because your software comes packaged with all dependencies anyway, or is even built locally that way.
This allows us to move on.

Independently. On a per-project basis.

And the project will bring its own database, cache, runtime and libraries with itself, without version conflicts, and without waiting for the distro to move or to provide at all.
Distros moving to Stream is just the consequence of that.

They are finally free from slow moving OSS projects preventing them from upgrading local components because they can't keep up.
Even teams in Enterprises are now free to move at their own speed, because they no longer have to wait for half a dozen stakeholders to get to the Technical Debt Section of their backlog.
CentOS moving to Streams is not only acknowledging that change, it also forced the slower half of the world to acknowledge this, and embrace it.

I say "Yay, finally, progress." 👍 ✔ 🎶 🕺
And if you rant "Stability goes out of the window!" - check your calendar and your processes.

It's 2020. Act like it.
Der Completeness wegen noch die Originalquelle:

"Wenn eure Compliance darauf basiert das laufende Endprodukt zu zertifizieren, wird euere Organisation nicht mit der Entwicklung mithalten können." -- @hikhvar
This is now a blog article.

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Kristian Köhntopp

Kristian Köhntopp Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @isotopp

7 Dec
Oh my.

Dec 7 12:09:22 zyxel.home.koehntopp.de message repeated 3 times: [[] [SYS-UPTIME 06:22:14:18]

und alles dunkel, Stille.
Auch der Zähler ist duster. In der Tat ist sogar der Bus Stop dunkel. Image
Dec 7 12:15:56 localhost kernel: [ 0.000000] Linux version 5.4.0-56-generic (buildd@lgw01-amd64-025)

Sechs Minuten später.
Read 6 tweets
3 Dec
TIL de.wikipedia.org/wiki/Hyperinkl…

Gold. Also auch im Kontext Divergenz zwischen dem was Politiker so als relevant oder gute Lösung wahrnehmen, und dem, was notwendig wäre.

Es gibt ein Wort dafür.
(via de.wikipedia.org/wiki/Pfadabh%C… und den folgenden Absatz)
@mausdompteur warf anderswo ein: Ist das so was wie Atlassian Syndrome a la @maikzumstrull ?

Ich fragte, "Was ist Atlassian Syndrome"?
Read 10 tweets
1 Dec

cc @solarwinds @InfluxDB
P_S tables can be seen as unlocked memory buffers. They look like tables, but are not.

GROUP BY and ORDER BY are unstable, as the values can change while your sort runs.
They also use no indexes. Maintaining an index on a P_S table costs time at write, a thing that P_S tries to minimize - it must not slow down production.

That means you should never JOIN P_S tables against anything.
Read 5 tweets
1 Dec
The Apple Build Farm Apple itself has never offered to their developers can now be rented at AWS.
Apparently using Minis. Rackable Xeon Macs are not an Apple thing, apparently.

One would think they have this, based on Supermicro or QCT machinery, at least for themselves.
Adding or emulating/replacing the nonexistent BMC on these minis must have been a major main in the ass, but needs to be done to properly automate the provisioning of the product.
Read 4 tweets
20 Nov
"Grundschule in Lichtenberg stellt digitalen Unterricht vorerst ein"

Bitte Artikel ganz lesen, Auszüge funktionieren nicht, das eskaliert durchgehend bis zu "Schüler sollen Lehrer nicht mehr anrufen"
Zum Mitmeisseln: Es ist weder Aufgabe einer Schule Server zu haben noch zu betreiben. Sie kann das auch nicht sicher tun.

Es muß Netz in die Schule und die Schule braucht Connect zu einer zentral betriebenen und einheitlichen Ausbildungsumgebung.
Zentral und einheitlich, Kris?

Ja, schon alleine, damit es bundesweit einheitlich eine API und Plattform gibt, für die Inhalte entwickelt werden können (die können dann gerne pro Bundesland variieren, wenn man drauf besteht - die Technik aber nicht).
Read 9 tweets
22 Oct
@realgiggls @georgloesel @kkklawitter @joerg_spengler

Wenn Du Deine Straßen so baust, daß sich Fahrrad und Auto möglichst nicht begegnen, dann ist die Frage nach der Vorfahrt müßig.

@realgiggls @georgloesel @kkklawitter @joerg_spengler Keine Begegnung, keine Vorfahrtsfragen.
@realgiggls @georgloesel @kkklawitter @joerg_spengler Keine Fucking Begegnungen, keine Fucking Vorfahrtsfragen.
Read 34 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!