►
From YouTube: CNCF Telecom User Group Meeting - 2019-10-21
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
A
Okay,
we
can
go
ahead
and
get
started,
so
this
is
the
second
call
of
the
month
for
the
telco
user.
This
calls
on
the
third
Monday
at
11:00,
UTC
or
7:00
p.m.
choice,
and
the
first
call
is
at
1500
UTC,
8:00
a.m.
so
not
as
I
guess
friendly
for
the
asia-pacific
time.
If
you
are
available
to
join
or
you'd
like
to
put
some
notes,
please
do
on
this.
I'm
definitely
want
to
try
to
I
collaborate
across
this.
If
it's
times.
A
A
A
So
one
of
them
is
planned
on
the
Monday
November
18th
we'll
have
another
one,
probably
the
next
day
or
the
following
day.
These
will
be
a
couple
of
hours
and
besides
any
other
ad
hoc
meetings,
but
we'd
like
to
carry
some
of
those
conversations
that
we
had
an
open
network
summit
on
so
if
you're
available
in
San
Diego
and
please
hey
Taylor
each
other.
Yes,
this.
B
Is
Dan
Kahn
from
CN
CF
I
just
want
to
interject
that
we
do
almost
have
those
I'm
set
and
we're
going
to
be
emailing
them
to
the
list
and
posting
them
on
slack
and
such
as
as
soon
as
we
do
it's
going
to
be
Monday
afternoon.
So
after
the
co-located
events,
probably
overlapping
with
the
with
the
lightning
talks,
and
then
it's
likely,
the
second
one
will
be
Wednesday
afternoon
and
I'll
just
point
out
to
come.
B
Normal
cube
concessions
are
35
minutes,
and
so
the
request
for
these
was
2
hours,
each,
which
is
much
more
challenging
to
schedule.
But
we
are
going
to
accommodate
that
in
order
to
try
and
allow
this
joint
meeting
of
the
telecom
user
group
and
see
NTP
and
we're
not
going
to
be
it's
not
going
to
be
posted
in
the
schedule.
But
we
do
we
will
be
sharing
the
notes
here.
We
encourage
folks
to
attempt.
C
A
D
Perfect,
so
I
went
ahead
and
collated
a
lot
of
different
things
that
a
lot
of
what
Taylor
had
written
in
some
parts
of
the
outline
and
created
a
chapter
one
a
sample
chapter.
D
This
is
that
incorporates
sort
of
cloud
native
for
Talcott
for
telecom,
101,
there's
I
think
a
little
bit
of
overlap
with
what
you're
working
on
Tomas,
but
not
too
much
and
Dan
and
I
are
in
the
process
of
just
making
sure
that
it
really
maps
to
what
community
sentiment
probably
will
be,
and
then
we
should
be
sharing
it
out
pretty
shortly,
so
the
community
can
have
a
look
at
it
and
and
weigh
in,
and
you
know,
add
their
own
inputs.
This
is
just
a
sort
of
a
version
one.
D
So
we're
happy
to
have
suggestions
and
changes,
of
course,
in
fact,
I'm
sure
that
they
will
be.
They
will
make
it
far
better,
but
it's
basically
covers
it
took
well
Taylor.
It's
based
in
part
on
some
of
the
things
that
you
wrote.
Some
of
the
the
bullets
on
on
you
know
on
how
OSI
layers
apply
to
to
cloud
native.
When
you
look
at
more
than
just
layer,
seven
and
also
some
just
basic
translation
from
vnfs
to
CNF
s--
in
a
few
other
items
like
that,
but
we
should
be
sharing
this
next
day.
E
Alex,
this
is
Thomas
I,
think
some
on
the
meeting
might
not
know,
but
Gergely
and
myself
have
also
started
working
on.
You
know
the
idea
CNF
part,
so
I
would
really
appreciate
Alex
your
feedback
on
that.
You
know
which
other
parts
which
might
overlap
and
which
are
the
parts
which
don't
overlap.
So
we
should
concentrate
on
those
I.
Think
time
is
running
short
and
and
and
I
would
prefer
to
concentrate
on
the
captors
and
on
the
parts
where
you
know
we
don't
have
any
overlaps.
E
D
C
C
E
E
Let
me
know
if
you
see
it
on
on
the
screen:
I
promise,
yeah
cool,
so
some
high-level
chapters
and
and
as
usual,
you
see
a
name
next
to
the
chapter
and
that
person
should
be
responsible
for
doing
the
chapters
so
right
now
the
work
is
divided
between
yoga
and
myself,
and
the
main
main
topics
are
Infrastructure
decoupling.
What
do
we
need
to
do?
I
mean
the
first.
The
whole
thing
is
about
hey.
E
We
need
to
reactivate
these
applications
if
we
want
to
cover
them,
see
and
F's,
and
then
we
have
the
cnc
of
cloud
native
definition,
which
should
fully
apply
but
needs
to
be
a
little
bit
interpreted
correctly
for
telecoil
and
and
the
paper
should
give
you
hints
and
help
about
how
to
interpret
that
correctly
for
taku
some
basic
principles.
One
is
the
decoupling
from
the
infrastructure
to
make
the
CNF
in
a
way
that
has
the
least
amount
of
dependencies
on
the
infrastructure.
E
Then
what
do
we
need
to
make
sure
that
we
have
the
right,
orchestration
and
automation
capabilities?
What
sort
of
surroundings
shall
the
CNF
depend
on
photos
and
how
do
we
extend
lifecycle
management
capabilities
of
kubernetes,
if
necessary,
for
stateful
services,
some
some
words
about
micro
services?
You
know
what
are
micro
services
in
a
trackhoe
context.
What
is
the
right
level
of
modularity?
What
are
the
benefits
of
modularity?
E
E
This
is
about
separating
state,
storage
and
and
business
logic,
benefits
and
and
and
how
shall
this
be
done
in
practice
and
then
last
but
not
least,
networking
how
to
use
standard
kubernetes
networking
as
much
as
possible
how
to
fit
in
into
an
existing
network
with
the
existing
gree
and
absentee
and
apps
for
sort
of
extra
requirement.
Does
that
put
on
the
system
and
as
some
examples
about
what
can
be
done
in
including
Muto's
denim
and
so
on?
F
E
I
think
I
did
justice
to
this.
What
we
have
so
far
and
I
think
what
these
mostly
discussed
is
that
Alex
already
started
working
on
something
and
is
in
the
process
of
talking
to
your
per
acre.
So
we
need
to
figure
out
if
we
have
a
novela
between
his
work
and
our
work
and
how
can
we
solve
that
overlap
as
fast
as
possible.
G
E
E
E
E
D
Top
thomas,
I
just
wanted
to
say
thank
you
for
your
patience-
will
be
sharing
very
quickly.
The
the
main
reason
we're
not
sharing
immediately
it's
just
because
I
am
so
new
to
this
I
just
wanted
it
and
just
wanted
to
make
sure
that
all
the
pieces
were,
you
know,
made
sense
or
were
were
correct
and
no
in
thinking
about
cloud
native.
You
know
for
from
a
community
standpoint.
We
should
be
sharing
it
very
quickly.
Thank
you
for
your
page.
E
E
F
E
Only
reason
I
have
started
a
separate
Google
document,
for
this
is
because
you
know
I
want
to
do
a
clean
sheet
of
paper
without
10,000
comments
and
and
just
my
thoughts.
You
know
that's
because
there
were
many,
many
things,
many
many
comments
and
good
discussions
there
I
didn't
want
to
inject
all
this.
In
fact,
I
started
and
I
realize
it
looks
very,
very
old
and
I
knew
that
Alex
has
thought.
It
is
something,
and
this
will
probably
have
to
be
merged
with
that
one
anyway,
so
to
make
it
make
the
merge
easier.
E
E
Yeah
and
I
think
I
think
that's,
maybe
that's
the
way
forward.
Maybe
we
should
we
should
you
know
that
plan
was
anyway
to
have
smaller
white
papers,
but
really
it's
done
more
frequencies
from
so
maybe
the
next
step
could
be
to
look
at
on
one
of
these
meetings
or
maybe
on
the
face-to-face
meetings,
the
existing
white
paper
topics
or
maybe
bring
some
more
up
and
together
figure
out
what
shall
be
the
next
topic
that
we
attack
and
then
we
break
that
out
and
we'll
work
on
that
separate.
Oh,
yes,.
F
E
A
Probably
at
a
point
where
we
need
to
update,
they
have
Chuck
on
music
root,
page
to
link
to
multiple
white
papers.
We
do
have
the
Google
a
Google
Drive
that
has
a
lot
of
other
documents,
so
I'll
put
that
on
my
list
too,
if
they
click
as
well
as
a
few
other
places,
so
that
we
can
have
an
index
out
to
the
multiple
talks.
Yeah.
E
E
Yeah
III
know
more
about
google
driver
less
about
github,
so
it's
just
not
ideal.
Maybe
for
collaborative
work
it's
better
to
to
I.
You
know
I'm
just
trying
to
find
the
best
option.
Since
Google
Drive
I've
seen
some
complications
between
many,
especially
those
working
through
their
eyes
on
they
had
trouble
accessing
the
document
using
their
corporate
email.
A
A
H
So
I
guess
to
do
it
somewhat.
Briefly:
we've
been
working
on
some
some
more
use
cases.
We
have
to
skate
with
a
router
use
case
from
NSM
that
we're
trying
to
incorporate
and
I've
been
talking
to
Nicolai.
That's
that's
part
of
the
development
team
and
put
in
SMS
wall
and
on
on
this,
because
previously,
when
we
were
using
the
universal
CNF,
that's
being
maintained
and
developed
by
NSM,
we
had
some
issues
with
external
interfaces
that
were
connected
through
DB
DK
and
we
after
some
debugging.
H
So
by
really
mounting
the
the
assists
directory
in
s,
read
I'll
rewrite
when
we
were
running
the
container
were
actually
able
to
have
much
better
control
of
the
physical
interfaces.
So
there
are
some
updates
come
into
the
use
cases
that
are
related
to
this
and
otherwise,
and
we're
just
making
sure
that
everything
is
easy
to
deploy.
H
Place
for
the
ESRI
OE
Network
device
plugin,
and
that
allows
us
to
have
some
better
control
over
the
ESRI
OB
interfaces
handed
to
each
container
and
that
that
all
seems
to
work,
and
we
had
some
issues
with
this
in
the
NSM
example.
I
think
the
one
that
would
be
in
show
case
that
ons.
But
with
this
this
new
changed
to
rebounding
the
assists
directory.
A
A
All
right
so
there's
this
is
the
road
map
for
the
CNF
test
bed
kind
of
going
forward,
and
some
of
these
were
mentioned
with
the
Gateway
update,
we'll
be
able
to
focus
on
more
of
the
NSM
use
cases
that
will
take
advantage
of
that.
One.
A
We
have
a
few
options
on
that.
We've
been
able
to
deploy
open
site
clusters
with
VPP
networking
as
the
EPP
being
a
high
speed,
V
switch
as
well
as
the
OBS
and
other
choices
for
OpenStack,
and
there's
been
some
issues
with
using
GRE
gateways
on
the
opposite
side
when
we're
doing
VPP
and
if
there's
anyone
that's
familiar
with
the
VPP
networking.
We've
have
some
open
bugs
that
we're
trying
to
resolve
on
that.
A
We
may
end
up
with
a
vs
endpoint
to
start
for
this,
and
we
would
want
to
get
VPP
in
place
before
benchmarking,
but
from
a
functional
side.
The
idea
is
to
have
some
type
of
network
function
or
set
of
a
chain
potentially
running
on
the
open
sect
side
and
another
set
that
are
running
in
thurber
Nettie's
and
being
able
to
connect
those
which
is
indicating
what
we're
seeing
at
production
setups,
where
you
may
have
different
vendors
running
requirements,
potentially
maybe
running
something
in
OpenStack
and
you're
wanting
to
connect
in
and
run
those
from
kubernetes
workloads.
A
So
that's
kind
of
the
goal
on
that
one,
we're
also
working
with
denimm
to
get
some
type
of
use
case.
This
will
probably
be
a
plated
is
updated.
It's
mention
SRV
use
case,
we'll
have
some
more
specifics
on
that,
and
we
have
some
tickets
that
are
going
in
based
on
some
specifications
that
we've
been
working
on.
A
E
Question
one
question:
this
is
tomash
only
on
the
on
the
MSM.
Sorry
no
be
testbed
roadmap.
That
was
an
item
on
on
five
years,
GSM
use
case
and
we
have
created
at
Ericsson,
since
we
are
doing
a
proof
of
concept
with
an
asam.
We
have
created
a
use
case,
description
for
a
5g
use
case.
So
the
question
is
where,
where
is
the
meeting
to
bring
it
on
for
discussion?
And
maybe
you
know
including
it
in
the
roadmap?
If
people
think
that's
meaningful.
E
E
No
I
reach
out
reach
out
and
I
make
sure
that
there
is
someone
from
our
site
you
can
participate.
Obviously
our
cost
strange
strange
situation,
I,
don't
think
I
would
be
able
to
participate
at
that
time.
But
I
talked
to
Henry
can
be
fair.
You
find
someone
to
go
to
the
meeting
tomorrow.
Yeah
I
think
as
long
as
we
have
the
invite
I
think
and
we
can
solve
that
if
it
possible
to
maybe
post
the
link
into
the
chat
here
or
something
for
simplicity,
sake.
J
E
A
A
Where
we
we
create,
we
created
a
issue
and
work
through
deciding
on
what
we're
gonna
actually
build
out
and
from
this
way
into
that,
there's
actually
Google
Doc
associated,
but
when
that
deciding
on
the
use
case
that
we're
going
to
actually
implement
and
that
so
it's
in
progress.
So
something
like
that
could
work
as
far
as
something
for
the
CNF
testbed
I'll
post,
the
to
the
network
service
smash
working
group
call
as
well
as
CNF,
test
bed
and
times
for
the
Thursday
into
the
the
telco
music
group
meeting
notes.
A
And
if
anyone
would
like
to
join
this
to
calls
their
weekly
and
we
can
contain
custom,
mastic
locks
it
and
just
thing
us
and
slack.
If,
if
you
want
to
set
up
a
call
outside
of
the
working
group,
call
to
dig
Antoninus
will
write,
leave
you.