►
From YouTube: Produban DevOps in action with Red Hat OpenShift
Description
Cristian Roldan, Produbans Lead PaaS Engineer, shows you how Produban was able to transform their traditional IT organization spanning multiple companies and countries in one built around DevOps. Watch how they leverage OpenShift and OpenStack to minimize environment differences, reduce deployment times, improve their time to market all while using the same tools for both Dev and Ops.
Don't forget to check our blog, https://blog.openshift.com/, to find more content that will help you ramp up your DevOps knowledge.
A
A
So
let
me
introduce
what
is
proven
proven
is
a
global
company.
We
belongs
to
the
Santander
group.
Santander
is
one
of
the
most
important
bank
in
Europe,
also
in
South
America
in
Poland.
We
are
more
than
5000
professionals
in
nine
countries
we
are
in
in
in
Spain
in
Germany,
United,
State,
nursing,
Dina,
Chile,
Mexico,
Brazil,
okay,.
A
A
Deb's
and
Hobbs
works
in
silos
in
general,
when
there
are
mixed
problems
in
production
in
China,
the
obsesses,
the
prohibition
and
the
Java
code
and
the
development
says
I
know
the
prince
with
a
lot
of
age.
We
promise
with
a
proxy
the
promise
with
a
application
server
the
proteins
from
the
the
WestEd
for
each
side.
So
these
are
the
the
most
common
problems
in
a
traditional
IT
IT
company.
Well,
they
in
general,
the
devs
sometimes
does
know
or
understand
the
the
arts
environment
complexity.
In
a
bank
we
have
a
lot
of
components.
A
There
are
a
lot
of
fun
component
that
are
interconnected,
so
it's
really
really
complex
to
to
understand
the
same
for
the
knobs,
the
ops
in
general,
when
we
receive
a
new
obligation
for
us,
his
application
is
a
black
box.
We
doesn't
know
anything
about
the
the
the
runtime
how
to
tune
the
application,
how
to
configure
application
and
that's
another.
Another
problem
lack
lack
lack
of
communication
between
their
son
or
an
OPS.
That's
a
is
another.
A
A
big
big
problem
and
they
were
knobs,
have
different
objectives
in
our
case
as
a
dolly
we
are,
we
are
two
different
companies,
one
for
production
and
another
for
development.
So
what
what
we
were?
The
reason
to
adopt
the
web
scene
in
our
company
in
general?
These
are
the
most
common
reason.
What
share
the
same
share
the
same
tools
for
them:
an
OPS
increase
collaboration
with
Whedon
depths
and
Hobbs
reduce
the
plumbing
time,
minimize
environment
differences,
improve
time
to
market
platform
tools,
automate
deployment
ask
provide
a
global
service,
reduce
infrastructure
operation
cost.
A
That's
was
one
of
the
most
important
topic
when
the
most
important
reason
continued
delivery
also
is
another
important
reason
why
we
decide
to
adopt
devolved
approach,
improve
resolution
time
and
also
more
time
available
to
add
value,
continues.
Improv
improvement.
Okay.
So,
in
order
to
adopt
this
this,
this
DevOps
approach
in
Perl
one
we
decided
to
create
a
service
called
Google
Pass
service
for
the
web's.
This
service
is
based
on
open
ship,
Enterprise
version
3,
and
let's
see
the
current
status
of
this
this
project,
we
have
deployed
a
global
path
that
is
based
on
operative
enterprise.
A
We
have
deployed
this
the
open
ship
in
different
regions.
We
are
in
Mexico
and
Spain.
In
Spain
we
have
two
data,
72
data,
centers
and
also
in
in
UK
in
the
next
two
weeks.
We'll
be
finish:
the
brazil
regions,
all
the
open
chief,
are
deployed.
On-Premise
are
employed
on
a
red
cotton
of
a
stock
version,
Juneau.
A
A
A
The
next
layer
is
the
open
ship
infrastructure
nose.
We
deploy
routers
and
also
the
ocular
service.
Ok,
we
are
not
using
the
offensive
registry.
Ok,
we
use
an
external,
an
external
docker
registry
for
the
next
layer
is
the
the
open
ship
node.
Here
we
is
where
we
run
the
applications,
the
containers
we
have
to
kind
of
nodes,
one
for
production
and
I
for
non
production
applications.
A
We
also
have
monitoring
system
for
the
infrastructure
we
use,
while
intrascope
from
CA
for
the
cloud
OpenShift
cluster
management,
we
we
are
trying
to
use
cloud
form,
but
at
the
moment
we
don't
use
cloud
forms,
but
our
idea
is
to
use
the
near
future
for
the
log
management
we
have
a
cluster
of
elasticity.
We
send
all
the
infrastructure
logs
to
this
central
log
repository.
A
We
use
a
jump
host
from
this
host.
We
deploy
the
rural
pass
infrastructure
and
also
we
manage
the
open
ship
cluster
from
this.
From
this
No,
we
deploy
a
monitoring
solution
for
the
applications
we
use
a
while
Interscope
and
we
have
external
docker
registry
in
each
region
and
we
have
a
data
lake
for
the
application
logs.
All
the
container
standard
output
and
standard
error
are
sent
to
these
data
lakes
or
ideas
to
use
this
data
like
not
only
for
the
container
logs,
also
for
the
the
metering
logs,
HTTP
access,
log,
etc.
A
A
In
order
to
improve
the
DevOps,
a
Productivity,
we
found
that
the
open
chief
console
is
good
is
not
enough,
so
we
decided
to
create
some
some
tools
around
open
chief,
so
ideas
to
introduce
some
some
tools
that
we
have
colored
in
proto
one.
Well,
this
is
the
first
tool.
This
is
the
status
page
from
this.
Using
this
this
tool,
we
can
get
the
the
the
cluster
status,
for
instance.
Here
we
we
have
the
master
service,
we
can
get
the
routers
they
three,
the
safe,
etc.
A
A
This
is
the
uptime
service.
We
have
different
views
for
the
uptime
we
for
instant.
This
is
the
monthly
bill.
We
have
the
information
the
uptime
for
every
month
and
also,
if
we
click
in
this
red
cycle,
you
can
get
the
issues
and
changing
for
that
for
that
month.
This
is
a
very
interesting
tool
for
the
DevOps
DevOps
team
for.
A
A
We
have
another
service,
very
interesting
service
called
the
notification
service.
This
is
our
public
service.
Every
Santander
employee
can
subscribe
to
the
service
you
who
want
to
get
information
about
issues
changes
in
our
platform
you
can
subscribe.
It
is.
It
is
public
service,
for
instance,
you
we
have
different
channels
for
instant
change
and
issues,
newsletters,
docker
corporate
images
and
also
we
have
a
global
path
portal,
where
we
publish
tutorials,
teach,
node,
etc.
We
also
provide
all
this
information.
We
are
the
rest.