►
From YouTube: Antrea Community Meeting 11/22/2021
Description
Antrea Community Meeting, November 22nd 2021
A
Perfect
good
morning,
good
afternoon
or
good
evening,
this
is
the
anthria
community
meeting
and
today
is
a
tuesday
november,
the
23rd
and
unless,
of
course,
you're
in
united
states
where
it
will
still
be
monday
november,
the
22nd.
So
for
today
we
don't
really
have
any
books
of
intelligent
agenda.
As
john
jun
asked
on
the
slack
channel,
we
can
have
a
chat
about
our
strategy
for
secondary
network
support.
A
A
So,
john
john,
do
you
have
a
any
idea
you
like
to
share
on
the
topic.
B
Yes,
send
some
story
yeah,
maybe
I
can
add
a
little
more
information
here,
yeah
sure
yeah.
I
think
when
we
started
singer
for
malik
paul
second
network
supporting
andrea
in
collaboration
with
intern.
B
At
that
time,
I
think
we
were
thinking.
Maybe
we
can
build
a
warning.
One
thing
I
plugging
that
means
we
can
be
the
thing.
I
probably
the
only
thing,
I'm
plugging
in
the
kubernetes
cluster
to
handle
water,
primary
primary
and
the
secondary
network
and
the
for
secondary
network
with
symbol.
We
can,
for
example,
do
sre.
B
B
At
least
at
that
time
we
are,
we
are
we,
we
were
thinking
that
probably
we
can
work
without
matters
and
we
can
replace
all
the
plugins
supported
by.
B
Matas
for
the
taco
use
case,
however,
I
think
recently
we
start
to
see
we
start
to
get
some
feedback
from
users
and
also
from
wemo
internal
solutions.
Toggle
solutions.
B
We've
found
it's
like
some
customers,
just
we
just
like
use
some
existing
plugins,
for
example,
ipv
language
microline,
it's
not
just
for
because
of
features
but
more
like
the
they
are
used
to
these
plugins.
B
They
are
more
familiar
with
plugins,
so
it
seems
like
we
cannot
really
see.
We
can.
You
know,
replace
water
plugins
by
andrea,
and
definitely
we
definitely
don't
want
to
rip.
B
We
fully
don't
want
to
represent
the
water
plugins
for
sure
right
and
then
yeah,
just
as
I
already
said
earlier,
then
the
country's
strategic
question.
What
should
we
do
here?
I
think
also
software
also
said
earlier.
There
can
be
two
options.
One
way.
Let's
assume
we
need
to
support
still
five
plugins
and
we
don't
want
to
reinvent
the
world
which
is
pretty
impractical.
B
Then
one
way
is
that:
could
we
implement
something
similar
to
matas?
That
means
we
can
manage
other
plugins.
B
For
example,
when
you
in
my
house,
you
have
a
network
attachment
definition
with
other
plugins
smarters
can
simply
execute
the
plugin.
B
It
can
be
one
one
option,
as
one
toning
was
not
here-
it's
not
here
today,
but
I
think
one
turning
once
also
suggests
this
option
and
we
have
some
designing
offline
about
this
one,
the
second,
the
second
way.
I
was
thinking
that,
if
we
don't
want
to
rip
in
the
marathons,
then
probably
we
the
only
way
is
that
we
still
work
with
matas.
B
B
B
Support
types
yeah:
let's,
let's
the
contest,
I
have.
D
B
I
I
think
that
that
means
for
primary
university.
You
still
on
trial,
maybe
in
zero.
You
can
say
we
just
handle
second
interface,
let's,
let's
assume
that
permanent
interest
is
untrue
or
maybe
we
keep
permanently
separate,
but
just
for
secondary
interface,
it's
mined
by
martha's,
the
mata
super
country,
probably
there's
a
there's.
B
There
will
be
a
config
option
for
andrea
to
say
the
the
cycling
satellite
is
not
managed
by
anterior
directory,
so
it
will
ignore
the
it
will
read
formatters
to
the
core
until
plugin
for
a
second
interesting.
A
B
I
think
antonin
once
had
the
point
of
saying
a
smart
house.
Functionality
of
managing
other
plugins
are
not
very
complex
in
a
sensory
implement,
martha's
spec
in
our
relative
secondary
network
support.
B
He
believes
it's
not
very
hard
to
implement
the
hologram
management
party
together,
but
my
major
concern
for
that
one
is
it's
just
like
it's
a
little
hard
to
justify
why
we
start
new
project
repeating
the
same
functionality
of
the
matters,
and
maybe
it's
very
hard
to
maintain
the
compatibility
with
broadhouse
going
forward.
A
Yes,
I
agree
with
that
concern.
Indeed
I
was
asking
if
we
see
any
benefit
in
re-implementing
maltese
functionality,
the
plan
and
for
implementing
the
plugin
manager
within
andrea,
because,
basically,
as
you
see,
then
we
will
need
to
keep
up
with
the
multis
making
sure
that
we
are
compatible
moving
forward.
A
There
would
be
probably
some
bugs
because,
let's
say
a
specific
plugin
will
not
work
correctly
with
the
anterior
plugin
manager,
whether
it
works
correctly
with
multiple
plugin
manager.
Issues
like
this,
but
if
there
is
a
any
benefit
I
mean,
I'm
don't
see
any
benefit
at
the
moment,
but
probably
I'm
missing
something.
So
I
don't
know
if,
if
there
is,
if
there
is
something
special
I
mean
I
mean
if
there
is
any
benefit
by
re-implementing,
the
plug-in
manager
in
entria.
Do
you
know
that.
B
Yeah
yeah,
that's
a
good
point.
I
think
I
can
talk
about
what
in
my
mind,
I
think
one
reason
originally
we
do
is
related
second
network
super
entry.
Just
because
we
got
some
feedback,
smart
houses,
compass.
B
It
has
some
overhead
according
to
intel
folks.
They
believe
that
have.
C
B
By
other
customers,
I
don't
have
any
not
being
said
on
overhead
part,
but
I
I
do
think
there
will
be
additional
capacity
to
raw
materials
in
the
management
house.
We
also
got
some
feedback
from
webml
taco
solutions
like
in
some
cases.
If
people
don't
familiar
with
smallhouse,
then
it's
definitely
some
capacity.
C
B
Them
to
manage
it,
so
if
we
believe
that
is
important,
then
yeah,
probably
there
can
be
some
water
to
see.
If
we
can,
we
can
remove
rockets,
so
you
don't
need
to
install
modules.
B
Yeah,
I
think,
probably
the
only
case
it
makes
sense
for
uncharted
to
do
everything
it's
like
android
is
already
the
same
plugin
for
the
parameters.
That
means,
anyway,
you
need
to
install
entry
on
that.
You
already
use
until.
B
I
don't
know-
and
I
didn't
look
into
the
overhead
part-
I'm
not
sure
it's
like
a
cpu
or
memory
consuming
or
why
we
say
why
why
some
people
saying
it's
some
more
helpful
knowing
smart.
B
C
C
I
think
if
we
were
implemented,
if
we
implement
multiple
interface,
maybe
we
have
to
consider
the
impact
on
existing
feature
or
venture
red.
Something
like
we
need
to
consider
how
to
support
flex
for
ipm
for
the
secondary
interface.
So
I'm
not
sure
whether
it
is
only
one
feature.
Maybe
we
need
to
consider.
B
Sure,
I
think
so
far
we
are
not.
We
actually
say
we
haven't
enabled
many
features
for
second
network.
Mostly
we
just
I
mean
today
we
only
support
srwe
and
we
started.
We.
We
just
do
ipam.
B
So,
potentially,
maybe
you're
right.
If
we
want
to
add
more
values,
maybe
we
should
think
about
how
to
add
more
features
for
second
network
too
yeah
further.
I
I.
B
C
C
B
C
I
can
think
another
another
feature
like
intro
network
policy.
So
do
you
think
that
we
need
to
enforce
the
policy
in
our
policy
for
the
secondary
interface.
B
It's
not
very
clear
to
me,
yeah,
I
think
originally
inside
whether
we
had
some
discussion
with
taco
folks
right.
I
think
mostly
at
least
for
tomorrow's
case.
They
they
don't
care
about
that
point.
That
much
but
of
course,
probably
they'll
always
be
people
think
they
can
be
values
if
we
can
enforce
that
policy,
but
still
guarantee
the
high
performance
high
bandwidth
requirements
for
the
taco
cloud.
Related
func
quality
level
function
use
cases
for
the
at
least
it's
not
very
critical
for
second
network
okay
yeah.
B
But
I
am
I
mean,
that's
something
probably
we
need
to
explore
more.
It
also
can
be
because
today
you
don't
have
a
very
performant
solution,
so
people,
you
know
and
don't
have
don't
have.
B
C
B
C
B
For
andrea
to
support
for
second
interviews,
actually
I
got
lots
of
feedback
on
this
one
and
I
know
for
sure
people
believe
there
are
some
complexity
regarding
ipam,
for
example.
Today
they
may
use
wearables,
but
in
in
many
distributions.
B
Whereabouts
is
not
integrated
so
constantly
to
deployment
variables
themselves
and
many
more
about
themselves,
and
they
do
believe
it's
a
complexity,
and
if
we
can,
if
we
can
do
ipad
and
that's
assuming
the
customer
already
using
android
for
the
primary
interface
and
if
we
can
do
ipad,
I
think
definitely
that's
quite
some
value
for
customers.
C
C
C
From
in,
inter
maybe
also
from
the
vmware
tech
bu,
I
remembered
when
they
mentioned
the
complaint
a
little
bit.
If.
E
C
Use
matters,
maybe
they
use
a
chain
with
different
cis
like
catechol
and
ensure
together,
but
maybe
some
configuration,
something
like
a
rod
will
be
override,
will
be
overrated
by
by
ensure
something
like
a
pre
configured
by
a
category
but
will
be
changed
by
ensure
some
selectives.
C
B
Yeah,
I
think,
from
community
perspective.
I
think
the
maripo
network
can
be
a
unique
feature
we
can
do
in
country
how
many
people
use
it.
I'm
not
very
certain,
I
think,
for
untrained
users
if
they
use
anchor
for
private
interface.
Maybe
it
makes
some
sense,
since
they
don't
need
to
any
other
plugins
or
install
martha
in
just
one
plugin,
and
now
they
can
also
create
second
interface.
B
I
think
they
they
probably
work
on
someone
to
provide
a
solution
for
them
because
they
don't
want
to
manage
the
pranking
themselves,
but
they
don't
care
that
much.
The
solution
is
is
is
untrue
or
something
else,
but
they
do
hope
someone
can
maintain
a
solution
for
them.
A
Yeah
thanks,
so
I
can
probably
summarize
it
there
are.
There
are
probably
not
a
single
topic
that
we
discussed
today.
We
discussed
more
two
topics
which
are
enabling
entry
a
feature
on
secondary
network
interfaces,
and
then
all
the
conversation
was
started
by
engineer
regarding
on
whether
we
should
do
more,
along
with
the
directions
that
we
have
currently
been
working.
A
A
So
that's
there's,
there's
all
available
in
my
opinion
and
as
as
for
running
andrea
as
a
secondary
on
secondary
interfaces.
I
agree
with
the
concern
from
wiki
that
we
might
want
to
enable
as
much
as
many
features
as
possible,
but
some
might
not
be
enabled,
and
in
that
case
I
mean.
I
believe
that
the
only
thing
that
we
could
do
is
to
have
like
a
sort
of
support
matrix,
because
I
believe
that,
for
instance,
enabling
andreia
policies
on
sliov
is
going
to
be
challenging.
A
As
john
john
said,
it
might
be
easier
to
do
that
on
obviously
pdk
and
then
I
don't
think
that
we
want
to
enable
all
the
sort
of
secondary
all
the
sort
of
integrations
in
this
way.
So,
for
instance,
I
don't
think
that
we
want
to
have
an
entry
native
solutions
for
macvilan.
Just
to
give
you
an
example,
or
do
you
think
this
could
also
be
a
potential
direction.
B
Yeah,
I
possibly
probably
will
not
do
exactly
the
same
microline
travel
back
when
I'm
plugging,
but
I
believe
it
makes
sense
to
do
some
willa
network
with
andrea
and
probably
with
certain
research.
A
Yeah,
yes,
that's
right,
I
mean
it
makes
sense
to
do
something
that
the
users
will.
That
will
make
users
life
easy.
So,
for
instance,
we
don't
require
them
to
deploy
mortals
to
pick
up
their
the
party
plugins
they
can
do.
They
can
do
everything
they
can
do
in
an
integrative
fashion
with
andrea,
and
that
will
be
probably
the
best
approach.
A
But
obviously
we
are
not
going
to
reinvent
all
the
cni
plugins,
we'll
probably
support
you
know
the
most
important,
the
most
important
features,
as
you
said,
and
but
still
we
might
want
to
have
some
users
that
want
to
that
want
instead
to
use
maltose
masters
and
now
for
these
kind
of
users,
I'm
still
not
sure
if
there
is
a
strong
case
for
implementing
the
motors
functionality
within
andrea
and
therefore
providing
the
plugin
manager
within
entria
from
what
we
have
discussed
today,
I
I
have
a
feeling
that
we
will
be
reinventing
the
wheel,
and
these
are
probably
users
that
would
be
perfectly
okay
with
the
maltese,
and
so
we
might
just
figure
out
strategies
for
making
andrea
work
as
a
secondary
as
a
secondary
if
needed
by
the
custom
value.
A
But
the
particular
use
case
on
this
node
do
you
think,
is
this
something
that
has
ever
been
done,
even
as
a
test
for
running
and
three
as
a
secondary
interface
amount
of
just
curious.
I
don't
think
that
anyone
has
ever
tried
that
right.
B
No,
I
don't
think
we
support
yeah
because
for
for
the
untreated
the
the
the
unsure
function
of
connecting
the
interface
to
os
bridge
today,
we
are
assuming.
There
must
be
permanent
interface
and.
A
C
B
A
I
mean
we
can
work
together
with
motors,
but
only
if
we
are
the
primary
right.
Yes,
yes,
yes,
okay,
and
the
thing
is
that,
at
least
from
the
typical
use
cases
that
I'm
aware
of
you,
you
usually
have
in
masters
the
primary
interface
with
all,
let's
say
the
management
and,
let's
say,
enterprise
functionalities
like
let's
see
like
security
load,
balancing
or
whatever
and
then
from
the
secondary
interface
is
typically
cnf
applications.
A
They
only
request
highest
throughput,
the
youngest
possible
throughput
in
secondary
interfaces,
which
means
that
probably
there
is
a
probably
not
strong
appetite
for
entry
as
a
secondary.
Unless
we
offer
a
solution
for
andrea,
where
we
give,
we
give,
you
know
high
performance,
we
know
that
we
can
do
sryov.
A
B
Yeah,
I
would
agree,
I
think,
the
the
only
reason
we
are
doing
srw
just
because
we
are
at
least
we
were
thinking
if
we
can
support
some
minimum
set
of
second
interface
types
like
srw
and
vlan.
That's
what
I
was
thinking
at
least
then,
probably
in
many
cases
people
can
just
use
anterior
for
both
permanent.
Second,
they
don't
need
other
plugins.
A
So
before
we
move
on
to
any
other
topic,
I
have
a
final
question
about
obs,
dpdk
and
its
performance.
Do
we
is
there
ever
been
a
poc
for
running
andrea
on
obvious
dpdk?
A
Someone
ever
worked
on
that
because
I
remember
that
at
some
point,
like
a
couple
of
years
ago,
someone
was
working
on
it,
but
the
report
was
that
the
performance
was
nowhere
comparable
with
the
with
the
sliov
or
any
other
native
solution.
But
now
I
don't
remember
if
there's
been
any
progress
in
on
that.
B
A
B
Because
how
will
you
bypass
the
whole
stack
yeah?
You
have,
however,
directly
handled
the
packets,
but
I
kind
of
feel.
Theoretically,
we
use
sometimes
when
I
say
right
here
with
dvd
datapaths.
If
your
container
stack
is
also
your
space
stack
ebdk
or
whatever
your
space
back,
the
format
should
be
much
better
than
kernel
datapass
yeah.
But
if
your
container
stack
is
kernel
stack,
then
probably
you
cannot
get
much
benefit
from
dvd
device.
The
problem
can
be
even
worse
than
kernel
database.
A
Right
and
still
on
this
topic,
we
also
didn't
do
any
experiment
with
the
xdp
database
right.
B
For
xdp
yeah,
I
don't
think
we.
A
A
A
Okay,
so
my
summary
on
that
is
that
it
is.
It
might
be
true
that
malta
says
some
overhead,
although
I
agree
with
genji
that
I
don't
know
about
any
overhead
in
terms
of
cpu
memory,
and
I
can
only
see
a
management
overhead
and
a
configuration
complexity
over
it.
That's
the
only
operator
I
can
see
my
feedback
here
is
that
if
we
do
the
same
functionality
in
andrea
chances
are
that
we
are
going
to
introduce
the
same
kind
of
overhead
even
within
andrea.
A
And
then
the
other
aspect
is,
let's
say,
industrial
community
acceptance.
So
now
I
don't
know
a
lot
of
every
major
kubernetes
distribution.
A
A
A
Yeah
I
mean
that's,
I
I
appreciate
you
might
not
have
any
feedback
on
that,
but
that's
something
that
you
know.
We
might
need
to
consider
also
when
making
this
decision,
because
if
we
reimplement
something
which
is
already
considered
default
in
several
distributions,
then
you
know
it's
a
it's
a
sort
of
worthless
effort
in
my
opinion,
and
we
might
be
better
off
in
if
we
find
any
problem
with
maltose
which
is
reported
by
users
or
figured
out
by
ourselves.
A
I
mean
that's,
let's
just
anyway
is
there
any
other
comment,
feedback
on
these
topics.
B
Yeah,
I
think
what
do
you
summarize
makes
sense
to
me.
Probably
I
can
do
a
little
more
in
my
speaking
on
the
overhead
amateurs
and
since
we
discussed
with
antonin
valentoni
is
not
here
today.
Maybe
we
can
have
a
plan
yeah
yeah,
that's
that's!.
B
Yeah
and
follow
the
interface.
A
A
B
We
have
one
pr
merged
for
sro
interface
convention
on
the
agent
set
said
is
another
pr
under
review
for
more
than
one
month.
I
forgot
how.
C
B
B
For
for
some
time,
I
think
the
latest
state
is
that
are
wrong
from
intel
is
doing.
He
told
me
they
are
doing
some
internal
tests
with
the
pr
and
then
he
said
he
will
get
back
to
us
and
ask
for
review
again
once
the
piaat
passed
their
tests.
A
Right
it
seems
that
this
exhausted
our
discussion
on
andrea
and
the
secondary
interfaces.
We
will
have
a
quick
follow-up
in
the
next
community
meeting.
I
will
make
a
note
to
not
forget
about
it,
and
is
there
any
other?
Do
you
have
any
other
comment?
Feedback
on
this
topic
wait
a
little.
A
A
Okay,
it
seems
that
we
don't
have
any
other
topic
in
this
case.
I
think
that
we
can
conclude
this
meeting
early
and
therefore
I
would
like
to
thank
everyone
for
attending
and
will
I
wish.
I
wish
you
a
good
evening
good
morning,
good
afternoon
and
we'll
meet
again
in
a
two
weeks
time
on
december.
The
7th
so
have
a
good
one
and
talk
to
you
in
two
weeks
time.