►
From YouTube: Case Study: Moving Workloads to OpenShift Online Tero Ahonen (GameRefinery) OCG Helsinki 2018
Description
Case Study: Moving Workloads to OpenShift Online Tero Ahonen (GameRefinery)
OpenShift Commons Gathering Helsinki 2018
https://commons.openshift.org/gatherings/Helsinki_2018.html
A
I
still
work
for
reddit,
also,
and
thank
for
me
to
giving
me
this
opportunity.
This
is
this
room
speak
here
during
my
free
time,
I
spent
my
time
in
a
startup
called
Cambridge
firing
paste
in
here
in
Helsinki.
What
we
do
we
analyze
mobile
games,
we
analyze
markets
and
based
on
the
features
in
the
mobile
games.
Currently
only
at
App
Store.
A
We
give
the
games
score.
How
well
they
are
implemented,
how
much
features
day,
what
features
they
implement,
how
they
implement
it.
The
higher
the
score
is
the
higher
probabilities.
The
game
has
to
reach
top
20
top
10
top
5
in
App,
Store
top
grossing
ranks,
and
if
you
read
the
top
20
or
top
10,
you
will
be
basically
make
a
lot
of
money,
so
it
might
be
one
feature:
change
from
A
to
B
might
give
you
a
lift
to
be
better
than
your
competitor
I,
you
make
more
money,
that's
about
the
company.
A
We
do
brief
history
about
the
stack
that
we
had.
We
started.
I
didn't
have
time
to
do
the
timeline
actually
I
was
vacation.
Last
week
we
started.
I
was
not
there
in
yet
with
PHP
and
MySQL
and
Google
Cloud.
It
was
an
demo
pilot
now,
actually,
no
real
customers
tested
it.
It
didn't
work.
Then
of
course,
then
I
we
moved
in
I
only
do
Java,
so
I
revolved
it
with
Java
I
moved
among
DP,
and
we
put
it
opens
its
own
way.
A
So
from
the
day,
one
that
we
have
run
in
user
pilots
and
production
stuff,
we
have
been
in
kind
of
sandbox.
We
have
been
using
gears
and
cartridges.
So
from
the
day
0.
We
have
had
a
mindset
that
we
are
in
sandbox.
We
are
not
using
EMS,
we
are
using
some
kind
of
pass
or
container
so
gears,
so
our
code
code
and
the
installation
was
pretty
minimal
and
we
moved
to
open,
sits
on
line
at
the
end
of
last
year
because
at
the
New
York
Post
online,
because
the
old
one
got
end-of-life
it
the
office.
A
What
we
run
actually
my
had
read
handwritten
with
pencil
with
actually
a
true
pen
in
there
an
airplane.
So
what
we
run,
we
have
services,
one
two,
three
and
four
that
we
run.
Those
are.
We
have
made
those
services.
I
cannot
say
that
there
are
micro
services,
they
are
guide
to
micro
services.
We
could
easily
split
each
of
those
services
to
smaller
pieces,
but
we
don't
have
to
it
works.
We
have
key
clock
running
for
SSO
and
we
have
so
fancy
user
interface
with
anger
that
I
don't
even
understand
how
it
works.
A
I
do
mainly
the
backend
nowadays,
I,
don't
coat
that
mats
I
mainly
concentrate
the
operations,
part
the
not
operation
spot,
but
how
it
runs.
Do
we
get
correct
alerts,
the
matrix,
APN
and
stuff
like
that?
We
have
several
different
services,
two
red
ones
that
are
the
external:
let's
send
grid
intercom
New
Relic
a
lot
of
other
services
that
we
integrate,
because
we
don't
have
time
or
money
to
build
everything
ourselves
and
for
Amazon
s3.
We
distribute
all
public
static
content.
A
We
either
from
direct
from
App
Store
or
from
a
stirry
we
with
powerful
tree
distributing
and
then
the
manga
DP
is
not
running
an
open
system.
It's
running
on
a
MongoDB
Atlas
their
cloud
offering,
and
it
was
I
think
that
one
of
the
smartest
move
dyed
it
to
move
it
outside
open
system.
It
works
fine,
it
opens
it
even
in
opposite
to
version
of
online
and
entry.
It
worked
fine,
but
I
have
to
say
that
the
MongoDB
knows
better
than
me
how
to
run
MongoDB
and
its
own
nice
replicas.
A
That
I
can
increase
the
machine
size
if
I
can
create,
read
only
repla
cast
regions,
it's
much
easier
than
run
it
in
open
system,
and
we
have
plain
we
have
built
on
machine.
We
have
one
built
on
machine
running
on
Amazon,
running
grown
shops,
people
of
lot
of
data,
and
it
is
just
more
effective
to
run
them
in
a
VM
as
a
cron
job.
It's
a
plain
Java
process.
We
could
run
them
as
a
jobs
in
opposite
online.
It's
fine,
but
we
like
them
with
the
current
job.
A
I
have
a
couple
of
key
points
that
I
would
like
to
promote
here.
So
first
externalize
everything
that
you
can
from
your
application
to
secrets:
config
Maps,
whatever
you
have
mined
all
the
certificates,
all
the
configuration
properties
either
to
conceive
max
maps
or
to
database
so
that
you
can
have
your
container
as
one
single
container
built
for
Deb.
You
taste
it
and
then
you
deploy
at
the
same
container.
A
Everything
else
comes
from
outside
so
and
this
is
the
key
point
to
have
basically
the
immutability
of
your
containers,
and
if
you
run
your
in
opposite
on
line,
you
have
to
provide
your
own
set
Achatz.
So
if
you
use
length
encrypt,
you
will
have
only
90
day
certificate
lifetime.
You
have
to
all
also
create
and
process
how
you
externalize
your
certificates
and
how
you
redeploy
them,
and
this
is
one
good
thing
have
a
champion
in
the
house.
A
It
happened
to
me
that
in
our
company
we
have
a
four-team
develop
for
persons
in
development
team.
You
need
to
have
a
champion
in
the
company
in
the
team
that
knows
their
OpenShift.
There
is
no
point
from
the
day
of
zero
to
say
everybody
to
code.
The
operative
trainings
and
learn
this
stuff.
Have
a
champion,
distribute
the
champion
in
different
teams
so
that
the
champion
is
not
part
of
one
team,
but
it
says
the
Noles
how
you
should
do
things,
how
you
should
not
do
things.
A
It
was
easy
for
us
because
I
work
for
95
bit
offensive,
so
it
was
easy
for
me
to
be
a
champion
in
in
in
the
startup
in
game
refinery
and
that
actually
meant
that
it
took
half
a
day,
maybe
day
for
our
developers
to
figure
out
how
things
work,
how
they
can
keep
push
and
deploy.
They
didn't
have
to
learn
about
openshift,
but
they
started
learning
about
open,
sift,
bits
and
pieces
when
they
needed
to
create
a
new
service,
create
a
new
route
or
add
a
new
line
to
the
config
map.
A
So
they
learnt
the
opposite
on
the
way
they
didn't
have
a
crash
course
to
open
sift.
Now
you
have
to
do
it
like
this,
but
they
have
a
champion
to
learn
basically
holding
the
hand
on
the
road
deployment
at
delivery.
This
is
basically
the
pipeline
that
we
have.
You
build
a
believe
everything
dynamically
big
copper
production
database.
No,
no!
It
is
not
us.
This
is
what
we
have
even
that
I
see
in
my
Red
Hat
I,
see
nice
stuff
that
companies
to,
for
example,
in
our
innovation
labs.
A
There
are
awesome
pipelines
and
stuff
and
I
have
a
huge
eagerness
to
connect,
build
these
and
do
this.
But
if
you
don't
need
a
huge
pipeline
for
deployment,
are
huge
automation
pipeline?
Don't
do
it
if
everything
works,
fine
start
from
the
easy
stuff
just
used
to
be
use,
just
plain:
Softimage
Peter
get
hook
and
we
build
it
from
there.
For
now
we
don't
need
anything
else.
We
deployed
the
staging
environment
automatically
every
commit
and
then
from
there
we
have.
A
We
need
to
have
manual
QA,
because
the
user
interface
is
pretty
hard
hard
to
test
automatically,
because
you
have
to
basically
read
the
stuff
and
understand
what
the
user
interface
does
and
then,
when
it's
done
verified
we
promote
image
to
production.
You
don't
have
to
be
this
kind
of
Netflix
or
let's
say
whatever
you
better
just
do
what
you
have
to
do.
Get
your
code
running
and
start
from
there
like.
Keep
it
simple
and
don't
overthink
like
I
could,
as
I
said,
we
have
for
micro,
is
micro
services.
A
I
could
split
each
of
those
services
to
ten
different,
smaller
services,
but
I
don't
need
that.
Need
that
because
it
works,
it
would
be
nice
to
have
a
smaller
services,
but
we
have
actually
one
currently
one
active
back-end
developer
and
me
doing
light
at
ten
percent
of
the
work
managing
those
four
different
services
that
they've
written
in
Java
running
on
my
fly
and
it's
working,
fine,
so
no
need
to
split
and
the
user
interface
is
a
whole
nother
story.
It's
so
weird,
and
even
that
I
just
mentioned
that
keep
it
simple.
A
You
have
to
keep
in
mind
that
Internet
is
global,
currently
be
run
from
Europe.
Our
data
is
in
Europe,
it's
actually
running
on
the
open,
its
online
European
region.
Our
MongoDB
Atlas,
is
in
Europe.
Everything
is
in
Europe.
We
have
customers
from
the
US.
We
have
some
latency,
but
they
are
not
that
much
annoyed
it
yet.
But
we
have
to
know
that
the
code
has
to
be
an
obligation
has
to
be
so
that
we
can
easily
make
it
accessible
better
from
let's
say:
Asia,
hey
back
and
us
Oh
also
lose
some
for.
A
That
is
that
that's
why
it
was
one
good
choices
to
move
to
MongoDB
Atlas.
We
can
easily
spread
today
the
pace
to
have
read-only
replicas
on
regions.
We
can
easily
deploy
the
same
code
to
a
pack
and
us
opens
it
online
and
just
have
one
global
load
bars
and
in
front,
and
we
have
a
local
reads,
so
we
can
do
that,
but
we
haven't
done
it
yet
because
we
don't
need
so
we
only
do
what
is
necessary
to
basically
get
more
customers
and
get
more
money
and.
A
A
Let's
say
there
are:
they
are
differently
than
the
data
doc
New
Relic
do
not
raise
multiple
vendors
to
go
inside
your
applications
and
know
what's
happening
your
application,
even
that
your
content
is
a
stateless.
There
are
still
prophecies
running
in
there
and
you
need
to
know
what's
happening
in
processes.
Without
the
information
what's
happening,
you
don't
know
what
acts
are
slow.
What
you
need
to
to
make
the
application
work
better
and
also
another
one.
Is
this
basically
chat?
Oops
try
to
have
some
signal,
let's
say
pane
of
glass
that
displays
information,
alerts,
notifications.
A
We
get
a
/
slack
message,
we're
not
one
of
star
service
isn't
running
and
currently
it
Kiko
goes
t
clock
goes
down.
Then
I
have
multiple
messages
there,
because
that
indicates
it
doesn't
work.
I
know
that
there
is
a
company
that
does
this
a
lot.
They
have
a
not
slack
but
similar.
So
there
is
no
point
to
go
in
today.
Let's
say:
I,
look,
not
co-op
in
stone
line
and
shake
its.
My
application
running
I
will
see
it
from
slack
and
sometimes
I
see
it
from
slack.
A
That
ok
opens
if
Dunois
was
updated,
because
service
is
down
about
30
seconds,
because
sometimes
it
happens.
That
note
goes
down
with
geek,
lock,
databases
and
that's
bad
and
always
run
two
replicas,
always
at
least
they
are
most
often
running
on
different
nodes.
So,
during
the
updates,
you
will
have
one
replica
at
least
running,
never
run
on
single
replicas.
A
Sharing
is
caring
as
Diane
mentioned
common
roofing,
this
same
topic,
I,
have
written
a
blog
post
block
open
system.
If
you
have
something
you
can
all
reach
your
local
Red
Hat
team,
we
will
guide
you.
You
can
also
contribute
there
or
you.
Can
google
opposite
moving
online,
that's
easier
than
the
URL.