►
From YouTube: CNCF Storage WG Meeting - 2019-01-23
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
A
A
B
A
What
we
had
discussed
when
we
were
sessions
and
shengyin
Seattle
was
that
we
were
going
to
lose
look
at
options
to
discuss
real
life
use
cases,
preferably
from
end
users,
so
that
we
can.
We
can
put
together
some
more
useful
patterns
in
terms
of
how
people
consume
story,
read
something
with
some
read
life
with
some
real-life
examples
and
I
wanted
to
poll
the
audience
to
kind
of
see
if
there
were
any
strong
references
on
the
next
items
to
do
sort
of
which
patterns
or
the
choose
cases
to
to
look
at.
A
Bearing
in
mind
that
the
white
paper
covered
a
large
variety
of
options
covering
sort
of
the
different
types
of
volumes
coverings
of
the
plot
devices
and
Frances
turns
etc,
as
well
as
the
API
driven
methods
of
accessing
storage.
So
things
like
key
value,
store
essence
and
object
stores,
as
well
as
databases
which
we
could
virtually
could
with.
So
service
there's
a
huge
variety
of
things
we
could.
We
could
cover
and
I
was
wondering
if
what
what
your
thoughts
were
so
kind
of
open
it
up
to
the
core.
C
Hey
Alex
I
was
wondering:
should
we
put
together
some
kind
of
survey
and
ask
a
user
questions
just
based
on
the
white
paper
like
what
type
of
store
today
using
and
what's
the
reason,
big
choose
those.
D
B
I
think,
broadly
speaking,
we
have
the
end
user,
bunch
of
people
and
contributors
and
there's
obviously
some
a
lot
of
overlap
between
the
two
groups,
but
we
can
probably
reach
out
to
them
somewhat
separately
from
each
other.
You
know
the
end
users
tend
to
hang
out
in
some
places
and
the
contributors
hang
out
in
other
places
and
I
think
both
of
the
inputs
are
probably
valuable,
but
we
need
to
just
make
sure
we
understand
whose
input
we're
reading.
When
we
read
the
input,
it's
a
quite
distinct
groups
of
good.
A
B
You
know
just
the
structure
of
such
a
questionnaire
and
you
know
they're
a
bunch
of
introductory
questions.
That
kind
of
all
questionnaires
need
to
have.
Who
are
you?
Do
you
consider
yourself
an
end
user
or
contributor?
How
big
are
your
cluster?
Is
blah
blah
blah,
so
we
could
perhaps
take
that
as
a
as
a
starting
point-
and
you
know
replace
the
long
term
support
specific
questions
with
storage,
specific
questions,
but
there's
a
fair
amount
of
that
that
we
could
reuse.
That's
really
useful.
Can
we
get
hold
of
that
questionnaire?
B
A
Right
so
I
mean
that
that
sounds
like
a
good
thing
out:
I'm
hoping
that's
when
the
end
user
sign
things.
If
you
know,
if
you
guys
can
join
the
engines,
are
regular
monthly.
A
B
Yeah
totally
agreed
one
other
brief
point
on
the
topic
of
questionnaires
and
versions
of
the
paper.
We
have
a
kind
of
a
logical
one
called
a
deadline,
but
a
potentially
logical
endpoint,
which
is
coupon
Europe,
which
is
made
may
eccentric
or,
and
so
we
should
probably
figure
out
what
we're
gonna
have
done
by
mid-may.
You
know
that
could
range
from
getting
a
link
from
the
from
the
questionnaire
and
produce
the
second
version
of
the
white
paper
based
on
that
input
and
presenting
it
is
keep
on
Europe
or
just
the
former
or
any
you
know.
D
C
B
Right
yeah,
so
I'm
gonna
send
those
in
anyway
I've
drafted
them
and
nearly
sent
them
in
this
week,
but
but
they're
fairly
generic.
It's
like
you
know
where
the
working
group
will
tell
you
what
we've
been
doing
and
we'll
give
you
an
update
on
the
other
and
and
closer
to
the
time.
We
can.
You
know
reword
that.
D
A
B
I
think
that
sounds
reasonable.
Something
else
to
bear
in
mind
is
that
the
couple
of
things
to
bear
in
mind
one
is
that
the
CNC
of
collections
are
going
on
right
now
and
so
I
may
or
may
not
be
on
the
TRC
next
time
around.
Who
knows,
in
which
case
my
role
in
this
group
is
maybe
you
know.
I
could
continue
a
lot
but
currently
I'm
here,
as
as
the
TRC
representative,
if
I'm
not
on
the
TRC,
that
wouldn't
make
sense,
so
we
should
sort
of
plan,
as
that
may
or
may
not
be
hearing.
B
Secondly,
the
TOC
is
in
the
process
of
Alex
knows
about
this,
about
formalizing
a
cig
structure,
and
they
will
almost
definitely
be
a
cig
storage
for
the
CN
CF
and
only
speaking
its
responsibilities
will
be.
You
know,
looking
after
the
health
of
all
storage
related
projects
in
the
CN
CF,
as
well
as
identifying
gaps
in
our
storage
portfolio,
and
you
know
finding
additional
CN,
CF
storage
projects,
etcetera,
etcetera.
So
that's
going
to
be,
you
know
significant
amount
of
work
for
somebody.
B
B
A
So
that's
a
very
good
point
enough
was
parking,
my
sort
of
reasoning
for
keeping
the
contents
to
be
smaller
blocks
that
we
can
do
a
good,
more
autonomously,
because
I
think
one
of
the
things
as
part
of
the
evolution
of
the
mistake
will
be
that
we'll
probably
need
to
put
some
focus
into
both
soliciting
information
from
from
different
projects,
and
potentially
we
might
be
given.
Tasks
from
peers
need
to
actually
review
potential
projects
right.
So
we
need
to.
We
need
to
factor
that
into
and.
B
I
must
say
if
I
were
to
have
to
make
a
choice
between
making
significant
progress
towards
a
storage
sink
bye-bye
I
think
I
mean
you
know
a
group
that
looks
after
all,
the
storage,
related
stuff
and
cncn
and
publishing
a
second
paper
of
some
sort
along
the
lines
of
what
you
described.
I
would
say:
the
former
is
more
important,
probably
than
the
latter.
You
know
nobody's
been
screaming
for
this.
B
A
I
think
that's
good
guidance.
How
about
how
about
this?
If
we
put
together
a
little
bit,
if
we
put
together
a
survey
or
questionnaire-
and
maybe
it's
in
the
music
sessions
as
our
next
steps,
at
least
we
can
get
sort
of
you
know
quantitative
and
qualitative
data
as
to
what
the
inducer
is
they're
interested
in
and
yeah
should
also
be.
You
know,
that's
a
useful
data
point
for
for
a
Content
breaker,
but
it's
also
a
very
useful
data
point
one.
What
maybe
we
can
shape
the
priorities
of
the
arc?
A
A
We
Pro
may
need
somebody
to
reshape
our
questionnaire
into
a
more
of
a
storage
type
thing,
and
then
so
somebody
needs
to
take
that
action
and,
if
possible,
I'm
happy
to
take
on
the
action
too,
to
work
with
Cheryl
to
get
a
session
with
with
the
end
users
and
maybe
plan
at
that
agenda.
With
a
couple
of
slides
together
to
facilitate
the
discussion.