11–20 of 94 posts
> snap > Ubuntu Pro > driving […] subscription Think I’ll stick LXC on proxmox
The only thing I miss is the kind of automatic deployment and network layers that Kubernetes has.
Earlier quoted context omitted.
> And IT does another cycle. People keep saying that as if it was a bad thing
It wouldn't be a bad thing if people learned from the previous iteration. But they don't. In fact, what they generally do is layer an implementation of the stuff they forgot last time on top of the preceding iteration which lacked it. So now, we have clusters of Linux boxes, built with a ton of new tooling on top of Linux because Linux is a UNIX and traditional UNIX doesn't have networking or clustering in the design…
Earlier quoted context omitted.
> And IT does another cycle. People keep saying that as if it was a bad thing
It wouldn't be a bad thing if people learned from the previous iteration. But they don't. In fact, what they generally do is layer an implementation of the stuff they forgot last time on top of the preceding iteration which lacked it. So now, we have clusters of Linux boxes, built with a ton of new tooling on top of Linux because Linux is a UNIX and traditional UNIX doesn't have networking or clustering in the design…
So.. we’re back to self-hosting your own services? And IT does another cycle.
Medical, we do everything in-house to make life easier.
Low value servers, in-house.
High uptime + scalable? You are not doing that in-house.
Earlier quoted context omitted.
> And IT does another cycle. People keep saying that as if it was a bad thing
It wouldn't be a bad thing if people learned from the previous iteration. But they don't. In fact, what they generally do is layer an implementation of the stuff they forgot last time on top of the preceding iteration which lacked it. So now, we have clusters of Linux boxes, built with a ton of new tooling on top of Linux because Linux is a UNIX and traditional UNIX doesn't have networking or clustering in the design…
So.. we’re back to self-hosting your own services? And IT does another cycle.
So.. we’re back to self-hosting your own services? And IT does another cycle.
The big gain from clouds is the flexible infrastructure, especially in the microservices world we are now. In the past, one needed to procure, provision, etc a new server to run a service (times X per environment). With a cloud, regardless if it's public or private, provisioning a VM (or container) to run a new service is a few clicks away.
Earlier quoted context omitted.
> And IT does another cycle. People keep saying that as if it was a bad thing
It wouldn't be a bad thing if people learned from the previous iteration. But they don't. In fact, what they generally do is layer an implementation of the stuff they forgot last time on top of the preceding iteration which lacked it. So now, we have clusters of Linux boxes, built with a ton of new tooling on top of Linux because Linux is a UNIX and traditional UNIX doesn't have networking or clustering in the design…
They did however accomplish pushing the "UNIX 1.0" into at least 1.1: as awkward as Linux's /proc is, it's still objectively better than sysctl; 9P is a practical choice for sharing files with a VM guest; and let's not forget everything Go brought to the table.
In retrospect, considering which technologies contemporary to Plan 9/Inferno have "won", I'm also grateful that we don't need to deal with an in-kernel JVM.
I recently tried Mikrok8s from Canonical and at idle (as in not running any of my containers) it ranges from 5% to 15%. I hope this product doesn't suffer the same wastage.
I swapped to k3s and the usage was half of what microk8s used.