►
From YouTube: CNCF Service Mesh Interface 2020-11-11
Description
CNCF Service Mesh Interface 2020-11-11
A
Your
fingers
very
good,
okay
cool,
so
welcome
everyone
to
our
bi-weekly
smi
community
meeting.
If
you
haven't
yet,
please
add
yourself
to
the
attendee
list,
and
with
that,
do
we
have
any
anyone
new
on
the
call,
nothing
for
sure
yeah?
Do
you
want
to
introduce
yourself.
B
Yeah,
yeah,
hey,
hey
everybody,
my
name
is
matt
yakabuchi.
A
lot
of
people
call
me
booch,
so
I
think
you
might
have
seen
some
of
my
messages
out
there.
So
I'm
working
with
nginx
and
so
we've
just
released
nginx
service
mesh.
It's
now
public.
It
was
a
little
bit
behind
a
wall
for
a
little
while,
but
now
that
we're
public
we're
trying
to
reach
out
to
the
community
and
and
be
and
be
better
members,
we've
got
all
the
legal
stuff
smoothed
out.
B
We're
able
to
contribute
both
to
smi
spec
and
smi
sdk
go
so
that's
all
good.
The
whole
team
is
is
ready
to
go
and
from
an
nginx,
bu
and
f5
perspective.
We're
ready
to
engage.
So
I
just
wanted
to
say
hello
and
I'm
going
to
try
and
be
a
semi-regular
member
to
these
to
these
meetings.
A
That's
awesome
very
warm
welcome,
and
it's
really
great
to
hear.
Do
you
maybe
want
for
next
time
or
whenever
you
plan
to
try
and
again
give
a
quick
demo
or
or
walk
us
through
a
little
bit.
B
Yeah
yeah
yeah,
that
sounds
that
sounds
great.
We're
still
trying
to
work
through.
Some
of
you
know
our
understanding
and
we
want
to
collapse
on
certain
understandings
around
the
specifications.
So
yeah
yeah
I'd
I'd
love
to
give
a
little.
You
know
five
minute
presentation
on
it.
A
Awesome,
and
can
I
also
ask
you
to
if
you
click
on
that
link
that
both
lee
and
also
bridgette
now
again
shared
to
add
yourself
there
just
saying
your
name
and.
B
C
B
It
is
smi
compliant
yes,
and
so
we're
up
to
all
the
latest
versions.
We're
shy
on
some
of
the
smi
metrics.
So
we
don't
support
every
resource.
That's
called
out,
but
we
have
stateful
sets.
Daemon
sets
deployments,
pods
and
name
spaces
I
think
is,
is
what
we're
limited
to
right
now.
A
That's
excellent
and
let's
make
sure
that
you
are
listed
on
on
our
web
page
there
right.
Yes,.
B
And
I
do
want
to
get
listed.
We
have
a
little
bit
of
an
embarrassment,
though,
with
circuit
breaker
in
rate,
limiting
there
was
a
miscommunication
or
misunderstanding
with
the
team
on
how
those
should
have
been
namespaced.
We
do
want
to
talk
to
you
guys
about
proposing
them
going
forward.
It
always
should
have
been
in
our
organization,
so
I
don't
want
to
communicate
that
until
maybe
next
week
I
could
send
you
guys
a
pull
request.
A
Awesome
perfect
thanks
for
that
yeah!
Yes,
oh
yeah,
richard!
Thank
you
very
much.
She
just
shared
the
link
up
to
add
your
logo,
the
fragment
in
the
in
the
repo
there.
If
you
just
follow
that
cool
thanks
a
lot.
D
E
A
Introduction
of
nginx
that
I
I
didn't,
I
didn't
really
see
that
I,
but
yes
thanks
a
lot
I'll
just
make
a
minor
correction
and
awesome.
So
are
we
good
to
go
to
tyrone's.
D
D
D
Yeah,
so
the
meeting
november
25th
would
be
one
day
before
us
thanksgiving
and
even
with
the
pandemic.
E
D
Certainly
have
like
family
obligations
around
that
time.
I
know
I'm
off
work
that
week
because
I
took
vacation
then
and
then
the
meeting
december
9th
would
be
fine
and
then
the
december
23rd.
One
again,
I
think
people's
vacation
schedules
might
might
be
such
that
it
would
be
very
difficult
for
us
to
have
an
effective
meeting.
So
my
proposal
is,
we
meet
december
9th
and
then
we
go
back
to
normal
january
6th
and.
A
Right
but
we
do
have,
we
do
have
these
topics
so
exactly
exactly
so.
Maybe
if,
if
anyone
like,
are
there
any
objections
regarding
the
cancelling
25th
and
kensington
23rd
december,
and
essentially
we
have
then
more
or
less
one
more
meeting
this
year
and
then
back
to
normal
january
6
right,
that's
the
bottom
line.
A
Sure
it's
like
github
issues.
Everything
goes
on
just
the
bi-weekly
meetings,
as
suggested
by
brit.
Okay,
then,
let's
record
that
25
is
cancelled.
23Rd
is
cancelled,
which
means
we
have
one
more
meeting
in
2020.,
it's
more
more
than
enough
for
2020
2020
doesn't
deserve
that
much
anyways.
Wasn't
that
good
cool!
Then
we
get
to
these
good
news
regarding
next
week.
G
Yeah
yeah
yeah
yeah
good,
good
news.
The
what
brizzy
has
written
here
is
accurate,
which
is
to
say,
I
think
it
yeah
it's
about
a
45
minute
long
slot
on
toward
the
evening
on
this
coming
tuesday
for
well
asmr.
You
know
all
things
smi,
I
guess
the
so
everyone
here
is
welcome
to
come
and
either
answer
questions
or
ask
questions
we'll
see
who
all
shows
up
to
so
it
would
be
assumed
that
we
would
join
of
the
ones
that
I've
hosted
like
this.
G
In
the
past,
it
has
been
helpful
to
generate
conversation
to
just
to
have
a
cup
a
slide
or
two
or
four
or
or
a
deck
in
the
background
that
that
when
people
don't
know
what
questions
they
have,
you
sort
of
bring
up
a
slide
talk
about
something
that's
new
or
that
that's
going
on,
and
that
generates
more
questions,
and
so
I
guess
yeah.
So
I
guess
the
thing
here
is
those
that
are
interested
in
inserting
a
slide
into
a
deck.
G
G
I
think
my
words
are
failing
me
today,
but
you
know
where
I'm
going
with
this,
so
some
it
would
be
good
to
yeah.
You
know
just
the
general
just
the
stump
speech
so
to
speak,
slides
also,
if
that
we've
got
relatively
new
things
coming
up
or
or
things
like
nginx
service
mesh
being
sort
of
yet
another.
A
G
A
G
A
G
Yeah,
that's
correct
yep
at
that
url
there's
a
pre-published
zoom
link,
so
I
don't
know
that
entirely
how
that
works.
If
people
actually
have
to
register
for
kubecon
to
be
able
to
get
into
it,
but
but
there's
a
cncf.
D
A
A
G
This
I'll
I'll
put
a
link
to
the
deck,
probably
I'll
go
grab
a
couple
of
things.
Lockhee
and
others
have
certainly
got
a
lot
of
good
fodder
out
there.
For,
for
it
and
I'll
ask
for
feedback
and
and
massive
editorial
review,
I
guess
it
didn't
have
to
be
much.
It
really
isn't
the
presentation
it's
more.
Just
like
hey
did
you
know
when
nobody
has
a
question,
it's
just.
A
G
D
A
I
just
imagine
that
like
for
me,
for
example,
that's
10
pm,
that's
still,
okay,
but
if
you're
like
central
europe
or
you
know
even
more
eastern
or
I
don't
know
for
asia,
it
might
just
be
too
late,
so
people
might
just
want
to
watch
the
recording
right.
That's
why
I'm
I'm
wondering
cool
then
thanks
a
lot
again
and
let's
move
on
to
the
next
one
richard
you
put
that
down,
but
that's.
D
I
did
and
I
saw
john
joined.
I
know
michelle
wasn't
able
to
join
this
call
today,
but
john,
I
see
michelle
extended
it
for
one
more
week
seeking
feedback
is
there
anything
people
should
know
if
they're
gonna
fill
that
form
out
to
offer
smi
metrics
feedback.
E
I
think
the
doc
does
have
a
pretty
good
description
of
what
we're
looking
at
for
that.
So
I
would
just
take
a
look
at
the.
A
Dock.
Okay-
sorry,
sorry,
I
didn't
mean
to
interfere
with
your
subscribing
there,
because
now
that
actually
makes
sense
to
handle
it
here.
I
don't
know
if
you
had
a
chance
in
that
context.
The
the
open
telemetry
issue
199..
So
we
got
someone
from
the
open
telemetry
community
just
in
there
commenting
on
it
offering.
So
if
you
click
on
that
199,
you
see.
I
commented
on
that.
I
had
a
conversation
with
them
over
on
gitter.
They
still
using
gitter.
A
I
guess
moving
to
slack
as
well
at
some
point
in
time,
so
I
would
think
that
as
soon
as
we
have
wrapped
up
the
previous
one
that
the
google,
dr
john
shared,
we
might
be
able
to
get
back
either
invite
justin
for
a
conversation
or
or
share
that
google
doctor
I'm
saying
okay.
This
is
where
we
are.
At
least
that
was
my
thinking
there.
A
So
I
really
appreciate
that
they
were
really
super,
open-minded
sense.
Okay,
what
do
you
need
right?
What
kind
of
semantic
conventions
or
whatever,
and
then
we
probably
just
need
to
communicate?
You
know
here
would
be
our
proposal.
A
G
Question
question
michael
in
your
mind,
is
this:
is
this
more
about
compatible
semantics
and
conventions
or
is,
or
is
this
also
inclusive
of
potential
in
because
the
word
instrumentation
is
mentioned
in
there.
A
E
A
Do
or
expose
or
or
capture
the
rest.
There
is
still
this.
You
know
on
the
wire
like
what
happens
with
open
metrics
will
metrics
be
adopted
by
hotel
metrics
as
the
wire
format,
et
cetera,
et
cetera,
where
I
think
we
from
the
smi
perspective,
we
might
have
an
and
you
know
an
opinion
on
that
or
an
input,
but
we
don't
really
own
that
right.
A
I
guess
it's
more
like
what
is
the
like
working
backwards
from
what
would
be
the
idle
situation,
someone
using
hotel
as
the
the
standard
is
able
to
instrument
an
smi
compliant
mesh
and
gets
out
everything
you
know
compliant
to
to
the
standard.
That
would
be
the
idle
case.
Right
and
semantics
to
me
are
the
kind
of
like
low-hanging
fruits
right
that
that's
something
that
doesn't
cost
a
lot
right.
Everyone
is
like
fine,
it's
just
a
convention
and
the
rest
is
essentially
up
to
everyone
to
implement.
A
Then
right,
if
you
are
buying
into
that,
if
you
think
like
yes,
I'm
gonna,
you
know
write
an
exporter,
I'm
gonna
write
something
in
the
sdk
or
whatever
in
hotel.
Then
you
know
that's
up
to
you,
but
I
think
that's
what
we,
I
think
for
our
smi,
implementers
or
or
people
who
actually
provide,
as
my
compliant
meshes,
want
to
provide
us
a
guidance
or
give
us
a
guidance.
I
guess
at
least
that's
that's
the
way.
I
see
it,
I'm
not
sure
if
everyone
agrees
with
that.
G
It's
helpful
that
well
thank
you
for
thinking
about
that
out
that
out
loud
and
then
I'll
progress
with
another
question,
though,
about
where
you
can
do
the
same
thing,
which
is
in
your
mind,
would
this
be?
Do
you
consider
that
this
might
be
additive?
The
like
an
additive
to
the
existing
metric
spec,
in
which
it's
optional
for.
G
A
A
I
do
believe
that
you
know
looking
at
different
specifications
or
future
standards
within
cncf.
It
would
make
a
lot
of
sense.
If
you
know
we,
we
support
each
other
right
like
if,
unless
there's
a
really
good
reason,
why?
Why
should
we
not?
But
I
also
see
that
kind
of
like
backwards,
competition
compatibility?
A
That
might
be
an
issue
right,
so
I
don't
really
have
a
strong
opinion
that
other
than
I
would
wish
everyone
going
forward
would
simply
commit
to
hotel
and
say
like.
Oh,
we
we
gonna,
implement
that
standard,
but
I
think
we
can
only
give
a
recommendation
there
and
saying
like
if
you
decide
to
adopt
hotel
in
your
implementation,
then
here
is
you
know,
for
example,
the
semantics
that
that
we
suggest
to
use,
rather
than
coming
up
with
your
own.
I
don't
think
that
we
can
like
make
that
a
requirement
or
force
anyone.
A
G
G
I
do
well
yeah
well
or
yes-
and
I
was
sort
of
saying
it,
tongue-in-cheek,
with
respect
to
the
smi
conformance
effort
to
go
over
and
verify
that
also
like
oh
yeah.
That
might.
B
Oh,
so
I
sorry,
I
would
say
that
we
have
some
freedom
here
being
alpha
and
it
is
a
moving
target.
There
is
a
real
nice
story
to
tell
to
align
with
open
telemetry,
and
I
think
you're
going
to
find
some
freedom
here,
because
I
think
a
lot
of
data
planes
are
going
to
be
decoupled
from
the
presentation
of
smi
metrics
versus
open
telemetry
anyway.
So
to.
I
think
this
is
more
of
a
presentation
problem
rather
than
any
like
data
sync
or
data
sourcing
problem.
B
So
we
should
have
some
freedom
to
to
move
between
either
implementation,
where
many
data
plans
probably
have
the
freedom
to
move
between
any
implementation.
So
I
shouldn't
see
us
saying
it's
mutually
exclusive,
but
I
should
I
would
like
to
see
a
should
to
say
collapse
on
open
telemetry.
If
that's
right,.
A
And
I
agree
and
if
I
could
also
ask
you
to
comment
on
that
issue
199
and
in
addition
to
the
google
docs,
that's
mentioned
there
to
the
smi
metrics,
essentially
sharing
where
you
are,
where
you
know
you're
thinking
there
is
given
given
where
you
are.
You.
A
B
A
The
the
issue
is
199
on
our
side.
I
think
the
tracking
it
differently
in
optimal
metrics.
But
if
you
comment
there
justin
from
their
end
is
the
liaison
and
then
I'm
trying
to
facilitate
things
from
our
end
and
I'm
not
sure
I
think
he's
from
lightstep,
I'm
not
entirely
sure
but
yeah
this
and
then
the
google
docs.
That's
in
the
previous
agenda
item
that
trump
pointed
out.
The
google
docs
around
smi
metrics
feedback.
A
G
So
last
time
we
met,
we
touched
on.
We
touched
on
the
topic
of
smi
conformance,
which
is,
which
is
an
effort
to
verify
that
I
give
an
implementation,
adheres
to
the
specs
to
the
smi
specs
and
there's
kind
of
a
lot
in
there.
G
It's
a
fairly
well
advanced
effort
that
is
functional
and
and
performs
some
tests
the
it
needs
to
perform.
Probably
or
let
me
step
back
and
say
so,
there's
a
lot
to
discuss.
Last
time
we
left
michelle
had
suggested
that
we,
you
know
that
we
call
a
meeting
and-
and
I
think
probably
her
ex-
that
we
call
like
a
recurring
work
stream
to
kind
of
advance
the
discussions
and
give
some
dedicated
time
to
it.
And
for
my
part,
I
thought
that
I
would
have
done
that
by
now.
G
I
thought
we
would
have
already
had
that
meeting
since
it
hasn't
happened
yet
and
there's
a
few
things
that
are
happening
within
the
service
mesh
working
group.
I
was
trying
to
find
a
spot
on
the
cncf
calendar
to
host
that
call,
or
that
discussion
and
thought
and
thought
of
leveraging
the
service
mesh
working
group
to
help
advance
it.
Do
you
so
two
questions?
The
smi
metrics
discussion
that
was
held
two
three
weeks
ago
was
that
how
was
that
scheduled?
Was
that
done
through
it.
D
G
Doing
you're
right,
it
won't
be
for
a
couple
of
reasons.
One
is
assuming
that
you
know
a
healthy
number
of
the
implementers
actually
participate.
It'll
take
each
implementer
or
each
service
mesh
a
little
bit
of
time
to
yeah.
The
short
answer
is
yeah,
we'll
need
to
meet
a
few
times.
That's
every
other.
D
I
put
a
note
on
about
your
proposed
time
just
because
friday,
1
pm
central
11
am
pacific
is
definitely
night
time
on
a
friday
in
europe,
and
I
guess
I'll,
ask
michael
to
kind
of
speak
to
and
staphon
to
speak
to
how
useful
that
time.
Slot
is
for
them.
But
that's
kind
of
my
concern
about
fridays.
A
G
F
D
And
you
want
to
start
it
the
december
whatever
it
would
be.
The
first
one
I
guess
would
be
december
2nd.
Is
that
what
you
would
prefer.
G
Well,
no,
because
that's
another,
like
it's
unfortunate
that
like
we,
I
wanted
the
initiative
to
be
done
this
year
to
be
over
with
it.
G
D
D
A
D
Awesome,
so
if
you
want
to
do
if
you,
if
michael
do
you
want
to
run
a
meeting
in
this
time,
slot
just
run
the
meeting
on
wednesday,
the
25th.
A
D
Awesome,
please
give
me
the
the
google
doc
enabled
email
address
that
you
just
send
it
to
me,
so
that
I
can
add
it
so
that
you
can
take
the
notes,
cool.
D
All
right,
then,
I
guess
it'll
be
me.