►
Description
OpenShift Commons Gathering in Seattle on Nov 7, 2016 "Members Talk back!" panel moderated by Brian Gracely (CloudCast) with panelists from Amadeus, CrunchyData, Unvia, Arctiq.ca
A
A
So,
thank
you
all
for
staying
for
the
afternoon.
We
are
closer
to
beer
than
we
are
breakfast,
so
we're
making
progress
real,
quick.
So
again,
thank
you
all
for
staying
I
know
it's
tough
to
be
here.
For
the
whole
day.
Are
we
having
a
good
times?
It's
been
useful
so
far,
good,
yeah,
okay,
real
quick,
give
Diana
round
of
applause.
Putting
this
thing
on
is
a
huge.
A
So
so,
we've
had
a
lot
of
really
good
technical
panels.
So
far
we
talked
a
lot
about
why
people
are
building
with
their
building
the
thought
process
behind
it.
The
engineering
that
went
on
behind
it
the
sessions
gonna
be
a
little
bit
different.
We're
gonna
do
a
panel
session,
but
we're
going
to
talk
a
little
bit
about
you
know
all
of
you
here,
there's
a
reason.
A
So
there's
a
part
of
what
you're
trying
to
get
out
of
all
this
beyond
the
technology
that
is,
do
I
want
to
be
part
of
this
community
right
and
this
community
being
a
subset
or
a
superset
of
the
cube
community.
So
we
want
to
talk
a
little
bit
about
what
that
means
in
this
session
and
so
first
I'm
going
to
introduce
everybody
on
the
panel.
In
fact,
why
don't
you
guys
go
ahead
and
introduce
you?
Cuz
you'll
do
a
better
job
than
I
am
but
go
ahead
and
introduce
you
we
put
this
panel
together.
A
We
wanted
to
have
sort
of
end-user
customers
and
sort
of
unique
end-user
customers
that
are
helping
to
contribute.
We
have
folks
on
the
panel
from
some
of
the
technology
ecosystem
partners
and
also
people
that
are
in
sort
of
the
vsi
world,
so
you're
seeing
sort
of
the
the
ecosystem
the
supply
chain,
if
you
will
for
doing
this
so
first
off,
go
ahead.
So.
B
Hi
everybody,
so
my
name
is
Christopher
chess
I
walk
with
the
menu,
so
first
I
apologize
for
my
fresh
French
accent,
but
you
would
have
to
bear
with
it.
So
amaris
is
an
IT
company,
providing
you
know,
IT
services
for
the
travel
industry,
like
airline
booking
systems,
reservation
systems,
and
we
do.
We
are
in
the
process
of
migrating
all
our
applications
to
open
shift
open
ship
running
on
steak
and-
and
we
are
in
partnership
with
right
at
two
to
work
on
the
opencv
three
very
intense
eerie
echo
right.
C
D
Chase
Stewart
with
Arctic,
we
are
more
in
the
SI
space.
We're
actually,
probably
one
of
the
newer
sort
of
members
of
the
Commons
groups
were
the
newbies.
Our
focus
typically
is
around
consulting
services
with
red
hot
products.
So
really
what
we
want
to
do
is
help
take
openshift
and
satellite
and
cloud
forms
and
all
the
upstream
components
and
help
our
customers
sort
of
have
a
great
experience
with
that.
But
at
the
same
time
we've
been
surprising
surprises.
D
We
started
that
most
of
our
customer
base
has
ended
up
being
sort
of
enterprise-grade
customers,
large
financial
firms,
things
like
that
which,
when
you
try
to
take
their
standards
and
take
new
technology
and
try
to
marry
them
together,
there's
a
bit
of
glue
that
needs
to
be
done,
and
so
really
our
focus
is
helping
them
step
ahead,
while
making
that
sort
of
process
smoother
and
sort
of
helping
them
develop.
Some
of
the
glue.
E
I'm
rob
lowe
loaned
I'm
general
manager
of
univ
anab,
ops,
Christophe
apologized
for
his
French
accent,
I
apologize
for
my
Canadian
one.
Hopefully
you
can
understand
me,
but
we
have
a
essentially
schedule
and
policy
system
for
Cooper
Nettie's,
so
it
sits
on
top
of
open
shift
or
any
of
the
Cooper
Nettie's
distros
and
provide
sort
of
advanced
workload,
management.
A
Cool
gentleman,
thank
you
for
being
here.
So
you
know,
one
of
the
tricks
is
when
you,
when
you
wake
up
in
the
morning-
and
you
look
at
the
schedule
and
you
realize
that
you
have
to
go
after
Kelsey,
there's
a
little
bit
of
anxiety
that
you
takes
on
and
you
wonder
how
am
I
going
to
keep
people's
attention
right?
I
was
a
little
bit
jealous
that
Alex
was
able
to
pull
out
Kelsey
into
a
session.
So
I
thought
all
right.
I
got
a
bunch
of
questions
prepared,
but
how
do
I
make
them
interesting?
A
Or
you
can
advance
it
if
you
want
to
it's
a
bad
approach,
all
right,
so
yeah
don't
try
what
move
on
alright.
So,
let's
start
with
this:
let's
start
with
this
real
simple:
what's
your
all
part
of
the
open
shift
ecosystem
in
some
way
right,
whether
it's
new
to
the
community,
whether
it's
been
working
on
it
for
a
long
time,
what's
working
in
anybody
jump
in?
But
what's
what
do
you
find?
That's
working
so
far,
what
wait
at
the
end
of
the
day
you
go,
this
is
making
my
life
easier.
D
Just
keep
it
easy.
Sorry,
it's
as
a
newcomer
to
the
sort
of
to
the
group.
Really.
This
is
about
connecting
people
with
other
people,
and
so
she's
been
fantastic
to
both
help
connect
us
with
other
organizations
that
might
be
able
to
help
us
out
as
well
as
connecting
them
with
us,
where
we
can
be
of
assistance
as
well,
or
you
know,
asking
us
to
participate
in
things
like
this
or
lead
events
or
do
demonstrations,
and
things
like
that.
So
for
me,
the
community
is
about
educating
and
she's
helping
us.
You
know,
be
smarter.
C
Yeah
I
definitely
would
agree
the
people
at
Red
Hat
really
sought
out
to
partner
with
us
and
bring
us
into
getting
the
latest
information.
The
best
sources
of
information
within
the
like
for
me,
the
engineering
group
and
having
real
direct
access
and
really
the
openness
of
that
given
tech
process,
has
been
a
good
experience.
I
think
that
works
very
well
elaborate.
C
For
me,
dealing
with
like
persistence,
issues
for
database
containers
has
been
a
big
deal
and
you
know
being
able
to
directly
interact
with
like
Cooper
Nettie's
or
openshift
developer
who's
working.
You
know,
upstream
on
that
particular
issue.
It
has
really
been
a
lifesaver
in
a
lot
of
cases
and
helping
me
figure
out
what
I
can
do
with
in
the
technical
space.
So
you.
C
B
So
yeah
for
us
it's
a
bit
the
same
I
mean
the
collaboration
we
have
some
people
in
that
are
embedded
in
the
open
chief
development
teams
and
the
communities
community
as
well
and
being
able
to
work
with
them
on
a
daily
basis.
To
you
know,
to
make
the
deploy
the
project
progress,
improve
and
so
on.
It
has
been
really
great.
It's
working
very
well
for
us,
no.
A
No,
you
guys
are
a
little
bit
unique
for
folks
that
don't
know
you're,
essentially
the
backbone
of
the
travel
industry
for
Europe
and
a
lot
of
the
world
I
read
recently.
Your
your
load
is
up
about
six
thousand
percent
about
6,000
times
what
it
used
to
be
in
terms
of
people
searching
and
so
forth.
Yeah,
something
like
that
rough
rough
numbers
talk
a
little
bit
about.
You
are
not
just
consuming
the
software
as
if
we
used
to
with
with
vendor
sort
of
the
vendor
customer
relationship.
You're,
now
writing
code
being
part
of
that
community.
A
B
A
A
lot
of
communities
Kelsey
just
got
done
talking
about
those
guys,
have
a
lot
of
choices.
Yeah,
there's
a
lot
of
open
communities.
There's
a
lot
of
you
know
opportunities
for
you
to
say:
how
do
we
want
to
go
to
market?
Who
do
we
want
to
work
with
whoa?
Why
are
you
here
today?
Why
would
you
choose
this
community,
the
Cuban,
a
DS
community,
the
open
shift
community
versus
other
communities,
because
your
time
is
valuable.
C
C
Now
it's
really
proven
out
to
be
a
good,
a
good
bet
and
the
way
that
community
worked
all
along
gave
us
more
of
a
comfort
level
that
hey
this
is
going
to
be
successful
and
we
want
to
be
part
of
this
and
we
think
our
customers
are
going
to
be
successful
in
this
platform.
So
for
us
it
was
about
a
two
and
a
half
year.
You
know,
let's,
let's
watch
this
happen
and
and
it
did
happen
in
the
way
we
we
wanted
it
to
turn
out
of
it.
A
Yeah
now
clarify
something
you
guys
are
fundamentally
in
the
persistent
data
you
know
persist,
stateful
application
space.
You
know
we
hear
a
lot
about
12
factor,
applications
about
all
these
sort
of
things
like
what
what
you
said,
your
customers
are
driving
you
towards
this.
What
about
their
applications?
And
this
sort
of
hybrid
platform
thing
makes
sense
for
them.
C
Customers
are
in
at
least
some
of
the
customers.
On
my
mind.
Right
now
are
kind
of
they
saw
a
lot
of
benefit
in
deploying
web
applications
in
a
container
environment
and
that's
really
easily
demonstrated.
But
a
lot
of
these
customers
have
very
large
database
deployments,
not
so
much
in
maybe
the
size
of
the
actual
data,
but
some
of
these
customers
might
have
you
know,
50
test
environments,
50
QA
environments,
and
they
may
need
to
spin
these
up
very
rapidly.
C
A
B
From
an
abortion
perspective
being
able
to
manage
your
database,
like
you
manage
your
application
is
something
that
is
very
interesting.
We
are
not
there
yet
I
mean
first,
the
database
is
still
outside
of
the
open
chief
cluster,
but
it's
something
we
are
walking
as
well
with
red
at
because
we
are
using
couchbase
the
test
earlier
and
we
are
working
with
you
guys
to
try
to
integrate
that
into
into
open
shift,
because
it
does
make
sense.
We
want
to
be
able
to
manage
everything
the
same
way.
It
makes
operation
much
easier
for
us
right.
A
Right
so
Rob
you're
in
the
sort
of
technology
vendor
space
same
as
a
lot
of
the
folks
here,
one
of
the
challenges
with
platforms
is
platforms
in
some
parts
of
the
industry
tend
to
be
a
winner-take-all
type
of
thing
where
you
start
with
something,
and
you
continue
to
add
features,
and
you
continue
to
add
features
in
the
ecosystem
sort
of
goes.
What
about
me
like?
E
Great
question
I
think
applicable
for
us,
because
we
see
a
lot
of
customers.
We
go
into
them.
They're
they're,
not
green
fields
throughout
their
brownfields,
it's
messy
and
nasty,
and
the
first
thing
they
come
up
with
was
what
about
my
all
my
batch
workloads.
I've
got
this.
You
know
2000
node
cluster
running
batch
work
and
got
some
spark
apps
over
here
and
Hadoop
workloads
and
I've
got
my
container
stuff
and
it's
not
not
a
real,
clean,
cloud.com
type
scenario.
So
you've
got
to
integrate
all
these
things
and
I.
E
Think
that's
where
you
know
a
lot
of
the
enterprise
vendors
like
red
hat
and
ourselves
that
have
that
experience
on
sort
of
pulling
this
brownfield
together
and
making
everything
work
together.
Now,
all
day
long
we
deal
with
that.
Enterprise
complexity,
whether
it's,
whether
it's
trying
to
integrate
mace
those
frameworks
or
batch
workloads,
are
all
these
non
containerized
things
that
get
really
complicated.
A
So
shape
talk
about
you
guys
get
probably
as
close
to
any
customer
is
anyway,
when
you're
an
SI
when
you're
you
know
quote-unquote
partnered
in
the
channel.
You
live
with
these
customers
every
single
day
like
what
is
their
journey?
Look
like
I
mean
what
is
realistically.
What's
it
looking
like
for
people,
because,
it's
great
to
say,
hey
new
shiny
thing
comes
out,
you
deploy
it
person's
a
rock
star,
everybody
gets
promoted,
you
know
billion-dollar
growth,
and
but
what
is
it?
What's
it
really
looking
like
for
customers?
What
are
you
seeing
their
bottlenecks?
D
D
Self-Service
was
something
that
was
very
difficult
for
them
to
win
in
the
virtual
machine
world
and
I
should
cabbie
this
all
by
saying.
I
am
from
Canada
sore
adoption
of
of
large-scale
clustering
systems
and
self-service
and
containers
has
actually
been
a
little
more
laggard
than
the
United
States.
So
we
get
introduced
to
a
group
and
we
say
new
shiny
thing
come
check
it
out,
do
a
POC
and
the
developer.
Experience
is
the
thing
that
that
latch
onto
it
is
wow
man.
I
could
really
spin
this
up
and
get
going
very,
very
quickly.
D
Wonderful,
that's
not
the
end
of
the
journey.
That's
just
the
bait
and
switch
right
like
that's,
get
them
hooked
on
it.
They
want
to
do
the
product
and
then
you're
going
to
have
to
go
and
implement,
which
usually
means
nine
or
ten
different
groups
of
people
that
they
haven't
figured
out
how
to
work
together
with.
So
this
is
the
traditional
DevOps
problem.
This
isn't
the
the
tooling
problem
of
something
like
openshift.
It's
helping
them
out
that
process.
We've
got
sort
of
a
couple
of
the
customer.
D
The
room
I've
worked
with
typically
takes
them
about
a
year
where
they
start
to
say
new
shiny
thing,
POC
develop
a
project
around
it
and
then
wrangle,
ops
and
developers
and
network
guys
and
everything
else
for
the
next
few
weeks.
Right,
I'm
working
with
one
very
large
tellico
is
I
met
them
in
September
they'll,
be
ready
to
start
deploying
in
December
and
they've
had
an
OpenStack
platform
available
for
that
entire
time.
D
Politics
right,
it
still
tends
to
happen
with
most
of
our
customers,
but
at
the
end
of
the
year,
once
that
developer,
goat
can
go
and
do
a
demo
and
show
live
that
they
just
pushed
a
new
piece
of
code
and
it
went
into
production
state,
that's
the
beginning
of
the
next
journey,
and
then
so.
The
beginning
of
the
next
journey
for
us
is
to
say
we
typically
give
them
a
little
bit
of
guidance
and
help
along
the
way
it's
check
back
every
few
months.
D
D
That's
the
biggest
question
that
we
have
today
is
like
how
do
I
see
what's
going
on
in
the
environment,
which
is
still
difficult,
and
so
then
that
next
journey
for
the
next
year
is
always
productive,
like
they
can
always
get
something
out
at
the
end
of
the
day
they
get
their
minimum
viable
product,
but
then
they
start
developing
on
the
next
thing
and
to
me,
that's
the
fun
part,
because
I
want
to
learn
whether
they're
going
and
help
them
out
along
that
journey,
because
that's
business
value.
That's
not
it's
on
a
technology
problem.
A
Right
so
there's
a
large
part
of
this.
This
is,
you
know
own.
Your
change.
You've
got
on
it,
but
any
any
tips
that
you
found
to
get
I.
Don't
know
a
group
to
showcase
to
somebody
hey.
This
is
this
is
worth
your
time,
even
though
you
know
the
numbers
might
not
be
simple.
You
know
like
like
telling
somebody
they're
gonna
become
more
agile,
sounds
great
until
you
have
to
put
in
a
spreadsheet
and
have
to
somehow
justify
it
any
tips
from
from
any
of
you
as
to
how
you
sold
that
internally,
I
would.
D
Say
the
lucky
thing
right
now
is
that,
if
you're
going
from
top
down
there's
somebody's
job
is
to
make
that
happen
right
now,
it's
on
their
MBO
list,
so
figure
out
whose
job
that
is
to
say.
I
need
to
get
my
teams
working
better
and
faster
together
that
gets
paid
on
that
and
then
take
each
one
of
the
groups
and
show
them
one
demo
make
sure
that
demo
is
what's
in
it
for
them.
How
is
ops
better?
How
is
development
better?
How
do
I
get
the
product
out
at
the
end
of
the
day?
B
What
is
important
is
to
stop
the
small
project
internally
and
not
to
try
to
address
everything
at
once.
I
mean
really
start
with
the
standalone
application.
That
is
already
more
or
less
ready
to
be
cloud.
You
know
cloud-ready
and
and
that's
the
way
we
did
it.
You
know
we're
really
starting
with
a
small
application,
smaller
application
from
our
second
showcase,
how
how
better
it
is
compared
to
you
know
what
we
have
a
county
so.
A
Are
you
going
to
jump
in
on
okay
good,
so
this
is
a
this
community-based
event.
It's
a
platform
based
event.
What
do
you?
What
do
you
guys
wish
we
were
doing
better
right,
so
you
guys
have
had
a
chance
to
sort
of.
This
is
great.
This
is
positive.
What
we
need
to
do
better
as
a
as
a
community
as
a
core
set
of
technologies
that
you're
hearing
the
market-
that's
just
like.
Why
aren't
you
guys
adding
this,
because
it's
the
most
obvious
problem?
We
have
what's
what
we
gotta
get
better
at
I.
B
C
I
think,
based
on
the
customers,
I've
worked
with
the
documentation
and
the
number
of
examples
and
the
ease
of
installation
all
those
really
greatly
improved
in
the
last
two
years,
no
question,
but
they
still
can
be.
Definitely
those
are
target
opportunities,
because
a
lot
of
people
will
just
say.
Well,
how
do
I
install
open
shift
and
you're
like
oh
okay,
so
there's
there's
a
side
of
it
before
you
can
even
sell
them
on
the
advantages
of
the
technology.
There's
this
her
love.
C
How
does
how
do
you
get
them
the
right
information,
and
how
do
you
make
the
installation
process
for
them,
something
that
they
can
deal
with?
You
see
I
know,
so
they
don't
just
totally
right
off
the
the
technology
without
so
I
would
always
say
the
just
continued
improvement
on
the
documentation,
and
example
sets,
and
things
like
that
would
be.
You
know
hugely
received
by
anybody
using
this
yeah.
Let.
A
Me
ask
the
audience
a
question
for
those
of
you
that
are
evaluating.
Openshift
have
played
with
it.
How
many
of
you
know
of
this
thing
called
OC
cluster
up
good,
it's?
Okay,
it's
better!
Okay!
So
for
those
of
you
that
don't
know
there,
you
know
goober
Nettie's,
fundamentally,
wasn't
the
easiest
thing
in
the
world
to
get
working
open
ship
wasn't
the
easiest
thing
I'm
will
to
get
working
and
in
classic
technology
fashion
you
can
go
and
search
the
blog's.
A
We
now
have
about
four
or
five
different
ways
that
you
can
have
one
command
to
bring
things
up.
I
will
see
cluster
up
being
the
simplest
one.
It's
going
to
bring
up
an
environment
right
on
your
laptop.
You
don't
have
to
mess
around
with
a
with
a
vm
or
anything.
It's
gonna
bring
the
whole
thing
up.
You
can
run
demonstrations
and
stuff
like
that,
but
there's
a
whole
bunch
of
others
taking
advantage
of
what's
going
on
with
cube
admin,
mini
cube,
mini
shift
bunch
of
things
like
that.
A
Excuse
me
so
we
talked
you
know
we're
going
to
we're
going
to
be
at
cube
gone
tomorrow,
we're
going
to
see
Cooper
Nettie's,
we're
gonna,
see
Prometheus.
Obviously,
docker
is
a
big
piece
of
this
ecosystem.
What
else
do
you
wish
from
a
you
know,
open
projects
that
you
know
are
out
there
was
more
tightly
brought
into
this
or
what
would
you
know
what's
on
your
list
of
things,
you'd
like
to
see
us
bring
in
into
the
community,
so.
D
So
you
know
I've
tested
out,
sistex
got
a
great
cloud
product,
but
they
also
have
an
open
source
tool,
something
along
those
lines
to
say
and
to
be
more
prescriptive
of
this
is
now
the
best
way
to
monitor.
Openshift,
I
think,
is
one
of
the
biggest
most
common
questions
that
I
have
and
we
can
say
I
go
to
nagios
and
I
can
build
a
bunch
of
you
know
plugins
to
go.
Do
that,
but
I
think
weíll
openshift
strives
to
be
open.
Sometimes
it
strives
to
be
to
open.
D
B
I
100%
agree:
it's
basically
our
main
pinpoint
right
now,
I
mean
we.
We
have
to
get
in
correction
with
the
pen
shift
in
the
next
I.
Don't
know
six
months
and
right
now
we
are
still
struggling
at
knowing
okay.
What
type
of
monitoring
you
know
platform
we
should
be
putting
in
place.
If
we
were
running
on
the
on
Google,
we
we
could
use
stackdriver
or
this
kind
of
stuff,
but
here
we
are
running
on
a
wall
in
premise.
Openstack
and
we
don't
know,
we
don't
know,
I
mean
city
could
be
an
option.
A
Your
look
at
so
this
isn't
so
much
a
request
for
we
want
you
to
only
ship
us,
the
Cystic
New
Relic
agent,
but
we
want
you
to
give
us
some
sort
of
guidance
and
if
that
guidance
is
around
ocular
or
prometheus
or
whatever
just
make
their
lives
better,
yeah,
okay,
all
right,
fair
enough.
What
else
anything
else
on
your
list
of
areas
that
you
want
to
say
mean
it
was?
It
was
the
big
data
area
that
we
talked
about.
B
Agencies
for
me,
not
specifically
big
data
but
ma
really
the
how
to
manage
the
test
alia.
So
you
know
the
persistency.
What
how
do
you
manage
the
past
and
see
that's
something
that
I
don't
think
anybody
has
really
started
out
right
now
and
that's
also
a
missing
piece.
As
I
said,
we
we
are
looking
to
try
to
manage
everything.
The
same
way
on
an
open
suppressor
and
the
best
eastern
sea
layer
is
one
of
the
big
question
right
now
so
right
that
would
be
the
next.
C
Yeah
totally
agree
on
the
persistence.
I
think
it's
improved
a
lot
in
two
years,
but
you
know
things
like
being
able
to
define
what
kind
of
storage
you
want
just
from
a
quality
perspective,
making
it
more
transparent
to
the
user
so
that
they
don't
have
to
worry
so
much
about
the
underlying
back-end
storage
and
then
also
you
know
things
like
if
you
want
to
have
data
replicated
in
your
environment.
That
would
be
great.
Just
have
that
baked
in
a
transparent
to
the
user.
Yeah.
D
D
Switch
a
little
bit
from
the
OP
side
to
the
to
the
user
side.
One
of
the
conversations
I
was
actually
having
last
night
was
surrounding.
Maybe
we
so
the
developer
experience
is
great,
a
developer
can
go
in
and
do
something.
That's
not
really
the
same
experience
that
we're
matching
up
with
the
application,
Omer
or
the
team
to
say
it.
What
do
I
have?