►
From YouTube: CNCF SIG Network 2021-02-18
Description
CNCF SIG Network 2021-02-18
A
A
A
Austin
I
saw
somebody
flash
up
that
looked
like
austin
person
earlier
yeah
yeah
that
yeah
you
got.
D
B
Yeah,
no,
I
boy,
I
tell
you
what
it's
never
been
such
a
luxury
to
have
a
cup
of
coffee,
I'm
counting
my
I've
got
my
lucky
start,
I'm
sitting.
Where
am
I
I've
moved
my
my.
I
have
a
portable
desk
at
this
point.
There's
no
there's
no
permanent
home.
For
me,
it
sort
of
depends
on
where.
B
The
so
I
tell
you
what
I've
got,
I'm
just
full
of
complaints
like
I've
got.
I've
got
endless
things
to
complain
about.
D
B
Not
news
to
anyone,
but
just
in
case
anyone
needs
a
reminder.
Well
I'll,
say
it
like
this,
so
so
the
roads
are
blocked,
so
we're
out
in
the
country
just
a
little
bit
we're
we're
in
austin.
The
roads
are
blocked
because
because
there's
a
big
hill
leading
up
to
up
to
the
city,
so
to
speak,
and
so
you
know
lots
of
lots
of
accidents
and
so
we're
on
our
own,
well
water
and
so
naturally
the
water,
the
that's
frozen.
B
So
there's
no
there's
no
running
water,
that's
no
different
than
some
of
the
other
other
folks
around
here,
the
electricity's
in
and
out.
So
then
you
know
naturally,
there's
no
there's
no
heating,
so
we're
just
running
there
anyway.
Long
story
short
like
eventually,
you
know
a
few
days
of
that.
You
kind
of
come
down
to
melting
some
snow
and
right
you're.
Just
everyone's
aware
of
this,
but
we've
got
a
couple:
we've
got
a
couple
of
dogs
as
a
reminder:
yellow
snow,
bad,
good,
white,
snow
good.
Just
so.
E
Yeah,
that's
tough,
I'm
here
in
portland.
We
have
it's
been
couple
of.
I
think
three
days
of
full
icy
roads
and
snow
like
about
200
000,
folks
lost
power
and
no
internet
and
water
has
been
scarce,
but
luckily
the
area
I
mean
I
didn't
have
any
of
these
issues,
but
I
could
I
could
see
it's
very
tough.
I
mean
if
the
city
is
not
prepared
for
that
yeah.
It's
too
for
a
long
period.
It's
really
difficult.
B
A
B
There's
some
there's
some
healthy
exercise
in
there
there's
some
yeah
but
yeah
to
zuku's
point.
If
the
area
that
you're
in
wasn't
made
for
the
cold,
then
right
even
just
a
little
bit
of
it,
yeah.
B
Yeah
they
turned
off
yeah,
yeah
yeah.
Well
very
well.
So
this
is
great.
This
is
like
this
is
the
type
of
meeting
that
that
I
can
get
into
like
people
have
got
webcams
on
people
are
making
corny
jokes
even
laughing
at
the
ones
that
I
say
this
is
nice
like
we're
we're.
B
I
think
we
kind
of
struggled
to
find
a
get
to
get
a
cadence
going,
but
but
I'm
seeing
folks
for
the
fourth
time
in
a
row
and
and
we're
really
just
on
the
on
the
br,
the
cusp
of
some
things,
I
think
you
know
ken
ken
owens
is
on
the
call
as
well
and
ken
and
I
are
overdue
to
catch
up
and
can
co-chairs
the
cncfc
network,
and
he
and
I
had
co-chaired
the
cncf
networking
working
group
as
well
and
we'd
always
like.
B
There
are
endless
number
of
problems
to
solve
in
and
around
networking
massive
complex
area,
and
yet
I
don't
know,
maybe
maybe
to
our
maybe
pointing
the
finger
back
at
us
like
we've.
I
feel
like
we've,
had
somewhat
inconsistent
topics,
and
so
I've
been
excited
about
the
service
mesh
working
group
and
some
of
the
initiatives
within
it
because
because
it
gives
us
a
cadence,
it
gives
us
some
regularity
to
to
some
of
the
things
that
we're
doing.
We
get
a
progression.
B
It's
it
ends
up
being
the
working
group
ends
up
being,
I
think,
that's
a
good
label
has
been
a
little
bit
different
than
a
cncf,
a
sig
network
meeting
which
even
the
past
had
done
and
continues
to
do
quite
important
work.
Some
of
the
more
important
work
about
reviewing
projects
so
reviewing
products,
projects
that
are
proposed
for
adoption,
those
that
have
been
here
and
are
coming
up
for
that
their
annual
review,
and
you
know
we
get
to
meet
new
folks.
B
We
get
to
look
at
new
projects
we
get
to
opine
on
those,
but
it
feels
somewhat
administrative
or
it
feels
a
bit
of
paddling
in
place
slightly.
That's
not
to
do
any
not
to
do
any
disservice
to
the
work
that
those
projects
do
and
how
important
it
is
for
them
to
be
adopted
and
go
through
that
review,
and
it's
critical
so
anyway,
working
within
on
some
some
long-lived
initiatives
to
me
is
nice.
B
So
so
that's
what
we're
going
to
do
we're
going
to
talk
about
some
of
the
same
stuff
that
we've
talked
about
before
we're
going
to
lead
off
today
with.
A
Hey
not
one
trivial
openly.
I
think
you
weren't
on
the
talk
call
the
other
day.
I
think
you
sent
a
note
saying:
hey
no
power
or
something
but
looks
like
they're
renaming
six
to
tags.
I
think
you
saw
that
note.
I
did
it's
up
for
vote
anyways.
I
should
say
more
specifically,
but.
A
Something
I
will
say
something
like
that:
I'll
personally
say
someone
who's
trying
to
sort
of
learn
and
navigate
the
world
of
cncf.
A
You
know
I
thought
I
understood
sigs
till
someone
said,
oh
by
the
way,
there's
kubernetes
6
2
and
that
sort
of
threw
me
for
a
whole
loop
when
the
kubernetes
guys
say
sigs,
they
talk
about
thirds
as
opposed
to
seeing
cf1.
So
I
think
differentiation
there
for
me
will
be
helpful,
so
it'll
mean
to
change
for
folks
who
have
been
involved
in
the
cncf6
for
a
while,
but
I
think
that's
navigable.
B
Yeah
yeah,
I
think
I
would
I'd
cast
my
vote
to
change.
I
think
I
had
been
vocal
when
we
first
named
the
sigs
sigs
on
that
particular
point
in
part,
because
the
kubernetes
sig
network
is
a
fair
like.
It
is
perpetually
the
case
that
I
go
to
speak
to
someone
about
cncfc
network
and
they
think
I'm
talking
about
kubernetes
sig
network
right.
B
Well,
fair
enough.
So
there's
there's
one
quick
note
about
what
is
out
before.
B
So
that
there
is
an
outstanding
discussion
on
ambassador
and
whether
or
not
its
name
would
change
to
whether
or
not
its
name
would
change,
I
I
didn't
you
know
dig
into
this
last
time
we
met
to
make
a
quick
remark.
I'll
say
that
there
are
other
projects
or
it's
interesting
to
me.
The
this,
the
cncf
and
the
process
like
you
would
imagine
for
any
organization
evolves
over
time,
and
so.
B
There
have
been
other
examples
of
hard
to
differentiate
corporate
entities
and
projects
themselves
that
are
out
there
and
whether
that
was
the
name
or
just
the
way
that
the
projects
are
governed.
B
B
And
I
hope
that
it
doesn't
mean
that
projects
are
being
treated
unfairly
from
projects
before
and
and
what
were
they
and
what
they
were
held
to
so
anyway,
just
as
a
side
comment.
So
the
crux
of
the
the
core
of
what
I
wanted
for
us
to
dive
in
today
to
today
is
to
to
one
recall
from
from
last
time
that
we
met
we
ended
up
talking
about.
I
think
it
was
mostly
on
service
service
mesh
patterns.
We
got
a
demo
from
about.
B
We
got
an
introduction
to
open
application
model
ohm
and
how
you
can
take
a
service
mesh
pattern,
the
the
60
or
so
that
we've
been
looking
at
and
articulate
those
in
a
yaml
file
in
an
ohm
compatible
yaml
file.
So
I'm
just
kind
of
recapping
from
last
week.
You
could
take
that
and
hand
that
to
a
service
mesh
manager
like
mcmastery
specifically
have
it
implement
that
pattern.
B
In
this
case,
I
think
the
demo
was
a
canary
release
releasing
a
canary
and
how
that
service,
mesh
pattern
and
ohm
interface
with
service
mesh
performance
specification
and
service
mesh
interface
specifications.
So
so,
with
that
context
today,
we've
got
some
discussions
on
get
nighthawk.
B
So
we've
introduced
the
project
in
the
past.
We've
kind
of
walked
through
the
the
goals
of
the
project,
and
I
think
everyone
that's
on
has
had
a
bit
of
an
introduction
to
it.
But
you'll
please
interrupt
if,
if
you've
got
questions
as
we
dig
into
get
nighthawk,
I
wanted
to
it's
always
my
goal
not
to
talk
on
meetings
like
these,
and
so
I
think
we're
going
to
be
successful
in
that
today.
There's
a
couple
of
folks
who've
been
working
on
get
nighthawk
brief
recap
on
get
nighthawk.
B
That's
it's
to
formalize,
just
a
few
distributions
of
nighthawk
as
a
performance
characterization
tool.
Nighthawk
is
a
load
generator
born
of
the
envoy
project
and
it
isn't
well
helped
get
that
into
people's
hands.
I
mean
that's
part
of
the
goal
of
get
nighthawk
there's
a
couple
of
other
goals.
That
part
of
the
goal
is
to
make
nighthawk
compatible
with
the
service
mesh
performance
specification
and
through
its
integration
with
mesheri
nighthawk
will
be
s
p,
compatible.
B
A
Okay,
yeah,
I
can't
tell
you
I've
already
seen
like
in
my
little
world
five
different,
similar
packet
generation
open
source
projects.
Dpdk
is
packet,
gen,
there's
like
moon,
gen
and
the
fido
fd.I
o
guys
have
one.
I
can't
remember
the
name
of
theirs.
It
seems
like
everybody
reinvents
the
wheel
on
a
regular
basis,
not
sure
whether
that's
out
of
a
need
for
origination,
a
lack
of
understanding
of
options
or
specific
elements,
but
whatever
okay.
E
Yeah,
I
guess
the
major
difference
again
here
is
looking
at
the
http
packets,
based
on
like
http
1.1
standard
or
http
2.
It
doesn't
necessarily
dig
into
the
packets
per
second
or
like
the
late
three
stats.
E
The
most
of
the
other
traffic
generators
looking
right,
so
that's
one
thing
that
we've
been
discussing
with
auto
maintainer
of
nighthawk
there's
a
little
bit
of
disconnect
between
l2
l3.
You
know
how
these
are
kind
of
standards,
there's
rc2544
versus
what
l72
is
going
to
generate,
and
I
said
yeah
we
had
a.
We
have
a
parallel
discussion
with
auto
there
to
see
how
we
can
bridge
the
gap
between
these
two
or
make.
A
B
B
I
don't
know
how
to
paraphrase
it
but
discourteous
and
how
they
they
just
bla.
They
just
like.
B
They
don't
wait
for
the
they're,
not
polite
about
it,
or
they
don't
wait
for
the
response
back
to
and
there's
another
one
of
those
different,
some
of
the
differences
or
I
I
can
imagine
the
need
for
different
load
generators
by
way
of
what
language
they're
written
in
and
and
what
sdks
are
available
to.
B
You
know
programmatically
interface
with
the
load
generators
that
that's
a
yeah
there's
actually
an
analysis
written
about
two
load;
generators
that
are
within
the
service
mesh,
wheelhouse,
fortio
and
well,
and
wrk
and
nighthawk,
and
a
little
bit
about
why
it
is
that
nighthawk.
I
believe
if
ottawa
is
here,
I
think
why
nighthawk
was
written
and
fortio
wasn't
reused.
B
So
so
of
this
so
and
actually
some
code
do
you
did
you
have
any
any
more
to
add
on
that
or
like
in
your
mind,
were
those
just?
Where
did
those
discussions
leave
off
in
terms
of
lower
layer
but
better
lower
layer
support.
E
Yeah
recently
said
we
have
a
google
doc
sheet
or
google
doc,
essentially
like
auto,
had
written
down
some
of
the
pointers
as
to
what
we
could
work
on.
We
hadn't
made
a
lot
of
progress
there
yet
because
I've
been
chasing
some
customers,
she
hadn't
really
gotten
a
chance
to
work
on
that,
but
he
did
forward
another
talk,
google
doc,
that's
being
I
think,
most
folks
from
onward
community
are
looking
at.
E
You
know
what
what
what's
a
good
set
of
features
required
for
load
generation
for
nighthawk
perspective,
and
I
could
for
that
google
doc
here,
but
yeah
that
one
goes
through
more
details
as
to
what's
required
in
nighthawk.
What
are
the
features
to
be
added
our
gaffes
and
things
like
that,
and
I
see
folks
from
many
different
companies
participating
there.
That's
where
we
are.
We
hopefully
make
some
progress
next
week,
nice
yeah
yeah.
If
that.
B
B
C
Oh
sure,
I'll,
oh,
are
you
presenting
it
good?
So
we've
put
up
this
talk
while
we
initiated
this
project
to
track
all
the
plan
of
action
and
sort
of
all
the
updates
in
here,
so
that
everyone
are
aware
of
it.
C
So,
looking
at
that,
the
first
step
that
we
followed
or
while
proceeding
with
the
project,
is
that
we
were
able
to
sort
of
build
the
project
individually,
but
meaning
nighthawk
as
a
project
has
several
components
like
the
client
or
the
grpc
server
that
runs
or
even
on
the
test
server.
So
we
were
able
to
build
them
individually
and
publish
them
as
an
artifact
right
now
manually.
C
So
having
that
accomplished,
we
put
up
a
list
of
planner
factions
that
we
are
moving
ahead,
what
we're
going
to
do
about
automating
this
process,
and
here
we
go
like
basically
this.
This
is
exactly
the
list
or
a
plan
of
actions
that
we
have
in
mind.
C
C
Which
would
be
stable
and
nightly,
but
yeah
like
basically,
this
is.
This
is
the
overview
of
what
the
current
progress
of
this
project
is
and
moving
it.
Hopefully,
the
ones,
the
ones
that
you
see
here
would
be
actually
removable.
The
next
time.
C
Yeah,
that's
that's
majorly.
The
update
around
the
project.
C
B
C
So
currently
we
are
targeting
two
operating
systems
which
are
linux
and
macros.
When
it
comes
to
linux
we
and
yeah.
Obviously,
there
is
docker
image
published
that
is
kind
of
separate
from
these
two
individual
networks,
but
yeah
like
when
we
talk
about
linux
distributions.
We
are
targeting
yum
and
apt
repository.
C
Currently
they
are,
they
have
the
highest
priority
and
apparently
we
have
for
mac
os
the
homebrew,
which
is
the
most
famous
homebrew
and
scoop,
which
is
an
optional
but
yeah.
The
target
is
that
homebrew
would
be
the
p1
priority,
one
and
and
yeah,
and
a
docker
image
build,
which
would
which
would
be
linux
based
yeah
like
these
are
the
only
ones
that
have
the
top
most
priority.
E
Gotcha
yeah,
I
think,
internally,
to
be
primarily
prioritized
ubuntu
and
sent
us
most
of
our
tests
are
based
on
that
and
yum.
And
yet
those
are
the
things
we
care
about
too,
and
I
think
centos
is
changing.
The
heart
is
changing
the
way
centaurs
is
distributed,
going
ahead
or
released
instead
of
a
full-blown
release.
It's
doing,
I
think
a
rolling
update
or
I
have
to
check,
say
it's.
The
release
model
is
changing,
but
yeah.
Maybe
that's
something
to
worry
about
in
the
future,
but
yeah.
For
now.
B
B
E
So
if
I
understand
this
effort,
the
difference
with
the
get
nighthawk
effort
is
more
in
terms
of
enabling
nighthawk
as
a
like
a
commodity
tool
to
be
or
a
package
tool
that
one
could
leverage
using
yammeria
is
or
are
you
also
looking
to
establish
a
ci
where
you
could
continuously
run
the
performance
test
off
on
y,
for
example,.
B
Yeah
both
the
yeah.
This
is
thanks
for
asking
it's
a
little
bit
confused.
I
think
that
there
are,
I
mean
to
your
to
your
question
that
there
are
a
couple
of
highly
related
efforts
going
on
and
when
you
step
back
and
look
at
them
all,
it
makes
a
lot
of
sense.
There's
like
in
context.
Okay
in
context
of
service
mesh
performance.
That
specification
part
of
the
goals
of
that
initiative
are
to
help
the
world
understand
different
performance
characteristics
of
service
meshes
and
part.
Why
nighthawk?
You
know
nighthawk
and
load.
B
Generators
are
of
interest,
is
to
be
able
to
answer
people's
questions
about
what
to
expect
in
terms
of
certain
overhead
or
in
terms
of
certain
environments
or
performance
like
a
very
specific
performance
overhead
they
might
get
from
invoking
a
particular
function
or-
and
so
so
there's
a
part
of
us
standard
to
help,
hopefully
bring
forth
some
common
tooling
to
hopefully
bring
forth
that
common,
tooling
sort
of
leans
into
something
like
get
nighthawk,
which
so
nighthawk
being
very
useful
and
somewhat
extensible
so
like
to
yeah
but
kind
of
hard
to
build
and
not
necessarily
well
promoted,
or
it
doesn't
have
its
own
website
like
that.
B
B
One
of
the
challenges
that
I
have
always
found
is
that
when
you
do
want
to
go
run
a
series
of
tests
that
it
often
ends
up
being
some
bespoke
heart
test,
harnesses
and
test
framework
and
test
environment
in
the
lab,
and
all
that
and,
like
you,
basically
end
up,
devoting
one
or
two
people
or
more
to
to
just
this
to
performance
engineering
right
to
just
this
type
of
and
when
universally
as
as
service
meshes
gain
in
popularity
people
every
time.
I
talk
to
have
this
question
around.
B
What's
the
overhead
and
how
do
I
manage
that
and
what
how
do
I
know
if
I'm
running
things
well
and
and
and
if
you
talk
to
any
of
the
individual
projects,
they'll
disagree
or
they'll
say
this
one's
better.
That
one
does
this
like
that.
You
know
it's.
B
It's
a
it's
a
challenge
for
people
to
understand
it
so
bringing
forth
a
standard
specification
enabling
people
with
easy
to
access,
tooling
and
then
more
than
just
getting
nighthawk
into
their
hands,
which,
which
is
great,
but
it
also
means
that
people
will
still
need
to
build
some.
B
What
I
would
consider
is
bespoke
tooling,
around
get
nighthawk
for
scheduling
when
it's
going
to
run
running
the
same
test,
consistently
tracking,
the
the
feedback
and
the
reports
comparing
the
performance
over
time
like
that,
then
that
that's
important
measuring
comes
to
bear
in
terms
of
facilitating
those
things
standing.
You
know
deploying
your
service
mesh,
deploying
your
applications,
scheduling
and
running
the
the
load
tests
in
a
either
in
an
interactive
way
in
which
people
can
go.
Look
at
and
examine
reports,
or,
yes,
I
think,
is
the
short
answer
to
your
question.
B
It's
sort
of
yes
to
both
they're,
like
yes,
you
would
part
of
the
goal
of
getting
get
nighthawk
is
to
through
the
through
integration
with
mesri
is
to
allow
people
to
put
this
into
their
pipelines
and
by
people
I
mean
all
of
the
users,
but
also
the
service
mesh
projects
themselves,
as
they
go
to
integrate,
get
nighthawk
and
and
meshery
into
their
pipeline
that
and
they
go
to
use
a
standard
specif.
E
Yeah
yeah
makes
sense,
yeah
yeah,
and
definitely
I
think
that
thanks
for
that
big
picture
kind
of
view
now,
one
other
thing
otto
was
mentioning
was
looking
to
build
some
performance
ci
for
envoy
using
nighthawk.
So
I
was
curious
if
both
go
hand
in
hand,
looks
like
you
know,
kind
of
a
line.
So
one
thing
I
was
mentioning
thought
also
was:
there's
a
cncf
desktop
available.
E
I
think
right
so
that
to
run
some
of
these
testing,
I'm
not
sure
if
you're
leveraging
or
looking
in
the
planning
in
the
future
to
leverage
running
these
test
performance
tests
on
the
testbed.
B
I
think
you've
almost
covered
the
you're
I
chuckled,
because,
yes
again
as
a
short
answer,
I
was
gonna
kind
of
go
into
the
longer
kind
of
when
you
look
at
like
hey
hey.
What
is
this
working
group
and
what
are
we
all
trying
to
accomplish?
Are
you?
What
are
those
those
things?
B
There's
a
few
initiatives
that
get
broken
down,
so
one
of
those
is
yeah
very
much
so
that
it's
been
we've
had
access
to
the
cluster
for
a
long
time
to
do
these
particular
tests,
part
of
our
challenge
in
going
and
actually
running
the
tests
and
publishing
some
results.
B
So
that's
one
of
the
things
that
that
all
of
you
here
and
or
others
that
aren't
here
like
for
my
part,
I'm
very
motivated
to
go
to
go,
do
that
we
haven't
done
it
in
the
past
because
a
we
don't
want
to
get
it
wrong
and
make
an
arse
out
of
ourselves
and
ours.
Out
of
you
know,
all
the
other
meshes
be
without
easy
to
access,
tooling
and
kind
of
without
having
to
write
a
bunch
of
bespoke
kind
of
going.
B
You
know
writing
bespoke,
tooling,
to
go
run
these
like
without
having
a
meshery
there
to
be
able
to
just
go
over
to
an
empty
set
of
you
know,
20
servers
or
so
or,
however,
many
in
the
lab,
and
and
take
a
pattern
file.
That
says
well
I'd
like
to
take
this
mesh
or
this
mesh
or
this
mesh
under
this
config,
this
config
disk
config
and
I'm
using
this
app
or
this
app
or
this
app,
and
I
like
to
run
this
action,
this
service
mesh
action.
B
Whatever
invoke
the
configuration
of
that
mesh
in
turn
do
get
get
nighthawk
like
spin
up
at
least
one
or
maybe
multiple
instances
of
nighthawk
hit.
The
endpoints
gather
the
load
back
from
nighthawk
present
it
and
then,
like
all
of
that
work
too
much
for
us,
like
it's
been
about
a
year.
Now
that
I've
been
saying
pretty
much
what
you
just
said,
which
is
like
hey,
wait.
A
second
there's
a
great
resource
sitting
here,
there's
a
common
question:
a
lot
of
people
have
are:
aren't
we
aren't
we
in
a
working
group?
B
B
B
Yeah
yeah
that
and
even
to
do
it
fairly
right
because
so
we've
been
around,
we've
talked
to
every
single
service
mesh,
that's
out
there
and
one
that
is
yet
to
be
announced
like
there's,
there's
one.
B
I
don't
know
when
they're
gonna
announce
but
to
to
be
able
to
say
well,
hey,
like
hey,
there's
a
specification
here.
You
you're
all
welcome
to
comment
on
it
and
make
sure
that
it's
like
yeah.
B
And-
and
so
I
don't
mean
to
to
prey
on
you
in
this
meeting,
but
cinco
you're
very
much
needed
in
that
like
like,
I
we
I
I
just
don't
have
the
for
speaking
for
my
part
like
I'm
I'm
tapped
out,
but
I
so
much
want
for
us
to
do
that
and
we're
so
so
yeah.
E
Yeah,
if
there
is
some
an
smp,
I
went
through
the
site
saw
the
github,
but
there
is
a
specification
in
the
works.
I'm
pleased
to
include
the
link
in
the
minutes
when
possible,
so
they
can
begin.
B
Oh
nice
yeah,
absolutely
absolutely
as
a
matter
of
fact,
that
might
be
good
to
tee
that
up
for,
like
the
next
time
that
we
meet
as
well
as
to
like
hey
what
let's,
let's
do
a
let's
do
a
spec
review
where
I
mean
we'll
we'll
get
you
that
info
in
the
meantime,
but
to
do
a
spec
review
to
do
a
walkthrough,
absolutely
yeah,
because
because
it's
missing
some
things,
I
guess
you
know
like
it's
a
it's
good,
but
there's
more.
That
needs
to
be
done.
Sure,
okay,
so
abhishek.
B
Thank
you
for
the
update
on
so
we've
had
progress,
so
nighthawk
is
being
built
built
locally.
You've
got
a
collection
of
folks
here,
adina
rodolfo,
who
are
gonna,
go
off
and
spend
some
time
in
github
workflows,
get
up
action,
workflows,
okay,
we've
also
had
I.
B
B
Your
irrespective
there's
a
collection
of
folks
who
are
working
on
under
this
domain
to
to
bring
forth
some
some
designs
that
have
been
made,
there's
a
link
to
the
designs
here.
B
Hopefully
everybody
that
wants
to
get
to
it.
Can
I
I
don't
think
I'm
going
to
be
successful
loading
it
at
the
moment
but
simple
static
site.
This
is
the
scope
and
structure
of
the
site.
There's
not
a
lot
to
show.
I
think
if
you
visit
the
url,
it's
going
to
be
pretty
barren,
there's
some
open
source
contributors
that
are
spending
what
time
that
they
can
doing
a
good
job.
B
One
other
item
on
here,
and
that
is
that
there
have
been
a
couple
of
I
think,
about
three
logos
drafted
as
possible
logos,
forget
nighthawk,
and
those
need
to
be
those
three
and
maybe
more
need
to
be
presented
to
you
all
for
a
vote.
We
need
to
open
up
a
poll
and
have
people
vote
and
or
suggest
that
a
redesign
be
done
or.
E
So
if
you're
looking
for
item
open
items,
I
missed
to
ask
this
in
in
the
beginning,
with
respect
to
the
some
of
the
work
that
you
mentioned
in
the
last
call
that
you're
working
with
some
universities
on
some
of
the
service
mesh
performance
aspects
or
test
aspects.
E
B
Great
question-
and
it's
also
well,
we've
done
yep.
How
do
I?
How
do
I
try
to
be
concise
here
and
it's
again
kind
of
part
of
the
bigger
picture
is
or
like
there's
some
specific
items
that
we're
engaged
with
a
couple,
a
couple
of
universities
on,
but
really
sunku
actually
use
against,
specifically
being
here
or,
and
it
could
be
ken
or
it
could
be
derek
or
but
it
has
to
be
more
people
than
me
because
I'm
just
I'm
it
is.
B
We
need
a
little
bit
of
a
a
new
kickstart
with
some
of
them.
So
there's
there's
two
professors,
one
at
nitk
nit
and
the
k
part
I'm
gonna
mispronounce
abhishek.
Do
you
recollect
but
yeah
it's
kharagpur.
Probably.
F
B
I
mean
this
is
the
this
particular
professor
here:
mohit
talayani,
so
nit
khan,
khar
khan,.
B
And
for
some
reason
his
page
isn't
coming
up.
G
B
Thank
you,
ken
there's
another
one
as
well.
Sorry
guys,
I
feel
like
I'm
so
disorganized,
just
there's
so
much
so.
There's
there's
this
professor
super
nice.
Individual.
His
areas
of
interest
are
right
within
the
same
kind
of
networking
space.
You
can
see
some
of
the
prior
research
that
he's
done
and
he's
there's
a
student
or
two
that
we've
been
engaged
with
who've
been
studying
and
kind
of
learning,
nighthawk
and
part
of
it's
we're
pretty
interested
in
its
adaptive
anyway.
There's
there's
a
few
different
things.
B
I
think
that
we
can
go
off
and
accomplish
and
by
we
I
don't.
I
mean
I
mean
ken,
and
I
mean
all
the
folks
on
this
call
that
and
they've
been
written
down.
Some
of
these
are
a
year
old
and
they're
writing
in
how
they've
been
written
down,
which
is
why,
when
sungku
says
hey,
do
you
have
a
link
to
it's
like
yeah?
There's
a
link
there
it's
dated
like
or
it
needs
to
be
updated,
but
irrespective
I
will
send
you
a
couple
of
links
about
the
projects
that
we've
discussed
with
them.
B
Introduce
you
to
these
folks
there's
an
a
professor
from
not
cornell
it's.
I
think
it's
nyu.
I
owe
him
a
response.
He
said
that
he
wants
to
engage
on
smp
and,
in
my
mind,
like
again
like
smp
mastery
nighthawk
get
nighthawk
nighthawk
the
patterns,
the
cncf
lab,
like
all
very
beautifully
intertwined
in
terms
of
or
overlapping
intertwined.
So,
even
though
he
said
he
wanted
to
engage
in
smp,
I
think
he's
open
to.
I
don't
remember
his
name
honestly.
B
So
now
that
I've
totally
digressed
this,
I
think
that
there's
two
things
for
us
to
cover
that
will
help
us
get
organized
and
help
empower
ken
and
sungku
abhishek
and
adina
to
move
some
of
this
forward.
B
The
second
thing
that
we
should
make
sure
that
we
discuss
is
ken
was
noting
that
there's
we
we've
consistently
done
a
sig
network,
deep
dive,
introduction
and
deep
dive
at
kubecons
and
that
the
upcoming
kubecon
has.
We
need
to
go
ahead
and
reserve
our
spot.
B
I
think
today,
and
so
can
can
I
yes,
if
you,
if
you
don't
mind
the
really
there's
just
this
generic
description
of
what
that
talk,
is
and
the
one
from
the
last
kubecon
or
the
kubecon
before
that,
will
it's
generic
enough
that
it'll
totally
work
and
can
reserve
our
spot
yep
I'll,
submit
it
today?
Thank
you.
Thank
you.
E
Yeah
on
that
topic,
otto
and
I
submitted
abstract
for
servicemeshcon
in
terms
of
learnings
from
benchmarking
or
performance
testing.
Some
of
the
measures
I
mean
our
work
has
been
onway
but
yeah,
so
I
figured
it
shares
some
of
the
common
learnings
awesome.
G
Yeah,
I
think
we
should
probably
like
sign
up
for
that
service
mesh
con
as
well,
just
to
kind
of,
let's
make
sure
they're
aware
of
the
sig
and
then
make
sure
that
you
know
we
can
bring
out
some
of
those
interesting
projects
into
our
discussions.
E
G
Don't
think
they
change
the
price
on
the
the
service
match
company,
like
the
the
I
guess
day,
zero
events-
they
call
them,
but
they
might.
I
I
have
the
fortunate
benefit
of
being
a
a
end
user.
So
I
get
I
don't
have
to
pay
for
coupons,
but
I
do
have
to
pay
for
the
service
match
con.
So
I
have
to
kind
of
factor
that
in
but.
B
B
Can
that,
thanks
for
raising
that
up?
Actually
it
had
been
suggested
that
this
sig
potentially
participate
in
the
program
committee
for
something
like
service
meshcon,
which
I
think
makes
a
lot
of
sense.
The
same
thing
had
been
suggested
for
the
security
cloud
native
security
day.
The
cloud
native.
B
Can
there
there
had
been
there's
two
other
topics
that
come
to
mind
that
that
I'd,
I
love
to
see
us
do
and,
and
is
something
that
I
think
that
that
it
would
take
an
individual
like
you
to
to
to
to
force
us
to
do
it,
and
that
is
that
is
we've
been
talking
about
the
the
cncf
polls
that
go
out,
that
that
inquire
about
usage
of
certain
technologies
yep
and
how
and
how
willfully
underdone
the
service
mesh.
G
B
B
Yeah,
it
adds
to
the
confusion.
I
think
yeah
I'd
like
to
see
us
not
not
doing
end
user
radar,
but
do
and
collaborate
with
cheryl
if
she'd
like
to
but
to
do
a
or
maybe
if
the,
if
the
end
user
radar
for
service
mesh
is
coming
up,
is
to
to
collaborate
on
that.
G
So
I
I
have
asked
to
a
couple
of
times
to
include
the
sigs,
because
it's
it
even
if
it's
an
end
user
poll,
you
still
want
to
have
like
the
right
choices
in
there
and
the
right
questions
being
asked.
That
would
be
helpful
to
the
say
it
shouldn't
just
be.
B
You
end
user
meeting
and
I
forget
the
name
of
the
individual,
but
he
was
trying
to
figure
out
if
the
proposal
for
multi-cluster
and
istio
was
really
going
to
work
for
people
in
the
way
that
they
name
space
their
kubernetes
clusters
and-
and
it
wasn't
going
to
work
for
him
because
he
uses
or
their
organization
uses
the
same
literally
the
same
name
for
the
name
spaces
across
every
kubernetes
cluster
and
the
multi-cluster
design
for
istio
was
that
they
had
those
name.
B
B
One
one
other
item
here:
istio
con
is
next
week
by
the
way
that
there's
a
we'll
we'll
be
giving
a
two
and
a
half
hour
workshop
on
istio,
we'll
use
meshri
to
help
teach
people
which
implicitly
we'll
use
nighthawk
and
at
some
point
we'll
be
using
get
nighthawk
it'll,
be
you
showing
people
introducing
people
to
snp
so
to
to
ken's
point
about.
Like
you
know,
another
venue
for
introducing
some
of
these
works
to
people
at
servicemeshcon
from
istiocon
for
sure
did.
Do
you
recall?
B
Did
the
cfp
come
back
with
the
the
talk
being
accepted
or
have
you
guys
heard
back
yet.
E
B
Okay,
ken
has
this
one
very
good
can
also
also
socialize
sounds
like.
Can
you
end
up
socializing
again
with
you'll
test
the
waters
with
cheryl?
B
If,
if
ken,
if
she
doesn't
come
back,
I
I'd
I'd
like
to
help
you
help
you
if
I
can
suggest
it
like
this
I'd
like
to
help
you
organize
a
poll,
get
some
some
questions
down
and
and
see
if
we
can
get
a
really
accurate
one
going
on.
B
E
So
this
one
so
sorry
and
the
topic
that
we
started
the
university
discussion
you
know
like
to
participate
there
see
what
we
can
do,
but
is
there
like
a
common,
not
not
necessarily
google
doc,
but
a
common
place
where
ideas
are
being
discussed
or
shared
as
to
what
what's?
What
are
the
things
could
be
done
or
being
explored
or
or
interest
from
the
university
side?
Is
there
a
place
commonplace
for
this
discussion.
B
It
has
been
to
to
date
not
by
design,
but
just
by
where
the
activity
has
been
and
where
we've
gotten
in
touch
with
people.
It
has
been
in
this
slack
here,
there's
a
performance
channel
and
a
webassembly
channel.
B
We
can
pull
those
discussions
like
I
very
much
so
desire
to
have
those
discussions
coming
into
here,
but
we
don't
have
a
regular
meeting
cadence
on
those.
I'm
hopeful
for
this
to
be
that
it
that
the
timing
of
when
we
have
this
call
is
tough
for
some
of
those
folks
but
yeah,
I
think,
being
getting
vocal
there
to
start
and
then
tsunku.
I
I'd
like
to
want
to
find
a
time
with
you
to
get
some
of
these
a
bit
more
better.
B
Just
you
know
better
described
on
paper,
get
smp
introduced
to
you
some
more
some.
You
know
better
yeah.
E
E
The
reason
why
one
of
the
reasons
why
I'm
curious
about
this,
especially
the
performance
is
so
I've
been
working
on
characterizing
envoy
on
bare
metal
and
what
we
realized
is
not
just
the
tool,
but
there
are
so
many
combinations
of
how
we
could
you
know
slice
and
dice
the
test
and
understand
the
performance
of
envoy
in
terms
of
scaling
in
terms
of
connections
or
latencies,
whatever
the
case
might
be-
and
this
is
just
leveraging
unvoiced
sandbox,
you
know
so
that's
published
on
on
my
website
and
nothing
complex
right,
just
the
docker
containers
and
once
we
get
into
kubernetes
environment.
E
You
know
it
gets
much
more
complex
with
services
and
you
know
number
of
side,
cars
and
whatnot.
So
what
I
realized
it's
too
much
for
you
know
one
or
two
sort
of
people
to
kind
of
do
a
comprehensive
study
right.
So,
even
though
we
prioritize
the
cases
that
we
need,
but
it's
just
a
lot
of
variations
of
what
could
be
done.
Definitely
I
mean
in
terms
of
automating
this
to
what
you
are
needed,
with
measuring
and
smv
and
in
a
ci
test
that
that
would
help
but
yeah.
E
So
what
you
realize
is
this
can
be
looked
at
different
angles:
changing
kernel
parameters,
changing
l2,
l3,
leveraging,
hardware,
offloads
and
whatnot.
So
that's
one
of
the
reason
to
see
from
if
there
is,
if
anyone
else
is
interested
to
collaborate
in
some
of
these
areas,
we
could
look
at
some
of
the
hardware
of
float
parts
and
collaborate
on
some
of
the
work
that
we're
doing
to
see
how
you
know.
So
we
can
enhance
mesh
performance
overall
right
yeah.
So
that's
one
of
the
goals
that
we
have.
B
Figured
out
that
I'm
trying
to
figure
out
the
best
way
to
you
could
yeah
you
welcome
to
my
nightmare
for
the
last
yeah
I,
which
is
like
yeah,
I've
said
it
on
stage
a
few
different
times
like
hey
people,
kept
asking
this
question,
so
we
won't
have
to
try
to
answer
it
and
then
little
did
we
realize
like
what
a
nightmare
performance
engineering
it
or
like
just
the
the
thousand,
the
millions
of
permutations
of
one
of
the
talks
that
was
given
at
actually
with
the
university
a
phd
candidate
here
at
ut
austin
was
was
very
much
so
just
on
like
trying
to
like
explicitly
identify
the
cost
of
a
given
service
mesh
function
like
what
does
it
cost
to
do
I'll
say
some
boring
thing
like
what
does
it
cost
to
do
a
round
robin
or
something
that's
kind
of
boring,
but
there's
a
bunch
of
service,
specific
things
that
are
so
there's
an
interesting
thing.
B
One
of
the
things
like
as
we
go
to
wrap
up
here
that
I've
heard
from
people
from
time
to
time.
I
think
the
first
time
I
heard
it
was
from
it
was
a
year
and
a
half
ago
from
the
aws
app
mesh
product
manager
when
I
was
introducing
some
of
these
concepts
to
him
in
in
his
you
know,
in
context
of
measuring
the
performance
of
the
mesh
and
measuring
the
perform.
B
You
know
whether
or
not
app
mesh
wanted
to
participate
and
kind
of
go
through
this
with
us,
and
I
think
his
perspective
was
well.
He
so
we're
an
envoy-based
data
plane.
So,
like
you
know,
it's
just
going
to
be
the
same
as
anyone
else
who's
using
envoy
as
a
data
plane,
and
I
we
ran
out
of
time
for
me
to
articulate
verbalize
to
him.
B
That,
like,
I
think,
that's
an
a
myopic
viewpoint
or
a
naive
viewpoint
that,
like
this,
was
actually
before
istio
had
refactored
in
1.6
to
move
all
the
telemetry
like
hey
the
way
you
design
your
control
plane
has
a
big
effect
on
how
the
data
plane
works
and
kind
of
vice
versa,
and
and
just
because
you're
using
envoy
inside
doesn't
mean
that
you're
that
the
performance
necessarily
looks
anything
like
a
different
service
mesh.
B
E
No,
I
agree.
Definitely
you
know
so
there
we
have
at
least
I
haven't
done
a
lot
of
analysis
on
control
plane.
E
Yet,
but
what
and
how
we
configure
control,
plane,
hto
or
xds,
whatever
the
case
might
be,
and
how
the
individual
proxies
had
car
proxies
are
deployed,
have
a
huge
impact
on
the
application
and
overall
performance,
and
we
see
that
that's
what
we're
trying
to
analyze
to
you
know
change
the
configurations
of
site
cars
to
see
what
effects
does
it
have
on
the
core
performance
or
I
o
performance,
and
I
know
how
exactly
we
can
tune
that
in
respect
to
filters
or
with
respect
to
what's
happening
in
the
control
plane,
how
much
can
be
leveraged
by
the
control
plane
right.
E
So
those
are
the
things
we're
looking
at
yeah
I
mean
even
small
variations
of
how
we
deploy
sidecars
or
or
your
ingress,
proxy
or
front
proxy
has
a
right
so
that
sometimes
this
might
be
the
case
that
front
proxy
might
do
a
lot
of
work
before
it
reaches
the
cycle
proxies
right,
so
the
how
we
deploy
and
our
environment
can
impact
the
performance
quite
a
lot.
I
was
to
say
one.
A
E
Point
yeah
so
yeah
definitely-
and
I
agree
with
you-
you
know
so
control
plane
and
this
one's
go
hand
in
hand.
So
at
least
my
our
team's
goal
is
catering
service
mesh
towards
the
telecom
deployments.
E
So
looking
at
the
5g
data
plane
and
how
like
how
5g
network
functions,
can
leverage
service
mesh
still
in
early
days
and
from
that
perspective,
but
yeah.
So
that's
the
ultimate
goal
where
we're
going
towards,
and
so
the
networking
becomes,
the
biggest
part
of
you
know
what's
happening
in
the
mesh
right,
so
the
network
data
plane
and
yeah.
So
for
sure,
I
agree
with
you
that
it
has
to
be
very
sensitive,
both
control,
plane
and
data
players
to
coordinate
together
to
reduce
the
impact
of
latency.
B
Good
well
well,
we've
got
an
agenda
teed
up
for
for
next
time.
Cinco
sounds
like
we'll
be
able
to
catch
up.
Probably
tomorrow,
I
love
a
meeting
where
I
get
or
ken
leaves
with
some
action
items.
That's
one
of
the
my
favorite
meetings.
G
Hey
not
a
problem
man.
I
was
glad
I
could
actually
join
a
meeting
for
once
and
not
at
my
my
new
company,
something
I
can
actually
enjoy
working
on
for
a
while
yeah
yeah.
G
Just
just
to
make
you
feel
badly,
we
got
about
12
inches
in
st
louis,
but
the
snow
plows
got
it
off
the
roads
in
about
an
hour
and
a
half,
and
we
have
no
issues.
We
have
no
water
problems,
we
have.
No,
you
know
everything's
good
here
you
gotta
have
to
like
get
some
snow
plows
down
there.
You
guys
have
all
these
trucks
just
put
some
plows
on
the
front.