►
From YouTube: Buenos Aires 2019 | OpenShift @ Banco Hipotecario | Pedro Cabello Salazar (Banco Hipotecario)
Description
OpenShift @ Banco Hipotecario: : Transformacion Digital
Pedro Cabello Salazar (Banco Hipotecario)
Buenos Aires 2019
OpenShift Commons Gathering 2019
A
Well,,
first
of
all,,
good
afternoon,,
thank
you
for
being
with
us.
Thank,
you
very
much
to
pray
for
allowing
us
to
give
this
presentation.
I
see
that
many
people
are
still
accompanying
us,,
so
it's
good
that
they
stayed
because
we
hope
they
take
away
some
lessons
from
here
on
what
our
path
of
life
was.
adoption
of
the
platform.
A
A
The
mortgage
bank
has
granted
throughout
its
history
throughout
Of
the
133
years
of
history,,
approximately
1.8
million
mortgage
loans,.
We
are
more
than
1,800
employees.
Those
of
us
who
work
within
this
institution
are
a
highly
regulated
industry,
like
all
financial
entities,
and
since
2017
the
bank
has
been
investing
heavily
in
what
it
It
is.
Its
digital
transformation.
A
Serious
problems,
because
it
was
a
platform
that
had
been
established
for
some
time,,
approximately
more
than
10
years,
and
we
were
running
out
of
support.
Maintenance
was
becoming
a
little
more
complex,.
So
we
began
to
face
a
challenge
to
be
able
to
leverage
what
the
The
bank
was
undergoing
its
digital
transformation,.
What
was
asked
of
us
was
to
be
able
to
mitigate
the
risks
of
infrastructure
and
applications
due
to
the
obsolescence
of
our
application,,
our
integration
platform,.
It
was
not
only
that
we
had
this
problem,.
A
After
some
time
we
tried
to
upload
another
integration
platform
within
the
bank,,
which
was
not
a
good
success
either,.
So
the
business
asked
us
a
lot
for
this
in
order
to
have
greater
availability
of
our
channels.
The
architecture.
We
had
two
years
ago
was
somewhat
complex,
where
we
had,
as
several
of
the
presenters
here
monolithic
applications
that
sometimes
went
directly
to
the
download
without
going
through
our
integrations
layer.
So
what
we
had
to
do
was
take
advantage
of
the
resources
we
had
in
a
more
optimal
way.
A
We
were
asked
to
automate
to
gain
speed
and
try
to
adopt
tools,
innovative
and
collaborative
today
at
the
bank
we
have
connected
since
then.
Also
for
two
years,
we
have
connected
more
than
30
applications
that
use
our
integration
platform
that
went
through
our
old
layer
of
integrations,
which
was
a
product
that
was
gradually
being
used
disk
continuing
and
we
transit
around.
We
traffic
around
5
million
daily
operations
of
daily
transactions
for
two
years,
with
the
arrival
of
a
new
of
a
new
headquarters
to
the
systems
area
within
the
bank.
A
We
were
not
seeing
that
the
microservices
architecture
is
that
support
is
in
transforming
large
functionalities
into
small
applications,
each
one,
with
a
very
particular
solution,
objective,
to
solve
a
very
specific
problem
and
in
having
different
pieces
that
we
can
manage
and
orchestrate
in
such
a
way
that
we
can
solve
these
'gara'.
Those
great
services
that
we
had
mounted
within
a
single
flow,.
A
Good
the
solution,
because,
because
redhat
is
good,
open
source
technology
which
leveraged
us
to
be
able
to
offer
the
business
new,
innovative
things
new
ways
of
thinking
about
how
to
solve
things,
it
has
a
self-
provisioning
platform
that
guarantees
agility.
Speed,
manages
support
with
local
resources.
A
Everything
which
is
ours,
our
partners,
who
accompanied
us
throughout
the
process
of
adopting
this
platform,,
guided
and
accompanied
us
throughout
this
time,
in
order
to
guarantee
the
success
of
the
project,,
something
that
is
very
important
to
what
this
platform
is.
When
you
begin
to
analyze
it
There
is
a
lot
of
information
on
how
it
works,
how
you
can
build
microservices
within
the
platform,
which
technologies
are
supported,
which
are
not,.
How
you
should
change
to
be
able
to
manage
your
services,
and
now
with
the
new
versions
of
the
platform,
well,?
A
A
We
tried
to
take
off
what
the
developer
was,,
who
had
to
dedicate
himself
solely
and
exclusively
to
to
develop
and
distanced
himself
from
thinking
about
how
he
had
to
implement
everything.
That
was
a
good
microservice
within
the
platform,,
as
we
have
already
said,.
This
technology
is
open
source
and
the
vast
majority
of
innovations
generally
come
from
the
open
south
side
with
what
which
we
have
guaranteed
that
part
of
the
platform.
A
When
we
began
to
evaluate
the
architecture
of
the
bank,
we
saw
that
we
had
a
lot.
We
had
a
very
important
job
to
do.
We
have
to
start
to
separate
everything
that
were
our
customer
service
channels
and
our
back
office
start
to
guide
them
to
start
using
a
first
one,
an
architecture
in
which
it
is
managed
solely
and
exclusively
with
our
integrations
layer
to
be
able
to
reach
our
bank
emails.
A
For
this
we
began
to
think
with
openshift
to
mount
our
entire
integrations
layer,
which
was
the
that
was
outside
of
the
one
we
started
this
project
with
and
with
which
we
started
working,
how
we
started
working
on
it,.
Well,
we
started
diagramming
everything
that
is
architecture
and
to
be
able
to
make
the
development
of
microservices
and
their
implementation
independent,.
We
also
acquired
what
was
the
trisquel
to
handle
everything
that
is,
the
security
layer.
A
How
we
started
when
we
were
presented
with
this
idea
of
being
able
to
set
up
the
platform
approximately
14
15
months
ago.
We
began
to
think
with
a
challenge
where
the
first
thing
we
did
was
install
a
master
node,
a
node
of
infrastructure
and
one
of
applications,
however,,
this
type
of
resources,
and
that
and
that
platform
was
too
small
for
us,
and
that
led
us
to
have
some
problems.
At
the
moment
in
which
we
began
to
have
problems,.
A
The
product
version
that
we
used
at
that
time
that
we
decided
to
change
was
3.7.
On
this
platform
we
installed
version
3.9
of
openshift,
and
we
mounted
each
of
the
nodes
with
four
cuts
in
each
one
of
them.
In
the
master
nodes
we
put
24
gb
of
ram
and
in
the
new
application
ones,
also
with
4
cuts.
We
also
mounted
them
with
24
gigabytes
of
ram.
This
was
our
initial
platform
to
be
able
to
support
everything
that
was
the
adoption
of
microservices.
A
When
managing
four
environments
within
the
bank,
we
thought
of
making
a
decision
to
what
to
do.
If
we
install
a
cluster
for
each
environment
or
divide
it
using
tennant.
The
advantage
that
open
chief
has
is
precisely
that
of
being
able
to
divide
the
environments
into
different
themes,
to
be
able
to
handle
different
different
environments.
A
How
we
started
once
we
had
the
platform
installed,
we
had
to
demonstrate
the
value
of
the
platform
with
which
we
held
a
small
meeting
with
the
management,
and
we
showed
them
through
a
hello
world.
What
were
the
benefits
of
the
platform
where
we
built
a
small
site
within
openshift
and
that
site
modified
it?
During
the
presentation
we
made
to
senior
management
I
modified
it,
we
made
a
small
modification
and
we
made
it
go
through
all
our
environments.
A
A
Core
layers
to
be
able
to
optimize
the
obtaining
of
the
information
we
carried
out
the
stress
tests
when
we
thought
about
setting
up
the
introduction,
many
uncertainties
arose.
Everyone
had
many
doubts,
our
platform
area,
our
government
area,
our
our
areas
that
give
us
production
support,
wondered
how
This
new
consolidated
position
was
going
to
work
when
it
was
put
into
production
and
it
is
logical,.
It
is
a
new
platform,.
It
is
a
new
technology,.
It
is
a
totally
new
architecture,
which
brings
with
it
a
lot
of
uncertainties,.
A
A
Help
of
Jamie
Ter
and
sending
him
a
load
of
approximately
double
what
he
supports
with
all
the
channels
in
production
brought
us
good
results,.
However,
they
were
not
yet
conclusive,
tests,,
with
which
we
began
to
work,
to
see
what
the
doubts
that
arose
from
the
uncertainty
were.
to
be
able
to
set
up
this
consolidated
position
in
production
and
what
they
asked
us
was,.
But
how
is
the
platform
going
to
behave
if
a
new
one
crashes,
if
one
of
the
nodes
crashes,
what
will
happen
if
it
suddenly
starts
to
receive
more
load?
A
How
are
we
going
to
react
to
be
able
to
make
it
work
if
we
do
not
have
the
support
that
guarantees
that
it
is
bringing
the
correct
information?
Well,
then,
we
begin
to
propose
other
types
of
tests.
Other
types
of
scenarios,
such
as
during
stress
tests,
we
drastically
lowered
a
node,
and
we
saw
how
automatically
Our
containers
record
another
of
the
new
ones
that
were
available,.
A
A
Also
began
to
do
other
types
of
tests
to
be
able
to
guarantee
the
number
of
transactions
that
he
was
going
to
receive,
and
we
selected
one
of
the
pilot
channels
to
be
able
to
work
with
this
consolidated,
position.
We
chose,
which
is
our
crm
since
it
had
the
feasibility
of
being
able
to
easily
configure
pointing
the
old
shovel
to
the
old
consolidated
position
or
to
the
new
consolidated
position.
Depending
on
whether
or
not
there
was
any
problem
when
it
was
deployed
in
production,.
A
This
is
how
we
left
in
October
of
last
year,
with
the
consolidated
position
until
production,
pointing
the
channel
is
re
m
and
what
we
observed.
We
were
monitoring
it
for
some
period
of
time
during
the
implementation.
The
same
many
doubts
uncertainty
start
to
see
how
this
consolidated
position
was
going
to
work
and
what
we
saw
Pleasantly,,
both
the
redesign
of
microservices,
being
able
to
implement
it
within
openshift,
and
the
redesign
of
the
accompaniment
of
the
forgiveness
channels
of
those
of
the
back
end
made
us
display.
A
The
customer
information
within
our
page
of
crm
from
the
main
page
took
around
30%
faster,,
which
was
a
great
relief
because
it
is
raising
the
consolidated
position
within
any
channel
has
to
be
something
very
fast
and
optimal,
and
this
good
gave
us
an
idea
that
this
was
the
the
path
that
we
had
to
follow
here
and
that
somehow
we
had
some
metrics.
The
platform
had
responded
adequately.
We
had
gained
in
performance
and
we
still
needed
many
other
things
to
discover.
A
Such
as
the
implementation
strategy,
as
we
already
mentioned,
we
installed
the
platform,
the
two
clusters,
both
the
pre-
productive
as
productive
in
May
2018
around
August.
We
were
able
to
make
a
small
bid
to
show
what
the
benefits
of
the
platform
were.
Like,
then
in
October
we
implemented
the
embi
that
took
approximately
10
percent
of
the
transactions
from
the
old
platform
to
this
new
integration
platform
and
with
the
guarantee
that
it
was
working
and
everything
was
working
properly.
A
Well
How.
We
managed
to
move
forward
with
this
plan
with
dedicated
resources
at
first
to
be
able
to
move
forward.
With
this,
with
the
pilot
test
and
with
the
embi
request
for
the
consolidated
position,,
we
had
a
team
of
three
developers,,
two
architects,,
a
platform
person
and
a
part
time,
person.
information
security
within
the
team,,
the
strongly
empowered
team,.
A
That
team
was
strongly
empowered
by
our
leadership,
by
our
Haitian
management,,
and
every
time
we
had
the
need
to
go
talk
to
an
area
where
we
had
to
go
to
request
resources
or
some
information,
security
need,,
something
that
It
is
natural,
that
it
blocks
us
from
moving
forward
and
we
go
with
the
openshift
flag
and
fortunately,
the
door
is
always
opened
for
us..
It
is
very
important
to
have
the
support
of
senior
management
to
be
able
to
move
forward
with
this
type
of
project.
A
If
it
is
not
a
little
difficult
that
we
did
before
being
able
to
deploy
the
mp
during
those
months
in
which
we
were
working
hard
on
the
migration,
we
had
to
define
standards
and
patterns
to
be
able
to
guarantee
that
the
deployment
of
our
microservices
would
always
be
the
same
way.
Now
in
the
next
In
detail,,
we
are
going
to
see
with
half
land,
or
we
did
good
empowering
the
team
for
decision-making.
All.
A
Our
developments
are
always
thought
of
in
the
architecture
of
microservices
and
peace,
to
accompany
the
digital
transformation
that
the
bank
was
asking
us
for
the
integration
of
the
channels
as
well.
It
is
via
API,,
with
which
we
are
working
hard
to
amplify
the
bank,,
not
only
from
channels
and
the
integration
layer,,
but
we
are
also
working
so
that
in
the
lower
layers,
we
also
start
talking
only
in
the
app,.
A
It
is
good
and
with
the
help
of
the
integration
of
pit
cycle
assembly
tools,
if
this
is
not
automated,
it
is
difficult
for
us
to
have
that
speed
that
we
continue
to
maintain
not
the
truth.
That
implementing
this
type
of
platform
is
only
the
tip
of
the
air.
All
the
rest
that
accompanies
the
implementation
of
This
platform
for
cultural
change
and
the
box
is
what
I
think
is
the
most
important
thing.
It
is
almost
90%
of
the
work
that
needs
to
be
done
to
be
able
to
make
that
cultural,
change.
A
A
And
do
more
open
source
to
have
to
investigate.
We
had
to
investigate
a
lot,
because
we
are
not
experts.
We
were
not
experts
when
we
started
working
with
red
hat
and
with
our
rehab
papers.
We
had
many
doubts
and
that
can
only
be
solved
by
investigating
testing,
testing
and
testing
failing
and
trying
again
good,
where
we
are
the
image
that
everyone
knows
the
box.
A
We
use
jenkins
for
the
hitler
pipelines
as
the
sonar
code,
centralization
tool
for
the
management
of
automatic
verification
of
nexus
code
as
a
server
for
the
central
repository
of
libraries
at
the
tower
level,
we
are
doing
some
pilot
tests
with
to
be
able
to
automate
at
the
time
to
be
able
to
implement
the
platform.
What
we
used
was
tower
with
the
play
books
provided
by
redhat
to
be
able
to
deploy
all
the
jira
resources
for
everything
that
is
the
cloudforms
life
cycle
to
monitor.
A
In
its
beginnings,
we
began
to
use
this
cloud
form
to
begin
to
see
how
the
platform
behaved
and
compare
it
with
the
tools
we
had
within
the
bank
and
see
how
we
found
if
it
was
Like
it
or
not,.
A
lot
of
doubts
arose
and
we
began
to
chat
with
him
with
the
red
hat
teams
that
somehow
later
classified
themselves
with
the
typical
use
of
the
platform,
good
for
capturing
blogs
and
visualizing,.
A
We
use
fru
ndi
to
be
able
to
capture
it
is
the
and
we
save
the
information
in
elastic
search
and
visualize
it
with
ivana
and
well
our
baby
manager
that
this
trees
cake,
which
we
have
in
hybrid
form,
what
else
to
monitor
the
tool.
Also,
as
we
have
seen,
some
standards
have
already
become
graph,
anahí
prometheus.
In
addition
to
the
corporate
tools
that
we
have,.
It
is.
A
Good
that
we
have
in
the
span
of
a
year
or
so
within
the
platform
we
have
my
degrees
and
100%
of
the
services
of
our
integration
layer
have
been
deployed,.
It
is
old,.
We
are
already
thinking
about
migrating
the
services
that
are
mounted
on
the
second
middleware
that
had
been
implemented
five
years
ago
and
that
did
not
come
to
fruition,.
So
we
are
working
hard
on
that,
but
not
only
have
we
migrated
microservices
within
our
integration
layer,
but
we
also
have
working
or
are
working
directly
on
the
openshift
platform.
A
Seeing
all
this
all
these
benefits
and
benefits
it
had
over
the
digital
edge.
Our
digital
edge
of
the
mortgage
bank
is
running
purely
on
openshift,
so
we
trusted
openshift
and
it
has
given
us
good
results
and
as
somehow
we
saw
that
everything
this
was
working.
We
worked
on
the
redesign
of
the
new
home
banking
that
today
is
also
running
and
containerized
within
openshift.
So
these
are
on
these
platforms
that
are
extremely
important
to
us.
A
We
have
had
the
confidence
to
be
able
to
mount
it
within
the
openshift
platform
because,
because
it
has
given
us
results,
when
we
started
to
do
the
stress
tests,
we
saw
that
it
worked.
We
have
had
practically
no
problems
today
when
we
have
worked
very
hard
with
the
platform
update.
We
have
not
had
great
risks
in
terms
of
adding
more
nodes,
so
it
has
many
benefits,
Being
able
to
start
working
with
openshift
that
we
have
today
within
the
platform.
How
is
our
production
cluster?
A
We
have
the
same
three
infrastructure
nodes
which
will
increase
from
4
to
having
4
corts
to
having
16
corts
each
of
the
nodes
with
470
GB
in
ram
and
24
GB
of
470.
You
arrive
on
hard
disk
and
24
each
one
of
the
nodes
becomes
in
rme
and
we
went
from
having
three
application
nodes
to
approximately
eight
nodes,
but
it
will
have
eight
application
nodes
supporting
all
of
this.
Each
of
those
application
nodes
has
16
16
8,
sorry,
it
has
8
corts
handles
24
gb
in
ram
and
170
gigabytes
of
hard
disk,.
A
So
it
is
our
productive
cluster,
which
we
are
also
beginning
to
evaluate
to
grow,,
because
we
have
to
put
more
applications
within
that
cluster
and
something
that
I
was
commenting
on
yesterday
with
Santi.
That
I
told
him
that
It's
going
to
kill
me,
but
we
've
also
been
inheriting
some
applications
that
are
built
on
old
versions
of
java
and
what
we
did
was
keep
them
up
and
put
them
into
the
platform.
Today
we
have
them
working
productively
productively
and
we
haven't
had
any
problems.
So
this
one
It
has
supported
everything.
A
That
is
the
infrastructure,
but
the
code
is
not
so
capable,
but
well,.
We
began
to
evaluate
and
see
that
the
issue
of
containerization
within
the
platform
gives
us
many
benefits,
because
before
we
thought
that
for
an
application
to
have
to
mount
it
within
of
our
systems
within
our
infrastructure,,
we
have
to
think
of
a
development
server,,
an
integration
server,,
an
approval
server
in
the
worst
case,,
but
a
large
one.
A
That
will
support
the
three
environments
and
also
two
servers
in
the
production
environment
to
be
able
to
support
high
availability
and
each
of
those
servers
with
their
licenses,
their
operating
system
for
their
monitoring
tools
with
the
computer
security
things
that
gmt
in
order
to
guarantee
their
functionality
plus
the
time
that
it
would
take
us
and
well,.
All
of
that
now
when
we
started
to
have
applications,
the
first
thing
that
What
we
do
is
try
to
contain
them,,
hoist
them
and
mount
them
on
open
chips,.
A
Throughout
all
this
time
we
have
had
several
lessons,
many
things.
We
have
gone,
through,,
I,
think
As
I
said
before,.
The
installation
of
the
platform
is
the
tip
of
Albert,
after
all,
everything
that
comes
after
it
is
what
is
linked
to
the
adoption
of
the
tools
of
the
box,,
the
life
cycle,,
being
able
to
sit
down
and
negotiate
with
the
areas
to
be
able
to
work.
and
to
empower
all
this
work,,
so
the
optimization
of
resource
resources,.
A
We
have
seen
it
when
comparing
what
was
the
old
integrations
platform
where
all
our
integrations
layer
was
mounted,,
which
managed
distributed
in
5
nodes,
approximately
120,
corts
and
220
gigabytes
of
memory
ram
now
trying
to
abstract
from
the
new
infrastructure
and
the
new
master.
Our
integration
layer
is,
with
all
the
with
100%
of
the
functionalities
and
80%
of
the
transactions
running
on
said
platform
in
openshift.
It
handles
around
70
80
core
depending
on
the
load,
and
it
does
not
eat
more
than
120
gigabytes
of
memory
in
ram,.
A
What
this
gives
us
is
a
saving
of
approximately
30
to
40
percent
in
terms
of
infrastructure
thinking
only
about
infrastructure,
because
we
also
did
an
important
job
when
going
to
the
microservices
architecture.
The
redesign
the
accompaniment
of
the
back
is
with
new,
more
optimal
functionalities.
In
some
way.
All
of
this
helped
that
the
work
of
optimizing,
the
infrastructure
we
are
seeing
now
well,
the
scalability
is
real.
It
really
amazes
me
how
being
able
to
support
the
doubling
the
load
within
the
platform
for
a
base.
Application
is
more
than
just
pressing.
A
A
button
is
nothing
more
than
pressing
a
button
to
be
able
to
already
have
22
posts
running
within
the
platform
and
supporting
practically
double
the
load.
Well,
the
tool
two,,
the
cultural
change
that
we
have
to
make
to
be
able
to
accompany
this
entire
life
cycle,
without
a
doubt,
collaborative
work,,
being
able
to
sit
down
with
each
of
the
areas
and
negotiate
how
we
are
going
to
move
forward
with
all
this
process,.
A
It
is
very
important
to
be
able
to
have
the
empowerment
of
the
direction,
because,
if
it
does
n't
become
a
bit
difficult
before
the
team
that
was
working
on
openshift,
there
were
only
three
dedicated
developments.
There
were
only
three
developers,
two
architects,
one
platform
person
and
part
insecure
IT.
Today,
open
chief,
is
somehow
ending
all
areas.
The
development
team
and
the
entire
team
of
the
largest
of
our
type
of
platforms
know
them
for
sure,.
They
are
also
aware
of
what
the
platform
is
and
how
they
worked.
Well,.
A
Standardization
is
extremely
important
to
establish
the
rules
on
which
we
are
going
to
work.
To
that
all
this
works
properly
and
the
most
important
of
all
is
the
cultural
change.
Thanks
to
the
tools
and
methodologies,
this
type
of
thing
can
be
achieved.
Well,
the
questions
they
told
me
that
they
can
ask
us
so
see
you
in
a
while.
Thank
you
very
much.