rafaelturk

The presenters look so stiff and rehearsed, and the makeup and lighting are so bland that it feels like an AI-generated video!

Star Wars: Episode V - I am your Father

I some point hoped that IBM and Red Hat would evolve into a ‘reverse takeover,’ where Red Hat’s culture would eventually take precedence over IBM’s. According to many friends, that outcome is still far from happening

That’s exactly my point. Instead of optimizing software, FinOps nowadays focuses on optimizing costs. While they might seem similar, they couldn’t be more different. We spend 100% our time optimizing our software, databases, etc. if we need more capacity we just add a new server to the cluster. But this hard on the cloud, easy onprem.

IBM thrives on complexity—that’s the core of many of their products and business model. The fact that even they are getting into ‘cloud cost optimization’ should be a signal for everyone to rethink public cloud strategies.

Meanwhile, we’re transitioning to on-premises infrastructure due to the increasing complexity of cloud services. Kubernetes and Docker are powerful platforms—we love them—but they were never meant to be cost-driven. Kubernetes is already incredibly efficient. However, surviving cloud costs and avoiding its traps requires granular cost control—far beyond just monitoring RAM, network, or CPU usage. It’s become overwhelming.

In a nutshell, any K8S deployment on-premises tends to be inherently optimized, saving a significant amount of time and resources. I have new servers and old servers in the same cluster, that is epic.

Modern FinOps often feels like a frustrating exercise: Should I choose 2x 2XXL instances or 4x 8XL instances? The conversation rarely focuses on optimizing software performance or database efficiency. Instead, the cloud has turned into a maze of cost centers, where it’s easy to get lost in ‘managing’ the cloud rather than building valuable products for end users.

congrats on your App!

Answering my own question, it looks like window tiling is finally solved.

Aside from the traditional and expected bells and whistles, are there any major core improvements?

Isn’t that the very definition of what an upcoming release should do?

Now that you’ve mentioned this, I feel compelled to share the lessons we’ve learned from moving from the cloud to on-premises.

* Fewer things to manage.

* Less prone to human error. We have one well-secured, central firewall that only a few developers can access. So, even if a developer forgets to properly secure something downstream, it will still be protected by the firewall. One could argue that this is possible in the cloud, but managing VPCs, etc., introduces risks. There’s always the possibility of something critical being left outside the VPC. On-prem, there’s no way something can physically escape our ethernet cables.

* IAM and bucket management issues. Anything in the cloud is inherently exposed to the Internet and, in most cases, open by default. You need to manage countless IAM configurations.

* Physical inspection. We can actually look at our setup, and if necessary, visually inspect if a server is physically encrypted.

* Simplicity and transparency. Things are simpler and more straightforward: Storage is storage, a disk is a disk, and ethernet is ethernet. Canot stress how beatufill this is, even with 100 servers it easy to manage them than in the cloud.

* Modern open-source software. Modern open-source solutions have incorporated many smart features from the cloud, making on-premise setups more powerful and easier to manage.

Kudos! We’ve successfully migrated away from the cloud, and it was an epic decision. It’s cheaper, insanely faster, easier to maintain, and unexpectedly more secure. I strongly recommend any startup or corporation to explore how modern frameworks like K8S, Ansible, Proxmox, and OpenStack—whichever suits your needs—can be incredibly easier to manage on-premises.

This like this is what made us leave the cloud and go back to our own private cloud.

You still receive security updates for all manjor MacOSes, so albeit lack of proper naming you can assume each new release as LTS.

I'm a Huge fan of Netplan, glad to see even more upstream improvements.

?. This comment makes no sense, why can't you upgrade Ubuntu? You don't have access to root?

Hopefully this will help resume work on a better High Availability code. Where one could have a cluster of 3 ValLey servers, with a superior HA protocol.

I can't wait for comunity consensus of the new de facto Redis Fork. So far seems that the current choice is in favor of Valkey.

My legal first name has a space in it ?

SableDB - Written in Rust, well kind of: RocksDB engine is written entirely in C++

hahaha

All the Pain an unclear future of the mainframe is IBM's fault. Its insanely closed ecosystem, from hardwar do software. No one other than IBM has access to it. Seems to me that going further not even IBM team will know how to manage.

Once market builds an interesting compelling offer to mainframe, enterprises will leave IBM as fast as possible.

Proxmox is great! I just wish that they had a better initial plan, plans start at €1020.

Inovation regarding FaaS comes from BigTechs. I wish we had more OpenSource FaaS solutions, albeit OpenFaas amazing achievements still lacks more robust ecosystem.

it seems to me that everyone has my data except me..

I'm playing a lot with MicroCeph. Its aopinionated low TOS, friendly setup of Ceph. Looking forward additional comments. Planning to use it in production and replace lots of NAS servers.

Intel's proposing the replacement of Nvidia CUDA across the entire industry is undeniably a bold move, yet it carries echoes of Steve Ballmer's dismissive stance towards the iPhone in its early days. At first glance, it might appear as a epic statement, but it seems to be of pure fear.

40% of datacenters? Akamai are you serious about your marketing stunts?

In my opinion if you need a stable production enviroment; MicroK8s stands out as the Kubernetes LTS choice. Canonical managed to create a successfull robust and stable Kubernetes ecosystem. Despite its name, MicroK8s isn't exactly 'micro'—it's more accurately a highly stable and somewhat opinionated version of Kubernetes.