►
From YouTube: SONiC DASH Workgroup Community Meeting Oct 5 2022
Description
PR225 for community to try for Chris, possibly merge by Friday
OCP: Taras presenting SAI testing catch-up
Scale #'s updated in documentation
A
A
B
I'll
just
talk
a
little
bit
about
progress,
working
on
an
issue
that
Hannah
filed
when
he
was
trying
to
write
an
IPv6
test.
He
was
adding
IPv6
the
seal
support
and
now
providing
a
unit
test
for
that
and
the
test
gets
stuck
when
it
goes
from
test
one.
The
tested,
because
I've
been
working
on
that
for
several
hours-
and
you
know
I,
don't
have
resolution
yet,
but
I'm
working
on
it
and
I'll
try
to
help
more
debugging
details
to
the
issue.
You
know
as
I
make
progress.
Yeah.
B
It
it's
nothing
you're
doing
wrong.
Believe
me,
it's
in
fact
you
can
take
the
existing
ipv4
test
and
just
duplicate
it
in
another
file
with
a
different
name
and
the
same
bug
happens
when
you
switch
from
test
one
to
test
two.
It
just
hangs
and
it
has
something
to
do
with
the
server
Communications
between
Thrift
and
grpc.
You
know
it's.
It's
I'm
having
to
drill
in
pretty
deep.
B
C
Right
and
as
you
know,
Chris
you
know
I
validated
the
V6
code
by
essentially
removing
the
V4,
you
know
file,
and
then
you
know
running
it
and
then,
since
that
V6
was
the
only
test
in
the
in
the
directory.
It
ran
fine
and
you
know,
but
however,
I
could
not
really
check
in
or
commit
to
it,
because
the
fact
that
it
would
have
basically
broken
everything
else.
You
know
had
it
I've
done
it
so
on.
C
B
B
D
B
D
B
I
would
just
mention
that
I
know
I,
don't
know
if
anyone
else
has
tried,
but
I
had
the
pull
request
where
I
use
Azure
ACR
for
for
Dockers.
Instead
of
my
Docker
hub
and
I
wonder
if
anyone
else
has
tried
to
run
that
branch
and
verify
it
works
for
them,
because
it's
it's
been
in
the
queue
for
a
couple
weeks
now
and
I
would
eventually
like
to
get
it
merged
in.
B
C
B
Containers
right
so
yeah
that
was
that
wasn't
that
was
definitely
an
interim,
so
I
guess
what
I'll
say
is
unless
there's
any
feedback
to
the
contrary.
I
would
like
to
merge
this.
Let's
say
Friday
unless
there's
any
dissension,
because
I
don't
want
to
think
the
language
there's
other
things,
that'll
have
to
change
once
that's
put
in
so
I
want
to
kind
of
unblock
the
queue.
B
Okay,
anyone
is
is
Keen
interest
in
trying.
All
you
have
to
do
is
clone
it
and
do
make
all
and
try
it.
That
would
be
enough,
and
you
know
in
running
it's
I've
run
it
dozens
of
times.
It's
always
nice
to
have
an
independent
person.
Try
it
just
to
make
sure
there's
not
an
environment
dependency
that
I
I
assumed.
C
Sounds
good
yeah
one
thing
that
Chris,
you
know
you
know.
In
our
conversation
we
talked
about.
There
were
two
workflows
right.
The
second
one
was
somebody
else
were
to
make
changes
to
the
container
and
want
to
check
in
and
so
forth
that
I
have
not
given
it
a
shot.
So
I'm
not
sure
if,
if
you
want
somebody
to
take
a
look
at
it
or
you
think
that
you
know
there's
already
enough,
testing
has
been
done
to
that.
You
know.
You
know
that
it's
kosher.
B
B
B
B
Yeah
towards
the
bottom,
the
very
end.
There's
all
these
workflows
right.
It's
kind
of
crazy
looking,
but
if
anyone
wants
to
try
and
try
to
let's
say
just
make
a
test,
Docker
file
and
practice
these
workflows,
they
have
to
work
with
them.
Otherwise,
the
first
time
someone
actually
wants
to
do
it,
we'll
just
we'll
just
do
it
then
there's
enough
I'm
feel
confident.
This
is
95
correct.
B
B
So
yeah,
oh
there's
no
urgency
really
in
someone
trying
all
those
things
I
think
it's
just
good
practice,
but
people
are
busy,
so
it
can
always
be
done
on
demand,
for
example,
whoever's
working
on
the
bmb2
like
Marian
or
his
colleagues
or
other
people.
If
they're
working
on
the
new
p4c
compiler
changes
they're
going
to
eventually
have
to
run
into
this
and
we
can
work
together,
then
there's
no.
E
B
E
E
A
F
E
A
When
we
had
the
original
documentation
we
had
in
the
transforms
document,
we
had
some
scale
numbers,
some
initial
swing
at
the
scale
numbers,
and
they
were
located
here
inside
of
the
packet
transforms
document
here
at
the
very
top
one
of
the
initial
documents
we
were
doing
scale
per
dpu
here
and
then
we
replicated
these
numbers
over
into
the
this
document,
which
was
the
testing
the
Hero
Test,
and
so
this
is
what
we
updated.
Was
these
two.
G
A
C
F
Present
in
I
think
Sonic
Dash
hld.md
file-
it's
just
as
a
hero
test,
did
not
have
these
numbers
in
it.
So
basically,
if
the
numbers
got
synchronized
across
the
pages,
so
there
is
no
one
page
says
the
number
and
the
other
Pages.
The
other
number
right
there
already
they're
present
for
a
couple
of
months
now.
G
D
G
That's
actually
a
good
idea.
Good
thing
you
take
that
down.
That
is
something
that
we
should
be
working
with.
Michael
I
think
that
not
a
lot
of
people
use
IPv6
on
the
inner,
but
we
should
set
the
expectations
as
if
they
do,
we
have
a
couple
of
customers
that
use
that
large
Enterprise
customers,
so
maybe
Michael
could
help
us
quantify
that
a
little
bit
better
Christina,
that's
a
good
good
point,
just
the
IPv6-
and
this
is
the
overlay.
G
B
G
G
E
G
G
G
B
G
Yeah
we
we
definitely
can.
This
has
to
be
like
I
I,
think
this
benefits
everybody,
whether
building
Hardware
or
whether
they're
working
on
the
simulator
or
whatever
having
all
these
different
tests
available
is
is
a
great
thing
and
the
T-Rex
has
made
there
there.
It's
not
the
same
as
it
was
a
year
ago,
like
a
year
ago.
You
couldn't
do
these
tests
with
T-Rex
anyways.
It
wasn't
fast
enough
to
I
think
it
was
limited
to
one
core
or
something
it's
now
all
DP
DK
enabled
multi-core
like
it's.
G
It's
actually
can
generate
the
traffic
patterns
that
we
want
at
the
rate
we
want.
The
only
thing
is,
of
course,
we
have
to
point
serious
Technologies
towards
it,
so
I
can
get
to
those
rates,
but
the
software
itself
is
not
limited
anymore,
and
so
we've
successfully
been
able
to
deploy
in
our
Network
and
test.
You
know
first
product
using
the
using
the
T-Rex
reach
the
numbers
now
that
it's
dpdk
enabled
so
we're
we're
pretty
impressed
with
that.