For clarity, start with "chroot" or "change root".
Unix has had thechroot() function and the 'chroot' command since before
my time, thus POSIX and Linux have it too.
Within a changed root environment, the process or program can only "see"
files from the new root directory on down.
The hardware architecture and the operating system (ABI or application
binary interface) remain the same.
The downside to this (or maybe the upside, depending on what you need)
is that programs running under 'chroot' "see" the same network stack and
devices. They also "see" other processes (and can signal them).
I used to say that 'chroot' was the closest thing Unix had to a virtual
machine. It's fantastic for development, and often useful for security.
But then came containers.
Containers are like "chroot on steroids". Processes running in a
container have the "root" indicated, but also have their own unique
_network address_ and a private _process space_. The advantage is
sharing of the kernel (or nucleus); no need to intercept I/O or
virtualize devices.
The hardware architecture and the operating system (ABI or application
binary interface) remain the same.
A container hosted by Linux is a Linux environment. A container hosted
by Slolaris is a Slolaris environment. A container (called a "jail")
hosted by FreeBSD* is a FreeBSD environment.
_Presumably a container hosted by z/OS (USS) is a z/OS (USS)
environment,_ but the sales pitches are perhaps vague. (It's also
possible that I'm just dense! I concede.)
So ... Timothy ... please speak it plainly for slowpokes like me.
*What exactly are these various offerings? *
Thanks!
*FreeBSD (or possibly one of the other BSDs) was first with this, by the
way. They call it a "jail".
-- R; <><
On 3/6/24 08:04, Matt Hogstrom wrote:
At Broadcom we announced support for K8s deployments of what I call the
surround z/OS software deployment. Internally we’ve tested deployments on
x86, zLinux and zCX with the latter two using OCP.
Its called WatchTower and leverages public REST APIs across the on z/OS and off
z/OS products. K8s makes deployment,management and upgrades so much easier.
We started with x86 as most Z shops are not ready on zLinux or zCX Cant wait
for that though.
Matt Hogstrom
PGP key 0F143BC1
On Mar 6, 2024, at 07:48, Jousma,
David<000001a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:
Timothy,
I’ll wait to see more information as it becomes available. So zCX is Ubuntu
Linux on z/OS, IBM has labelled Redhat Openshift as zCX-OCP, and now we have
zOSCP. I like the container Ideas, but this literally sounds like z/OS Unix
inside a container? I guess that surprises me, as I don’t hear about people
actively coding in z/OS Unix. Or is this something else?
BTW, I am a big proponent of ZCX, and would like to see IBM move its ancillary
mainframe support software into a docker container. I know TWS DWC, Omegamon
TEPS, and others are moving that way. Just waiting for more to come. We
are also running Rocker Terminal Emulator Webedition in ZCX to replace all of
our desktop out-of-date Bluezone implementations.
Dave Jousma
Vice President | Director, Technology Engineering
From: IBM Mainframe Discussion List<IBM-MAIN@LISTSERV.UA.EDU> on behalf of Timothy
Sipples<sipp...@sg.ibm.com>
Date: Tuesday, March 5, 2024 at 8:46 PM
To:IBM-MAIN@LISTSERV.UA.EDU <IBM-MAIN@LISTSERV.UA.EDU>
Subject: IBM Announces the z/OS Container Platform
I’d like to draw your attention to this IBM announcement: https: //urldefense.
com/v3/__https: //www. ibm.
com/docs/en/announcements/zos-container-platform-delivers-industry-standard-cloud-technologies-build-run-zos-unix-applications-as-containers-natively-zos__;!!MwwqYLOC6b6whF7V!g9jgcYA166VI9yCFuvhNkTfHy8dDjgaHN__msC1njoKwcSod3-qptPTbiM-TB68jc0uSWrpixIKdSvtHkw$<https:
//urldefense. com/v3/__https: //www. ibm.
com/docs/en/announcements/zos-container-platform-delivers-industry-standard-cloud-technologies-build-run-zos-unix-applications-as-containers-natively-zos?region=US__;!!MwwqYLOC6b6whF7V!g9jgcYA166VI9yCFuvhNkTfHy8dDjgaHN__msC1njoKwcSod3-qptPTbiM-TB68jc0uSWrpixIKZu1F5Bg$>
I’d like to draw your attention to this IBM announcement:
https://urldefense.com/v3/__https://www.ibm.com/docs/en/announcements/zos-container-platform-delivers-industry-standard-cloud-technologies-build-run-zos-unix-applications-as-containers-natively-zos__;!!MwwqYLOC6b6whF7V!g9jgcYA166VI9yCFuvhNkTfHy8dDjgaHN__msC1njoKwcSod3-qptPTbiM-TB68jc0uSWrpixIKdSvtHkw$<https://urldefense.com/v3/__https:/www.ibm.com/docs/en/announcements/zos-container-platform-delivers-industry-standard-cloud-technologies-build-run-zos-unix-applications-as-containers-natively-zos__;!!MwwqYLOC6b6whF7V!g9jgcYA166VI9yCFuvhNkTfHy8dDjgaHN__msC1njoKwcSod3-qptPTbiM-TB68jc0uSWrpixIKdSvtHkw$><https://urldefense.com/v3/__https://www.ibm.com/docs/en/announcements/zos-container-platform-delivers-industry-standard-cloud-technologies-build-run-zos-unix-applications-as-containers-natively-zos?region=US__;!!MwwqYLOC6b6whF7V!g9jgcYA166VI9yCFuvhNkTfHy8dDjgaHN__msC1njoKwcSod3-qptPTbiM-TB68jc0uSWrpixIKZu1F5Bg$<https://urldefense.com/v3/__https:/www.ibm.com/docs/en/announcements/zos-container-platform-delivers-industry-standard-cloud-technologies-build-run-zos-unix-applications-as-containers-natively-zos?region=US__;!!MwwqYLOC6b6whF7V!g9jgcYA166VI9yCFuvhNkTfHy8dDjgaHN__msC1njoKwcSod3-qptPTbiM-TB68jc0uSWrpixIKZu1F5Bg$>>
—————
Timothy Sipples
Senior Architect
Digital Assets, Industry Solutions, and Cybersecurity
IBM Z/LinuxONE, Asia-Pacific
sipp...@sg.ibm.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN
This e-mail transmission contains information that is confidential and may be
privileged. It is intended only for the addressee(s) named above. If you
receive this e-mail in error, please do not read, copy or disseminate it in any
manner. If you are not the intended recipient, any disclosure, copying,
distribution or use of the contents of this information is prohibited. Please
reply to the message immediately by informing the sender that the message was
misdirected. After replying, please erase it from your computer system. Your
assistance in correcting this error is appreciated.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email tolists...@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
