►
From YouTube: CNCF SIG Storage 2020-05-27
Description
CNCF SIG Storage 2020-05-27
A
A
A
A
B
B
B
B
B
B
A
A
A
C
C
C
C
C
C
A
A
A
A
A
A
A
A
A
So
I
posted
I
posted
the
link
to
the
to
the
agenda
in
the
chat
window
in
the
zoom
chat
window.
I
guess
there
are.
There
are
just
a
few
things
we'd
like
to
cover
off
today,
so
the
storage
landscape
documents
I
sent
out
an
email
asking
for
asking
for
comments,
has
been
brilliant
sisters
being
50,
odd
comments.
So
far
last
in
the
last
day,
hopefully.
A
We
are
going
to
prepare
a
quick
summary
to
share
I.
Think
it's
fair
to
say,
though,
and
Jing
it
would
be
lovely
if
you
could
weigh
in
here,
but
I
think
it's
fair
to
say
that
the
the
survey
wasn't
wasn't
horribly
conclusive
in
the
sense
that
it
doesn't
pinpoint.
You
know,
specific
pain
points
what
it.
A
What
it
did
kind
of
tell
us
is
that
there
is
a
broad
level
of
different
understanding
about
cloud
native
storage
and
that
people
are
using
or
end
users
are
using
a
wide
variety
of
solutions,
whether
it's
it's
on
Prem
and
in
the
client.
But
what
it
kind
of
did
highlights,
though,
was
that
you
know
the
need
for
information,
and
the
need
for
best
practices
is
is,
is
definitely
kind
of
implied
by
some
of
the
answers
within
within
the
survey
sharing
I.
E
A
A
Moving
on,
oh
sorry,
we're
there
any
questions
on
the
on
the
survey
at
this
stage
you,
okay,
so
moving
on.
The
next
item
was
the
performance
and
benchmarking
document,
so
I've
put
a
little
bit
of
work
to
tidy
it
up
and
to
include
some
of
the
feedback
items
that
people
had
committed
to.
The
document
I
think
it's
beginning
to
take
shape,
but
the
one.
The
one
item
which
is
which
is
still
pending,
are
the
benchmark
example.
So
it's
you
know
some
examples
of
how
to
run
volume.
D
A
A
A
All
right
going
once
going
twice
in
that
case,
what
I'll
suggest
is
I'll
I'll,
finish
off,
tidying
up
the
draft
and
send
out
an
email
to
the
mailing
list
asking
for
for
for
further
comments
or
or
for
further
help.
If,
if
that's
possible,
and
then
we
can
try
and
close
this
off,
because
we've
we've
had
this
open
for
a
while.
Now
the
next
item,
which
which
I'm
hoping
to.
A
A
We
we
had
an
action
item
that
Aaron
Lewis
and
myself
we're
going
to
meet,
to
discuss
the
use
case
templates
and
for
backgrounds.
The
use
case
templates
that
we
were
putting
together
stemmed
as
a
follow
up
from
the
landscape
documents.
So
we
kind
of
thought
once
the
landscape
document
is
out
there.
The
next
step
would
be
to
kind
of
take
it
one
step
further
and
document
some
use
cases
and
best
practice
for
different
use
cases
that
can
be
applied
to
declare
native
storage.
A
We
we
prepared
some
items
of
some
items
which
might
be
suitable
for
a
template
and
we
we
had
quite
a
quite
a
useful
debates
back
and
forwards
as
to
what
types
of
use
cases
and
what
types
of
examples
and
how
we
would
build
this.
The
idea
originally
being
that
we
would
have
kind
of
like
a
library
of
use
cases
in
a
github
repo
that
that
different
people
could
help
contribute
to
and
maintain
that
will
provide.
A
You
know
useful
guides
to
to
to
end
users
who
are
looking
to
deploy
applications
on
different
eclair,
native
storage,
riders
or
decline
into
storage
options,
and
some
of
the
you
know
some
of
the
best.
Some
of
the
best
practice
could
include
you
know
things
like
tuning
or
best
apology
options
or
or
settings
for
availability
or
scalability,
for
example,
for
those
particular
use
cases.
One
of
the
one
of
the
biggest
challenges
that
came
up
very
quickly
was
the
the
concept
of
the
kingmaker
right.
A
How
do
we
decide
which
use
cases
should
get
included
in
which
these
cases
should
be
excluded?
And-
and
you
know
how
do
we,
how
do
we
avoid
its
the
use
cases
being
defined,
as,
as
you
know,
implicit
or
explicit
recommendations
for
a
particular
product?
Because
that's
something
that
that
is,
you
know
quite
clear
in
the
CNC
after
our
tulips,
we
shouldn't
be
really
doing
those
there's
this
type
of
recommendations.
A
Are
these
documents
still
useful?
Is
it
worth
the
time
that
were
that
were
interesting
in
this
I
think
this
brought
up
a
fairly
a
fairly
important
issue
in
that,
in
order
for
the
use
cases
to
be
valuable
to
end-users,
they
probably
do
needs
to
be
specific
and
they
probably
do
needs
to
be
specific
to
certain
projects.
A
That's
if
we
did
bring
it
down
to
sort
of
those
super
generic
levels
of
those
high
level
categories
that
the
effect
of
these
use
cases
might
be
might
be
that
they
become
useful
to
very
few
people.
Or
you
know
they
don't
become
useful
at
all.
So
on
that
note,
we
kind
of
came
to
the
conclusion
that
perhaps
we
shouldn't
proceed
with
creating
these
theses
case.
Examples
in
the
use
case,
guidance
documents
and
I'd
love
to
hear
from
the
rest
of
the
community
to
kind
of
get
your
feedback.
You.
A
G
I
agree:
I
think
we
really
are
feedback,
at
least
from
the
community.
We
discussed
this
in
our
call
was
many
people
are
looking
for
opinionated
direction
on
how
to
do
things,
and
you
know
we
want
to
provide
to
them
something
that's
meaningful
and
if,
if
we
can't
do
that
effectively
by
being
overly
vagues-
and
it
may
not
be
something-
that's
worth
our
time-
putting
a
lot
of
work
into
just
creating
generic
Docs-
that's
that's
not
what
they
need.
They
need
to
understand
how
each
of
these
components
work
together.
So
I
agree
with
the
stance.
F
F
A
C
I
think
that
seems
like
a
reasonable
way
forward.
We
do
have
to
worry
about.
You
know
no
king-making
and
anytime.
We
start
to
talk
about
a
specific
product
versus
another
product,
that's
kind
of
a
sign
that
we
should
be
careful
about
what
we're
going.
I'll
turn
on
the
other
end,
I
think
what
you
said
sounds
right
in
order
for
this
to
be
valuable,
you
kind
of
have
to
be
specific,
so
it
makes
sense
that
maybe
this
is
not
the
right
direction
to
take
at
the
moment.
A
F
D
A
And
I,
you
know
my
recommendation
at
this
stage
would
be
for
us
to
just
pull
back
and
dedicate
our
resources
to
to
a
more
useful
project,
perhaps
which,
where
we
can,
you
know
where
we
can
actually
do
something,
a
bit
more
useful
for
the
end
users
and
for
the
CNC
f.
You
know
whether
that's
you
know,
project
reviews
or
or
or
other
information
documents
or
whatever
that
some
W
think
are,
are
going
to
be
more
valuable.
H
A
Yeah,
absolutely,
you
know
I
think
I,
think
the
work
that
we
put
in
to
define
the
type
of
information
that
would
go
into
use
cases
is
still
valid
and
I
think
you
know
it's
at
some
point.
If,
if
the
situation
changes
on
sort
of
opinionation
or
specificity
for
these
projects,
then
then
you
know
we
could
we
could.
A
A
A
Finally,
I
wanted
to
just
talk
about
the
the
projects
which
are
on
deck
so
for
tea,
I
cave,
be,
we've
had
the
presentation
and
sod
has
been
involved
in
the
due
diligence.
Talk,
Aaron
and
I
needs
to
put
sort
of
formalized
the
sake
recommendation
in
thats
document
and
then
the
github
and-
and
we
will
also
include
a
link
to
the
to
the
project,
presentation,
recording
and
so
that
we
can.
We
can
take
that
off
and
and
put
the
TI
caving
on
the
on
the
two
wheel
on
on
sorting
on
the
two-week
comment
period.