►
From YouTube: CNCF Storage WG Meeting - 2019-05-08
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
B
A
B
We
obviously
we
obviously
wanted
to
get
feedback
from
the
user
community
which
we'll
be
getting
through
the
survey.
But
in
the
meantime,
I
just
want
to
pull
this
group
to
see
if
there
were
any
specific
use
cases
that
you
felt
or
imagine.
If
you
have
the
resources
or
some
basic
information
to
to
be
able
to
move
forward
as
well.
So
we
could
have
a
list
of
those
for
consideration.
B
B
So
I'll
I'll
take
off
this
concert
so
that
the
idea
for
the
use
case
since
myself
so
I
had
an
idea
that
you
know
even
the
priorities
of
the
end
users
assigned
I
think
it
would
be
useful
to
cover
a
use
case
documents
for
some
common
options
for
for
volumes,
so
sort
of
covering
the
ephemeral
volumes.
The
the
local
in
support
that's
been
recently
introduced,
incriminate
ease
and
persistent
storage
from
when
using
a
storage
provider
to
cover.
B
You
know
it's
on
some
different
use
cases
or
different
applications
that
kind
of
fit
to
those
three
types
of
volumes,
because
this
is
quite
possibly
a
fairly
common
question.
We
get
asked
at
storage
arrests,
but
I'm
I'm
open
to
sort
of
hear
comments
from
anybody
else
on
the
team
as
to
whether
they
think
this
is
a
good
idea
or
whether
they
would.
Rather,
we
did
something
else.
I.
C
B
A
C
A
B
Yeah
there
was
a
blog
post
with
the
with
the
feature
release.
I
was
I,
was
thinking,
I
was
thinking
more
something
along
the
lines
of
you
know.
This
is
this.
Is
you
know
this
is
these
are
some
examples
of
what
you
could
use
the
ephemeral
storage
for
these
design,
examples
for
the
local
or
the
roblox
store,
and
these
are
some
examples
of
running
into
many
at
once.
You
know
resistant
system
or
service
to
kind
of
help.
People
with
just
general
guidance
on
these
things.
A
B
A
C
Think
there
are
some
blog
posts,
have
more
use
case
cut
like,
for
example,
the
local
boarding
I
think
there
is
a
pretty
good
blog,
covering
use
case
actually
from
I.
Think
ubers
using
that
or
something
but
for
the
roblox
for
the
blog
post
doesn't
really
cover
clear
use
case.
So
I
think
that
one
maybe
we
can
see
if
we
can.
You
know,
add
more
to
that.
A
Be
used
for
something,
okay,
no,
that
makes
sense
and
actually
I,
had
a
similar
thought.
Strug
comment
when
Alex
was
soliciting
agenda
items
yesterday,
I
think
this
word
use
cases
kind
of
become
overloaded
in
the
sense
that,
and
maybe
we
need
to
come
up
with
a
new
with
different
words,
but
in
my
mind,
there's,
like
specific
user
has
specific.
You
know
project
where
they
did
something
and
other
people
might
be
interested
in
understanding
like
what
exactly
they
did
and
why
they
did
it
and
whether
it
succeeded,
etc.
A
Now,
I
don't
know
if
we
call
that
thing
a
use
case
or
something
else.
My
sense
is
that
we
probably
need
to
call
that
something
else,
and
then
there
is,
you
know
in
a
more
generic
sense
like
what
are
the
categories
of
use
case
for
this
feature,
what
kinds
of
things?
What
are
the
properties
that
you're
looking
for
you
know
a
more
generic
kind
of
description
of
something
and,
and
that
also
I
think
currently
gets
referred
to
as
a
use
case,
and
maybe
that's
confusing.
B
So,
for
example,
a
classic
example
of
this
is
the
official
HCV
operator
actually
uses
ephemeral
storage.
So
if
all
the
nodes
have
a
Paris
flight
failure
at
the
same
time,
you
will
actually
just
lose
all
the
few
dates
up,
because
that's
the
way
the
operators,
design
and
I
think
it
would
have.
It
would
benefit
a
lot
of
people
to
avoid
these
sort
of
stumbling
blocks,
including
sort
of
adopt
some
of
these
kinds
of
technologies
quicker.
B
If
we
just
said
these
are
the
types
of
volumes
that
you
can
have
just
because
you're
you
have
a
PV
from
from
from
CSI
driver
or
a
native
driver
doesn't
mean
it's
pretty
persistent.
Doesn't
mean
these
sort
of
things?
These
are
some
of
the
categories
and
therefore
you
know
use
them
accordingly.
Kind
of
thing
and
I
was
I
was
thinking
about
this.
In
terms
of
you
know,
short-circuiting
some
of
the
pain
points
that
users
are
finding
when
they're
using
the
official
repos
yeah.
A
Okay,
that
that
makes
sense
and
I
think
that
that
kind
of
stuff
falls
very
squarely
in
in
our
set
of
responsibilities.
The
sense
that
we,
you
know
across
multiple
projects
and
across
multiple
yeah
things.
We
need
to
sort
of
provide
a
comprehensive
understanding
to
you.
The
end
users,
however,
when
it
comes
to
a
specific
feature:
release,
for
example,
local
ephemeral
volumes
for
kubernetes
or
whatever
one
would
hope
that
those
are
described
by
the
kubernetes
project
and
in
cases
where
they're,
not
where
we
don't
think
they
are
sufficiently
described.
A
B
A
A
B
This
came
up,
for
example,
and
the
other
thing
when
I
was
discussing
this
at
the
Vita,
the
actual
hell
charts
today
installs
its
converts.
It
runs
up
it's
easy
on
ephemeral
storage,
which
basically
means
when
the
pods
dies.
That
instance
of
fcd
goes
away.
No,
no.
You
know
if
you're
running
as
in
as
many
users,
it's
a
just
three
notes
or
something
like
that.
It's
quite
easy
to
get
into
a
situation
where
you
lose
quorum
or
you
lose
all
of
the
three
parts
same
time
and
that
basically
means
that
there's
no
data
to
recover
it.
B
A
Understand
so
your
your
distinction
was
between
ephemeral
versus
local
rather
than
local
versus
remote
casillases.
Oh
I,
understand
sorry.
I
wasn't
actually
aware
that
there
was
a
distinction.
Okay,
that
makes
sense.
I
was
just
the
the
reason
I
asked
was
was
there
is
a
perception
that
storing
at
CD
data
on
remote
discs
is
a
good
idea
and
and
that
it's
a
bad
idea
to
use
local
volumes
and
I'm,
not
sure
that
that
does
sufficient.
A
B
Cool
all
right,
so
so,
in
that
case,
I
can
I
can
potentially
maybe
sort
of
for
the
for
the
document
outline
together
to
cover
together
this
and
then
maybe
we
can
work
collaboratively
to
split
up
different
sections
of
the
document.
Hopefully
this
can
be
a
nice
short
document
that
we
can
turn
around
that
we
can
turn
around
quickly.
It's
so
going
to
be
something
as
neatly
as
the
white
paper.
A
B
A
Wish,
okay
for
a
very
specific
kind
of
pair
of
alternatives?
Yes,
okay,
that
makes
sense.
Yeah
cuz
the
the
whitepaper,
tended
to
sort
of
try
and
sketch
all
the
possible
alternatives
and
and
pros
and
cons
of
each
which,
which
tends
to
be
a
much
more
difficult
thing
to
give
a
clear
answer
to
so
it
tends
to
be
begging
in
a
lot
of
areas
behind
a
section,
so
you,
okay,
that
makes
sense.
C
B
D
B
D
A
A
You
know
a
uniform
commodity
hardware
with
a
converged
approach
and
it's
sort
of
more
flexible,
but
on
the
other
hand,
your
capacity,
provisioning
and
performance
impact
between
your
computers
and
you
or
storage
loads
gets
mixed
up
so
which,
which
I
think
was
a
very
good
summary
of
the
my
understanding
of
the
pros
and
cons.
So
I
guess
what
I'm
wondering
is.
What
more
do
we
think
we
need
to
add
to
that?
It's
not!
It's
not
obvious
to
me
that
there's
anything!
That's
not
answered
by
those
questions,
but
maybe
you
have
other
ideas
as.
D
B
B
B
So,
for
example,
professional
reasons
are
one
thing:
you
know
where
that,
where
perhaps
they're
looking
for
say,
optimized
storage,
notes
versus
optimized,
compute
notes,
but
other
reasons
which
are
fairly
more
common
are
actually
operational
and
and
sort
of
day
two
operations
type
thing
so,
for
example,
and
they
might
have
a
high
rate
of
change
under
their
compute
notes,
especially
if
they're
running
with
managed
services
in
the
cloud
environments,
they
may
want
on
their
storage
notes,
for
example,
I.
Don't
know
whether
that
actually
merits
and
it's
a
paper
or
an
entire
documents.
B
C
The
otherwise
the
roadblock
that
I
mentioned
I
think
it
would
be
good
to
see,
and
it's
still
relatively
new
I'd
like
to
see
who
is
using
it,
and
you
know
if
they
are.
They
think
this
is
something
they
need
that
maybe
helps
them
improve
performance
versus
the
the
file
system
mode,
but
this
I
think
I
need
some
user
input.
B
B
C
B
C
C
Don't
think
it's
I,
don't
think
this
is
it
we
just
say
the
general.
You
know
blocks.
Are
you
using
blocks
through
the
system
or
not?
Because
this
is
our
specific?
This
is
like
a
one
mode
in
kubernetes
right,
so
the
for
the
for
the
PVC
right.
So
so
we
don't
have
something
that's
specific
in
our
server,
yet
our
service
kind
of
a
general.
C
A
So
all
the
CNC
of
storage
projects
just
checking
in
with
them,
making
sure
that
they're
happy
and
healthy
and
and
whether
there's
anything
that
needs
to
be
brought
to
the
attention
of
the
TOC
and
then
the
other
area
is
identifying
what
we
believe
to
be
gaps
in
the
storage
portfolio
of
of
the
CNC
F.
So
I,
don't
think
either
of
them
are
like
super
burnin
urgent,
like
need
to
be
done
in
the
next
couple
of
weeks.
B
B
One
other
one
other
project
or
initiative
that
I
thought
might
be
helpful,
but
I
am
looking
for
guidance
here,
because
I
do
understand
that
this
could
be
potentially
controversial.
So.
B
I'd
be
interested
in
putting
together
some
guidance
for
how
we
actually
measure
some
of
the
different
attributes
that
we
defined
in
the
white
paper.
So,
for
example,
you
know
something
like
performance
might
be
a
good
place
to
start
with
something
that's
quantifiable,
but,
as
we
all
know,
benchmarking
is
notoriously
complex
and
subjective,
but
I
was
kind
of
wondering
whether
it
would
be
useful
to
put
together.
You
know
something
like
a
sample
set
of
Eider
benchmarks
for
tooling
or
or
even
just
maybe
a
standardized
sort
of
automation
framework
for
some
of
this
stuff
suspects.
B
End
users
can
easily
use
that
framework
as
a
starting
point
to
say
for
when
they're,
comparing
different
cloud
providers
or
different
storage
systems
within
their
environments-
and
you
know
the
idea
being
as
we
started
performance
for
perhaps
move
it
to
other
areas
where
we
have,
for
example,
things
like
availability
or
something
like
that.
So,
for
example,
I
know
the
open,
EDX
guys
have
have
a
framework
which
which
perhaps
could
fit
the
bill
in
terms
of
things,
sort
of
chaos.
A
Together,
for
instance,
I
think,
I
think
the
general
principle
is
very
good,
I
think
having
a
place
where
users
can
go
and
find
a
set
of
tools
that
we
believe
to
be
useful
for
this
kind
of
stuff,
and
maybe
even
some
performance
robot
results
that
we've
done
on
you
know
either
CN
CF
projects
or
general
other
projects.
Other
I
mean
in
the
extreme,
possibly
even
products,
although
that
gets
even
more
controversial.
My
reservation
is
whether
we
have
the
bandwidth
and
the
longevity
II.
A
You
know,
I,
don't
want
us
to
build
tools
that
we
don't
maintain
over
time.
So
if
we're
gonna
build
tools,
we
need
to
actually
sign
up
for
maintaining
them
properly
over
time
and
I.
Think
as
a
thing,
we
have
necessarily
the
infrastructure
to
do
that
properly
and
the
same
goes
for
performance.
You
know
if
we
publish
performance
figures
for
version
X
of
product
Y
or
project
Z.
A
B
So
I
I
completely
agree
and
just
to
be
clear,
I'm
not
proposing
that
we
he
got
me
the
sort
of
published
results.
I
don't
get
a
date
very
quickly,
and
it's
apart
from
the
fact
that
you
know
we
don't
really
want
to
get
into
sort
of
a
comparison
of
products
ourselves.
Well
on
what
I'm
talking
more
about?
Is
this
kind
of
providing
the
same
say?
B
A
That
makes
sense.
I
would
propose
that
as
a
first
step,
we
we
just
surveyed
the
landscape
of
available
tools
and
that
can
be
used.
These
kind
of
measurements
and
perhaps
publish
a
white
paper.
Just
saying
you
know
these
are
the
ones
we
looked
at.
These
are
the
pros
and
cons
of
the
various
tools.
These
ones
measure
these
things
and
these
other
ones
measure
these
other
things
and
here's
you
know
a
couple
of
sample
runs,
maybe
of
some
of
them
just
so
that
you
know.
A
The
the
idea
of
building
automation
implies
that
we
maintain
that
stuff
and
keep
it
working,
and
these
things
you
know,
presumably
that
automation
is
going
to
rely
on
underlying
tools
which
change
over
time
and
you
know,
may
or
may
not
run
on
particular
operating
system
platforms,
etc,
and
that's
where
I
don't
want
us
to
like
implicitly
sign
up
to
maintain
a
bunch
of
software
that
we
don't
actually
have
the
people
bandwidth
to
do
properly.
A.
D
B
D
B
That
would
be
great
I,
so
I
like
the
idea
of
stopping
small.
We
can
start
small
with
with
a
survey
of
some
of
the
tools
and
provide
some
service
guidance
on
which
tools
to
use
and
then
I
guess,
depending
on
the
uptake
we
get
from
the
community,
we
can.
We
can
make
a
course,
so
we'll
only
wants
to
take
that
further.
I
I
completely
sort
of
agree
with
you
Quentin.
B
We
should
not
must
not
bite
off
more
than
we
can
chew,
but
I
kind
of
feel
that,
with
potentially
dozens
of
storage,
vendors
and
companies
who
are
sort
of
sponsoring
this
and
could
be
interested
in
the
sig
we
might
actually
get.
We
might
actually
get
a
bit
of
a
community
around
this,
because
I
suspect
that
this
is
a
common
problem
for
end-users
and
the
sort
of
storage
community
alike.
A
B
I
was
just
saying:
I
think
we
may
find
stats.
That's
so
there's
a
bit
of
a
drive
from
boats
and
users
and
the
defenders
and
the
community
error,
and
the
sake
that
that
we
may
find
is
there's
quite
a
bit
of
I've
taken
this.
So
I
like
the
idea
of
just
starting
small,
with
the
put
in
a
dock,
with
the
landscape
of
the
available
tools
and
they're
kind
of
taking
it
further
based
on
uptick.
A
Yeah
I,
totally
agree
and
and
I
think
that
the
general
principle
of
making
real
hard
data
easily
accessible
to
users
is
is
very
I,
strongly
support
that
because
I
think,
as
you
point
out,
you
know
we
wave
our
hands
and
we
say
that
you
know
these
kind
of
stores
are
faster
than
these
kind
of
stores
are
more
consistent
or
whatever,
but
I.
Don't
think
people
appreciate
quite
how
many
orders
of
magnitude
difference.
A
They're
arbitrary,
some
of
these
things
and
when,
when
we
sort
of
make
statements
that,
when
you
use
the
wrong
stack
of
storage
technologies
or
not
necessarily
the
wrong
one,
but
if
you
use
a
particular
combination
of
layers
in
your
storage
system,
this
is
the
result
in
terms
of
performance
or
consistency
or
whatever
the
property
might
be.
And-
and
it
is
like
you
know,
a
X
number
of
orders
of
magnitude
different
than
than
a
different
approach
and
I.
Think
people
always
appreciate
quite
how
big
the
differences
are.