►
From YouTube: Config WG Meeting 11/29/2018
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
Welcome
just
I
could
have
agenda
item
for
the
long
long
plans
for
galley
based
on
the
new
East
your
one
month
plan.
So
you
still
want
one
is
gonna
ship
sometime
in
January,
so
and
I
think
it's
like
a
baby
female
a
for
the
debut
of
galley
I
think
we
can
do
more
work
within
galley,
both
in
terms
of
production
cessation.
You
know
making
it
more
stable,
as
well
as
adding
features
that
might
be
missing
so
I
think
they're
gonna
have
a
discussion
of
what
this
and
it's
you
see
meeting
tomorrow.
A
I
think
the
the
primary
outcome,
or
the
primary
thing
that
we
want,
is
to
enable
galley
by
default.
So
that
will
be
the
primary
mechanism
and
I
think
what
we
want
to
push
for
is
actually
start.
Maybe
doing
the
service
discovery
implemented
in
galley
as
well
like
the
the
endpoint
ingestion
to
be
implemented
in
jelly
as
well,
but
we
can
possibly
make
it
all
pop.
So.
B
Well,
have
knobs
for
all
these,
so
it'll
be
a
it's
a
flip
to
use
mCP
and
most
of
us
in
this
our
pilot
and
make
sure
it's
organic.
You
stood
up
and
it
could
serve
all
sorts
of
serve.
Endpoints
you
can
serve
cafe
goes,
nobody
consumes
it.
It's
not
less
risk,
especially
what
we're
doing
today.
Even
if
you
turn
off
NCP
the
hell
option,
at
least
oh
they're
all
ready
to
serve
traffic,
as
somebody
asked
for
it
I'm.
B
Certainly,
what
we're
talking
about
is
is
a
sort
of
bit
for
pilots
that
AB
it's
what
makes
in
to
say
what
configuration
they
want
to
get
from
galleon
what
they
want
to
get
one
of
these.
So
if
we
have
those
bits
in
place-
and
we
have
it
to
mention
properly
so
reaches
use
your
config
in
endpoints-
that's
the
two
bits
pilot
and
maybe
make
sure
it's
just
difficult.
Ok,
so
what's
there
now
and
those
components,
then.
B
Can
okay
think
it
can
fake
they
can't
get
in
place?
And
it's
and
it's
a
single
bit
for
pilot
hand
mixer
exposed
to
help
yeah.
Obviously
you
can
go
down
and
you
can
customize
that
so
I
want
make
sure
to
get
from
kubernetes
and
if
they
get
from
Galilee.
But
as
long
as
we
have
the
right
level
of
bits
exposed-
and
we
can
say
these
are
the
defaults
and
with
some
recommendations
about
if
we
want
to
turn
them
off
based
on
your
particular
deployment.
Okay,
so.
A
B
Might
be
more
than
two
bits
depending
on
how
what
load
so
the
load
for
user
author
config
is
pretty
low
in
Galway
I'm,
not
sure
what
the
load
for
end
points
will
be
on
gala.
If
we
need
to
turn
that
off,
unless
we
characterize
it,
we
know
that
galleys
not
gonna
consume
excess
amount
of
resources
sure.
But
that
means
the
bit
is
also
consumed
by
Delhi
the
end
points,
but
at
a
top
level,
okay,
it
could
be
the
same
one
at
any
lower
level.
B
C
A
B
That's
why
I,
depending
on
what
the
migration
path
is,
so
we
hadn't
one
thing
when
we
forget,
if
it's
gonna
be
on
by
default,
we
need
to
work
out
the
migration
path
yeah,
so
we
had
originally
not
been
well
we're
not
planning
to
do
that,
because
there
was
not
a
thing
for
alpha.
If
we
say
it's
gonna
be
beta,
then
we
need
to
work
through
that
and
besides,
is
there
one
bit
or
are
there
two
bits,
so
you
roll
it
out
shake
with
galilei
with
all
these
extra
features?
Okay,
that's
stable!
A
B
So
so,
how
many
will
not
I
would
not
expect
tell
them
to
provide
any
thing
now.
It's
gonna
be
just
everything
goes
hope
for
the
best
in
the
future,
and
when
this
operator
that
we're
planning
is
developed,
then
we
could
have
a
single
bit
which
says,
use
and
use
this
feature,
and
there
could
be
some
orchestration,
but
we
can't
rely
on
that.
Yes,
so
we
have
decide
whether
maybe
it's
sufficient.
If
this
is
throw
everything
at
the
wall
and
let
it
resolve.
B
The
sect
that
will
be
well,
this
will
be
a
disruption
in
that
I
said,
depends
on
how
we
upgrade
so
if,
if
we
set
up
things
properly
so
that
we
do
a
true
rolling
update
with
pilot,
the
old
pilot
wouldn't
stop
until
the
new
ready.
Your
pilot
is
ready
and
if
we
can
say
that
the
new
pilot
is
not
ready
until
we
can
get
endpoint
data
and
user
can
fare
from
Galilee,
then
there
then
we
might
be
able
to
sequence
things
that
way,
fit
that
so
we're
still
using
the
old
pilot.
B
D
B
B
B
Should
just
work
if
we
get
all
the
readiness
tests
in
place,
we
have
some
minimal
readiness
text
now,
a
pilot
will
not
I
won't
indicate
that
is
ready
to
kubernetes
and
it's
not
ready
to
receive
traffic
until
it
gets
some
indication
from
galley.
We
need
to
verify
that
we
did
that
indication
that
galley
provides.
The
pilot
is
sufficient.
A
B
One
if
we
yeah,
if
we
didn't,
do
a
full
sync,
we
thought
we
had
a
complete
view
of
the
world
and
we
then
propagated
that
to
pilot.
So
Pilate
was
unready.
Then
you
could
have
a
gap.
I,
don't
know.
If
that's
a
real
problem,
we
need
to
test
it,
and
if
it
is
a
problem
then
we
might,
we
need
to
fix
it
and
that
fix
might
include
propagating
up
the
explicit
per
component
bit.
A
A
B
B
B
A
B
A
B
B
Up
mode
is
reversing
the
direction,
so
the
the
use
case
is
today.
The
source
of
district.
The
source
of
configuration
is
the
server
the
destination
is
the
client,
so
that
mostly
works
in
kubernetes.
But
if
you
wanted
to
have
a
more
distributed
architecture
where
you
have
a
like
a
hub
cluster,
that's
running
pylon
and
galley
and
spoke
clusters
that
are
behind
firewalls.
You
mean
might
need
to
reverse
the
direction
so
that
the
hub
and
reach
the
spoke.
B
E
B
B
A
B
A
A
Mcpon
by
default
that
will
be
the
highest
priority.
Its
beta
little
quality
service
discovery
support
with
alpha
level
quality
of
body.
That's
the
second
priority
item.
It's
actually,
we
need
to
make
ensure
that
the
quality
release
quality
is
in
place
for
these
things,
and
that
stretch
is
the
dialogue
stretch.
Number
one
is
the
dialogue
more
than
stretch
number
two
is
the
incremental
density
for
service
discovery,
yeah
and
number
two
would
be.
B
You
mean
four
days
ago
right
for
number
of
services,
number
of
end
points
and
and
roughly
then
there
were
eight
types
of
configuration:
they're
writing
for
service
yeah.
Presumably
the
preferred
group
has
this:
I
know
that
Cloud
Foundry
has
done
some
testing
and
they've
gotten
pretty
high
in
there
they're
running
into
some
there
they're
having
to
play
around
with
chair
PC
method,
size
right
now,
so
something
more
like
that:
okay,.
B
A
B
A
Late,
okay,
so
here
is
an
example,
so
this
is
my
head
tests
thing
that
I
did
so.
You
can
actually
specify
metadata
here.
That
says:
oh
like
this
is
a
community
is
custom
lease
or
suspect
its
namespace.
This
is
this
group.
This
is
version.
This
is
kind
and
by
the
way,
this
is
just
something
very
basic
speaking.
We
can
actually
make
it
more
richer
and
I'm
from
the
same
proto.
We
can
produce
multiple
different
CID
definitions
or
versions.
A
That
was
a
file
we
love
this,
which
actually
much
better
okay
right,
so
this
is
kind
of
the
IMO
file
that
gets
generated.
So
this,
like
is
a
CIT
definition
that
is
very
similar
to
what
we
have
in
the
repo.
Then
the
one
big
difference
is
now
we
had
the
well
Dacian
portion
filled
up,
it's
open,
API
is
dimma
bays
mo
right
and
it's
based
on
the
structure
of
the
photos
themselves,
so
this
is
gonna
come
and
even
when
we
do
like
versioning
or
build
Asian
API
server
level,
it's
something
very
basic.
A
Just
does
something
very
structural.
In
addition
to
this,
it
actually
ends
up
creating
this
file.
This
actually
acts
as
an
input
to
the
to
native
code
generator
right,
so
we
create
oh
there's,
a
basic
type
that
actually
has
title
meta,
an
object,
meta
and
then,
if
there's
a
spec
portion,
which
is
essentially
the
actual
contents
of
the
the
proto
itself
here
right,
so
it's
fairly
straightforward,
fairly
basic
and
from
here
we
can
generate
the
rest
of
the
client
library.
I
mean
this
is
this
is
probably
something
that's
gonna
take
a
week
or
so
to
come.
B
Crafted
and
they
were
doing
with
some
issues
with
one
out
and
JSON
PD.
So
if
we
can
get
I
think
so,
there's
another
group
that
was
doing
something
somewhere.
If
we
can
get
this
poem
through
with
a
single
type
and
then
maybe
trying
to
get
them
to,
we
can
all
work
on
the
same
thing
we
can
get
it
pushed
into
API
yeah.
So
my
seems
to
be
the
matter
of
cycles
to
get
right.
A
So
this
is
essentially
I
mean
this
is
a
prototype,
I
mean
and
I'm
sure
we're
gonna
run
into
like
many
wonderful
H
cases
as
we
make
progress.
I
was
maybe
pushing
this
into
the
tools
you
pull
and
then,
like
you
know,
like
pointing
people
to
this
thing
of
hey.
You
know,
let's
try
to
work
on
this,
but
it's
not
completely
a
time.
It's
just
like
your
basic
prototypes
level.
What.
B
A
That's
just
the
api's,
so
yeah
I
mean
you
need
to
do
the
basic
wiring
so
that
you
know
you
can
deal
with
like
you
know,
change
the
code
here
and
then
you
can
do
it
like
quick
iterations
with
the
rest
of
the
code.
But
it's
not.
This
is
not
even
there.
You
try,
so
this
I
mean
this
doesn't
handle
like
innermost
one
offs
or
or
any
of
the
more
interesting
stuff
right
yeah.
A
A
Yes,
so
this
is
a
very
low
prior
to
thread
for
me
at
this
point.
So
if
somebody
wants
to
pick
this
up
or
like
you
know,
help
with
it,
that
would
be
great
and
I
can
direct
it.
So
like
we
do,
you
want
to
add
what
you're
already
safe,
actually
on
our
side
is
adding
production
real
date
right,
which
actually
annotates
proto's
with
json
schema
like
expressions
as
well,
so
we
can
actually
make
them
work
within
the
validation
code,
visible
so
that
that's
my
office
go
Ashley.