►
From YouTube: APAC Hybrid Cloud Kopi Hour (E7) | Automation!
Description
Main Deck: https://speakerdeck.com/redhatlivestreaming/getting-started-with-event-driven-automation-and-ansible-lightspeed
Ansible Lightspeed Tech Preview: https://docs.ai.ansible.redhat.com/
Event Driven Ansible: https://ansible.com/event-driven
Get Hands On!: https://labs.demoredhat.com/
Are you ready to make your life easier?
Join us for a special session of the Kopi Hour on all things automation! Our panel of experts will introduce you to some of the most exciting new concepts in automation, from Event Driven Ansible to Ansible Light Speed. We'll also be talking about AI, integration, and more.
Your guides are Red Hat APAC associates Mitesh Sharma, Richard Hailstone, and Prakhar Srivastava. They will share their expertise and insights on how you can use automation to save time, improve efficiency, and get more done.
This session is for anyone who is interested in learning more about automation. Whether you're a beginner or an experienced user, you'll come away with new knowledge and skills that you can use to automate your tasks and workflows.
00:00 Intros
06:45 Automation at Red Hat
10:00 Event Driven Ansible
27:18 Ansible Lightspeed with IBM Watson Code Assistant
36:50 Demo intros
41:27 Demo Event Driven Ansible
54:05 Demo Ansible Lightspeed
A
A
A
As
a
quick
reminder,
we
are
talking
copy,
which
is
a
wonderful
coffee,
drink
you
get
in
Singapore,
which
I
usually
have
a
cup
of
today,
but
with
our
later
start
today,
it's
a
bit
too
late
for
a
coffee
drink,
so
I've
gone
for
some
water,
which
you
can't
you
can't
really
see.
Maybe
if
I
get
it
there,
we
go
some
water,
so
that
is
where
we
get.
The
name
from
I
am
August
simonelli
I'm,
a
technical
marketing
manager
at
red
hat
and
I'm
usually
joined
by
Dave
Schoenberg.
B
A
And
so
we,
you
know,
while
kopia
hour
was
super
important,
he
was
he's
spending
time
with
his
family.
Now,
however,
I
do
have
some
great
guests
with
us
here
today
to
talk
about
something
very
exciting
automation.
So
let's
go
ahead
and
around
the
room,
we'll
basically
go
alphabetically
and
start
off
with
who
we
have.
The
first
person
is
Richard
Hailstone
who's,
a
principal
special
solution,
architect
from
Red
Hat
Richard.
Why
don't
you
go
ahead
and
say
hello.
B
A
D
D
Our
mission
is
to
optimize
sales
and
marketing
strategies,
ensuring
that
the
word
truly
grasps
all
the
grind,
breaking
capabilities,
which
we
have
with
red
hat
all
the
products
which
people
have
inward
hat.
We
try
to
Showcase
that
in
front
of
our
customers
using
sales
and
marketing
strategies
and
marketing
strategies,
initiatives
like
these,
which
August
is
hosting
in
here,
thanks
August,
for
giving
us
the
opportunity
to
talk.
Thank
you.
A
No
I'm
thrilled
to
have
you
guys
here,
so,
let's
get
right
to
it.
So
today
we
are
going
to
talk
about
Automation
and
specifically
a
couple
of
exciting
product,
new
products
or
product
enhancements
that
we
have
in
the
automation
space
before
we
jump
into
that,
I
want
to
go
through
a
little
bit
of
something
as
I
like
to
do
in
the
morning
in
in
the
shows.
I,
don't
know
how
many
people
know
what
you're
looking
at
here.
So
this
is
my
journey
to
automation.
Do
you
guys
know
what
that
is?
A
Brother
maybe
this
is
this-
is
Big
Brother
four,
so
this
was
monitoring
software
that
we
implemented
at
a
job
that
I
was
at
in
I,
don't
know
early
2000s
right
and
so,
where?
How
do
we
get
to
automation?
Well,
Big
Brother
obviously
monitored
our
systems
and
we
had
to
get
notifications
to
make
Big
Brother
work.
So
this
is
I
found
this.
This
is
literally
from
the
original
notes
from
like
2002,
and
this
is
what
we
had
to
deal
with.
This
is
what
they
put
on
their
website.
A
You
know
you
had
to
do
these
crazy
things
to
make
it
work,
and
so
you
know
if
we
could
get
notified,
then
we
would
take
action.
So
then,
obviously
that
was
crazy,
so
we
moved
up
to
nagios,
which
is
still
popular
today,
and
this
is
just
my
you
know
notific.
This
is
a
monitoring
software,
so
nothing
to
do
with
automation.
But
of
course
we
then
wanted
to
automate
system
builds
tied
into
nagios,
tie
it
into
alerts
and
I.
For
me,
it
was
always
puppet
that
I
used
still
out
there.
A
We
played
with
CF
engine
and
stuff
like
that,
but
where
am
I
going
with
this
right?
Well,
the
world
and
for
sysadmins
has
changed
a
lot,
and
so
we've
moved
into
this
one.
You
know
this
this
world
of
Eda.
What
is
Eda
well
you're,
going
to
hear
that
today
the
guys
will
teach
you
about
that.
But
what
was
it
for
me?
Well,
Eda
was
event
driven
August,
so
when
an
event
happened,
I
got
a
page
on
my
BlackBerry
and
I.
Remember
sitting
there.
A
You
know,
maybe,
with
my
baby
like
when
the
girls
were
little
and
I'd
get
a
notification.
You
know
a
server
is
down
something's
wrong
whatever,
and
so
that
was
how
we
did
things
and
nothing
fixed
anything
for
me,
I
got
a
page
or
I
had
to
get
out
of
the
supermarket
line
and
deal
with
it
and
all
that
kind
of
stuff.
A
That's
not
what
we
do
anymore
and
we're
gonna
actually
move
ahead
and
I've
got
a
subtle
reference
reference
to
one
of
our
product
names
we're
going
to
go
light
speed
into
the
future,
which
is
now
today
to
talk
about
where
we
actually
are.
With
this
whole
process
and
how
we
can
be
a
lot
more
proactive
and
productive
in
the
way
we
do
things
so
I'll
shut
off
my
silly
slides.
A
So
where
are
we?
What
does
this
mean?
It's
kind
of
exciting
and
I
I'm
super
excited
to
see
that
we've
got.
We
do
have
some
comments
coming
in
on
the
chat.
We've
got,
people
very
excited,
automation
is
it's
like
Las,
Vegas
man,
it's
shiny
and
it's
happening
and
there's
stuff
going
on
so
I'm
super
chilled
I'm
super.
You
know
excited
for
that
too.
So,
Richard
I
think
you
know
it
would
be
good
to
hand
over
to
you
to
kind
of
set
the
stage
of
all
these
things.
B
Yeah,
that's
a
really
awesome.
Acronym
you've
changed
it
to
the
August
event,
driven
in
August
and
I.
Think
I'm
going
to
make
a
suggestion
that
we
change
it
immediately
and
the
logo
I
know
exactly
what
that's
going
to
look
like
now
too,
for
the
Improvement
automation,
so
I
too
yeah
I
started
way
back
in
the
in
the
days
of
CF
engine.
B
B
You
there,
the
thing's
starting
to
Arc
up,
so
apologies
for
that
yeah.
So
you
know
over
time.
You
know
customers
like
the
way
Red
Hats.
You
know
software
development
model.
Works,
obviously,
is
we
do
everything
based
in
community
upstream
and
then
we
package
that
into
the
lovely
milk
container
like
to
call
products
and
we
life
cycle
that
and
it
moves
forward
and
that's
sort
of
where
you
know
we
went
with
ansible.
We
we
turned
those
two
products
that
we
had
into
one
and
renamed
it
a
platform.
B
You
know
devops
sort
of
functions
that
you
do
when
you're
automating
things
there's,
like
a
you
know,
a
capability
within
the
platform
to
sort
of
match
each
one
of
those
touch
points
as
you
try
and
move
the
automation
through
your
environment
right.
So
people
still
think.
Oh
ansible
automation
platform,
that's
just
ansible,
but
it
you
know
it's
so
much
more
than
that
and
I
think.
What
we're
here
today
to
talk
about
is
I.
B
B
B
I
guess-
and
you
know
that's
another
one
commodity
like
that's
an
imperative,
but
I
think
we
still
struggle
to
see
people
putting
slas
around
Automation
and
it's
still
just
a
really
a
nice
to
have
I
think
that's
kind
of
like
the
last
mile.
We
need
to
get
through,
but
certainly
writing
code
and
getting
assistance
with
that's
gonna.
You
know
it's
going
to
be
a
game
changer!
It's
going
to
have
a
good
knock-on
effect
for
what
we
can
do.
Events
we're
moving
forward
nice
cool.
A
B
Cool
cool
there
you
go
cool,
yes,
I'll
put
some
slides
together.
I've
got
the
agenda
there
and
it's
not
really
agenda
right
so,
but
we've
just
mentioned
we're
going
to
go
through
event,
driven
ansible,
and
so
they
so
so
that's
been
added
to
the
platform
as
a
capability.
As
of
the
2.4
release
of
automation
platform,
you
know
so
you
can
draw
down
and
use
this
today
as
you
can
with
Lightspeed.
So
these
two
capabilities,
Lightspeed,
is
you
know
it's
a
free
public
service,
though
it's
being
released
as
a
tech
preview.
B
In
this
sense,
anyone
can
use
it
if
you've
got
an
automation
subscription
or
not.
So
it's
yeah,
it's
very
nice
additions
to
the
family
as
I
mentioned
earlier,
so
we're
going
to
go
through
I'll,
go
through
a
quick.
You
know
a
brief
intro
to
those
two
capabilities
and
then
I
think
we're
gonna
run
a
demonstration
of
this
stuff
too.
So
event
driven
automation
is
essentially
I
like
to
think
of
it.
B
Rather
than
this
long-winded
definition,
it's
essentially
like,
as
in
most
event-driven
architectures,
we're
talking
about
consumers
and
producers
right
so
in
event,
driven
in
the
event-driven
world,
something's
producing
an
event
and
another
thing's
reading
it.
You
know
instantaneously
and
that's
where
event
driven
automation,
steps
in
right
to
to
be
the
consumer.
In
that
scenario,
so
we're
talking
about
consuming
from
things
like
logging
platforms
or
alerting
systems
or
message
queues.
B
You
know
net
devices
directly
or
through
aggregated
platforms
as
well.
You
know
like
Splunk
or
even
your
itsm
tooling,
around
service,
now
that
any
anything
can
really
be
a
producer
in
this
sense-
and
you
know
it's
about
connecting
those
Dynamic
events
to
actions
and
actions
in
this
sense
of
automations
right
but
yeah.
B
Let's
expand
on
that
concept
of
event,
producers
a
little
further,
because
I
think
it
kind
of
shows
the
value
in
what
automation
platform
does
and
it's
in
in
wide
use
across
lots
of
organizations
already
and
so
what
event
driven
what
ansible
does
is
allows
you
now
to
tap
all
your
existing
Automation
and
the
ecosystem.
That's
within
ansible
right
into
that
sort
of
a
consumer
and
producer
ecosystem,
to
deliver
more
value
and
get
more
value
out
of
your
platform.
B
Okay,
and
so
you
know,
it's
all
designed
around
making
the
job
of
making
applications
run
more
smoothly,
more
uptime,
keeping
the
lights
on
all
that
stuff
and
across
a
hybrid
Cloud
architecture
like
we
have
these
days,
we've
got
stuff
in
our
own
data.
Centers
we've
got
stuff
in
cloud
and
a
mixture
of
apps
spread
across
those
and
automation
platform.
A
Yeah
so
I'm
thinking
about
producers
and
and
just
the
the
scope
of
it
right.
If
I
think
about
my
big
brother
days,
you
know
we
weren't
messing
with
network
switches.
We
weren't
messing
with
anything
beyond
a
basic
Enterprise
when
it
wasn't
even
relevant,
but
you
know
basic
Red
Hat
servers
that
kind
of
thing
we
just
we
didn't
we,
those
other
things,
were
the
domain
of
other
teams.
They
were
areas
you
didn't
touch
and
I
love.
How
this
kind
of
brings
everything
together.
Not
only
the
you
know
the
technology,
but
the
teams
right.
A
B
Yeah
and
those
technology
owners
can
still
look
the
good
way
that
ansible
structured
means
that
those
teams
and
those
owners
with
the
know-how
can
still
be
the
owners
of
that
domain
right.
But
the
platform
allows
them
to
do
that,
but
share
it
and
integrate
it
with
the
other
teams,
which
is
really
cool.
It's
powerful,
yeah.
D
A
And
it
was
terrifying,
I
mean
honestly
as
this
admin
it
was
terrifying,
I,
I,
didn't
know
what
was
going
to
happen
next
and
I.
Remember
one
time
all
the
guys
were
at
some
festival
and
I
was
the
only
one
and
it
was
like.
Oh
goes
wrong.
I,
don't
know
what
to
do
if
I
could
have
told
a
system.
Well,
if
this.
B
Yeah
for
sure-
and
you
wouldn't
have
you
know
with
something
like
this-
we're
talking
about
reducing,
wait
time,
an
event
happens.
Something
can
be.
You
know,
triggered
straight
off.
The
back
of
that.
You
know.
Wait
time
between
handoffs,
between
teams
or
getting
notifications
is
what
extends
the
outage
windows
and
all
those
sorts
of
things,
and
also
as
I
nutted.
In
your
slide
August,
you
had
a
Blackberry
in
there.
B
B
So
I'll
move
on
okay,
so
let's
have
a
look
at.
There
was
plenty
of
other
slides.
I
could
have
shown
at
this
point,
but
I
think
I
just
show
the
audience
a
quick
look
at
what
about
what
we're
talking
about
here.
So
if
you're
already
using
ansible
you're
familiar
with
playbooks
right,
so
everyone's
got
to
write
and
play
books
to
to
get
an
automated
outcome,
and
the
Playbook
shows
you
the
steps
to
get
that
automated
outcome,
and
now
what
we're
doing
with
event
driven
ansible
is
we're
having
Rule
books.
B
Okay,
it's
a
slightly
slightly
different
way
of
driving.
It
and
rulebooks
are
pretty
basic
to
understand.
They're
still,
look
and
feel
like
ansible
playbooks
they're
still
written
in
yaml,
but
they
have
a
source
and
then
a
condition,
and
then
an
action
and
the
sources
is
all
about.
You
know
all
this
stuff
I
had
in
the
previous
slide.
All
these
these
tools
and
tooling
that
you
know
operations
and
developers
and
alike
are
using
every
day
we
can.
We
can
match
sources,
today's
not
match
no
one
types
to
those
sources,
I
should
say:
take
the
event.
B
Payload
run
it
through
this
rules.
Engine
which
we
could
have
multiple
conditions,
we're
checking
for
and
then
run
a
Playbook
or
an
automation
off
the
back
of
that.
You
know
either
a
directly
or
with
raw
modules
being
called
here
from
ansible,
or
we
can
also,
you
know,
trigger
automations
to
run
within
automation,
platform
right
where
we
get
all
that
centralized
logging
and
credentials
and
all
the
extra
benefits
around
that.
B
B
This
is
engine
the
right
word,
I,
don't
know
if
it's
an
engine
but
yeah
a
conditional
framework
that
we
can
use
to
make
you
know
to
pull
apart
the
alert
that
we've
got
or
the
event
that
we've
received
to
pull
that
apart,
using
this
condition,
rule
book
or
engine
and
just
trigger
automations
off
the
back
of
that
yeah.
That's
all
baked
into
this.
This
new
capability,
yeah
right.
D
A
B
Indeed,
so
yeah
look,
I,
don't
think
I
will
dig
much
further
into
like
it
at
a
slide
level
right.
We
can
just
talk
around
this
a
bit
more
if
you
want,
but
I
think
somebody
some
of
the
cool
use
cases
I
think
I
mentioned
this
the
other
day
to
to
you
August.
We
were
talking
through
this
and
I
was
saying
like
how
you
know.
Some
of
the
conversations
with
customers
have
been
around
stuff
happening
in
the
data
center.
B
Someone
plugs,
you
know
a
cable
into
a
switch
or
something
like
that,
and
we
can
get
the
link
up
action
or
event
to
be
logged
Central
if
right,
an
event
driven
automation
can
be.
You
can
pick
up
on
this,
and
so,
if
that
event
comes
in
with
a
data
payload
saying
this
switch
in
Rally
For
example
or
Denver,
wherever
it
may
be,
just
had
a
link
up
on
it
on
Port
24.
we
can.
B
B
We
can
start
to
look
up
different
sources
and
use
the
information
to
match
and
then
allocate
IP
addresses
and
things
like
that,
for
example
to
the
device
that
perhaps
was
plugged
in
generated
DHCP
config
for
that
and
send
it
out
to
that
location,
to
sort
of
start,
that
process
up
and
then
potentially
bootstrap
the
thing
that
was
off
the
back
of
that.
So
this
is
really
cool
for
those.
Not
only
those
data
center
type
scenarios
where
people
are
plugging
things
in
whether
they're
meant
to
be
or
not
right.
We
can
also
do
the
reverse.
B
If
someone
plugs
something
in,
we
can
log
into
that
switch
and
shut
the
port
down
right.
But
but
you
know,
this
is
where
we
can
start
to
use
Automation
in
ways
we
haven't
been
able
to
use
it
before
in
a
little
bit
more
of
a
a
proactive
way
to
stop.
You
know
to
stop
people
having
to
to
get
involved
in
some
of
these
manual
tasks.
Yeah.
A
And
that
makes
sense,
I
mean
you
think
about
remote
data,
centers
or
inaccessible
data
centers
or
if
it's
just
the
time
to
get
to
them,
that's
pretty
powerful.
But
what
really
intrigued
me
there?
You
said
you
know
you
can
actually
block
an
action.
So
ansible
can
look
after
something
and
say:
look
this
port's
come
up,
it's
not
meant
to
so
take
no
action
or.
B
Yeah,
potentially
just
ignore
that
or
you
know
what
I
I
default
everything's
meant
to
be
switched
off
in
my
in
my
network,
so
nothing
should
really
be
getting
a
link
up
all
of
a
sudden.
So
because
we
know
what
port
it
was,
what
switch
it
was.
We
can
then
actually
go
and
Connect
into
that
with
the
automation
and
you
know,
shut
down
that
Port
so
to
speak.
So.
A
That's
cool
I
mean
that
from
a
from
a
physical
hack
or
a
security
point
of
view,
that's
powerful,
avoiding
a
mistake
and
we've
all
done
it
I
remember
when
it
wasn't
me
pulled
the
the
cable
out
of
the
exchange
server
but
and
I
know,
I
know
you
can't
stop
that
with
automation.
But
the
point
is
we
get
people
into
the
data
center
and
you
know
maybe
certain
areas
don't
have
to
be
touched
in
the
first
place.
Yeah.
D
A
B
Absolutely,
and
even
in
the
sense
yeah
not
having
someone
to
have
to
go
there
to
do
that
task
for
plugging
a
cable
in
or
to
do
the
extra
tasks
after
that,
I
guess
means
that
we
can
now
sort
of
deliver
equipment
remotely.
In
this
example-
and
you
know-
someone-
that's
not
even
necessarily
I.T
Savvy
can
potentially
just
plug
cables
in
off
the
back
of
that.
So
yeah,
there's
all
sorts
of
ways
to
apply
that
thinking
and
and
take
advantage
of
it.
Yeah.
A
And
I
assume
for
even
when
you
look
at
things
like
stores,
I,
guess
Edge
yeah
yeah
under
a
counter
at
a
at
a
at
a
gas
station.
Something
like
that
where,
if
things
are
hooked
up
the
right
way,
you
can
actually
start
to
I
mean
there's
not
going
to
be
someone
at
a
service
station
who's
able
to
do
that.
They
just
need
to
get
things
going
so
yeah.
B
B
We
call
all
these
things
use
cases
right.
What's
the
use
case
for
using
it
but
yeah
another
another
example
could
be
because
we
can
hook
into
monitoring,
Solutions
and
tooling,
like
I,
guess
you
know
app,
Dynamics
or
dynatrace,
or
some
of
those
other
partners
and
things
where,
where
we
can
look
at
the
performance
of
a
server
right
and
if
it's
underperforming
so
to
speak,
and
it
might
be
part
of
a
group,
we
can
start
to
look
at
things
like.
Why
is
it
underperforming
or
perhaps
it's
you
know
it's
on
a
noisy
server.
B
This
instance
that
slow
is
on
a
noisy
server
and
we
could
quickly
rebuild
a
node.
That's
on
a
not
so
noisy
server
or
redeploying
of
different
availability
Zone
to
add
that
back
into
the
cluster
and
take
the
slower
one
out.
You
know
we
can
start
to
do
things
like
that
and
with
these
conditional
engine
right
we
can
say
that
if
the
event
comes
in-
and
it
says
the
io
wait,
time
was
graded
in
15,
milliseconds
right
and
that's
slow,
like
let's
do
this
process
and
let's,
let's
be
proactive
about
it,
yeah.
A
And
that's
neat
because
the
time
is
spent
for
the
engineers,
not
in
fixing
broken
things
and
and
running
around.
You
know
trying
to
resolve
things
but
actually
planning
out,
like
you
were
mentioning
planning
out
scenarios
and
saying
if
we
architect
things
in
certain
ways,
we
understand
that
the
conditions
we
might
hit
and
actually
planning
for
that
and
and
I
think
that'd,
be
so
much
more
interesting
as
an
engineer
as
a
developer
as
well
to
get
to
interact
with
my
infrastructure
that
way,
rather
than
it
constantly
being
this
reactive
sort
of
panics,
probably
a
bit
of.
D
A
Of
there
I
mean
and
I
remember
back
in
in
those
days,
I
would
turn
my
phone
off
when
I
wasn't
on
call
I
mean,
like
phones,
have
off
switches,
you
know
so
because
it
was
really
stressful.
It
really
was
hard
and
it
also
meant
that
that
I
didn't
get
the
good
night's
sleep
or
whatever,
and
so
I
wasn't
actually.
And
then
this
is
my
bias
system.
Administration,
I'm,
sure,
there's
developer,
use
cases
too,
but
you
know
I
didn't
I,
wasn't
I
wasn't
sharp
the
next
day.
A
B
Yeah,
that's
it
it's
a,
but
I'll.
Just
come
back
to
the
original.
Point
too,
is
that
it's
kind
of
it's
good
for
the
people
using
it.
You
know,
because
the
people
that
are
getting
involved
and
writing
it
and
everything
you
know
a
little
bit
more
challenging
to
put
a
you
know
a
value
on
it
above
that
you
know
around.
You
know
how
is
it
improving
my
business
or
how
is
it
doing,
X
or
whatever
right
to
valid
to
to
make
some
of
this
more
relevant
up
the
chains?
B
You
know
to
people
that
allow
us
to
do
these
things
and
I
think
you
know
part
of
the
value
around.
This
is
particularly
around
that
that
mean
time
to
recovery
or
responding
to
stuff
that
lets
apps
stay
up
longer
and-
and
you
know,
business
is
less
impacted
right.
Doing
more
with
less
too
is
another
thing.
Metrics
around
that
right,
yeah.
B
B
I
love
that,
but
you
know,
certainly
people
will
will
listen
to
that
right,
because
that
is.
That
is
important.
That
is
key
to
having
a
good
business
right
absolutely,
but
it's
also
a
good
intro
to
the
next
point.
They're
August
right
around
sharing
is
caring
and
bringing
other
people.
You
know
making
it
easier
to
write
automation
or
even
improving
on
the
Automation
and,
of
course,
once
you
get
started
on
this
stuff,
it
can
be
a
bit
like
a
drug.
B
You
want
to
just
go
on
to
the
next
bit
and
the
next
challenge
and
see
how
far
you
can
push
this
stuff
right.
Yeah-
and
this
is
where
maybe
ansible
light
to
be
with
IBM
Watson
code
assistant
comes
into
play.
I
could
say
that
so
right,
so
this
is
pretty
cool.
This
is
a
new
feature
where
you
know
generative
Ai
and
language
learning
models
specifically
trained
with
ansible
content
right
specifically
trained.
So
this
isn't
a
language
model.
That's
been
trained
to
interpret
natural
language
and
and
spit
out
some
code.
B
This
is
a
language
model.
That's
been
trained
with
ansible
content
to
specifically
identify
a
request
and
match
an
example
to
it,
and
this
is
how
you
know
this
is
how
we're
going
to
take
these
people
with
the
know-how
in
an
organization
or
our
peers
that
haven't
written
automation
before,
but
they
have
the
know-how
about
how
things
hang
together
and
how
the
it
environment
operates.
B
Right,
there's
a
reason
why
you
used
to
get
called
at
that
time
in
the
morning
August,
because
you
know
you
were
the
only
guy
that
knew
how
to
bring
things
back
up
or
why
What
that
particular
failure
meant
whether
you
could
respond
to
it
or
whether
you
could
ignore
it
right.
So
that's
the
know-how,
that's
that's
the
stuff
that
we
can't
replace,
but.
A
B
Cool
very
cool,
and
that's
where
that
know-how.
We
can
start
to
put
it
in
a
model,
and
so,
if
we
capture
that
you
know
we
can,
we
can
start
to
get
this
model
to
suggest
Collections
and
ansible
code
based
on
that
know-how
and
examples
that
we've
fed
into
it
from
our
own
organization,
our
own
teams,
and
then
we
can
reiterate
that
process
each
time
as
the
next
people
come
and
use
it
right.
B
We
can,
we
can
build
upon
it
and
it
can
be
further
enhanced
and
customized
to
give
suggestions
and
things
that
are
relevant
for
what
we're
doing
right
and
I.
Think
that's
where
the
AI
really
needs
to
go
so
yeah.
Introducing
that
capability
and
red
hat
and
IBM
have
joined
forces
there
to
accelerate
your
adoption
of
you
know:
ansible
automation,
platform
and
and
get
more.
B
You
know
more
value,
I
guess
and
more
return
on
investment,
but
but
not
just
to
that,
but
also
you
know,
sharing
that
know-how
and
making
lowering
the
barrier
to
entry
for
people
wanting
to
automate
something
you
know
like
most
of
us.
The
way
we
learn
is
software
development.
These
days,
if
you
want
to
do
software
development,
where
do
you
go?
A
Yeah
and
I
think
it's
important
I
was
talking
to
a
nephew
of
mine
so
and
he's
in
computer
science
and
talking
about
Ai
and
co-generation,
you
know,
but
isn't
it
a
cheat?
Is
it
a
cheat
and
he's
like?
No,
this
is
the
way
things
are
done.
It's
a
way
to
learn.
It's
a
way
to
to
build,
to
educate,
to
use
that
Collective.
A
You
know
stuff
to
get
better
and
to
feed
back
in
and
all
that
and
I
think
that's
super
important
to
understand
that
it's
not
a
cut
and
paste
and,
oh
you
know,
I
did
my
job.
It's
helping!
You
build
your
own
skill
set
and
add
back
into
that
skill
set
and
into
that
Collective
group.
So
it's
it's
a
really
neat
thing,
because
at
first
when
I
was
seeing
these
demos
and
I'm
excited
to
see
a
demo
soon
it
was
sort
of
like
oh
wow.
A
This
means
you
know
my
my
five-year-old
I
don't
have
a
five-year-old,
but
you
know
my
five-year-old
could
could
write
code.
It's
like!
No,
that's
not
the
point.
There's
still
the
human
there,
knowing
what
they
need.
It's
getting
the
code
syntactically
correct!
It's
looking
at
different
ideas
of
how
it
can
be
better
and
I.
Think
that's
just
so
cool
and
you've
said
that,
but
it's
just
it
was
very
neat
to
hear
a
20
year
old
kind
of
really
get
this
confirm
it
yeah.
B
D
Just
a
tool
which
helps,
but
it
is
can't
replace
the
human
touch
and
you
need
to,
and
and
only
the
person
who
is
writing
it
understands
his
involvement.
The
any
language
processor
will
not
be
able
to
understand.
What's
going
on
your
data
center,
you
need
to
know
about
your
data
center
what's
happening
which
Cloud
you're
using.
So
it's
like
it's
a
tool
to
use,
but
not
it's
not
like
cheating
but
yeah.
A
D
B
B
D
B
You
know
something
to
something
to
give.
If
they're
going
to
work
with
me
and
so
so
I
think
AI
is
going
to
give
me
the
ability
to
go
in
there
and
play
with
it
see
what
they've
done
use
the
suggestions
get
the
feel
for
how
this
stuff,
you
know,
is
cobbled
together
before
I,
go
asking
all
those
dumb
questions
right
and
that
in
that
way,
I
can
sort
of
jump
in
where
they're
at
a
bit
a
bit
more
readily
and
a
bit
sooner.
So
that's
really
cool
yeah.
B
Thank
you
all
right,
so
look
I.
Think
we've
been
around
all
our
been
around
the
traps
with
some
of
these
other
points
right,
but
I
think
just
at
the
end
there.
Just
if
anyone's
interested
this
is
you
know,
I've
mentioned
it's
free,
so
just
hit
that
URL
at
the
bottom.
There
it's
self-supported,
and
so
so
you
know
no,
no
one
to
ring
at
this
point
at
3am
in
the
morning,
but
but
one
one
primary
thing
that
it
does
is
it's
targeted
at
developing
code
and
specifically
ansible
tasks.
B
So
a
natural
language
definition
of
the
task
is
all
you
need
hit.
The
enter
key
and
Lightspeed
will
make
a
suggestion,
but
moving
forward
I
think
the
you
know.
The
goal
would
be
for
light
speed
to
understand
the
project
that
you're
working
on
a
little
bit
more
broader
speaking.
What
what's
the
automated
outcome,
I'm
trying
to
get
rather
than
the
granular
task
by
task
and
then
I
think
where
it
can
go
to
from
there
is
maybe
understand
it
at
an
even
broader
level.
B
What
the
Enterprise
is
trying
to
do
as
a
whole,
for
example,
we
might
be
trying
to
move
to
Cloud.
So
if
you
say,
for
example,
you
know
I
want
a
provision,
a
user
or
I
want
to
give
someone
access
to
this.
You
know
the
automation
can
start
to
understand
the
difference
between
whether
that's
a
user
ad
command
on
a
Linux
machine
or
whether
it's
an
IAM
ad
or
an
active
directory
ad
in
the
cloud
and
so
on,
and
so
on.
A
Yeah,
which
is
the
reason
to
jump
on
now,
I've
put
the
link
in
the
chat
just
to
get
in
there
and
play
yeah
and-
and
we
can
put
these
slides
up
too
because
I
know
obviously
don't
touch
your
screen.
You
can't
click
it,
but
we'll
we'll
put
these
up,
although
you've
done
the
short
link.
So
that's
great
you'll.
B
A
Good
right,
so
it
gets
us
thinking.
It
gets
us
understanding
what
we're
talking
about
here,
but
the
best
part
is
when
we
can
see
it.
So
I
can
see
matisha
she's
starting
up
the
engine
it's
happening,
so
so
I
think
it
would
be
great
now
to
go
ahead
and
as
yeah
as
the
sun
comes
down
in
Sydney
to
go
ahead
and
get
a
demo
of
some
of
this
so
for
car.
A
D
So
I'll
put
some
fuel
and
before
we
start
there,
you
go
okay.
So
as
I'll
start
with
the
August
opening
comment,
which
was
ansible,
is
a
language
of
CIS
admins.
So
that's
what
we
are
trying
to
do
in
here,
big
thanks
to
Richard
for
setting
up
the
stage
as
we
deep
dive
deeper
into
the
limitation
demo,
keep
in
mind.
We
are
exploring
two
Dynamic
chapters
in
ansible's
word.
Firstly,
we
will
deep
dive
into
event
driven
ansible.
D
Now,
even
driven
invisible
is
not
just
limited
to
world
source,
as
Richard
was
explaining
just
now,
it
can
be
triggered
by
multiple
sources.
It
can
be
synced
with
the
platforms
like
alert
manager
or
Kafka,
and
so
on
now
in
today's
demo,
which
mitesh
will
be
showcasing.
We
are
zoning
in
openshift
events
now
so
when
a
new
namespace
rolls
out
in
openshift
health
doesn't
skip
it,
it
swiftly
sets
a
resource
quota,
ensuring
our
developers
really
nice.
D
They
don't
have
all
the
resources
on
offensive,
which
is
a
very
common
issue,
not
putting
the
resources
not
putting
the
limits,
requests
and
easily
without
any
bad
intentions.
They
hog
out
the
open
shift
resources.
Another,
a
very
common
thing
which
we
see
is
developers
generating
or
creating
a
route
and
forget
to
patch
it
with
TLS.
So
we
are
running
we.
B
D
Looking
at
the
openshift
event,
as
soon
as
the
route
gets
created,
it
should
patch
the
route
with
TLS
by
talking
to
the
search
manager,
so
there's
a
Playbook
which
will
trigger
using
that
event
and
will
pass
the
routes.
Another
common
thing,
which
we
see
as
soon
as
we
create
a
persistent
volume
claim,
a
snapshot
needs
to
be
taken.
So
that
is
one
of
the
other
things
which
mitesh
will
be
showcasing
now.
What
ansible,
driven
and
even
driven
ansible
is
all
about.
D
D
Now,
let's
switch
the
gears
and
talk
about
bit
of
a
light,
speed
which
again
mitesh
will
be
showcasing
now
consider
ansible
light
speed
as
ansible's
linguistic,
linguistic
sidekick,
he's
a
robin
for
our
Batman,
so
seamlessly
bridging
human
dialogue
with
automation.
Now,
as
ansible
light
speed
is
using
a
natural
language
processing
through
IBM
code
assistant,
it
effortlessly
turns
the
Casual
conversations
into
ready
to
rule
playbooks.
D
So
we
don't
have
to
worry
about
writing
correct
statements,
whatever
we
as
two
sis
admins
are
talking.
Let's
talk
to
the
light
speed.
Let's
tell
it
give
me
the
recommendation
to
create
a
ec2
instance.
Give
me
a
Playbook
which
can
automate
my
stuff
on
my
Cisco
router.
So
we
will
just
talk
to
a
friend
so
ensure
light.
Speed
is
the
sidekick
for
un
civil
expert.
D
Now
now
one
of
the
things
which
we
are
always
in
need
of
a
sensible
experts,
but
sometimes
we
fall
short
of
these
Savvy
Minds
who
can
jot
down
intricate
playbooks,
so
ansible
light
speed
also
fills
out
that
space.
So
if
a
company
doesn't
have
good
and
simple
developers
or
they
are
not
able
to
find
smart
people
to
write
their
eligible
playbooks,
we
have
it
for
you
so
sensible
light
speed
can,
as
I
was
talking
about.
It
will
create
a
scaffolder
for
you.
D
It
will
create
a
skeleton
playbook
for
you
and
then
you
just
configure
it
whatever
you
want.
However,
you
want
to
set
in,
depending
on
your
environment
now
mitesh
will
give,
will
give
the
brand
tour
demonstrating
how
tasks
even
a
complex
are
setting
up
a
cockpit
on
rel9
mode.
So
cockpit
is,
if
you
guys,
are
familiar
in
the
old
times
we
used
to
have
web
Webmail
to
manage
the
Linux
boxes.
So
cockpit
is
the
tool
which
is
a
browser-based
system,
admin
tool
which
can
help
you
to
manage
the
real
nodes.
D
So
message
will
show
how
he
will
write
a
ansible
Playbook
which
will
configure
cockpit
on
Rel
ninth
modes,
so
that's
something
which
he
will
be
showing
where
you
will
be
witnessing
that
into
the
action
now.
Two
of
these
cameras
is
showcasing
and
civil's
powers
and
versatility
fossil
your
seat
belt
for
a
blend
of
innovation,
precision
and
sheer
space
is
your
show
time.
D
C
In
the
devops
automation
example,
we
will
see
how
event
driven
ansible
helps
to
automate
resource
code
deployment.
As
soon
as
new
name
space
gets
created
in
openshift
cluster.
You
know:
infrastructure
marketing
example.
We
will
see
how
effectively
events
will
can
take
an
action
like
creating
volume
snapshot
as
soon
as
new
persistent
volume
gets
created
and
in
India
security,
orchestration
example,
we
will
see
how
quickly
even
driven
ansible
patches
the
non-ssl
routes
with
the
SSL
certificate
to
implement
these
secure
communication.
C
So,
let's
understand
Rule
books,
which
we
have
already
discussed.
Let
me
explain:
okay,
so
in
the
event
driven
ansible,
we
create
Rule
books,
which
tells
the
system
which
events
to
flag
and
how
to
respond
to
the
event.
We
write
Rule
books
in
yaml,
and
it
looks
traditionally
like
ansible
playbooks,
which
makes
it
easier
to
understand
to
build
the
rule
books
for
our
needs.
C
A
rule
book
is
comprised
with
the
three
main
components:
sources,
rules
and
the
action,
so
sources
sources
defines
which
event
Source
we
will
use
these
sources
are
available
as
a
plugins.
In
our
example,
we
are
using
Eda
k8s,
which
is
meant
to
read
openshift
cluster
events
by
adding
a
kind
parameter.
We
are
making
the
source
more
specific
and
limited
to
name
spaces.
There
are
some
other
plugins
which
are
already
included
like
web
hooks,
Kafka
alert
manager,
Etc
that
can
be
used
in
place
of
Eda.
According
to
our
requirement
rules.
C
C
Now.
Look
at
the
action
action
triggers
what
we
need
to
perform
if
condition
is
met.
In
our
example,
action
triggers
the
job
template
which
will
be
setting
up
the
resource
code
on
newly
created
namespace
rulebooks
also
have
some
other
actions
in
place
of
run.
Job
templates
we
can
use
like
a
run,
Playbook
run,
module,
set,
packs
event,
debug
Etc.
C
Let's
see
how?
How
do
we
configure
these
Rule
books
in
event,
driven
controller
in
so
there's?
This
is
a
web
interface
for
even
turbulanceable
controller,
so
we
create
a
decision.
Environment
decision
environment
is
a
container
image
which
includes
all
of
the
necessary
dependencies
which
are
required
by
the
plugins,
and
they
then
we
we
create
a
project
that
project
can
be
from
any
Source
like
GitHub
or
maybe
anything
so
there,
where
we
keep
all
of
the
rule,
books
and
Rule
books.
C
C
If
automation
I
mean
Eda
controller
is
configured
cluster,
then
it
will
be
running
on
open
shift
or
maybe
if
it
is
going
on
individual
rail
machine,
so
it
will
be
creating
Parts
online
machines,
but
so
going
back
to
you,
the
vs
code
editor
here
so
here
you
can
see
like
if
we
get
a
new
name
space
created,
it
triggers
a
job
template
which
is
a
set
resource
code
on
language
space.
If.
B
C
So
it's
a
simple
playable,
which
we
write
all
the
time
for
doing
the
automation.
So
here
we
have
couple
of
variables
defined.
One
of
the
variable
which
is
online
number
six
called
NS,
have
the
value
set,
is
ansible,
underscore
idiot
or
even
dot
resource
dot,
beta
Dot.
So
this
masses,
this
variable,
is
coming
from
a
rule
book.
So
rule
book
has
a.
C
A
C
Exactly
so
further,
there
is
a
task
you
you
get
correct
module,
which
is
setting
up
the
resource
quota
on
the
name
space
which
rulebook
is
saying
to
set
on
right.
So
we
have
three
examples.
So
for
all
three
examples,
we
have
three
different
playbooks
like
here.
We
have
already
configured
these
three
playbooks
on
automation,
controller
in
a
template
which
you
can
see
here,
set
resource
code,
Tower,
enable
space
password
which
third
and
the
create
volume
snapshot
right.
So
these
these
playbooks
are
already
configured
as
in
as
a
job
template.
C
C
C
Damage
space,
so
I
have
already
created
a
object
file
which
you
can
see
yeah.
So
it's
a
milliable
format
and
it's
creating
simply
a
rocket
chat
name
space
in
the
openshift
cluster,
so
to
create
that
one
I'll
simply
run
OC,
create
command
NSF
and
what
so,
what
it
is
going
to
do.
It
is
going
to
create
a
namespace
the
moment
name.
Space
will
be
created
automatically.
You
know
our
source
will
pick
the
event
and
that
will
trigger
a
job,
but
you
can
see
here
so
a
job
got
triggered
from
ansible
automation,
controller.
C
D
C
Because
this
is
really
nice,
one
yeah
I
forward
to
show
like
if
you,
if
you
really
wanted
to
see
that
what
are
the
logs,
what
are
the
events
got
triggered
and
got
captured?
We
can
literally
click
on
one
of
the
Rule
books
activation,
so
it
shows
if
you
go
to
the
history,
it
shows
that
this
is
the
thing
which
got
triggered
and
have
all
the
logs
here
available.
D
B
C
C
B
C
A
Right
and
you
think
about
the
times
you
like
I,
mean
I,
was
building
up,
I,
think
front
door
in
front
of
a
bunch
of
openshift
things
and
I,
always
yeah
I
had
forgotten
it
or
whatever,
and
it
was
just
a
hassle
because
I
was
being
repetitive
and
just
for
a
demo.
But
the
point
is
yeah,
the
the
I
forgot,
I
forgot
and,
and
it
needed
to
be
there,
it
was
sloppy
what
I
did
and
nothing
worked
and
I
was
confused
for
10
minutes.
So
this
is
great
yeah.
C
C
C
C
C
B
A
B
C
Right
this
everywhere,
yeah
yeah,
so
guys.
We
know
the
principle
like
you
speak
with
I
even
bought
some
Watson
code
assistant
is
available.
We
are
the
ansible
visible
Studio
code
extension
and,
if
I
show
I
have
my
visual
studio
code,
open
and
extension
is
installed
by
the
way.
Installation
extension
is
not
enough.
So
upon
the
installation
of
extension,
we
will
get
this
icon,
so
you
just
need
to
click
the
icon
and
connect.
So
when
you
click
on
again.
C
Open
a
browser
and
there
you
need
to
go
through
the
authentication,
so
you
as
a
play,
request
the
prerequisite.
You
should
have
GitHub
account
with
you,
so
I've
I
have
already
gone
through
the
process,
so
you
I
mean
here
you
can
see,
you
can
choose
November,
so
I
have
already
my
environment
capacity.
So
once
you
will
get
through
that
process,
you
will
have
this
icon
as
a
logged
in
so
yep.
C
And
what
you
see
here,
you
see
like
a
Playbook
with
a
couple
of
lines
commented
lines
like
just
for
a
demo.
I
commented
three
lines
so
here
what
I
have
to
do
is
uncomment
these
class
description
and
ask
and
split
speed
for
an
AI
Solution.
That's
it
it's
very
simple
as
passing
enter
and
tab
to
accept.
So
let
me
show
you
here.
A
C
Yeah,
so
one
more
thing:
we
need
to
pay
attention
here
like
after
enabling,
if
you
are
writing
a
Playbook,
you
need
to
make
sure
that
it
shows
at
the
bottom.
It
should
show
a
simple
light
speed
here.
If
it
doesn't
show,
then
you
will
not
have
a
what
some
segmentation
available.
So
here
I
just
uncommented
this
line,
and
you
know
if
you
are
doing
it
as
a
beginner
so
or
maybe
as
a
as
a
first
Playbook.
So
you
will
need
to
write
name
and
the
description
of
what
you
wanted
here.
C
A
C
Through
yeah,
so
let
me
hit
enter
here.
Take
another
situation.
Recommendation
here
is
knows
that
these
are
the
location
which
may
have
the
file,
if
you
do
it
or
if
we
have
a
file
here
for
a
cockpit,
so
recommendation
engine
or
light
speed,
reads
the
the
content
from
the
file
to
provide
the
solution
and
the
recommendation.
A
This
becomes
a
great
learning
tool
as
well,
because
rather
than
get
lost
in
syntax
and
stuff
like
that,
you
can
really
get
the
basic
stuff
down,
and
then
you
start
going.
Oh
I
I
could
do
so
much
more
with
ansible
and
there'll.
Be
rules
that
don't
write
out
a
properly
right,
I'm
sure
I
think
you
can
submit
a
fix
or
of
course
you
can
edit,
you
don't
have
to
accept
it.
You
know
it's
your
code,
but
it
really
teaches
you
a
best
practice
and
then
to
to
be
a
good
coder
yourself.
A
C
At
least
it
will
make
it
better.
So,
in
the
last
example,
I
just
asked
allow
cockpit
through
firewall,
so
I'll
simply
hit
enter
and
I'll
have
the
recommendation,
but
we
know
like
we
may
use
some
of
the
things
like
predefined
or
default
parameters.
We
can
directly
enable
in
the
Playbook,
so
I'll
just
enable
this
part,
which
has
a
defaulting
parameters
for
a
firewall
D
module
right.
So
if
I
go
back
and
delete
this
Edition,
so
here
you
can
see
we
have
a
permanent.
C
A
true
at
the
moment
now,
just
to
make
sure
recommendation
reads
the
content
to
before
it
gives
the
recommendation.
If
I
hit
enter
again,
you
can
see
the
documentation
is
bit
different,
so
it
doesn't
include
the
permanent
equal
to
option
because,
as
for
the
context
it
has,
it
sees
that
it
is
already
enabled
as
a
default.
So
it
is.
A
D
C
C
That
it
is
really
cool.
It
spent
a
lot
of
time
like
sometimes
when
I
do
write,
write
a
tasks.
Obviously,
I
need
to
visit
the
documentation,
so
it
is
saving
a
lot
of
time.
I
don't
need
it
if
I
need
to
tweak
it
I'll
just
take
and
use
my
use,
my
parameter,
so
maybe
something
else
yeah
and
then
I'll
have
to
ask
in
just
few
seconds
yeah
right.
So
that's
all
about
this
demo.
What
do.
D
A
Now,
and
then
you
know
again
the
sysadmin
of
me
20
years
ago,
I
mean
five
years
ago
when
I
was
young
was
was
very,
would
have
loved
this
right.
It
would
have
loved
the
opportunity
so
to
to
those
who
are
new
to
the
profession,
and
such
this
is
a
great
place
to
to
be
at
the
Forefront
of
it
and
to
shape
the
future
of
what
they
do.
Yeah
I
love
that
Yeah
Yeah
well,
yeah,
terrific.
This
is
terrific.
A
It's
been
nice
for
me
kind
of
going
down
memory
lane
thinking
about
about
that
world,
as
it
was
before.
As
I
was
thinking
about
the
show
and
and
just
how
advanced
this
has
become,
I
don't
have
much
more.
What
I
do
like
to
do
is,
if
you
have
any
final
words,
Richard
I,
don't
know
if
you
wanted
to
to
sum
up
everything,
but
we've
covered
it
nicely,
but
please
do
I.
B
B
A
Yeah,
so
what
we'll
do
is
we'll
update
the
description
we'll
place,
a
link
to
the
deck
as
well.
I
can
grab
a
deck
from
you
and
place
that
and
I'll
do
that
all
this
evening,
and
then
people
can
review
the
session
they
can
watch
us
in.
In
fact,
we
talk
really
fast
and
that
can
always
be
fun,
but
yeah
look.
Thank
you
so
much
for
the
demo
prakar
thanks
for
bringing
it
all
together.
I
hope
to
do
many
more
of
these
with
you,
probably
I,
don't
know
you
and
mitesh.
D
A
Join
us
join
us
for
sure
all
right.
Well,
thank
you.
Everyone
for
joining
us
for
the
copy
hour.
Yet
again,
I
do
want
to
point
out
that
red
hat
Summit
connect
is
going
on
right
now
we
just
had
our
event
in
Sydney
and
Richard
was
presenting
there,
so
that
was
wonderful
to
see
but
head
to
this
URL
and
check
it
out
and
then,
of
course,
for
future
streaming,
we
got
all
kinds
of
cool
shows
happening
on
the
red
hat
calendar
and
the
live
streaming
so
definitely
check
those
things
out
with
that.