►
From YouTube: Buenos Aires 2019 | OpenShift @ Sulamerica - Kadu Barral (SulAmérica) | OpenShift Commons Gathering
Description
OpenShift @ Sulamerica
Kadu Barral (SulAmérica)
OpenShift Commons Gathering
Buenos Aires 2019
A
Hi,
are
you
listening
sorry
for
not
speaking
Spanish,
but
I
prefer
to
speak
in
English?
My
English
is
not
so
very
well,
but
it's
better
than
my
Spanish
and
I
will
talk
about
how
you're
using
opposite
tool
America
and
how
our
good
size
eg
plan
can
save
her
life
and
I
will
talk
about
how
we'd
apply
a
code
before
up
a
shift
and
the
verbs
and
after
OPA
shift
and
I
will
show
the
size
of
our
environment
and
our
most
used
development
stack.
A
But
first
I
would
like
to
introduce
myself
and
Salaam
Eric
I'm
a
software
engineer.
I
am
currently
leading
2
Chainz
actual
America.
One
is
restful
responsible
for
the
web
applications
infrastructure
and
another
one
is
responsible
for
monitoring
and
if
the
applications
are
running
well
on
Seoul
America
I
have
time
to
rent
you.
A
A
A
This
code
was
the
first
project
that
we
that
we
migrated
to
openshift.
They
usually
run
on
lagus
and
was
one
of
the
first
projects
that
we
immigrated
to
over
shift
to
gain
scalability
on
that
quotes
and
in
curry
shirts.
We
start
to
use
telematics
to
discover
the
driving
patterns
of
our
customers,
and
with
this
we
can
apply
the
scouts
for
good
drivers.
A
Auto
slides
with
information
of
Sioux
America
I
I
took
from
presentation
from
made
for
shareholders.
This
presentation
is
public
and
I.
Put
the
link
here.
It's
public
information
and
highlights
the
importance
of
IT
and
the
parties
of
technology
in
our
business.
Now
was
a
time
that
IT
was
just
a
cost
center.
Now
every
company's
a
tech
company.
A
So
we
are
a
120
years,
tech
company,
so
we
have
a
lot
of
things
to
do
from
a
frame
our
legacy
applications
running
basically
on
WebSphere,
and
now
we
are
in
our
journey
to
cloud
and
this
one
is
the
services
running
on
sole
America.
We
use
dynaTrace.
If
you
know
that
address
you
know
this
image
and
those
are
the
had
had
products
that
are
how
girls
in
in
this
journey,
especially
OpenShift,.
A
A
So,
first
we
have
to
discover
if
the
application
is
new
or
not,
and
if
the
application
already
exists.
We
just
enter
your
own
application
server
and
apply
the
code.
This
process
took
one
day
or
two
depends
if
you
are
busy
or
r2q,
but
if
the
application
is
new,
we
have
to
create
a
new
environment,
so
we
have
to
work
with
the
brutalization
change
for
a
new
vm.
A
We
have
to
work
with
Network
team
to
get
a
new
IP
operation
system
chain
do
the
whole
configuration,
and
after
that
we
can
install
the
application
server
and
after
a
few
years
we
can
release
the
coding
product
I'm
joking
about
the
years,
but
this
process
took
you
one.
Now.
This
first
took
two
weeks:
it's
a
lot
of
time
and
after
OpenShift
in
the
ROPS,
the
developer
finished
the
codes
and
they
commit
some
baggage
and
book.
She
automatically
starts
a
trigger
that
called
jenkins.
I,
like
Jenkins
Jenkins,
do
the
homework
check
out.
A
A
A
This
process
is
to
a
lot
of
metal
but
I
work
it
for
a
while
I
said
to
work
it
for
a
while,
because
our
results
of
open
shift
was
that
we
gained
a
lot
of
velocity,
and
now
we
don't
have
to
wait
until
2
a.m.
to
the
player
code
to
the
playing
production
because
of
a
shift.
You
have
running
the
plow
and
other
deployment
strategies,
so
we
can
deploy
in
productions
anytime.
A
We
are
delivering
fast
minimum
value.
Product
OpenShift
is
microsoft's
already,
but
we
also
have
a
lot
of
monolithic
is
running
there
and
what
I
think
that
was
the
most
important
thing
that
increased
the
environment
was
that
now
we
have
can
okay,
we
can
have
a
lot
of
environments
for
the
same
application.
A
A
A
A
A
A
A
So
this
is
our
sizing
now
now,
no
it's
three
weeks
ago,
probably
with
these
numbers
increased
a
lot.
We
have
almost
40
hundred
projects
and
more
than
33
thousand
ramblings
running
on
overshift,
you
use
three
masters.
Nonnie
routers.
This
is
to
VM
is
because
we
don't
need
big
machine
store
to
her
the
Masters
and
routers.
A
We
separate
our
environment
with
using
note
selectors,
so
the
same
masters,
control
production
and
no
production
environment.
We
separated
those
with
note
selector,
and
we
have
a
la
11
stage,
notes
mix
it
up
between
bare
metal
events,
and
we
have
2
infra
notes
that
run
in
logging,
matrixes
and
other
operational
apps
for
open
eaves,
and
we
started
to
use
of
a
shifted
3.3
and
now
we
are
on
the
latest
version
latest
3
version,
not
foreign,
yet
311.
A
As
I
said,
we
have
a
lot
of
legs
that
we
just
me
great
to
show
off
my
shift,
but
the
new
application
about
90%
of
the
new
application
runs
on
t
stack.
That
is
basically
java
spring
boot
running
under
town.
We
use
the
high
curry,
you
know,
is
a
connection
pool.
It's
very
fast
is
very
good.
The
hiker
is
CP
and
Sansa.
Gouda
is
a
Brazilian
company.
It's
a
password
vault
to
connect
to
to
database.
A
A
A
These
routers
sends
the
traffic
to
the
OB
shifter
routers,
that
I
said
the
trick
clusters
and,
after
that,
to
the
application
running
a
shift.
We
use
dynaTrace
for
application
monitoring.
It's
blank
is
more
for
security
analysis.
The
security
needs
a
lot
of
blank
primer
fields
for
OpenShift
2,
matrix
and
openshift
comes
with
logic,
search
and
Cubana
for
logging,
and
we
have
happy
gremlins
running
there.
A
This.
This
is
the
best
feature
that
cabinets
brings
to
to
to
to
guarantee
the
availability
of
the
application.
So
you
have
to
use
readiness,
aliveness
setup
required
requests
in
limits.
This
is
very
important
to
the
pod
finds
the
right
know,
which
two
feet
and
openshift
use
this
pupil
to
pad
out
scaling
to
a
tip
is:
do
some
load
tests
to
find
the
right
size
of
the
art
projects
and
parts
the
right
size
of
CPU
and
memory
to
configure
the
request
and
limits.
A
Not
know
D
resource
and
we
are
using
bare
metal-
and
this
is
very
important,
especially
if
you
are
using
bare
metal
just
to
reserve
some
resources,
just
systems
to
operational
system
and
to
cobranet
the
eviction
policies
is
important
to
bare
metal
can't
do
if
a
lot
of
pods
have
a
number.
Imagine
others,
and
it's
good
come
to
configure
the
max
number
of
pods
running
in
on
each
server
so
couple
arguments
these
are
friend,
you
use
it,
and
this
is
what
we
need
to
the
future.
A
It's
it's
not
fair
to
do
a
presentation
after
the
this
session
that
we
saw
now,
because
almost
that
we
want
the
opposite
for
will
the
virtuous,
but
we
want
to
go
much
clouds.
Our
environment
is
just
on
prams
running
on
bare
metal
and
we
want
to
gain
scalability
running
on
different
clouds
and
with
that
we
have
a
better
disaster
recover.
A
We
have
one
specific
one
specific
case
that
we
needed
to
do
some
cannery
releases
for
different
hospitals,
and
we
have
some
hospitals
that
some
features
starts
with
this
hospital
and
do
canary
canary
release
with
we
can.
We
can
do
kind
of
release
now
with
open
shipped,
but
just
for
percentage
or
amount
of
traffic
and
with
service
image
we
can
do
better,
can
release
for
just
for
one
location
just
for
one
stage.
One
city,
one
hospital
and
some
smash
will
help
us
with
traffic
management
and
security,
and
we
need
to
improve
our
our
infrastructure
as
code.
A
This
is
very
important.
We
do
a
lot
of
work
in
manually,
yet
we
still
reusable
and
we
do
a
lot
of
virtue,
but
have
room
to
improve
here,
especially
for
self-healing
the
infrastructure.
As
I
said
OpenShift,
you
have
the
readiness
aliveness
that
is
perfect
for
Suffolk
healing
of
the
application
of
the
pods.
But
if
a
machining
goes
down,
if
a
server
goes
down,
we
can
use
infrastructure
as
code
we
can
use
as
before
that
and
infrastructure,
as
good
help
for
faster
provide.