►
From YouTube: Network Service Mesh WG - 2018-08-17
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
A
So
we
have,
we
have
a
document
added
on
using
CNI
with
with
mini
cube,
that's
been
merged
in,
and
we
also
have
added
a
note
for
our
usage
on
depend
upon
so
so
those
are
the
two
items
that
that
were
that
were
added
in.
So
if
anyone
wants
to
to
take
a
look
at
those
two
pieces
of
documentation
and
see
if
they're,
clear
and
meet
and
or
if
there's
any
questions
about
how
this
works,
you
know
those
are,
those
are
the
places
to
find
it.
A
This
has
been
written
by
person
who
goes
by
the
neck,
doon
hammer
and
can
sort
of
remind
me
whose
name
is
is
attached
to
doing
hammer.
That's
me,
it
was
John.
Alright,
so
John's
been
working
on
a
set
of
guidelines
were
extending
network
service
match.
So
we'll
discuss
more
in
detail
about
that,
but
there's
a
document
that
needs
review.
So
you
know
well.
D
D
B
D
A
That's
it
that
so
so
we
have
these
guidelines
that
have
been
that
have
been
sent
in,
so
we're
gonna
take
a
look
at
it
on
on
our
particular
side.
But
if
someone
someone
who's
not
as
familiar
with
how
to
extend
out
network
service
much,
we
really
appreciate
if
someone
can
take
a
look
at
it
and
see
if
you
can
make
sense
of
it.
That
way
that
you
know
we
can
make
this
approachable
for
for
newcomers
as
well.
So.
E
One
of
the
comments
from
Kyle
was
whether
it
could
be
internet
to
tree
as
a
thing
added
to
the
agenda,
so
I
created
based
on
Kyle's
or
thoughts,
I
created
our
out
of
tree
template
that
would,
with
a
script,
they'll,
basically
create
a
complete
tree
with
make
file
snowing,
using
Serge's
simple
data
plane
as
a
kind
of
a
template.
Well,
it's
not
quite
all
there
I
think
it
needs
a
few
more
things,
but
it's
one
way
of
doing
it
and
it
seems
to
kind
of
work.
E
I
think
a
few
bugs
still
get
to
get
out
of
it,
but
I
can
create.
You
know.
Different
data
planes
and
you
only
need
to
do-
is
really
edit.
The
photo
file
in
the
go
file
to
get
most
of
it
working
what's
really
missing,
is
some
sample
end
points
and
how
to
once
you
have
a
data
plane
and
how
to
send
traffic
between
machine
over
the
data
plane.
A
little
more
examples
around
that
would
help.
B
A
Yeah
and
these
kind
of
these
kind
of
exercises
and
discussions
like
they,
they
help
out
a
lot
because
it's
from
from
a
high
level
conceptual
view
like
we
can
try
to
make
a
simple
architecture.
But
we
know
that
the
that
there's
a
lot
of
detail
that
can
they
can
get
down
when
you're
trying
to
actually
implement
it.
And
so,
when
one
thing
that
we
have
to
focus
on
iterate
on
and
and
where
this
can
also
really
help
is
is
on.
How
do
we
make
this
approachable
like
if
you're
a
newcomer?
A
A
We
have
templates
laid
out
generators
or
anything
that
they
need
just
to
get
started
type
in
the
code
that
they
that
they
need
and
then
they're
off
and
running,
or
we
go
the
opposite
direction
and
you
know
even
with
fantastic
documentation,
but
just
have
so
much
detail
in
there
and
so
many
little
things
I
have
to
take
care
of,
and
you
know
and
it'll
still
be
really
difficult
for
them
to
approach
and
that'll
limit
our
adoption.
So
I.
E
Think
you
think
of
said
in
the
to
do.
There's
three
audiences
willing
to
think
about
one.
Is
you
guys
who
are
writing
the
infrastructure?
To
is
the
guys
who
want
to
use
infrastructure
to
write
and
ascend
plugins,
and
then
three
is
the
people
who
want
to
use
a
plugins
to
actually
do
something,
and
it's
some
cases
that
may
all
be
the
same
people
but
I,
think
I,
think
thinking
about
three
different
audiences
and
how
to
address
it
documentation
and
how
to
address
the
like.
E
How
to's
for
that
first
point,
and
so
it's
there's
a
minimal
friction.
I
just
want
to
use
MSM
and
something
else
is
built.
A
plugin
I
should
try
some
Yama
files.
I
should
not
need
to
do
in
know
anything
else.
Really.
That
may
be
how
to
deploy
the
said
if
I
want
to
extend
NSA
I
shouldn't
need
to
know
too
much
of
a
little
details
just
enough
to
do
a
data
playing
or
an
endpoint.
D
The
things
they
care
about
I
talked
about
this
as
keeping
things
under
the
complexity
curve.
So
if
you
picture
like
an
X
and
y
axis,
where
on
one
side,
you
have
you
know
on
why
you
have
the
complexity
of
what
it
takes
to
do
a
thing
and
on
X
you
have
the
complexity
of
the
thing
you're
trying
to
do.
There's
a
45-degree
line
there
that
you
need
to
make
sure
you
always
stay
below
right.
You
always
need
to
stay
below
that
45-degree
line
at
at
all
times,
yeah.
B
It's
not
always
possible,
you
know
it's
yeah
or
try
to
try
to
get
people
a
way
to
at
least
navigate
through
it
quickly
with
samples
that
they
can
that
they
can
leverage
and
modify
of
things.
Speed.
E
E
E
D
E
So
Fred,
you
know
I'm
Sergi
created
that
simple
data
plane
mm-hmm.
If
we
could
create
a
couple
of
Yama
files
for
that,
so
that
we
could
use
you
know
I
know
maybe
a
little
boy
if
advanced
in
ping
Tom.
But
you
know
I
like
a
web
ngx
server
to
talking
to
a
REST
API
and
then
using
a
simple
data
plane
as
a
transport.
How
I
said.
D
D
E
D
D
D
B
I
agree
with
that
data.
Plane,
transparency,
that's
something
we
we
haven't
had
an
other
endeavors
and
I
mean
like
like
neutron,
for
example,
even
ODL
doesn't
quite
have
everything
for
data
playing
transparency
and
the
release
yet
for
because
she
doesn't
have
the
southbound
four
at
comp
really
quite
in
there
yet
and
a
bit
certainly
be
nice
to
have
it.
In
this
platform.
D
They
don't
really
care
a
lot
about
performance
or
latency
and
for
those
people,
a
simple
data
play,
probably
works
great,
you
know
and
then
you'll
get
people
who
care
a
lot
about
those
things
and
for
those
people
that
want
a
more
sophisticated
data
playing
and
and
so
welding
to
any
single
data.
Plane
is
probably
not
a
good
thing.
One
other
thing
I
think
we
will
find
is
that
we
actually
have
different
classes
of
data
point
in
the
system.
A
G
F
Concrete
example
is
definitely
good
because
you
know
like
I,
want
to
play
with
the
data
plane,
but
sometimes
I
just
can't
think
of
a
good
scenario
to
test
out
just
to
prove
it
out,
and
so
you
know,
having
a
concrete
example
to
say:
hey
I
want
to
connect
this
to
that
and
be
able
to
do.
X
Y
Z
is
just
as
so
much
help
to
be
able
to
get
in
and
use
it
with
just
a
concrete
example
that
you
can
then
extend
to
how
you
want
to
use
it
later.
On.
A
So
in
the
interest
of
time,
because
we
have
some
pretty
big
items
on
the
agenda,
so
I'm
gonna
wrap
them
real,
quick
with
the
this
part,
so
just
to
finish
up
by
SRV
I,
don't
think.
We've
had
much
movement
on
the
packet
net
side
for
for
this
particular
week.
So
that's
something
that
we're
gonna
have
to
work
out.
A
You
know
do
we
do
we
want
to
to
see
if
we
can
find
out
we'll
find
a
way
to
experiment
with
them
or
see
you
in
get
a
reserve
device
and
work
out
like
which
type
of
reserve
a
device?
What
we
like
there's
some
logistics
we
have
to
cover
on
on
that
side
before
we
can
really
before.
We
can
really
test
out
that
assumption
that
that
it
really
is
the
bios
issue
and.
A
So,
in
terms
of
the
going
back
to
the
a
to
the
main
agenda,
one
of
the
things
that
we
have
to
do
is
we.
We
have
very
little
time
for
the
open
source
summit
arrives
and
I
want
to
make
sure
that
we
have
enough
built
up
for
documentation
approachability
so
that
we
can
really
drive
people
who
are
interested
in
the
community.
F
A
C
C
A
Bring
it
up
so
a
couple
other
things
as
well
is
I.
I
think
it
would
be
very
good
for
us
to
have
someone
who
is
who
is
present,
who
is
willing
to
take
notes
on
some
of
the
types
of
questions
that
are
that
are
asked,
so
in
other
words,
if
there's
something
interesting
that
comes
up,
that
it
looks
like
network
service
meshes,
it
would
be
well
suited.
For
someone
asks
a
very
specific
question
that
we
may
not
have
the
answer
or
they're.
You
know
being
able
to
capture
that
information,
and
then
we
can.
A
If
it's
something
like
like.
Oh
it
always
it
always
bothers
me,
like
you
go
into
a
conference
and
someone
asked
the
question
is:
does
it
all
get
back
to
you,
except
that
connection
never
happens?
And
this
actually,
you
know
it
shows
a
level
of
commitment
that,
yes,
we
do
want
to
get
back.
We
do
want
to.
A
We
do
want
to
engage,
and
we
want
to
be
active
about
about
doing
so
and
and
so
I
think
if
we
were
to
to
go
with
with
something
like
that,
I
think
I
think
that
that
would
that
would
that
would
help
drive
attention
towards
us
as
well,
not
to
mention
it
would
also
help
us
for
our
own
records
and
were
our
own
information
as
to
what
type
to
work
out
what
type
of
questions
people
are
asking.
So
the
next
time
we
hear
that
question.
We
all
know
the
answer.
A
A
And
so
so,
I
think
like
we
need
to
work
out
this
week.
What
information
we
want
to
put
on
this
landing
page
like
what
scenarios
we
want
to
discuss
and
copy
over
some
of
the
data
from
the
repository
into
into
a
web
format.
In
this
scenario,
which
should
be
pretty
easy
because
it's
almost
all
most
of
our
stuff
is
marked
down
so
yeah.
G
C
Gonna
say
one
thing:
I
was
thinking
we
should
do
this
week.
Is
you
know,
I
was
planning
to
push
to
push
this
out.
You
know
as
a
new
repository
a
new
git
repository
I'm
the
website.
Basically,
and
then
what
I
was
hoping
we
could
do.
You
know
we
can
iterate
that
way
this
week
on
it
before
we
end
up.
Excuse
me
in
the
coming
week
before
we
end
up
pushing
it
live
at
the
end
of
next
week,
because
that
way,
everything's
pull
requests
right
and
we
can
have
it.
We
can
have
it
built.
F
D
A
So
we
don't,
we
don't
have
to
work
out
right
now
what
what
those?
What
exactly
should
be
on
that
I
think
we
should
rally
on
on
on
IRC
and
rally
around
the
repository
and
glue
requests.
So
so,
if
this
doesn't
already
on
github,
if
if
we
can
create
a
repository
that
I
have
the
that
I
have
a
network
service
mass
group
and
one
option
is
we
could
land
it
in
there,
and
that
means
that
we
don't
have
to
give
people
access
to
the
main
to
the
main
repo.
A
So
that's
that's
one
place
say
we're
good,
potentially
live
to
start
off
with,
but
the
main
point
is
that
yeah
we
need
have
a
repo
that
people
can
send
their
pull
request
to
and
you
access
to
and
I
think
I
think
it
should
be
okay.
How
to
to
preamp
some
of
the
questions
as
well
that
we
expect
to
do.
We
expect
people
to
see
like
we
know
that
certain
people
a
certain
questions,
often
so
we
should.
We
should
feed
the
page
with
those
with
those
facts.
Yes,.
C
D
C
F
C
I
did
for
now
I'll
just
I'll
just
highlight
some
things
right,
so
I
had
to
put
the
spider
up
here,
as
was
was
mentioning
to
me
for
now.
For
now.
I
just
put
you
know
a
home
link
which
obviously
goes
back
here,
a
link
to
the
source,
our
doctor
images,
if
we
want
to
have
a
blog
and
then
I
was
going
to
give
the
landing
page
for
the
open
source
summit
as
well,
where
we
could
put
a
bunch
of
collateral
and
things
there.
This
this
just
has
essentially
a
quick
rundown.
C
C
I
haven't
gotten
to
this,
yet,
but
roughly,
that's
it
so
and
and
we're
free
to
iterate
on
what
we
you
know
like
like,
like
Fredrik,
was
talking
about
we're
free
to
iterate
on
what
we
want
to
put
on
the
top
well
and
things
like
that.
But
but
I
really
like
the
way
this.
This
theme
for
Hugo
kind
of
flows,
I
think
it's
pretty
cool.
D
D
C
E
C
Yep
yep
yep
definitely
so,
and
I've
been
looking
at
some
of
those
some
of
those
as
well.
Definitely
so
so
this
is,
and
and
definitely
once
we
get
this
pushed
out.
We
can
all,
as
a
community
iterate
next
week
by
pushing
patches
to
this
this
website
and
tinkering
with
it
until
we
get
it
to
to
the
point
we
were
pretty
happy
and
and
I
and
I
definitely
expect.
We
will
continue
to
iterate
on
it
even
after
the
open-source
summit,
but
but
the
goal
next
week
should
be
to
just
get
something
that
we're
happy
with.
E
D
C
F
A
D
A
Okay,
so
group
to
test
out
depend
the
bot,
so
I
personally
think
the
pinna
pots
been
doing
a
pretty
good
job.
We
found
that
one
area
where
he
didn't
upgrade
properly
Kyle
fixed
that
up
so
overall
I'm
pretty
happy
about
it
and
anyway,
I
wanted
to
talk
about
their
experiences
with
depend.
The
bot
in
the
past
week.
B
A
One
area
that
I
that
I
think
that
is
not
as
not
as
well
hey,
Kyle
did
when
when
the
error
occurred,
because
we
did
have
one
problem,
the
weary
it
couldn't
upgrade
dependencies
properly
did.
Did
the
pendant
bot
open
a
pull
request
thing
or
an
issue
saying
that
it
couldn't
upgrade
or
would
did
you
have
to
go
to
the
dashboard
in
order
to
see
that
that
it
wasn't
working.
C
Anymore,
it
was
something
on
the
dashboard
and
it's
not
you
know
so
that
that
was
the
problem.
It
is.
They
do
note
that
I
forget
if
the
golang
support
is
either
alpha
or
beta,
but
but
I
remember
they.
They
did
note
that
the
golang
was
somewhat
recent
compared
to
some
of
the
other
dependencies
for
languages
so
that
that
might
be
part
of
the
problem,
but
but
that
was
you're
right,
that
was
mildly
annoying.
That
I
had
to
go
just
look
there
and
there
wasn't
a
ton
of
of
information.
C
However,
that
being
said,
this
is
a
completely
free
service
that
we're
using.
So
you
know
there
is
that
as
well.
The
other
thing
that
I
really
like
about
the
depend
about,
though,
is,
is
that
the
the
source
code
for
it
is
for
the
actual
bot
is,
is
completely
open
source.
So,
if
we
ever,
if
we
ever
did
hit
issues
or
anything,
we
should
be
able
to
look
at
the
source
should
we
so
choose
and
in
theory
we
could
actually
run
our
own
version
of
the
bot
hosted
somewhere
else
if
we
wanted
as
well.
C
A
That's
that's
good
to
know
so
if
it
ever
becomes
owner
s
where
we
have
to
keep
looking
at
this
dashboard
to
work
out.
If
these
problems
have
occurred,
then
one
option
that
we
that
we
have
then
is
to
modify
the
the
code
to
do
what
I
wanted
two
things
we
can
either
have.
It
create
an
issue
when
such
a
problem
occurs
and
block
until
it's
block.
A
D
So
I've
got
a
lot
of
input
and
I've
been
trying
to
sit
down
and
do
a
draft
meeting
every
week.
For
me,
and
so
I
become
really
clear.
You
need
to
get
a
lot
rotor
a
lot
punchier
and
very
focused
on
on
goals
and
the
purposes
of
the
working
group.
Those
goals
need
to
be
basically
about
clearly
documenting
the
things
that
go
into
network
service
match.
D
So
basically
how
do
people
you
know
basically
how
the
architect
document
in
the
architecture
documenting
the
api's
from
the
people
of
things
that
actually
plug
into
it
and
so
forth
and
I
think
this
will
eventually
into
being
quite
crucial
because
we
are
going
to
want
to
have
people
who
want
to
do
things
like
external
network
service
managers
or
proxy
metric
service
managers,
that
plug
into
the
system
will
have
people
who
are
wanting
to
plug-in
data
planes
and
so
forth.
So
will
definitely
definitely
need
to
get
that
redrafted,
but
have
not
yet.
D
Anyone
who
wants
to
actually
take
a
pen
I'm
happy
to
grant
edit
rights
to
the
document
and
I
think
you
know
several.
Have
you
already
have
them
so
I
mean
the
lovely
thing
about
about
Google
Docs
is
to
keep
this
stream,
so
nothing
is
truly
lost.
So
please
don't
don't
feel
like
I'm
sitting
on
this
work
item.
A
Do
we
find
important,
and
you
know
once
we
once
we
have
those
and
what
we
can
do
is
create
the
set
of
heuristics
describe
like
oh,
you
want
horizontal
scalability.
You
know
the
this
is.
This
is
what
you
should.
This
is
what
you
shouldn't.
Look
at
you
know
you
should
look
at
how
to
twelve
factor
apps
work.
How
does
how
does
kubernetes
horizontal
scaling
work
and
what
is
it
like?
What's
required
like
for
for
your
application
to
like
what
properties
your
application
just
have
and
I
think
what's
whittled
it's
going
to
end
up
happening?
A
Is
that
we're
gonna?
Have
people
who
have
different
sets
of
dates?
They're
not
gonna,
have
the
needs
for
everything
for
all
of
those
goals,
but
if
you
have
an,
if
you
have
a
need
for
data
plane
must
let
your
data
plane
needs
to
be
fast,
cannot
have
anything
any
intermediaries
because
of
the
performance
requirements
and
it
needs
to
be
horizontally.
Scalable
then,
is
I.
We
can.
They
can
look
at
the
various
heuristics
and
just
and
just
learn
from
it
and
then
that'll
help
them
make
better
design
decisions
as
they
move
forward.
A
So
that's
the
sort
of
patter
that
I'm
I'm
thinking
of
at
this
point,
because
I
think
there's
too
many
ways
too
many
types
of
things
we're
trying
to
that.
We're
talking
about
that
until
we
have
a
very
solid
definition
of
what
a
CNF
even
is,
which
we
haven't
even
gotten
to
yet
in
the
community,
then
you
know
you
saying:
hey
here's
yours
to
create
them
doesn't
doesn't
make
as
much
doesn't
make
as
much
sense,
but
saying
these
are
the
five
goals
that
people
care
about
I
think
can
help
drive.
C
A
D
What
is
there
is
a
list
of
which
NICs
are
with
which
flavor
at
packet,
and
so
that
actually
is
helpful.
The
second
thing
that
I
dug
up
is
the
availability
of
flavors
varies
radically
by
site
in
packet,
and
so
what
are
the
issues
that
we
were?
Having
was
the
only
flavor
that
was
available
in
the
Canadian
site
that
that
was
where
Sergey
was
trying
to
work
was
not
a
particularly
helpful
flavor
in
terms
of
giving
the
stuff
working
and
we
discovered,
for
example,
there's
San
Jose
site
and
have
all
odd
things
there.
D
A
Yeah
just
to
just
to
be
clear,
so
PACA
dead
not
to
be
confused
with
the
one,
and
only
ed
is
mentioned
that
there's
no,
that
even
in
the
even
in
the
site
there
may
be
that
there
may
be
variants
in
in
hardware
and
configuration
so
so
I
don't
think
we
can
rely.
Given
that
that
document
it
doesn't
fully
coincide
with
the
information
that
I
was
told
about
how
you
can
pick
an
instance
and
end
up
with
a
with
potentially
a
different
card.
So
that's
something
we
should
be
careful
with.
A
Completely
agree
and
I
also
think
that
what
we
should
do
is
we
should
work,
try
to
work
out
who
the
right
person
is,
who
controls
that
particular
decision
and
see,
if
hosting
convinced
them
to
to
flip
that
decision
around
and
say
look
you
want
to
tackle
these
particular
groups,
and
then
it
appears
that
you've
mentioned
you
want
to
head
off
in
this
direction
and
if
that's
true,
then
you
really
need
to
enable
this
feature
and
take
a
look
at
it.
I.
D
D
Some
way
of
getting
a
deterministic
result,
if
you
need
a
deterministic
result
right,
if
they
could
literally
just
give
you
a
little
checkbox
that
says
you
were
guaranteed
the
advertised
Nick.
When
you
select
the
flavor,
they
can
still
have
diversity
in
their
test
in
their
in
their
underlying
hardware,
because
you're
working
all
of
that
out
as
hard
and
expensive.
But
but
if
I
like
XYZ
flavor
and
it's
supposed
to
have
ABC
Nick
and
I
click,
the
little
checkbox
I'm,
damn
well
gonna
get
ABC
Nick
I.
A
D
D
B
E
B
E
C
E
C
The
reason
that
came
up
actually
John
was
when
I
was
reviewing
it.
You
know
the
directory
structure
you
had
I
was
confused
at
first
because
it
didn't
match
what
we
had
in
the
network
service
mesh
repository.
But
then
it
made
sense
to
me
when
you
indicated
that
you
were
kind
of
thinking
of
almost
a
clean
slate
out
of
tree.
E
So
what
I
did
was
a
trajectory
idea:
I
wrote
script
that
basically
uses
the
work
search.
He
had
done
and
just
pulled
a
bunch
of
the
existing
make
files
and
stuff
and
created
night
of
tree
template
structure.
So
now
you
can
basically
run
a
script.
I'll
create
a
natural
tree
NSM
for
you
to
go
and
do
your
own
work,
and
then
you
can
do
a
build
against.
They
link
to
the
NSM
main
repo
to
basically
create
a
separate
plugin
for
you.
D
I
think
there
are
two
really
crucial
points
that
we
have
to
make
sure
we
do
no
matter
what
we
decide
right
and
then
the
two
really
crucial
points
are
number
one.
We
need
to
remain
welcoming,
meaning
that
for
reasonably
kinds
of
things
we
are
welcoming
to
having
an
appropriate
place
to
put
them
in
tree
and
number
two.
We
have
to
remain
flexible,
meaning
it
should
be
possible
to
do
work
out
of
tree.
If,
for
any
reason,
you
decide,
you
want
to
work
on
a
tree.
C
Everything
else
is
gravy,
definitely
and
I
and
I
will
I
will
indicate
that
that
past
experience
you
know
years
back
in
Neutron
entry
for
things
got
got
complicated,
just
just
because
you
know
so
so
that
would
ask
that
got
unwieldy
at
that
point
now.
I
I,
don't
know,
do
most
see
and
I
plugins,
for
example,
live
out
of
tree
or
is
there
a
central
or.
D
How
does
that
work?
They
mostly
live
out
of
tree
and
so
I
guess
the
the
thing
the
thing
I
want
to
be
careful
about
is
I
want
to
I
want
to
be
avoid
the
appearance
of
there
being
the
one
true
data
plane,
but
at
the
same
time
we
have
to
do
some
data
playing
work
in
tree,
just
to
get
done
right
and,
and
so
I
don't
want.
I
I
agree
with
you
that
you
can
get
out
of
hand
at
some
point.
D
If
we
do
get
out
of
hand
under,
we
have
to
sort
of
figure
out
how
we're
going
to
handle
that
reasonably,
but
we're
far
from
the
day
of
getting
out
of
hand.
So
I
think
we
need
to
remain
vigilant
about
getting
out
of
hand,
but
I
wouldn't
want
someone
to
come
and
look
at
network
service
professions
say,
for
example,
oh
that's
only
a
few
GP
well.
B
A
Want
to
be
careful
with
as
well
is
that,
if
someone's
trying
to
do
something
entry,
then
that
means
that
someone
from
we
either
have
to
give
those
communities
commit
access
to
merge
in
their
own
stuff,
which
gives
us
commit
access
to
much
more
more
or
we
have
to.
We
end
up
being
the
gate
they
gatekeepers
on
an
area
where
we
really
shouldn't
be
the
gatekeepers
and
so
I
think
I.
Think.
A
E
Just
now
is
that
I
mean
I
had
to
do
some
detective
work
to
figure
out
what
all
the
files
were
for
creating
a
sample
data
point
where
the
where
in
the
tree
and
that's
why
I
created
my
own
template
tree.
So
it
took
me
a
Dale
fussing
around
to
get
it
right.
So
if
every
ties
to
spend
a
day
well,
I
I
knew
my
way
around
a
little
bit
already
so
I
mean
Emily
coming
in
blind
who
says.
Oh
I
wanted
to
jump
in
and
create
a
sample
data
plane.
B
B
That
and
and
I'm
aware
of
that,
because
I
tried
to
do
some
of
the
same
thing.
I
took
all
the
sample
data
plain
code
tried
to
figure
out
where
it
all
was
and
got
to
that
point,
and
it
is
a
little
bit
complicated
because
there's
a
lot
of
files
in
different
places,
all
right,
but
that's
useful,
I,
figured
that
once
you
did,
you
follow
what
you're
talking
about
John
and
then
people
if
that
data.
B
If
that
thing
were
to
be
put
in
the
pull
request
and
they
were
all
back
to
a
fork
or
something
and
then
put
in
a
pull
request-
that'sthat's
the
workflow
that
I
envisioned
in
my
head
for
what
I
was
going
to
do.
Yeah
I
put
it
where
it
was
convenient
to
do
development
and
then
put
it
back
and
then
test
it
before
I
did
the
pull
request?
I,
don't
know
I
mean
that's
just
my
own
peculiar
way
of
doing
things,
but
it
kind
of
made
sense
that
I
don't
know
whether
early
in
the
development
phase.
B
F
B
You
know
whatever
different
governance
roles,
you
know
it
could
get
I
think
I
have
certain
amount
of
it
in
this
project
is
probably
a
good
idea
for
a
while
I'm,
not
questioning
people's
way
of
and
I
think
that's
separate
from
what
workflow
you
uses
an
individual
developer
in
your
own
space
fork,
whatever
you're
going
to
do
you
know,
but
at
some
point,
when
you
get
ready
for
a
pull
request,
we
should
converge
on
something,
but
for
at
least
for
the
first
four
five
six.
Maybe
they
go
back
in
here.
B
A
I
think
something
we
can
do
that'll
that'll
help
in
the
future
as
well.
As
you
know,
we,
if
we
identify
you
know
where
what
files
are
we're
necessary,
they've
been
scattered
around
and
and
so
on.
We
can
start
to
structure
the
codebase
in
such
a
way
that
this
becomes
an
easier
or
an
easier
process
and
worse,
well,
one
one
potential
path
towards
this
as
well
as
we
we
could
potentially
expose
out
some
form
of
of
an
API
or
something
similar
and
use
some.
A
You
know
we
can
use
some
form
of
hugs
or
something
or
something
somewhere.
That
knows
how
to
abstract
a
lot
of
this
away,
so
that
way
that
it
really
becomes
very
easy
for
a
developer
to
type
in
the
code
in
the
appropriate
sections
and
get
the
results
that
they're
that
they're
expecting,
and
so
you
know
so
I
think
that
you
know
we
should.
E
You
take
a
look
at
what
I
did
I'll
post
it.
I
did
he's
essentially
what
you're
talking
about
friend
and
in
that
I
created
a
tree.
They
had
all
the
files
for
sample
data
plane
and
make
an
cut
dynamic
file
so
only
built
the
sample
data
plane,
so
that
could
be
in
tree
or
a
tree.
So
I
think
it
makes
the.
E
Care
solves
both
problems,
so
you
could
do
it
in
tree.
If
you
wanted
didn't
you
do
a
tree.
If
you
want
to
there's
no
restriction,
it
allows
people
to
you
know,
do
a
pool,
as
Fred
said,
you
know,
Thompson
bring
into
a
pool
request,
and
then
you
know
push
it
back
in
again
and
then
we're
fairly
confident
that
that
pool
and
that
change
request.
There's
only
just
touching
the
sample
code,
it
won't
touch
anything
else
which
makes
reviewing
it
a
lot
easier,
cool.
A
If
you
can
do
one
thing
for
me
as
a
if
you
can
add
in
a
github
issue
talking
about
providing
an
easier
way
for
these
integrations
to
to
work,
just
don't
mess,
we
code
or
anything
just
say
just
so.
We
have
something
tracking
this
and
in
terms
of
Hana
and
the
hardware
nix
there's
a
link
on
the
on
the
agenda,
and
if
we
have
time
do
we
can
we
can
cover
it
next
week
and
more
in
more
detail
and
people
gonna
have
that
way.