Teaching an AI How We Build Operators
It’s been a while since my last post – life got busy, as it usually does when
you’re deep in the weeds of operator development. Between reconciliation loops,
CRD schemas, and the occasional CrashLoopBackOff that keeps you company on a
Friday evening, finding time to write about what you’re doing (rather than just
doing it) has always been the hardest part.
Podman for DevOps - Second Edition
Having worked with OpenStack and
Ceph for many years, I’ve had a front-row seat to one of
the most significant transformations in modern infrastructure: the shift from
bare metal deployments to containerized workloads. When I started, everything
ran directly on physical machines. Then came virtual machines, and eventually,
containers changed everything.
Before moving to Red Hat OpenStack Services on OpenShift
(RHOSO),
I witnessed how Podman became the backbone of container
management in both OpenStack and Ceph deployments. Even today, it’s still the
foundation for running nova-compute services on EDPM (External Data Plane
Management) nodes.
Working with these systems in production has taught me how important it is to
understand the building blocks that power our container infrastructure.
That’s why “Podman for DevOps Second Edition” caught my attention.
Authors Alessandro Arrichiello and Gianni Salinetti have produced something
that goes beyond typical technical documentation. They’re tackling the question
I’ve been recently thinking about: what comes next in container technology,
especially with AI/ML workloads becoming mainstream?
Gopher is still alive - Welcome to port 70
It’s been a while since I’ve written my last post.
Actually I was absent because in the meantime I’ve got a new job, I’m going to
make some family’s changes (new house, new life), so all of my efforts were (and
are) focused on doing my best in my new job, handle all the things that the life
reserved to me, and yes, it’s been a quite hard find a moment to stop myself,
thinking and writing.
Finally I’m here, trying to find some time to write a little post on things I
love and I really hope it can be a rule for the next months.
Even though I love what I do day by day, there are few side projects I think
they deserved to be told and yes, this post is about one of them.
To make a long story short, few months ago reading how the Redis
development was going I was inspired by a new, old topic: the implementation of
the gopher protocol.
It’s not a joke, and I know today gopher is not widely used anymore (HTTP rules),
but I’ve seen in it an opportunity to learn a bit of history and why not, the
opportunity to make a pure C implementation of a Gopher server to revive it’s
RFC1436 and figure out how internet (the
internet people know today) was at the very beginning, when the need was to empower
people to publish and share information, getting rid of all it was related
to the style and the cosmetic issues on presenting information to the end users.
Anyway, c_gopherd tries to be a tiny,
minimal re-implementation of a gopher server and tries to make alive again that
world in which you just had text based documents, hyperlink connections to other
resources, experimenting a different way to do things.
If you want to have more context on this, I suggest reading few useful documents:
Scaling applications with Openshift - A real Use Case Scenario
One of the last days of this year, one of the last job travels that give me some
time to write a post.
This year I’ve made a full immersion on kubernetes and inhered technologies like
openshift as container orchestration platform and I have to say that definitively
I’ve learned tons of fun things on cloud native software.
With the help of this kind of tools the software development cycle is becoming
more agile, more flexible, you can deploy applications thousands of times without
breaking the service you’re offering to your customers, rolling out new (and maybe
different version or just a % of traffic) of a deployment in no time;