►
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
Hi
all
welcome
to
the
monday
june
15th
or
if
you
happen
to
be
in
other
parts
of
the
world,
tuesday
june
16th
sub
project
meeting
for
the
azure
cloud
provider-
and
this
is
a
meeting
conducted
under
the
cncf
code
of
conduct.
It
is
being
recorded
and
will
be
posted
to
youtube.
Later.
A
I
think
brief
is
a
understatement
for
how
few
agenda
items
there
are.
Maybe
we
should
talk?
Actually,
I'm
gonna
add
an
agenda
item
we're
talking
about
how
we
do
a
better
job
of
building
an
agenda
and
get
ideas
for
that.
We
can
maybe
start
there
if
there
aren't
other
things,
but
first
actually,
let's
just
welcome
everybody
here.
I
actually
don't
know
you
shabbana.
Do
you
mind
introducing
yourself
and
let
us
know,
sort
of
what
your
interest
is
in
the
azure
cloud
provider.
A
Great
well
welcome.
Thank
you
appreciate,
appreciate
you
joining
so
feel
free
to
ask
any
questions
about
anything.
That's
not
clear
or
feel
free
to
just.
B
B
A
B
So
I
I
interested
in
this
provider
asa.
A
Okay,
so
you'll
probably
be
better
off
attending
the
cloud
provider.
Bi-Weekly
call
yeah,
which
is
general
to
all
of
the
cloud
providers.
This
one
is
very
specific
to
how
we
adapt
that
cloud
provider
to
use
the
azure
infrastructure
as
a
service
apis.
The
vms
that
works
in
storage.
A
So
yeah
so
there's
a
cloud
controller
manager
and
that
cloud
controller
manager
kind
of
determines
what
needs
to
happen
from
the
kubernetes
cluster
configuration
and
then
the
cloud
providers
then
make
that
happen
on
the
individual
cloud
infrastructures.
A
And
so
there
are
kind
of
two.
I
don't
have
time
to
do
the
whole
thing,
but
there
are
basically
two
types:
there's
the
entry
cloud
provider
which
azure
and
aws
and
google
and
vmware
had
all
implemented.
There
are
then,
the
later
cloud
providers
that
joined
that
are
called
out
of
tree
cloud
providers
and
all
of
us
entry
cloud
providers
are
in
the
process
of
moving
from
being
in
the
kubernetes
tree
to
out
of
tree
for
the
implementations
for
how
we
actually
interface
with
the
underlying
cloud
infrastructure.
A
So
I
we
can't.
I
can
share
a
couple
of
links.
If
you
want
to
send
me
a
slack
message:
I'm
just
craig
l,
peters,
yeah,.
C
So
I
just
added
an
item
about
color
provider.
So
during
the
last
few
weeks
we
are
working
together
with
a
few
teams
from
club
providers
like
and
moving
the
controllers
from
original
cool
control,
cognitive
repo
into
a
separate
ripple.
So
after
this
work,
all
the
controllers
from
cognitive
repo
would
be
easily
consumed
from
outer
cheek,
like
proper
error.
So
in
the
future
we
want
to
avoid
the
vending
packages
from
cognitive
director.
We
want
to
vendor
only
vendor
the
package
from
sub
projects
from
the
repos
built
from
digging
directory.
C
The
kia
had
been
murdered
so
next
week,
our
checklist
of
manager.
We
we
could
render
that
into
our
repo
and
check
whether
we
could
simplify
the
the
vendor
updates
in
our
repo.
A
C
A
C
So
because
of
the
speeding
and
the
the
virtual
linking
in
kuni
ripple,
it's
very
hard
to
do
the
good
mode
update
today.
A
Yeah
that
will
simplify
a
lot
of
things
for
maintenance
for
sure.
Is
there
a
an
issue
in
the
backlog
for
updating,
gomod.
C
If
not
so
I
think
we
could
just
use
the
original
eclt
track
this
work.
This
is
actually
part
of
our
train,
color
provider.
C
And
also
another
thing
we
are
working
recently
is
improving
the
union
test
coverage
for
cloud
provider.
So
if
you
check
out
project
border
and
check
the
sound,
the
the
thumb
panel,
you
you
could
find
a
lot
of
pr
mode
recently,
including
united's
coverage
improvements
for
for
my
name,
irs
basic
files.
C
C
C
Yeah
so
the
cast
of
the
prs,
I
think
in
the
down
panel,
and
we
still
have
some
some
more
still
working
on.
So
when
we
add
a
new
prs,
I
would
implement
into
our
project
board.
A
Okay,
great,
so
what
is
the,
I
guess
are
any
of
these
sort
of
targeted.
A
C
A
D
And
there's
also
an
update
from
my
site:
azure
disk
csi
driver
migration
goes
better
in
1
2019,
so
azure
disk
micro,
the
migration
of
the
driver,
examination
yeah
and
for
the
edge
of
fire
since
says.
Do
we
need
to
add
some
magazine
tests?
So
it
also
remains
in
alpha
in
the
in
1.19
and
we
are
going
to
add
some
automatically
the
same
side
vibration
test
for
the
identifier
and
once
that's
done.
I
think
it
could
be
better
in
1.20.
D
D
Your
country
is
for
the
migration
part.
We
we
only
had
some.
We
have
only
added
some.
I
mean
we
see
only
manual
tests
because
there's
a
blocking
issue.
We
we
have,
we
have
already
fixed
in
1.19,
but
it's
nothing.
It's
not
merged
in
the
some
side
class
of
the
idle
fire
csrpaline,
so
yeah,
it's
blocked.
A
Okay
blocked,
and
so
what.
D
Yeah,
when
when
the
non-19
was
released,
a
will
be
released
and
we
will
use
the
latest
side
card
for
the
id5
csr
driver
and
then
the
marketing
will
work
and
then
we
will
add
some
and
automation
tests
for
the
azure
file
system.
Migration
feature.
A
C
Got
it
okay
and
another
thing
is
about
the
external
registry
credential
provider,
so
they
the
pr
working
on
this
cap,
but
there
are
no
updates
recently.
So
I
I
just
depend
the
pr
author
and
the
cloud
provider
owners.
I'm
not
sure
whether
this
is
your
blind
as
at
this
release,.
A
No,
I
do
not.
I
have
missed
the
last
two
cloud
provider
extraction
meetings.
Unfortunately,
okay,
so
I
do
not
did
you
ping
only
in
the
pr
or
did
you
also
ping
on
slack.
C
I
I
just
pinned
on
the
pr
I
didn't
pin
under
select.
Yes,.
C
So
I
think
originally
this
year
should
be
finished
with
him
when
I
did
recycle
right.
A
Yeah,
if
you,
if
you
don't
hear
back
anything
and
you
want
me
to
reach
out
to
andy
andy
or
chef
taco,
I
can't
remember
his
first
name.
A
Yeah,
so
if
you
wouldn't
mind,
let's
wait
one
day
and
then,
if
you
don't
hear
anything,
unfortunately,
my
github
notifications
are
crazy.
If
you
could
just
ping
me
in
teams
or
slack
and
then
I'll
reach
out
to
them
during
working
hours
here
in
the
us.
C
D
Okay,
so
and
another
thing-
maybe
it's
not
related
to
the
compromise.
I
also
started
a
new
project.
On
the
kubernetes
side,
it's
called
the
csi
java
smb
gyro,
and
it's
actually
it's
booked
by
folks
from
the
id5
csi
driver.
It's
mainly
focused
on
the
model
more
generic
smb,
because
we
currently,
we
only
have
the
you
know
before
we
only
have
the
smb
effects
volume
driver
and
the
community
wants
smp
more
common
smp
csi
java.
So
I
started
that
project
and
we
already
released
an
alpha
feature.
D
D
A
D
Yeah
yeah,
I
already
provided
a
link
and
yeah.
It
should
work
on
both
the
linux
node
and
the
windows
note.
So
it
will
not
only
benefit
the
the
either
users
microsoft
products.
It
was
also
benefits
the
community
yeah
great.
Do
you.
D
And
we
are
going
to
enable
that
actually,
we
only
have
the
unit
test
and
now
we
are
adding
the
test.
And
finally,
we
will
add
the
entire
test
and
I
think
when
we
have
the
action
test,
we
can
yeah,
we
can
reach
better.
That's
the
calculator
alpha
and
some
users
are
already
trying
that.
A
Excellent,
and
so
what
this
means
is
that
I
would
be
able
to
mount
an
smb
file
server
on
the
lytics
host.
D
Yeah,
it
works
also
works
for
azure
azure
file,
because
that
file
is
actually
smb
java
smb
using
smb
protocol
yeah,
okay,.
A
D
For
user
for
photo
users
already
using
id5,
I
think
they
need
to
say
they
can
use
sfi
driver,
it's
more
convenient
for
them,
but
the
other
also
other
users.
They
are
using
on-premise
smb
server
and
they
can
use
this
csi
gyro
and
also
there
are
some
users
using
on-premise,
kubernetes
cluster.
Yes,
they
cannot
use
amplifier,
they
need
to
set
up
the
smb
server
and
then
yes,
they
can
use
this
style
yeah.
It.
D
A
I
understand
well,
maybe
maybe
ernest
or
hello,
that's
an
interesting
thing
for
you
to
explore.
I
don't
know
I
don't
have
to
figure
out
what
what
these
things
do.
It
could
be
an
interesting
way
to
to
get
familiar.
Yeah
yeah.
D
A
Yeah
lucky,
congratulations
well
done
and
I'll
actually
share
that
with
some
of
the
other
teams
here.
That
might
be
interested
fantastic.
A
D
I
think
one
maybe
usually
is
that
actually
we
don't
have
so
many
work
items.
I
mean
cloud
provider,
azure
is
country
stable,
I
mean
a
stable
projects
and
we
me
mainly
because
we
don't
have
so
many
work
items
and
yeah.
Sometimes
we
we
don't
have
any
candy
and
yeah.
A
D
D
I'm
using
the
provider
azure
tag,
but
if
you
look
at
other
other
texts
from
the
kk
repo,
I
don't
think
there
are
a
lot
issues.
Okay,
yeah
I
haven't
looked.
A
A
Anybody
else
have
any
other
ideas,
or
should
we
do
it
like
yeah,
because
one
that
one
possibility
is
that
we
leave
it
scheduled
every
two
weeks,
and
if
there
are
no
agenda
items,
then
I
just
cancel
the
meeting
and
we
can
rely
on
the
slack
channel
and
email
distribution
list
to
resolve
issues.
A
A
D
Yeah
from
the
quiet,
I
believe
that
just
leave
it
the
way
it
is
yeah.
I
agree
we
can
first
a
few
in
the
agenda
before
before
this
meeting
happens
and
if
there's
no
agenda,
I
think
we
can
skip
the
meeting
yeah.
Okay,
that
sounds.
A
So
you've
seconded
that
approach,
hey
faye,
do
you
have
a
strong
opinion.
C
I
agree
with
with
both
of
you,
so
I
think
we
could
try
to
figure
out
the
agenda
before
the
meeting
and
the
name
decide
whether
we
want
to
cancel
or
if
there
are
no.
No,
no
idea
to
talk
about.
A
That
sounds
good,
okay,
so
I'll
continue
to
prompt
in
the
slack
channel
for
agenda
items
and
then
two
weeks
from
now,
if
let's
see
one
day
beforehand,
if
there
are
no
agenda
items,
then
I'll
cancel
the
meeting
yeah
I'll
make
that
decision.
Actually
I
probably
end
up
not
being
one
day
before,
because
that's
a
sunday
here,
I
probably
figure
that
out
on
the
monday
morning,
when
I
get
into
the
off-
and
you
know
to
my
computer
working-
does
that
make
sense.
A
Okay,
we'll
do
that.
A
Okay,
great
well,
thank
you
guys
for
coming.
I
will
post
the
recording
by
tomorrow
and
have
a
great
day
there
in
china
and
shimano,
I'm
not
sure
where
you
are,
but
we'll
have
a
nice
evening.
Earnest
tonight.