Maybe your missing the point of zCX. Nobody expects to run big
distributed stacks as that would be dumb. Distributed software is
designed to run on commodity hardware that can fail, hence the CAP
theorem and RAFT protocols. zCX can save customers money
https://ibm-messaging.github.io/mqperf/MQ%20with%20zCX.pdf
On 1/6/2023 7:33 pm, kekronbekron wrote:
I think K8s is the USS of yesteryear
Sad noises... I would like to see zOS native containers integrated directly to
WLM instead.
WLM is literally the workload manager.
It may not make sense for it to do everything k8s does, but could maybe do what
consul or docker swarm does?
Me stomach turns seeing OpenShift inside zCX.
How many layers of faking do we need? PR/SM -> (maybe) zVM -> zOS -> zCX ->
container.
zOS security/network configuration ... zCX security/network configuration ...
OpenShift/k8s/containers security/network configuration ... contained
application's security/network configuration
It would be fun to see zCX "unwrapped" and presented as Linux System Services
instead.
Like OMVS STC is to USS, zCX-renamed could be that to LSS.
- KB
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
