►
Description
You have heard of Red Hat Ansible, but have you heard of its capabilities and impact in the mainframe space? Join experts from IBM zSystems to hear the capabilities IBM has been contributing into the Ansible community, and how Ansible is standardizing the approach to automation for z/OS users.
Dan Jast – Product Manager Ansible for IBM zSystems
Connect with Dan Jast on LinkedIn: https://www.linkedin.com/in/daniel-jast-863598123/
Bryant Panyarachun - STSM - Ansible for z/OS Ecosystem Architect
Connect with Bryant Panyarachun on LinkedIn: https://www.linkedin.com/in/bryant-panyarachun-21510625/
Join the Ansible for IBM zSystems Community:
https://www.ibm.com/community/z/software/ansible-for-ibmz
Learn more at the Ansible for IBM zSystems documentation: https://ibm.github.io/z_ansible_collections_doc/index.html
A
A
A
Whatever
that
ended
up
being
so
that
that
was
that's
very
exciting,
almost
as
exciting
as
our
guests,
so
we
don't
actually
have
any
other
announcements
today,
we're
going
to
jump
straight
into
all
the
things
so
joining
us
here
today
from
across
the
aisle
over
at
IBM
is
Bryant
and
Dan.
I
am
not
attempting
your
last
name
Brian.
We
didn't
discuss
that
before
and
I'm
not
doing
it
now.
It's.
B
C
Thank
you
and
hi
everyone
thanks
for
joining
today.
My
name
is
Dan.
Just
I
am
one
of
the
product
managers
here
at
IBM,
covering
our
ansible
for
IBM
Z
systems
initiatives.
Here
it's
been
a
really
exciting
last
three
years
of
working
in
this
space
and
we're
really
excited
to
you
know,
share
with
the
audience
here
with
the
get
Ops
guide
of
the
Galaxy.
What
we've
been
doing
over
the
last
three
years-
and
you
know,
talk
ansible,
it's
been
a
really
fun
time.
I'll
pass
it
off
to
Brian.
D
Brian
yeah
yeah
I'll
make
sure
to
pronounce
that
for
everyone,
so
my
name
is
Brian
pinatra
and
I'm,
the
Chief
Architect
for
the
ansible
for
Zeos
ecosystem.
So
you
know
leading
the
technical
side
and
you
know
everything
that
we're
contributing
into
the
ansible
space.
You
know
enabling
zos
and
all
that
automation,
goodness.
C
But
when
you
think
of
what
a
z
system
is
it?
What
a
Mainframe
is
you
know,
I
always
like
to
relate
it
back
to
you
know,
servers
that
are
driving
lots
and
lots
of
transactions.
So
in
most
cases
a
lot
of
people
don't
even
realize
how
much
every
day
they're
interacting
with
the
Mainframe.
Every
time
you
pre,
you
know
you
show
you
swipe
your
credit
card
or
every
time
you
book
an
airline
use.
You
know
your
insurance
anything
like
that
is
actually
behind
the
scenes.
C
You
know
working
against
our
transaction
processors
that
are
running
on
the
Mainframe
I.
Think
in
95
percent
of
you
know,
major
transactions
happening
worldwide.
Actually
those
transactions
in
some
point
or
another
are
coming
through
a
Mainframe.
So
really
really
big
servers,
as
I
saw.
You
know,
Mr
Callahan
just
put
out
in
chat
it's
great.
It's
really
really
powerful
systems.
Brian.
You
want
to.
D
A
B
A
B
D
Yeah
no
I
mean
you're,
absolutely
right,
I
mean
I.
Think
the
general
sentiment
really
aligns
with
you
know
at
least
the
the
ability
to
support
all
that
throughput
of
transactions.
It
used
to
be
that
size
as
well,
not
So,
Much
Anymore.
More
recently,
the
mainframes,
you
know
a
common,
you
know,
viewer,
you
know
has
been
like
that
they're.
You
know
the
size
of
refrigerators
and
they're
kind
of
shrinking
down
they're,
actually
like
this
half
of
a
refrigerator.
Now,
in
most
cases
for
at
least
the
flagship,
you
know
and.
D
Were
power
consumption
there,
but
also
more
recently,
with
Z16?
This
is
the
introduction
of
rack
mount
as
well,
so
not
being
able
to
leverage
all
the
different
types
of
rack
and
server
type
of
storage
and
fitting
in
you
know
all
the
different
types
of
of
storage
that
our
customers
have
as
well
and
that
that
new
form
factor
so
that
that's
a
big
deal
from
the
hardware
perspective.
The
new
rack
now.
A
So
I'm
gonna
geek
out
a
little
bit
on
the
things
that
I
know
before
we
start
diving
into
how
Ansel
plays
into
this.
So
the
things
that
I
know
that
I've
I've
heard
over
from
other
colleagues,
is
not
not
just
about
the
power
thing,
but
one
that
zos
is
open
source
and
has
always
been,
who
that
it's
backwards
compatible
for
apps
that
have
been
built
for
it
all
the
way
back
to
its
Inception.
C
So
it's
it's
pretty
impressive,
what's
happening
behind
the
scenes,
I
like
to
compare
it
sometimes
to
my
gaming
PC,
where
I
was
super
excited
to
upgrade
from
16
gigabytes
of
memory
to
32
at
one
point
and
we're
talking
about
I,
think
the
two
two
bosses
ago,
I
think
had
40
terabytes
of
memory
just
alone.
So
it's
it's
ridiculous.
C
A
A
D
What
I,
what
I
like
to
compare
the
Mainframe
to
as
well
is
I,
don't
know
if
you
guys
are
fans
of
of
F1,
but
I
see
it
as
a
an
F1
car
right.
It's
an
extremely
high
performance,
highly
specialized
vehicle
that
takes
a
highly
skilled
set
of
Engineers
to
be
able
to
operate
against
and
are
specialize
in
various
facets
of
that
vehicle
tuning
right.
You
have
a
suspension.
A
B
I
wonder
also
if
this
is
a
common
misconception
coming
from
like
the
x8664
world
to
like
mainframes,
because
it's
like
it's
almost
like
a
paradigm
shift
that
you
have
to
do
with
your
mind,
coming
from
like
the
X
lower
rank
because,
like
that
would
be
like
my,
this
will
be
my
question
right
coming
from
the
x8664
world,
it's
like
I
wonder
how
all
this
stuff
differs,
but,
like
you
know,
I'll
let
the
I'll.
Let
the
experts
answer
this,
because
yeah
I'm
curious
myself
and.
A
C
Yeah
so
I
mean
I'll,
kick
it
off
and
I'll
pass
it
to
you
Brian
to
get
into
it
more,
but
IBM
guarantees
a
very
high
level
of
availability
with
the
Mainframe
I.
Believe
it's
right
now.
It's
seven
nines
of
availability,
if
I'm
not
mistaking
which
comes
down
to
about
I,
think
three
seconds
per
year,
or
something
like
that
that
we're
talking
around
downtime
and
we're
not
even
really
talking
about
downtime,
because
there's
so
much
failover
built
into
the
way
the
system
operates.
C
D
Yeah,
no
absolutely
I
mean
really
that's
one
of
the
key.
You
know
value
propositions
of
the
Mainframe
is
that
resiliency
over
you
know
multiple
layers
of
residency
for
every
single
component,
we're
not
talking
just
Hardware
the
operating
system
and
all
of
our
software
as
well.
Right.
You
have
multiple
layers
where
you
have
multiple
backup
batteries:
multiple
C
CPUs,
I
o
components.
You
know
crypto
cryptography
modules,
multiple
layers
and
and
dedicated.
You
know
channels
for
all
those
things
to
really.
You
know
help
against
that.
You
know
resiliency.
A
But
your
backups
have
backups,
have
backups
your
failovers
have
failovers,
have
failovers
and
also
the
I
think
that
that's
a
very
brilliant
usage
of
the
resources,
but
the
fact
that
the
fact
that
you've
they've
been
able
to
make
like
the
Mainframe
has
been
evolving
this
whole
time
right.
It's
one
of
those
things
in
the
shadows,
Stephen
mentioned
that
he
thinks
of
mainframes.
He
thinks
of
cobalt
like
yeah,
that's
still
running
on
mainframes,
absolutely,
but
they've
gotten
smaller
they've
gotten.
We
talked
about
this
more
energy
efficient.
You
have
backup
batteries.
A
Well,
your
backup
batteries
can
last
you,
especially
on
that
low
of
a
power
draw
until
backup
generators
turn
on
and
all
these
types
of
places
that
are
going
to
have
a
Mainframe
really
they're,
also
going
to
have
backup
power,
all
those
other
all
their
additional
failovers,
so
the
Mainframe
doesn't
even
it
doesn't
need
to
do
all
the
failover
lift,
but
the
fact
that
it's
so
efficient
allows
it
to
do
so.
Much
of
that
until
the
generators
kick
on,
the
power
is
restored.
What
what
have
you
and
so.
C
Forth
and
some
of
the
testing
I
I
personally
used
to
work
at
Poughkeepsie,
where
the
manufacturing
plant
for
the
Mainframe
is
and
some
of
the
testing
that
they
go
through.
There
is
incredible:
they
have
these.
You
know
environmental
Chambers,
they
put
the
mainframes
in
where
they
vibrate
them.
They've
dropped
the
temperature
super
low.
They
bump
the
temperature
super
high
I,
even
heard
at
one
point:
a
Mainframe
fell
over
on
its
side
and
was
continuing
to
drive
the
applications
that
was
running
in
it.
So
I
mean
it's,
it's
unbelievable.
C
B
A
It's
adorable,
the
internet
is
such
a
place.
Okay.
This
will
make
it
entertaining
to
follow
the
the
comments
thread
so
folks
who
have
us
on
slack.
If
you
want
to
ask
questions
in
slack,
go
ahead
and
do
that
I'll
watch,
my
slack
I
don't
usually,
and
so
that's
it.
Let's
actually
start
maybe
getting
to
the
ansible
ansible
portion
of
the
show.
C
B
A
Our
audience
is
very
chatty.
I
am
going
to
call
you
out
on
having
not
actually
watched
this
stream
too
much
before
coming
on.
So
you
won't
have
noticed
that
our
audience
is
very
chatty
and
talks
a
lot
and
asks
a
lot
of
questions,
not
always
on
topic.
There
could
be
entire
other
conversations
happening
in
our
chat
while
we
are
on
topic
and
so
yeah
anyway,
we'll
just
we'll
just
let
them
do
do
their
things
and
interrupt
you
as
need
be.
So
we
all
know.
A
C
I
mean,
first
of
all,
you
know
Brian
did
kind
of
hit
on
it
a
little
bit
earlier.
Where
working.
You
know,
this
incredible
system,
which
is
the
Mainframe,
comes
with
a
very
specialized
set
of
skills
as
well
right.
When
you
talk
about
working
on
the
Mainframe,
you
talk
about
some
of
the
technologies
that
we're
working
with
on
a
daily
basis.
D
Kelly
I
mean
more
commonly
like
you'll,
you
know
a
user
will,
you
know,
have
a
JCL
with
a
couple
of
job
steps.
You
know
executing
ifbr
14
and
maybe
another
exec
with
the
IB
copy.
You
know
with
like
a
copy
and
a
select
statement.
You
know
you
know
copying
some
of
the
desired
members.
You
know
and
you
guys
follow
that
right.
I
mean
that's
fairly
straightforward.
D
Ryan,
why
do
you
tell
them
what
I
mean?
Essentially,
what
that's
describing
is
you
know,
leveraging
some
Mainframe
specific
tools
really
just
to
create
a
directory
and
copy
a
file
to
something
right.
But
you
know,
as
with
everything
being
so
specialized
on
the
platform,
you've
got
tools
that
are
very
specialized,
that
you
know
kind
of
are
constrained
against.
You
know
historical
constraints
in
terms
of
naming
right
and
there's
a
lot
of
proprietary,
different
Technologies
in
terms
of
scripting
and
languages
with
JCL
and
how
you
use.
D
You
know,
control
statements
and
things
like
that,
and
it's
not
necessarily
the
most
intuitive
thing
as
a
new
person
coming
into
the
platform.
So
that
was
really
one
of
the
things
that
you
know
why
I
loved
ansible
and
when
I
started
looking
at
it,
because
I
was
doing
some
automation
early
on
in
my
Development
Career.
D
You
know
against
Zeos
products
and
within
the
Mainframe
and
seeing
that
well
I'm
having
to
learn
all
of
this
unique
stuff
and
why
can't
I,
you
know,
use
some
of
this
other
technology
that
I'm
looking
for
you
know
when
I'm
searching
on
stack,
Overflow
or
right
and
I
see
you
know
people
using
all
this
other
automation
tools,
but
I
can't
I
can't
leverage
that
against
any
of
our.
You
know,
Z
OS
utilities
or
anything
like
that.
So
that's
where
you
know
really
started
diving
in
and
seeing
what
can
we
do?
C
B
Yeah
so
well
I
kind
of
just
kind
of
wanted
to
point
out
with
WD
Callahan.
The
only
thing
I
like
about
ansible
is
that
I
didn't
have
it
earlier
in
my
life,
that's
like
very,
very
true,
especially
for
me.
So
in
case
you
didn't
know
Hillary
and
I
used
to
work
together
before
Red
Hat
and
in
case
Hillary.
In
case
you
didn't
know,
we
used
a
combination
of
puppet
and
Chef.
B
As
code
per
se,
we
had
more
of
like
the
puppet
and
Chef
who
was
very
app
Centric
and
very
like
what
it
takes
to
get
this
app
running
on
a
system,
point
of
view
versus
managing
a
system
right
which
is
kind
of
like
where
I
think-
and
this
is
kind
of
like
if
ansible
was
around
I-
would
have
just
totally
used
ansible
back
then,
because
you
know
we
had
to
use
kind
of
this
weird
combination
of
like
puppet
Chef.
Shell
scripts
wrote
this
abstraction
layer;
it
was
really
really
it.
It
worked
with
the
time.
B
C
A
We
didn't
like
it
wasn't
just
like
a
Jenkins
job.
This
was
you
know,
Maggie
in
Ye,
Old
Days
of
yore.
We
had
Daisy
chained,
Jenkins
jobs
to
do
so
much
of
this
for
us,
and
so
that
was
like
I
had
I
had
a
lot
of
that,
like
I
interacted
with
the
Jenkins
jobs.
Fortunately,
because
of
where
I
sat
versus
having
to
deal
with
his
whole
puppet
chef
thing,
but
I
worked
I
will
it
worked?
C
C
So
there's
a
there's
a
you
know
an
inherited
skills
challenge
in
working
with
this
platform
here,
where
we're
really
trying
to,
in
the
two
words
I,
throw
around
a
lot,
are
providing
a
standard
and
consistent
experience
coming
from
other
platforms
or
coming
in
from
college,
where
you
can
apply
your
python
skills
or,
if
you're
learning
ansible
on
other
platforms.
Just
writing
that
same
yaml
Playbook
code
and
being
able
to
automate
on
the
Mainframe
right
and
just
being
able
to
take
that.
You
know
same
tooling
work
with
it
on
the
Mainframe
and
that's
really.
A
D
D
B
So
is:
is
it?
Is
it
a
build
so
again,
I'll
be
the
ignorant
one
I'm
not
afraid
to
ask
dumb
questions?
Is
this
a
build
of
ansible
running
on
like
a
z
system,
or
is
it
like
Rel
running
on
C
system
that
happens
to
have
a
a
package,
an
ansible
pack,
because
it
needs
to
be
compiled
right
I.
Imagine
like
there's,
you
know
it's
a
different
CPU
architecture.
D
Yeah,
no
that's
a
great
question.
Actually
ansible
today
doesn't
run
on
the
s390
architecture
in
a
supported
way.
Now
you
can
certainly
there
are
definitely
people
who
are
rebuilding
ansible
recompiling
it
to
run.
You
know
like
in
a
Docker
container,
on
Linux
on
z,
that's
available
as
well.
But
again
you
know,
and
especially
with
like
things
like
awx
too,
but
when
we're
talking
ansible
automation,
platform,
things
like
that
and
getting
service
and
support,
that's
not
technically
a
supported
route,
but
it
does
work
there.
D
But
you
know
our
strategy
and
what
we've
you
know
been
working
with
a
lot
of
clients
really
is
you
know
getting
clients
comfortable
as
as
well
leveraging
off-platform
ansible
right,
leveraging,
x86,
environment
and
managing
you
know
their
Z
systems,
environments,
because
I
think
that's
one
of
the
other
challenges
with
the
Mainframe
Community.
Is
the
idea
and
very
much
being
used
to
being
in
silos
right.
D
So
they
actually
don't
even
need
to
know
how
to
deploy.
Ansible
have
to
manage
those
environments.
They're
just
getting
straight
to
writing.
Playbooks
and
saying
this
is
what
we
need
go
deploy
it
on
your.
You
know,
existing
automation,
controller
and
you
know,
give
us
access
to
that
and
we'll
go
from
there.
B
What's
what
I
find
really
cool
about
that
in
like
I?
Guess
it's
worth
mentioning
about
ansible,
because
as
ansible
is
really
for
for
better
I
guess
you
can
make
an
argument
either
like
it
is,
or
it
isn't,
but
it's
kind
of
agentless
if
you
think
about
it
right
and
agentless,
meaning
it
uses
SSH
so
technically,
running
SSH
is
the
agent
but
really
I,
guess
SSH
and
you
know
maybe
a
couple
of
python.
Libraries
is
really
like,
just
the
bare
minimum
to
have
like
a
client
out
there
right.
B
C
A
Lean
into
it
not
be
allowed
to
name
things,
we
really
should
not
be
allowed
to
name
things.
I
say
this
as
somebody
who
this
week
heard
like
four
times
yeah.
This
thing
was
great,
but
the
name
was
terrible.
I'm
like
yeah,
but
see
I
work
at
red
hat,
and
you
know
that
I
belong
here,
because
I'm
also
bad
at
naming
things.
A
And
if
I
understand
it
correctly
and
I
think
I
saw
this
on
the
website.
The
hybrid
cloud
with
mainframes
is
becoming
a
thing:
that's
becoming
a
standard
architectural
model
as
we
move
into
what
is
this,
this
increasingly
complicated
global
economy,
global
data
economy
even
as
well,
because
part
of
the
reason
I?
A
What
are
the
drivers
for
that
I
believe
is
actually
also
the
fact
that
you
have
the
data
sovereignty
laws,
so
some
of
these
places
have
been
moving
their
piping
all
of
their
data
through
like
what
one
Mainframe
and
somewhere
someplace
right
and
now
with
data
sovereignty
laws.
They
can't
do
that,
but
with
they
don't
also
don't
want
to
lose
everything
they
have
already
going.
That's
a
good
thing
on
the
Mainframe,
so
I
think
that's
one
of
the
reasons
why
we're
starting
to
see
a
hybrid
Mainframe,
Cloud
architecture,
model
and
I
think
ansible.
A
D
That's
absolutely
right:
I
mean
ansible
fits
perfectly
within
that
hybrid
Cloud
strategy
and
that
ecosystem
and
deployment
you
know
model
that
we're
seeing
a
lot
of
customers
go
forward
with,
as
well,
obviously
with
ansible
being
able
to
automate
against
all
those
different
Cloud
platforms,
AWS
gcp,
Azure
ANSI
systems
and
then
also
actually
be
deployed
on
all
those
things
as
well.
You
know
that's
another
option.
B
B
You
know
I
was
going
back
before
with
the
different
architectures
I
mean
I
include
arm
in
that
as
well.
Right
like
it's
just
like
you
have
this,
you
know
you're,
managing
your
your
Mainframe
you're
at
managing.
You
know
your
x8664,
your
arm
architecture
and
we'll
also
have
support
for
things
like
networking
equipment
right
like
like
they
can
log
into
like
your
Cisco
switches
and
right
start
making
updates
and
getting
those
there's
F5.
B
You
know
for
your
load
balancers
like
there's
a
there's,
a
module
for
that
there's,
a
module
for
like
Windows
as
well,
like
it
really
has
become
kind
of
like
a
lingua
Franca
right
for
like
sys,
admins
and
and
really
kind
of,
like
you
know
the
go-to
for,
like
you
know
some
more
of
like
the
cloud
native
sort
of
like
workflows
right.
You
know
we've
here,
you
know
at
the
stream.
B
We
feature
Argo
a
lot
right,
but
and
we
concentrate
on
cloud
native
infrastructure,
but
there's
like
you
know,
that's
like
really
only
a
small
part
of
like
your,
maybe
your
entire
organization
right,
you
may
be.
You
may
have
to
manage
other
things.
That
is
maybe
not
so
Cloud
native,
and
it
really
is.
B
C
That
yeah
and
you're,
hitting
at
one
of
our
biggest
entry
points
here,
because
in
most
cases,
right,
ansible's
already
running
in
our
clients,
shops
just
not
on
the
Mainframe
side
of
the
house,
so
they've
already
recognized
the
value
that
Ansel
can
bring
their
business.
They
have
used
cases
that
have
been
proven
for
great
use
cases
for
ansible
and
now,
with
the
content
that
that
you
know,
mine
and
Brian's
teams
are
being
able
to
provide
to
the
ansible
community
you're,
basically
just
extending
the
value
that
you've
already
recognized
now
to
the
main
frame
as
well
right.
A
So
we've
talked
about
the
good
I'm
gonna
skip
the
bad.
Tell
me
about
the
ugly.
What
are
some
of
the?
What
are
some
of
the
the
hardest
things
you've
had
to
solve?
What
are
whether
that's
a
people,
a
process
of
Technology
kind
of
an
aspect?
What's
what's
what's
the
ugly
about
this,
because
it
all
I
mean
I.
We
know
it's
good
we're
here,
because
we
know
it's
good,
so
tell
us
a
little
bit
about
the
ugly.
C
We've,
ultimately
come
up
with
a
pretty
good
story
there
about
the
benefits
of
of
you
know,
Creed
of
being
onboarded
onto
that
existing
ansible
architecture.
That's
you
know.
Standing
up,
you
know,
that's
been
stood
up
already
and
allows
kind
of
the
Mainframe
side
of
the
house
to
focus
on
playbook
development
and
Source
control
management
of
their
playbooks
and
not
have
to
focus
on
installing
ansible,
Tower
or
ants
of
automation,
platform
and
managing
all
the
role-based
assets.
Trolls
that
come
along
with
that
of
Distributing
that
automation
across
the
Enterprise
right.
D
Yeah,
honestly,
that
was
the
first
one
that
came
to
mind
as
well
kind
of
touching
on
a
little
bit
of
what
I
talked
about
around
the
cultural
aspects
of
things
right,
the
silos
that
some
clients,
you
know
want
to
continue
to
kind
of
keep.
You
know
ownership
of
right
and
kind
of
keep
their
teams
like
within
these
these
silos
and
and
being
really
comfortable
around.
D
You
know,
starting
to
leverage
more
open
software,
more
open
tools,
right
and
actually
trusting
some
of
the
new
skills
as
well
from
the
other
platforms
or
their
new
tenure.
Folks,
who
actually
are
more
familiar
with
some
of
this
stuff,
because,
again,
the
main
frame
platform
is
highly
specialized
and
takes
years
and
years
of
experience
right
to
really
be
comfortable,
be
productive
and
understand
the
inner
workings
of
the
system
and
for
someone
to
be
able
to
come
in
and
leverage
a
tool
like
ansible
and
be
immediately
productive
right.
D
B
What's
the
most,
so
what
what
I'm
interested
in
right,
like
all
right,
cool,
like
you
guys,
are
using
ansible
and
you
know
the
there's
customers
using
it,
which
is
like
on
Z
systems,
which
was
amazing
just
thinking
in
my
head.
How
much
this
this
this
this
piece
of
software
has
grown.
What's
the
what's
the
most
unique
thing,
you've
you've
seen
being
automated
and
what
I
mean
unique.
I
mean
like
like
specific
disease
systems.
B
A
C
C
B
Yeah,
that's
one
thing
actually
again:
another
paradigm
shift
and
another
thing
about,
like
you
know,
patching
and
upgrading
like
Z
systems
is
I
mean
we
we,
you
know
on
the
other
side
of
the
fence.
Take
you
know
we
take
advantage
of
things
like
dnf
or
apt,
even
things
like
RPM
and
Debian
packages
like
that
that
stuff
is
that
stuff
is
easy
right,
like
I
used
to
manage
Solaris
systems
and
like
even
on
the
spark
right
like
it's,
it's
it's
it's
not
it's
not
so
easy
to
do.
B
Whatever
your
your
flavor
is
even
easier
now
on
on
kubernetes,
where
you
just
pull
a
new
image,
the
you
know
that
that's
another
Paradigm
Shift,
it's
like
oh
yeah,
updates,
like
I,
just
took
it
for
granted
like
on
Amazon
x86
system,
just
say,
upgrade
this
package,
but
like
never
really
occurred
to
me
that
yeah,
it
is
a
little
bit
more
complex
on
on
a
Mainframe
right
like
it
was
complex
on
a
spark
system
like
like
me.
Thinking
back
I
would
imagine
it's
like
probably
exponentially
more
complicated,
like
on
a
z
system,
yeah.
D
And
just
to
give
a
little
bit
more
insight
into
kind
of
what
it
looks
like
with
smpe.
That
one
of
the
differences
here
is
that
products
are
shipped
not
as
as
one
all-encompassing
binary
package,
it's
shipped,
basically
as
a
library
of
a
bunch
of
different
modules
that
you
install
and
then
when
you're,
actually
installing
with
SMP
there's
different
zones.
So
you
have
like
your
distribution,
libraries
and
your
target
libraries
that
basically
make
a
copy
of
your
runtime
of
your.
D
You
know
product
that
you're
installing
and
then,
when
you
apply
updates
to
that,
you
basically
get
something.
What's
called
like
a
PTF
which
I
think
is
a
program
temporary
fix.
But
that's
like
an
update
of
a
small
subset
of
your
library.
So
you
get
different
modules
that
have
actually
been
updated,
so
you're
doing
an
incremental
update
you're,
not
ever
installing
the
entire
package.
D
B
I,
remember
like
updating
spark
systems
like
I'm
just
making
this
this
analogy,
because
it's
probably
very
similar
because,
like
you,
would
download
the
patch
and
then
like,
oh,
you
know,
the
system
will
tell
you.
You
can't
install
this
patch
because
you
need
this
patch,
so
you
go
to
that
patch
like
well.
You
can't
install
this
patch
because
you
need
this
other
patch
and
then
you
try
to
install
that
other
patch
and
you're
like
well.
It's
incompatible
with
your
system.
B
You
installed
that
you
know
boss
would
be
like
you
install
that
patch
it
to
the
to
the
systems.
It's
like
well,
I'm,
still
trying
to
three
weeks
later,
I'm
still
trying
to
like
figure
out
like
which
set
of
patches
is
the
magic.
You
know
the
thing,
so
you
know
some
of
the
things
that
we
kind
of
take
take
for.
C
A
Don't
know
compounding
nightmares
here,
I
think
so:
yeah,
okay,
if
I
I
I'm
trying
to
be
slightly
mindful
of
time
and
we're
at
a
little
under
40
minutes
right
now.
So
I
really
really
want
to
talk
about
these
open
shift.
Playbooks
I'm,
seeing
in
this
in
this
GitHub
repo.
Let's
talk
about
openshift
and
mainframes.
C
C
C
Think
I
honestly
did
that
three
years
ago,
before
I
took
this
role
in
ansible
land
as
assistant
programmer
installing
one
of
the
first,
you
know
demo
openshift
systems
for
our
technical
sales
communities
there
with
an
ansible
Playbook
that
was
provided
from
the
openshift
and
Z
development
team
back
in
the
day.
So
that
was
a
pretty
cool
thing
to
be
able
to
do
back
then,
on
Linux
on
Z
I.
C
Think
the
other
side
of
it
is
really
being
able
to
work
with
ansible
operators
and
being
able
to
provide
self-service
type
of
approaches
for
developers
to
be
able
to
drive
tasks
via
these
ansible
operators
via
openshift.
You
know
no
matter
really
where
you're
logging
into
this
openshift
environment
from
you.
Have
these
tasks
available
at
hand
to
be
able
to
drive
I
know,
that's
what
Bryant
has
kind
of
been
driving
as
a
part
of
one
of
our
other
offerings
at
IBM
I'm,
providing
these
operators
to
be
able
to
provision.
D
A
No
I,
so
this
is
one
of
those
things.
You
probably
know
this
being
preaching
to
the
choir
here
right.
The
the
kubernetes
operator,
like
the
SDK,
is
just
that
is
ansible
right.
That's
that's
ansible
under
the
hood,
so
you
can
have
a
goaling
operator
or
you
can
have
an
ansible
operator.
You
can
have
a
Helm
operator.
You
can
I.
Think
I
saw.
There's
Java.
Operators
is
another
one
in
the
work
right
you
you
can
have
whatever
flavor
of
that.
A
You
want
it's
various
levels
of
capabilities,
but
it's
because
it
is
ansible
under
the
hood
right.
You
just
get
so
much
of
that.
Basically
for
free
with
the
ansible
operators.
Like
the
the
I
know.
We
talked
about
this
in
our
emails
and
I
could
not
find
it
when
I
went
to
look
for
it
again,
but
the
process
to
go
from
ansible
playbooks
to.
B
B
A
You
or
there
was
when
I
went
looking
for
it
again.
I
couldn't
find
it
I
know.
I
sent
you
all
something
along
that,
though,
that
that
should
simplify
it,
but
there
at
least
there
was
it
probably
still
exists.
It
just
got
moves
and
I
didn't
know
where
to
find
it.
So
somebody
from
the
ansible
group,
if
you
know
where
that
went
to
tell
us
we
want
it,
but
anyway
yeah
so
I.
A
A
A
C
I
think
that's
a
good
question,
I
think
more
recently
we're
looking
at
more
integration
with
some
of
the
bigger
hyperscalers
out
there
as
well
I
think
that's
an
angle
that
you'll
start
seeing
coming
from
from
IBM
pretty
soon
here
you
know,
taking
advantage
of
some
of
the
you
know,
maybe
Source
control
libraries
that
they
that
they're
using
over
there.
You
know,
specifically,
we
worked
in
the
major
Bank
who
you
know
all
of
their
ansible.
Playbooks
are
actually
hosted
in
Azure
repositories,
and
now
it
kind
of
is
a
nice.
C
You
know:
that's
some
of
the
power
of
ansible
too
right
is
that
now
we're
able
to
have
Azure
collections
that
are
driving
Azure
processes,
matched
up
with
the
zos
playbooks
that
are,
you
know,
driving
zos
processes
and
it's
kind
of
this
hybrid
Cloud
landscape
that
we're
just
generally
creating
right
there
through
ansible
as
well,
but
yeah
I.
Think
the
hyperscaler
stuff
is
probably
what
I'd
go
to.
What
about.
D
You
Brian
yeah,
no,
that's
that's
what
I
was
thinking
about
as
well.
I
think
openshift
very
much
is
a
part
of
many
of
our
Mainframe
customers,
hybrid
Cloud
strategy,
because
again
it
is
for
us
from
the
IBM
perspective,
a
key
piece
in
in
what
we're
providing
from
the
cloud
native
developer
experience
right.
That
really
is
you
know
our
solution.
It's
centralizing
around
openshift
and
all
of
our
other
platform
tools.
D
You
know,
I
I
talked
about
the
zeros
Cloud
broker,
but
that's
really
only
one
of
the
very
you
know
many
other
components
that
we
have
in
that
in
that
offering
and
being
able
to
leverage
that
with
openshift
and
also
you
know
be
able
to
deploy
that,
so
it
is
available
as
a
self-managed
service.
You
know
within
AWS,
you
know
and
and
we're
working
on
other
Cloud
platforms
as
well,
but
you
know
I
think
it
is
really
a
key
piece
for
any
of
our
Mainframe
customers
in
the
hybrid
cloud.
C
D
So
some
I'll
touch
on
some
of
the
other
components
right.
We
have
this
whole
Wazi
Suite
of
tools
which
you
know,
code
ready
workspaces
as
part
of
that
Wazi
sandbox,
which
provides
the
ability
to
deploy
containerized
us
environments
as
well
in
openshift
right.
So
you
can
actually
deploy
a
virtualized
dos
and
use
that
as
a
Dev
test
sandbox,
we
have
a
number
of
of
analysis
tools
right
being
able
to
analyze
your
applications
and
you
know
be
able
to
see
all
the
different
dependencies
API
tools
as
well.
B
D
A
A
Specifically.
He
has
this
great
story
about
going
back
out
of
retirement
for
Contracting
for
the
Y2K
stuff
and
having
to
is
having
to
expand
the
date
fields
from
a
two-digit
to
a
four
digit
and
he's
telling
me
he's
like
yeah.
You
know
it
wasn't
that
we
couldn't
do
it
at
the
time.
It
was
that
never
in
our
wildest
dreams
did
we
think
this
stuff
would
still
be
running
yeah
yeah.
They
did
not
think
they.
A
B
Well
and
I
think
I
think
it
goes
to
it's
indicative
of
like
how
much
like
kind
of
like
to
your
point,
Hillary,
like
hi.
How
much
of
the
stuff
is
like
still
out
there
in
production
and
still
running
things
this
like
I
I,
always
you
know,
I
see
you
know,
people
time
to
say.
Oh
the
open
shift
on
Z,
that's
kind
of
weird,
like
you
know,
openshift
like
why.
B
B
Imagine
a
financials
kind
of
situations
where,
like
Banks,
need
to
do
these
transactions
like
Ultra
quickly
right
like
if
you
think
about
like
kind
of
like
some
of
the
stuff
like
I,
you
know,
you're
paying
you
know
for
things
like
using
your
phone,
like
those
transactions
go
really
quick.
They
show
up
almost
immediately
on,
like
your
bank,
like
some
of
these
transactions
have
to
go
really
really
fast
and
I
I.
Imagine
like
NASDAQ.
Also,
like
needs
super
super,
fast
transaction
and
so
yeah.
B
C
Absolutely-
and
you
know
about
what
about
two
and
a
half
three
years
ago
now,
when
some
of
the
election
stuff
was
going
on,
Cobalt
was
going
viral
because
some
of
those
back
end
some
of
those
applications
to
drive.
Some
of
that
you
know
was,
maybe
not
you
know,
being
perceived
as
working
correctly
and
Cobalt
went
completely
viral
at
that
point,
which
you
know
you
know
definitely
wasn't
Cobalt's
fault
and
I.
Think
IBM
said
some
pretty
good
messages
about
that
at
the
time.
C
But
you
know
I
think
it
was
like
when
I
cut
off
Brian
there
I'm
sorry
about
that
Bryant
and
he
was
getting
into
the
API
strategy
and
kind
of
hitting
on
your
point
Christian.
You
know
for
this
stuff:
that's
been
used
forever.
Now,
that's
where
it's
really
really
cool,
because
now,
what
we're
doing
is
we're
taking
some
of
those
components
of
those
applications
that
have
been
in
production
for
40
60
years
and
we're
front
ending
that
with
an
API.
So
then
we
can
leverage
some
more.
C
A
By
the
way,
quick
piece
of
career
advice,
Cobalt
Engineers
still
get
paid
very
well
still
a
relevant
skill
of
every
now
and
again,
my
father-in-law
still
gets
a
call,
and
it's
like
hey.
Are
you
he's
like
no
I'm
retired?
He
he's
an
instructor
at
Danza,
Community
College,
he's
very
happy
with
that.
He
he'd
be
quite
content
to
never
program
in
Cobalt
again,
but
that
is
not
a
that.
That
is
not
a
disappearing
skill
that
it
said
it's
still
highly
sought.
After
so
you
know
all
those
occasional
early
career.
A
D
There's
a
lot
of
resources
out
there
available
now
again.
Sometimes
Mainframe
has
that
sort
of
perception
that
you
know
it's
inaccessible
and
there's
not
a
whole
lot
of
information
around
it
or
at
least
to
learn
which
is
true
to
a
certain
extent.
But
more
recently,
there's
been
a
lot
of
effort
around.
You
know:
curating,
more
programs
and
resources,
and
things
like
that
and
you
know
IBM
Z
explores
one
of
those
right
where
you
know
it
used
to
be.
You
know,
formerly
known
as
Master
the
Mainframe.
A
C
Of
people
that
have
went
through
Master,
the
mainframing
z
explorer
there
and
gotten
jobs
just
based
off
of
the
basic
level
of
training
for
the
Mainframe,
because
those
skills
are
so
specialized
that
you
learn
as
a
part
of
that
training
program.
I
also
believe
there
are
Awards
along
the
way,
as
you
get
through
the
different
levels
of
that
training,
that
they'll
send
you
like
a
cool
IBM,
backpack
or
you
know
some
cool,
IBM
swag,
so
just
a
little
incentivization
to
maybe
go
check
out
that
program
in
the
process.
Oh.
A
My
gosh
I,
have
you
guys
wouldn't
know
this,
maybe
even
most
of
the
stream
Watchers
wouldn't
know
this
I
do
an
entire
I
have
a
red
hat
sponsors,
a
non-profit,
Community,
cold
women,
software
engineering
with
a
non-profit
called
the
wit
Network,
where
we
teach
women
how
to
do
things
like
pass
coding
interviews.
Do
General
code
mentorship
I,
actually
literally
have
a
coding
coach
coffee
hour
next
week
that
I
didn't
have
an
agenda
for
yet
and
guess.
What
is
my
new
agenda?
This
is
going
to
be.
This
is
my
new
agenda
for
it.
A
A
C
Well,
I
think
that
was
something
that
we
can
talk
about
quickly.
Is
you
know
red
Hat's,
doing
a
great
job,
enhancing
the
ants
of
automation,
platform
as
a
whole
right
and
as
new
features
come
out
for
the
ansible
automation
platform?
We're
trying
to
be.
You
know,
right
behind
them
and
being
able
to
extend
those
features
for
zos
and
the
Mainframe
right.
So
there's
some
really
exciting
announcements
that
had
recently
come
out.
I
believe
that
the
last
Red
Hat
Summit
and
you
know
at
other
conferences
around
this.
C
It's
going
to
be
able
to
populate
A
playbook,
not
only
with
the
modules
that
you
want
to
build
out
there
for
your
automation,
but
also
ingesting
the
system,
specific
information
to
fill
in
the
variables
it
needs
to
so
we're
looking
at
a
super
cool.
You
know
future
with
ansible
here,
not
only
from
that
perspective,
but
also
helping
our
Mainframe
Community
get
started
and
adopt
this
technology.
By
being
able
to,
you
know,
take
advantage
of
those,
you
know:
Auto
completion,
type
of
capabilities
there
and
Brian's,
the
one
you
know,
leading
the
charge
there
yeah.
D
I
mean
generative
AI
I
mean
that's
such
a
Hot
Topic
nowadays,
and
it's
just
super
exciting
again.
I've
been
able
to
work
with.
You
know
some
of
the
early
wisdom
models
and-
and
you
know,
do
some
a
little
a
little
bit
of
training
of
that
with
some
of
our
Z
Collections
and
it's
just
super
exciting
for
me
to
be
able
to
say
copy
a
data
set
to
blah
blah
blah
and
it
automatically
populates
all
of
our
modules
for
zos,
with
the
correct
parameters
right
and
and
understand
some
of
the
contexts
within
the
playbooks.
C
D
A
B
A
C
A
A
I
was
watching.
I
was
watching
the
numbers
go
through
and
we
had
over
86
people
watching
at
a
certain
point
awesome.
So
that
was
obviously
a
topic.
People
were
excited
about
we'll
keep
in
touch.
Maybe
have
you
guys
come
back
about
something
sometime
or
just
I,
so
that
more
people
can
nerd
out
about
Mainframe,
since
it
was
a
very,
very
exciting
topic
and
thank
you
again
also
for
the
resources.
A
C
A
C
B
A
All
of
my
favorite
things
coming
together
in
one
place,
that's
a
good
day
for
me.
All
right,
I
have
a
really
hard
stop,
so
I
have
to
Force
Christian
industry.
Thank
you
guys.
So
much.
We
really
appreciate
you.
You
can
follow
both
Bryant
and
just
or
Daniel.
Just
sorry,
I
read
your
last
name.
First
I'm
the
worst
follow
them
both
on
LinkedIn
and
I.
Think
I.
It
never
doesn't
apply
as
always.
Choose
your
technical
debt
wisely
folks
and
we'll
see
you
back
here
in
two
weeks.