> 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

------- Original Message -------
On Thursday, June 1st, 2023 at 3:57 PM, Matt Hogstrom <m...@hogstrom.org> wrote:


> Similar experience. Not sure if its the same person but I had dinner with 
> Jeff Nick (former Felllow with Z) and his story was that they needed Posix to 
> meet a Federal requirement. He also said that it was contentious internally 
> and so they assembled a team and isolated them from the others so they could 
> make fast progress.
> 
> In an update on how they were doing they were finally able to fork a process. 
> He said it was more like foooooooooorrrrrrrrkkkkkkkk. Clearly, they fixed the 
> performance and little did they know that it was such a critical decision for 
> the platform that it saved z/OS. I think K8s is the USS of yesteryear. No one 
> knows it yet but it will add another 25 years to the platform.
> 
> Matt Hogstrom
> PGP key 0F143BC1
> 
> > On Jun 1, 2023, at 05:34, David Crayford dcrayf...@gmail.com wrote:
> > 
> > I've worked with a few ex-OE guys, including my close colleague who used to 
> > the IBM DE running the OE project out of POK. Let me tell you, some of the 
> > stories they have are absolutely fascinating! It's my understanding that 
> > the POSIX certification was mainly pursued to meet the requirements set by 
> > NASA. But here's an interesting twist: NASA doesn't run a mainframe anymore.
> 
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to