On Fri, Jun 26, 2020 at 07:07:51AM -0400, Neal Gompa wrote:
> > Everything will run in a virtual machine given that
> > enough care has been put into creating the VM. I don't think the same
> > can be said for containers.
> I think in todays world we should develop for containers first.
> Especially when k8s abstracts many things and provides useful
> infrastructure for application. A bit like systemd a decade ago, by
> providing useful APIs like socket-activation, watchdog, restarts,
> parallel invocations locks, applications do not have to care about
> re-implementing boring stuff over and over again.
The difference is that it's actually a huge pain for people to run
containers on Kubernetes. All these things you described can be done
with systemd units in regular RPMs. In fact, for the AAA solution, I
*already* did that so that we can reuse it for the Fedora and openSUSE
While I think it'd be valuable to figure out the container workflow
for apps deployed in containers, let's not forget all that stuff in
our infrastructure requires OpenShift, and I don't know about most of
you, but I'm fresh out of OpenShift at home to be able to do this sort
Actually, I have 5 node 3.11 at home now (3 VMs and 2 old laptops).
Over the summer I'm looking at installing OKD 4.4 on laptops + 1 VM,
apparently 3-node could be done with "compact clusters".
But I digress…
Tomasz Torcz 72->| 80->|
tomek(a)pipebreaker.pl 72->| 80->|