►
From YouTube: In the Clouds with Red Hat Leadership (S1 E6): Joe Fitzgerald, VP and GM Management Business Unit
Description
Red Hat’s senior leadership is having to execute at an ever-increasing pace. That means that today's technology decisions have to balance short-term risk with long-term gains. This unique series provides host Chris Short inviting thoughtful and candid discussions with each guest. This episode's senior leader is Joe Fitzgerald, VP and GM Management Business Unit.
A
Good
morning
good
afternoon
good
evening
and
welcome
to
a
very
special
episode
of
openshift
tv,
I'm
joined
by
the
one,
and
only
joe
fitzgerald,
the
vp
and
gm
of
management
of
business
unit.
This
is
our
in
the
clouds
with
red
hat
leadership
series.
Joe.
Would
you
like
to
introduce
yourself
to
the
audience.
B
Sure,
hey
chris
thanks
for
having
me
joe
fitzgerald,
as
chris
said,
I
run
the
management
and
automation
businesses
here
at
red
hat.
I'm
super
excited
to
join
you
my
background.
I've
spent
over
35
years
in
I.t,
mostly
in
the
area
of
management,
so
I've
seen
a
couple
of
different
generations
of
a
couple
of
different
paradigm
shifts
and
looking
forward
to
the
next
one.
Here.
A
Yeah,
a
couple
paradigm
shifts
yeah,
there's
been
so
much
change
in
the
industry,
especially
this
year.
You
know
in
in
ansible
and
acm
advanced
cluster
management
are
both
under
your
purview
right.
So
there's
a
lot
of
automation
there
and
you
said
it
the
other
day.
I'm
still
your
thunder
a
little
bit,
and
you
know
you
said
that
forrester
called
automation,
a
boardroom
topic
right,
like
I
can't
remember
what
the
exact
quote
was,
but
like
automation,
is
now
key
in
the
the
circumstances
that
we're
in
in
the
world.
A
B
B
2020
was
sort
of
like
an
accelerant
right
where
we're
just
automation
takeoff,
and
it's
funny.
You
know
with
thousands
of
customers,
you
know
they're
using
ansible,
and
when
we
talk
to
them
you
know
it's
funny.
Each
one
has
a
different
automation
perspective,
so
we're
trying
to
automate
their
traditional,
it's
they
can
move
people,
and
you
know,
resources
to
do
a
new
digital
transformation.
B
You
know
stuff
other
people
already.
You
know
on
the
digital
transformation
side
and
they're
trying
to
accelerate
other
people.
Just
have
you
know
simple
things
like
access
problems
or
don't
have
enough
staff
or
have
you
know
time
to
market
challenges
that
drives
automation.
So
it's
pervasive,
but
the
stories
are
different.
You
know
across
each
each
enterprise.
A
So
you
know
I'm
a
huge
fan
of
ansible
right
like
I've
used
it
since
you
know
2013
2014,
I
think
right,
like
I
remember,
answering
fest
pre-acquisition
kind
of
deal
right,
so
you
know
I
always
ask
people
like
how
did
you
first
become
involved,
not
just
with
ansible
or
kubernetes
but
like
how
do
you
become
involved
with
redhead
like
not
as
an
employee
but
as
a
consumer
customer?
And
I
think
in
your
case
you
have
a
very
unique
situation.
B
B
My
sort
of
journey
was,
I
would
say
well,
over
15
years
ago
we
were
using
rel
right
at
enterprise
linux
to
develop
and
test
software
on
like
a
lot
of
people
right
and
with
a
lot
of
customers
who
are
running
in
production.
So
that
was
our
target
platform
right
for
some
of
the
software
we
were
developing
then
about
10
years
ago
I
founded
a
startup
around
management
right
because
that's
the
area
that
I've
been
in
and
we
were
a
redhead
partner.
B
So
then
I
dealt
with
red
hat
as
a
you
know,
go
to
market
partner,
which
was
you
know,
another
sort
of
facet,
and
then
eight
years
ago,
actually,
eight
years
ago,
in
a
couple
weeks
here
in
december,
red
had
acquired
the
company.
That
was
that
I
found
manage
iq
and
I
joined
red
hat
and
at
the
time
red
hat
didn't
have
a
management
business
unit.
They
had
management
software.
They
had
satellite,
they
had
a
number
of
technologies,
but
over
those
years
we've
really
looked
at
management.
B
Automation
focused
on
on
hybrid
clouds
and
ansible,
showed
up
on
my
radar
pretty
early
and
ended
up
bringing
ansible
and
through
acquisition
about
five
years
ago.
So
it's
been
an
interesting
journey
at
red
hat
over
the
past.
You
know.
Well,
it
goes
back
15
plus
years,
but
right
now,
for
eight
years.
A
B
A
What
do
we
do
to
make
sure
that
it
was
a
success
like
it
has
been?
In
my
opinion,
you
know
you've
gone
through
quite
a
few
acquisitions.
I
think,
and
the
the
the
things
that
we
did
to
make
ansible
successful
like
how
what
what
were
those
steps?
Like
I'm
sure
there
was
some
missteps.
But
what
do
you
think
were
the
good
things
that
we
did
to
bring
ansible
on
board.
B
It's
a
great
question
and
so
at
last
count
I
think
I've
been
acquired
at
least
five
times,
and
you
know
history
shows
a
lot
of
acquisitions.
Don't
work
well
right!
There's
culture
clashes,
there's
expectation
gaps,
there's
all
sorts
of
challenges
with
ansible.
I
was
determined
since
I
was
the
person
driving
the
acquisition.
B
I
remember
asking
you
know
the
red
hat
senior
management
to
acquire
ansible,
and
so
I
felt
like
I
was
not
only
responsible
to
red
hat
for
the
success,
but
also
for
the
company
and
the
people
that
were
ansible
and
the
technology,
and
so
we
had
a
couple
of
advantages.
There
were
a
number
of
ex
red
hat
folks.
It
was
culturally
compatible
with
red
hat,
so
that
was
a
good
starting
point,
location
wise.
They
were
close
to.
You
know
red
hat.
You
know
facility
in
north
carolina
and
raleigh,
but
they're
in
durham.
B
We
have
facilities
in
raleigh's
close,
but
it's
more
than
that
a
lot
of
times
in
the
acquisitions
I've
been
through.
They
start
changing
things
almost
immediately
out
of
the
gate.
Let's
make
this
thing
apart.
We
love
this
thing,
you've
built
now.
Let's
take
it
apart
right
and
move
it
into
different
teams
here
and
split
up
and
whatever
the
magic
was,
and
whatever
that
thing
was
that
you
acquired
it
becomes
sort
of
disassembled
like
a
transmission
when
they
go
put
it
back
together.
B
They're
like
what's
this
gear,
what's
that
gear,
and
so
with
ansel
we
were
determined
not
to
screw
it
up
both
from
a
you
know,
a
company
culture
as
well
as
from
a
community
point
of
view.
So
ansel
was
a
small
company
right
when
we
acquired
it
five
years
ago.
It
had
a
you
know,
sort
of
you
know
young
but
excited
community.
Oh.
B
You
know
I
I
would
say
you
know
I
I
you
know
we,
we
didn't
screw
it
up
right
from
a
community
point
of
view,
we've
actually
been
trying
to
catalyze.
You
know
facilitate
work
with
the
community
in
a
way
that
has
seen
this
huge
proliferation
of
automation.
Ansible
has
expanded
into
so
many
domains.
Networking
security
we're
moving
towards
edge
where
we've
instrumented
it
into
all
these
different
ways
to
invoke
automation,
because
that's
important
too,
but
from
the
community
side
it
was.
B
It
did
very
well
from
a
sort
of
a
corporate
side
like
how
we
integrated
it
inside
red
hat.
It
wasn't
perfect,
no
acquisitions
ever
perfect,
but
it
was
pretty
good
in
terms
of
making
sure
that
we
listened
to
the
people
who
came
over
from
ansible
since
they
knew
it
in
business,
integrating
it
with
we've
integrated
it
to
a
lot
of
the
different
technology
areas
inside
red
hat.
Oh
yeah.
B
A
Well,
I
think
one
of
the
coolest
things
we
did
as
a
company
here
at
red
hat
was
when
we
made
insights
was
that,
like
we
gave
people
like
here's
what's
wrong,
but
also
here's
potentially
a
playbook
that
could
fix
it
right,
like
it's
not
just
like
identifying
problems
right,
like
any
number
of
tools,
could
identify
a
problem.
It's
the
identifying
the
problem
with
the
knowledge
that
we
have
here
at
red
hat
and
then
giving
you.
You
know
the
expert
produced
playbook
to
fix
it
like
that.
A
It's
changing
settings,
not
installing
packages
right
like
it's
very,
very
complex
things
that
we're
asking
people
to
do
to
get
work
around
bugs
between
like
oracle
database
and
red
hat
enterprise,
linux
kind
of
thing
and
you
know
to
hand
someone
a
playbook
to
fix
those
things-
is
just
an
amazingly
powerful
thing
in
my
opinion,
because
that
playbook
can
be.
You
know
considered
trusted
to
an
extent
right
like
it's
coming
from
red
hat
and
yeah.
B
Yeah,
I
think
a
couple
of
comments
about
that.
First
of
all,
for
those
of
you
who
don't
know
what
redhead
insights
is
basically
it's
a
sas
service
that
we
offer
that
there's
no
cost
right
for
our
subscribers.
Basically,
what
it
does
is
it
analyzes
rail
systems
to
determine
their
configuration
settings
software
patches,
you
know
things
like
that
and
then
basically
either
tells
people
what
they
need
to
fix
change
or
what
their
their
risk
profile
and
their.
B
You
know
potential
for
challenges,
the
environment,
and
then
we
can
either
tell
you
about
it
or,
as
you
just
mentioned,
we
can
drive
an
ansible
playbook.
Now
I
want
to
separate
those
two
thoughts
for
a
second
one
of
the
things.
I
think
that
is
a
sort
of
paradigm
shift.
That's
occurred
and
is
continuing
to
occur.
Is
what
I'll
call
composable
management,
what
the
hell's
composable
back
to
it.
Think
of
a
devops
tool
chain
right.
B
What
are
people
doing?
They
have
a
tool
chain?
What
is
it
mulching?
It's
a
collection
of
different
tools
that
do
different
things
along
the
process
of
you
know,
building
and
integrating
and
testing
applications
and
deploying
right
and
even
within
the
same
organization.
You
may
have
different
different
tools.
The
point
is
that
you
can
unplug
one
tool.
If
you
don't
like
your
current
version
control
system,
you
can
unplug
it
and
plug
in
another
one
and
the
wrap
your
tool
chain
is
still
relatively
intact.
I
call
that
composable
management.
B
About
darwinism,
now
it's
about!
Well,
you
know,
if
I'm
not,
if
I'm
not
happy
with
my
monitoring
tool
or
my
version
or
my
testing
system,
I
can
go
swap
in
another
one,
and
I
don't
have
to
like
change
my
entire
world
in
order
to
do
that.
So
getting
back
to
ansible
ansible
is
very
composable.
It
does
automation.
B
B
Call
ansible
right.
People
use
ansible
in
their
in
their
devops
tool
chains,
but
a
lot
of
operational
teams
use
ansible
for
a
whole
set
of
operational
issues,
the
other
dynamic
there
is
because
it's
composable
keep
expanding.
What
it
can
do.
We've
seen
a
lot
of
people
adopt
it
as
a
standard.
Now
you'd
used
to
be
balkanized.
You'd
have
corp.
Enterprises
have
dozens
of
automation
tools;
they
always
did
networking
one
for
storage,
one
for
compute
one
for
accounts.
B
All
different
things,
and
so
now
what's
happened,
is
there's
now
a
tool
that
can
automate
across
these
different
domains.
Well,
wow.
What
does
that
mean?
That
means
I
can
now
have
a
person
who
understands
how
to
automate
across
domain.
That's
a
pretty
useful
person
today,
oh
yeah,
well
we're
trying
to
adapt
to
do
things
fast.
I
don't
have
to
I'm
the
storage
guy
call
the
network
guy.
I
need
changes.
Okay,
call!
The
you
know.
B
A
I
think
that
that
very
much
rings
true,
because
I
remember
like
right
before
I
switched
from
the
ansible
team
over
to
the
openshift
team.
It
was
very
much
I
was
seeing
the
world
through
ansible
lenses
right
like
that
bespoke
ipmi
device
that
I
needed
to
talk
to
that
that
weird
switch
hanging
out
over
here
that
that
cloud
service
hanging
out
over
there.
I
just
went
to
the
ansible
module
and
I
would
read
the
I
would
read
the
doc
and
I'd
be
like
okay.
A
I
understand
how
this
thing
works,
just
reading
the
documentation
from
ansible
about
the
cloud
native
service
or
the
cloud
thing
or
the
storage
thing
or
whatever,
and-
and
I
could
very
much
feel
pretty
confident
about
what
I
was
doing,
because
I
knew
like.
Obviously
I
wasn't
deleting
things
I
was
you
know,
updating
or
maintaining,
or
you
know
changing
things,
but
I
wasn't,
you
know
doing
anything
destructive.
So
I
knew
that
ansible
was
going
to
do
that
in
a
safe
way.
A
Right,
like
the
modules
are,
you
know,
written
and
tested
and
so
forth,
so
that
I
can
trust
that
it's
going
to
do
what
I
tell
it
to
do,
and
that
includes
the
entire
module
suite
right,
like
potentially
thousands
and
now
the
modules
are
collections,
and
you
know
there's
a
whole
decision
behind
that.
You
want
to
talk
about
ansible
collections
at
all
or.
B
Sure
yeah,
let
me
talk
a
little
bit
about
the
sort
of
the
the
parts
and
pieces
because
I
think
it's
important
right.
I
talked
about
composable
management
at
a
high
level.
One
of
the
reasons
I
think
the
ansible
community
has
been
so
successful
and
why
the
automation
has
proliferated
is
because
it's
modular,
you
can
add
an
ansible
module,
as
you
know
that
integrates
into
people
have
done.
You
know
smart
light
bulbs
or
all
sorts
of
strange
devices.
Why?
B
Because
it
doesn't
have
to
put
an
agent
on
it,
just
needs
a
network
connection
and,
second
of
all,
because
I
can
write
a
module,
an
ansible,
that's
very
bound
in
terms
of
the
scope
of
what
I
need
to
add
to
write
that
module.
I
don't
have
to
you,
know,
compile
a
system
with
8000
modules
and
hope
everything
is
all
you
know
correct
and
everything
else.
B
B
When
you
take
that
automation,
whether
it's
the
modules
that
integrate
into
you
know
different
apis
and
software
and
hardware,
and
things
like
that
or
the
playbooks
right
that
actually
describe
what
kind
of
automation
you
want
to
do,
or
the
roles
or
the
other
parts
and
pieces
you
can
just
go
out
to
the
community
and
go
you
know,
pull
stuff
out
and
say
geez,
I
you
know
I've
got
a
lot
of
time
on
my
hands
and
you
know
I'm
just
doing
this.
For
myself,
hey,
I'm
gonna
go
grab
this
stuff.
B
I'd
like
to
know
what
people
are
running
right,
especially
if
they're
touching
network
devices
and
firewalls
and
ports
we
integrate
into
security
systems
we
can
create.
We
can
do
all
sorts
of
things
across
many
many
different
domains,
that's
the
power
of
it,
but
you
want
to
make
sure
that
you
have
certified
curated
content,
how
you
distinguish
between
I'll
call
it
community
grade
automation
and
enterprise
grade
automation,
okay,
what
I
use
in
my
house
to
turn
on
the
lights
in
my
room
or
to
play
music
on
a
you,
know,
smart
speaker
or
something
awesome.
B
You
know
attenuator,
I'm
thinking
that
I
probably
want
enterprise-grade
automation
and
so
what
we've
been
doing
is
we
have
been
taking
the
automation
that
the
community
and
red
hat
develop
and
we've
been
moving
them
into
certified
collections
right
and
it's
a
coherent,
curated
sane
certified
supported
set
of
automation
that
you
can
count
and
if
you
have
a
problem
with
it
or
if
it
breaks
or
if
there's
a
security
expo
we're
gonna
tell
you
we're
gonna
we're
gonna
update
it.
We're
gonna
support
you.
So
it's
sort
of
the
old
red
hat
mantra.
B
A
So
right
like
incredibly
dangerous
right,
high
pressures
high
temperatures
all
this
stuff,
but
they
were
managing
everything
like
one
like
one
by
one
on
you
know
everything
was
this
bespoke
thing
and
it
was
just
like
how
do
you
know
when
something
changes
right
like?
How
long
does
it
take
for
you
to
see
the
update?
It
was
like
minutes,
and
it's
like
you
know,
if
something's
exploding,
I
kind
of
want
to
know
now
not
later
right
like
because
you
know
we
were.
A
You
know
hundreds
of
thousands,
not
thousands,
maybe
thousands
of
feet
away
from
the
actual
manufacturing
facility.
Monitoring
these
things
so
having
consistency
across
the
board
made
tremendous
difference
in
how
we
monitored
all
these
weird
kind
of
you
know:
manufacturing
pieces
of
equipment,
but
ansible
gave
us
that
flexibility
to
do
it
and
if
we
didn't
have
it,
I
definitely
feel
like
there
would
have
been
a
lot
more
issues.
B
So
now
now
look
around
the
corner
edge
is
coming
five
to
your
incoming.
What
does
that
mean?
You're
gonna
have
orders
of
magnitude,
more
devices
running
more
software,
connecting
across
more
diverse
network
conditions
that
are
going
to
require
security
settings
applications,
all
sorts
of
updates
right,
and
so
it's
essential
that
in
that
environment,
that
you
have
automation
that
scales,
that
is
reliable,
that
can
handle
the
diversity
of
devices
network,
connectors,
hardware
and
software.
B
So
ansible
is
going
to
have
a
big
role
to
play
in
edge
automation
and
that's
a
big
area
that
we're
pushing
on
and
again
it's
going
to
challenge
even
people
that
are
running
the
best.
You
know
highest
levels
of
automation
in
the
traditional
it
environment.
Now
you
add
another
comma
and
some
zeros
onto
the
end
of
the
number
of
devices
and
the
number
of
software
versions
and
os
patches
and
certificates
and
all
the
other
things
that
have
to
happen
to
make
everything
run
smoothly.
A
A
B
B
B
You
know
you
know
small
small
everything,
small
network
small,
you
know
you
know:
compute
small
storage,
small,
app
set
stuff
like
that
5g
5g
speeds
are
blistering
right,
and
so
it's
going
to
change
the
amount
of
network
bandwidth
available
right
to
to
talk
to
and
configure
these
devices.
By
the
way
these
devices
are
generating
a
ton
of
data
that
would
be
filtered
sifted,
managed,
collected,
exchanged.
B
You
have
models
going
down
right,
you
know
so
there's
a
whole
ai.
You
know
you
know
yeah
into
this,
like
what
do
I
do
with
all
data?
How
do
I?
How
do
I
control
you
know
and
automate
that
flow?
But
you
know
these
devices
are
not
tiny
devices
on
a
tiny
network
with
little
capacity.
These
are
becoming.
B
You
know,
multi-app.
You
know
fat
pipe
yeah,
you
know
decent
horsepower
systems,
and
so
what
does
that
mean?
That
means
more
apps
right,
more
settings
more.
You
know
things
that
have
to
be
managed
and
automated
and
that,
I
think
that's
you
know.
Every
infrastructure
or
software
paradigm
shift
has
had
a
corresponding
management
paradigm
shift.
I've
equip
it's
fitzgerald's
law,
you
know
what
I
mean
I'll,
see
you
with
new
management.
You
want
to
change
the
application
delivery
process,
I'll
see
you
with
new
management,
so
it's
an
evergreen.
B
A
I
agree
and
it
it
will
adapt
as
quickly
as
5g
will
force
us
right,
because
community
will
respond
in
kind
and
red
hat
will
as
well.
This
is
a
question
I
always
get
and
I
think
it'll
be
a
unique
question
for
you
specifically,
given
some
changing
of
things
behind
the
scenes.
You
know.
I
always
like
to
ask
our
leadership
the
same
question:
how
has
the
ibm
acquisition
impacted
you
and
the
business
unit,
the
management
business
units.
B
B
There's
always
you
know
sort
of
a
concern
whenever
an
acquisition
occurs,
whether
you're
being
acquired
like
we
were
with
ibm
or
whether
we
were
acquired
like
in
the
case
of
america
or
when
I
was
acquired
advantage
iq
in
other
companies,
so
I
think
ibm
did
a
really
good
job
at
sort
of
the
same
philosophy
that
we
took
to
much
smaller
ansible
acquisition,
which
is
you
know,
sort
of
the
hippocratic.
Oh
first
do.
C
B
B
B
We
may
be
changing
them
as
opposed
to
them.
Changing
us
right
right,
but
you
know
paul
who
drove
the
red
hat.
You
know.
Product
technology
strategy
for
for
two
decades
is
doing
it
at
the
ceo
level.
Now
for
red
hat
with
the
same
philosophy
and
the
same
experience
and
ibm
has
embraced,
encouraged
and
supported
that.
So,
if
anything,
it's
added
more
sort
of
fuel
and
energy
to
the
red
hat
system,
so
much
what
we
did
with
ansible.
If
ansible
was
a
smaller
standalone
company,
they
would
have
had
a
different
journey.
B
B
A
B
A
Know
a
lot
of
my
friends
are
like
well,
we'll
see
you
in
two
years
and
I'm
looking
at
the
clock
and
the
calendar,
and
I'm
like
a
lot
of
stuff
would
have
to
change
in
the
next
few
months
for,
like
that,
two-year
thing
to
pay
off
right
for
them.
So
it's
kind
of
like
yeah.
You
know
I
stuck
around
for
good
reasons.
A
Right,
like
red
hat,
has
pretty
much
been
untouched,
but
I
think
one
of
the
coolest
things
that
ibm
did
like
very
early
on,
I
feel
like
was
moving
the
the
mcm
crew,
the
advanced
cluster
management
team,
over
to
red
hat
and
the
way
we
handled
that
as
like
putting
them
through
new
higher
orientation
and
treating
them
as
like.
Hey
welcome
to
red
hat
the
new
company
right,
like
your
new
employer
kind
of
thing,
but
very
much
still
working
with
our
ibm
team.
I
thought
that
was
so
cool
and
how
that
was
done.
B
Hear
that
yeah?
No,
I
that's
another
interesting
dynamic,
which
is
you
know
a
lot
of
times.
The
direction
when
you
are
acquired
right
is
the
acquiring
company
starts
sort
of
breaking
parts
off
right.
That's
part
of
the
disassembly,
hey
you've
got
this
great
thing:
let's
move
it
into
the
department,
you
know
or
the
organization
here
that
works
on
that
thing
or
is
craving
that
thing
in
this
case
ibm
actually
went
the
other
way
and
said
you
know
what
we
have
some
technology
here.
B
That
is
actually
a
better
fit
with
the
red
hat
portfolio
and
it
would
be
built
in
the
open
right
and
it
should
grow
in
this
environment,
so
they
actually
moved
the
team
and
the
technology
over
to
the
red
hat
side,
we're
in
the
process
of
open
sourcing
it
just
like.
We
were
open
sourcing,
the
private
code
that
ansel
had
yeah
right,
so
we're
being
red
hat
about
this,
but
I
thought
that
was
another.
You
know
incredible
proof,
point
that
ibm
said
look.
B
This
is
you
know
we
could
have
kept
it
on
our
side
and
you
know
kept
it
blue
and
you
know
done
whatever,
but
we
think
it's
a
much
better
for
open
community
for
innovation
for
what's
going
on
in
advancing
these
container
environments,
they
pushed
it
to
the
red
side
and
then
into
the
open.
So
that
seems
fantastic
by
the
way.
B
If
you
want
to
talk
about
technology
that
was
built
from
scratch,
you
know
on
kubernetes
for
kubernetes
with
deep
kubernetes
experience,
that's
one
of
the
things
that
you
know
as
sort
of
composable
management
that
integrates
to
openshift
and
federates
openshift
clusters.
Basically,
you
know
looks
at
you
know:
controls
cluster
lifecycle
management
activities.
It
looks
a
policy
governance.
B
It
looks
at
application
deployment.
You
can
do
it
based
on
policy
and
tags
really
powerful
stuff.
We
plugged
ansible
into
that
working
with
that
team,
so
we
extended
ansible
in
a
way
that
look
at
the
right
point
in
time
when
something
happens,
invoke
an
ansible
playbook.
Why
is
that
important?
Most
of
the
conversation
we've
had
today
about
ansel
has
been
around
the
technical
side.
Events
we'll
go
integrate
with
storage
or
network
or
security
or
something
yeah,
there's
a
whole
other
set
of
ansible
integration
that
maybe
it's
not
so
exciting,
which
is
go
open
up.
B
A
change
ticket
go
change.
The
cmd
go,
do
something
to
the
systems
of
record
that
has
to
track
what's
going
on
in
this
highly
dynamic
environment,
and
we
have
a
ton
of
customers
doing
that
in
all
different
ways.
That's
what
we
did
was
we
said
well.
Can
we
make
this
easy
make
it
easy
to
plug
in
these
legos
these
automation
legos
at
the
right
place
during
the
processing
of
these
environments,
whether
you're
deploying
new
apps,
deploying
new
infrastructure,
changing
you
know,
policies
and
you
know,
and
settings,
and
things
like
that.
B
Can
we
actually
make
it
easier
and
we
worked
with
the
acm
team
to
do
that
and
wow.
We
showed
that
at
ansible
fast
and
I'll
tell
you
it's
people
like
wow,
that's
exactly
what
I
was
looking
for
so
again,
one
of
those
areas
where
we're
extending
automation
into
a
domain,
in
this
case
openshift
and
kubernetes,
but
also
the
instrumentation
one
other
comment
about
that
when
we
acquired
ansible
five
years
ago,
their
main
product,
their
flagship
product,
was
ansible
tower.
Yes,
okay,
it
was
private.
There
was
an
open
core
model.
B
You
know
the
rest
of
the
stuff
was
open.
Source
tower
was
closed.
We
open
sourced
it,
but
what
we've
done
is
we've
extended
ansible
in
so
many
ways
in
how
you
invoke
automation
most
recently,
in
addition
to
acm
and
ansible
fest,
we
demoed
openshift
serverless
proof
of
concept,
invoking
ansible.
What
does
that
mean?
Well,
you
can
do
event
driven
automation.
B
Well,
isn't
that
cool
right?
I
can
take
events
coming
in
now
and
instead
of
driving.
You
know
serverless
right.
You
know
I
can
still.
You
know,
use
openshift
serverless
to
kick
off
python
or
some
other.
You
know
you
know
function.
I
can
now
do
function
as
a
service
where
the
function
is
the
ansible
playbook
right.
So
we're
building
bridges
to
enable
the
community
to
go
wow.
You
know
what
I
could
do
with
that.
B
A
Exactly
yeah,
it's
it,
you
know,
I
hate
to
say
it,
but
this
was
the
first
year
in
quite
some
time
that
I
wasn't
able
to
make
it
to
ansible
fest,
because
I
was
doing
things
like
this.
You
know
live
streaming
to
the
greater
red
hat
communities
in
world.
So
how
was
ansible
fest
this
year?
It
was
virtual
for
the
first
time
ever.
B
So
look,
you
know.
2020
was
a
year
of
great
adaptations
right
for
all
for
all
these
industries.
You
know
events,
everything
became
virtualized.
Red
hat
summit
became
virtualized.
You
know
we
had
a
venue
picked
out
for
ansible
fest
we're
going
to
go
to
san
diego.
We
have,
we
had
all
the
you
know,
logistics
and
everything
was
all
set
up
and
it
was.
It
was
going
to
be
a
wonderful
thing.
Then
the
world
you
know,
threw
us
a
curveball.
B
Like
many
other
events,
we
went
virtual,
we
said
you
know
we
just
don't
want
to
have
a
like
sort
of
the
online
version
of
what
we
would
do
at
a
you
know,
convention
center
or
hotel
with
whatever.
How
can
we
make
it
better
right?
And
so
your
team,
in
a
typical
ansible
way
that
you'll
appreciate,
said
how
would
we
do
this
differently?
How
would
we
approach
this
differently
and
then,
of
course,
we
we
set
up.
You
know
sort
of
the
whole
virtual
event
process,
and
you
know
we
said
how
many
people
show
up.
B
B
A
C
B
People
registered
okay
and
and
more
than
half
those
people
showed
up
a
lot
of
people
register
for
events
and
then
their
schedules
change
or
they
watch
it
recorded
or
whatever
it
is
yeah,
but
but
but
over
half
of
those
people
showed
up,
and
you
know
we
had
people
registered
from
over
130
countries
wow
it
was.
It
was
a
global
event.
We
had
customers
and-
and
you
know,
people
presenting
technology
from
from
a
number
of
different
geographies.
B
It
was
amazing
right
in
terms
of
the
amount
of
interest.
I
think
that's
that's
a
tell
about
how
important
automation
is,
but
specifically
ansible
and
I'll
I'll
make
a
claim,
and
you
know
people
can
take
it
with
a
grain
of
salt.
I
work
for
a
vendor.
You
know
disclosure,
you
know
whatever
design
work
for
red
hat
ansible,
I
think
is,
has
become
or
is
becoming
the
de
facto
automation
technology
for
for
a
lot
of
reasons.
B
B
So
by
all
the
numbers,
it's
really
really
growing.
If
you
look
at
the
domains
that
we
can
automate,
if
you
go
back
five
years
and
say
okay,
what
can
you
actually
automate
with
ansible?
And
then
you
compare
the
number
of
modules
and
playbooks
and
roles
and
all
the
different
things
that
can
be
used
to
automate
now
it's
an
explosion
of
domains
and
things
that
you
can
automate
and
the
ways
that
you
can
invoke
automation
and
so
we're
seeing
a
lot
of
people
that
are
sort
of
they're
standardizing
on
ansible.
A
B
C
B
B
If
one
team
builds
some
awesome
automation,
wouldn't
it
be
great
if
all
the
other
teams
could
find
it
use,
it
rely
on
it,
oh
and
by
the
way,
when
that
automation
gets
updated,
that
they
could
know
and
get
it
and
use
it,
and
that
people
who
are
like
looking
at
all
these
systems
could
figure
out
what
what
are
we
automating
right?
How
is
it
working
how's?
It
scaling?
What's
the
you
know,
what
what's
the
view
on
all
that
stuff?
B
B
So
that's
the
kind
of
thing
that
red
hat's
been
really
investing
in
and
showing
leadership,
which
is
how
can
we
make
it
so
that
a
very
large
distributed
organization
could
share
automation
at
a
large
scale
that
is
reliable,
certified
supported
trusted
and
give
them
visibility?
We
added
analytics
services,
we're
adding
more
so
that
they
can
look
at
the
automation
and
over
time,
be
able
to
understand
what
animation
am
I
running?
What
are
my
you
know?
You
know
how
how
long?
What's
the
you
know,
success
rate
of
that
automation?
How
long
does
it
take?
B
What
did
I
say,
what
was
the?
What
was
the
sort
of
that?
You
know
people
displacement
by
running
that
automation?
How
fast
am
I
doing
things?
How
am
I,
how
am
I
scoring?
What
automation
am
I
using?
What
are
the
other
people
using
out
there?
What's
the
best
way
to
automate
this
situation?
What
are
other
people
doing
by
having
those
kind
of
analytics
people
can
make
better
choices?
You
do
it
in
your
consumer
life.
You
go
check,
reviews
you
go
see
what
other
people
are
doing.
You
want
to
understand.
B
A
Absolutely
so
so
I'm
I'm
trying
to
feed
some
links
to
some
folks
in
chat
here,
just
real,
quick,
yeah
someone's
asking
about
the
new
kubernetes
collection,
so
that
was
announced.
I
think
this
week
or
last
week,
but
I
gotta
find
the
blog
post
so
any
partying
thoughts
before
we
go
joe.
I
think
we've
kind
of
run
through
all
the
questions
that
I
can
think
of.
B
B
Where
would
I
use
automation
in
this
area?
How
many
automation
tools
do
I
have
I've
got
six
10
12.,
I'm
gonna
get
it
down
to
two
three
one:
how
many
teams
are
doing
automation
in
my
environment?
I
bet
you
if
you,
if
you
really
looked
inside
your
organization,
you
find
a
lot
of
people.
Oh
I'm
doing
it.
I
got
scripts.
I
got
this,
I
used
this
tool
wrote
this
thing
you
know
is
that
the
business
that
you're
in
are
you?
Are
you
a
software.
B
A
A
force
of
nature,
yes,
please
check
out
ansel.com,
there's,
there's
tons
of
resources
available.
There
there's
also
galaxy.ansible.com,
where
you
can
pick
up.
You
know
all
the
community
contributed
collections
and
playbooks
and
roles
as
well.
As
you
know,
just
follow.
Jeff
gerling
on
twitter
and
you
know,
like
you'll,
have
a
wealth
of
ansible
knowledge
just
right
there.
I
can't
I.
A
Yeah
yeah
all
the
fast
contents
out
there,
and
then
you
know
just
you
know
you
mentioned
linkedin.
You
mentioned
you
know
it's
a
good
thing
for
your
career.
I
credit.
You
know
three
pieces
of
technology
for
changing
my
career,
linux,
ansible
and
kubernetes
right,
like
ansible,
definitely
changed
my
career
completely
right,
like
went
from
just
like
sysadmin
plugging
away
at
stuff
to
like
okay,
now,
you're
gonna
be
a
devops
engineer.
You're
gonna
do
automation
at
scale.
You're
gonna
help
us
solve
these
big
problems
of
deployments.