►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Matt
Davis,
Red,
Hat
solution,
architect
and
with
me,
is
Bubba
Puryear,
an
IT
fellow
at
Syngenta
and
J
Huddleston
Senior
Red
Hat
consultant.
So
Syngenta
is
one
of
those
DevOps
unicorns
that
you
read
about
when
they
were
implementing
DevOps
they
started
by
building
out
their
DevOps
culture.
Then
they
laid
down
their
processes
and
after
all
of
that
was
done,
they
selected
the
right
tools
for
the
job.
They
chose
open
ship
dedicated
as
the
platform
for
running
their
containerized
workloads.
The
journey
from
legacy
was
challenging.
They
were
trapped
on
proprietary
platforms
in
a
managed
data
center.
A
They
had
very
little
access
to
the
platform.
The
configuration
the
logs
very
little
knowledge
as
to
the
application
behaviors,
but
his
team
was
able
to
containerize
those
workloads
and
lift
and
shift
on
to
open
shift,
and
then
they
reacted.
These
applications
breaking
them
down
into
micro
services.
So
with
DevOps,
tooling
and
containerization,
they
were
able
to
realize
the
benefits
that
we
commonly
talked
about,
such
as
shorter
application,
delivery
times
better
value
back
to
the
business.
A
But
today
we're
going
to
focus
on
some
of
the
lesser
discussed
operational
benefits
such
as
making
it
easier
to
manage
and
debug
applications
specifically
he's
going
to
talk
about
and
tell
the
story
of
a
nasty
N+
1
query
ish
in
production
and
how
they
were
able
to
discover
debug
fix
test
patch,
a
live,
critical
production
application
all
inside
of
three
days
with
no
application
downtime.
So.
B
So
we
we
sell
the
tools
to
farmers.
They
can
bring
planned
potential
to
life,
so
big
farmers,
small
farmers,
organic
conventional.
It
doesn't
matter.
We
we
sell
them.
These
tools,
also
seeds
and
chemistry,
so
to
maximize
the
benefit
of
their
plants
to
the
farmer
and
also
to
bring
that
potential
to
you
and
I.
So
I,
don't
know
about
you,
but
I
am
looking
forward
to
dinner
in
this
foodie
town
and
I'm
gonna.
Thank
a
farmer
when
I
get
home
for
we're
providing
it.
B
So
there
are
customers
and
kind
of
why
Syngenta's
mission,
really
matters
really
hit
home
to
me
and
I
watched
Neil
Halloran's
the
fallen
of
world
war,
two
interactive
video
online.
So
it's
a
very
somber
video
and
I
highly
commit
it
to
you.
Really
I
do
and
I'm
a
positive
person
really,
and
it
ends
with
this.
B
So,
in
a
sense
you
know,
Syngenta's
mission
is
early
to
make
sure
that
your
kids
and
mine
don't
have
to
go
to
war
over
who
gets
to
eat
dinner,
which
is
an
awesome
mission.
So
my
job
at
Syngenta
I'm,
primarily
a
technology
evangelist
these
days,
I'm
supposed
to
be
an
architect
and
for
the
last
four
years,
I've
been
an
architect
on
an
internal
transformation
program
that
is
delivering
a
set
of
tools
to
implement
like
ancestry.com
for
plants
since
our
seeds,
business.
B
B
About
two
years
ago
we
got
tapped
and
said:
hey
like
everybody
else
in
Syngenta,
you
need
to
pick
your
load
up
out
of
the
datacenter
and
get
it
to
cloud
and
by
the
way,
you
not
given
any
additional
time
for
your
regular
work
and
you're
not
going
to
get
any
additional
funding
to
do
it.
So
you
know
fearless
leader,
looked
at
me
and
said:
hey
you're,
the
architect
on
the
program.
B
B
So
I
did
what
any
good
architect
would
do
and
I
got
on
YouTube
and
did
a
lot
of
blogs
and
yeah
I
see
some
nods,
so
thank
you,
Dave
Han
and
first
Sutter
and
Kelsey
Hightower
and
Matt
Stein
and
all
the
others
and
I
kind
of
put
together
this
theory
and
I
kind
of
conned
our
graphics
artist
into
putting
this
propaganda
where,
together
to
say,
hey.
This
is
what
winners
are
doing
on
cloud.
So
I
went
looking
for.
How
do
I
do
cloud
and
I
kept
running
into
micro
services,
DevOps
and
containers?
B
And
yes,
I
did
still
Joe's
quote
there
from
the
Forbes
article
and
didn't
ask
him
for
the
likeness
I
hope
you
like
it
and
I
took
this
to
DevOps
days
Raleigh,
which
was
the
first
one
in
2016
and
I,
asked
everybody
I
could.
Is
this
true
I've
drank
the
kool-aid
pretty
hard,
but
I've
got
zero
experience
with
this
and
I
kept
running
into
these
all
these
people
from
this
team
on
this
product
called
openshift
and
they
said
yeah.
B
We
believe
this,
and
not
only
that
we
have
a
platform
for
you
and,
of
course,
that
platform
is
OpenShift
and
so
I
go
back
to
work.
The
next
day
and
I'm
like
I,
go
into
the
boss's
office
and
say
hey
chai,
I
found
this
thing
called
openshift
I
think
we
should
do
it.
It
should
really
leapfrog
us
on
our
innovation
journey
and
I
started
going
into
the
wholesale
spiel
about
how
dedicated
you
know.
Red
Hat
will
take
care
of
all
the
hardware
and
the
software
stack.
Would
you
have
to
put
our
load
on
it?
B
B
So
all
that's
remained
on
task
and
in
flight
and
in
parallel
we
brought
in
additional
technology
and
help
from
Red
Hat
to
kind
of
bootstrap
us
on
this
journey,
and
it
went
really
well,
and
so
we
decided
we
want
to
do
real
infrastructure.
So
it's
one
thing
to
demonstrate
that
you
can
take
your
internal
line
of
business
application.
That's
you
know,
got
internal
phen,
occation
authorization
and
push
it
out
on
the
internet
and
make
sure
it
works
with
your
data.
That's
secured
internally!
It's
another
thing
to
do
that
in
a
repeatable
scalable
way.
B
B
That's
when
all
the
data
is
coming
in
and
material
and
everyone's
busy,
so
kind
of
our
Black
Friday
and
as
our
in
our
company
is
when
the
northern
hemisphere,
which
is
where
most
of
land
mass
on
the
earth
exists,
is
in
harvest.
So
between
the
middle
of
August
in
the
middle
of
October.
It's
not
a
good
time
to
be
messing
with
things.
That's
in
that's
a
good
time
and
that's
right
when
we
did
did
this
and
went
off
without
hitch,
it
was
great.
B
It's
like
mobile
application
development,
and
just
today
we
enable
bring-your-own-device
so
for
our
internal
line
of
business
tool.
That's
designed
for
Internet
Explorer
on
this
ingenta
Windows
laptop.
Now
our
users
can
use
on
iPads
and
whatever,
which
is
really
cool
and
useful.
It's
not
just
cool
it's
useful,
so
I
mean
it
be
clear,
so
we
spent
quite
a
bit
of
money
last
year
on
open
shift
and
professional
services
engagement,
but
the
speed
and
the
resolution
that
we're
able
to
get
has
really
paid
for
itself.
B
So
this
is
we're
really
really
excited
about
technology
platform
and
when
the
culture
changed
so
now,
I'm
gonna
talk
about
this
incident.
We
had
so
the
deal
was
we
had
a
service
that
took
a
list
of
things
and
then
for
each
thing
in
the
list
it
would
spawn
a
thread
inch
thread
to
go
grab
it.
You
know
a
good
database
connection
and
do
its
thing,
which
is
bad,
but
it's
not
so
bad.
If
nobody
ever
passes
a
lot
of
things
to
the
list
we
didn't
know.
This
was
the
problem.
B
Of
course,
all
we
knew
is
October
10th
of
20-17.
We
came
into
work
and
the
helpdesk
board
was
lit
up
like
a
Christmas
tree
with
people
saying
hey
that
system
we've
wasted
on
us.
It's
down,
it's
stuck,
it's
frozen,
I
can't
login
a
bunch
of
new
users.
You
know,
why
did
you
do
this
to
us?
It's
our
busy
season
it
and
so
openshift
really
helped
us
in
four
different
ways
managed
through
this
issue.
B
The
first
way
was
was
just
what
pods,
so
it
didn't
take
us
long
to
realize
that
not
everybody
was
complaining
about
the
system,
and
so
that
made
us
wonder
why
some
people
were
having
success
in
the
system
and
other
people
weren't.
Was
it
a
regional
thing
and
what
was
going
on
and
in
within
a
few
hours
we
figured
out
that
it
was
basically
one
pod
was
was
stuck,
and
so
you
know,
spending
up
more
pods
reduces
the
blast
radius
of
the
issue,
so
we
did
and
my
counterpart,
who
kind
of
runs
production
supports.
B
If
you
think
of
me,
as
like
the
guy
over
all
the
devs,
you
know
my
equivalent
on
the
ops
side
said:
hey
look.
That
pot
is
dead
and
users
can't
do
anything.
Isn't
this
platform
supposed
to
you
know
fix
things.
So
what
if
we
just
killed
that
pod
and
so
I
said?
Okay?
Well,
we've
never
done
that
before,
but
fine,
so
he
killed
the
pod
live
and
open
shifted.
B
What's
supposed
to
do
and
spun
up
a
new
pod
and
thanks
to
the
magic
of
session
persistence,
all
the
web
sessions
from
the
spun
down
pod
got
attached
to
the
new
one
and
for
most
users
the
experience
went
something
along
the
lines
of
you
know.
The
system
was
spinning
and
waiting
and
whatever-
and
it
came
up
with
some
goofy
error
message.
I,
don't
know
about
your
users
but
90%
of
mine.
In
that
case,
when
it
comes
back,
they
just
push
the
button
again
and
they
did
it
worked
because
it
was
a
healthy
pot.
B
B
So
the
next
thing
that
really
helped
was
all
the
integrated
logging
that
openshift
has,
and
this
this
actually
was
a
stumbling
block
for
us
at
first
and
actually
kind
of
how
Jake
came
to
us.
He
was
helping
us
out
a
number
of
things,
one
of
which
was
you
know,
with
distributed.
Pods
you
got
distributed,
logging
and
distributed.
Logging
is
painful,
so
our
logs,
initially
just
log4j
logging
straight
to
standard
out
or
whatever
we're
going
over
each
line
as
an
individual
entry
into
cabana.
B
So
it
was
not
very
useful
for
searching
so
Jay
helped
us
fix
our
stuff
up
so
that
you
know
individual
log
entries
are
going
over
HUL,
even
if
it
had
a
full
stack
trace
in
it.
So
that
allowed
us
to
very
quickly
that
that's
actually
what
helped
us
discover,
which
pods
that
we
had
a
problem
with
a
pod
and
which
pot
it
was
because
the
database
guys
are
basically
saying
hey.
This
connection
is
starved
and
then
we're
able
to
look
in
the
Cabana
logs
and
say
in
that
connections
associated
with
this
pod
ergo.
B
That's
the
pod
that
we
need
to
do
something
about
that.
Also,
of
course,
gave
our
teams
all
the
context
clues
necessary
to
get
started,
trying
to
debug
the
and
find
the
issue
which
is
tricky
because
the
symptom
was
a
bunch
of
people
saying
the
system
doesn't
work.
It
wasn't
a
lot
to
go
on.
So
the
next
way,
OpenShift
really
helped
was
having
sand
boxes
for
testing
fixes.
B
So
the
team
were
obviously
we're
trying
to
find
things
that
might
be
wrong,
looking
at
different
cases,
so
standing
up
sandbox
environments
and
we
eventually
figured
out
oh
hey
yeah,
who
wrote
that
code,
we
fixed
it
and
then
you
know.
Of
course
we
commit
the
change
and
then
we
tested
in
our
QA
environment.
So
it's
it's
awesome
being
able
to
have
sandboxes
and
QA
environments
that
are
exact
replicas
of
your
production
environment
and
having
infrastructures
code
on
top
of
a
canary
platform.
B
You
know
that's
not
hard,
and
you
know
there
really
is
no
excuse
for
not
having
it
once
you're
there,
so
that
was
really
awesome
and
then
really
cool
song
on
the
Thursday.
So
again,
you
know
Tuesday
morning
it
was
a
circus.
You
need
to
set
up
the
circus,
but
we
were
all
upset
that
this
issue
had
to
pull
the
warm
room
team
together
by
Thursday.
We've
got
the
fix.
We've
got
the
image,
alright,
we're
ready
to
push
it
out.
B
We
just
did
a
hot
deploy
and
you
know
on
the
live
system
and
the
bug
was
gone,
which
is
cool,
we'd,
never
done
before
open
shift,
we've
never
done
rolling,
deploys
and
hot
deploys.
So
we'd
always
have
to
broker
an
agreement
with
our
users.
One.
Can
we
get
it
outage
window
because
remember
it's
it's
Black
Friday
season,
so
we've
got
people
running
24
by
7,
ops
and
whatever.
So
we
can't
just
take
this
to
sometime
for
maintenance
whenever
we
feel
like
it.
B
So
not
being
able
to
keep
the
system
up
and
not
taking
it
down
was
a
huge
benefit.
So
I
mean
honestly
the
between
the
technology
platform
and
the
partnership
with
Red
Hat
I
mean
we
came
a
long
ways
in
less
than
a
year
and
now
Jason's
going
to
tell
us
a
little
bit
about
the
benefits
of
working
with
with
the
partnership,
with
consulting
so.
C
Bubba
story
really
shows
how
the
partnership,
with
read-out
consulting
shorten
Europe's
your
time
to
market
by
utilizing
our
consultants
of
experience
with
various
products.
We
can
also
reduce
the
learning
curve
by
through
our
training
programs
or
just
by
knowledge
transfer
by
working
with
our
consultants.
I
was
assigned
to
Syngenta
to
help
with
a
few
few
things
that
are
on
the
screen:
the
cross
cluster
promotion.
We
were
promoting
code
between
their
dev
and
their
proud
of
the
cluster.
Also,
the
logging
issue
that
Bubba
talked
about
earlier,
a
few
registry
and
user
issues
and
some
AWS
integrations.
C
B
So
very
very
true,
I
mean
so
hats
off
to
the
openshift
team.
I
mean
you
guys
have
put
an
awful
lot
in
the
box.
So
it's
it's
a
cool
product,
but
it's
also
an
awful
lot
to
really,
as
a
mat
says,
to
go
from
kind
of
101
to
senior
level
work
and
I
can't
commend
any
stronger.
You
know
get
help.
You
know
it's.
It's
tough
to
tackle
a
large
learning
curve
on
your
own,
with
your
own
team,
so
I
mean
since
since
then,
we've
really
kicked
up
the
innovation
level.
Honestly.
So
you
think
about
this.
B
We
had
an
internal
line
of
business
application
that
had
never
seen
the
light
of
the
Internet
right
so
internal
users.
Only
so
you
seem
it's
a
hardened
perimeter,
so
your
team
is
not
rigorously
focused
on
security
issues,
not
that
we're
sloppy.
But
it's
just
it's
not
it's
not
ever
done
in
anger
right
because
it's
internal,
we
took
that
and
lift
it
out
and
stuck
it
out
on
the
internet.
I've
got
a
diagram.
B
I'll
show
you
up
here
the
basic
connectivity,
so
the
databases
are
still
in
Syngenta's,
private
virtual
cloud,
so
we've
got
firewalls
and
all
that
in
place,
but
this
has
really
allowed
us
to
take
advantage
of
other
online
internet
facing
services.
So
maybe
a
picture
is
worth
a
thousand
words,
so
we've
got
to
we've,
got
to
open
shift
clusters
and,
of
course,
they're
sitting
out
on
the
big
bad
internet,
and
this
is
allowed
us
to
do
things
like
mobile
application.
Development,
which
you
know
mobile
apps,
are
easy
to
create
these
days.
B
It
would
be
a
lot
harder
to
do
just
in
our
in
our
virtual
private
cloud
with
no
internet
ingress.
So
you
know
our
databases
and
all
of
our
build
tooling
and
dev
support
tools
are
all
are
all
internal
and
you
know
our
application
code
is
hosted
externally
and
this
kind
of
it's
kind
of
how
we
set
it
up
and
how
we
do
it
so
like
to
say
a
huge
thank
you
to
Red
Hat
for
sponsoring
DevOps
days,
because
without
that
we
wouldn't
have
found
you
guys.
B
Thank
you
to
Red
Hat's
professional
services
and
consulting
for
helping
and
bootstrap
us
I
mean
honestly.
Our
team
has
come
a
long
ways
in
a
very
short
period
of
time
and
hats
off,
of
course,
the
openshift
team
for
such
a
fantastic
product
and
to
this
team
up
here
so
I'm,
largely
a
purveyor
of
powerpoints
and
diagrams.
So
these
these
are
the
folks
that
actually
made
it
real
and,
of
course,
to
our
leadership
for
having
the
inspiration.
I
mean
I,
can't
stress
enough.
B
If
you're
gonna
make
a
transformation
journey,
you've
got
to
have
leadership
skom,
it
meant
to
say,
hey,
innovate,
give
you
freedom
to
operate
and
to
go
after
things
so
appreciate
it.
And,
of
course
my
management,
for
you
know,
authorize
me
to
come
out
here
and
speak
to
you
today.
I
appreciate
that
as
well.
So
thank
you
for
Treece.