►
From YouTube: Building End to End Telecom Solutions Using Magma ac... Brian Barritt, Arpit Joshipura and Tina Tsou
Description
Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
Building End to End Telecom Solutions Using Magma across Open Source Projects - Brian Barritt, Facebook Connectivity, Arpit Joshipura, The Linux Foundation and Tina Tsou, Arm
A
Magma
is
a
hyper
scalable
and
distributed
core
one
of
the
things
that's
different
about
magma
is
it's
designed
to
run
at
the
far
edge
on
far
edge
appliances
to
support
local
breakout
to
ip
all
the
way
at
the
sell
site,
it's
open
source
and
license
free?
It's
cloud
native
containerized
and
features
control,
plane,
user,
plane,
separation,
it's
modern
vendor
and
transport
agnostic
and
supports
integration
with
existing
mobile
network
operator
cores
using
the
optional
federation
gateway
shown
on
the
diagram
as
amar
explained,
and
it
supports
all
access
conversions.
A
A
Magma
was
announced
as
an
open
source
project,
with
the
release
1.0,
backed
and
supported
by
the
open
infrastructure
foundation,
the
telecom
infra
project,
as
one
of
possibly
several
open
core
networks
and
the
open
air
interface
software
alliance
and
since
july
2020
the
community
has
grown
rapidly
so
across.
These
three
sets
here
of
advocates
contributors
and
participants.
A
A
The
community
is
actually
even
larger
than
that.
If
you
look
at
the
last
tier
in
the
orbit
model
of
people
who
are
observers
of
the
project
that
are
starring
our
repo
or
pulling
a
branch
on
on
github,
it's
actually
even
larger.
So
we
have
we
clock
in
over
1500
members
of
the
community
at
this
point
that
are
either
members
of
our
slack
community
or
starring
our
repo
and
are
pulling
a
branch
on
git.
A
So
when
the
magma
core
foundation
was
founded
in
2021,
we're
really
trying
to
position
magma
as
the
de
facto
open
source
network
core,
and
we
think
we're
there
with
the
launch
of
the
magma
core
foundation.
So
you'll
find
familiar
governance
from
the
linux
foundation
with
a
technical
steering
committee
and
a
governing
board.
The
technical
steering
committee
is
comprised
of
is
elected
group
of
contributors
and
the
governing
board
is
comprised
of
members
that
join
to
help
steer
the
project's
strategy.
A
So
we
retain
our
affiliation
with
the
telecom
info
project
as
one
of
possibly
several
open
core
networks.
Facebook
community
still
provides
a
backstop
of
software
engineering
contribution
to
the
community.
We
also
provide
a
backstop
of
technical
support
to
systems
integrators
and
value-added
resellers
that
want
to
deploy
magma,
who
can
be
assured
of
that?
It
can
receive
level
4
support
from
the
facebook
software
engineering
team
for
any
operational
issues
that
could
emerge.
A
A
The
academic
community
really
helps
spur
innovation
that
we
see
flowing
into
startups
that
want
to
use
magma
to
build
novel
solutions
that
they
build
on
top
of
and
then
startups
help
drive.
Adoption
in
industry
groups
so
startups
often
will
partner
and
use
magma
technology
to
build
end-to-end
solutions,
new
innovative
solutions
and
take
things
to
market.
A
If
you're
a
startup
or
an
investor,
we
think
the
magma
stack's
pretty
compelling
because
it
lets
you
build
your
solution
faster
and
accelerate
your
product
development,
your
total
time
to
market.
If
you
have
an
expert
community,
you
can
lean
on
and
you
can
explore
adjacent
opportunities
in
emerging
use
cases
around
the
core
problem
you're
trying
to
solve.
So
it
really
it's
just
going
to
help
you
accelerate
as
a
project.
A
So
you
can
see
here
some
of
the
quotes
from
from
boris
the
founder
and
ceo
of
freedomfi,
and
also
patrick
the
founder
and
ceo
of
connect
5g,
who
know
how
magma
helped
them
in
their
project
go
to
market
faster.
Deploy
faster
and
and
really
act
as
an
engine
powering
wireless
innovation,
so
I
noted
magna
is
partnering
with
academic
and
public
domain
projects.
A
So
if
you
think
about
some
bleeding
edge
research
projects
that
you
know
are
trying
to
do,
experimentation
on
some
of
the
latest
things
in
3gpp
or
other
projects,
it's
not
very
practical
to
start
from
scratch.
Recreating
parts
of
a
4g
or
5g
stack
only
to
add
your
new
use
case,
or
differentiation
or
research
project
on
top
of
it,
and
it's
difficult
to
do
that
with
any
existing
commercial
solutions,
because
you
don't
have
access
to
the
source
code.
A
So
what
we're
witnessing
is
that
a
lot
of
the
bleeding
edge
features
are
showing
up
first
in
open
source.
So
an
example:
there
is
a
non-terrestrial
connectivity
with
the
satisfy
project
or
the
esa,
alex
project
by
the
european
space
agency
to
adapt
cellular
protocols
and
waveforms
to
be
used
for
non-terrestrial,
high
altitude
platforms
and
satellite
connectivity
projects.
A
That
has
a
quicker
turnaround
time
on
vulnerabilities.
So
we
support
several
universities
as
well
shown
here
who
are
using
magma
and
are
contributing
back
to
the
community,
so
just
to
highlight
a
couple
of
really
interesting
building
blocks
and
solutions
that
we
see
happening
in
the
community
that
were
featured
in
our
magma
developers.
Conference
that
I
thought
were
particularly
exciting.
So
we
featured
in
in
february
of
this
year
that
we
now
have
support
for
amazon's,
far
edge
appliances
to
deploy
the
magma
access
gateway
component.
A
You
just
tell
amazon
where
you
want
them
shipped
and
one
of
these
boxes:
ships
out
pre-provisioned
with
the
ami
for
the
magma
access
gateway
and
set
up
for
zero
touch
provisioning,
where
it'll
connect
back
to
your
to
your
aws,
hosted
orchestrator
in
an
aws
region
or
on-prem
on
outpost
and
set
up
your
network
for
you
and
you're
ready
to
go.
You
just
connect
your
5g,
4g
or
5g
radio
to
it,
which
I
think
is
pretty
exciting.
So
these
are
ruggedized
boxes
that
are
low
cost.
A
A
B
B
B
One
of
the
fundamental
things
that
we
have
been
doing
here
at
the
linux
foundation
is
trying
to
get
them
to
evolve
these
markets.
So
in
the
middle
you
kind
of
see
a
big
segmentation,
you
know,
there's
the
enterprise
networking
users
and
then
there's
the
service
providers.
Service
providers
obviously
include
cloud
service
providers,
telecom
carriers,
etc,
and
then
in
the
enterprise
you
have
the
different
verticals
that
each
have
a
different
need
from
an
iot
and
an
edge
perspective
that
will
use
magma
as
well
as
other
projects
slightly
differently.
B
So
if
you
look
at
the
specific
use
cases
on
that
are
very
important
in
2021
and
maybe
a
couple
of
years
since
then,
specifically
for
enterprise
networking,
you
can
see
we
have
private
lte
how
workloads
run
across
clouds.
How
do
you
get
network
visibility
for
an
enterprise
in
these
multi-cloud
deployments,
but
then,
when
it
comes
to
service
providers,
the
telecom
and
cloud
service
providers
are
collaborating
significantly
under
the
linux
foundation.
B
Networking
under
the
linux
foundation
edge
under
cncf
to
bring
you
know
an
end-to-end
5g
based
deployment
to
train
people
on
5g,
to
develop
global
connectivity,
huge
initiatives
going
on
and
and
and
then,
as
you
get
into
some
of
the
very
important
users
that
are
taking
advantage
of
this
open
source
stack.
You
know,
government
across
the
globe,
is
at
the
forefront
of
building
on
these
end-to-end
open
source
projects.
B
B
You
know
I've
presented
this
at
multiple
conferences,
but
it
keeps
getting
better
and
better
and
and
as
more
innovation
comes
in
from
the
left,
the
various
means
of
access,
mobile
networks,
residential
small,
medium
or
enterprise,
whether
they
have
their
own
data
centers
or
not.
You
come
in
through
oram
a
project
under
lfh
called
home
edge,
fledge
eve.
B
B
So,
let's
talk
through
how
these
projects
come
together
from
an
open
source
perspective.
As
we
all
know,
projects
are
hosted
under
neutral
governance.
With
the
developer
community,
tsc
code
gets
produced,
documentation
gets
produced
a
set
of
use
cases
whatever
right
I
mean
it's.
It's
a
set
of
technology
that
gets
produced
created
across
the
world,
brought
together
by
either
products
and
integration
integrators.
So
these
could
be
vendors
system,
integrators,
bringing
it
all
and
then
put
into
production
where
people
can
make
money
and
then
invest
back
in
the
community.
B
So
that's
kind
of
the
the
circle
of
project
life,
if
you
may-
and
one
of
the
things
that
we
have
seen
in
the
last
three
years-
is
the
need
for
accelerating
what
is
the
lower
part
of
the
cycle
products
to
production,
and
for
that
a
couple
of
things
need
to
happen.
The
interop,
the
compliance,
the
verification,
the
testing,
the
certification,
et
cetera,
et
cetera,
needs
to
happen
in
the
open,
open
world.
It's
not
open
source
software,
but
it
is
open
source
governance
and
two
initiatives
that
I
want
to
point
out.
B
One
is
lf
networking's,
a
project
that
kind
of
combined
two
existing
projects:
opnfv
and
cntt.
I
mean
I'm
throwing
a
lot
of
acronyms
here,
but
essentially
they
they
are
responsible
for
defining
architectures
reference
architectures,
whether
it's
openstack
based
or
kubernetes,
based
into
a
reference
implementation
that
a
solution
can
get
tested
against,
whether
it's
an
fbi,
man
or
vnfs,
and
get
certification
and
batching
for
that.
B
B
As
you
know,
it's
it's
one
of
the
largest
communities
and
the
largest
alliances
to
disaggregate
and
open
up
the
rand,
which
is
one
of
the
last
pieces
of
the
puzzle
in
the
telco
network.
Linux
foundation
hosts
the
software
community
for
oran,
which
is
called
oran
sc,
and
the
use
cases
that
are
being
produced
created,
discussed.
There
are
rg
end-to-end,
slicing
quality
of
experience,
optimization.
How
do
different
white
boxes
come
in,
etc?
B
Then
you
move
on
to
you
know:
kubernetes
openstack,
you
know
sort
of
the
cloud
layer
or
or
the
virtualization
layer.
If
you
may
infrastructure
there,
and
then
you
get
into
anuket,
which
I
talked
about
open
compliance,
verification,
standardization,
onboarding,
reference,
implementation,
onap.
I
I
won't
talk
about
the
control
plane
projects.
You
know
they
have
been
proven
and
deployed
in
in
for
quite
some
time
now.
But
then,
when
you
get
into
onap,
you
get
into
5g
network
slicing
cross
cloud.
Vpn
zero
touch,
close
loop
control
loop.
B
You
know
lots
of
these
real
use,
cases
that
are
needed
for
network
automation
and
then
on
top.
Obviously
the
magma,
which
is
you
know,
a
critical
piece
of
the
open
source
core
wireless
network.
So
you
know
these
use.
Cases
are
being
done
in
each
of
these
projects,
and
you
know
our
our
goal
is
to
bring
it
all.
Together.
B
You
move
up
into
the
or
move
out
into
the
edge
of
the
network.
You
know
you
have
a
set
of
projects
that
are
now
trying
to
unify
the
edge
across
the
cloud
deployments
across
iot
across
the
enterprise
and
across
telco.
So
think
of
you
know
these
four
markets
trying
to
solve
the
same
problem
of
plumbing
life,
cycle
management,
onboarding,
etc
for
the
edge
computing
world
right
and
I'll
talk
about
the
definition
in
just
a
bit.
But
some
of
the
examples
include
you
know:
virtualization
on
on-prem
devices,
anomaly,
detection
right.
B
You
have
projects
like
fledge
that
are
doing
extremely
constrained,
sensitive
iot
type,
predictive
maintenance
and
and
base
monitoring,
right
turbines,
transformers
pumps,
etc,
or
you
have
ajax
foundry,
which
is
one
of
the
large
projects
under
lfh.
That
would
do
iot
frameworks
again
all
in
the
open
source
for
building
automation,
industrial
process
control,
smart
cities
and
then,
of
course,
you
have
on
the
edge
crano,
where
you're
going
to
build
blueprints
for
testing
out
these
various
use
cases
and
deploying
it
very
very
quickly.
B
So,
let's
take
a
moment
and
define
the
edge,
and
this
is
important
because
you
know
you
will
see
very
quickly
that
you
know
when
tina
comes
and
talks
about
an
icn
blueprint
under
a
crano.
It
kind
of
uses
terminology
that
fits
together
beyond
what
magma
you
know
defines
in
the
core.
So
this
diagram
is
one
of
the
most
most
screenshotted
diagram
in
this
kind
of
new
world
of
the
pandemic.
B
Right,
I
wouldn't
say
the
most
widely
used,
but
the
most
screenshotted
diagram
that
we
have
seen
on
all
these
virtual
presentations
and
what
it
is
is
under
an
umbrella
called
lfh.
We
have
taken.
The
community
has
taken
the
liberty
to
define
the
definitions
in
terms
of
an
edge,
and
this
is
what
the
diagram
shows.
So,
if
you
look
at
the
bottom,
there's
really
two
types
of
edges
and
before
I
get
into
that,
you
know
think
of
the
terms
that
you
have
used
in
edge.
You
know
thin
edge
thick
edge,
far
edge
near
edge.
B
You
know
all
these
are
relative
terms
and
they
don't
mean
the
same
thing
to
everybody.
So
what
the
community
did
was
they
standardized
on
definition?
So
we
would
really
appreciate-
and
you
know,
as
magma
community
as
well
as
you
know,
cncf
community
starts
looking
at
edge
computing
to
use
and
utilize
these
terms,
because
that's
what
the
edge
community
has
done
so
there's
two
types
of
edges:
there's
a
user
edge
and
then
there's
a
service
provider
at
user
edges,
dedicated
and
operated
by
the
user
service
provider
edge
is
shared
and
as
a
service.
B
If
you
go
in
the
user
edge,
it's
not
one
implementation
and
that's
part
of
the
challenge
we
have
in
the
community,
but
we
have
been
able
to
standardize
across
three
specific
implementation.
There
is,
on
the
extreme,
left,
an
edge
that
really
has
extreme
constraints,
right,
physical
constraints,
resourcing
constraints,
memory,
compute,
etc,
hardening
constraints
and
that's
called
constraint
device
edge.
B
These
could
be
microcontroller-based.
This
could
be
embedded,
compute,
etc.
Then
you
get
into
some
more
semi-secure
locations
where
you
know
you
may
have
an
iot
gateway
sitting
around
still
in
the
control
of
an
enterprise
user
or
an
iot
user,
and
there
you
may
have
something
called
a
smart
device
edge
and
then,
if
you
are
a
large
enterprise
or
if
you
have
enough
of
these
factories,
buildings,
homes
etc,
where
you
have
servers
in
a
semi-secure
location,
then
you
have
something
called
on-prem
data
center
edge.
These
are
all
again
in
the
control
of
a
user.
B
B
So
if
you're
putting
edge
compute
below
the
ram
and
if
you're
putting
it
in
a
smart
central
office
about
say
one
to
six
servers,
you
can
get
the
about
20
milliseconds
of
latency
across
the
application
and
that's
very
critical,
because
5g
really
narrows
down
on
the
transmission
like
see,
as
we
all
know
so,
once
you
have
that
you
can
now
have
edge
computing
all
the
way
to
the
smart
central
office.
Anything
after
that,
the
latency
may
be
a
tricky.
B
B
So
with
that
said,
the
projects
shown
here-
and
I
won't
go
into
that
because
some
of
them
are
relevant
to
magma's
community.
Some
of
them
are
not.
Some
of
them
are
relevant
to
the
cncf
community,
but
the
more
important
thing
here
is
there
is
a
different
types
of
constrained:
edges,
everything
from
infrastructure
to
application,
edgex,
foundry
and
crano
being
the
the
two
largest
projects
most
mature.
B
If
you
make
stage
three-
and
we
have
seen
several
other
projects
moving
up
the
pipeline
as
well,
if
you
want
to
download
the
whole
lf
edge
report,
we
just
published
it
under
lfi
state
of
the
edge
and
it's
huge,
the
market's
huge,
and
we
want
to
take
advantage
of
that
whole
edge
computing.
You
know
using
using
cncf
projects
using
lfn
lf
edge
and,
more
importantly,
you
know
integrating
with
magma.
So
I
really
I
wanted
to
take
this
couple
of
minutes
to
get
into
explanation
of
the
the
edge
terminology.
B
So
with
that
said,
how
do
we
pull
this
all
together?
We
pulled
this
all
together
in
an
end-to-end
solution
in
a
project
called
or
I
would
say,
an
initiative
called
end
to
end
5g
super
blooper,
it's
hosted
by
the
linux
foundation
networking,
so
you
can
go
to
www.linuxfoundationnetworking.org
5g
super
blueprint.
It
is
a
task
force.
It's
a
pro.
It's
a
it's
a
it's
a
project
that
is
extending
an
existing
governance
under
the
under
the
lfn
demo
that
we
did,
but
it's
more
than
the
demo.
B
It's
now
bringing
components
together
from
an
end-to-end
perspective
that
crosses
lf,
networking,
lf
edge,
magma,
cncf
oran
and
a
lot
more
okay.
These
are
just
some
examples
and
what
we're
doing
is
we
are
building
this
blueprint
in
real
time,
so
we
really
encourage
everybody
to
participate
in
this
join
mem.
You
know
as
members
if
you
want
to
influence
this
even
more
under
lf
networking,
but
it
is
an
open,
open
initiative
to
everybody.
So
let
me
walk
you
through
how
magma
is
getting
integrated
into
these
components.
B
So
here's
the
overall
roadmap
that
the
community
has
created
lots
of
details
are
being
worked
in
real
time
because
these
projects
themselves
have
a
roadmap,
so
bringing
all
these
projects
back
together
is
obviously
going
to
be
a
challenge
and-
and
the
reason
we
want
to
show
it
in
an
open
community-
is
so
that
it
can
be
done
under
a
neutral
governance.
And
then
you
know
we'll
have
vendors
system
integrators
end
users
doing
distros
doing
you
know
multiple
things
with
it.
B
Linux
foundation
is
not
in
the
business
of
that,
but
what
we
want
to
do
is
show
a
blueprint
that
can
easily
pull
projects
together
upstream
and
downstream
and
solve
specific
use
cases.
So
here's
how
these
things
use.
Look
the
team's
working
on
this
quarter,
it's
working
on
getting
you
know
the
5g
core
and
some
version
of
mac
integrated
with
a
whole
set
of
components
that
can
bring
an
open
source
core
stack
and
edge
stack
together.
B
We
get
into
the
end-to-end
slicing,
which
brings
not
just
the
core,
but
it
also
brings
a
set
of
commercial
brands
and
from
an
open
source
perspective,
end-to-end
slicing
in
play
and
then
finally,
through
the
q4
time
frame.
This
brings
not
just
the
en
end
to
end
network
for
rand,
but
it
also
opens
up
the
ram
with
oram
sc
software
and
it's
a
fully
disaggregated
open
source
based
5g
stack
so
with
obviously
all
the
use
cases
that
are
required
by
the
end
user.
B
So
let
me
walk
you
through
the
three
steps.
The
first
phase
is
the
following:
we're
going
to
use
emulators
for
the
ram
easy
to
do.
I
mean
easy
to
say
hard
to
do,
but
those
are
sitting
right
there
on
the
left.
You
come
in
and
you
bring
in
you
know:
onap
onboarding
through
a
project
called
openness
plus
anoka,
then
kubernetes
bring
it
all
in
into
magma
magma
orchestrator,
using
the
access
gateway
through
the
obviously
the
n6
and
obviously,
all
the
n
interfaces.
B
What
is
shown
here
on
the
akraino
side
is
icn
and
I'll
have
tina
talk
about
this
in
a
lot
more
detail
on
how
to
do
it.
So
I
won't
go
into
this,
but
that's
kind
of
the
application,
control
and
application
layer
and
then
on
the
bottom.
You
see
the
nfvi
in
the
telco
terms,
right
network
function,
virtualization
infrastructure
layer
which
uses
a
whole
bunch
of
what
is
called
open
source
projects
from
data
plane,
acceleration
to
control
plane
to
to
storage,
etc.
So
that's
kind
of
the
phase.
B
One
phase
two
is
relatively
straightforward,
but
what
you're
doing
is
kind
of
adding
two
main
things
here:
one
is
you're
adding
the
support
for
commercial
ramps
and
then
the
other
thing
you're
doing
is
adding
end-to-end
network
slicing,
which
kind
of
comes
from
the
magma
road
map.
Onap
already
has
support
for
the
network.
Slicing
magma
is
working
on
it
and
I
think
it
comes
together
very
nicely
and
then
finally,
in
phase
three,
you
include
the
oran
community.
So
today
the
over
na1
interfaces
from
oran
to
onap,
already
tested
and
and
released.
B
There
are
other
interfaces
that
need
to
be
worked
out
both
for
non-real-time
rick,
as
well
as
real-time
rig,
but,
more
importantly,
bringing
it
in
such
a
way
that
it
is
a
seamless
end-to-end
use
case
across
these
projects.
So
very
ambitious
to
participate,
it's
part
of
lf
networking's
initiative
and
there's
a
large
community
that
is
working
on
it.
B
C
Thank
you
appit.
This
is
how
equino
are
four
blueprints
available.
Now
we
announced
in
february
24th
so
from
here
you
can
see
see.
There
are
four
blueprints
which
which
are
new
is
indeed
indicated
in
blue.
So
you
can
see
the
industry
iot,
predictive
maintenance
blueprint,
sits
on
the
smart
device
edge
and
it
has
been
integrated.
C
If
and
if
in
flesh,
so
it
supports
for
the
industry
iot
case
like
when
the
temperature
is
up,
it
will
give
indication
an
alarm
to
the
backhand
like
a
gcp
and
the
other
new
one,
the
air
edge
autonomous
vehicle,
the
ivix,
which
support
integrate
the
auto
dot
where
outerwear,
the
auto
sorry,
otherwise,
the
auto
and
the
federated
landing
a
which
has
been
deployed
in
the
financial
technologies
has
been
widely
deployed
by
we
bank,
the
other
one,
the
icm
private
fight.
Glt.
I'm
gonna
talk
about
this
a
lot
and
later
slides.
C
It
has
been
deployed
in
the
cloud
and
in
the
edge
the
public
cloud
edge
interface
here
sitting
above
the
public
cloud
core
part
and
public
cloud
edge,
part
which
has
provided
api's
orchestrations
for
the
telcos
and
hyperscalers
to
work
together
via
pcs
layer
and
the
other
one.
We
have
the
kni
industry
edge,
which
is
a
new
which
is
new
to
support
operator
in
france,
about
their
deployment
for
the
industry,
iot
and
also
the
manufacturing.
C
C
Okay,
this
is
private
lte5gicn.
The
purpose
is
to
create
an
epc
5g
in
a
box
to
enable
enterprises
and
operates
to
deploy
lte
5g.
There
are
we
use
it.
We
use
oss
like
35gc
and
magma,
so
magma
has
been
used
here
and
also
free
by
gc.
You
can
see
the
infrastructure
orchestration
include
ironic,
miter,
3
and
cluster
api
string
could
be
so.
This
is
quite
white
and
also
the
onap
has
been
used
as
orchestration
layer.
C
We
covered
the
network
segments
all
the
way
from
ucpe,
using
kubernetes
on
the
network
edge
number
one
and
cross
the
network
call
which
runs
the
kubernetes
as
the
as
the
e1,
the
epc
5gc
there
and
same
as
edge
number
one
and
the
other
side
of
the
network
is
the
network
engine
number
two.
In
this
case
we
can
support
the
many
industry,
the
manufacturing,
retail
farming
and
mining.
C
C
C
We
have
the
kubernetes
plus
open
openness
with
the
good
infra
orchestration
and
the
magma
sits
on
top
of
it.
For
example,
we
open
this
cnf
number
one
to
have
a
look,
so
we
have
the
magmod
orchestration
orchestrator
on
the
top
and
sitting
on
top
of
the
agw
for
5g,
the
smf
and
amf
and
upf
is
at
the
controller
layer
and
data
plan
layer.
So
it
connects
with
the
other
cn2
cnf
number
two,
with
the
m1
interface
to
the
5g
ue
emulator
and
through
the
n2
interface
to
genome
b
emulator.
C
So
the
n3
is
between
the
gm
genome
b
and
emulator
to
the
upf
directory
and
the
upf
interconnect
with
the
data
network.
So
this
is
runs.
The
bnf
number
one
and
magma
sits
for
the
cnf
number
number
one.
So
the
workflow
is
like
this
number
one.
We
first
installed
the
the
the
kubiaf
kubf
number
one
and
two,
and
then
we
installed
onap
and
encode
as
the
orchestrator.
C
After
that
we
registered
it
could
be
kobe.
Ref
number
two
could
be
ref2
with
the
onap
and
aimco
and
we
onboard
cnf
one
and
two
you
can
see
from
here
and
also
bnf
number
one.
In
this
case
we
can
create
a
network
service
with
cnl
for
vms
and
we
can
deploy
the
network
services
like
what
you
can
think
about
for
the
5g
private
lte
like
manufacturing,
etc,
and
then
we
registered
the
awg
with
the
magma
orchestrator.
C
C
Okay.
Here
we
can
see
the
magma
integration
plan
details
the
magma
awg
5g
early
implementation
available
as
a
vm
like
here
is
a
vnf,
also
the
magma
orchestrator
early
implementation
available
as
a
container.
We
call
it
cnf,
of
course,
and
the
private
lte
5g
icmt,
which
is
our
blueprinting
part
of
ice
and
blueprint
family,
will
orchestrate
these
two
using
onap
the
uen
and
genome.
The
b
emulator
will
also
be
orchestrated
as
a
cnf.
C
Let's
see
the
previous
page
as
a
cnf
number
two,
if
available
in
a
containerized
form,
so
this
is
our
detailed
plan,
so
lfh
and
equinox
community
are
very
excited
to
have
magma
to
join
the
lf
and
collaborate
on
innovative
blueprints
to
provide
these
end-to-end
solutions.
Thank
you
again
for
the
opportunity
to
discuss
this
here
at
the
magma
day.
Thank
you
have
a
good
one.