►
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
All
right
sure
my
screen.
A
A
So
looks
so
we
got
the
migration
and
the
credential
provider
caps,
both
merged
as
implementable,
so
I
think
like
up
to
a
code.
Freeze,
we're
all
just
working
on
mutation
right
and
it
gets
over
topsy.
Welcome
to
data
before
we
go
into
the
cap.
Implementations
I
did
want
to
highlight
this
one
PR
here.
A
So
someone
opened
a
well
I
asked
one
of
our
community
members
who
is
looking
to
be
a
member
to
who's,
also
developing
the
cloud
stack
provider
to
write
some
docs
on
how
to
do
the
entry
to
external
provider
manually
and
so
there's
currently
a
work
in
progress.
Doc
I
had
recommended
to
to
use
AWS
as
kind
of
the
example
provider.
Just
because
most
of
our
users,
Ronnie
it'll,
be
less
and
it
just
seemed
like
you
know
it
might
as
well
just
use
one
that
has
a
procedure.
A
A
A
Okay,
so
I'll
go
first
with
the
CCI
migration,
so
I
have
a
working
branch
off
of
this
PR
I
opened
a
while
ago.
It's
working,
but
it's
not
like
I,
think
it
needs
to
be
polished
a
lot.
So
we
need
to
agree
like
so
some
things
we
didn't
agree
on
and
the
cap
was
like
the
exact
naming
of
component
flags
and
the
exact
like
the
API
type
for
the
config.
A
B
A
A
C
I'll
tell
you
on
the
GC
east
side,
we've
got
like
five
controllers,
and
so
I
would
like
to
start
compacting
those
down
to
two,
maybe
three
and
so
I
think
at
least
on
my
side.
He
definitely
has
some
value
I.
Think
at
some
point
there
are
one
or
two
controllers.
The
security
team
would
like
to
break
out
so
I
think
there
is
a
lot
of
value
in
keeping
it.
Generic
okay
is.
A
A
A
So
yeah,
like
Tamiya
controller,
make
sense
yeah
because
we're
the
leader
election
part
is
just
the
how
we're
doing
it
and
I
don't
know.
Maybe
we
need
like
I'm
wondering
if,
like
in
the
future,
there's
gonna
be
different
types
to
implement
the
migration
so
then
like
so
maybe
that
can
be
determined
by
the
kind
of
the
config
or
something
else.
I,
don't
know,
Walter
what
you
think
yeah.
C
C
A
A
C
Who's
that,
oh
that's,
the
network,
proxy
right,
sorry
I-
think
we're
doing
pretty
well
on
getting
things
done.
A
lot
of
work
happened
recently,
so
we've
got
a
lot
of
the
load.
Balancing
we've
been
doing
a
bunch
of
perf
testing,
I'm
I'm,
pretty
hopeful
that
we
actually
hit
beta
on
this
in
118,
so
I
mean
there's
still
quite
a
few
fixes
and
I
realize.
We've
only
got
a
couple
of
weeks
left,
but
things
are
looking
pretty
good
and
definitely
a
shout-out
to
to
Patrick,
Chou
and
Geoffrey
for
all
the
great
out
work
they've
been
doing.
A
A
Yeah
I
would
because
yeah
okay,
sorry.
Can
you
say
that
one
more
time
understood
now
I
was
asking
if,
like
we
need
to
feature,
get
that
and
I
think
we
do
like
I
forgot
how
we
like
did
we
decide?
Did
we
already
determine
the
cap?
How
discovering
the
plug-in
mechanism
like
the
plug-in?
It
is
a
big
directory
discovery
and
then
yeah.
D
A
D
D
C
C
I
created
this
repo,
there
is
a
dummy
version
that
will
come
up
with
whatever
caveats
and
then
whatever
is
needed
to
be
done
on.
Kk
is
to
pull
it
in,
even
if
you're
only
pulling
in
the
dummy
is
in
place,
and
then
you
can
iterate
on
that
after
the
code
freeze,
because
it's
a
separate
repo,
but
everything
that
needs
to
happen
in
the
KK
repo
is
done
and
dusted
by
the
code
got
it.
Does
that
make
sense,
yeah.
A
A
C
I
think
that's
the
right
thing
to
do
for
the
for
individual
providers.
I
just
think
it
might
be
nice
to
have
a
reference
implementation
that
is
somewhere
central.
If
we
can
do
that,
I
mean
the
alternate
is
if
you
want
to
make
the
Amazon
your
reference
implementation,
that's
fine
too,
but
I
do
think
that
we
one
way
or
the
other.
We
should
have
an
example
of
what
the
credential
providers
service
looks
like.
A
C
A
D
A
C
With
me,
I
think
the
part
of
its
the
p-doped
people
problem,
but
also
for
us
to
legitimately,
say
it's
alpha
I
think
we
should
have
at
least
one
cloud
provider
or
where
it
works,
and
it
can
be
demonstrated.
So
if
it's
Amazon,
that's
Amazon,
that's
fine.
The
other
cloud
providers
can
use
it
as
a
reference
and
build
their
own,
but
I
think
for
us
to
declare
the
we
succeeded
in
alpha.
We
should
be
able
to
show
that
it
works.
A
Yeah
there's
even
actually
so
I,
don't
know
if
you
guys
know
about
the
harbour
project,
but
I,
don't
I
might
be
able
to
get
someone
on
the
harbour
project
to
implement
like
our
interface
for
harbour,
which
could
also
be
a
nice
representation,
because
it's
it's
C,
it's
a
cloud
agnostic
registry.
So
it.
C
I'm
gonna
beat
the
drum
on
the
e2e
stuff
again
sorry,
but
at
some
point
we
we
really
do
need
to
sit
down
and
work
out.
I
mean
I
realize
we're
several
releases
away
from
the
problem,
but
I
believe
that
it's
going
to
take
several
releases
to
actually
come
up
with
a
solution.
We
can
agree
on
once
the
cloud
providers
are
out
of
tree.
C
A
A
D
A
What
I'd
like
to
do
instead
is
do
live
demos
of
like
us,
showing
users
how
to
migrate
from
entry
to
out
of
tree
for
each
provider
so
that
we
have
like
a
good
recording
of
like
step
by
step
gotten
how
to
do
it
and,
like
part
of
that,
could
be
like,
for
example,
like
while
you
demo,
the
AWS
Bharath,
or
you
can
also
show
switching
from
like
the
ECI
provider.
Entry
to
a
tree
got.
B
A
B
A
B
I
since
Alex
Khan
can't
like
attend
most
of
these
meetings,
he's
based
in
New
Zealand
I've
been
trying
to
like
help
bridge
him
in
so
I.
Don't
know
if
he's
going
to
coop
con
tu,
but
I
will
be
there.
So
hopefully
we
can
figure
something
out,
because
I
think
that
that
would
be
really
useful
for
people
more
than
slides,
actually
seeing
how
it
all
works.
Awesome.
A
So
yeah
like
maybe
what
we
could
do
is
like
yeah.
So
let
me
know
if,
if
you
actually
want
to
come
on
stage
with
us
and
like
do
the
opens
that
part
and
if,
if
not,
you
can
either
like,
you
can
either
help
us
like
make
a
download
video
of
doing
it.
Oh
yeah
give
us
an
environment
and
we
can
walk,
try.
We
could
try
walk
through
it.
Yeah.