►
From YouTube: Kubernetes SIG Storage 20161110
Description
Kubernetes Storage Special-Interest-Group (SIG) Meeting - 10 November 2016
Meeting Notes/Agenda: https://docs.google.com/document/d/1-8KEG8AjAgKznS9NFm3qWqkGyCHmvU6HVl0sk5hwoAE/edit#heading=h.58bopdnkwi5b
Find out more about the Storage SIG here: https://github.com/kubernetes/community/tree/master/sig-storage
Moderator: Saad Ali (Google)
Chat Log:
09:09:40 From Saad Ali :
F2F Agenda: https://docs.google.com/document/d/1drdxPkZEiGA06-jnsbSqywzQ6z0bT8uMpJdnIzkRoPo/edit?ts=57ed5df2#heading=h.hs60nbsyz2jk
F2F Meeting minutes/notes: https://docs.google.com/document/d/10AJzJvJcEA5w1wW6wMgS7aOfiH0FTZhszt_P6VNRxLk/edit?usp=sharing
A
So
hello,
everyone-
this
is
the
bi-weekly
meeting
of
the
storage.
Sig
today
is
Thursday
November,
10
2016
and
as
a
reminder,
this
meeting
is
public
and
recorded.
So
the
agenda
looks
pretty
light
today.
I
think
a
lot
of
folks
are
out
due
to
cube
Con
this
week.
So
this
is
probably
going
to
be
pretty
short.
If
you
have
any
items,
feel
free
to
add
them
to
the
agenda.
A
A
There
are
a
couple
of
items
that
are
still
pending.
They
are
for
the
1.4
branch
and
bug
fixes.
One
in
particular
is
the
NFS
cluster
containerization
work.
That's
going
on
for
GCE
jinx.
You
on
our
side
is
working
on
that
I
believe
the
current
status
is,
the
code
is
already
checked
in
and
she
is
doing
verification,
adding
testing
and
making
sure
everything's
okay
before
it's
patch
back
second
bit
is
rashad
on
our
side.
A
It
has
been
working
on
improving
the
messaging
around
the
scenario
when
binaries
are
missing,
so
he
added
in
a
can
mount
option
to
the
mount
or
interface
that
is
called
before,
before
the
actual
amount
happens
and
for
the
volume
plugins
that
it's
implemented
for
it'll
go
out
and
check
what
binaries
are
actually
installed
and
if
they're
requisite
binaries
for
mounting
are
available
or
not,
and
then
an
event
gets
created
for
the
pod.
If
the
binaries
aren't
present,
that
tells
the
user
that
the
binaries
aren't
present.
A
Other
than
that
I
think
most
of
the
work
for
1.5
is
complete
for
storage.
There
were
a
couple
of
things
that
didn't
make
it
into
1.5
one
was
the
rbd
attacher
work,
we're
going
to
continue
working
on
that
for
1.6
and
then
I
believe
the
default
provisioners?
That
was
one
that
we
really
should
have
gotten
into
1.5,
but
I
think
we
dragged
our
feet
on
the
code
reviews
a
little
bit
and
so
that
didn't
make
it
in
we're
going
to
make
sure
that
it
gets
into
1.6.
B
Yeah
this
is
Steve
one
I
was
there
I.
We
had
those
original
meeting
notes
with
a
perspective
agenda.
We
held
a
vote
because
there
were
way
too
many
topics
cover
and
up
voted.
Four
of
them.
I
think
we
got
to
about
two
and
a
half
out
of
our
list
of
four.
So
there
are
some
meeting
notes.
Let
me
see
if
I
can
figure
out
as
a
relatively
recent
zoom
user,
how
to
patch
these
in
I'm
just
going
to
put
them
into
the
meeting
and
jen
and
notes
for
this
week.
A
B
So
we
had
a
lot
of
discussion
of
how
to
come
up
with
a
mechanism
to
support
drivers
going
forward
in
the
long
run,
storage
plugins
and
came
up
with
this
idea
that
there's
a
matrix
of
entry
versus
out
of
tree
and
in
process
versus
out
of
process
and
that
going
forward.
The
goal
is
going
to
reduce
that
matrix
of
four
possibilities
down
to
either
two
or
three,
but
in
the
short
term
it
is
what
it
is
today.
B
So
in
those
meeting
notes,
there's
a
picture
of
the
whiteboard
at
the
very
end
and
a
bunch
of
texts
that
talks
about
it,
I,
don't
think
we
made
a
final
decision
so
there
you
know
in
terms
of
a
plug-in
interface,
the
the
Flex
volumes
are
still
moving
forward,
but
as
a
longer
term
solution,
I
think
flex
volumes
next
generation,
lib
storage
or
some
third
thing
yet
to
be
determined
are
all
potentially
on
the
table.
Here.