►
From YouTube: CNCF SIG Storage 2020-02-12
Description
CNCF SIG Storage 2020-02-12
A
Hey
Alex,
hello,
how
are
you
good
good?
It's
good
to
see
you
in
yes,
yeah
right
on
and
I
think
we'll
won't
be
spending
some
time,
Allah
like
in
the
next
hour
to
to
today,
as
well
with
the
cns
day
con
job
planning.
So
you
thought
I
hope
you
missed
me.
Alex
is
it
looks
like
you're
gonna
get
a
lot
of
me.
Now
we
love
you.
A
A
B
B
A
B
A
B
A
A
Exactly
in
that,
my
firt
is
that
I.
Can
you
see
the
slide
deck
here
now
we
can
okay
and
actually
the
first
slide
here.
Alex
is
about
what
the
expectations
are
for
today.
So
you
know
we
went
through
the
process
for
from
going
from
sandbox
to
incubation.
You
know
last
year
over
a
year
ago-
and
you
know
we
did
the
whole
formal
presentations
to
the
TOC
and
you
know
writing
up
all
the
due
diligence
and
a
pull
request.
The
TOC
repo.
A
You
know
all
the
criteria,
steps
like
we
would
move
to
that
whole
thing
and
we're
we're
in
the
middle
of
that
right
now
for
graduation,
the
graduation
criteria.
So
after
talking
to
our
you
know,
CSUF
liaisons,
Amy
and
Chris
anatec,
you
know
one
of
the
things
that
we
learned
is
necessary
as
step
this
time
for
graduation
is
to
talk
to
the
sig
and
get
the
review
and
diligence
done
by
the
sig
here.
So
we
wanted
to
just
go
ahead
and
get
the
conversation
started
today.
A
We
are
not
ready
for
a
full
proposal,
but
we
want
to
go
ahead
and
figure
out.
Where
do
we
have
gaps?
Where
are
some
obstacles
and
things
that
we
should
be
concerned
about?
And
you
know
what
are
the
next
steps
that
we
need
to
need
to
work
through
so
the
goal
the
hopeful
goal
here
is
that
we
would
be
able
to
finish
the
graduation
process
and
all
the
diligence
and
have
a
vote
by
the
COC
before
Cuba
and
answer
damn,
which
is
its
variant
of
March.
A
A
So
what
that
means
is
that
it
has
a
lot
of
automation
and
through
custom
controllers
and
CR
DS
within
kubernetes,
that
automates
a
whole
bunch
of
storage
management,
deployments
operational
tasks
and
it
started
off
as
being
a
operator
specifically
for
staff
distributed
storage
system,
and
we
around
the
time
of
getting
transitioning
from
sandbox
to
incubation.
We
went
ahead
and
started
an
effort
on
a
framework
to
allow
other
storage
providers
and
solutions
to
be
part
of
the
rug
project
and,
to
you
know,
get
the
benefits
of
you
know:
orchestration
and
automatic
management
in
kubernetes
environments.
A
So,
as
Alex
was
saying,
we
got
accepted
into
the
sandbox
stage
in
January
of
2018
rooms,
the
first
storage
project
to
be
accepted
into
the
CNC
F,
and
at
that
time
our
sponsor
was
Ben
Heineman.
And
then
we
went
to
the
incubation
stage
in
September
of
2018
and
so
for
this
next
stage
to
graduation.
We
have
a
proposal
I'm
going
to
be
talking
to
Saad
more
about
that
for
to
Assad
too,
and
his
new
one
of
his
first
tasks
as
being
a
new
TOC
member
is
to
hopefully
sponsor
the
REC
project.
So
so.
A
Effort
and
support
over
the
years
side
for
sure,
so
let's
go
ahead
and
call
it
real,
quick.
Some
of
the
things
we
know
are
two
do's
right
now
things
we
have
not
done
so.
You
know
submitting
the
diligence,
pull
request
and
official
proposal
to
the
TSE
repo
that
is
going
to
be
all
written
up
and
submitted.
Formally
we
have
a
list
of
production
users
and
adopters
so
they're
a
project.
We
need
to
finalize
that
and
flesh
that
out
a
little
bit
more.
A
We
have
a
couple
of
governance
updates
that
Travis
will
be
walking
through
in
a
second
and
we're
updating
or
implementing
our
security
disclosure
process.
So
we
have
a
core
request:
that's
almost
done
with
that,
so
that
should
be
done
soon,
and
we
also
know
that
we
need
to
do
our
the
core
infrastructure
initiative,
best
practice
badger
like
80%
through
that,
and
so
we
need
to
finish
that
off
as
well.
So
those
are
the
things
we
know
we
have
not
done.
The
gaps
were
aware
of
and
just
a.
A
The
results
and
stuff
yes,
so
the
security
audit
is
completely
done
and
we
did
that
with
the
true
trail
of
bits.
They
also
did
one
of
the
upstream
kubernetes
security
audits.
So
that's
fully
completed
all
of
the
issues
we're
identified
in
the
I
think
that's
on
one
critical
issue
that
has
been
since
fixed
and
patched
and
released,
and
the
full
write-up
of
that
is,
is
published
and
available.
I,
don't
think
we
must
link
it
from
the
repos,
so
it's
more
available
in
public.
But
that's
that's
done
this
here
is
just
the
security
disclosure
process
of.
A
If
someone
in
the
wild
finds
the
security
bug,
you
know,
how
do
they
responsibly
disclose
it?
And
what
is
our
process
around
that?
So
the
audit
is
done,
but
then
the
process
for
finding
new
security
bugs
is
disclosing
their
miss.
The
thing
that's
not
done
yet
perfect,
yep
and
then
real
quick.
Some
numbers
on
a
slide
here
so
on
the
left
is
what
our
stats
were
for
the
project
in
the
community
at
the
incubation
acceptance
stage
and
then
on.
The
right
is
where
we
are
current
day.
A
So
you
know,
container
downloads
is
another
10x
from
sandbox
to
incubation
was
10
x
from
like
1
million
to
10
million
in
the
now
10
million
100
million.
So
the
project
continues
to
grow
in
popularity
with
getup
stars.
We
have
a
lot
more
releases,
we're
you
know
doing
a
lot
more
actual
release
process
there
to
get
more
fixes
out
contributor
a
lot
of
most
most.
Everything
is
at
least
2
X
3
X
growth.
Since
the
incubation
phase.
A
E
Real
work
cleaned
down
there
since,
since
incue
bation
yeah
we've
definitely
had
a
lot
of
lot
going
on
in
the
project.
We've
have
basically
a
quarterly
cadence
as
far
as
getting
releases
out
so
from
bo9
up
to
1.2
is
our
latest
release
in
December.
You
know
some
of
the
major
things
going
in
like
edgy
FS
Cassandra
NFS
operators
are
all
new
back
in
the
Niner
least
yoga
by
DB
and
1.1,
so
up
to
stick
six
storage
providers.
E
Now
in
in
rook
there
now
there
are
a
couple
of
others
in
early
phases
of
a
PR
open
right
now
for
Apache
ozone,
which
is
a
possibility,
but
anyway,
storage
providers,
making
it
available
for
for
others
is
yeah
has
been
a
journey.
I
two
of
those
staff
and
edgy
fests
have
been
declared
stable.
As
far
as
the
the
CR
DS
and
supported
ability.
Like
Jared,
said,
we've
completed
the
security
audit.
E
A
E
It'll
be
around
for
a
while,
but
definitely
and
then
yeah
we've
been
collecting
our
production
adopters,
a
lot
of
them,
probably
I,
think
Jared.
You
said
60%
of
the
people
we
surveyed
don't
want
to
publicize
what
company
they're
from
so
they're
a
lot
more
than
this
list,
but
here
here's
some
of
them.
That
said,
we
could
publish
their
names,
so
we
are
following
up
with
them
on
to
get
quotes
and
things
for
how
they're
using
rook
and
how
big
their
clusters
are,
and
things
also
I
guess
missed
in
this
list.
E
A
Know,
I
think
that's
really
what
we
wanted
to
share
today
here
and
you
know
we
know,
there's
a
busy
agenda
today,
so
it
won't
take
up
too
much
time,
but
you
know
if
there's
any
obvious
feedback
or
you
know
we
can
follow
up
in
other
channels
like
on
the
mailing
list
or
you
can
email
us
directly
and
we
could
talk
about.
You
know
what
are
the
things
we
really
need
to
focus
on
and
worry
about,
such
that
you
know
we'll
we'll
have
good
chances
of
proceeding
with
our
next
steps
from
the
graduation.
G
Is
kind
of
like
the
textbook
process
that
you
follow
through
sandbox
and
incubation
graduation
I,
don't
personally
see
any
major
stumbling
blocks.
What
I
can
say
is
that
you
know
just
the
nature
of
the
TRC's
busyness
before
you
con
you
should
you
should
try
and
get
those
last
checkbox
items
wrapped
up
in
the
next
week
or
so
because
practically
it
takes.
You
know
a
couple
of
weeks
before
there's
a
TAC
meeting
and
then
they
vote
and
people
are
out
of
office.
It
can
take
up
to
a
month
just
to
you
know,
get
that
process
completed.
G
B
So
I
think
the
follow-up
item,
then,
will
be
too
if
you,
if
you
follow,
if
you
finish
off
those
check,
pointed
those
check
box
items
and
the
security
or
the
debt
cetera
and
finish
of
the
presentation,
then
maybe
at
the
next
sake
meeting
you
can
do
the
formal
presentation
and
have
that
recording
and
then
we
can.
We
can
put
together.
A
B
Okay,
sorry,
sir,
so
I
was
just
saying
so.
The
next
steps
is,
if
we
finish
up
those
checkboxes
and
then
have
a
proper
formal
presentation
in
the
next
Sigma
T,
then
we
can
have
that
recording,
plus
the
delivery.
The
due
diligence
talk
and
our
recommendation
for
the
toc
votes
in
for
the
next
for
the
early
early,
March,
I
guess.
C
B
B
G
Clear
that
I
don't
think
there
is
a
conflict
of
interest
there
I
think
he
can
represent
the
TSE
and
the
sorry
cigar
and
and
by
the
way,
congratulations
that
so
I,
wouldn't
personally
worry
too
much
about
that.
Unless
there's
you
know
some
major
concerns
that
this
seems,
like
a
you,
know,
very
straightforward,
a
graduation
process
to
me
just
to
be
clear.
The
majority
of
the
of
the
due
diligence
happened
in
the
migration
to
emigrated
it
to
what
is
the
word:
I've
just
lost
incubator,.
G
That's
the
one!
So
unless
they've
been
you
know
major
regression
since
then,
it's
mostly
you
know
getting
this
badge
getting
the
security
order
done,
making
sure
that
you
have
enough
contributors
and
have
maintained
errs
from
different
companies.
It's
a
tree,
most
of
which
it
seems
you've
done
you're
just
getting
the
final.
You
know
reports
together,
so
we
can
get
somebody
else
to
do
the
the
due
diligence,
but
the
due
diligence
is
essentially
making
sure
that
all
those
things
have
actually
been
done.
It
sounds
like
they
have
so
there's
not
much
to
do.
D
G
B
H
Is
this
is
Michael
from
the
harbor
team?
I
mean
the
would've
done
with
sig,
runtime
and
I
put
a
link.
There
is
of
the
you
know,
they're
also
as
busy
as
everybody
else
and
they've
asked
me
to
create
a
PR
that
basically
kind
of
drives
some
of
the
due
diligence
that
the
CEO
supposed
to
do
and
that
that
PR
essential
is
just
one
file.
That
kind
of
puts
all
the
checks
and
balances
that
the
sig
is
supposed
to
do,
and
they
were
gonna
just
go
through
it
really
quickly
and
verified
the
that
who've
done.
H
What
we're
supposed
to
and
answering
those
ten
questions,
Sado
really
appreciated.
If,
if
you
have
some
time
to
look
at
it,
we're
really
trying
to
lets
get
a
decision
from
the
TOC
if
we're
gonna
graduate
before
Kubik
on
and
we've
been
on
hold
now
for,
like
almost
four
months,
so
it'd
be
good.
If
you
can
actually
get
the
process
moving
a
little
bit,
I'll
try
to.
H
I
G
B
G
B
So
we
completed
the
review
for
the
Dragonfly
project.
We
submitted
a
couple
of
a
couple
of
queries
to
the
team
they've
provided
it's
the
replies
this
week,
which
is
which
is
great
and
I.
Think
going
through
the
replies.
The
disc
covers
of
the
queries
I
had
anyway,
so
I
am
going
to
I'm
going
to
give
this
a
thumbs
up
and
put
a
an
addendum
in
the
in
the
DV
that
we
covered
this
off
and
we
can
we
can.
B
B
We
have
we
have
the
process
which
which
Liz
had
been
driving,
which
is
covered
in
the
slide
deck,
and
she
has
created
a
pr2
to
update
the
existing
criterion
process
on
the
TOC
it
up.
Aaron
templates,
which
mean
which
is
basically
a
merge
of
templates.
We
already
had
in
the
six
storage,
together
with
the
templates
in
see
gaps
as
being
as
being
combined,
and
we
put
it
into
the
into
the
into
the
issue:
three
four
four
which
which
is
linked
there
and
that
template
was
agreed
on
two.
B
So
this
needs
to
be
finally
converts
to
the
you
should
just
needs
to
be
converted
to
a
PR,
so
it
can
get
so
get
approved,
but
I
think
we're.
We
now
have
a
proper,
easy-to-follow
process
and
set
of
templates
that
we
can
use
for
sandbox
incubation
projects.
So
I
think
this
is.
This
is
a
really
good
milestone
between
the
TOC
and
the
sake,
and
thank
you,
everyone
for,
for
the
work
involved
to
get
us
to
this
point.
B
We
have
two
sets
of
edits
which
we're
looking
to
merge
into
the
into
the
landscape
document,
so
so,
the
first
being
the
database
update
stock,
which
sugu
handwritten
I've,
made
some
changes
and
asked
for
a
review.
Superman
Quentin
have
put
in
their
comments,
which
all
look
great
to
me,
so
I'm
just
going
to
add
that
into
the
document.
B
It
would
be
great
if
anybody
else
who
has
comments
would
up
with
have
a
quick
look
at
that
database
update
document,
which
is
now
Rihanna
standing
for
a
little
while,
but
we
we
would.
We
would
love
to
close
this
off
so
assuming
there
aren't
any
more
updates
by
the
end
of
this
week.
I'll
look
to
merge
this
into
the
into
the
into
our
landscape
white
paper.
B
Similarly,
Jing
had
had
an
action
to
update
the
orchestration
and
management
interfaces.
Section
to
kind
of
you
know
reflects
the
the
current
state
of
the
market,
given
that
you
know
given
that
over
the
last
18
months
since
we
published
the
white
paper,
there
have
been
sort
of
a
number
of
changes
around
CSI
and
things
like
that.
So
there's
there's
a
link
to
the
updated,
the
doc
that
she
has
refreshed
in
in
the
link
attached
on
the
agenda
as
well,
and
she
actually
has
San
Jing
has
also
sent
out
as
an
email.
J
B
B
B
Great
ok
and
then
we
have
the
performance
benchmarking
paper.
So
the
the
author
team
met
last
week
and
we
know
week
before
last
there
and
agreed
on
some
of
the
work
that
we
needed
to
do
and
started
with
the
updates
we've
pulsar
B
has
joined,
as
rings
the
the
sort
of
the
white
paper
team
and
he's
contributed.
B
After
the
tear
sequel,
he
mentioned
that
there
were
some
other
tools
that
that
we
made
that
we
may
look
to
consider
that
he
had
been
working
with
as
part
of
the
crib
annuities
benchmarking
performance
sake
and
will
will
probably
live
to
see
if
there
is
some
criminality
or
some
overlap,
that
we
can
that
we
can
include
in
here
too
so
so
again.
Looking
for
some
feedback-
or
you
know
point
you
know
we
specifically
we're
kind
of
interested
in.
B
G
B
All
right,
so
any
other
any
other
things
on
that
or
recurring
move
on,
while
we're
going
through
this
again
they're,
pretty
quick,
so
the
use
case
doc
documents.
So
so,
just
to
recap
on
this,
the
use
case
documents
is
is
something
that
is
something
we
wanted
to
work
on
and
has
also
been
the
subject
of
sort
of
end
user
feedback.
B
B
The
current
template,
which
is
in
github
to
to
a
Google
Doc,
to
make
it
a
little
easier
to
collaborate,
we're
going
to
we're
going
to
change
the
focus
of
the
template.
So
that's,
rather
than
being
specific
product
use
cases,
they
will
be
focused
on
use
case
categories
rather
than
the
rather
than
a
specific
product,
and-
and
this
is
to
sort
of
address
concerns
of
you-
know,
creating
unfair
bias
or
showing
preference
to
to
any
particular
project
or
vendor
or
whatever
else.
B
So
I'd
really
love
to
hear
your
thoughts
on
this.
Are
we
heading
in
the
direct
in
the
in
the
right
direction?
Are
there
any?
You
know
serious
objections
to
this
idea,
if
not
pull
together
to
Google
Doc
and
send
it
out
for
for
for
review
in
terms
of
a
template
and
then
hopefully
maybe
we
can
assume
we
can
get
agreement
on
templates.
We
can
move
forward
with
that
template
and
and
create.
You
know
the
first,
the
first
category
and
sort
of
just
make
sure
that
the
template
works
towards
comments,
violent
objections.
B
B
B
To
get
to
get
some
to
get
some
publicity
there
until
you
cover
projects
that
have
recently
being
introduced
to
the
CN
CF
like
like
Triborough
fastened
and
long
horn,
for
example.
So
I'm
happy
to
do
that.
But
if
anybody
else
wants
to
volunteer
to
do
a
PR
to
add
that
list
to
the
and
the
cig,
repo
I
could
do
with
some
help.
Save
one
time
like.