►
Description
OpenShift User Panel (Game Refinery, Elisa, Suomen Asiakastieto) moderated by Diane Mueller (Red Hat)
OpenShift Commons Gathering Helsinki 2018
https://commons.openshift.org/gatherings/Helsinki_2018.html
A
A
Who
are
one
who
is
a
pseudo
gamer
game
refinery
on
his
off
time,
doing
work
at
game
refinery,
but
also
a
red
hat
or
so
there's
a
little
expertise
here
beyond
just
production
use
as
well,
but
you
this
is
your
opportunity
to
ask
them
anything
about
their
current
production,
their
future
and
all
of
that
and
and
I
know
so.
I
have
a
couple
of
questions
that
I
wanted
to
ask.
A
After
listening
to
their
talks
today
and
the
first
one
from
auntie,
it's
an
auntie
like
aunt,
okay,
auntie,
can
you
tell
us
a
little
bit
about
what's
in
the
application
stack
under
Sun
the?
So
what
are
you
you
want
to
recruit
people?
So
you
know
what
cool
technology
are
you
trying
to
run
there
to
do
all
that
aí
and
aí.
B
C
B
C
A
You
talk
about
that.
We've
made
a
number
of
offenses
if
those
of
you
who
don't
know
coop
flow.
The
tensorflow
community,
along
with
the
kubernetes
community,
have
created
another
open
source
upstream
project
to
make
tensorflow
and
other
not
just
tensorflow,
but
other
things
run
very
nicely
for
the
ml
stacks.
C
A
E
With
right,
so
it's
design
yeah
good
so
are
like
I
mentioned.
Our
IT
is
a
total
of
30
people
just
about
and
the
guys
doing,
OpenShift,
but
by
a
significant
effort.
Well,
it's
me
and
Jenny
over
there
she's,
the
UPS
guy
I'm,
the
dev
guy,
so
yeah,
basically
guys
so
since
Auntie
did
his
shameless
plug
I'm
gonna
do
mine.
If
you
want
to
do
some
cool
stuff,
then
this.
A
Is
what
happens
at
community
events
shameless
recruitment,
all
right,
which
is
quite
okay
but
but
I?
Think
one
of
the
things
that
you've
just
made
this
equity
acquisition
or
merge
with
UC
and
I
heard
the
word
mainframe
used,
there's
going
to
be
a
lot
of
educational
challenges
and
bringing
people
up
to
speed
on
what
containers
are.
What
what
are
your
plans
for?
You
know
trying
to
educate
that
whole
crew
of
new
new
folks
and
convert
them
to
cloud
native
container
enthusiasts,
yeah.
E
Well,
that's
the
question:
isn't
it
well,
let's
put
it
this
way:
they're,
pretty
tired
of
the
whole
mainframe
thing
themselves,
so
they're
looking
for
for
alternatives
and
I
think
having
the
best
solution
is
to
it's
the
first
part
and
then
is
about
I,
guess
selling
it
to
them
as
well.
We
have
to
get
our
own
stuff
together
properly
first
and
then
we
can
roll
out,
but
I
can
definitely
say.
They're
they've
been
interested
because
there's
all
these
things
I've
been
able
to
promise
already
so
yeah
time.
Little
shall
I
guess.
A
Yeah
so
I'll
put
a
shameless
plug
in
for
learning,
openshift,
calm
and
the
stuff
that
we're
doing
at
cata
Kota.
Just
please
take
advantage
of
that
and
people
can
learn.
If
there's
any
of
these
new
topics,
pretty
much.
There's
a
learning
session
with
online
access
to
deploying
and
testing
with
clarin
openshift
comm,
which
has
been
really
good
and
also
mini
shift,
if
you
haven't
heard
of
that
as
well,
is
a
great
way
to
deploy
open
shift
locally
and
get
started
and
have
some
hands-on
experience.
F
D
E
I
mean
I,
don't
think
there
was
a
huge
difference.
I
mean
it
was
pretty
easy
because
we
actually
migrated
the
testing
environment
for
the
DDP
our
service,
and
it
was
pretty
painless
actually
to
get
it
running
so
I
mean
I.
Guess
you
have
to
be
a
little
more
careful
with
the
ambien
one,
because
if
you,
if
you
make
a
route
to
your
program,
then
it's
in
the
internet.
C
A
D
Actually,
we
don't
need
to
externalize
anything,
but
we
can
basically
run
what
ever
we
want.
An
open
shift
nowadays,
maybe
not
functions
yet,
but
sterilized
functions
will
be
in
multi-tenant
Mourinho
pest
online
soon.
But
if
we
see
that
something
is
better
run
elsewhere,
then
we
move
it
like
the
manga
DP.
We
saw
that
we
get
the
better
performance,
it's
easy
to
manage.
We
get,
let's
say
like
a
new
lyric
integration
from
there.
We
because
a
better
authentication
and
there
then
it's
just
for
the
business
it's
better
on
elsewhere.
A
D
B
E
A
G
I'm
Elena
question
for
arrow:
how
do
you
prioritize
picking
the
applications
that
are
we
done
into
cloud
native
environment?
Do
pick
the
low-hanging
fruits
from
the
point
of
view
that
it
is
easy
to
migrate
into
cloud
native,
or
do
you
want
to
have
operator
operator
operations
slowed
pickup
from
checking
up
from
the
operators
for
them
to
focus
on
other
things?
Do.
E
Yes,
so
we've
I
think
we're
going
with
generating
more
revenue
like
first,
that's
the
I
think
that's
the
arrow
head
like
what
what
sort
of
new
business
can
OpenShift
give
us,
rather
than
going
for
the
cost
savings.
That
was
the
question
right
so
I'm
doing
24/7
for
some
services
will
we'll
bring
that
in
and
being
able
to
respond
to
heavy
loads.
Very
quickly
is
probably
something
I'm.
We've
lost
one
or
two
like
a
stockman
hold
by
that
type
of
thing.
E
A
F
F
A
B
The
task
was
rather
difficult.
Yes,
it's
not
well.
Maybe
I
should
say
that
at
first
we
even
didn't
run
any
Red
Hat
version.
We
installed
the
community
version
and
well
that
took
a
lot
of
kind
of
understanding
of
what
the
components
do
and
what
they
can
used
for
and
how
they
should
be
configured
and
lots
of
trial
and
error.
Well,
luckily,
since
we
have
our
own
data
centers,
we
have
quite
a
good
amount
of
hardware
readily
available.
B
So
we
ended
up
kind
of
well
guessing
a
good
set
up
of
hardware
that
that
we
could
try
on
well,
we
cut
it
up
and
running,
but
pretty
soon
it
was
kind
of
clear
that
that
maybe
the
supported
version
would
work
better
for
our
environment,
because
there
would
be
a
need
for
operations
capability
and
yeah.
Well,
the
community
version
isn't
well
documented,
so
it's
really
hard
to
know
what
to
do
to
maintain
it
and
keep
it
running
properly.
B
So
I,
don't
I,
don't
have
an
estimate
here
it
how
long
or
how
much
time
or
how
much
effort
it
took.
But
I
could
say
that
it
was
significant,
but
actually
it
was
good
to
kind
of
do.
The
exercise
runs
with
the
Community
Edition,
in
my
opinion.
So
now
we
have
a
couple
of
guys
that
are
really
skilled
at
well.
A
So,
in
that
experience
with
OpenStack
and
using
the
Community
Edition,
you
mentioned
that
you
had
contributed
to
the
upstream
and
your
talk
about
that
and
I'm.
Supposing
that
your
experience
is
well,
OpenStack
allowed
you
to
contribute
back
to
the
OpenStack
community
feedback,
probably
on
their
lack
of
documentation
or
other
things.
But
can
you
talk
a
little
bit
about
because
you've
also
opens
open
sourced
your
load,
balancer
integration
with
open
shift?
Thank
you
very
much.
A
B
In
my
opinion,
that's
still
a
work
in
progress,
so
some
not
all
kind
of
are
working
with
the
open
source
model
we
are
trying
towards
it
and
I
guess.
The
DevOps
team
is
leading
that
way
in
that
area,
because
we
work
a
lot
with
open
source
technologies.
So
so
that
way,
it
became
natural
for
us
to
kind
of
run
or
lead
the
way
I
should
also,
by
the
way
mention
that
we
have
contributed
to
to
cover
kubernetes
and
open
shipped
as
well.
So
we
have
collaborated
with
the
upstream
directly
yeah.
A
And
I
think
that's
one
of
the
points
that
I'm
trying
trying
to
make
as
well
is
that
it's
not
just
open
shift
that
we
want
you
to
do.
You've,
contributed
to
OpenStack
and
kubernetes
and
lots
of
other
places
and
all
of
that
gets
fed
into
you
know
we
all
benefit
from
that,
but
I'm
curious,
culturally,
like
how
you
worked
with
management
to
get
them
to
allow
you
to
open
source,
say
your
load.
A
B
A
On
my
to
my
direction
so
yeah,
so
so,
I
get
to
work
with
all
different
market
sectors
and
not
all
of
them
are
Linux
kernel
developers
and
so
in
highly
regulated
industries
like
finance
or
banking
and
stuff.
Like
that,
there's
a
lot
of
issues
in
terms
of
them
being
allowed
to
disclose
what
they're,
working
on
and
thisis
do
you
have
have
you
been
contributing
back
arrow,
no.
A
A
This
is
me
encouraging
you,
but
I'm
also
gonna
say
that
contributions
come
in
lots
of
forms,
your
questions
or
contributions,
your
stories
or
contributions,
documentation
and
support.
Changing
your
grammar
checking
all
kinds
of
ways
you
can
contribute
back
to
communities.
It's
not
just
code
contributions
or
open
sourcing
projects.
So
I
really
encourage
you
to
to
think
about
when
you're
you're
worried
about
whether
or
not
you're
making
a
code
contribution
or
you
were
going
to
be
a
committer
or
something
like
that,
make
smaller
steps.
A
D
H
So
question
so
a
question
actually
20
about
Aliza
clusters.
So
how
much
you
using
were
like
well
normal
workload
compared
to
workload
which
needs
to
be
optimized
for
the
hardware,
so
like
high
packet
network,
transmission
or
I,
don't
know
some
hardware
accelerators
or
some
like
protected
from
noisy
neighbors
and
overall,
how
much
of
your
clusters
are
on
top
of
OpenStack
and
how
much
bare
metal,
okay.
B
B
We
have
been
looking
into
GPU
processing
for
the
AI
training
cycles,
but
that's
not
done
in
production
yet,
but
it's
been
planned,
but
that's
pretty
much
it.
We
do
have
a
separate
cloud
environment
for
the
telco
stuff,
that's
more
like
networking
heavy
or
needs
certain
latency
requirements,
and
that's
probably
I
think
it's
using
DP
DK
for
the
acceleration,
but
I'm
not
too
familiar
with
the
technology
that
it's
running
on
currently.
A
So
I'm
just
I
feel
like
I'm,
adding
all
the
bookmarks
here.
So
if
you're
looking
up
to
for
information
about
open
shift
on
OpenStack
on
bare
metal,
there's
a
great
number
of
blog
posts
and
videos
and
briefings
by
a
gentleman
from
Red
Hat
called
Jeremy
eater
Edie
er
he's
done
some
great
work
on
performance
and
Ramon
Alvarez
from
the
OpenStack
team
at
Red.
Hat
does
has
a
great
briefing
on
the
open
shift,
Commons
briefings,
which
is
again
on
YouTube
at
our
H
open
shift.
A
If
you,
google,
either
their
names
you'll
find
lots
of
information
on
the
bare
metal
question
that
you've
asked
so
I'm,
not
the
expert
on
it
anyway.
So
taro
you've
got
a
day,
job
yep,
it's
at
Red
Hat.
We
know
he's
a
Red
Hat
er.
How
do
you
manage
switching
gears
between
your
day
job
and
the
game
refinery
in
the
evening?
And
where
do
you
find
time
to
do
all
of
that?
I
travel.
D
A
So
it's
interesting
because
what
we
have
up
here
is
we
have
an
open,
stack,
open,
shifter.
We
have
an
online
open
shifter
and
we
have
an
on-prem
open,
shifter
and
we
have
almost
like
is
none
of
you
are
using
dedicated
yet
okay,
so
we've
pretty
much
got
one
of
each
of
the
variations
that
you
could
think
about.
Deploying
open
shift
on
and
I'm
wondering
from
your
perspective,
because
you're
such
a
smaller
thing,
the
benefits
of
running
on
open
shift
online
and
having
that
operations
team
behind
you.
How
that's
played
out
for
you
I.
D
Would
say
that
it
makes
things
a
lot
easier.
I
know
that,
because
of
my
data,
I
know
what
it
needs
to
manage
an
open
sift.
So
we
don't
have
time
for
that
and
we,
since
we
started
from
the
day
one,
we
started
from
open
sift,
so
we
don't
have
any
requirements
that
we
need.
Our
own
open,
CV
need
cluster
admin
rights.
We
are
happy
with
the
sandbox
that
we
have,
so
we
are
not
even
thinking
about
having
our
own
cluster,
because
we
don't
basically
have
ops
if
you
don't
just
deploy
containers
around
the
application.
E
A
So
if
you
could,
just
if
you
could
just
pause
pause
for
one
second
before
you
ask
your
question,
a
woman
just
walked
in
the
back
of
the
room
who
we
have
to
say
thank
you
to
before
she
takes
off
and
goes
and
organizes
another
one
Tania
repo
here
is
has
been
the
main
organizer
behind
this
whole
day
for
the
past
three
months.
While
you
are
all
on
vacation,
let
me
just
tell
you
fins
take
vacations,
but
Tania
really.
Thank
you
very
much
before
you
take
off.
Thank
you
all
right.
So.
B
Well,
our
office,
it
is
installed
on
top
of
OpenStack,
and
some
workloads
do
actually
run
on
OpenStack
alone,
so
we
don't
run
them
in
OpenShift.
That's
basically
because
we
started
with
the
OpenStack
only
version
and
openshift
came
along
later,
so
some
workloads
were
set
up
in
OpenStack
and
we
haven't
migrated
or
don't
see
the
need
to
migrate.
Everything
or
oh
thanks
all.
A
I
Yes,
I'm,
you
sure
the
last
one
to
ask
I
wonder
when
you
started
this
use
of
open
shift,
and
you
discussed
with
your
with
your
people
on
how
they
will
work
in
in
the
future
and
you,
of
course,
it
makes
some
change
into
the
how
the
developers
have
to
behave
and
how
maybe
business
have
to
go
on.
Did
you
encounter
some
kind
of
new
issues
like
oh,
we
have
been
doing
this
like
this
before.
Why
should
we
now
suddenly
change,
or
was
that
already
clear
for
everybody?
I
B
Yeah
yeah,
obviously,
people
have
been
used
to
working
in
a
certain
way
and
with
the
changing
cloud,
environment
and
cloud-based
kind
of
production
model,
there
have
been
some
some
kind
of
issues
that
people
think
the
cloud
works
in
a
certain
way.
I
mean
then
doesn't,
and
they
feel
that
this
is
wrong
and
and
not
easy,
and
and
all
that,
that's
why?
Actually
we
do
have
the
DevOps
team
at,
and
so
we
try
our
best
to
help
with
these
sort
of
pitfalls
before
they
happen.
B
D
D
Sorry
in
what
fly
in
local
machine
tail
and
run
their
HTTP
different
local
machines
once
it
goes
to
get
then
its
container,
so
developers
can
do
whatever
they
want.
As
long
as
it's
compiles
doing
the
build.
So
it's
easy.
So
there
is
no
cultural.
Like
mismatch
that
now
we
are
the
open
for
openshift,
no
we're
just
writing
code.
We
are
not
developing
an
open
system.
E
First
I
think
there's
definitely
two
things
here.
First
of
all,
I
was
talking
about
how
we're
gonna
make
it
incremental
and
easy
to
get
into
the
openshift
I
think
that's
one
critical
part,
and
the
second
is
what
teller
was
talking
about
in
his
presentation
about
the
app
being
the
the
champions
having
the
champions.
I,
think
I,
guess
I'm,
the
dev
channel
of
our
company
and
I
think
our
organization
is
sufficiently
small
to
the
point
where
I
can
just
go
and
talk
to
the
people.
E
A
Training
champions
and
hiring
you'll
be
doing
so.
That's
all
the
time
we
have
for
AMA.
Thank
you
for
your
questions.
Much
appreciated
and
we're
going
to
now
thank
our
panelists
for
sharing
their
stories
with
us
and
their
production
use
cases
and
ask
them
to
keep
coming
back
and
as
they
change
and
grow
and
and
add
new
things
into
their
projects,
we'll
have
them
at
meetups
and
upcoming
events,
and
we
hope
to
hear
from
all
of
you
as
well
in
the
future
and
so
that
you'll
share
your
stories
too.
So,
thank
you
and
thank
you.