►
From YouTube: GMT 2018-06-26 API WG
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
C
C
C
So
to
support
using
store
local
shows
provider
to
create
volume
and
district
volunteer
from
from
okay,
sorry,
so
yeah,
just
from
CSI
bag
storage,
we
introduce
a
new
type
of
storage
source,
not
control
and
have
also
block,
and
then
we'll
introduce
these
operations.
Priya
volume
destroy
volume,
volumetric
o'clock,
they
are
so
called
non
spec
with
the
operation.
That
means
I.
If
you
look
at
the
create
volume
product
like
this,
we
specify
the
source
for
the
week
and
we
don't
specify
the
target.
C
Like
the
outcome
of
that
volume,
we
pass
this
source
to
the
eventually
to
the
storage.
Locker
is
provider,
and
then
it
will
call
the
CSI
jaribg
calls
to
carve
out
the
volume
and
making
can
the
attributes
and
fill
in
the
the
bath
abuse
and
create
new
resource
and
return
in
a
rich
conversion
and
in
master
we
compare
it
to
the
new
type
of
resource
and
then
we
can
offer
out.
So
the
thing
I
especially
want
to
discuss
is
first
this.
So
for
now
creating
support.
C
We
support
creating
okay,
so
these
create
volume
actually
convert
a
raw
disk
resource
to
either
for
now,
so
either
a
mount
or
path.
Disk
resources
and
whether
we
don't
want
to
convert
a
raw
this
resource
to
amount
or
path
is
sped
up
here,
so
we
this
can
only
be
either
amount
of
path
and
and
and
basically
well.
The
circle
will
fill
in
that
the
type
like
based
on
this
field,
but
but.
C
It's
there
like
anger
and
then
because
path
is
suitable,
so
infirmary
can
say:
I
won't
only
use
five
kick
so
I
create
it
like
it
can't
kitty
can
just
cut
it.
Just
got
a
part
of
it
and
use
it,
but
the
real.
The
whole
thing
is
this
time
of
Units.
So
you
need
to
be
attached
to
stages.
You
only
consume
that
volume,
so
you,
the
other
five
five
King,
is
looks
like
free
from
the
message
prospective
the
I
are
very
kind
of
have
normalization
its
high
to
do
agent.
C
So
if
another
ephemeral
caddy
are
the
remaining
of
the
five
cake,
a
papist
and
say
once
you
use
it
another
agent,
then
there
will
be
a
problem,
but
right
now,
in
our
like
resource
up
fraction,
there
is
no
way
to
come
to
you
like
Express.
They
are
some
some
sort
of
correlation
between
these
two
pieces
of
resources.
Right.
D
Let
me
rephrase
what
I
understood
sure.
So
you
said
when
we
create
a
volume
and
the
target
type
is
Pat
mm-hmm
with
an
external
resource
provider.
That's
something
that
we
should
not
allow
at
all,
because
the
path
is
usually
bound
to
an
agent.
Is
that
roughly,
what
you're
saying
or
are
you
saying,
I'm
saying
path
by
definition
in
mrs.
even
is
suitable?
C
D
C
D
In
the
next
general
resource
provider
case,
when
you
ask
it
to
create
a
volume
with
the
target,
a
path
where
is
that
thing
getting
created?
It's
just
an
action:
it's
not
in
any
agent
at
its
create
in
the
external
storage
space
somewhere
right.
It's
not
really
any
agent
any
agent
and
you're
saying
when
framework
wants
to
use
that,
and
then
it's
sent
an
assent
as
an
offer.
You
should
not
be
able
to
use
only
part
of
it
right
the
whole
of
it.
Okay,.
C
C
D
C
Now
something
is
backed
by
a
CSI
marlin,
maybe
in
the
future,
not
now,
but
in
the
future.
Maybe
the
season
plug-in
will
want
to.
We
may
not
like
may
prefer
like.
No
one
should
touch
the
file
system
on
top
of
that
storage.
It
should
all
do
all
the
work
through
CSI
plugin,
maybe
just
this
time-
it's
not
the
reality
right
now,
but
it's
like
it's
kind
of
it.
So
if
we
support
path,
that
means
our
disk
disk
to
you
or
is
that
that
this
view
isolator
have
a
like?
C
A
E
You
know
like
for
some
kind
of
resources
to
use
the
isolate
around
for
other
ones.
You
should
be
a
CSI,
plugin,
Adi
I
said:
there's
a
chance
to
enforce
the
quota.
You
said
it
right
or
what
sorry
like
for
some
for
some
and
resources
you
will
like
the
isolator,
be.
Thank
you.
It's
the
u.s.
order
to
enforce
the
iota
and
for
other
ones
that
I
think
it
should
not
run,
and
it
should
be.
This
year's
idea
does
this
curve.
C
The
crunch
I
changed
her
into
a
plan
knife
he
doesn't
and
he
he's
updating
that
the
sbu
of
a
sizer
did,
but
he
planned
to
not
like
doesn't
couch
path,
is
not
backed
by
CSI
for
now,
okay,
so
and
like
David.
So
I
list
like
to
two
reasons
about
like
a
debate.
This
path
introduced
some
kind
of
issues
or
like
that,
some
issues
when
we
thinking
about
CSI,
so
I'm
thinking
and
and
another
another
reason
is
like
actually
in
being
like
from
our
like
minus
50.
C
C
E
C
C
So
so
I
have
a
discussion
with
other
layers,
guys
creative
stories
recently
and
we
feel
like
it
doesn't
make
love
sin
to
support
path
here.
Right
now,
and
so
we
are
thinking
about.
If
we
about
removing
this
and
and
requiring
that
repeating
that
this
operation
can
only
carve
out
Mount
volumes
and
what.
C
D
Unknown
and
right
now,
if
someone
sends
more
blocker,
you
just
rejected
invalidation
yeah.
C
C
C
And
it
will
also
make
the
API
cleaner
and
then
following
this
I
I'm,
also
such
I'm
also
proposing
if
we
can
chain
this
to
create
mount
disc,
and
this
will
be
destroyed,
mount
disc,
create
block
disc
and
destroyed
block
this.
So
the
reason
of
the
name
change
is
because
we
Ori
I
overload
this
term
volume
in
a
couple
places
now.
So
the
cream
on
here
is
not
a
persistent
volume
but
only
say
create.
C
We
are
creating
a
persistent
model,
so
it's
a
little
bit
like
overloaded
and
and
bake
so
I
feel
like
if
we
rename
this
to
like,
say,
create
mountains,
it
will
be
much
cleaner
in
a
navy
icon
its
concern.
What
do
you
mean?
It's
not
a
persistent
desk,
so
in
the
English
story,
which
I'll
provide
only
create
volume,
it
just
create.
It
says
cop
user
sees
when
Carol
one.
It
is
no
persistence.
Many
data
on
that,
so
the
workflow
is
more
like
reserve.
C
D
C
The
reason
I
think
we
in
the
earlier
discussion
with
Ventimiglia,
so
we
feel
this
is
slightly
better
because
we
are
actually
doing
a
religious
conversion
related
disk,
so
the
resource
type
is
disk
so,
and
so
why
not
just
make
it
like
toilet
disk
and
then
I
I
feel
like
in
the
future
we
can
say
about
is
our
like
something
now
that
the
the
communal
use
volume
on
top
of
like
either
this
type
of
dislike,
root
path,
amount
or
classes?
These
are
volumes,
so
you
create.
C
E
C
Have
like
create
another
another
problem.
Another
problem
I
want
to
do.
The
renaming
is
that
currently
in
a
CEO,
he
already
has
create
audience
which
is
for
this
create
call.
Also
the
thing
this
thing
is
distinguished
that
the
name
is
like
a
mess,
so
I
want
to
like
try
to
make
it
as
clear
as
possible.
I.
C
Is
another
this
is
another
variant
we
can
support,
but
is
the
the
I
think?
The
purpose
of
that
is
that
we
have
a
one
call.
The
problem
is
that
we
need
this
like
document.
Not
only
these
types
are
supported
in
that
parameter
and
when
you
validate
that
and
use
an
interpreter
will
be
aware
of
that
and
the
Vantage
of
the
other
routes
that
we
have
different
different
operation
for
different
types
is
that
is
clear
from
the
name,
but
the
design
has
to
be.
D
Not
follow
that,
so
if
you
have
a
message
we're
desk
and
inside
it,
you
have
in
yeah
that's
a
new
enum
inside
the
create
create
desk.
It's
not.
C
C
C
D
Know
this
mountain
block
mountain
block
inside
it,
and
then
you
select
one
of
those
types
and
then
very
so
if
they
need
the
reason
that
you
want
to
kind
of
distinguish
those
two:
are
they
usually
going
through
the
same
paths
or
are
they
completely
different
functions
and
stuff
like
that?
As
far
as
mrs.
Matsen
agent
are
concerned,
or
are
they
like
or
from.
C
E
C
E
Could
think
of
having
just
one
API
go?
It's
like
you,
have
less
Canora,
t4,
ACLs
or
something
you
got
I,
don't
know
where
that
matters
where
you
would
just
want
to
yeah.
Yes,
that's
what
I
see
downside
say:
I
can
come
up
with
which
I
know
we're
not
finished,
you're,
not
good,
but
so
it's
something
that
would
be
different.
I.
D
D
E
E
C
B
C
C
B
C
D
C
E
You
already
have
some
other.
If
you
have
a
bootable
API
cause,
then
why
won't
you
should
Saturday
already
I
go
instead
of
adding
an
enum
there
yeah
you
could
have
create
volume,
create
disk
I
guess
you
could
have
sorry
create
a
block
right
yeah.
We
have
Priya
block
so
a
future,
if
even
I
mean
mu,
IV
I
go
for
immunity
I.
Instead.
Oh
sorry,
wellness
support
like
if
we
have
separated.
C
D
B
D
I
was
saying
if
we
have
like
a
nested
proto,
the
very
put
in
am
seen
underneath
it
it's
probably
easier
to
do.
Common
validation
for
the
create
this
call
versus
to
a
disco
operation
versus
now
having
different
operations
for
different
types
might
mean
that
we
have
to
try
to
validate
encode
separately
for
each
of
them.
As
we
add
them
week,
you
won't
be
able
to
take
advantage
of
the
common,
create
this
validation,
for
example.
B
D
B
Feel
I
feel
like
both
both
patterns
work
just
as
well,
and
maybe
it's
just
a
matter
of
establishing
a
convention
and
being
consistent
across
the
api's
like
EMM.
To
have
granular
calls
where
we
have
a
separate
call
for
every
action,
or
we
have
very
general
calls
with
lots
of
options
embedded
and
when
I
think.
D
D
D
C
E
C
Now,
for
now
we
are
managing
all
the
parameters
through
sort
of
profiles,
so
there
is
no
need
to
add
like
additional
parameter,
but
I
don't
know.
If,
in
future
we
may
have
a
special
create,
a
function
that
need
to
input
additional
provider,
but
definitely
can
be
honest.
Actually,
those
are
elves
of
snowfield.
You
mean
for
create
for
system
volume
or
for
create
disk,
create
this
one
I'm,
not
sure,
okay
in
volume
here
and
we.
C
C
We.
This
makes
sense
only
if
we
are
growing
a
persistent
volume,
but
for
the
mount
and
block
is
that
backed
by
CSI
plugin.
There
is
a
plan
to
having
new
call
that
can
expand
all
volumes,
so
it's
more
like
a
conversion
that
takes
mount
volume
and
all
disk
and
then
grow
that
mod
into
a
larger,
larger
and
then
restrict
you
precision
model,
but
also
entry,
but
I'm.
Considering
we
just
support
growing
personally
I,
like
just
support,
hold
on
means.
We
support.
E
C
B
C
C
C
B
C
E
C
E
C
C
E
E
E
C
B
I
think
my
feeling
at
the
moment
anyway,
is
that
a
single
message,
kind
of
makes
sense
when
I
think
about
our
other
calls.
It
seems
like
they
tend
to
have
an
action
and
then,
like
one
object
that
you're
performing
that
action
on
and
then
anything
more
specific
in
that
is
in
the
metadata,
like
you
launched
a
task
where
you
launched
a
task
group
mm-hmm
resources
when
it
comes
to
the
particular
type
of
greece's
for
the
particular
metadata
about
your
task
in
the.
C
Call
like
one
small
opinion
I'd
like
to
bring
up
is:
oh
I'm,
not
so
I
didn't
formally
confirmed
with
James
yet,
but
it
seems
he
preferred
a
way
to
have
like
when
you
use
ap
I
prefer
to
have
shorter,
like
exit
path.
What
I
mean
is,
instead
of
like
operation,
dot
craven
dot,
whatever
Tarwater
there
was
a
dot
copy
from
something
is
seen.
Well
he's
mine
is
four
seven
like
he
thinks.
Probably
that's
our
overall
access
path
is
easier,
basically
is,
is
Kim
cleaner
for
API
comes
ran.