►
From YouTube: OCB: Introduction to Cloud-native Network Functions for OpenShift - Paul Lancaster (Red Hat)
Description
Cloud-native network functions (CNF) are network functions designed and implemented to run inside containers. Containerization of network architecture components makes it possible to run a variety of services on the same cluster and more easily on-board already decomposed applications, while dynamically directing network traffic to correct pods. In this briefing, Red Hat's Paul Lancaster will give an introduction to CNFs and discuss how to ensure your containerized network architecture components can be designed, implemented, and supported with Red Hat OpenShift.
A
Well,
hello
and
welcome
to
another
openshift
commons
briefing,
and
today
we
have
my
friend
and
colleague,
paul
lancaster
from
the
partner
development
group
over
at
red
hat
in
the
cloud
platform
bu,
and
we're
going
to
talk
about
something
that
I
bet.
People
have
heard
a
lot
about,
but
don't
know
really
the
origins
of
and
what
the
details
are
behind.
It.
Cloud
native
network
functions
or
cnfs
which
get
misspoken
as
container
native
functions
or
cloud
native
functions.
A
But
today
you
know
diane
will
try
not
to
alliterate
the
the
acronym
and
let
paul
introduce
himself
and
tell
us
about
how
all
of
these
things
came
to
be,
and
hopefully
give
us
some
insights
in
how
you
too
can
build
some
cloud
native
network
functions
and
work
with
us
here
at
red
hat,
so
paul.
Take
it
away.
Thank
you
very
much
for
coming
today.
B
B
Your
network
applications
on
okay.
So
so
I
guess,
let's
start
first
of
all
with
defining
what
exactly
a
cloud
native
network
function
is
so
so
a
little
bit
of
credit
to
legato.
Here
I
pulled
this
from
their
their
site.
If
you
go
to
l-I-g-a-t-o
dot,
io
you'll
you'll
see
an
explanation
of
what
this
is,
but
at
a
high
level
right.
A
cloud
native
network
function
is
simply
an
application,
but
it's
a
specific
application.
B
So
it's
a
very
distinct
type
of
application
and
there
are
some
things
that
around
tuning
and
specifics
in
building
it
and
best
practices
that
we
can
talk
a
little
bit
about
as
we
go
on,
and
maybe
I
can
give
you
some
examples
of
but
think
about
this
as
an
application.
There
are
some
specifics
around
the
application,
but
it
is
a
type
of
application
that
is
built
on
kubernetes.
It
uses
kubernetes
principles.
B
There
are
some
specific
tunings
that
you'll
want
to
have
and
in
fact
we've
built
into
openshift
for
you.
So
at
a
high
level.
That's
what
a
cnf
is.
Okay,
so
in
terms
of
the
journey
that
the
community
and
the
partners
and
the
service
providers
themselves
are
on,
it
is
not
an
uncommon
journey
from
other
cloud-based
applications
right
so
very
similar
to
other
applications.
In
the
cloud
it
started
as
what
you
would
call
bespoke
hardware-
that's
very
verticalized,
especially
in
this
industry,
to
more
monolithic
applications
that
ran
as
virtual
machines.
B
Eventually
those
things
got
sort
of
broken
out
and
ran
on
more
horizontal
platforms
such
as
openstack,
where,
by
the
way,
we've
had
a
lot
of
experience
with
that
as
well,
and
then
you
know
ultimately
are,
are
making
their
way
or
have
made
their
way
and
still
are
making
their
way
towards
being
cloud
native
okay.
So
that's
the
network,
functions
or
nfv
journey
that
a
lot
of
these
folks
are
on.
B
Hopefully,
a
lot
of
you
folks
that
are
on
the
call
today
are
well
acquainted
with
this
and
and
what
what's
driving
it,
I
mean
what's
driving
it
more
than
anything
right
so,
and
there
are
a
couple
things
I
mean.
Obviously,
the
idea
of
a
next
generation
networks
around
the
world
are
really
driving
this
right,
so
both
the
csps
and
as
well
as
the
media
players
all
want
to
get
to
the
same
place,
which
is
to
be
able
to
run
applications.
B
Just
like
you
would
in
any
other
cloud,
okay
to
be
able
to
install
those
applications
to
manage
the
life
cycles
around
those
applications.
I
mean
really
to
just
make
it
easier
to
operate
and
deliver
new
services.
The
same
model
that
really
any
other
company's
journey
to
the
cloud
is
is
undertaking
again.
There
are
some
specifics
around
the
way
that
the
needs
of
these
applications,
but
this
is
what's
driving
it
right.
B
B
B
B
So
to
that
end,
red
hat
has
been
very
active
in
a
lot
of
upstream
communities,
not
just
the
kubernetes
or
the
cncf
communities,
but
many
different
communities,
including
linux
foundation.
Networking
you
know
I
mean
the
list
is-
is
very
long
open
air
interface,
the
oran
community
and
we
see
lots
of
our
customers
participating
in
these
communities,
and
this
is
a
just
a
for
instance,
of
a
customer,
a
very
large
customer,
china,
china
mobile,
who,
who
has
been
investing
in
in
helping
build
what
is
ultimately
going
to
land.
B
You
know,
ultimately
for
for
a
lot
of
different
service
providers
out
there
ways
to
deliver
these
applications.
You
know
using
open
source
technologies
right,
so
you
can
read
more
about
this.
I
the
the
actual
use
case
itself.
I
mean
you
just
simply:
google
5g
and
china
mobile
there's
a
lot
of
data
there,
but
in
particular
within
the
lfn
community
linux
foundation,
networking
community.
You
can
see
a
lot
of
the
work
that
china
mobile
has
done,
and
this
is
across
various
parts
of
their
network,
including
radio
and
ai,
and
their
entire
ecosystem.
B
This
is
one
of
the
partners
that
we
partners-
customers
players
in
the
service
provider,
community
that
we
see
oftentimes,
and
so
we
have.
You
know,
we've
worked
with
them
and
ultimately,
what
we've
done
as
far
as
putting
together
this
this
model
for
5g
cloud
native,
you
know
service
providers
like
china,
mobile
will
be
adopting
and
have
adopted.
B
So
maybe
I
can
talk
a
little
bit
about
some
of
the
architecture,
and
this
is
not
an
uncommon
architecture
that
you
would
find
due
to
many
services
that
are
being
built
out
in
a
global
way.
But
this
is
very
specific
to
to
network
functions
and
some
core
functions
and
some
edge
functions
that
you,
you
might
want
to
sort
of
build
out
your
architecture
to
look
like
this
right.
B
So
you
know
we
work
with
many
tier
one
service
providers
around
the
world,
and
this
is
kind
of
an
example
of
an
architecture
you
might
see
out
there.
So
where
there
are,
there
are
core
packet
processing
functions,
there's
an
sdn,
if
not
multiple,
sdn
layers,
and
then
there
are
edge
sites
out
there
with
applications
that
are
closer
to
radio
towers,
so
making
it
multiple
levels.
You've
got.
B
The
radio
tower
is
the
farthest
edge,
you've
got
a
centralized
office
edge
and
then
you've
got
your
data
center
edge
and
all
of
those
areas
are
sort
of
being
modified.
If
you
will
and
then
becoming
cloud
native
as
far
as
this
particular
architecture
is
concerned,
so
this
is
kind
of
an
example
of
what
we
did
or
what
we
are
doing
in
the
community.
Okay.
So
let's
talk
a
little
bit
about
the
poc
that
we
did
so
a
couple
of
years.
B
Back
now
we
started
working
on
something
called
vco,
which
is
short
for
virtual
central
office.
This
programmatically
has
gone
through
well,
not
programmatically,
but
technically
has
gone
through
a
couple
of
different
iterations.
We
of
course
had
a
virtual
machine
based
one,
but
now,
as
of
even
a
couple
years
ago,
had
moved
on
to
something
that
was
cloud
native
and
for
those
of
you
who
may
have
attended
cubecon
in
the
last
in-person
kubecon,
which
I
think
was
in
san
diego
a
few
years
back.
B
All
that
was
done
in
the
open,
and
these
were
the
locations
that
we
that
we
actually
used
right.
So
we
had
a
location
for
radio
that
was
in
europe.
We
had
a
location
for
the
control,
plane
and
core
which
was
in
montreal,
and
then
we
also
had
another
location
for
radio
and
core
which
was
based
in
san
diego,
and
this
made
up
our
global
network
for
delivering
this
plc.
B
This
was
the
architecture
for
the
poc
right,
so
all
of
the
functions
themselves
broken
out
for
four
as
well
as
radio.
You
can
see
how
that
sort
of
looked
here
and
who
some
of
the
players
were,
our
partners
like
kulum
and
lenovo
in
in
montreal,
as
well
in
san
diego
and
then
what
the
technologies
they
used
were
based
on.
So
it
was,
you
know,
obviously,
red
hat
enterprise,
linux
and
red
hat
enterprise,
linux,
core
os,
as
well
as
as
well
as
openshift.
B
B
B
B
This
is
the
software
stack
that
we
use
right,
so
it
was
all
running
on
bare
metal.
Well,
not
all
of
it.
Some
of
it
was
running
in
a
public
cloud,
but
for
a
lot
of
the
cnfs
that
was
running
on
bare
metal,
with
with
red
hat
enterprise,
linux
and
red
hat
enterprise
square
os,
openshift
container
platform
running.
On
top
of
that,
a
lot
of
the
cloud
native
applications
and
projects.
B
We
were
leveraging
all
the
ones
that
you
can
see
there
on
the
left
and
then
for
the
public
cloud
pieces
you
can
see.
Some
of
the
functions
were
actually
run
there
and
then,
of
course,
the
list
of
partners
that
we
had
folks
like
a10
and
ultron,
and
the
ones
that
I
mentioned
before
ultimately.
Making
this
happen.
B
B
Red
hat
believes
that
we
have
the
most
enterprise
ready,
kubernetes
distro
out
there,
and
we
look
to
the
community
to
help
us
make
make
it
better
frankly.
So
this
is
the
work
that
we've
been
involved
in.
In
terms
of
you
know
the
ecosystem,
the
cncf,
the
lfn
and
making
all
of
this
work
available,
ultimately
to
our
service
provider.
Customers
who
run
who
want
to
run
their
cloud
native
functions
on
top
of
openshift.
B
This
is
what
the
bare
metal
deployment
look
like.
Don't
have
to
get
into
too
much
of
the
detail
here,
but
you
can
see
how
we
set
up
real
time
and
had
fpga
cards.
So
these
are
some
of
the
things
that
I
talked
about
earlier.
That
are
little
tweaks
that
are
expected
from
folks
in
the
service
provider.
Industry,
red
hat
includes
operators
that
take
care
of
these
tunings.
B
A
A
B
B
B
B
A
If
you
just
put
it
in
the
chat,
chris
short
can
run
the
video
and
play
it
pull
it.
We
can
pull
it
down,
but
don't
worry
about
it
just
go
on
to
where
you're
at
in
in
the
slides
and
you.
If
you
give
me
the
video
and
anyone
who's
listening,
I
will
throw
the
video
into
the
edited
version
of
this
so
that
you
can
hear
the
play-by-play.
A
B
B
B
A
A
This
whole
thing
into
something:
that's
actually
a
program
now
for
certifying
container
native
network
functions.
You
know
it's
been
yeah
we've
been
watching
this
transition
and
all
for
almost
I've
been
watching.
I'm
sure
you've
been
watching
it
much
longer
because
you've
been
in
the
telco
space
waiting
for
this
all
to
evolve.
But
for
me
it
sort
of
hit
in
2019
when
the
gentleman
from
china
mobile
came
and
stood
up
on
stage
and
he
was
saying
waving
his
hands
and
he
had
the
most
deep
dive
thing.
A
You
know
it
was
sort
of
mind-blowing
this,
the
schematics
that
he
was
doing
yeah
and
what
what
you're
showing
now
is
so
much
more
I
mean
it's,
it's
comprehendable
that
you
know
that
the
dyers
and
I
think
that's
what
these
container
native
network
functions
have
done,
is
they've,
taken
the
complexity
out
of
deploying
this
and
cleaned
it
up.
So
it's
reproducible
and
automatable
in
a
way
that
even
in
2019
was
you
know,
somebody's
dream
well,.
B
I
mean
I
think
that
is
the
case
right,
so
a
lot
of
the
work
that
we're
finding
in
the
in
the
ecosystem.
Now,
in
terms
of
the
partners,
I
mean
they're
definitely
make
doing
a
lot
of
work
to
make
their
applications
much
more
easily
deployable
on
openshift,
and
a
lot
of
that
has
to
do
with
their
belief
in
things
like
kubernetes
operators,
the
operator
framework
and
building
operators
to
do
things
like
not
only
the
the
day,
one
sort
of
install
and
upgrade
stuff,
but
ultimately
how
they
operationalize
their
application.
B
So
the
day
two
things
and
all
of
the
additional
functionality
you
can
build
using
an
operator.
So
so
there's
that
and
not
only
that,
but
what
we've
built
into
our
platform
from
an
operator
perspective.
So
a
lot
of
the
learnings
that
we've
taken
from
having
customers
that
are
tier
one
service
providers
around
the
world.
B
We've
actually
put
those
tunings
into
our
product
using
operator
concepts
right
using
literal
operators
like
I
keep
mentioning
the
performance
add-on
operator
and
the
sriov
operator
to
make
it
that
much
easier
for
anyone.
Who's
interested
to
deploy,
build,
deliver
their
cloud-native
functions
on
top
of
openshift.
B
B
B
A
I
think
somebody
told
me
the
other
day
we
had
around
40
to
45
of
them
in
in
the
you
know
already
certified
out
there,
but
I'm
sure
there
are
lots
more
use
cases
and
different
things
that
we
can
do,
and
so
the
more
people
talk
about
you
know
what
it
took
to
build
them
to
containerize
these
things
and
and
get
them
tested.
I
think
that'll
be
an
interesting
thing
for
the
community
to
to
learn
about,
and
also
you
know
how
some
of
these
things
are
being
used
in
in
practice
too.
A
B
B
We
certainly
hope
to
be
able
to
bring
some
of
the
partners
or
a
lot
of
the
partners
that
we've
worked
with
to
do
openshift
commons
and
have
them
talk
about
the
work
that
they've
done.
There's
some
very
specific
work,
depending
upon
the
use
case.
That
probably
is,
is
very
interesting
to
to
the
attendees.
B
Obviously,
if
you
know
you're
a
radio
application,
it's
a
lot
different
than,
if
you're
say
a
core
application,
and
we
can
talk
maybe
to
some
of
those
those
those
partners.
I
mean
the
the
partners
that
we're
working
with
on
the
radio
side
or
partners
like
altostar,
parallel
wireless
ericsson.
I
mean
this
kind
of
goes
on
and
then
on
a
core
side.
It's
very
similar,
your
firm
networks
of
the
world,
your
maven
years
of
the
world,
casa
systems,
erickson,
etc
so
yeah.
A
B
B
A
B
B
It
is
indeed
yes,
okay,
so
the
first,
the
very
first
step
for
anyone,
who's
interested
in
partnering
with
red
hat
and
helping
having
us
help
them
build
their
cloud
native
network
functions
to
best
practices
on
openshift
is
for
them
to
join
the
technology
partner
program
right,
so
you
can
go
to
slash
access.redhat.com,
there
is
there's
a
there
should
be
two
options.
There.
B
One
option
is
the
technology
partner
program,
and
once
you
join
the
the
technology
partner
program
that
will
allow
you
access
to
all
of
our
products
and
services,
including
openshift
right,
it
will
allow
you
to
do
things
like
you
know,
grab
subscriptions,
etc,
but
that
is
is
where
you
want
to
start
now.
There
is
a
there
is
a
workflow
which
I
can
share
with
everyone
on
how
to
go
through
this
journey.
It's
a
git
book
and
maybe
I'll.
A
There
there
is
one
question,
but
it
might
be
slightly
off
topic
and
it's
coming
in
from
one
like
either
youtube
land
or
somewhere.
What
are
the
benefits
of
openshift,
serverless
and
openshift
service
mesh?
I
think
that's
a
bit
off
topic
for
today,
but
I
don't
know
from
from
my
perspective.
I
think
that's
not
something
in
this
belly.
Wick.
B
A
Work
with
there's
a
ton
of
there's
a
ton
of
other
openshift
commons
briefings
on
both
of
those
topics
that
we
can.
We
can
shoot
you
through
and
now
and
get
you
to,
but
I
think
that's
a
little
out
of
scope
for
today's
conversation.
Just
to
let
kesh
know
that
chris.
That
would
be
okay
and
we
definitely
will
cover
that
in
in
multiple
times
and
we'll
cover
it
in
future
talks
as
well.
A
So
I
I
think
that
the
the
interesting
thing
for
me
is
and
then
I'm
going
to
go
back
to
this
evolution
of
from
2019
to
you
know.
Here
we
are
in
2021
and
it's
you
know
highly
operator
focused
and
there's
certification
programs
in
there.
What
do
you
see
is
the
next
big
thing
in
this
road
road
map?
What's
beyond
you
know
getting
your
your
functional
certified,
I
would
say.
B
B
You
know
tier
one
service
providers,
even
through
two
service
providers,
are
all
sort
of
going
through
this
transition
and
that
you
know
ultimately
is
driving
the
next.
The
next
level
I
mean,
hopefully
the
next
level
will
be
continued
to
be
open.
There
are
projects
that
are
even
looking
at
how
to
open
more
of
the
radio
bits
or
radio
applications
projects
like
oran
and
the
open
air
interface
which
I
mentioned
earlier.
B
A
Together
and
you
know,
and
in
industry-backed
initiatives,
but
they
weren't
really
huge
open
source
players
and
and
now
you're
seeing
them.
You
know
all
you
know
coming
together,
whether
it's
in
the
linux
foundation
or
in
you
know
the
cloud
native
foundation,
and
that
is
really
huge
eye
opener
for
me,
and
I
think
that's
also
helping
a
lot
drive
these
things
to
be
much
faster
in
the
evolution.
B
Excuse
me,
a
lot
of
the
vendors
who
are
or
have
been
supplying
the
telecommunications
service
providers
for
many
years
are
now
starting
to
realize
that
this
is
the
trend,
and
so
all
of
these
vendors
are
are
now
starting
to
collaborate
in
the
open,
and
I
think
that
is
you
know.
That's
the
sea
change
that
everybody
wants
right.
It's
the
sea
change
that
the
customer
wants,
and
it's
also
the
it's
the
evolution
of
how
we
all
work
together
and
so
we're
starting
to
find
the
various
players.
B
A
A
Because
it,
you
know,
there's
a
huge
initiative
inside
of
red
hat
around
telcos
is
you
know,
coalescing
of
different
technologies?
I
mean
you're
focused
on
one
area,
but
there's
you
know.
There's
another
team.
I've
been
working
with
bill
wright
and
lisa
k
wood
around
this
enterprise
neurosystems
initiative
around
leveraging,
what
a
few
what's
the
mexican
telcos
name.
I
can't
think.
A
Yeah,
thank
you
mobile.
Thank
you.
I
have
been
doing
and
they're
open
sourcing
all
their
ai
ops,
for
you
know,
automating
and
and
the
the
back
end
side
of
the
telco
operations,
and
you
know
you
know
ten
years
ago,
five
years
ago
you
weren't,
you
wouldn't
see
this,
and
this
is
just
I
think,
and
and
we
see
it
in
every
industry.
A
So
it's
it's
not
new,
but
the
embracing
of
you
know
the
open
source
development
model
and
the
understanding
that
doing
it
and
innovating
together
benefits
everybody
and
also,
I
think
it
makes
it
easier
for
end
users
and
customers
to
adopt
and
trust
the
services,
so
they're
not
dealing
with
one
big
locked-in
proprietary
entity.
So
I
think
it's
a
it
gives
a
better
level
of
trust
that
you
know.
Maybe
they
can
move
and
play
in
different
spaces
and
aren't
as
locked
in,
but
it
benefits
everybody.
B
You
know
in
the
energy
world
and
mining
and
and
the
service
providers
are
a
part
of
this,
and
this
and
the
applications
that
live
on
the
network
are
all
part
of
this.
So
again,
a
lot
of
those
use
cases
ultimately
are
driving
changes
as
well.
In
addition
to
the
fact
that
everybody
on
their
handset
wants
to
have
the
best
possible
experience,
there's
these
other
use
cases
that
are
sort
of
adding
on
top
of
that
to
drive.
What's
the
change
in
intel
communications.
A
So
it's
going
to
be
an
interesting
ride
this
next
couple
of
years.
I
think
watching
watching
this
space
and
seeing
what
comes
out
of
the
telcos
space
as
they
learn
more
and
more
about
you
know
the
power
of
collaborating
here
and
I
think,
the
stuff
that
your
team
has
been
doing.
You
were
working
with
a
couple
of
architects.
A
So
it's
really
interesting
to
watch
how
the
partner
ecosystem
is
evolving
and
the
best
practices
and
getting
the
labs
set
up
and
getting
all
the
stuff
available
and
the
role
of
red
hat
as
the
vendor
or
and
partner
for
all
of
these
folks
who
are
collaborating
helping
them,
you
know,
do
the
testing
you
know
get
the
best
practices
in
place,
make
sure
it's
all
secure.
We
really
it
is.
A
B
It's
interesting
that
you
mentioned
best
practices,
I'm
going
to
put
another
link
into
the
chat
for
folks,
but
this
is
a
document
that
we
spent
a
lot
of
time
on
with
it
with
verizon
in
particular,
and
it's
a
road
map.
It's
a
very
in-depth
and
detailed
road
map
on
how
to
best
build
your
cloud
native
functions
for
openshift,
it's
60-plus
pages
of
very
deep
technical
and
engineering
information
on
how
you
can
do
that,
and
so
you
know
it's
a
pdf.
I
would
encourage
you
guys
to
go
grab
it.
B
A
B
A
With
any
of
this-
and
I
think,
that's
the
beauty,
beauty
of
having
having
you
on
to
be
able
to
explain
this
because
it's
like
most
of
us-
we
hear
about
this
stuff,
but
we
don't
have
you
know
this.
You
know
this
is
this.
Is
big
buck
lab
setups?
I
know
this
is
not
your
home
lab
thing
that
you're
gonna
do
with
okd
or
something.
A
Yeah,
no
I've
heard
you
guys
bandy
about
some
price
tags
for
these
labs
and
I'm
like
okay
and
out
of
my
little
open
source,
okd
home
lab
budget
here.
But
it
really
I'm
grateful
that
you
came
and
you
spent
the
time
today
and
and
you
you
shared
the
stories
with
us.
I'm
really
looking
forward
to
you
kicking
off
a
series
with
some
of
the
partners
to
tell
us
about
their
journeys
and
what
they're
doing
on
the
edge
and
in
telco
and
how
this
is
working.
A
And
what
I
really
think
is
that
some
of
the
we
should
get
the
open
air
folks
and
yeah
the
other
build
them
to
come
in
to
tell
you
know,
give
sort
of
an
update
on
where
they're
at
with
their
projects
and
where
they're
going.
You
know
what
the
roadmap
is
and
where
you
know
how
to
contribute
in
the
upstream
too.
A
So
I
think,
there's
there's
a
lot
of
content
here
that
we
can
tease
out
and
in
the
coming
months
to
to
really
showcase
some
of
this,
because
you
know
we've
come
a
long
way
since
the
barcelona,
spain,
china,
mobile,
talk
that
that
I
gave
that
kind
of
was
like
whoa.
This
is
really
complicated,
I'm
not
sure
I'm
going
to
get
you
know
and
the
odds
you
could
see.
A
Sometimes
you
know
that
the
diagrams
were
like
packed
in
every
inch
of
his
slide
and
he
was
he
did
a
wonderful
job
of
it
and
especially
in
the
time
allotted,
but
you
could
see
where
the
complexity
has
really.
The
operator
ecosystem
has
really
helped,
simplify
a
lot
things,
and
so
that's,
I
think
the
other
piece
of
the
puzzle
is
the
other
technologies
kubernetes
and
maybe
service
mesh
and
serviceless,
and
all
of
these
other
things
start
to
come
into
play.
A
Simplifying
the
complexity
of
where
we
are
at
even
just
in
2019
over
the
coming
months
will
be
really
what
I'm
looking
forward
to
seeing
hearing
more
about
and
where,
where
people
can
contribute
in
the
upstream,
and
if
you
it.
Definitely,
if
anyone's
watching
this
and
listening
and
you're
interested
in
you
know
getting
on
board
in
the
labs
or
getting
your
you
know,
learning
more
about
the
best
practices
or
getting
certified
for
open
shift.
Calls
the
person
to
reach
out
to.