►
From YouTube: Buenos Aires 2019 | Customer Keynote: OpenShift @ ExxonMobil | OpenShift Commons Gathering
Description
Customer Keynote: ExxonMobil
Buenos Aires 2019 OpenShift Commons Gathering
Mauro Aragunde (ExxonMobil)
Ezequiel Campos (ExxonMobil)
Lucas Paglia (ExxonMobil)
Sebastian Madrazo (ExxonMobil)
Andrew Block (Red Hat)
A
A
B
B
Before
really
starting
with
the
topic
that
we
have
come
to
present,
I
wanted
to
tell
you
a
little
about
the
company
with
you,,
although
it
is
not
very
open
to
the
public,.
Many
do
not
know
what
you
do,
exxonmobil,.
The
number
1
largest
oil
company
in
the
private
sector,
is
also
in
the
area
of
petrochemical
oenology,.
B
We
have
a
presence
throughout
the
world,.
We
are
not
just
offices
or
refineries,
franchises,
service
stations.
Platforms
in
the
elderly
are
sites
of
various
types.
What
has,
like
all
these
types,
is
that
they
require
connectivity.
Services
is
essential
and
there
are
also
their
applications.
We
in
total
around
the
world
are
more
than
61,000
employees,
particularly
in
buenos
aires
that
we
have
around
1000
these.
B
That
the
mobile
service
situation
of
the
rubricants,
we
continue
to
support
all
this
infrastructure.
We
have
around
30
thousand
devices.
These
are
network
equipment
and
servers,
mainly
the
problem
with
this
is
that
being
so
big,
it
will
be
constant.
Instead,
the
issue
of
scalability
and
maintenance
of
our
entire
corporate
network
of
third-party
services,.
B
Which
forced
us,,
let's
say,,
to
look
for
automation,
a
solution
to
all
this
problem,?
It
was
already
getting
out
of
hand,.
This
is
a
huge
number
of
devices
and
with
the
number
we
are
in,
all
these
sites
is
already
being
difficult
to
manage.
Everything
currently
continues.
Many
of
the
operations
that
are
done
are
manual.
B
B
B
We
did
simple
operations
that
would
launch
the
team,,
configure
everything
by
hand
or
manual,.
There
were
perhaps
good
practices
or
prepared
things
that
were
spreadsheets,.
There
were
few
applications
or
scripts
that
were
isolated,.
They
were
the
owners.
same
duplicate
teams
and
things
like
that,
and
if
there
was
a
small
application,
they
were
inside
virtual
machines,
which
was
also
not
within
our
scope.
Many
massive
areas
of
knowledge,
let's
say,
and
it
should
be
noted-
that
there
was
no
knowledge
of
ibero
for
developer
life
within
the
teams.
B
They
were
all
engineers
specialized,
in
particular,
serial
infrastructure,,
be
it
security
in
the
workplace
and
others.
The.
First
change
that
arises
from
the
game,.
This
is
the
year
2017
with
the
introduction
of
docker,.
It
is
when
the
containers
first
reached
our
company,,
which
facilitated
this,
so
was
the
process
that
we
had
to
get
access
to
cost
solutions
or,,
as
in
this
case,,
the
good
ones,
and
it
facilitates
a
little
more
than
this,.
I
am
not
saying
much
more
flexibility
for
us
to
start
creating
at
that
time,.
B
I
did
not
mention,
but
I
did
not
have
much
knowledge
in
containers
at
that
time,
and
what
I
went
up
to
solve
was
A
lot
of
that
work,.
The
issue
of
maintenance
of
the
life
cycle
and
the
contents
made
it
very
difficult
to
explain
it
to
them,
for
example,
a
network
engineer
how
he
had
to
set
up
the
known
container,,
something
totally
new
for
them,,
added
to
the
fact
that
he
had
to
develop
applications
for
that,.
So
it
made
it
much
easier
for
us.
B
B
Collaboration
was
complicated
because
I
believed
it
was
growing
at
different
steps
in
all
the
teams,
and
also
because
of
the
location
as
we
are.
Distributed
all
over
the
world,.
The
subject
of
collaboration
was
also
complicated,.
This
had
a
lot
of
reuse.
Let's
say
the
good
thing
about
transposed
was
the
creation
of
many
applications
for
this
time,.
B
Let's
say
more
common
in
infrastructure
teams
to
see
people
with
a
developer
ball,.
So
that's
how
it
was..
Many
applications
began
to
appear,,
but
many
compared
to
the
one
I
had
before,,
but
that
connector
was
still
missing.
It's,
like
it
automates
certain
operational
tasks
in
a
more
formal
and
professional
way,,
but
the
entire
process
that
actually
performs
was
not
chained.,
Let's
go,.
So
there
will
continue
to
be
tasks.
manuals,
and
this
also
changed
a
lot
when
we
introduced
sanctions
such
as
frei
with
automation,
among
others,
that
we
use
all
the
teams
we
had.
B
B
There
are
funds
to
start
consolidating
teams
that
were
closest
to
a
culture
of
ops.
Although
there
are
100
the
box,
there
is
already
an
infrastructure
that
understands
what
to
do,
or
at
least
how
to
consume
those
services,
how
to
try
to
translate
its
infrastructure,
its
definition
into
code
by
executing
it
I,
am
getting
an
idea,
for
example,
is
an
author
who
finished
off
Reuters
the
definition
of
the
entire
configuration
team
and
others
that
Mauro
now
we
will
give
more
details,
but
to
give
it
an
idea
of
the
work
we
do.
B
Now,
what
the
guys
are
going
to
present
Mauro
from
the
networks
and
place
of
error
are
two
cases
of
real
uses
to
each
buenos
aires
the
case
of
manolo.
We
are
docked
at
the
final
stage
and
where
several
teams
are
integrated
to
carry
out
a
common
task
to
provide
real
customer
service,
and
it
is
not
just
a
team
employee.
In
the
case
of
lucas,
it
is
The
way
they
present
their
services
to
their
clients
is
at
the
most
internal
level
of
the
group,,
but
perhaps
it
is
in
a
slightly
earlier
stage..
B
B
C
We
encountered.
o
Of
the
challenges
we
found
when
we
wanted
to
start
automating,.
It
was
a
bit
what
it
said
to
follow
the
difference
in
background
between
people
from
traditional
infrastructure
and
developers,
or
people
who
wanted
to
start
getting
a
little
more
involved
with
the
code
were
in
a
very
big
barrier
and
what
What
we
decided
to
do
to
facilitate
all
this
progress
and
also
consolidate
all
the
services
that
we
wanted
to
provide
was
to
develop
a
framework
that
allows
us
to
easily
start
automating,
simple
tasks
and
then
also
more
complicated,
tasks..
C
That
is
why
we
started
to
develop
this
framework
and
we
have
to
decide
with
what
application
or
what
part
of
this
entire
process
of
configuring
network
equipment
and
maintaining
the
network,
and
we
are
going
to
start
back.
Then
the
standard
configurations
of
network
equipment
were
stored
in
excel
with
many
companies.
Perhaps,
and
it
was
very
difficult
to
consume
those
configurations.
A
network
analyst
to
configure
a
team
had
to
find
excel
open
them
fill
in
certain
variables,
depending
on
the
team
copy.
All
that
and
paste
it
into
the
team
has
a
copy-paste
which
was
very
cumbersome.
C
It
could
cause
many
problems
and
it
was
not
optimal.
That
is
why
we
developed
what
What
would
be
the
first
application
that
we
call
standard
configuration
is
that
it
is
basically
an
IP
and
that
taking
advantage
of
certain
information,
such
as
the
hosting
of
the
device,,
the
operating
system,,
the
version,
etc.,.
It
returns
the
standard
configuration
for
that
device,
and
this
also
allowed
the
collaboration
of
the
teams
of
the
infrastructure
network,,
since
they
will
be
in
charge
of
writing
the
standard
configurations,.
If
what
we
developed
was
mostly
the
application
itself
that
did
this
interaction,.
C
With
this
we
got
many
advantages,.
First,
we
started
to
version
the
configurations
in
git,,
which
was
very
easy
to
determine
what
changes
were
made,
who
made
them
much
easier
than
in
an
excel
after
there
was
what
I
call
single
sors
of
truth
of
the
standard
configurations
and
also
we
reduced
time
and
errors,
and
we
allowed
a
very
important
factor.
The
integration
with
other
applications
associated
with
this
one
The
application
could
be
built
by
other
applications
such
as
dancing
all
or
a
user,
since
it
also
had
a
front
end,
but
well
after
this.
C
What
we
finally
wanted
to
do
was
start
putting
these
configurations
on
the
network
equipment
automatically,
and
we
realized
that
this
was
going
to
to
cause
certain
changes
in
the
network
and
it
could
be
such
errors.
There
could
be
problems
and
we
decided
to
start
with
another
continue
with
another
application.
That
was
to
verify
that,
after
a
change,
the
equipment
continues
to
work
correctly.
That
is
why
we
built
our
next
tool.
We
are
change
testing
based
on
in
jenkins.
C
What
it
basically
does
is
take
a
snapshot
or
photo
of
the
device
before
making
a
change,
then
the
change
is
made
either
automatically
or
manually,
and
then
another
snapshot
is
taken
of
the
post
state.
With
this
it
runs
on
a
set
of
tests
and
it
is
verified
if
the
state
of
the
device
is
correct,
it
is
the
desired
one
or
not.
If
it
is
not
the
desired,
one
can
quickly
revert
the
configuration.
C
This
was
the
first
tool
that
we
noticed
that
there
was
a
lot
of
collaboration
between
the
infrastructure,
team
and
automation,
teams
that
have
more
degree
more
from
developers,
since
we
also
developed
the
tool
itself,
but
all
the
tests
were
developed
by
network
experts
since
they
knew
what
to
test,
and
it
allows
them
to
extend
these
tests
whenever
they
want.
Without
going
through
the
automation
team,
In
itself,,
then
it
was
a
very
important
tool
and
well,.
In
parallel.
C
We
were
building
what
was
the
tool
to
automate
these
configuration
diplomas
that,
after
some
research,
we
decided
to
go
for
eagerness
since
it
had
many
network
modules
and
was
widely
used
in
the
industry.
For
the
network
area,
we
started
to
create
certain
scripts
in
anzio
to
check
equipment,
configurations,,
remedy,
equipment,,
etc.,
and
we
realized
that
to
scale
we
needed
to
run
these
scripts.
On
a
platform
we
decided
to
start
with
double
x
as
a
quick
start
for
those
who
don't
know
it's
a
front.
End
is
a
platform
to
execute
action.
C
C
Now.
We
are
in
a
period
in
which
many
of
the
network
analysts
collaborate
and
also
put
new
features
in
this
framework,
of
which
the
automation
team
is,
and
the
development
team
was.
a
big
change
good
and
all
this
is
deployed
in
openshift.
This
allowed
us
to
scale
much
more
easily.
We
went
through
the
stadiums
that
ezequiel
said.
The
conference
standard
was
first
in
a
docker
container
in
a
virtual
machine.
C
The
plan
for
new
versions
was
a
pretty
big
and
good
change
to
finish.
I
wanted
to
share
very
briefly
two
cases
that
we
are
and
about
which
we
carry
out
on
the
automation
framework.
One
is
the
automatic
remediation
of
network
equipment.
Basically,
what
this
does
is
that,
from
time
to
time,
all
the
network
equipment
has
been
scanned,.
C
D
Good
on
the
server
side
in
many
of
the
30,000
devices
that
ezequiel
mentioned
are
obviously
servers
and
the
usual
requests
that
we
have
are
obviously
the
registration
and
deregistration
of
servers
and
the
control
of
access
to
them,.
What
we
realized
was
that
the
way
our
clients
had
to
carry
out
those
orders
was
by
directly
contacting
members
of
our
team
through
a
generic
ticket
system
where
the
user,
in
this
case,,
our
client
had
to
type
by
hand
what
he
needed
and
in
a
non-standard
way
that
arrived,.
D
What
resulted
was
that
there
was
usually
incomplete
information,
because
the
user
did
not
know
the
data
that
had
to
be
entered
or
forgot
to
put
something
or
They
were
in
disarray
and
also
the
standard
format
which
did
not
allow
for
later
automation.
Of
carrying
out
that
order,,
we
had
to
see
all
the
orders
by
hand,
see
what
information
was
there,.
D
You
will
be
able
to
automate
the
rest
of
the
process,
that
is,
a
client
from
now
on
and
will
be
able
to
enter
a
web
form,
fill
in
all
the
data,.
If
you
did
not
have
all
the
data,,
you
cannot
complete
the
form,
once
the
data
is
completed,,
send
us
the
request,
and
instead
of
giving
it
manually,
we
could
send
that
to
a
computerized
script
that
processed
the
access
controls.
Finally,
what
we
would
do
was
a
database
to
keep
statistics
to
see
how
this
helps
us
improve
response
time,
how
many
requests
accepted,?
D
D
It
was
like,
well,
you
had
to
somehow
install
all
the
packages
again
and
Something
was
always
missing
and
the
worst
thing
we
thought
was
what
would
happen
if
one
day
we
have
this
in
production
and
we
have
to
find
a
way
to
replicate
the
production
environment.
How
long
would
it
take
the
time
it
took
to
generate
the
environment
again
made
us
think
of
alternatives
such
as
containers,,
so
the
first
thing
we
started
was
to
move
everything
to
play.
What.
D
There
were
generally
new
ones
and
obviously
to
be
able
to
generate
production
minds
when
we
want
and
in
the
way
we
want,
we
finally
switched
to
openshift,
because
in
a
world
of
box,
we
only
needed
things
that,
when
carlos,
we
had,,
for
example,
the
fact
of
being
able
to
scale
to
many
environments
of
having
high
availability,
and
since
we
were
working
mainly
with
web
forms.
We
needed
security
in
the
web
pages
and
eloquent,
for
example,
adding
ssl
security
as
easy,
like
ticking
a
Czech
and
in
the
blink
of
an
eye.
D
Again
we
had
a
lot
of
tools
that
we
did
n't
have
in
a
separate
container
acade.
We
had
an
orchestration
tool
and
all
those
features
that
I
mentioned
before
all
this
code,
a
practice
that
we
began
to
take
into
account
It
was
using
version
control,,
but
in
addition
to
using
version
control
that
allowed
us
to
work
collaboratively
with
all
previous
versions
of
our
code,
in
case
something
bad
happened,
and
we
had
to
open
a
previous
version,.
We
implemented
a
model
of
what
the
repository
branches
would
be.
D
so
that
we
can
separate
what
was
production
from
what
was
development
so
that
it
does
not
overlap
and
also
thinking
about
this
transition
to
the
box
that
when
a
member
of
the
work
team
opens,
we
can
work
on
two
functionalities
at
the
same
time,
without
stepping
on
each
other,
afterwards
being
able
to
work
everything
together
and
what
gave
us
version.
Control
was
that,,
whatever
we
were
already
working
on.
Other
initiatives,,
such
as
they
have
been,,
but
we
added,
for
example,
branch.
Modeling
is
for
this
project.
D
So
all
those
services
at
this
time
also
had
to
interact
with
our
legacy
ticket
systems
and
everything
that
was
working
as
before,
with
which
there
we
have
a
communication
between
the
gas
ticket
system,
and
that
should
also
send
the
data
to
what
would
be
another
payton
micro
service
of
that
block
is
up
there.
That
is
in
charge
of
collecting
the
data.
D
We
are
starting
to
use
relational
databases
and
data
visualization
models
that
consume
the
data,
that
is
in
the
visualization
in
the
relational
database,
in
a
very
visual
and
easy
way
to
access
all
the
data
and
see
how
it
is
progressing
over
time
and
how?
What
we
are
doing
is
reducing
the
response
time.
We
have
the
users.
B
B
B
As
I
was
saying
before,,
we
are
infrastructure
people,.
We
work
with
people
who
are
very
focused
on
that
and
perhaps
differently,
it
revealed
for
the
applications
whose
work
or
use
this
only
for
the
host
and
to
see
their
applications
and
also
our
work
does
not
end
once
the
application
is
created.
But,
along
with
that,
we
but
test
the
service
to
automate
all
the
infrastructure
and
have
the
service
available
and
make
the
aggression
really
the
knowledge
of
distributing
the
knowledge
among
a
lot
of
networks
and
developers,
and
even
people
from
servers,.
B
It
is
a
mixture
that
center
of
the
three
to
generate
all
this
is
very
difficult
on
a
verbal
scale
also,
as
I
said
before,
to
share
all
this
and
avoid
generating
more
effort
all
creating
what
same
time
and
again,
we
are
still
in
that
process.
We
are
still
talking
about
many
teams
that
reach
the
last
stage
that
I
mentioned,
and
several
that
are
already
integrating
new
technologies,
such
as
cloud
and
others
thinking
or
designing,
with
their
artificial
trade
winds,
and
also
everything
for
the
infrastructure.