►
From YouTube: CNCF Telecom User Group Meeting - 2020-04-20
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).
B
I
will
sorry
about
that,
but
I
just
wanted
to
say
that
yeah
I
did
want
to
kick
off
this
meeting.
This
is
our
third
Monday
meeting,
which
is
more
friendly
for
Pacific
and
European
Time,
so
really
appreciate
Taylor
getting
up
at
6:00
a.m.
and
it's
7:00
for
me,
and
the
main
thing
on
the
white
paper
front
is
that
we
have
locked
down
the
prologue
paper
and
are
now
just
trying
to
finalize
the
operators
that
are
going
to
be
the
official
co-authors
of
it.
B
C
Is
the
plan
we
did
this
led
to
original
white
papers
which
were
created?
There
was
one
which
was
created
even
before
the
tag
and
that's
like
parts
of
it
currently
in
the
repo
in
the
vu
corpse
github
account,
and
there
is
the
other
white
paper
which
was
agreed
by
the
tag
and
that's
sitting
in
some
Google
Docs.
C
B
B
B
B
C
C
B
A
C
A
A
A
Parallel
I
guess,
testing
efforts
that
are
happening
and
the
same
confirm
ensuite
one
is
focused
on
the
work
load,
testing
and
CNF,
specifically
having
it
ready
for
testing
the
scene
of
Micra
services
like
vdn
or
I
before
it
or
the
different
pieces,
and
the
cloud
native
aspects
on
that
and
a
another
portion
is
focused
on
testing
platform,
the
platform
itself,
the
categories
I
posted
a
link
to
the
main
page
on
the
read
made.
Those
categories
are
primarily
the
same
and
they
were
working
on
a
test
category
page,
which
is
give
the
link
here
so
long.
D
A
Sea
NTT
overview
for
the
reference
architecture
to
on
the
different
expected
areas
for
a
platform
to
cover
resilience.
Tea
and
some
other
ones
would
be
potentially
some
that
we
have
on
here.
As
part
of
this
effort
for
the
platform
side,
we're
mapping
the
coverage
from
kubernetes
conformists.
So,
if
you're
running
a
certified
kubernetes
cluster
than
what
tests
will
already
cover
many.
B
A
The
specifically
the
cloud
native
aspects
of
CNT
Pease
needs
for
a
platform
or
operator
and
vendor
what
they're
looking
at
and
we're
also
looking
at
mapping
other
kubernetes
1010
tests.
That
would
go
beyond
the
conformance
test,
which
there's
extensive
integration
test
coverage
with
a
lot
of
that
mapping
directly
to
what
would
be
seen
and
I
in
the
Santa
T
requirements.
A
Part
of
that
can
be
saying
our
effort
with
Santa
T
on
mapping
all
of
all
of
these.
So
there's.
This
is
something
on
if
you're
part
of
the
reference
architecture
and
reference
implementation
meetings
on
sandy
T
and
we've
been
doing
collaboration
directly
on
those
and
mapping
out
the
actual
requirements
and
where
they
tie,
which
you'll
see
here,
is
sandy
T
priorities
on
how
the
requirements
are
seen
from
an
overall
upgrader
perspective
and
then,
if
they're,
going
to
match
with.
Is
this
in
scope
for
cloud
native?
A
If
anyone
wants
to
come
in
and
test,
this
is
going
to
be
focused
on
the
the
workload
because
that's
further
along
and
that
was
started
first
I'm,
going
to
paste
that
into
the
into
the
zoomed
chat
as
well,
and
this
walks
through.
If
you
would
like
to
try
out
and
use
the
CNF
conformance
suite,
then
this
is
a
quick
walk
through
of
what
you're
needing
including
the
prereqs
I'm,
so
expected
to
have
a
access
to
some
kubernetes
cluster
there's
further
documentation.
A
So
that's
the
main
part
on
the
workload.
There
is
a
example
of
a
scoring
and
scoring
for
this,
which
would
be
anywhere
from
you,
aren't
using
good
practices
to
you're,
doing
better
or
moving
towards
what
we
could
think
of,
maybe
as
a
gold
CNF.
But
right
now,
it's
more
focused
on
relating
it
to
it
seems
to
be
very
important
from
cloud
native.
A
A
lot
of
this
would
match
up
with
the
CM
TT
requirements
for
stuff,
like
must,
and
should,
although
some
of
them
may
be
a
must
from
a
cloud
native
and
a
recommended
from
Sandy
T
says
that's
in
the
works
from
from
the
conformance
side.
I
think
that
gives
a
pretty
good
overview
that
Dan
and
unless
you
want
to
point
out
anything
specific
and
I'll
leave
it
up
and
for
some
questions.
B
A
Sure
I
don't
know
if
Gergely
or
anyone
else
here
that
can
speak
a
little
bit
specific
on
all
the
topics,
but
they,
as
far
as
the
work
from
the
conformant
Sutton
and
Sandy
tea,
trying
to
help
with
the
RI.
So
the
implementation
side
for
a
lab
and
that
overlaps
with
the
CNF
testbed
initiative
as
well,
which
is
being
used
as
one
of
the
ways
to
bring
up
a
example,
cluster
and
environment
for
the
conformance
testing
and
as
well,
as
example,
CNS,
which
are
going
into
being
tested
by
the
conformance
we
so
the
implementation.
A
And
then
the
feedback
and
updates
to
the
reference
architecture.
To
help
broaden
I.
Guess
the
availability
to
use
different
options
and
for
the
implementation
so
directly.
Helping
on
those
and
there's
several
talks
about
that
from
the
implementation
architecture.
And
then
the
new
reference
certification
work
stream
on
Santa
T,
so
directly
involved
in
those
on
seeing
where
the
cloud
native
aspects
can
impact
that
have
a
help.
C
C
So
I
just
was
scheduled
why's
the
clematis
related
reference.
A
textured
session
is
on
day
2,
which
is
on
Wednesday,
starting
from
quarter
past
11
UTC.
So
that's
that's
the
reference
I
lecture
to
deep
dive
and
that
lasts
until
one
o'clock
UTC
and
then
from
half
past
one.
We
will
have
the
reference
implementation
deep
dive.
C
C
A
E
D
Think
so
I
told
you
say
the
the
debate
I
find
but
I
think
most
useful
to
the
communities
as
a
whole
is
the
Taylor
shared.
So
the
most
kind
of
obvious
link
between
the
two
activities
is
with
the
RC
to
work
stream.
That
bill
was
just
set
up
within
C,
NT,
T
and
CNF
conform,
but
I
think
the
the
requirements
analysis
that
that
is
pulling
out
the
requirements,
whether
the
principles
or
requirements
or
specifications
from
the
reference
model
and
are
a
to
will,
will
essentially
give
a
really
really
good
structure
to
what
it
is.
D
C
A
A
E
B
It's
on
github
and
we're
going
to
be
publishing
it
as
a
PDF
in
the
in
the
coming
weeks
and
it'll
be
on
the
ciencia
website.
But
we
basically
locked
down
the
draft
in
the
prologue.
But
the
answer
is
that
these
things
started
to
Google,
Doc
and
then
move
to
github
and
then
get
published
as
a
PDF
I
mean.