►
From YouTube: CNCF Telecom User Group 2020-01-20
Description
CNCF Telecom User Group 2020-01-20
A
B
B
A
A
A
C
Like
to
just
bring
a
question,
and
now
I'm
not
sure
how,
for
you
guys
aware
of
sea
entity,
activity
is
something
we
start
to
look
at
is,
if
you
think
about
open
a
V.
For
example,
we
do
have
groups,
you
can
open
a
V
and
tolling
to
create
an
instant
of
the
infrastructure
difference
implementation
as
we
call
them
in
sea
entity
who
we
trying
to
figure
out
what
would
be
the
right
way
of
creating
a
container
based
implementation
and
have
that
as
a
reference
orientation
that
we
could
make
it
compliant
to
the
CNTV
specification.
A
A
Think
there's
probably
several
people
on
the
call
right
now
I'm
looking
at
like
from.
Let's
see,
hey,
Bill
and
other
folks
really
could
talk
about
tooling
from
my
understanding,
there's
going
to
be
a
lot
of
different
pieces,
so
probably
thinking
multiple
parts
as
far
as
what
could
be,
what
could
be
used,
different
alternatives
for
bringing
up
nine
pieces
of
you're
gonna
have
the
applications
inside
and
then
maybe
the
platform
side
would
be
the
simplest.
A
But
even
with
that,
you
could
start
looking
at
a
lot
of
different
components
and
that
would
be
put
together
and
then
there's
probably
a
lot
of
options.
But
maybe
some
folks
have
some
specific
things,
and-
and
this
probably
is
something
to
I-
would
recommend
posting
to
the
telco
music
group
mailing
list
so
that
folks,
that
aren't
on
the
call,
maybe
could
give
some
responses
and
feedback
on
that.
Okay,.
D
I
guess
if
I
can
just
jump
in
this
is
Bill
Morgan
from
I
know
tiller
you
guys
in
CNF
testfit
are
currently
using
cue
spray
right
now.
Were
you
considering
using
cube
one
so
I
know
those
are
both
two
tools:
they're
like
available
open
source
right
now?
Obviously,
there's
all
of
other
solutions
on
the
market
too,
but
I
think
I'd
be
good
to
get
other
people's
opinions
too.
A
Breakdown,
that's
high
enough
level
for
people
to
get
into
and
talk
about
some
of
the
different
parts.
So
you
can
say
cube
spray
is
going
to
bring
up
a
cluster
and
a
kubernetes
cluster
with
a
few
specific
parts
on
that,
it's
not
going
to
include,
let's
say
all
the
different
things
that
are
going
to
be
needed
in
a
maybe
a
production
platform
versus
just
saying
the
cluster
itself.
A
What
are
all
the
extensions
to
kubernetes
that
you're
gonna
install
and
then
there's
a
bunch
of
other
parts
if
I'm
thinking
of
what
is
the
CNT
T
looking
at
it's
the
whole
lifecycle,
so
management
and
stuff
of
the
cluster
would
be
one
part,
there's
also
management
of
applications
and
a
bunch
of
other
things
without
looking
at.
How
would
you
design
that
I'm,
stepping
back
and
thinking,
Robby
or
saying
how
would
we
even
have
a
something
to
start
playing
with
and
and
trying
out
and
I
think
is
what
you're
asking
versus?
C
A
C
Contribute
to
or
adding
some
requirements
and
trying
to
maturity
or
evolve
it
to
become
the
reference
implementation
for
C
entity
based
implementation
and
that's
basically
to
cover
the
operators
use
cases
that
they
are
interested
in
so
a
tool
door
projects
with
a
github
repository
to
allow
us
to
do.
That
would
be
ideal.
B
A
To
be
a
lot
of
alternatives
like
the
cube
one,
can
you
can
deploy
clusters
and
manage
the
lifecycle
of
say
a
a
worker,
node
and
other
parts
and
bringing
them
in
and
scaling
them
outs?
And
that
may
be
something
that's
desired
and
someone
else
may
want
to
try
something
else
for
the
cluster,
provisioning
or
or
whatever
there's
a
lot
there.
A
And
then
you
can
say
here's
another
component
that
we
need
and
there's
a
set
of
tools
that
could
be
used
for
that
and
if
you
start
there,
then
we
could
probably
get
a
discussion
happening
on
the
mailing
list
and
probably
slack
as
well
would
be
a
good
place
to
post
and
link
to
a
message
about
that.
As
far
as
a
github,
repo
and
I
think,
if
we
can
get
the
conversation
going,
it's
probably
be
interest
in
various
projects.
Until
you
get
something
going,
it
may
even
be
like
a
Santi
tee.
A
A
From
the
scene
of
tests
at
the
end
point
I
could
see
doing
something
more
as
an
example.
Here's
some
pieces
that
could
work
too.
If,
if
you're
saying
someone
wanted
to
implement
a
platform
in
a
specific
way,
then
here's
some
pieces
that
you
could
put
together
and
do
something
that
follows
that
specification.
A
I
can
see
that
as
as
a
way
to
do
it,
that
would
be
kind
of
it's
almost
towards
a
reference
implementation,
but
kind
of
prior
to
that
and
saying
here's
here's
an
example
of
some
of
the
tooling
and
and
how
we
would
recommend
building
it
from
starting
from
using
cloud
native
principles.
I
wouldn't
really
want
to
think
this
is
a
reference
platform,
though
so
I
think
it's
a
good
complement
to
what
you're
talking
about,
though,
and
I
definitely
been
shouldn't
chatting
with
you
some
more
about
that.
C
Yes
with
insanity,
it
is
a
score
difference,
implementation
which
I
don't
think
this
bid
belongs
in
that,
but
also
there's
the
reference
certification,
where
the
testing
is
need
to
be
happening.
So
I
think
Moe
discussion
needed
to
see
how
that
will
align
to
what
we
intend
to
do
in
C
entity.
But
yeah
I
agree
to
your
point,
I
think.
Certainly
a
lot
of
questions
need
to
be
taken
to
understand
whether
how
they
fit
within
what
we
try
to
do
in
C
entity.
C
A
C
So
Santa
T
stands
for
common
and
the
VI
telco
task
force
and
the
intention
behind
that
is
to
bribe
provide
the
consistent
implementation
and
architecture
of
the
infrastructure
that
runs
both
vnf
sensory
nerves.
We
do
have
two
tracks
within
c
entity,
one
targeting
the
vnf
and
using
the
open,
Evo
key
system
to
create
the
reference
orientation.
Also,
we
have
a
second
track,
which
is
focusing
on
two
in
the
cloud
native
and
containerized
platforms
and
Tom
Kivlin
is
a
Nicole
he's
the
lead
of
the
peripherals
architecture
2,
which
is
the
kubernetes
perceivers
architecture.
A
I
think,
unless
someone
has
anything
else,
the
other
thing
that
we
had
is
the
white
paper
related
to
the
Telkom
user
group
white
paper,
which
specifically
I
say
the
white
paper
there's
actually
quite
a
few
that
have
been
being
worked
on.
There's
a
white
paper.
That's
the
cloud
native
thinking
for
telecommunications
and
I'm,
going
to
post
that
link
here
chapter
one
has
been
being
worked
on
for
many
many
months
now
and
I
think
move
some
stuff
forward
on
that.
A
Tom
had
some
thoughts
about
maybe
moving
to
github
posting
to
the
white
paper,
folder
on
the
tug
repo
and
then
creating
some
issues
and
PRS
for
making
some
updates
on
the
final
items
and
I
think
that
there's
maybe
a
few
of
the
pieces
and
the
paper
on
the
Google
Doc,
which
I've
posted
to
the
chat
here
that
are
probably
ready
to
close
out.
There's
a
lot
of
systems,
kind
of
replacements
on
items
that
were
agreed
on
in
earlier
parts
that
I
can
see
but
didn't
weren't
clicked
as
resolved.
A
E
Ya
can
do
what
you
say
of
copied
over
Ozzy's
as
comments
and
suggestions
are
closed
within
Google
Docs.
We
can
easily
modify
the
PR
and
the
idea
was
rather
than
having
kind
of
lots
of
different
comments
and
suggestions
within
a
single
Google
document.
You
can.
You
can
raise
issues
with
regards
to
a
particular
sentence
statement
paragraph
and
then
that
will
be
discussed
within
the
issue
and
then
the
change
made
in
a
specific
PR,
but
just
think
it
would
be
clean
a
way
to
manage
the
document.
F
F
F
B
C
So
I
think
tiller.
This
is
Robbie
for
for
the
purpose
of
this
white
paper,
the
chapter
one,
the
content
Tom
is
proposing
I
think
there's
generally
agreement
to
in
the
content,
so
it
might
make
sense
just
to
push
that
and
merge
it,
and
it
is
any
change
needed.
Then
that
will
be
following
the
PR
process.
At
the
moment
the
PR
is
introducing
that
content.
So
I
think
was
the
quantities
in
there.
You
can
start
adding
their
own
PRS
to
change
anything
if
they
feel
they
need
to
do.
A
A
Google
Doc
I
think
maybe
one
positive
would
be
and
folks
who
don't
have
access
to
Google
Docs,
there's
a
lot
of
companies
that
are
not
able
to
access
random
organizations
or
Google
orgs,
so
they
wouldn't
be
able
to
access
and
there's
a
lot
of
different
reasons.
So,
ideally,
yab
would
give
access
for
more
people.
So
that
would
be
a
good
thing
if
there's
any
disagreement,
if
you'd
give
a
+1
and
the
doc.
If
you
agree
for.
A
G
Sorry
for
it's
late
from
how
is
that
I
want
to
I
want
to
say:
is
there
any
a
ruse
on
this
pure
thing,
because
I
don't
know,
maybe
how
long
should
we
wait?
For
you
know
if
there's
any
comments
or
fears
happened
or
we
just
I,
don't
know
how
the
schedule
goes
because
it's
like
when
we
are
doing
this
with
Google
Docs.
We
have
many
comments
as
well.
F
D
A
Better
in
the
github
than
it
was
in
the
Google
Doc,
where
it
started
to
become
so
large
that
it
can
be
a
little
bit
harder
to
tell
where
which
direction
it's
leaning.
You
can
have
a
someone
that
may
put
a
whole
lot
of
content
and
it
seems
like
it's
pushed
more
one
direction,
but
you
have
several
people
that
just
gave
a
plus
thumbs
up
or
thumbs
down
and
and
then
the
history.
Once
we
close
out
a
comment
in
Google
Docs,
you
don't
really
see
where
that
is
so.
A
The
conversations
and
in
github
for
PR,
specifically
even
more
than
say,
issues
would
be
good.
So
maybe
we'll
get
a
little
bit
more
of
that
fill
assembly
and
I
think
the
other
thing
would
be
even
if
we
close
stuff
out,
let's
say
over.
If
we
just
said
leave
it
there
for
a
week
or
whatever
it
is,
someone
can
come
back
in
and
create
an
APR
or
we
can
add
to
the
issue
and
the
same
issue
and
say
I.
Don't
think
this
is
ready
and
here's
some
reasons
or
open
another
one
and
reference.
D
A
D
A
A
A
Probably
the
only
thing
that
I
can
think
that
we
may
have
talked
about
if
Dan
was
on.
The
call
was
the
CNF
conformance
and
I.
Don't
know
how
much
she
wants
to
go
into
that
since
it's
kind
of
early
most
of
it's
been
mentioned
before,
but
at
a
high
level
talking
about
bronze
silver
gold,
potentially
for
how
the
breakdown
for
certifications
could
be
and
what
we're
looking
at.
So
there's
some
efforts
to
go
along
with
that
high
level
idea
for
kind
of
the
plan
for
what
could
be
testing
and.
A
Are
these
things
following
cloud
native
principles
and
are
they
utilizing
stuff
that
would
be
expected
in
kubernetes,
and
maybe
some
of
the
things
like
metrics
and
and
monitoring
pieces
that
you
could
use
different
tools
like
Prometheus
and
open
telemetry
and
as
far
as
those
type
of
tooling?
How
are
you
exposing
the
application
platform?
A
These
are
all
initial
ideas,
along
to
kind
of
move
forward.
The
thoughts
for
the
gold,
silver
bronze
type
ideas
that
would
be
potentially
a
test
suite
that
could
run
and
looking
at
ideally
being
able
to
run
that
on
the
CNF
testbed.
The
the
end
goal
would
be
the
test.
Suite
itself
would
be
open,
source
and
available
for
anyone
to
download
and
run
possibly
two
parts,
maybe
completely
separate.
That
looks
at
the
actual.