►
From YouTube: SONiC DASH Workgroup Community Meeting Aug 2 2023
Description
Merged 2 PRs PR403 and PR404, and opened a couple more for test case creation and P4 DPDK exploration. @Chris Sommers and @Kristina Moore performed a ‘stale branch’ cleanup of the Repo. Next week NVidia would like to revisit the ACL Tags conversation.
A
78Th
meeting
and
the
last
time
we
were
here
together,
I
hadn't
sent
the
notes.
Yet
we
talked
about
pr404
talking
about
the
or
might
have
been
402
talking
about
the
throwing
out
that
underlay
routing
functionality
here
in
this
information
here,
and
so
we
all
talked
about
that
and
left
some
comments
in
the
pr
and
left
it
open
for
people
to
talk
about,
and
then
we
also
closed
a
couple
of
PR's
and
we
welcomed
kumaresh
and
some
different
people
and
then
over
here.
A
This
is
the
the
board
that
we've
been
working
on
and
we
were.
We
changed
a
cup
oops.
We
changed
a
couple
of
these
items
to
closed,
so
these
ones
here,
Mark
just
done
so.
Marion
had
fixed
this
bmv2
pipeline
source
code
change,
and
then
we
had
a
couple
of
more
items
here
that
were
done,
and
then
we
have
these
items
that
are
still
to
do
this:
one's
the
oldest
one
number
289,
and
this
one
came
from
Prince.
This
generate
PSI
for
Apple
tags.
A
A
Okay,
great
thank
you
and
then
I
can
pop
it
in
here.
That's
awesome
thanks
for
letting
me
know,
and
then
we
did
open
like
an
actual
issue
for
this
p40bk
on
the
horizon,
because
we
talked
about
it
last
week
and
I
think
Rasmus
said
she
would
follow
up
on
it.
So
so
we
have
that
and
the
rest
of
those
are
done,
but
I
was
curious.
I
ended
up
joining
the
P4
call
this
week,
and
so
I
was
curious.
C
A
D
A
E
D
A
totally
new
group
of
apis
for
next
hope,
ID
as
well
as
nexop
ID
group,
will
have
to
be
implemented
as
part
of
a
subsequent
PR.
So
current
PR
just
addresses
route
next
hope,
ID
apis
and
for
the
holy
CMP
you
will
have
to
be
a
separate
PR.
So
as
of
now,
we
are
adding
the
behavior
for
out
and
the
behavior
for
hair
pinning
we
are
leaving
it
unchanged
from
the
current
implementation
till
the
CMP
gets
implemented,
yeah
in
a
different
job.
D
Yeah,
so
the
fourth
we
Implement,
Port
ID
could
be
used
as
next
hop
ID
in
the
current
implementation.
Of
course,
future
implementation
can
now
support
for
interfaces
and
other
things,
but
to
have
support
for
interfaces.
First,
an
interface
needs
to
be
added
in
bmv2
and
so
on.
So
each
extra
apis
that
we
add
have
to
be
their
own
PR
and
add
additional
functionality.
B
D
B
A
D
A
A
E
I'd
like
to
make
a
comment:
if
you
look
in
issues-
okay,
it's
just
a
general
comment
to
keep
people
informed
if
they've
been
paying
attention,
but
fellow
named
Camille,
kudne
he's
a
Microsoft
employee,
very
active
inside
I
think
he's
a
maintainer
inside.
It
looks
like
he's
going
through
and
doing
a
big
scrubbing
operation
on
okay
on
the
dash
PSI
implementation,
which
is
a
good
thing
he's
trying
to
make
a
compatible
to
compile
it
into
sync
D,
for
possibly
a
virtual
switch
have
an
emperor.
E
We
talked
about
probably
a
year
and
a
half
or
two
years
ago.
Could
this
ever
be
done?
So
it
looks
like
I'm
trying
to
align
it
with
a
standard,
PSI
implementations.
So
it's
going
to
require
a
bit
of
work
on
various
people's
part
he's
doing
the
most
of
it,
but
he's
gonna
be
submitting
issues
and
poll
requests
to
to
align
the
website
and
get
it
out
of
its
little
sandbox,
which
it's
in
and
make
it
a
little
more
conformant.
E
E
F
E
I
think
he's
trying
to
take
the
regenerated,
PSI
headers
from
latest
commits
and
manually
copy
them
into
the
psy
repo
Dash
version
to
bring
it
up.
So
that's
just
one
of
the
things
he's
working
on
and
it
looks
like
zigon
is,
is
Angel
based
on
that,
although
Intel
might
want
to
keep
an
eye
on
what's
going
on
too,
because
you
you
guys
and
Nvidia
have
been
the
most
active
in
you
know,
curating.
E
E
A
G
E
G
E
Yeah
and
and
I
I
just
need
to
correct
myself.
It
looks
like
this
okay
right
there
yeah
it's
actually
merging
into
open
compute
Master,
oh
so
if
I
was
wrong
about
it.
Being
that
he's
going
from
the
dash
Branch
into
master
I,
don't
know,
I
think
that's
a
Psy
maintainer
kind
of
decision
which
I
have
a
lot
to
say
about,
but
it
makes
your
comment
more
timely.
G
E
E
E
G
G
A
There
it
is
okay,
all
right
all
right.
Thank
you,
so
I'll
make
sure
and
add
that,
okay,
so
back
to
what
we
were
talking
thanks
Vincent
for
that
that's
awesome.
So
basically
it
looks
like
Camille's
doing
this
work
and
I
messaged
him.
While
we
were
just
talking
now
and
I,
let
him
know
that
I
added
him
to
the
repo,
so
it
would
be
easier
for
him
to
work
with
us.
E
G
So
another
goal
actually
has
to
say
without
Chris
would
be
to
run
test
cases
like
since
we're
using
the
side
Challenger
the
side,
changer.
Okay,
either
interface
with
the
sci3
server,
which
is
the
current
model
or
the
Cindy
which
I've
played
with
and
it
works
well
yeah,
so
maybe
I
don't
have
a
goal
is
to
get
the
thing.
The
integration
tested
with
the
side
Challenger
and
some
test
cases.
E
E
A
A
A
H
A
Nice
to
see
you
nice
to
see
you,
so
this
is
kind
of
the
Cadence
of
what
we
do
we
get
together.
We
socialize
we
talk
about
PR's
issues,
forward,
movement
in
the
repo
and
and
the
repo
here
Naveen
is.
We
actually
have
different
sections
with
documentation
and
probably
what's
more
interesting
to
the
developers
is
the
pipeline
area
and
that's
where
the
bmv2
and
the
side
pieces
are
so
just
FYI,
but
there
there's
a
lot
of
documentation.
A
That's
the
high
level
design
here
and
it
describes
a
lot
more
things,
and
then
we
have
this
one's
more
authored
by
me
and
Prince
and
whoever's
helping
and-
and
these
are
the
older
documents
that
are
actually
still
pretty
useful,
with
a
lot
of
pictures
and
things
like
that
with
packet,
Transformations
and
pipelines,
and
Enis
and
vnis
and
encapsulation,
and
examples,
and
things
like
that.
So
that's
what
that
is.
So,
okay,
thanks.
Thanks
for
coming
on
camera,
okay,
yeah.