►
Description
OpenShift In Financial Services Panel
at OpenShift Commons Gathering 2019
at Red Hat Summit
moderated by Ben Henshall (Red Hat)
panelists:
Daniel Sanchez (Banco Hipotecario)
Eero Arvonen (Suomen Asiakastieto)
Raj Channa - Royal Bank of Canada (RBC)
Glen Rhodes (ANZ)
Walid Saleh (CIBC)
A
A
A
A
From
New,
York
and
actually
Argentina,
so
so
I
think
I
think
we
win
the
diversity
award
all
right,
so
I'm,
just
gonna
ask
some
questions
and
we're
going
to
hear
what
these
gentlemen
have
to
say
what's
going
on
their
world.
So
if
you,
gentlemen,
could
just
very
briefly
in
about
a
minute
or
so
just
explain
how
long
you've
been
using
redhead
OpenShift,
what's
roughly
in
your
stack,
what
version,
if
you
know,
and
and
start
off
by
saying
your
company
and
what
you
do
then
that'd
be
great.
Okay,.
C
Hi
my
name's
Glenn
Rhodes,
New
Zealand
XE,
probably
tell
I
work
for
ANZ
Bank
is
the
platform
manager
for
container
services.
State
assuming
technical,
stick
run
on
x86
platform
using
VMware
and
current
version
of
3.11,
and
we
recently
migrated
to
that
and
pretty
seamless.
We
run
a
Bluegreen
upgrade
and
it's
proved
to
be
quite
the
busy
picking
out
all
the
new
prometheus
product
seats
and
eagerly
waiting
in
the
420
exclusion.
As.
A
A
D
Name
is
Waleed:
I
worked
for
CIBC,
which
is
the
Canadian
Imperial
Bank
of
Commerce,
which
one
of
the
big
five
banks
and
in
Canada
I'm
the
Senior
Director
for
the
data
center
services.
So
my
team
manages
all
the
data
center
services.
We're
have
been
using
open
shifts
for
roughly
two
years
where
other
versions
3.7
we're.
Obviously
in
the
process
of
upgrading
as
well,
and
we're
really
looking
to
move
some
of
our
crown
jewel
applications
onto
open
shift.
B
Me
our
CEO
tends
to
make
this
joke
that
any
foreigner
will
go
to
extreme
lengths
not
to
pronounce
our
our
name
so
you're
all
excused
not
trying
so
we've
been.
We've
have
we've
had
our
private
OpenShift
cluster.
For
about
a
year
now
we
are
running
version,
3.2
n,
it's
running
on
VMware.
We
mostly
develop
on
Java
on
EAP.
B
E
Raj
China
from
Royal
Bank
of
Canada
I
am
part
of
the
technology
infrastructure
team.
There
were
a
ton,
the
technology
strategy
and
research
function,
so
we've
been
using
open
shape
for
about
two
and
a
half
three
years
now
and
we're
currently
3.9
and
we
are
in
the
process
of
going
to
311.
So
what's
in
the
stack
I
would
say
you
know,
apart
from
the
core,
open
shaft
infrastructure
itself,
the
masternodes,
the
infrastructure
nodes
and
the
app
nodes
I
think
some
critical
components
are
the
CI
CD
platform
that
goes
with
it.
E
The
different
repositories,
which
are
you
know
whether
it
is
you
know,
have
a
code,
repository
or
container
repositories.
We
do
have
vulnerability
scanning
engines
both
for
code
and
containers
and
then
you
know
I
think
all
the
logging
and
monitoring
function
that
goes
with
it
and
you
know
the
external
load,
balancers,
etc.
Yeah.
Thank.
F
You
hi
I'm
Daniel
Sanjay
from
mango
boticário.
We
have
started
using
open
shift
like
more
than
one
year
ago,
but
we
strongly
are
working
on
that
from
September
October.
We
are
currently
in
a
project
of
migrating
all
the
apiary,
all
the
all
services
that
we
used
to
have
to
api's.
It's
a
it's,
a
very
aggressive
project
that
we
are
now
in
cursed.
F
We
tried
that
for
two
reasons.
Why?
Because
the
bank
is
missing
strongly
in
all
the
digital
transformation,
but
also
because
we
had
a
need
of
going
on
that
direction,
because
we
were
in
an
of
solid
platform
before
so
now
that
the
project
is
going
on.
We
already
have
many
things
in
production
and
we
are
just
start
seeing
all
the
benefits
that
we
have,
but
still
we
need
to
get
more
matrix
on
and
start
knowing
the
program.
Every
time
that
you
implement
anything,
you
know
how
that
works
and
you
go
adjust
and
then
go
again.
A
Thank
you.
So
we
can
see
here,
ladies
and
gentlemen,
that
there's
quite
a
diverse
maturity
and
adoption
of
openshift
with
their
different
versions
and
their
different
infrastructure
stacks.
So
I
think
this
is
quite
a
quite
a
good
panel,
particularly
given
the
different
geographies
that
they're
dealing
with.
C
I
guess
the
business
context
is
firmly
in
our
digital
space.
Banking's
are
quite
competitive
markets,
getting
more
competitive
of
open
source
banking.
Our
traditional
way
of
delivering
services
could
take
weeks
or
months,
and
it
wasn't
good
enough,
so
they
challenged
technology
to
look
at
a
solution.
So
from
a
technical
perspective,
it
was
pretty
easy.
Everyone
knows
about
containers
and
humanities,
so
we
set
off
on
a
journey
to
not
only
port
there,
but
a
bunch
of
other
services
that
we
needed,
but
bucket
had
a
victory
and
so
on
like
the
Incans.
C
So
we
not
only
see
it
a
journey
and
the
way
with
openshift,
but
also
but
back
at
Jenkins
and
artifactory
to
support
it,
and
that
was
really
exciting.
So
we
took
a
bunch
of
our
rock
stars,
we
put
them
in
a
room
and
we
got
started
and
it's
been
about
a
year
and
a
half
and
we've
been
live
and
production
for
over
eight
months,
yeah
a
large
portion,
our
digital
services,
are
running
on
that
or
starting
to
develop
onto
the
platform.
So
it's
been
interesting.
C
C
To
value
or
differently
so
I
mean,
if
you
think
the
business
come
up
with
an
idea
or
concept
for
a
feature
and
it's
in
production
the
following
week.
This
is
three
or
four
months,
so
definite
business
value
smiles
all
around
smiles.
All
around
you
right,
you're,
the
hero,
I'm,
not
famous,
very
modest.
You
thank.
D
You,
yes,
so
I
think
actually
for
us
is
kind
of
interesting
because
it
wasn't
really
driven
by
the
application
team
or
the
infrastructure
team.
You
know
it
actually
was
a
move
from
the
architecture
team.
Saying
yeah
we
want
to
industry
lies.
If
you
like,
microservices,
create
a
API
marketplace
and
open.
You
know
this
API
is,
for
you
know,
used
by
everybody.
So
it's
really,
you
know
a
push
into
creating
that
open
bank.
D
If
you
like
and
there's
a
session,
actually
that
our
architecture
team
are
going
to
present
on
Wednesday,
if
you're
interested
you
can
go
and
listen
to
the
team
talking
about
this
whole
transformation.
That
is
really
how
it
started.
This
is
you
know
who
pushed
us
into
the
container
space
from
an
infrastructure
deploying
containers.
You
know
using
OpenShift
to
support
the
teams.
We
actually
have
roughly
forty
or
you
know
or
plus
you
know,
micro
services
running
there,
but
you
know
to
to
your
point
been
around.
You
know
what
the
reaction
was
in
fact.
D
Actually,
what
happened
is
that
we,
the
other
eighty
teams,
are
the
application.
Development
team
got
quite
excited
about
the
potential
so,
as
we
were
building
this
API
marketplace
and
building
the
infrastructure
to
support
it,
you
know
that
demand
was
just
you
know
was
really
beyond
what
we
expected.
We
actually
have
a
bunch
of
apps
that
even
went
live
today
in
our
private
cloud.
You
know,
if
you're
into
structured
notes,
you
can
go
notes,
dot,
CIBC
dot-com.
You
know
this,
sir,
is
a
plug.
D
If
you,
you
know,
if
you
wanna
do
structured
notes
in
capital
market,
but
you
know
it
was.
It
was
really
interesting
that
I
think
you
know
the
the
teams,
the
ad
team
started,
seeing
the
the
potential
you
know
in
terms
obviously
of
the
time
to
market.
In
terms
of
you
know
how
the
you
know,
the
architecture
really
differs
from
the
legacy
that
we
have,
and
you
know
we're
seeing
a
lot
of
excitement.
You
know
in
that
space.
Thank
you.
Okay.
Well,.
B
So
so
that's
definitely
that
it's
something
that
was
mended
by
by
the
open
shift
platform
now.
Another
thing
regarding
this
high
availability
thing
is
that
the
way
we
use
to
run
our
systems
is
that
we
have
a
set
number
of
application
servers
which
are
crammed
with
deployed
artifacts
and
now,
if
one
of
those
goes
haywire
that
can
affect
other
services
as
well
so
resource
isolation
provided
by
containers
is
definitely
a
huge
factor.
Great.
A
E
Rbc
we've
been
going
through
a
cultural
transformation
for
a
couple
of
years
now,
mainly
to
you
know,
enable
the
business
to
you
know,
move
faster
to
be
more
agile
right.
So
to
that
end,
we
done
a
lot
of
things
with
agile
devops
how
people
interact
with
each
other.
The
way
we
do,
we
reward
a
open
source,
culture
and
engineering
culture,
how
innovation
happens,
etc.
So
all
of
this
is
to
enable
faster
time-to-market
write,
faster
provisioning
and
abling
applications
to
be
delivered
faster.
E
F
F
We
need
to
go
on
how
the
functionalities
divided
in
container,
to
be
able
to
touch
all
the
same
time,
given
that
on
the
velocity
that
we
have
for
deploying
in
in
that
architecture
and
also
for
the
stability
that
they
give
us
and
the
ability
also
to
scale
in
the
big
days.
It's
some
of
the
factors
that
make
us
go
in
that
direction.
Right.
A
Thank
You
Daniel
I,
said
you
know,
I.
Think
folks
again,
just
with
my
experience
across
the
asia-pacific
I've
seen
in
financial
services,
this
real
switch
from
a
cost-saving
sort
of
model
of
save
money.
You
know
IT
department,
so
now,
how
do
you
enable
the
digitization
of
banking
or
financial
services
in
the
most
expeditious
and
fast
and
agile
way?
How
do
you
get
your
code
out
into
production
in
the
most
efficient
and
productive
and
stable
high-performing
way,
and
it
sounds
like
from
all
of
you
really
that's
been
the
prime
motivator
I've
not
heard
really
about
much.
A
How
do
you
save
money?
How
do
you
actually
deliver
code?
You
know
in
a
consistent
and
and
much
more
more
lane
lane
can
I
can
I
ask
you,
gentlemen,
what
are
the
top
two
things
that
you're
planning
on
doing
with
containers
or
OpenShift
in
the
next
sort
of
twelve
months,
just
to
give
the
audience
a
sense
of
you
know
now
that
you've
got
the
platform
in
or
you're?
Actually,
you
know
putting
a
number
of
applications
already
in
production.
What
what
are
you
next
looking
at?
A
C
To
just
to
just
yeah,
we
we
put
ourselves
under
pressure,
so
it's
about
five,
but
and
for
a
customer
with
looking
at
a
queuing
or
Kefka.
Is
a
service
also
service
mish
for
the
team,
we're
focusing
all,
obviously
on
vision
for
it,
but
also
where
the
fusion
for
potentially
a
gene
platform
redesign.
So
it's
our
key
focus
and
one
of
the
other
things
we're
doing
also
is
showcasing
the
technology
to
different
teams
within
technology.
C
D
Yeah
I
think
there
is
a
laundry
list
of
items
you
know
upgrade.
You
know
make
sure
that
you
know
we
have
the
right
skills
and
you
know
all
of
that.
I
think
the
the
the
one
of
the
interesting
one
for
me
is
actually
work
better
with
or
work
closer
was
the
application
of
the
solutions
and
design
teams.
You
know
the
the
way
the
architecture
is
is
completely
different
from
the
old
legacy.
You
know
the
old
in
the
old
days
we
would
used
to
say
it's
like
for
like
what
we
want.
D
No,
it's
like
for
better,
so
citrus
that
make
them
understand.
You
know
how
that
this
is
not
the
same
way.
You
know,
I
have
an
app.
You
know
this
is
I'm.
Gonna
I'm
gonna
now
deploy
an
app
and
then
I
need.
You
know,
you
know
15
different
machines,
you
know
and
I'm
gonna.
You
know
by
15
different
nodes
for
open
shift
and
then
another
apps
are
gonna
have
another
15
and
we
end
up
with
you
know:
600
CPU
consumed
on
apps
that,
frankly,
are
not
actually
worth
it
most.
D
Probably
right,
but
you
know
it's
more
around
and
make
them
understand
how
the
architecture
is
and
and
obviously
also
understand,
better
how
we
charge
back
your
bags
at
the
of
the
day.
I
give
you
a
dollar,
you
know,
so
you
can
save
you
know
a
certain
amount
could
be.
A
dollar
could
be
more
depending
on.
D
You
know
how
you
know
your
finance
team,
how
stringent,
if
our
nest
team
is
so
it's
very
important
actually
that
you
know
we
figure
out
the
right
cost
model
and
help
our
solution,
design,
team,
an
application
team
understand
actually
how
to
size
and
how
to
design
properly,
and
how
that
you
know
it's
a
change
in
and
the
way
things
would
work
there
is
you
know,
there's
more
sharing.
It's
not
you
know,
you're,
isolated
legacies.
Some
like
you
used
to
do
is
a
lot
of
hardware.
D
B
Right
so
for
the
last
year
it's
been
clear
that
the
new
way
we're
developing
our
services
is
it's
pretty
successful
and
right
now
we
have
mandate
to
basically
make
build
or
all
of
our
new
services
right
and
OpenShift,
but
that
hasn't
completely
happened.
So
it's
my
personal
goal
to
pull
that
all
the
way
to
100%
and
for
the
new
new
services.
So
that's
that's
one
and
then
there's
the
other
thing.
B
E
Top
two
things
I
think
well,
oh
the
past
couple
of
years
we've
been
doing
a
lot
of
work
on
continuous
and
Linux
workloads.
Right
I
mean
we
see,
there's
a
bigger
opportunity
in
container
icing,
Windows
workloads
now
so
essentially
with
you
know,
dotnet.
That
is
a
big
area
for
opportunity
for
us,
that's
something
that
we'll
be
concentrating
on
going
forward.
E
The
the
other
thing,
too,
is
we
like
this
marriage
that
has
happened
between
IBM
and
Red
Hat,
essentially
because
RBC
is
a
big,
IBM
sure
and
like
every
other
Bank
here,
so
you
know
we
in
order
to
support
all
the
IBM
frameworks
we
had
to.
In
the
absence
of
this,
you
know
integration
we
would,
we
would
have
had
to
create
separate
clusters.
They
would
sort
of
be
like
two
different
brains
that
don't
talk
to
each
other.
E
A
Interesting,
it's
interesting
about
the
windows
about
that
I
mean
I,
I've
been
at
red
head
eleven
and
a
half
years,
and
you
know
obviously
having
Satya
talk
tomorrow
and
then
you
know,
Microsoft
do
their
thing
and
it's
just
wonderful
to
see
this
lovely,
heterogeneity
and
polyglot
really
coming
to
the
fore
and
to
have
a
bank
talk
about
the
fact
that
they're
going
to
be
focusing
on
Microsoft
workloads
on
I've
been
chief.
You
know
one
of
the
most
highly
regulated
industries,
I
think's.
You
know
just
testament
to
the
fact
of
this
stuff.
F
Well,
I
mentioned
before
that
we
are
in
the
middle
of
this
process
for
putting
all
these
all
services
in
in
API
some
micro
services,
but
that
was
more
than
you
need
than
the
portion
that
we
want
to
do
that,
have
open
different
doors
or
different
functionalities
to
to
be
able
to
develop
in
the
Indy
Bank,
we
have
created
a
the
onboard,
a
digital
onboarding
for
our
customers.
We
put
that
all
over
home
in
ship.
F
It's
a
new
channel
and
calling
all
the
API
is
for
validating
identity
of
the
person
calling
to
a
agency
that
is
governmental
agency
for
validating
that
the
person
is
Hussein,
making
facial
recognition
using
English
services.
We
already
launched
that
on
December
of
a
year
and
we
continue
evolving
that
and
in
the
meantime
we
are
talking
here.
They
are
making
the
last
stress
test
because
we
are
launching
the
the
new
home
banking
for
the
bank.
F
That's
also
using
only
P
is
based
on
OpenShift
and,
of
course,
every
time
we
are
launching
something
we
need
to
test
and
ensure
that
all
the
configurations
are
set
properly.
But
we
are
going
on
that
direction.
Every
channel,
every
API
that
we
are
developing,
we
are
making
air
engineer
E
and
putting
that
on
open
ship
right.
A
A
The
way
that
redhead
thinks
about
financial
services
is
generally
sort
of
really
three
themes
around
digital
engagement.
There's
a
you
know.
This
theme
around
open
banking,
which
is
really
this
API
first
approach
of
internal
and
then
external,
and
then
those
sorts
of
things
with
the
legislation
coming
in,
but
then
the
new
markets
that
that
presents
and
then
that
transactional
operational
efficiency
in
high
security-
and
we
all
know
the
Internet's-
really
safe
right,
yeah.
A
A
C
C
More
and
culture,
I
think
and
one
of
the
clear
things
we've
noticed
over
the
last
three
or
four
months
as
the
adoption
to
look
at
the
technology
stack
has
slowed
down
a
bit
and
maybe
when
we
started,
we
should
have
had
a
similar
like
team
running
in
parallel.
That
would
help
we've
got
quite
a
large
development
community
Java
core
help
them
will
coach
them
onto
the
new
technology.
Six
much
like
the
Innovation
Lab
Ziggy's
that
listening
today
I
think
that
innovation
labs
are
great.
C
It's
been
a
Red
Hat
person
up
on
stage
with
partners
talking
about
all
the
success
stories,
so
it's
quite
interesting
but
yeah.
If
we
could
do
one
thing
again,
I
think
we
would
put
just
as
much
effort
into
a
team
that
was
going
to
coach
in
to
take
our
developers
on
the
journey
right.
So
you're
saying.
C
They
can
pretty
much
put
something
in
to
create
a
project
and
run
up
through
the
CI
CD
pipelines
in
and
put
it
into
prod
within
a
week
if
they
want
to
do
so-
and
we
wouldn't
know
right
so
that's
sort
of
the
downside
of
that
is
some
of
them
think
it
might
be
too
hard
and
go
back
to
the
old
traditional
way
of
thinking.
I'll
put
this
on
a
server
we
just
want
to
quell
that
and
coach
and
help
people
on
the
journey
as
well.
Yeah.
Thank
you.
Yeah.
D
I
mean
for
us,
open
banking,
you
know
is:
was
the
driver
that
started
you
know
on
the
container
path?
It
is
absolutely
part
of,
and
parcel
of
our
strategy
in
the
bank
is
very,
very
important,
so
that
piece
in
would
continue.
This
is
gonna,
be
huge
focus.
You
know,
for
our
back,
I
would
say
the
other
piece.
You
know
you
know.
If
I
go
back
in
time,
I
would
I
would
spend
more
time.
With
my
you
know,
the
community
of
practice
was
the
development
team
break
more
barriers.
D
Explain
that
you
know
sharing
is
not
just
caring,
but
sharing
will
also
result
in
better.
You
know
return
on
investment,
and
you
know
financial,
because
every
one
of
the
unit
obviously
are
liable,
for
you
know
for
the
you
know,
for
the
cost
of
the
infrastructure
gets
built.
So
more
of
you
know
explaining
how
you
know
we're
changing
the
way,
we're
doing
the
infrastructure,
and
that's
you
know
we
can.
B
We
are
a
credit
information
company
and
PSD
to
is
very
interesting
to
us.
For
that
reason,
because
or
we
we
could
really
use
the
access
to
the
accounting
information
data
now
in
the
EU
open
banking
is,
is
really
driven
by
the
PSD
to
regulation
and
there's
a
huge
lack
of
standards
there.
So
developing
anything
on
top
is
like
shooting
in
the
dark,
basically
hoping
to
hit
something
right.
B
B
E
I'll
take
year,
what
would
you
do
differently?
Cuz
right,
so
we
all
know
there's
a
learning
curve
with
kubernetes
and
to
that
and
we
find
that
you
know
in
a
big
enterprise.
You
know
people
are
always
busy
they're
trying
to
do
a
lot
of
different
things
at
the
same
time
and
you
know
making
it
a
lot
more
easier
for
people
for
developers
to
be
able
to
containerize
something.
You
know
we
started
off
doing
CI
CD
with
some
existing
tools
that
we
had,
and
you
know
it's.
E
You
know
it's
even
for
people
who
have
used
CI
CD
traditionally
in
a
traditional
environment
or
maybe
in
another
past
service,
like
you
know,
Cloud
Foundry,
for
example.
There
are
some
changes
when
you
move
over
to
open
shift
in
kubernetes
right.
So
what
we
you
know
what
I
would
have
done.
Definitely
it's
possibly
made
it
as
simple
as
an
AWS
lambda,
or
something
like
that
where
they
would.
E
A
E
A
F
But
we
have
many
regulations
that
need
to
go
together
with
a
technology
right.
So
in
the
case
that
we
can,
we
are
opening
some
of
the
api's
to
the
movie
on
our
company.
So
in
our
case
we
have
one
example
of
it's
like
a
housing
ministry
that
we
are
opening
for.
Creating
micro
credits
to
is
a
kind
of
social
service
that
the
government
gives
and
that
that
kind
of
functionalities.
F
Now
we
are
open
to
provide
to
external
relations,
but
there
is
a
reg
occasion
of
the
business
delegation
of
the
people
to
start
seeing
that
opportunities
right.
It's
not
only
that
the
technology
needs
to
be
there
and
that's
all
now
we
have
the
opportunity,
then,
what
we
need
to
do
with
that
things.
It's.