►
From YouTube: SONiC DASH Workgroup Community Meeting Aug 16 2023
Description
Removal of ACL tags from P4
Kamil uplifting libsai, longterm goals to make SONiC instance that includes DASH behavioral model
Fix APIs and reconcile small shortcomings
Chris reviewing PRs, checking CI pipeline
If anyone has 'Stale' branches, please tidy them or bring to Kristina or Chris' attention
A
A
These
are
the
basically
the
notes
that
I
sent
out
from
last
time
so
up
here,
I'm
doing
a
new
thing
where
I'm
putting
basically
our
project
items
that
we
looked
at
last
time.
More
of
in
a
format
like
this,
where
you
can,
we
can
click
on
them.
Last
time
we
continued
the
conversation
about
the
Apple
tags
and
we
all
agreed
that
maybe
we
wouldn't
need
them.
So
we
talked
about.
B
A
There
and
I
I
ended
up
opening
an
issue
to
go
ahead
and
remove
those
from
P4,
and
then
we
Chris
mentioned
that
Camille's
doing
some
work
in
the
background
for
us
on
the
repo.
So
that's
Camille
good
Nick.
He
works
over
on
my
end
and
so
I
talked
to
him.
Yesterday
I
thought
maybe
he
could
come
explain
some
of
his
changes
or
the
work
he's
doing
he's
in
a
different
time
zones.
A
So
I
don't
know
if
he'll
show
up
today,
but
maybe
next
week,
and
so
we
could
look
at
his
closed
or
merged
items
there.
So
that's
what
happened.
Oh
and
then
of
course.
Last
week
we
had
a
couple
of
new
Arista
people
joined
the
team
and
Javon
and
Max.
Did
you
receive
the
meeting
notes
from
last
week
that
I
sent
out.
A
A
The
number
309
which
is
from
before
the
update,
scaling,
underlay
routing
service
tunnel,
private
link,
encoding
and
related
that
to
psi
attributes
for
Apple
rules
should
include
list
of
IP
prefixes,
because
Camille
was
working
on
this.
So
I
put
these
into
the
list
here,
Vincent
and
related
them
to
each
other,
and
so
we'll
see
if
we
can
get
work
done
on
those.
When
prints
comes
back,
yeah
no
problem
and.
C
C
D
C
C
A
Okay,
cool
thanks
thanks
Chris
yeah
yeah,
so
I'll
go
ahead
and
put
this
into
our
list
and
I.
Think
I'll
start
filtering
out
all
this
work
that
we've
done
here
so
I'll
do
that
we
won't
have
an
update
today
from
rushman
unless
someone
else
on
the
call
from
Intel
might
be
able
to
tell
us
about
408
the
P4
dpdk,
possibly.
E
A
Until
next
week
she
said,
thank
you,
chinos
yeah,
okay,
so
it's
kumaresh
on
the
coast,
I,
don't
see
him.
He
was
gonna.
Take
a
look
at
this
first
one
here.
I
can
check
with
him
later
too
so
he's
in
Azure
boot
camp
this
week.
So
I'll
take
a
look
at
this
one
offline,
the
meter
policy
scale-
and
we
also
have
a
this
one
here.
Did
this
Marion
did
this
one?
A
D
F
A
Okay
and
then
so
I'm
trying
I
I
think
this
one
here
the
clarifying
scale
in
route
so
I
feel
like
we
did.
Do
the
update
to
the
scale
tables
and
everything
a
few
weeks
ago,
but
I'm
trying
to
understand-
and
maybe
it's
me
I
was
trying
to.
Maybe
it's
me.
Why
is
it
important
to
know
whether
the
routes
are
inbound
or
outbound
and
knowing
the
scale
of
those,
maybe
if
you
guys
could
help
me
or
help
me
understand
that
maybe
I
could
take
it
back
to
the
team
internally.
A
A
A
A
A
A
C
A
A
B
A
B
C
C
B
A
F
A
Hi
so
Camille
hi,
I'm
Christina.
This
is
everyone
in
the
dash
community.
So
I
have
everyone
here
from
broadcom
AMD,
Intel,
keysight,
peel,
Vision,
Nvidia,
gosh,
I'm,
sorry,
if
I'm
forgetting
anyone
dream,
big
semiconductor,
Arista,
Etc
and
so
a
Camille.
We
go
through
the
repo
once
a
week
and
the
community
call
here
and
go
over
pull
requests
and
issues
and
Q
a
and
things
like
that.
So
everybody,
this
is
Camille,
he's
a
principal
engineer
over
in
Prince
Camilla
I'll.
Let
you
introduce
yourself.
B
Hi
everyone,
I'm,
Camille
and
I
will
I
work
in
Microsoft
for
11
years
right
now
and
I,
don't
know
seven
or
eight,
maybe
in
in
Sonic
and
lately
I
was
given
a
task
to
to
make
some
changes
in
the
dash
repo.
So
our
goal
is
to
make
a
some
like
something
similar
that
we
had
in
the
side.
Ideas
like
the
wheelchair
Suite.
B
So
we
want
to
have
ability
to
connect
the
bmv2
with
a
P4
model
and
to
the
CD
and
be
able
to
you
know
to
make
make
use
of
the
dash
apis
from
The,
Arc
agent.
I.
Think
that
I
think
that's
our
goal.
There
is
also
another
possibility
that
we
that
we
are
deciding,
because
the
current
Dash
repo
is
just
supporting
only
the
dash
dash
part
of
the
PSI
API.
So
there
is
no
other
underlying
functionality
for
other
apis
and
although
I
saw
that
someone
already
posted
some.
B
A
B
Yeah
so
I've
been
doing
last
week
or
last
two
weeks,
refactoring
of
the
site
in
the
dash
report,
so
I.
Basically
the
fact
of
everything
that
almost
everything
that
was
there
I
found
some
bugs
and
some
issues
which
I
already
opened
in
the
in
the
dash
issues.
I
saw
that
you
already
mentioned
one
of
my
one
of
my
bags
and
I
refactored.
The
codes
of
this
to
improve
the
code.
B
A
A
B
Maybe
I
have
just
one
question
here
sure,
because
what
I
noticed
is
that
those
Dash
feathers
in
the
industrial,
those
are
like
auto-generated
from
the
P4
model
and
those
are
actually.
There
are
some
changes
which
are
different
from
the
actual
Fighters
that
are
in
the
site
in
the
side
level.
So
I
think
when
I
spoke
with
Gohan,
he
told
me
that
we
should
probably
treat
the
daso
repo
as
a
grant
Truth
for
the
dash
headers.
B
A
F
Yeah
there
is
this
limitation
for
now.
As
far
as
I
know,
there
was
a
work
done
to
just
partially
support
that
and
either
expand
a
rule
or
something
like
a
similar
to
that
or
support.
Only
one
value
out
of
the
list.
I,
don't
recall
who
was
doing
that,
but
it
was
someone
from
Microsoft,
so
I
can
I
can
check
that
and
point
to
how
this
is
being
overcome
in
the
BMV
too,
but
it
is
kind
of
like
partially
supported
yeah.
E
F
Oh
that's
what
our
agent
is
doing
is
expanding
tags
that
come
from
from
the
controller,
but
it
doesn't
expand
lists
so
or
Cajun
basically
still
generates
one
rule
with
a
list
of
prefixes
that
came
from
text,
but
expansion
of
a
list
is
done
in
the
style
layer.
I
can
look
for
the
plural
request
it.
It
should
have
been
emerged
long
ago
to
support
that
in
PSI
implementation
for
bmv2.
D
It's
kind
of
related
to
the
issue
that
I
brought
again
last
time.
It's
the
bmv2
is
doesn't
support
everything
that
needs
to
sorry.
We
generate
the
apis
from
the
bmv2,
except
that
there
are
a
few
caveats
on
that
right
now
and
that's
the
problem
we've
listed
in
list
of
prefix
and
all
that
jazz
that
we
find
in
ACL.
A
E
Both
all
software,
such
as
head,
the
Gap
that
they
do
not
support,
lists
directly
and
work
around,
for
that
is
the
same
for
all
of
them,
which
is
have
some
layer
of
Control
software
above
the
software
switch,
expand
the
lists
out
into
digital
career
prefix
entries,
that's
the
same
workaround
for
all
of
them.
I
would
recommend
a
reference
model.