►
From YouTube: CNCF Telecom User Group Meeting - 2020-07-06
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
I'll
go
ahead
and
kick
it
off
so
for
our
north
american
attendees.
I
very
much
appreciate
the
early
morning
call
particularly
our
folks
in
austin
and
seems
like
that.
We
have
a
number
of
folks
from
europe
and
india.
So
thank
you
for
joining.
This
is
dan
khan.
I'm
sorry
was
the
executive
director
of
the
cloud
native
computing
foundation
until
last
month.
A
I
still
am
the
vice
president
of
strategic
programs
at
cmcf
and
I'm
now
the
general
manager
of
the
linux
foundation,
public
health
initiative,
which
is
going
to
be
launching
in
a
couple
weeks.
So
I
wanted
to
give
just
a
short
update
on
me
and
the
telecom
initiative
and
and
priyanka
and
such
and
then
handed
off
to
taylor,
to
talk
about
the
event
last
week
and
the
progress
on
the
cnf
testbed.
So
the
good
news,
or
hopefully
good
news
that
people
see
it.
A
That
way
is
that
I
am
still
very
much
involved
in
the
telecom
work
for
cmcf
and
in
fact,
I'm
continuing
to
lead
the
telecom
user
group
and
the
cnf
testbed
and
cnf
conformance
initiatives
for
cncf.
A
So
priyanka-
and
I
have
spoken
about
this
repeatedly
in
some
detail-
I
think
most
of
you
will
have
seen
that
priyanka
sharma
joined
as
the
new
general
manager
for
cncf
and
she
has
a
ton
of
different
issues
on
her
plate
and
agrees
that
telcom
is
extremely
important,
but
has
asked
me
to
stay
on
and
continue
managing
that
indefinitely,
and
let
me
just
say
a
minute
more
on
that,
which
is
that
we
both
believe
that
cfcf's,
really
spectacular
kind
of
unprecedented
growth
over
the
last
few
years
can't
continue
indefinitely
and
has
likely
come
close
to
plateauing,
partly
due
to
coronavirus
and
economic
slowdowns
and
conferences
moving
virtual
and
such
but
more
just
the
fact
that
we
kind
of
have
pulled
in
the
entire
industry.
A
I
mean
we
have
every
big
cloud,
all
the
enterprise,
software
companies
etc,
and
so
there
are
some
limits
to
growth.
I
think
folks
are
aware
that
over
the
last
the
last
four
years
we've
grown
from
28
members
to
560..
I
believe
that
was
when
I
left
a
month
ago.
A
I've
stepped
down
and
we're
now
at
571,
so
definitely
not
done
growing,
but
I
think
the
pace
has
slowed,
but
she-
and
I
also
both
agree-
that
telcom
remains
one
of
the
biggest
growth
opportunities
for
cmcf,
and
so
we
already
have
a
number
of
those
organizations
or
a
lot
of
cases.
Your
organizations
as
members,
but
now
trying
to
do
the
additional
work
to
demonstrate
how
kubernetes
can
be
used
as
the
substrate
of
a
modern
telecommunications
platforms.
It
has
really
been
the
purpose
of
this
group
and
and
all
of
that
work
continues.
A
So
folks
are
welcome
to
reach
out
to
her
and-
and
I
know
that
several
of
our
our
biggest
telecom
members
have.
But
I
also
encourage
you
to
to
reach
out
to
me,
and
so,
if
there's
things
that
you'd
like
to
see
differently
about
this
call
or
concerns
that
you
have
or
ideas
or
such,
I
really
do
encourage
you
to
ping
me.
A
I
remain
very
active
on
cncf
slack
and
then
I
am
available
to
do
a
call
with
anyone,
and
you
can
just
book
onto
my
calendar
at
at
this
address,
which
is
the
dancon.comc.
A
So
the
the
two
other
kind
of
announcements
that
I
would
make
is
one
is
that,
unfortunately,
we
have
decided
that
kubecon
north
america
is
also
going
to
be
a
virtual
event,
and
I
don't
think
that's
a
huge
surprise,
given
the
the
path
of
the
unfortunate
path
of
the
coronavirus
in
the
united
states,
where
it
still
is
very
much
not
under
control,
and
so
we
are
hard
at
work
on
those
plans
and
and
you'll
see
a
lot
of
them
coming
together
over
the
next
couple
months.
A
Of
course,
right
now
we're
focused
on
the
kubecon
eu
happening
much
sooner
and
then
the
other
part
that
I
just
want
to
mention
is
that
we
do
have
this
telecom
white
paper.
That
is
basically
done
we're
just
trying
to
line
up
the
final.
A
A
couple
authors
for-
and
I
do
want
to
apologize-
that
delay
is
definitely
on
me,
where
I
also
am
trying
to
launch
this
elf
public
health
initiative
and
get
a
bunch
of
our
founding
members
together,
and
so,
but
my
expectation
is
that
both
of
those
things
will
finally
happen
this
month,
but
they
they
kind
of
got
piled
up
behind
them.
A
So
I
think
that's
my
introduction:
are
there
any
questions
anyone
has
about
that
content
or
my
participation
in
it
or
other
information
folks
would
like,
or
should
I
go
ahead
and
and
hand
it
over
to
taylor.
A
Going
once
okay
taylor,
could
you
tell
us
about?
Maybe
the
the
cnct
meeting
this
month
would
be
a
good
place
to
start,
and
then
you
could
give
us
some
other
con
context
as
well.
B
Sure,
thanks
stan
trying
to
see
if
who
else
is
on
the
call
is
bill
mulligan.
B
He
was
talking
a
little
bit
with
me
about
the
cnt,
specifically
the
lf
forum,
okay,.
B
Well,
the
elephant
forum
had
a
lot
of
the
cnt
related
items
for
the
folks
that
weren't
on
that.
I'm
sure
that
a
lot
of
people
on
here
were
on
that
and
including
tracks
from
about
the
ovp
initiative
of
ebb
2,
specifically
for
the
open,
op,
fv
verification
program
for
the
cnt
kubernetes
reference,
and
also
tracks
from
opnfv
and
onap,
and
from
the
I
guess,
the
cncf
telecom
side
and
specifically
around
the
cnf
conformance
as
well
as
a
cnf
testbed.
B
We've
been
attending
a
lot
of
those
and
trying
to
see
where
we
can
collaborate.
So
there
was
a
lot
of
conversations
around
tooling,
sharing
different
ideas
and
stuff
around
that
on
the
reference
implementation,
and
it
calls
there's
a
a
lot
of
conversations
about
the
environments
how
to
bring
up
both
from
provisioning
hardware.
Networking
all
the
way
through.
B
Actually,
bootstrapping
kubernetes
and,
I
think,
there's
a
lot
of
the
terminology.
That's
maybe
not
consistent
enough
to
to
make
sure
that
everyone's
on
the
same
page
and
that
rolled
over
from
the
lfn
forum
talks
and
our
conversations
and
to
some
of
the
sandy
t
weekly
meetings
this
week
going
into
the
both
the
implementation,
as
well
as
the
reference
certification
meetings,
the
rc2,
and
by
that
I'm
I'm
referring.
B
If
you
look
at
some
of
the
tables
that
cnt
has
this
on
the
wiki
page,
one
of
them
is
about
kubernetes
installers
and
there's
was
some,
maybe
some
confusion.
I
think
it's
again
because
of
the
terminology
but
confusion
about
what
is
handling
kubernetes,
very
specific
parts
of
maybe
having
the
software
initially
start.
B
B
B
That's
going
to
be
updated,
maybe
over
the
next
couple
of
weeks,
is
trying
to
address
that,
so
that,
when
we're
talking
about
tool
chains,
it'll
be
clear
where
we're
what's
what
layer
that
we're
talking
about
and
and
then
the
other
part
was,
I
think
that
ties
in
with
the
cnf
conformance
specifically,
although
it's
similar
in
the
cnf,
testbed
and
and
some
other
efforts
and
other
projects
initiatives,
is
how
to
make
things
compatible
so
that
people
have
choice
to
come
in
and
plug
different
things
in
so
opnfv
has
a
a
ci
cd
tool
chain
that
runs
stuff,
like
kubernetes
conformance
on
their
ci
cd
chain,
specifically
on
the
kubernetes
side
that
they're
doing
testing.
B
So
how
can
we
plug
in
other
things?
If,
if
someone
has
a
cocd
chain,
how
could
you
plug
in
something
else,
so
the
cnf
conformance
right
now
has
a
you
could
call
it
a
first
version
or
it's
it's
a
little
bit
past
proof
of
concept
at
this
point,
but
the
results
that
come
out
are
generated.
Yaml
configuration
for
cnf,
conformance
and
we've
tried
to
think
about
ford
compatibility
to
plug
into
other
things.
B
I
think
probably,
what
we're
going
to
be
looking
at
over
the
next
several
weeks
is
how
to
directly
more
directly
support
running
the
cnf
conformance
as
a
gate
for
pipelines,
whether
that's
something
like
if,
if
it's
part
of
the
ovp
and
running
directly
in
the
cicd
pipeline
opnfv,
if
that,
if
it's
wanting
to
be
able
to
use
it
similar
to
other
tests
that
are
running,
it
could
be
one
of
the
requirements
or
even
more
directly
for
operators
or
a
cnf
developer.
B
A
vendor
could
be
using
as
part
of
their
ci
cd
pipeline
for
testing
software.
An
operator
that's
acting
as
a
integrator
could
use
the
cnf
conformance
and
for
those
who
haven't
heard
it
to
maybe
bring
this
back.
What
is
in
scope
for
cnf,
conformance
with
the
cnf
conformance
is
doing.
Is
it's
trying
to
validate
if
an
implementation,
whether
that's
a
workload,
so
the
applications
that
are
running
or
the
actual
platform
kubernetes
with
all
extensions
and
whatever
else
may
be
running?
B
B
B
So
you
can
think
of
it
as
one
of
the
many
checks
that
someone
may
desire
whenever
they're
doing
testing
so
from
an
operator's
perspective,
which
one
of
the
comments
from
elephant
in
in
elephant
forum
many
times
and
you've
potentially
heard
this
other
other
places.
Operators
act
as
integrators,
often
between
all
the
different
software,
that's
coming
from
the
vendors
and
other
places
that
they
are
taking
stuff
in.
B
B
So
again,
I
think
that
it's
it's
been
there
kind
of
implicitly
that
we
want
it
to
support
integration,
and
what
we'll
be
looking
at
is
how
to
more
directly
support
that
so
that
that
was
one
of
the
big
things
coming
out
of
there.
B
Let's
see,
there's
some
folks
that
were
on
the
elephant
forum
and
hey
michael
pedersen.
I
see
that
you're
on
you've
been
on
a
lot
of
these
ri2
rc2
calls.
Does
anyone
have
any
comments
about
the
cnt
and
lfn?
I
have
some
more
cnf
conformance
specific
things,
but
before
moving
on.
C
Maybe
I
can
jump
in
hey
this
is
this
is
george
we
have
been
creating
in
the
an
ra2
implementation
focus
project
in
openv
to
formalize
the
development
process,
a
little
bit
more
so
out
of
the
the
cntt
rit
work
stream,
which
of
course,
initially
focuses
on
identifying
requirements
and
defining
what
the
implementation
looks
like.
Based
on
the
reference
architecture,
too,
the
openmv
project
is
focusing
on
providing
the
the
corresponding
reference
implementation,
just
as
described
by
by
taylor.
C
So
if
anybody's
interested
in
in
contributing
to
that,
given
your
knowledge
interest
in
getting
that
work
up
and
running,
to
combine
cncf
related
efforts
like
this
with
the
openav
project,
feel
free
to
reach
out
to
to
the
team.
Basically,
I
can
post
a
link
to
the
project
proposal
here,
we'll
find
it
in
a
second.
The
project
has
recently
been
approved
by
the
openwv
tsc.
C
A
C
Go
okay
there
we
go
feel
free
to
reach
out
if
you're
interested
in
supporting
that
and
yeah.
That's
basically,
all
I
wanted
to
say.
A
I'm
curious,
if
you
can
say
what
installer
you're
planning
to
use
for
this
reference
implementation.
C
Yeah,
it
is
currently
this
is
still
very
early
work
and
since
the
ri
2
ra
2
is
still
very
much
work
in
progress.
It's
also
an
investigation
kind
of
process
on
the
ri
side.
C
Currently
we're
looking
at
an
installer
around
spray,
so
cube
spray
would
be
the
the
the
basic
framework
again
then
using
qradium
under
the
hood.
I
think
those
are
the
latter.
One
is
the
obvious
choice.
Cube
spray.
Is
the
the
ansible
play
based
play
books
collection
that
then
gets
extended
by
another
set
of
playbooks
maintained
by
intel,
so
it's
an
intel
bmra
bare
metal
reference
architecture,
it's
basically
a
showcase
deployer
for
kubernetes,
with
really
a
lot
of
different
pre-integrated
extensions,
ranging
from
from
mulches
to
a
device
manager.
C
All
of
these
well
very
often
turquoise
specific
extensions
of
core
kubernetes,
but
I
would
like
to
point
out
that
it's
not
in
any
way,
I
would
say,
yeah
not
decided,
is
probably
also
not
the
right
term.
We
are
happy
to
have
discussions
around
what
installer
actually
should
be
should
be
used.
So
taylor
was
referring
to
the
wiki
page,
where
we're
looking
at
the
feature
set
basically
of
various
different
installers
and,
to
be
honest,
yes,
there's
a
mismatch
of
levels
in
there,
because
there's
cube
adm
and
cube
spray
which
are
not
on
the
same
level.
C
But
please
forgive
there's
this.
We
also
looking.
We
will
potentially
be
looking
at
airship
because
that's
a
very
deco
focused
thing
as
well
and
that's
being
used
in
cntt
on
the
openstack
side
of
things,
and
since
it's
at
the
core,
it
is
kubernetes.
Obviously
that
will
be
looked
at
also
yeah.
A
I
would
definitely
recommend
cubespray,
I
think
it
as
being
part
of
the
core.
Kubernetes
project
has
done
a
very
good
job
of
keeping
up
to
date
on
that
and
its
use
of
cube,
adm
and
such
so.
I
think
that's
a
great
choice.
C
Yeah,
so
that
that's
for
sure
part
of
the
the
set
of
installers
we're
going
to
look
at.
Obviously
this
the
the
goal
is
to
use
cncf
components
and
not
much
else.
Obviously
there
might
be
a
little
bit
of
extra
tooling
around
that,
like
the
bare
metal
provisioning.
It's
one
example,
but.
B
Thanks,
michael
for
posting
that
link
the
the
link
for
the
current,
what's
labeled
installer
comparison,
michael
peterson
posted
that
and
cube
sprays
list
on
that,
I
think
what
may
happen
is
we
may
end
up
with
another
table
that
has
makes
a
little
bit
more
clear
on
what
is
sub
components
or
the
within
the
larger
ones
like
cube.
Adm
is,
as
used
by
cube.
B
Spray
kind
is
also
on
the
list
and
kind
uses
cubadium
underneath
I'm
not
sure
if,
if
air
spray
is
using
something
different
at
this
point
underneath,
but
a
lot
of
them
are
doing
that,
but
the
it
has
a
list
at
least
of
a
lot
of
the
different
items
and
the
features,
I
think
is
probably
what
we'll
end
up
making
a
little
bit
more
clear.
So
we
have
something,
that's
very
specific
and
then
higher
level
management.
B
Probably,
what
would
be
good
is
some
diagrams
that
talk
about
how
you
layer
things
up
from
hardware
provisioning
network
all
the
way
up
and
to
the
point
where
you
have
okay.
Now
we
can
connect
some
of
the
kubernetes
components
and,
and
then
how
do
you
manage
those
and,
of
course
something
like
errors?
Airship
does
a
whole
lot
more
across
all
the
layers,
and
that's
that's
fine.
We
can
say
some
things
can
do
multiple
layers
and
some
focus
on
one.
B
B
B
One,
I
guess
another
thing
that
came
out
of
the
the
different
talks
was
and
and
specific
at
least
to
cnf
testbed.
B
There
seems
to
be
still
a
desire
to
use
the
tool
chain
and
the
environment
set
up
for
that
came
out
of
cnf
testbed
in
other
labs
and
other
places,
and
that's
been
ongoing
since
a
start.
But
it's
increased
a
lot
for
the
last
six
months
and
out
of
the
lfn
forum.
B
One
of
the
ideas
that's
come
out
is
potentially
taking
one
of
the
available
apps
and
trying
to
target
and
add
support
for
that,
and
I
I
think
efforts
to
do
that
can
help
the
lab
to
be
have
the
capabilities
to
support
other
tooling
and
probably
would
be
something
that
could
help
any
other
tools
that
are
also
wanting
to
support
multiple
labs.
So
one
of
the
specific
ones
that
we're
looking
at
right
now
from
the
cnf
testbed
is
the
opnfv
labs
lab
as
a
service.
B
And
we
have
some
conversations
going
about
that
and
if,
if
we
get,
if
that
moves
forward-
and
we
have
if
it
looks
like
a
good
match-
and
we
end
up
with
support
for
targeting
that
lab
as
well
as
packet,
then
I
expect
the
updates
for
the
cm
of
testbed
to
make
it
easier
to
target
other
custom
labs
or
just
other
services.
B
Most
of
the
underlying
tool
chain
is
already
kind
of
set
for
targeting
cloud
provider
type
things
and
it
uses
cube
spray
which
can
target
any
set
of
machines
for
the
setup
on
provisioning
has
a
terraform
for
actually
requesting
machines
and
those
parts
are.
We
could
split
those
off
and
use
something
else.
So
I
think
we
have
a
lot
going
there
and
george.
Maybe
something
interesting
to
talk
about
how
to
to
take
different
work,
that
opinfe
is
doing
and
be
able
to
target
other
labs.
B
And
if
we
have
the
capability
to
target
multiple
places,
then
it's
most
likely
the
improvements
on
the
tool
chains
and
those
are
going
to
get
better
and
share
those
ideas
and
the
target
labs
like
exposing
stuff.
Like
the
networking.
How
do
we?
How
do
we
configure
those
and
have
it
not
tightly
integrated
into
maybe
a
higher
level?
B
So
I'd
be
interested
in
talking
some
about
that
with
you,
and
I
do
know
that
and
and
michael
you
may
have
more
information
on
this,
but
as
since
you've
been
so
directly
involved
with
cnf
testbed
development,
there
are
people
that
have
been
using
the
cnf
testbed
in
their
own
labs
operators
specifically
and
some
vendors
doing
testing,
but
we
want
to
make
x
make
that
more
available
so
that
anyone
that's
wanting
to
have
what
the
cnf
testbed
does
can
use
it
in
their
own
lab
for
testing
playing
with
different
cloud
native
technology
options,
whether
that's
platform
or
or
workloads,
is
the
idea
with
that,
so
that
I
think
it's
a
good
complement
to
other
tooling,
that
are
being
maybe
very
opinionated
and
trying
to
pick
specific
tools.
B
D
D
D
So,
even
if
we
deploy
a
let's
say
an
into
extra
large,
we
can
say
for
certain
exactly
what
cpu
sku
we're
getting,
and
I
guess
it
has
a
little
bit
of
impact
with
the
cpu
enumeration
then,
and
pci
devices
and
whatnot
there's
still
work
to
do
there,
but
but
at
least
we're
gradually
gradually
modifying
what
we
already
have
to
to
try
and
generalize
it
a
bit
more
and
similarly,
I
think
some
of
the
playbooks
we
have
now
can
probably
benefit
from
being
split
out
a
little
bit.
D
D
B
B
But
right
now
that's
what
a
lot
of
those
parts
this
would
be
before
either
before
cube
spray
comes
in
so
setting
up
some
host
specific
things.
If
we
want
to
optimize
those
and
what
you
said
in
the
configuration
and
and
then
potentially,
if
there's
anything
that
you
want
to
tweak
after
the
fact,
but
that's
what
those
those
parts
are
for
getting
the
machines
ready
on
host
and
network
for
the
underlying
machines,
nodes
and
network
that
that
you're
going
to
run
kubernetes.
C
C
Yeah,
exactly
maybe,
if
I
can
add
one
more
sentence
here
that
is
because,
like
the
current
rit
work
has
specifically
looked
at
that,
and
we
sorry
for
forgetting
to
mention
that
we
have
also
looked
at
the
scene
of
this
but
before
and
then
right
now,
because
of
the
reason
that
both
the
scene
of
test
bed,
as
well
as
the
the
intel
bmra,
is
making
use
of
cube
spray
as
a
deployer.
C
That
requires
some
some
pre-provisioning
in
and
the
openvc
ocd
pipeline
has
typically
been
like
an
end-to-end
deployment
thing
where
you
just
need
to
have
something
to
do
the
the
deployment
of
the
host
to
assets
and
then
put
either
one
of
those
on
top
of
that.
C
So
getting
that
end-to-end
workflow
done
would
be
like
one
of
the
the
obvious
next
step
on
on
that
side
of
the
project
and
exactly
what
you
just
mentioned
is
then
part
of
input
to
various
upstream
places,
wherever
it
fits
best
like
making
sure
that
the
I
don't
know
you
have
the
right
host.
C
C
Yeah,
unfortunately,
I
need
to
drop
now,
but
trailer,
happy
and
michael.
C
Follow
up
with
you
on
these
discussions
and
yeah
so
I'll
be
around.
B
So,
on
the
cnf
conformance
side,
we've
just
finished
a
round
first
round
of
beta
testing
on
the
cnf
conformance
and
gathering
feedback
and
there's
we
had
a
group
that
was
consisting
operators
and
cnf
developers
that
have
working
on
different
parts
engaged
in
a
lot
of
these
different
communities
and
familiarity.
And
and
of
course,
everyone
is
open
to
go
and
try
out
the
software
use
it
cnf
conformance
software.
B
This
was
more
of
targeted,
trying
to
get
specific
feedback
on
how
the
whole
process
of
getting
set
up
and
and
running
it
using
it
to
test
a
workload
and
how
the
interactions
with
the
actual
tooling
was
and
try
to
get
feedback
on
that,
so
that
we
could
target
installation
setup,
make
it
smoother
for
folks
to
get
going
and
to
help
with
guidance
on
the
actual
results
and
other
items
like
that.
Overall,
it
was.
B
It
was
very
positive
and
we're
planning
on
breaking
down
all
of
the
the
feedback
and
looking
at
it
from
a
perspective
of
guiding
on
updates
and
features
and
were
some
of
them,
the
maybe
early
pre-beta
setup
and
testing.
B
Consistency
for
getting
things
set
up
the
way
that
the
actual
cli
for
the
cnf
conformance
tool
once
it's
actually
built
how
it
works
and
taking
feedback
from
that
and
started
making
updates
along
with
going
through,
using
it
repeatedly
and
team-wise,
and
people
that
are
contributing
going
through
and
thinking
from
a
cnf
developer.
That's
wanting
to
test
their
software
or
use
the
tool
for
helping
to
improve
the
cloud
nativeness.
B
So
that
was
the
goal
with
a
lot
of
the
testing
and
we've
been
trying
to
take
that
perspective
and
come
up
with
a
lot
of
little
updates
and
stuff
that
have
many
of
them
have
coincided
with
the
beta
feedback
that
we
got
and
we're
in
progress
to
make
those
updates
and
we'll
continue
with
whatever
feedback
we
have
and
we're.
Also,
looking
at
the
platform
specific
testing
and
how
that
could
run
to
test
the
how
to
actually
what
are
the
implementations
in
a
kubernetes
based
platform.
B
If
you
look
at
extensions
and
how
it
interacts
with
the
host
and
other
parts,
how
do
those?
How
would
something
that
a
a
telecom
platform
would
look
like
so
kubernetes
all
the
extensions
anything
else,
operators
that
may
be
running
and
how
do
we
test
that
those
are
implemented
and
actually
using
cloud
native
principles?
B
So
we've
been
building
out
a
first
round
of
here's,
some
things
to
test
and
we'll
be
starting
to
implement
some
of
those
tests
to
run
soon,
along
with
all
the
workload
tests
that
are
running
right
now
and
and
we're
going
to
continue
on
that
side.
B
But
we
would
be
happy
to
have
more
testers
if
you
want
to
specific,
be
whether
you
want
to
do
it
on
your
own
and
you
can
feel
free
to
go
through
the
existing
documentation,
whether
it's
source-based,
we
have
source-based
installation
or
you
can
use
the
binary
and
more
simplified
approach
to
getting
things
up.
B
We'd
be
happy
to
get
your
feedback
that
way
and
if
you'd
like
to
be
part
of
another,
more
targeted
beta
test
round,
where
there's
a
specific
set
of
instructions
and
more
focused,
then
happy
to
add
you
to
the
list
for
doing
that.
Just
let
us
know-
and
we
are
going
to
do
some
specific
testing
with
several
groups,
and
we
are,
of
course
working
with
cnt
and
trying
to
look
at
how
to
integrate
with
the
conform.
B
The
certification
site
and
opnfv,
like
george,
was
talking
about
for
being
able
to
run
cnf
conformance
as
part
of
different
testing
that
they
do.
So.
We
want
to
support
those
projects
from
a
side
of
maybe
closer
to
cnf
developer
site,
we're
going
to
work
with
projects
like
network
service
mesh
to
be
able
to
test
various
examples.
Hey
nikolai!
B
B
A
A
Okay,
let's
and
things
there
thanks
everybody
for
the
call.
Today
we
will
be
available
on
slack
and
email,
and
our
next
call
is
in
a
month
goodbye.