►
From YouTube: What's Next on OpenShift AMA Panel - Diane Mueller @OpenShift Commons Gathering Helsinki 2018
Description
What's Next on OpenShift AMA Panel - Diane Mueller @OpenShift Commons Gathering Helsinki 2018
Tero Ahonen, Ilka, Ed Seymour, Diane Mueller, Jeremy Brown
moderator Carol Chen
B
A
First
of
all,
as
Diane
mentioned
earlier
with
you
know,
the
cross
community
collaboration
I
want
to
thank
them
for
letting
me
have
this
chance
to
get
collaborate,
yeah
and
learn
more
about
openshift
and
also
get
to
know
the
wonderful
community
that
she
works
with.
So
thanks
for
that
and
speaking
of
community
and
because
I
also,
you
know,
do
something
similar,
and
you
mentioned
earlier
on
today
with
the
change
of
the
name
from
openshift
orange
into
okd,
and
you
wasn't
mentioned
until
Edie
came
up
and
you
know
possibly
about
it.
A
B
Well,
conceptually,
when
openshift
was
first
created,
it
was,
as
I
said
earlier,
a
Ruby
on
Rails
platform
as-a-service
using
MongoDB,
and
we
had
all
these
wonderful,
almost
proprietary
naming
conventions
of
gears
and
cartridges
and
for
the
five
been
with
Red
Hat
now
a
little
over
five
years.
So
for
the
first
couple
of
years
we
were
always
trying
to
evangelize
that
platform
as
a
service
and
then,
when
we
pivoted
to
kubernetes,
the
open
source
project
has
always
been
origin
and
will
be
pivoted.
B
We
kept
the
same
name
for
the
open
source
project
that
is
under
the
hood,
but
it
didn't
really
reflect
what
the
NIC
that
true
nature
of
the
open
source
project
was.
So
the
renaming
initiative
is
really
around
making
it
very
clear
that
our
open
source
projects
that
is
up
streamed
into
OpenShift
all
the
products
is
a
community
distribution
of
kubernetes.
So
I
think
there
was
a
little
confusion
about
that.
B
B
Okay,
D
in
engineering
team,
I
think
they're,
just
agreeing
with
me
right.
So,
yes,
I
need
that
in
okay,
D
yeah
cool
so,
but
it
really
is
all
about
making
sure
that
you're,
the
people
who
are
using
the
project
are
aware
that
they
are
getting
a
distribution
of
kubernetes
every
time
they
download
and
install
it.
So
we
are
we're
hoping
the
name
change,
isn't
too
confusing.
I,
don't
think
it
is,
and
to
make
sure
that
it's
really
not
that
confusing.
We
didn't
change
the
repo
at
all.
So
any
of
you
scripts.
B
You
know
if
your
playbooks
or
anything
that
you
wrote
or
any
download
automation
that
you've
written
should
absolutely
still
work,
as
is
so
we're
trying
just
really
to
make
it
very
clear
that
this
is
not
a
fork
of
kubernetes.
It's
not
a
platform
as
a
service
anymore.
It
is
a
distribution
of
kubernetes.
If
that
it's
clear.
A
E
Google
announced
you
know
Google
next
que
native
initiative,
which
is
basically
a
framework
to
help
build
several
s,
solutions
on
kubernetes,
so
it
uses
custom
research
definitions
to
build
the
basic.
It
grew
between
the
several
s
implementation
and
on
Copernicus
and
the
Red
Hat's
platform
functions
will
be
built
on
top
of
K
native
and
we
are
contributing
it
and.
D
A
A
Good,
so
this
is
the
first
time
I'm
actually
hearing
more
details
about
the
innovation
labs.
So
maybe
you
can
tell
us
you
mentioned
that
there
are
pop-top
labs
that
can
provide
very
similar
services.
But
what?
What
is
special
about
the
physical
labs
that
maybe
people
who,
like
me
like
to
travel,
we
want
to
go,
and-
and
you
know
how
would
you
describe
what
the
additional
stuff
you
can
provide
at
the
physical
labs.
D
A
D
By
the
way,
what's
the
secret
sauce
about
what
we
do,
it's
the
open
parts
over
the
open
innovation,
labs,
I
think
in
some
ways,
I
think
that
there's
nothing
special
about
the
the
physical
space
at
all.
But
actually
we
did
design
the
physical
spaces
with
a
lot
of
intention
about
how
we
were
using
the
space
so
and
if
you
come
and
visit
us
in
London
I
hope
some
of
you
do
come
to
London
to
visit
and
it's
kind
of
a
funky
space,
because
we
didn't
have
like
a
huge
big
room.
D
It's
quite
a
long
thin
space
and
we
use
it
for
a
lot
of
different
things.
So
we
actually
built
it
to
be
constantly
change.
So
everything
in
the
space
is
on
wheels.
So
we
even
have
lots
of
plants
I,
I
kind
of
actually
originally
wanted
a
living
wall
in
the
space,
but
our
workplace
solutions.
People
told
us
that
living
walls
are
expensive,
jeremy
and
we're
an
open-source
software
companies.
D
So
literally,
when
a
developer
wants
to
work
with
another
team,
they
can
just
unplug
roll
their
desk
somewhere
else
and
actually
plug
in
again,
and
that's
kind
of
the
principle
that
we
used.
So
that's
kind
of
cool,
also
I
should
say
if
you
come
to
us
and
we
basically
surrounded
most
of
the
space
with
writable
whiteboard
walls,
and
we
didn't
have
enough
space,
so
we've
actually
taken
over
all
the
windows,
and
we
also
have
like
post-it
notes
everywhere
and
I.
Think
that's
one
of
the
things
that
you
can
take
from
our
physical
space
and
I.
D
Think
if
you
talk
to
any
of
the
people
that
have
been
in
some
of
our
residences
who
are
here,
is
that
we
really
like
making
all
of
the
work
that
we
do
visible
and
transparent
so
that
we
can
have
a
conversation
about
the
work.
So
we
actually
use
physical
Kanban
boards
or
physical
sprint
boards
and
all
of
our
architecture
is
kind
of
in
the
open.
So
that's
some
cool
things.
I
could
talk
loads
about
it,
but
yeah
I.
B
A
Alright,
so
for
add,
you
mentioned
about,
you
know,
figuring
out
how
an
application
can
be
containerized,
but
as
Darrell
when
he
talked
about
serverless,
there
are
some
cases
where
you
don't
go
service.
Is
there
some
very
obvious,
or
you
know
clear-cut
cases,
that
you
don't
containerize
it
up?
Yeah.
F
Absolutely
I
mean
there's
so
we
we
touched
on
a
couple
of
those
in
in
the
presentation
around
you
know.
Maybe
the
architecture
isn't
quite
right
and
things
like
that,
but
you
might
have
applications
which
technically
you
could
containerize,
maybe
they're
they're
nearing
their
end
of
life
or
they,
the
actual
business
value
that
you
would
get
out
of
moving
it
into
OpenShift.
Just
doesn't
justify
the
effort
needed
to
do
that.
F
So
that's
quite
often
you
can
see
that
and
we
typically
end
up
with
we
do
things
like
Jeremy
mentioned
things
like
Pathfinder,
which
help
us
make
these
sorts
of
assessments.
As
you
look
at
a
range
of
applications,
there's
probably
some
very
quick
things
that
you
can
do
to
filter
down.
So
you
maybe
get
a
body
of
applications.
You
know
portfolio
that
we'd
then
go
and
do
run
those
assessments
on
and
then
based
on
those
who
might
decide
that
we'll
just
leave
it
alone.
F
We
might
just
be
doing
a
Rijos,
so
we
just
take
the
app
put
it
in
a
container.
We're
not
changing
the
app
at
all,
we're
just
running
it.
Now,
in
a
container
we
talk
about
replac
forming
so
say
you
wanted
to
modernize
so
you're
running
a
je
application.
It
was
on
IDE
no
je6
and
you
wanted
to
go
to
je
seven
or
eight.
Then
we
can.
We
can
do
that.
So
we
could
re
platform
and
then
there's
then
you
start
getting
into
refactoring.
F
So
this
is,
but
ideally
what
you
do
in
that
first
phase
is
to
basically
get
the
apps
onto
the
platform
and
the
development
teams
opting
that
and
the
operational
teams
adopting
adopting
that
approach
is
the
way
that
we
deliver
that
application
into
service
and
then
once
you
winter
at
that
point
you
you've
got.
You
know
what
you
might
call
a
fast,
fast-moving
monolith,
and
so
we
can
then
very
quickly
then
iterate
around
that
and
start
making
improvements
to
it
in
innovating
around
that
can.
D
The
micro
services
introduce
a
super
complex,
distributed
system
problem
for
developers
and
the
only
reason
you
would
do
that
is
where
your
monolith
cannot.
You
know,
I
think
in
the
rule
of
thumb,
is
that
and
with
the
monolith,
usually
especially
it's
basically
down
to
the
number
of
people
that
can
concurrently
work
on
that
monoliths.
At
the
same
time,
and
the
reason
you
go
micro
services
to
split
it
out,
so
more
teams
can
work
in
parallel,
but
a
lot
of
our
customers
are
doing
micro
services
with
like
a
development
team
of
six
and
I.
D
A
B
D
B
B
B
I
think
I
want.
The
oldest
story
is
probably
I,
think
some
of
the
work
that
I've
done
a
lot
of
work
in
the
early
days
of
XML
and
HTML,
and
some
of
the
xml
standards
working
on
financial
standards.
If
any
of
you
are
filing
corporate
reports
or
doing
anything
with
XBRL,
it's
not
my
fault
really
but
yeah.
So
a
lot
of
the
my
very
first
experiences
were
with
highly
regulated
industries,
creating
standards
for
that
and
doing
open
source
contributions
to
some
of
the
taxonomy
around
that
so
really
ridiculously
arcane.
Our
accounting
knowledge.
B
But
it
taught
me
a
lot
about
working
with
bringing
open
source
awareness
to
companies
that
have
a
very
restrictive
interactions
with
other
companies
and
how
to
create
collaborate.
Collaboration
in
the
financial
sector,
which
is
one
of
the
toughest
arenas
and
still
working
with
other
organization
like
fin
OS
and
banking
industry
standards
groups
open
source
groups.
Is
they
still
struggle
with
being
able
to
collaborate
in
the
open
and
I?
B
C
So
at
the
time,
I
was
working
in
the
company
that
wasn't
open
for
any
kind
of
open
source
publishing,
because
that
time
it
was
about
do
not
release
patents
or
something
it
was
heavy
time
of
fear
answer
and
then
doubt
so
contribution
at
the
time
was
inside
that
company,
so
it
was
rather
rather
big
company,
so
I
was
doing
all
kinds
of
like
Linux
and
Linux
kernel,
maintenance
and
and
and
stuff
like
that.
Distribution,
maintenance
for
the
company
and
building
community
around
that
within
the
company
company
was
at
the
best
more
than
hundred
thousand
people.
C
B
C
Some
after
that
also
similar,
it's
also
contributing
to
the
community
I
think
when
you
like,
for
example,
this
OpenStack
fin
group
that
I've
been
similar,
krob
krob,
like
not
this
big,
but
anyway
local
meetup,
I,
think
it's.
It
was
2012
or
something
when
I
started
it
so,
acting
as
a
kind
of
accelerator.
B
F
D
He's
had
a
problem
with
his
is
very
long
story,
but
he
had
a
problem
with
the
little
magnet
inside
his
KTM
that
that
basically
stops
working
in
the
engine
we
had
to
get
apart.
This
size
sent
from
Germany
and
it
took
four
or
five
weeks
and
had
to
go
through
customs,
and
in
that
time
we
ended
up
starting
a
company
just
the
way
it
happens,
and
but
basically
the
company
that
we
was
was
a
software
consultancy,
company
and
and
in
the
end
we
did
some
local
consulting
we
with
in
Cameroon,
and
then
we
had.
D
We
had
a
partner
in
Switzerland
who
gave
us
Photoshop
files
of
designs
of
websites,
and
we
created
PHP
themes
in
WordPress
and
plugins
and
stuff
to
make
the
word
prep.
The
actual
websites
websites
looked
like
the
Photoshop
and
we
employed
some
guys,
but
we
turned
our
office
into
a
co-working
space
and
that
this
is
the
real
reason
why
we
wanted
to
start
our
own
company.
D
We
felt
like
we
wanted
to
find
Cameroonian
guys
who
didn't
have
a
lot
of
access
to
seed
funding
in
capital
to
find
guys
who
were
starting
little
Internet
companies
in
Cameron,
and
we
got
them
seed
funding
and
in
order
to
actually
find
these
guys,
we
actually
started
Cameron's
first
bar
camp
and
first
tech
conference
and
for
like
developers,
so
that
was
super
cool
and
that
was
kind
of
community
and
I've
done
lots
of
contributions
to
open
source
in
minor,
tiny
ways.
I
think
most
of
my
background
is
not
Linux.
D
It's
Java,
I
worked
doing,
Java,
apps
and
but
I
think.
The
thing
that
I'm
proud
about
now
is
I
think
I
contribute
a
lot
towards
Red,
Hat's,
commercial
success
and
I
know
that
doesn't
sound
like
really
funny
in
a
kind
of
a
community
way,
but
I'm
really
motivated
by
the
idea
that
open-source
is
transforming
the
world
and
making
everywhere
better
for
Red
Hat
as
a
company
to
continue
to
exist.
We
need
to
make
money,
we
need
customers
and
I
feel
like
one
way
that
I
contribute
to
that
is.
D
E
Two
most
recent
is
actually
with
Tony
and
Diana
arranged
in
the
seventh,
but
I
haven't
done
a
code
contributions,
but
let's
say
that
sometimes
I
find
a
feature
in
our
protégés
product,
so
creating
Bugzilla
tickets,
so
informing
about
those
features
that
we
might
have
so
that
they
can
be
fixed
in
the
upstream
I.
Think
that
that's
the
most
important
how
I
have
influenced.
F
F
In
that
we
were,
we
could
build
our
application
in
a
way
that
was
right
for
that
application
and
the
application
design
and
not
be
locked
into
making
choices
that
were
there
to
drive
a
particular
proprietary
business
case
that
we
would,
if
we
were
buying
software
from
a
from
a
from
a
vendor,
and
so
I
felt
it
actually
improved
the
quality
of
our
software.
It
was
still
pretty
bad
by
using
open
source
technology.
F
I'd
say
nowadays
moving
on
actually
getting
involved
in
communities.
It
doesn't
need
it
can
be.
You
know
this
Tara
was
saying
we
can.
You
know
contributors
by
raising
issues,
or
you
know
there
may
be
like
a
Doc's
bug
or
something
like
that
and
I
mean
just
I.
Remember
the
first
time
getting
a
PR
accepted.
It's
like
wow.
This
is
really
cool.
F
I'm
really
part
of
something,
and
it
was
just
a
really
simple
thing:
it
must
have
been
like
one
line
of
code
or
something,
but
that
that
kind
of
stuff
is
is
really
great,
and
it
you
really.
It
really
feels
like
you're
you're.
You
know
you
were
actually
contributing
something
really
valuable
and
worthwhile.
So
that's
my
experience
great.
A
Question
I
actually
got
to
learn
a
lot
from
of
my
own
colleagues
and
I've
actually
heard
of
to
boost
Africa
I
just
did
well
nice
to
meet
you
in
person
and
I
agree
a
contribution
to
community.
Is
you
know
not
just
code?
You
know,
organizing
events
attending
events
telling
your
friends
about
it
translations
design,
but
there
are
many
many
ways
you
can
contribute
and
I'm
actually
going
to
abuse
my
moderator
privilege
and
tell
you
a
little
bit
from
my
point
of
view.
A
A
So
first
open
source
kind
of
experience
or
I've
used
two
things
before,
but
more
as
a
user,
but
so
that
was
that,
but
that
wasn't
as
much
of
a
community
around
it,
so
I
would
say
even
more
influence
of
stuff
that
I
did
was
after
leaving
Nokia
I
started.
Organizing
like
me,
go
meetups
and
later
joined.
A
B
B
One
of
us-
and
we
do
know,
though,
but
one
of
the
first
jobs
I
had
for
the
Python
community,
was
reviewing
all
the
licenses
in
all
of
the
read
reads
in
all
of
the
Python
libraries
for
active
States
distribution
of
Python
and
talk
about
learning
curve.
You
know
like,
and
you
know,
because
you
made
needed
to
make
sure
there
wasn't
like
a
poison
pill
kind
of
license
in
the
distribution
and
if
somebody
hadn't
snuck,
one
in
or
for
to
put
one
in.
B
So
my
big
lesson
that
I
learned
through
that
was
I,
probably
could
tell
you.
You
know
all
the
different
licenses
that
are
out
there
in
the
Python
world
or
were
about
10
years
ago,
but
also
the
one
thing
that
I
would
always
say
is
if
you're
contributing
code
back
in
there
make
sure
you
put
a
license
in
there.
B
Don't
leave
that
blank
because
that
is
almost
worse
than
putting
a
bad
license
in
or
they're
a
prohibitive
license
in
there,
because
by
not
putting
one
in
you're
causing
anyone
who
consumes
your
code
had
to
have
to
go
back
and
review
it
and
reach
out
to
you
find
you
and
get
you
to
put
it
in
or
it
breaks
their
license.
Agreements
too.
So
there's
lots
of
aspects
of
community
and
contribution
that
you
can
really
help
with.
B
D
I
make
a
comment
on
the
license
thing.
I
think
don't
just
pick.
The
most
permissive
license
be
really
thoughtful,
yes
about
what
you're
doing
when
you're
doing
the
license,
and
also
when
you
put
a
license
on
a
piece
of
work
and
it's
kind
of
if
effects
that
work,
and
if
someone
finds
that
you
had
an
old
license
and
you
changed
it.
There's
some
implications
so
and
my
personal
view
is
I
would
strongly
recommend
that
you
consider
the
copyleft
licenses
if
first
for
a
lot
of
use
cases
and
to
protect
your
work.
D
Think
about
it
like
DJ's.
If
you
don't
mind
that
another
DJ
remixes
your
work
and
gets
a
record
hit
and
makes
all
the
money
from
it
then
go
for
it
and
put
a
permissive
license
on
it.
But
if
you
want
to
somehow
make
sure
that
that
DJ,
who
makes
a
piece
of
music
from
your
work,
you
can
then
remix
their
work
and
use
their
work.
To
make
other
hits
then
make
sure
you
put
a
copyleft
license
on
it
and
I
I
think
and
there's
a
little
bit
of
an
interesting
Redis
story.
That's
just
kicked
off!
D
So
that's.
What
can
happen
if
you
don't
quite
pick
the
right
license,
so
yeah
just
think
about
it,
like
in
the
concept
of
DJ's
remix
in
music,
if
you're,
okay,
that
someone
can
take
a
piece
of
your
work
and
make
a
proprietary,
and
you
don't
have
access
to
that
work
anymore.
Think
about
copyleft
is
that
you
can
all
you
if
they
make
a
fork
and
it's
better
than
what
you
did.
You
can
always
pull
it
back
into
your
work,
whereas
if
it's
permissive
you
it,
the
remix
ability
disappears
yep,
just
a
thought.
E
If
you
want
to
contribute,
feel
free
to
catch
us
from
the
meetup
to
come
and
have
an
open
it
meter,
if
you
have
a
team,
you
have
a
venue,
you
have
free
beer,
that's
fine!
We
can
help
you.
We
can
help.
You
find
an
speaker.
If
you
have
a
topic,
you
can
find
speakers.
So
if
you
want
to
basically
build
this
openness,
comic
community
in
Finland,
yeah,
yeah.
B
Would
also
add,
along
with
the
meetup
stuff,
is
we
do
on
open
chef,
Commons
tons
of
open
shift,
Commons
briefings
like
two
to
three
a
week
and
the
cigs
do
usually
when
the
cigs
happen.
I
make
them
do
at
least
two
mini
talks
within
each
cig
meeting
on
different
topics,
so
there's
lots
of
content
out
there,
but
what
I'm
always
interested
in
is
hearing
what
you
want
to
hear
about.
B
So,
if
there's
a
topic
that
we
didn't
cover
today,
that
you
want
to
hear
more
about,
could
you
let
us
know
over
beer
or
something
like
that
or
if
there's
a
topic
that
you
want
to
talk
about,
that
there's
some
open
source
project
that
you
want
to.
You
know
hear
about
on
patife,
ik,
pontificate
about
or
promote,
please
let
us
know
we
really
I,
always
joke
I,
don't
like
to
hear
the
sound
of
my
own
voice
anymore.
B
I
mean
I
really
want
to
hear
what
what's
going
on
out
there
and
we've
been
talking
a
lot
of
on
the
sidelines
today
over
coffee
at
different
times
about
trying
to
figure
out
what
the
next
big
thing
is,
and
a
couple
of
things
have
happened
to
two
things:
this
one
because
OpenShift
and
Red
Hat
is
doing
so
much
work
on
kubernetes.
We
get.
We
really
get
a
lot
of
insight
into
where
kubernetes
is
going
and
stuff.
B
So
you
know
I'm
gonna,
try
and
do
a
little
research
about
you
know
what
the
network
effect
is
where
the
next
hotness
is
in
the
kubernetes
world,
and
it's
very
hard
to
predict
that.
But
I
also
think
that
there's
quite
quite
a
bit
of
it.
One
of
the
things
that's
been
wonderful
about
being
part
of
the
kubernetes.
There
is
sometimes
I
get
to
be
one
of
the
reviewers
for
the
call
for
papers
for
a
coop,
con
and
I.
Think
kook
on
this
time
had
over
6,000
submissions
right.
B
B
But
if
you
get
asked
to
be
the
reviewer
of
a
conference
volunteer
and
say
yes,
because
you
can't
believe
how
much
you
learn
about
what
the
new
things
are
or
what
people
want
to
talk
about,
and
our
passionate
about
and
I
have
learned
so
much
by
just
looking
at
the
agendas
for
conferences
and
reviewing
people's
papers
about
what's
coming
down
the
pike.
But
it's
you
guys
out
there
that
are
really
gonna
help
us
understand
where
we
should
be
going
with
OpenShift
and
with
kubernetes
and
with
all
of
the
other
projects
at
Red
Hat.
B
B
B
If
you've
got
a
production
case
study-
and
you
want
to
talk
about
your
journey
like
the
folks
did
earlier
today-
please
let
me
know
because
again,
I
don't
I
mean
I,
probably
looked
like
I
I
love
the
sound
of
my
own
voice,
because
I
talk
so
damn
much,
but
I
really
want
to
hear
what
yeah
and
have
you
share
your
stories
so
that
everybody
learns
from
your
lessons
and
your
war
stories
and
your
successes.
So
that's
really
key
to
keeping
the
conversations
and
the
stories
flowing.
I.
A
Really
like
yokas
drawings
and
also
his
voice
so
like
to
ask
you
a
question:
you
talked
about
like
being
like
Kimi
räikkönen,
where
you
know
you
focus
on
stuff
and
don't
worry
about
the
things
happening
behind
you
and
gain
speed,
but
occasionally
something
you
know:
Matt
you
might
be
blindsided
and
something
hits
you
or
something.
How
do
you
do
with
that?
How
can
you
prevent
it
or
how
do
you
recover
from
it?
I
think.
C
G
F
Would
add
whatever
whatever
approach
you'd
adopt?
You
need
to
be
looking
at
an
agile
approach
where
you,
where
you're,
able
to
assess
what
you,
what
you're
doing
in
the
in
the
you
know
the
direction
that
you're
going
a
regular
short-term
intervals,
and
so,
if
the
unexpected
happens,
then
you're
able
to
adapt,
adapt
your
plans
and
change
and
reconfigure
around
that.
D
It's
really
funny
that
you
mentioned
openness
is
the
place
to
start
with
some
of
this,
because
when
we've
been
what
we've
been
learning
is
we've
worked
with
customers
in
their
transformations?
Is
that
and
we
talked
about
the
pillars
of
open
organizations,
but
we
found
that
transparency
is
actually
the
first
step
in
transforming
organizations
just
sharing
more
widely.
The
work
that
you're
doing
and
making
your
work
visible
is
really
powerful.
Part
of
that
so
I
agree.
It's
a
really
interesting.
It's.