►
From YouTube: Webinar: Using KubeVirt in telcos
Description
Kubernetes has become the defacto standard for cloud-native architecture. Kubernetes has been primarily built with a strong focus around containers whereas the telco world is still far away from complete migration from VNF (Virtual Network Functions) to CNF (Container-based cloud-native functions). To make Kubernetes useful for telcos, we need the hosting capability of virtual machines inside the PODS. This has been made possible bt the CNCF sandbox project KubeVirt (https://kubevirt.io/).
In this Webinar, we will cover the relevance of KubeVirt for telcos. There will also be a demonstration of using KubeVirt in hosting a windows VM and discuss current limitations and challenges from the telco adoption perspective.
Presenter:
Abhinivesh Jain, Distinguished Member of Technical Staff @Wipro
A
Webinar,
you
are
not
able
to
talk
as
an
attendee.
There
is
a
q,
a
box
at
the
bottom
of
your
screen.
Please
feel
free
to
drop
your
questions
in
there
and
we
will
get
to
as
many
as
we
can.
At
the
end.
This
is
an
official
webinar
of
the
cncf
and,
as
such
is
subject
to
the
cncf
code
of
conduct.
Please
do
not
add
anything
to
the
chat
or
questions
that
would
be
in
violation
of
that
code
of
conduct.
Basically,
please
be
respectful
of
all
your
fellow
participants
and
presenters.
A
B
A
B
All
right
so
about
myself,
I'm
an
author,
speaker
and
blogger.
I'm
an
open
source
contributor.
I
work
primarily
in
a
linux
foundation,
edge
project
called
latino
and
I
will
be
taking
case
study
from
echino
extec
and
I'm
working
as
dmts,
which
is
distinguished
member
of
technical
staff
in
cto
5g
team
in
wipro
all
right.
So
here's
the
agenda
for
today.
B
Okay,
so
the
first
one
is
legacy.
Applications
are
not
going
to
go
away
very
soon.
Right
now,
though,
cloud
native
computing
adoption
is
growing
at
a
very
fast
pace,
but
there
are
situations
like
applications
which
can't
be
containerized,
because
either
there
is
no
source
code
or
maybe
they
are
not
architected
for
containers
and
in
many
cases
they
are
using
some
proprietary
os.
It
could
be
from
telco
vendor
or
from
some
somewhere
else,
or
maybe
some
operating
system,
which
is
not
supported
in
container
world
right.
B
So
this
is
one
of
the
category
of
legacy
application
which
can't
be
containerized,
and
second
category
is
non-replaceable
legacy.
Apps
right.
So,
though,
everyone,
if
if
there
is
a
legacy
app
which
can't
be
categorized,
then
the
next
logical
conclusion
is
that
why
not
replace
it
with
something
modern
right
and
something
which
is
cloud
native
and
and
maybe
the
upgraded
version
of
the
application
and
so
on.
B
But
in
few
cases
there
are
applications
which
can't
be
replaced
either
because
they
are
like
20
years
old,
even
they
are
given
from
a
small
vendor,
which
is
no
more
present
right.
So
there
could
be
several
scenario.
So
the
summary
from
this
slide
is
that
legacy
applications
will
be
there.
I
mean
having
100
cloud
native
world
is
a
kind
of
myth.
B
Now,
second,
challenge
is
about
vnf
right.
So,
though
everyone
so
before
we
get
into
vnf.
Let
me
first
cover
what
is
vnf
and
cnf,
so
it
all
started
from
pnf
right,
which
is
physical
network
function.
So
in
telco
world
you
have
all
kind
of
network
function
right,
some
something
like
firewall
routers.
Those
are
very
commonly
used
network
functions
and
earlier
they
were
present
in
terms
of
applies
right
and
they
were
called
phys
pnf
physical
network
function
right
now
the
challenge
was
pnf
was
they
were
very
difficult
to
scale?
B
So
if
you
want
to
scale
it,
you
have
to
buy
more
appliances,
and
you
have
to
manage
it
individually
right
because
they
they
were
like
all
in
a
box
kind
of
solution
right
and
then
came
vnf,
which
was
virtual
network
function
right
where
the
hardware
and
software
segregation
was
done
right.
So
then,
so,
let's
say,
if
it
is
firewall,
then
firewall
was
given
as
vnf,
which
you
can
run
on
any
of
the
x86
hardware
right,
but
still
it
was
vm
based.
B
So
it
was
virtual
machine
based
and
the
most
commonly
used
open
source
platform
for
dnf
hosting
is
openstack
right
and
now
after
vnf
came
cnf,
which
is
cloud
native
network
function
right
so
or
container
native
network
function.
Some
people
call
it
that
way.
Also
so
in
cnf
what
happened?
I
mean
these
virtual
network
function,
which
were
like
vm
based.
They
were
kind
of
converted
into
container
waste.
B
B
B
Right,
second,
is:
cnf
is
still
evolving,
so,
as
of
today,
it's
not
like
5g
core
is
100
cnf.
There
are
still
some
vnf's
present
there,
and
even
if
we
manage
to
convert
entire
5g
core
into
cnf,
the
4.5
g
or
the
lte
advance
is
going
to
be
there
for
a
decade
or
more
right,
because
5g
the
way
right
now
things
are
happening
right.
You
we
have
3g
and
4g.
Both
and
3g
is
kind
of
getting
phased
out
now,
where
5g
is
already
rolled
out
right.
So
so
what
is
going
to
happen
for
next?
B
Several
years
we
are
going
to
have
both.
So
we
are
going
to
have
lte
advance
as
well
as
5g.
That
means
vnf,
which
were
introduced
in
in
lte
advance,
will
still
be
there
and
we
have
to
manage
vnf
right.
We
cannot
have
cnf
in
lte,
advanced
right
and
last
point
is
that
kubernetes
is
still
adopting
to
telco
specific
requirement.
So
there
is
a
in
cncf.
Also
we
have
a
dedicated
telecom
user
group
right,
which
is
focusing
on
this
kind
of
work
right.
B
So
the
key
message
here
is
that
having
a
world
where
only
cnfs
are
present,
it's
not
going
to
happen
very
soon
right.
There
will
be
vnfs
and
cnn
both
now.
I
have
briefly
covered
this
slide,
but
the
other
message
from
this
slide
is
that,
right
now
there
is
no
single
hosting
platform
for
vnf
and
cnn
both
right.
So
if
I
want
to
host
vnfs,
I
have
to
go
with
openstack
right
and
if
I
have
to
host
cnf,
of
course
I
mean
the
multiple
option,
I'm
just
covering
open
source
based
option.
B
B
In
other
words,
what
what
we
are
saying
is
can
kubernetes
host
my
containers
and
my
virtual
machine
inside
containers.
Right
so
I
mean
it's
like
reversing
the
way
things
were
done
so
earlier
you
were
running
a
container
on
top
of
virtual
machine.
Now
we
want
a
virtual
machine
to
run
inside
containers,
okay,
coming
to
next
challenge
in
terms
of
mec
platform.
So
right
now
we
don't
have
single
mec
platform.
Mvc
stands
for
multi-access
edge
computing
right,
so
in
mec
you
have
all
kind
of
scenarios
right.
B
There
might
be
some
cnf
also
from
private
network
perspective
right,
so
mec
is
going
to
have
a
mix
of
all
so
mec
will
mvc
platform
will
have
vnf,
hosted,
cnf,
hosted
and
some
third-party
applications,
which
are
either
container
based
or
vm
based
right
now
there
is
no
native
support
for
virtual
machine
hosting
in
kubernetes.
Everyone
knows
that
right.
So
kubernetes
is
container
orchestration
platform.
It
was
kind
of
designed
and
developed
for
that
purpose.
B
Only
right
and
now,
if
we
want
to
fix
these
kind
of
scenarios,
where
we
want
capabilities
for
vm
and
container
both
so
vm
hosting,
can
be
done
with
openstack,
dcn
kind
of
architecture
and
container
hosting
can
be
done
with
kubernetes,
but
the
problem
is:
if
I
go
with
to
msc
platform
right,
then
I
am
kind
of
increasing
complexity
for
my
msc
platform
management.
I'm
also
increasing
the
cost
right,
so
it
the
real
question
is:
can
we
have
just
one
mvc
platform
that
will
satisfy
both
the
needs?
B
B
It
helps
in
marrying
virtual
machines
and
container
world,
and
it
allows
us
to
run
vms
inside
a
pod
okay.
So
the
the
major
difference
here
is
what
we
are
saying
that
it's
okay,
if
we
are
not
able
to
get
rid
of
vm,
because
everyone
wants
to
get
rid
of
vm
and
come
to
container
world,
but
it's
okay.
If
we
can't
do
that,
what
we
want
to
do
here
in
cubot
is
bring
that
vm
as
vm.
Okay.
B
So
let's
say:
if
there
is
a
one
windows,
virtual
machine,
I
want
to
run
windows
virtual
machine
inside
my
kubernetes
cluster.
As
is
I
mean
I
still
want
to
do
remote,
desktop
to
virtual
machine
and
do
all
the
operation
the
way
I'm
doing
right
now
right,
but
I
want
the
flexibility
and
benefit
of
keyboards
there
right
scalability
benefits
and
single
management
benefit.
B
So
that's
the
objective
here
in
qubit
and
qubit
helps
in
eventual
containerization.
What
is
easy,
so
eventual
containerization
is
all
about
cloud
native
adoption
stages
right.
So
when
some
organization
is
on
their
cloud
native
adoption
journey,
there
will
be,
let's
say,
percentage
adoption
where
if
they
have
100
application,
they
will
containerized,
maybe
20
application
in
the
beginning.
80
will
still
run
in
non-container
world
and
so.
B
B
What
happens
in
this
journey
that
you
have
your
virtual
machine
hosting
platform
like
hypervisor
based
platform,
and
you
have
your
container
platform
like
kubernetes
in
parallel
right,
both
exist
in
parallel,
so
the
easier
way
is
that
we
can
move
vm
as
vms.
While
some
company
is
adopting
this
eventual
containerization
or
cloud
native
journey,
they
can
on
the
day
one
what
they
can
do.
They
can
simply
migrate
all
the
vms
right,
two
kubernetes
right
and
and
run
them
as
vm,
okay
and
then
slowly
pick
up.
B
Maybe
one
application
at
a
time
right
and
then
try
to
convert
that
into
micro
services,
try
to
convert
those
into
containers
and
then
get
rid
of
that
vm
and
so
on
right.
So
that
way,
it's
it's
possible
to
remove
vm
hosting
platform,
even
before
you're
100
there
right.
So
that's
one
of
the
key
benefit
of
this
concept.
B
B
Now,
let's
see
how
kubert
runs
so
I'm
not
getting
into
kubert
architecture
or
kubert
component
details
and
all
I
will.
I
just
want
to
show
this
from
a
real
action
perspective
right.
So
so
this
is
a
small
case
study
that
is
based
on
akuno
edge
stack
project
right,
which
is
called
kni
kubernetes
native
infrastructure
based
edge
stack
in
that
kni
edge
stack.
We
have
cubot
integrated
right,
so
the
thing
that
is
mentioned
here
is
open
shift
4.2,
but
openshift
4.2
is
not
mandatory.
B
You
can
use
open
shift
open
source
version,
which
is
called
okd
right
and
that
will
also
give
the
same
result.
So
objective
here
is
to
run
windows.
Let's
say:
2012
iso
image
right.
We
want
to
run
windows,
machine
on
kubernetes
platform
right
and
we
want
to
see
like
if
I
have
a
vm
based
right.
How
do
I
run
that
vm
based
application
inside
kubernetes
and
why
I
picked
windows,
because
windows
vm
is
much
more
complex
than
linux?
One.
This
one
is
quite
straightforward,
all
right.
So
what
are
the
prerequisites
here?
B
B
Okay,
so
when
someone
wants
to
use
qubit,
it
comes
as
an
operator.
Okay,
but
cuberd
alone
doesn't
really
work.
I
mean
you
have
to
have
other
surrounding
systems
for
qubit.
Okay,
like
you
need
to
have
cdi,
and
you
need
to
have
word
ctl.
You
need
to
have
vnc,
so
cuber
does
only
one
thing
right
it.
It
helps
in
getting
your
vm
kind
of
provision
inside
part
right,
but
to
make
that
thing
happen,
you
need
to
have
your
let's
say.
B
Linux
image
to
be
there
right,
which
will
be
used
for
installation
to
get
that
part.
We
use
two
things.
One
is
word
cdl,
another
one
is
cdi
which
is
container
data
import,
okay
and
then
there
are
yaml
file.
Given
there
are
so
many
sample
yaml
files
given
in
cubot
website,
and
you
can
to
start
with.
You
can
use
any
of
those
yaml
file
related
to
your
use
case,
okay
and
then
modify
it
according
to
your
needs
and
from
a
space
perspective,
you
need
to
create
a
persistent
volume
right
which
will
hold
the
windows
installation.
B
So
the
way
it
happens
is
I
mean
just
for
a
visualization
perspective,
see
when
you
get
a
new
laptop
and
you
want
to
install
your
operating
system.
What
do
you
do
you
plug
your
pen
drive
or
cd
or
dvd
inside
it?
And
then
you
start
installation
right.
It
just
boots
the
server,
and
then
you
do
the
installation.
You
do
some
parameter
configuration
and
at
the
end
you
will
have
your
windows
up
and
ready.
B
The
same
thing
is
done
here
right
now
in
this
case,
what
we
want.
We
want
that
iso
image
to
be
available.
First
right
as
some
drive
right
drive
in
windows
world
and
that
iso
mode
should
be
bootable,
it
should
run
on
its
own
when,
when
we
want
to
launch
that
instance,
it
should
run,
and
then
we
will
do
the
configuration
using
vnc
viewer,
vnc
vr
is
one
common
utility
that
all
of
us
know
about
right
and
after
that
you
installed
windows.
So
now
the
question
is
iso
based.
B
Installation
is
something
where
you
have
to
do
some
everything
from
scratch.
Right,
so
is
this?
The
only
option
for
vm
hosting
answer
is
no.
You
can
as
well
migrate
your
existing
vm
image,
which
might
be
in
format
like
qco2
format
or
some
other
format.
That
is
also
supported
right,
so
you
can
bring
your
cuco
to
image
here
and
then
you
don't
need
to
do
any
installation.
It
will
simply
it's
like
cloning
right,
so
that
is
also
supported.
B
So
I've
taken
a
bit
complicated
case
and
in
this
particular
case
I
am
also
using
chef
for
my
storage
and
rook
operator
is
also
used.
Okay,
so
chef
rook
will
also
be
in
picture
now.
Let's
see
how
we
do
it.
So,
as
I
mentioned
before,
there
will
be
eight
steps.
First
step
is
configuring.
The
cdi
right
cdi
is
containerized
data
importer.
So
this
guy
does
the
image
report?
Okay.
B
B
B
Moving
to
next
one
now
we
are
going
to
configure
keyboard
right
so
for
qubit
configuration
I
have
taken
version
26.
So
whatever
is
the
latest
version
when
you
are
doing
the
installation,
you
can
pick
the
latest
version
at
that
time.
So
first
we
create
one
name
space
right.
So
all
these
commands
are
being
executed
inside
your
kubernetes
cluster
right,
so
first
and
I'm
showing
oc
apply
now.
If
you're
running
it
on
kubernetes,
you
can
simply
replace
oc
with
cube
ctrl.
B
So
you
say:
cube
ctl,
apply,
dash,
f
and
give
your
keyboard
operator
file,
location,
right
and
keyboard,
cr,
location
right
and
if
you're
running
this
on
open
shift
or
okd,
then
you
have
to
run
this
security
context
file.
Also
right
and
again,
if
you're
running
root
chef,
then
you
have
to
apply
one
more
file.
Okay,
now
last
two
steps
are
not
applicable.
If
you're
not
using,
let's
say
chef,
you
might
be
using
host
path
or
something
else
and
the
if
you're,
not
using
openshift,
then
obviously,
security
contacts
related
setting
is
also
not
required.
B
B
A
keyword
website
has
word
ctl
utility
right,
so
you
take
the
same
version
which
you
have
taken
for
kubert
all
right,
and
this
is
very
much
the
standard
process
that
you
follow
right,
just
download
it
and
change
the
execution
mode
to
I
mean
just
to
plus
x
and
it
will
be
executable.
Okay.
Now,
before
you
run
the
image
upload
command,
which
is
word
ctl
image
upload,
you
need
to
have
the
upload
proxy
url.
Okay.
Now,
how
do
you
get
that
upload
proxy
url?
B
B
B
So
I'm
just
giving
pvc
name
here
which
is
iso,
win
2k12
pvc,
then
we
say
access
mode,
read
only
money,
then
we
give
some
pvc
size,
25
gb
for
being
on
higher
side,
but
even
15
gb
is
good
enough,
because
typically
windows
image
is
around
10
to
12
gb,
so
15
gb
is
good
and
then
you
give
the
image
path
wherever
it
is
present
right.
So
in
my
case
it
was
present
in
temp
folder.
B
So
I
gave
that
path
and
then
you
say:
insecure,
flag,
okay
and
then
wait
second
for
number
of
seconds
right.
Wait!
Second,
is
required
so
that
it
does
not
time
out
because
sometimes
based
on
image
sizes.
Unlike
linux
windows,
image
sizes
are
huge,
so
let's
say
14
gb
10
gb.
These
kind
of
image
upload
runs
into
several
minutes,
so
by
default.
This
timeout
is,
I
believe,
60
seconds.
B
So
if
you
don't
increase
it
after
60
seconds,
it
will
simply
time
out
so
just
increase
that
to
some
reasonable
number,
maybe
five
minutes
six,
ten
minutes,
whatever
okay.
So
how
does
this
command
look?
Like
I
mean
what
is
the
output
we
get
so
once
you
run
this
command,
you
get
this
kind
of
output.
It
says
using
existing
pvc
and
waiting
for
pvc
upload
port
to
be
ready
and
then
uploading
data.
B
So
the
iso
image
without
extract
was
like
4.17
gb,
so
it
uploaded
4.17
gb
in
one
minute,
13
seconds,
okay
and
what
it
does
internally
is.
It
will
create
two
pvcs.
One
will
be
with
the
name
that
you
give
wind,
2k12,
pvc
or
whatever
name
you
have
given,
and
one
will
be
with
dash
scratch.
So
scratch
is
like
temporary
space
right,
so
it
copies
actually
on
scratch,
folder
first
and
then
from
there
it
copies
to
main
folder,
and
then
scratch
is
removed.
B
Okay,
so
once
this
part
is
done,
your
image
is
uploaded
right.
Where
is
it
uploaded?
It
is
uploaded
to
a
pod
now
coming
to
the
pvc
creation.
So
if
you
are
using
rook
right
with
ceph,
then
you
have
to
create
pvc
like
this
right
and
which
storage
class
to
use
which
I'm
highlighting
in
red
that
you
can
find
out
from
cube,
ctl,
get
storage
or
oc,
get
storage
right
and
give
that
appropriate
storage
file.
Storage
class.
B
B
B
B
So
this
is,
I
believe,
some
250
mb
to
300
mb
file
right,
so
you
get
this
file,
and
after
this
you
run,
as
I
said
in
the
beginning,
you
can
download
any
of
the
windows
example
file
just
to
play
with
it,
just
just
to
see
how
it
is
really
working,
and
so
I
have
taken
a
sample
file
from
cubot
github
link,
okay
and
then
I'm
just
running
that
yaml
file
and
it
says
bmi
windows
created
now
what
happens
so?
It
has
created
a
vm,
but
it
is
not
up.
B
Okay,
it
is
in
shutdown
mode.
So
if
you
run
a
command
cube,
ct
will
get
vms
oc,
get
vms.
You,
you
will
say
running
equal
to
false
right,
so
to
make
it
I
mean
to
so
so.
What
next
step
is
you
need
to
start
the
vm
right,
so
you
run
a
command.
What
ctl?
What
what
ctl
is
your
command
line?
Interface
for
all
kind
of
operations?
Okay,
so
to
start
the
vm
simply
say,
start
vm
and
give
your
vm
name
right.
B
Vm
name
is
defined
inside
that
yaml
file,
and
then
it
will
say
it
is
scheduled
to
start
it
will
take
some
time
and
then,
after
some
time,
if
you
run
oc
get
vm,
you
will
see
your
sample
vm
running
okay,
and
then
you
will
see
your
I
mean
when
you
do
oc
get
vmi
vm
instance
that
will
be
hosted
inside
some
pod
right.
So
when
you
say
oc
get
vmi,
it
says
sample
vm,
five
minutes
it's
running
from
five
minutes.
B
B
So
now
we
will
connect
to
that
vm
using
vnc
viewer.
So
you
run
this
command
word
ctl
vnc
and
give
your
vm
name
right.
You
need
to
run
it
from
any
x
terminal
like
mobile,
xterm
or
any
other
software
right
so
and
if
you
get
some
error
like
remote
viewer
not
found,
then
obviously
you
need
a
word
to
your
installation.
B
So
after
this,
obviously
you
know
all
the
steps
you
just
do
next
and
start
giving
different
different
steps.
Different
configuration
okay,
now
here
since
you're
running
inside
pod
and
all
you
your
keys,
will
not
work
right.
So
you
have
to
use
all
these
tabs
spacebar
and
the
traditional
old
way.
You
have
to
do
this,
okay
and
once
you're
done,
it
will
restart
your
vm
and
there
is
a
nice
video
also
on
keyboard
website.
I
have
given
the
link.
B
You
can
have
a
look
at
that
video
that
video
talks
about
how
to
use
those
word
io
drivers
which
one
is
supports
and
how
to
select
the
right
to
a
tio
driver.
So
all
that
is
given
in
this
website,
you
can
refer
to
that
and
after
successful
installation
you
will
see
screen
similar
to
below
right.
Of
course,
you
will
not
see
congratulation
message,
but
yeah.
You
will
see
the
familiar
windows
screen
and
you
can
access
it.
The
way
you
wanted
to
where,
where
you
are
used
to
use
windows
10.
B
Now,
let's
learn
apart
from
this
particular
setup,
one
that
putting
vm
inside
a
pod
results
in
nested
virtualization.
In
fact
you
have
to
enable
nested
virtualization,
then
only
it
works
right.
Hence
it
has
some
performance.
Overhead
right
and
kuber
team
is
working
on
improving
that
part,
and
there
are
so
many
features
which
are
work
in
progress
like
in
traditional
vmworld
right
your
you
can
easily
change
your
cpu
memory
right
on
the
fly,
but
here
it
is
not
allowed
till
now
right
and
next
point.
B
Okay,
and
to
fix
that
I
have
already
shown
we
need
to
run
one
script
which
is
given,
and
then
there
was
some
bug
related
to
vnc,
due
to
which,
whenever
I
was
launching
the
vm,
it
was
kind
of
coming
and
going
right
away.
I
mean
so.
You
will
see
that
there
are
some
windows
machine
is
there,
but
you
will
not
see
that
for
more
than
a
few
seconds,
so
that
was
some
bug
in
cubert
and
upgrading
cubot
helped
in
fixing
this.
B
So
upgrading
keyword
is
very
simple
job,
very
straightforward,
single
command
job,
so
upgraded
to
latest
version,
and
that
issue
is
gone.
In
fact,
that's
why
I
suggest
to
always
use
the
latest
version.
Okay-
and
I
mean
sometime,
this
cluster
operator
also
gets
degraded
authentication
operator
and-
and
you
just
need
to
fix
that,
so
that
you
don't
get
this
no
root
to
host
error.
Okay,
these
are
common
challenges,
some
of
the
key
takeaways,
so
cubot.
As
you
know,
it's
maturing
at
very
fast
pace.
B
So
obviously,
a
lot
of
changes
happening
things
are
improving
day
by
day.
Some
issues
are
expected.
That
is
fine,
because
still
it
is
not
graduated,
it
is
still
a
sandbox
project,
but
the
good
part
about
cuboid
is-
and
that
is
one
thing
I
would
suggest
everyone
to
join
cubot
slack
channel
and
there
we
have
a
lot
of
people
who
are
there
to
respond
to
your
queries
almost
immediately
right
and
I'm
also.
B
I
also
want
to
recommend
this
examples
website
right,
which
has
so
many
examples
that
you
might
want
to
try
right.
So,
let's
say
three
different:
linux
version
hosting
or
five
different
windows,
vm
hosting
options,
and
also
all
those
examples
are
already
there
very
good
documentation
and
very
good
selection.
B
Now
the
key
question
is
from
telco
perspective,
see
in
my
previous
case
study.
If
you
were
having,
let's
say
a
cucumber
right.
In
fact,
cubot
has
a
vm
migration
option.
Also
right
it
has
some
condition,
but
yeah
it
works.
Okay.
So
you
don't
need
to
really
do
iso
based
installation.
You
can
do
vm
migration,
okay
and
from
telco
perspective
there
are
some
features
which
are
listed
on
the
left
right.
B
You
see
here
so
you
need
all
these
features
to
be
available
so
that
we
can
call
it
telco
ready,
so
huge
page
support
so
since
cubot
runs
on
top
of
kubernetes,
so
some
of
it
are
related
to
kubernetes
itself
right.
So
whether
kubernetes
support
that
at
the
first
place.
If
yes,
then,
whether
the
same
thing
is
now
extended
till
cuberd
or
not
right,
like
sra
sr,
iov
support
right.
So
it
was
there
in
kubernetes
and
now.
B
Cubot
also
supports
sri
uv
right
with
some
way,
and
I
want
to
mention
one
more
thing
that
in
this
case
study
you
have
seen,
I
was
doing
a
lot
of
steps
like
cdi
operator
and
word
ctl
and
all
that.
So
there
is
a
work
going
on
in
parallel,
which
is
called
opinionated
keyword
right
where
hyper
converge
operator
hco
is
created,
which
is
like
operator
of
operators
right
which
will
take
care
of
all
these
operators.
B
Okay,
so
you
don't
need
to
really
worry
about
setting
up
four
different
operators
and
then
your
final
thing
comes
up
right,
so
that
opinionated
cubot
is
one
thing
you
can
search
for
and
get
more
details
all
right.
So,
coming
back
to
is
cuber
telco
ready
right,
so
huge
base
support
it
is
there.
Sri
ov
support
is
also
there.
Cpu
pinning
newmar
support
yes
and
multi
interface
support
using
multis.
B
It
is
there
live
migration
work
in
progress,
kind
of
thing
where
it
is
supported
with
some
condition.
Hot
plug
hot
plug
is
the
feature
where
you
change
your
cpu
or
memory
on
the
fly
right.
So
that
is
not
there
right
now
and
then
another
important
feature
that
we
are
so
habitual
in
virtual
machine
world
right
in
hypervisor
world,
which
is
fencing
right
where,
if
a
host,
let's
say
esxi
host
goes
down,
then
your
virtual
machine
automatically
moves
to
other
available
esxios
right
so
that
node
failure.
B
Let's
say
in
this
case,
if
my
virtual
machine
is
running
on
worker
node,
one
right
and
if
worker
node
one
goes
down,
what
happens
to
my
virtual
machine,
which
is
running
inside
a
pod?
Will
it
automatically
go
to
let's
say
worker
node
two
and
run
automatically?
The
way
pod
runs
right,
in
fact,
expectation,
is
that
it
should
right
and
that's
where
the
kubernetes
benefit
comes
into
picture,
so
it
is
partially
supported
now
as
of
today
and
coming
to
next
feature,
which
is
arm
64
support.
B
So
it
is
about
running
it
on
running
qubit
on
that's
a
raspberry
pi
kind
of
devices,
so
that
is
not
supported
as
of
now
and
the
last
one
is
gpu
and
fpga
support.
So
this
is
also
work
in
progress,
and
I
think
this
will
be
the
feature
which
will
come
up
very
soon,
maybe
in
next
few
weeks
or
very
soon.
Actually,
so
I
think
it
is
in
final
testing
phases
and
also
gpu
and
fpga
support
will
come
okay,
so
that
shows
the
cuberd
readiness
from
telco
perspective.
A
B
Okay,
so
see,
msc
is
used
primarily
for
two
purposes.
Right,
one
is
for
hosting
your
applications
right,
but
in
certain
cases
one
of
the
form
of
mac
could
be
that
you
want
to
have
your
private
network
deployed
right
and
in
let's
say,
private
5g
deployment.
There
are
three
or
four
different
deployment
architectures
in
private
5g,
where
you
can
have
all
the
setup
everything
running
at
the
customer
premise
or
you
can
have
something
running
at
far
edge
and
that's
where
the
edge
coming
into
picture
right.
B
So
you
can
have
maybe
your
towers
and
all
set
up
in
customer
premise,
but
your
the
control
plane
running
from
far
edge,
not
your
core
data
center
forage
right.
So
in
those
kind
of
scenarios
you
will
have
and
and
of
course
that
core,
which
is
running
at
far
edge
to
cater
to
multiple
private
networks,
will
be
like
a
core
data
center
right.
But
it
is
outside
your
core
data
center.
B
A
B
A
B
Okay,
so
the
simple
example
could
be
a
firewall
right:
f5,
not
top
five.
Sorry,
any
firewall
follow
aldo
firewall
or
some
firewall
so
that
firewall
in
older
days
used
to
be
appliance
right.
You
get
a
device
right
which
is
kind
of
black
box.
You
don't
know
what
operating
system
is
running
there.
Mostly,
it
is
some
proprietary
operating
system
and-
and
you
are
running
some
software,
of
course,
which
is
doing
this
firewall
job,
and
there
is
this
box
which
you
just
plug
into
your
network,
and
you
start
using
it.
B
B
There
are
so
many
network
function
right
so
so
earlier
there
were
physical
network
function,
pnf
right
and
then
telco
world
decided
that
it
is
not
good
to
be
dependent
on
appliances
right,
because
the
scalability
is
not
possible
there.
So
why
not
move
hardware
separately
and
software
separately
right?
So
then
what
they
did?
B
Vnf
came
virtual
network
function
where
they
accepted
the
software
out
of
it,
okay,
and
that
software
was
then
given,
as
let's
say,
ova
file
in
vmware
world
or
some
image
which
you
can
import
in
your
hypervisor
right
and
you
have
your
file
running.
Let's
say
pf
sends
firewall,
it's
a
it's
a
vnf
which
is
open
source.
So
now
that
pf
sense
firewall
is
not
dependent
on
any
specific
appliance
right.
You
can
run
it
on
your
laptop,
also
right.
B
So
as
long
as
you
have,
of
course,
you
need
to
meet
the
requirement
of
network
because,
because
there
is
heavy
throughput
requirement
and
all
but
then
the
the
hardware
dependency
is
removed,
then
came
cnf,
so
cnf
and
vnf
is
something
that
we
can
easily
understand.
So
cnf
is
a
container
native
network
function
right
so
where,
instead
of
using
virtual
machine
based
image,
why
not
have
some
docker
images
right?
B
So
why
not
use
containers
and
deploy
it
inside
kubernetes
or
some
container
orchestration
platform,
so
that
is
cnf
so
same
firewall,
which
was
coming
as
an
appliance
is
called
pnf
when
it
started
coming
as
a
software
image
again
image,
not
something
that
you
do
next
next
install,
not
that
one
but
the
image.
Okay,
that
is
enough
and
then
the
same
thing
when
comes
as
a
docker
image.
That
is
cnf,
so
hope
that
answers
long
answer.
Sorry.
A
B
Oh,
that's
a
very
good
question,
so
right
now
the
biggest
hurdle
I
mean.
I
have
already
shown
the
keyboard
readiness
from
telco
perspective
and
from
telco
perspective,
the
biggest
hurdle
is
performance
right.
So
if
you
have
worked
on
telco
area,
you
will
know
that
there
is
a
requirement
of
faster
practice,
processing
right
and
there.
So
you
are
already
doing
nested
virtualization
right.
So
you
are
running.
B
Let's
say
there
might
be
cube
on
cube
kind
of
scenario,
also
right
where
kubernetes
itself
is
running
on
kubert
right,
so
in
nested
virtualization,
your
performance
is
affected.
So
so,
in
this
case,
I
think
the
biggest
hurdle
is
getting
the
telco
great
performance
right
and
that's
where
the
major
work
is
happening,
how
to
get
the
telco
great
performance,
and
I
would
like
to
highlight
that
in
june
end
there
was
a
nice
webinar
in
cncf
on
high
packet
process,
faster
packet
processing
in
cupert.
B
B
B
Absolutely
absolutely,
in
fact,
that
is
the
whole
purpose
that
you
deploy.
Cnf
cnf
deployment
is
straightforward.
Right
you
get
the
docker
image
from
wherever
you
can
get
and
just
deploy
that
docker
image
using
your
kubernetes
way.
Now,
then
you
get
vnf
and
vnf
deployment
can
be
done
using
cubot.
So
then,
your
vnf
and
cnn
both
will
be
hosted
in
same
kts,
cluster.
B
Yes,
soviet
based
migration
is
supported
yeah,
so
we
can
do.
Let's
say
one
image
is
running
on
your
hypervisor
and
there
are
two
three
formats
that
are
supported.
I
need
to
check
the
documentation.
I
don't
want
to
make
generic
comment
here,
but
qco2
image
is
certainly
supported
and
iso
image
is
supported.
B
A
B
Okay,
so
in
image
upload
I
am,
I
was
using
iso
image
which
you
can
get
from
windows.
Microsoft
website
the
normal
iso
file,
but
so
it
is
not
docker
image
and
not
over
nothing.
It
is
iso
image,
but
iso
is
not
the
limitation.
As
I
said,
you
can
have
a
qco2
image
also
or
you
can
in
fact
migrate.
Your
vm,
as
is
from
your
source,
and
that
image
is
loaded
there.
A
B
No,
no
so
in
fact,
this
multi-cni
right,
which
is
used
for
multiple
interface
support
and
which
is
one
of
the
requirement
in
turkog,
which
is
same
I
mean
multicni,
is
multus
network
plugin
is
used,
so
there's
no
separate
plugin
for
windows
or
linux.
In
fact,
most
of
the
things
that
kubernetes
remains
kubernetes
level
remains
same.
It
runs
on
top
of
kubernetes.
B
B
So
if
that
is
the
question,
then
answer,
is
you
just
go
with
your
source
side
setup
right?
So
if
your
source
has
let's
say
8gb
memory
and
whatever
eight
core
cpu,
then
you
can
use
lgbt
memory
and
exclusive
here
and
obviously
it
looks
very
much
higher
on
higher
side
from
container
perspective
right.
But
that
is
how
these
vm
runs
right.
They
they
are
more.
A
Okay-
and
we
got
your
question
mark
in
the
chat
and
also
in
the
q
a
here-
it
says
you
mentioned
nested
virtualization,
a
pod
is
not
virtualization-
is
simply
a
set
of
namespace
that
constrain
visibility
of
resources
combined
with
c
groups
which
gate
resource
allocation.
You
have
pods
and
containers
linux
processes.
Where
does
nested
virtualization
come
into
play?
Are
you
assuming
that
the
pods
are
actually
hosted
by
the
vms.
B
So
nested
virtualization
comes
when
you
get
your
vm
running
inside
pod
because
for
running
vm
you
need
kvm
kind
of
thing
right.
So
cubot
also
relies
on
kvm,
so
kvm
liberty,
everything
is
there.
Those
demons
run
inside
port
for
every
single
vmi
instance.
You
will
have
your
kvm
instance
also,
and
that
requires
one
nested
virtualization
parameter
to
be
enabled.
A
B
Okay,
so
one
of
the
performance
thing
is
a
faster
packet
processing
right,
so
sri
ov
support
or
huge
page
support.
All
these
are
steps
towards
getting
into
that
stage
where
we
get
telco
grade
career
grade
performance
right,
so
sra,
ov
support
also
helps
in
that.
But,
since
sorry,
since
you
are
not
running
it
directly,
the
way
you
are
running
it
in
bare
metal
and
all
you're
running
it
through,
I
mean
you're
passing
through
kubernetes
right.
So
that's
why
it
is
not.
It
is
having
those
performance
issues.
B
B
They
can
be
executed
right
because
performance
is
not
the
criteria
all
the
time
right
in
all
kind
of
so
it's
not
telco
is
not
all
about
faster
packet
processing.
There
are
telco
applications
or
mec
application
which
which
do
not
require
faster
profit
processing
that
that
part
is
already
done
by
upf
and
all
so
yeah.
A
B
Okay,
so
I
would
say
for
so
two
parts
to
this
question:
modern
software's
required,
so
I
would
say
just
look
into
cube,
documentation
or
look
into
github
page
for
opinionated
keyboard,
where
you
don't
really
need
to
worry
about
cdi
and
word
ctrl
and
everything,
because
those
are
already
taken
care.
Those
are
already
merged
and
you
can
do
that
very
easily.
This
installation
part
and.
B
A
A
Just
for
folks,
we
can
display
that
last
year,
perfect
awesome
so
feel
free
to
connect
offline
here
with
abi
on
cube
vert,
I'm
sure
he
would
love
to
answer
more
of
your
questions
than
I
know
there
were
a
lot
we
tried
to
get
to
as
many
as
we
could
today
a
friendly
reminder
that
the
recording
and
the
slides
will
be
posted
later
today
to
the
cncf
webinars
page:
that's
cncf,
dot,
io
webinars.
We
hope
to
see
you
at
a
future
cncf
webinar
and
thanks
again,
everyone
have
a
great
day.