►
From YouTube: CNCF SIG Storage Meeting 2019-11-13
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
CNCF SIG Storage Meeting 2019-11-13
A
A
A
A
C
A
C
A
So
on
the
agenda,
as
hopefully,
everyone
knows
by
now.
We
had
pretty
sad
news:
Brad
childs,
who
was
one
of
the
HOH
tech
leads
of
the
scene.
Storage,
sync
and
one
of
the
co
leads
of
storage
sake,
his
passed
away.
So
if
you
would
like
to
record
a
video
memory
for
Brad
that
will
be
given
to
his
family,
there
is
a
link
in
the
agenda.
That
first
item
is
the
sooner
you
can
do
that.
A
E
D
A
B
A
B
Just
the
directory
use
cases,
so
what
I've
done
here
is
kind
of
taken.
Your
feedback
from
the
previous
meetings
had
it
in
a
way
that
it's
simple
to
add
simple
to
edit
simple,
to
track
versions,
simple,
to
remove
and
simple
to
add
new
ones
and
keep
it
a
keep
it
concise
for
those
who
are
new.
So
what
I
try
to
do
is
I
created
a
small
template.
That's
right!
B
There
and
I
created
a
simple
use
case
using
the
template,
so
we
can
click
on
a
template
first
and
you
can
see
how
simple
it
is
and
I
took
the
top
part
from
kubernetes
style
of
doing
caps.
So
this
is
just
an
idea.
Every
again,
this
is
a
strawman
I'm,
not
saying
this
is
the
way
it
should
be,
but
it's
a
it's
just
a
start
and
if
you
guys
feel
this
is
the
correct
direction,
we
can
continue
to
go
in
this
direction
or
we
can
give
it
in
another
direction.
B
Then
you
can
see
that
area
looks
is
just
taken
from
from
the
caps
in
kubernetes
and
it
provides
a
way
to
track
it
and
know
the
state
of
the
document
and
things
like
that.
And
then
the
document
is
just
regular
markdown
the
document
the
way
I
have
structured.
It
is
to
make
it
simple
for
readers
and
then
refer
back
to
the
storage
landscape
document
in
any
any.
B
This
is
a
small
example
of
how
to
deploy
manao
and
have
the
storage
back-end
for
it
in
the
use
case
is,
as
is
described
here,
I
modeled,
with
the
requirement
of
accessing
files
over
a
shelf,
our
system
and
an
object
store
at
the
same
time.
Okay,
so
for
that
use
case,
you
can
go
down
and
it
says
what
the
goals
are
for
the
small
document,
but
you
can,
if
you
go
to
scroll
down
a
little
bit.
B
Thank
You
Khan,
so
here
you
can
see
the
storage
landscape
summary
it
tells
you
that's
recommended
to
use
those.
It
tells
you
if
you
use
one
of
those.
This
is
what
you
should
check
for.
If
you
use
a
block
store,
make
sure
you
have
a
file
system
on
top,
and
you
also
need
a
service
to
be
able
to
to
share
that.
If
you
go
down
a
little
bit
more
in
file
systems,
it
says
it
says:
look
if
you
have
a
remote
file
systems.
B
It's
actually
really
nice,
because
the
storage
system
already
has
a
model
for
for
clients
to
access,
and
it
has
a
model
for
you
to
go
from
node
to
node,
to
connect
and
disconnect.
So
so
pretty
much.
This
is
like
you
know,
and
then
again,
I
said,
look
up
six
doors
and
key
values
that
they're
they
just
don't
work
in
this
use
case.
So
this
is
the
Stroman.
If
you
can
notice.
Also
things
like
durability
and
file
systems
and
other
stores
are
all
links.
They
all
refer
to
that
section
in
the
landscape
paper.
B
So,
as
a
user
that
I'm
not
very
familiar
with
storage
and
I
want
to
click
on
file
systems,
can
click
on
that
and
it
puts
me
right
on
that
page
on
the
story's
landscape.
So
I
can
read
that
more
information
about
it
and
again
the
goal
is
to
make
it
concise.
I
didn't
want
to
go
into
too
much
detail
and
we
can't
add
more
detail,
but
it
is
just
a
use
case
recommendation.
A
B
C
B
It's
I'm
not
I'm,
trying
to
not
say
that
it's
not
recommended
I
guess
that's!
The
word
dislike
is
a
binary
thing.
Maybe
we
cannot
make
it
binary,
make
it
three
many
like
doesn't
matter
right,
but
right
now
it's
binary,
but
it
really
doesn't
matter
it's
how
the
stories
that
does
it,
because
it's
it's
more
of
an
in
protocol
front,
but
you're
right
I
mean
maybe
maybe,
instead
of
just
recommended
and
not
recommended,
we
couldn't
have
three
states
like
it
it
na,
like
not
applicable,
something
like
that
yeah
yeah.
All
right
is.
B
C
B
B
F
You
know
we
in
this
particular
example.
We
kind
of
seem
to
start
with
the
assumption.
This
mini
is
the
solution
and
then
essentially
justify
it
and
it
it
sort
of
doesn't
feel
to
me.
That's
the
flavor
that
we,
you
know,
understood
the
problem,
the
requirements
and
then
you
know,
spelled
out
a
bunch
of
different
ways
to
do
it
with
pros
and
cons
of
each
way,
which
would
seem
like
the
sort
of
balanced
approach
to
something
like
this
all
so.
B
B
F
G
B
We
want
to
I
mean
trying
to
go
back
to
the
root
of
this
proud
of
this
task,
which
is,
do
we
want
to
be
like
that
that
we
want
to
say
you
are
deploying
Kafka
as
a
use
case,
here's
the
recommended
storage
for
that,
in
other
words
here
so
I
recommend
an
app
and
here's.
The
storage
for
that
and
I
chose
the
app
to
be
Mahna
Mahna.
Oh
now,
do
we
not
want
to
do
that?
Do
we
want
to
be
really
really
generic
like
if
you
deploy
a
like
a
message,
bus
app
do.
B
C
To
sum
my
two
cents
here,
I
mean
many:
oh,
it's
possibly
a
bit
some
big
interest
because
it
kind
of
they
sort
of
sits
in
the
storage
space,
as
well
as
being
a
use
constraints
that
could
consume
storage,
but
I
I
think
would
be
really
want
to
catch
out
of
these
use.
Cases
is
different
applications
that
consume
storage
and
link
that
to
what
we
have
in
the
landscape.
Looking
at
Sparrows
say
this
application
these
these
type
of
topologies.
C
This
type
of
storage
is
optimal
or
recommended
for
them,
and
we
may
want
to-
and
we
may
want
to
sort
of-
maybe
augment
it
and
have
maybe
a
notes
category
or
something
in
this
in
this
example
template,
but
that
we
can
talk
about
because
in
the
landscape
I
can
write.
We
have
the
attributes
like
failover
and
scalability
and
performance
like
I,
think
and
maintain
consistency,
durability
whatever.
C
So,
maybe
we
can
say
you
know
we
could
have
a
section
with
notes
to
cover
some
of
those
attributes
to
be
added
to
this,
so
it
would
be
a
use
case
like
Kafka,
perhaps
or
or
a
database
or
a
message
queue
or
you
know.
Whatever.
That's
they
for
news
cases
that
that
is
consuming
storage
and
we
say:
okay,
we
have
the
we
have
to
you
know
it
should
be
fastest
and
should
be
locally
remote
should
it
be
distributed
to
volunteer
or
centralized
whatever,
and
we
and
we
list
all
of
those
things.
C
C
B
Exactly
right,
I
mean
that's,
that's
the
model
on
going
after
and
I
know
that
we
had
it's
a
kind
of
a
double-edged
sword
because
we're
talking
projects
as
applications
that
consume
storage,
but
they're
also
proposing
promoting
those
projects.
So
we
have
to
be
careful
again
I.
This
is
a
straw.
Man
I
want
to
really
get
your
opinion
on
it.
So
I
completely
understand
quinton
what
you
mean
and
I'm
trying
to
I,
don't
know
how
to
satisfy
the
requirement
of
helping
customers
and
users
at
what
the
same
time
being
ambiguous.
A
Right
like
if
we're
just
just
mention
the
general
data
structures
and
put
it
into
a
document,
it
doesn't
really
help
people
get
started
or
understand
different
things.
There
is
an
issue
of
these
becoming
stale
like
there.
There
could
be
something
a
different
operating
than
video
I
mean
I.
Think
we
just
we
like
all
open-source
things.
We
would
open
it
up
to
different
use
cases
that
also
address
the
same
thing
exactly.
B
B
D
Agree
that
we
want
to
make
this
as
useful
as
possible
and-
and
you
know
having
it
very
generic-
is
it
makes
it
difficult
to
be
useful,
but
at
the
same
time
I
think
I
agree
with
Wynton.
We
have
to
be
aware
that
you
know
the
C
and
C
F
can
be
used
as
a
platform
for
promotion
and
as
soon
as
a
product
is
mentioned
anywhere,
it
incentivizes
anybody
who
is
a
competitor
in
that
space.
B
C
Rights,
its
but
just
to
clarify
rights,
we're
not
we're
not
specifying
different
storage,
relax
here
and
we're
not
saying
if
you
want
to
run
Kafka
for
sake
of
the
argument:
here's
this
product.
What
we're
saying
is
these:
are
the
attributes
you're
looking
for
out
of
the
storage
system,
and
these
are
the
things
that's
that's
that
she
needs.
C
That
means
consider
for
that
use
case
right
now.
The
idea
of
doing
anything
get
up
was
also
a
case
of
right.
If
you
can,
you
can
now
look
at
Kafka
and
you
can
say
it
benefits
from
a
local
file
system
with
strong
performance
or
whatever,
and
then
def
allows
them
to
look
at
the
storage
landscape
and
make
your
own
decisions
as
to
what
storage
systems
are
going
to
use
more,
what
cloud
service
or
projects
or
whatever
else
they're
going
to
use
so
we're
on,
but
I'm
actually
recommending
a
project
per
se.
C
D
D
Agree
with
the
intention
of
this
and
I
understand
that
the
intention
is
not
to
pitch
a
product,
it
is
to
explain
a
use
case
and
then
use
a
product
as
necessary
as
an
example,
but
I
think,
even
with
that
you're
going
to
have
folks
who
are
gonna
say
hey.
Why
is
my
competitors
product
named
here?
I
want
to
update
this
example
to
include
my
product?
That's
not
fair!
Let
me
in
and
so.
E
D
B
There's
two
more
two
answers:
that
one
is
that
it's
on
github,
so
anybody
can
edit
and
we
can
go
through
the
process
they
can
create.
They
can
create
their
own
also.
So
we're
not
it's
not
like
when,
when
we
go
through
the
process
of
accepting
a
project
into
the
CNC
f,
you
have
to
go
through
certain
things,
but
creating
a
small
page
on
github,
that's
very,
very
easy
and
very
low,
real
or
ramp.
B
The
second
one
is
that
it
could
be
that
instead
and
here's
another
way
of
doing
it,
instead
of
us
creating
this
pages
and
hosting
it
here
which
could
cost.
The
issue
is
that
we
create
the
template
and
we
let
projects
host
them
on
their
page
on
the
web
pages
and
they
manage
we
just
kind
of
promote
the
the
template
and
let
the
project's
then
post
it
on
their
pages
right
and
they
think
of
refer
back
to
the
landscape
document.
Just
like
this
github
documents.
Doing
then
that
it's
not
up
to
us.
F
I,
don't
necessarily
think
hosting
is
is
the
problem
in
my
opinion.
In
my
opinion,
the
function
of
this
group
is
to
provide
unbiased,
balanced
and
useful
information
to
you
primarily
to
the
user
country
community.
As
one
of
our
functions,
we
have
other
functions
too
and
I
think
that
doing
that
focused
on
one,
maybe
I'm
out
of
line
here.
I
mean
repetitive
it.
It
just
doesn't
feel
like
we're
fulfilling
the
need
here,
but
the
need
is,
you
know:
I
want
to
build.
F
My
own
object
store
on
top
of
my
file
systems,
what
what
options
do
I
have
and
and
what
are
the
pros
and
cons
of
the
different
options?
That
to
me,
is
what
we
were
trying
to
do.
Oh
and
correct
me:
if
I'm
wrong,
when
I
can
come
to
a
page
like
this
and
says:
oh
okay,
you
know
at
least
these
options,
and
and
most
people
use
this
option,
and
but
one
of
the
problems
is
X
and
and
if
X
is
a
problem
for
you,
you
also
have
up
y&z
these
other
downsides.
F
B
You
think
that
what
I
meant
by
another
repo
means
like
we
don't
like-
we
don't
put
it
up
here
but
like
we
don't
advertise
it,
but
I
think
we
are
here
so
an
idea.
What
I
think,
following
what
you
said
is
that
in
when
you
write
technical
papers,
you
on
towards
the
end,
you
have
to
write
like
when
you
write
patents.
Things
like
that.
You
have
to
write
a
section
of
what
other
things
are
out.
There
are
similar.
We
could
require
that
when
you
create
one
of
these,
you
know
there's
a
section.
B
C
D
Think
my
concern
is
mostly
around
having
any
sort
of
product
names
mentioned
in
anything
that
resembles
a
recommendation
or
by
the
CNCs,
and
the
reason
for
this
is
kind
of
the
history
that
we
had.
If
you
all
recall
the
fiasco
with
when
we
try
to
define
what
C&C,
F
or
cloud
native
storage
meant
turned
into
a
giant
for
all.
D
A
Maybe
a
good
way
would
be
to
put
the
use
case.
Instead,
object,
store
gateway
using
manao
would
be
Juke
store
gateways
and
then
so
it
would
explain,
use
cases
why
we
would
want
to
use
an
object,
store
gateway,
the
topology
architecture,
advantages
of
that
and
then
under
references.
Yes,
it
would
be
up
to
the
author
to
provide
an
examples,
though
we
could
reference
architectures,
or
example
references
or
or
do
we
just
expect
the
user
to
go
out
and
google.
Those
I
thought.
B
I
think
just
sorry,
I
just
I
thought
about
that
Aaron
and
the
problem
was
was
that
in
each
implementation
of
the
Gateway
it
was
different.
For
example,
if
I
compare
mean
I
know
to
and
I
view
this
as
an
application
that
consume
storage
right,
if
I
mean
IO
to
open
sex
with
to
rock,
they
have
different
ways
of
requiring
storage
the
end,
then
they
all
have
the
same.
They
all
satisfy
the
requirement
of
accessing
the
file
and
an
object.
B
D
E
D
The
same
time,
I
do
think
that
products
are
responsible
for
providing
their
own
documentation
for
how
to
deploy
uber,
Nettie's,
etc,
etc,
and
what
we
want
to
capture
here
is
not
necessarily
hey.
Here
is
how
you
integrate
with
a
specific
product,
but
holistically
here
is
a
product
category
and
here's
generally
architectural
II,
how
it
works,
and
then,
if
you're
interested
about
a
specific
product,
you
go
look
at
that
products.
D
C
So
can
I
can
I
just
quickly
ask
a
question
here:
right
are
we?
Are
we
getting
ourselves
tied
up
in
knots,
because
the
example
that
we
happened
to
choose
first
was
happens.
P
storage
relates
it
would
we
feel
this
way
if
we
were
talking
about
I,
don't
know
how
to
deploy
a
sequel
database.
You
know
if
your
choice,
it's
my
secret
or
Postgres
or
whatever
on
an
and
what
type
storage
they
would
require.
C
Would
that
change
the
thinking
at
all,
because
I
I
kind
of
do
feel
that
it's
we
there
are
lots
of
things
that
could
consume
storage.
Obviously,
and
we
went
to
great
lengths
to
define
all
the
different
storage
types
and
how
they
work,
and
you
know
pros
and
cons,
and
things
like
that,
and
what
what
we
always
said
we
were
going
to
do
as
the
next
step
was
defined.
C
The
use
cases,
the
kind
of
an
examples
of
how
does
how
real-life
consumers
of
that
storage,
where
they
faith
phases,
whether
it's
a
message
queue
whether
it's
a
stateful
application
of
whatever
type
is
consuming
the
storage.
Now,
in
this
particular
case,
we
kind
of
chose
a
time
biggest
example,
because
video
is
obviously
both
a
storage
consumer.
Animal
storage.
Try
there
so
so
I
can
I
can
understand
the
wiring
here.
But
if
this
was
say,
I
don't
know
a
database
or
an
example
of
how
to
configure
a
message.
F
It
hit
the
nail
on
the
head,
Alex
I,
think
if
we
treated
the
use
case
here
as
building
an
object
store
on
premise,
it
looks
like
is
kind
of
the
assumption
then
and
and
Minaya
was,
was
listed
as
one
of
the
options
that
was
available.
If
you
wanted
to
build
an
on
premise,
object,
store,
I,
think
that
would
be
totally
fine
and,
and
the
same
goes
for
the
database,
stuff,
I,
think
I'm,
probably
less
to
mentioning
products
than
Saudis
and
and
I
understand,
Cincinnati's,
but
I
think
to
be
useful.
F
We
have
to
be
comfortable
saying
this
is
the
most
commonly
used.
You
know,
I
think
we
should
be
able
to
say
my
sequel
is
a
commonly
used
relational
database
and
so
is
Postgres,
and
there
are
also
these
other
ones
that
are
less
commonly
used,
for
example,
but
I
think
there
are
a
whole
bunch
of
things
that
are
common,
whether
you
are
deploying
Postgres
on
my
sequel
or
any
other.
You
know
of
those
style
of
databases.
F
Regarding
what
disk
you
store
your
data
on
how
you
set
up
your
caching,
all
of
those
kinds
of
things
and
I
think
they
can
be
dealt
with
generically
and
and
I
think
we
can
say
the
pros
of
putting
your
you
know.
Log
file
database
logs
are
non
SSD
or
the
following,
and
the
cons
are
the
following,
and
this
is
the
common
way
of
doing
it
for
performance,
durability
or
cost
is
bit
more
important
because
it's
the
common
way
of
doing
it,
I
think
I'd
be
totally
fine.
F
A
B
C
B
B
A
B
A
I
mean
we
would
obviously
want
to
highlight
the
open
source
ones
that
are
part
of
the
C
and
C
yes,
right,
I
mean
if
they're
there.
We
should
be
able
to
put
them
here
as
a
viable
option,
but
it's
nice
if,
if
the
use
cases
could
be
put
in
such
a
way
like,
why
do
I
need
object?
Storage?
Why
would
I
want
to
use
a
gateway
like
it
explained?
A
I
would
want
to
do
that,
which
I
think
you
you
done
and
then
the
more
specific
pieces
we
would
just
leave
to
these
references
we
wouldn't
put
those
specific
changes
is:
if
I
did
this
in
nuba
or
I?
Did
it
in
manao?
What
would
the
differences
be?
That's
up
to
the
user
to
go
experiment
what
works
best
for
them
right
and
so
that
so
then
we
would
leave
product
specific
under
references.
We
would
open
that
up.
Who
would
let
anyone
add
their
reference
there?
You
know
we
we
need
a
disclaimer,
probably
like
we
do
not.
A
H
B
H
C
So
so
trust
to
clarify,
though
right
we
are,
we
are
not
building
storage
to
use
cases
we
are.
We
are
not
going
to
build
a
catalog,
all
the
storage
projects
and
say
this
is
the
best
way
of
deploying
these
faithful
these
these
storage
systems.
It's
not
about
that.
The
huge
cases
are
end-user
use
cases.
So
in
some
cases
there
might
be
some
ambiguity
because
somebody
might
be
deploying
a
key
value
store
like
at
CDP,
and
you
might
want
to
have
a
use
case,
which
is
how
do
you
deploy
it
see?
C
What
is
the
important
thing
that
you
need?
That's
the
storage.
Well,
you
need
the
file
system.
You
need
strong
durability
and
in
strong
resistance
is
very
acceptable.
I
think
it's
okay
to
say
that
and
I
think
it's
okay
to
say:
that's
what
the
CD
means
and
if
and
if
somebody
wants
to
write
they
use
face
for
a
console,
then
fine,
let
them
do
it.
C
That's
the
whole
point
of
having
a
community
repeater
right
and
I
think
the
same
thing
that
plays
through
to
other
things,
whether
it's
you
know
message,
queues,
databases
or
any
other
type
of
Statesville
application.
I.
Think
somebody
might
say
this
is
how
you
deploy
I,
don't
know
WordPress
on
on
a
stateful
application.
You
want
the
client
system
or
or
or
if
you're,
installing
WordPress.
You
want
to
thank
the
base
with
this
type
of
consistency
or
this
particular
application
needs
a
key
value
store,
which
means
attributes,
as
the
backend
I
think.
C
Those
are
all
perfect
things
to
have
here.
The
the.
What
we're
trying
to
remove
is
the
ambiguity
from
the
end
users.
That's
that
they
kind
of
look
at
this
and
they
go
okay.
There
are
a
look
at
the
CN
CF
landscape
and
there
are
you
know,
four
hundred
different
options.
How
am
I
even
gonna,
where
do
I
even
start
from
right,
and
this
is
pointing
them
to
something
to
say
you
have
these
attributes.
C
It
means
to
deify
system
where
it
needs
to
be
a
key
value
store,
it
needs
to
be
whatever,
and
this
is
how
you
can
do
it.
This
is
this
is
what
we're
trying
to
build
here
so
I'm
just
trying
to
keep
everybody
on
track,
because
I
feel
like
we
were
having
a
circular
discussion
where
we
discussed
this
five
times
or
anything
round
button
to
the
point.
Where
were
where
we're:
putting
a
template
together
and
then
rehashing
the
same
old
discussion,
I.
B
Let's
stop
now
yeah
exactly
what
I
was
gonna
say
because
to
me,
when
I
asked,
Orage
and
and
again
I
complete
here,
what's
sad
and
Quinton
are
not
I'm
trying
to
balance
it
and
Aaron,
so
I'm
not
done
nothing
not
do
that
I'm
just
trying
to
come
up
with
as
a
user.
What
can
I
can
can
six
storage
kind
of
compile
down
to
me
for
me,
something
like
a
you
know
like
a
a
card
that
I
can
just
look
at
with
bullets.
G
B
G
It
if
this
is
what
I'm
hearing
so
I
might
agree
with
it
that
a
document
like
this
that
describes
storage
use
cases
by
class
look
object.
Store
is
a
class.
It
is
not
commingled
with
sequel
based
relational
databases
that
would
be
a
different
class,
but
have
a
document
per
class.
Maybe
inside
that
document
you
could
link
examine
at
the
end
with
links
to
supplemental
documents
maintained
outside
the
CNC
F.
G
B
G
B
A
Be
fine
with
the
use
case
to
mention
a
product
and
instead
requiring
authors
of
these
use
cases
to
provide
at
least
two
different
references
in
the
bottom
and
it
links
to
somewhere
else
out.
We
provide
a
disclaimer
saying
we
don't
the
C&C
F
does
not
endorse.
These
are
provided
purely
for
reference
and
move
on.
Is
that
would
everyone
feel
comfortable
with
that
yeah.
F
I
sorry,
just
one
point
in
common
Minaya,
so
I
think
one
of
our
functions
here.
We're
supposed
to
be
cloud
made
up,
storage
experts
and
people
are
looking
for
us
looking
to
us
for
advice
and
so
so
I
think
it's
actually
fairly
reasonable
for
us
to
endorse
ways
of
doing
things
saying.
We
think
this
is
a
good
way
of
addressing
this
use
case,
and
we
think
this
is
a
less
good
way
of
addressing
this
use
case,
and
sometimes
that
will
involve
mentioning
open
source
projects,
for
example,
and
I.
F
Don't
think
we
should
be
petrified
of
doing
that.
That's
out
Java.
What
we
do
have
to
be
sure
of
is
making
sure
we're
being
objective
about
this
and
transparent
and,
for
example,
if
a
person
writing
a
document
works
for
a
company
that
sells
product
X,
they
should
declare
that
upfront
and
and
whenever
we
make
recommendations,
we
should
explain
why
we're
making
them
and
what
the
alternatives
on
what
the
present
comes
up.
The
different
alternatives
are
awesome.
B
D
I
appreciate
that
I
think
the
problem
with
that
approach
is
that
the
folks
who
have
the
most
incentive
to
go
and
make
the
changes
are
the
ones
who
are
getting
paid
to
make
those
changes
all
right.
So
the
companies
who
have
products
that
they're
trying
to
sell
are
gonna
be
the
ones
that
are
very
actively
trying
to
manipulate
these
pages.
To
make
their
products
look
good.
It
seems.
D
G
I,
like
your
own
suggestion
too,
and
maybe
add
on
just
a
procedural
quite
that
when
the
PR
gets
approved,
maybe
representatives
from
the
people
linked
below
should
be
on
that
approval
list.
So
you
know,
in
other
words,
if
somebody
puts
their
own
product
as
one
of
the
references
in
some
other
product
as
the
second
reference,
let's
have
a
rule
that
somebody
associated
with
that.
Second,
reference
actually
approves
the
text
above.
Does
that
make
sense,
yeah.
B
H
B
B
G
E
G
Example,
if
I
wanted
to
be
nefarious,
I
could
link
to
some
five-year
old
document.
That
would
be
bad
and
we
don't
want
that
to
happen.
So
I
think
if
somebody's
name,
product
or
even
open
source
project
is
included
here,
that
somebody
affiliated
with
that
particular
talk.
Target
of
the
link
should
at
least
review
the
document,
rather
than
getting
blindsided
by
some
public
documents
suddenly
appearing
that
they
had
never
seen
before.
Okay.
A
So
let's
do
four
things:
we're
going
to
have
the
use
case,
feed
genericized
we're
going
to
provide
at
least
two,
if
not
more
references
to
implementations
of
that
use
case,
with
an
approval
out
to
those
open
source
projects
to
approve
that
they
want
that
use
case
included
and
it's
the
appropriate
link
and
we
will
also
add
a
disclaimer
to
the
references
to
say
these
are
not
endorsed
by
the
scene.
Cf
storage,
sig
merely
provided
as
a
reference
to
implement
this
particular
pattern.
Is
everyone
good
with
that?
Can.
C
C
G
Would
say
that
the
use
case
for
a
specific
solution
or
project
is
linked,
so
it's
not
like
we're
saying
it
doesn't
exist.
It's
just
there's
a
top-level
document
that
attempts
to
cover
the
category
and
then
provide
links
to
deeper
dives
into
best
practices
and
considerations
were
using
particular
implementations.
Now,
if
those
implementations
are
open
source
under
the
CNC
F,
maybe
it
belongs
under
the
auspices
of
this
group,
but
in
some
cases
maybe
these
links
are
going
to
point
to
other
things.
You
know
using
the
landscape
as
an
example,
the
landscape
even
allows
commercial
products.
B
A
D
A
H
E
A
C
C
Tuning
things
now
with
users
from
pro
Kona
and
data
core
and
plant
scale
storage,
OS
and
with
the
split
the
documented
sections
and
we're
working
on
delegating
the
authoring
of
the
of
each
of
the
sections
to
two
different
people
kind
of
in
a
similar
fashion
to
how
we
did
the
storage
landscape
documents.
So
it's
it's!
It's
coming
along,
there's
still
quite
a
bit
of
work
to
do,
but
we're
hoping
that
we
should
be
having
their
drafts.
Within
a
few
weeks.
Maybe
two
weeks,
q
ConAgra
obviously
slowed
things
down
somewhat.
C
A
A
C
F
A
A
Right,
thank
you
for
the
update
and
thank
you
for
putting
that
together.
The
next
piece
we
have
two
minutes
left
dragonfly.
We
briefly
discussed
this
in
the
beginning
of
October
and
I.
Don't
think
we
circled
back
around
and
so
I
think
we
had
wanted,
maybe
to
do
more
of
a
due
diligence
and
had
I,
don't
know
sod
if
we
had
talked
to
you
or
Brad
about
doing
that
due
diligence
for
that,
but
I
think
that
was
kind
of
the
next
steps
was
there.
Did
you
guys
do
a
coat?
B
A
A
C
C
Further
down
in
the
meeting
minutes
and
I
recall
we
built
took
some
notes,
but
it's
kind
of
unfortunately
slipped
through
the
cracks
and
I.
Don't
think
we
followed
up
on
it.
So
we
do
have
an
outstanding
to
do.
I
can
do
do
follow
up.
There
were
written
and
I
had
some
concerns
projects,
but
we
need
to
write
it
up
down
some
notes
and
and
share
them.
So
if,
if
one
of
the
techniques
wants
to
re-review
the
the
presentation
and
you're
recording
I'm
happy
to
sync
up
with
and
share
my
enhance
as
well
should.
E
A
Okay,
the
process
is
still
pretty
squirrely
from
Diggs
doing
it
to
the
TOC,
because
the
other
thing
that
happen
is
I
believe
they
presented
to
us
and
then
the
following
week.
They
also
presented
to
the
TOC,
so
we
have
to
better
iron
out
that
process.
So
thank
you
for
bringing
that
up
and
I'll
include
both
recordings
in
here
as
well
and
then
be
specific,
I'll
think
up
Assad
separately
and
we'll
figure
out
the
due
diligence.
Thank
you.