►
From YouTube: KubeVirt community meeting 2020-12-02
Description
Recording of the KubeVirt Community meeting held on 2020-12-02 at 16:00 CET
A
C
B
All
right
the
link
for
the
the
docs
in
the
the
community
meetings,
so
we
talked
a
little
bit
about
this.
Last
week
we
had
a
number
of
discussion
items,
so
I
just
got
three
three
topics
in
here,
but
we
don't
need
to
adhere
to
those
specifically.
Those
are
just
three
that
I
know
that
some
changes
that
I
made,
but
there's
been
some
discussion
on
the
mailing
list
as
well,
and
we
can
cover
that
too.
B
All
right
so
I'll
go
to
the
doc
here
and
just
kind
of
go
over
one
of
the
first
items
to
kind
of
like
introduce
this
again
like
talk
a
little
bit
about
like
use
cases,
goals
and
things
like
that,
and
so
the
first
thing
is
one
of
the
things
like
that
I
want
to
accomplish.
With
this
proposal
I
kind
of
titled
it
I've
kind
of
tried
to
sum
it
up
here
like
offline
virtual
machine
migration.
B
So
essentially
the
idea
that
I
can
take
a
virtual
machine.
I
can
sort
of
like
put
it
aside.
I
can
save
it.
I
can
save
its
ram.
I
can
save
everything
associated
with
that
virtual
machine.
Take
its
execution,
take
it
down
and
then
at
some
point
later
on,
I
can
then
bring
it
back
up
and
start
where
exactly
where
I
was
and
continue
off
with
whatever
I
was
doing,
I
think
offline
virtual
machine
migration
is
kind
of
the
term
that
I've
seen
use.
So
I
figured
I'd
use
it
here.
B
It
seems
appropriate
essentially
taking
that
machine
down
and
moving
it
somewhere
else
and
using
it.
So
now
the
use
cases
kind
of
generally
go
along
with
this.
The
idea
that
an
administrator
can
take
a
misbehaving
virtual
machine
and
save
it
and
investigate
it
at
a
later
date.
Maybe
in
an
environment,
that's
more
secure,
doesn't
have
internet
access
and
do
some
sort
of
debugging
there
and
making
sure
or
figure
out
what's
wrong.
B
B
I
have
a
few
definitions
terms
here,
since
I
think
there's
a
lot
of
there's
a
ton
of
terms
associated
with
this
and
from
what
I
could
tell
there's
a
lot
of
these
terms
in
different
definitions
based
on
platforms
and
hypervisors
and
all
sorts
of
things.
So
I
kind
of
define
that
here
just
so
that
we
have
a
consistent
understanding
and
kind
of
what
I'm
talking
about
was
when
I
say
use
some
of
these
terms.
Pause,
suspend
keyword,
has
pause
so
essentially
temporarily
putting
machine
on
hold
no
cpu
network
or
disk
activity.
B
D
B
B
Yeah
so
I'd
say
I
even
kind
of
yeah,
so
I
guess
you
could
say
like
for
both.
That
would
be
the
case.
That's
fine!
I
actually
think
this
does
that,
like
I,
I
was
looking
at
this
like
when
I've
done
some
testing
in
this.
I'm
I'm
pretty
sure
that
this
command
delivered
actually
does
a
pause
and
then
does
a
save
just
whether
or
not
what
happens
afterwards
and
that's
kind
of.
B
D
D
So
you
just
meant
that
when
you
go
down
to
the
acronyms
again
yeah
a
little
bit
you're
saying
is
non-gold
create
an
api
for
vitamin
safe
flex.
This
is
just
you
mean
you
don't
want
to
say.
Is
you
want
it?
Don't
want
to
implement,
live
migration,
a
live
snapshot,
I
guess
just
to
save
operations.
Degree,
I'm
just
a
little
bit.
Maybe
I'm
asking
the
questions
too
early
and
you
want
to
go
more
into,
but
maybe
I'll
come
back
to
that
later.
Just
go
on
and
explain
your
stuff.
Sorry
for
drafting
too
early.
Okay.
E
D
I
guess
it
makes
sense
from
the
well,
I
it
depends
the
live
snapshot.
I
guess
this
only
even
goes
as
far
as
you
know.
If
the
guest
agent
is
installed,
you
can
really
do
live
snapshot
with
pretty
much
no
visible
down
time
right,
so
live
snapshot.
Snapshot
is
much
more
complicated,
so
I
guess
in
general
it
makes
sense
to
say
that
this
does
not
want
to
implement
it.
I
guess.
B
Yeah
I
like
I
get
like
the
the
way.
The
way
I'm
approaching
is
that,
like
a
way
I
look
at,
is
that
the
sort
of
the
end
result
like
is
the
virtual
machine
running
yes
or
no,
and
I
don't
want
to
end
up
like
what
I
don't
want
to
implement
here
is
where,
after
I
do
this
save
or
whatever
snapshot,
we
end
up
with
a
live
virtual
machine,
a
running
virtual
machine.
That's
not
quite
what
I'm
after.
I
think.
B
E
Think
from
our
standpoint,
if
we're
looking
at
actually
getting
this
thing
implemented,
we
actually
have
to
understand
both
because
it's
something
where
we're
going
to
approach
live
snapshots
at
some
point,
and
this
is
unfortunate-
it's
overlapping.
I
understand
that
you
don't
really
want
to
to
implement
necessarily
the
use
case
where
it's
running
afterwards,
but
we
at
least
have
to
have
understanding
of
how
that's
done
and
how
this
interact
like
how
these
things
are
related,
at
least.
Does
that
make
sense
like.
B
Yeah,
okay,
I
I
understand.
Okay,
I
understand
you
guys
are
saying
okay,
so
I
the
reason.
So
let
me
tell
you
my
motivation.
I
reason
I
wanted
to
focus
just
on.
One
was
because
I
felt
like
we're.
I
felt
like
the
discussion
was
getting
lost
in
terms
of
like
what
we
were
talking
about.
So
that's
why
I
wanted
to
focus
on
one.
I
understand
how
to
relate
it,
so
I'm
fine.
If
we
want
to
do
talk
about
both
together
and
yeah,
I
mean
that's
fine
with
me
and
even
as
part
of
the
implementation.
E
B
D
D
B
Okay,
cool,
okay,
all
right,
so
then
I
think
that
so
that's
like
the
first
topic.
I
guess
is
that
kind
of
use
cases
that
and
those
those
three
things
so
I
mean
is
that
do
we
have
any
more
discussion
on
that
because
I
know
like
we
had
some
comments
last
time
about
some
of
these
cases
and
is
that
clear
kind
of
does
everyone
understand
what
I'm
trying
to
accomplish?
E
F
E
What
we're
talking
about
we're
talking
about
a
virtual
machine
instance
or
a
virtual
machine?
It
says
virtual
machine
instance
in
this
use
cases,
but
what's
the
admin,
I
don't
completely
understand
the
end-to-end
use
case.
If
we're
looking
at
virtual
machine
instances
river
instead
of
virtual
machines,.
B
Okay,
so
this
could
be
my
understanding,
so
the
way
the
wave
looked
at
is
that
I
have
looked
at
the
virtual
machine
instance,
and
this
is
what
I've
considered
my
running
vm,
that's
like
how
I'm
using
it
in
the
language
here
and
virtual
machine
being
not
running.
That's
like
how
I'm
looking
at
it,
and
so
I'm
not
looking
at
it.
Maybe
the
way
you
are
with
like
the
objects,
so
I
that's
kind
of
my
perspective
on
this
because
running
virtual
machine
being
that
how
that's
how
you
get
the
ram.
E
E
So
you
have
a
suspended
virtual
machine.
That's
saved
off
completely
the
ram
and
everything
is
the
state
where
you
can
restore
it,
but
it's
like
suspended
in
memory
and
it's
not
actually
running
anywhere.
It's
not
taking
any
resources
in
the
cluster
other
than
the
storage
resources
like
I
can
represent
that
in
that
same
high
level
object.
The
vm
object
that
when
we
talk
about
virtual
machine
instance,
I'm
trying
to
represent
just
as
a
virtual
machine
instance
with
other
like
save
state
and
things
like
that,
it
becomes
more
disjoint
and
I'm
just.
D
Yeah
I
mean
it's,
it's
the
same
like
at
with
it
like
with
the
virtual
machine
instance.
As
such,
there
is
no
strong
binding
in
any
way
or
just
in
virtual
machines.
It
just
references
some
stuff,
and
you
have
to
keep
these
references
right,
restoring
exactly
it's
another
object
like
like
you
have
with
the
virtual
machine
snapshot
where
also
there
is
no
virtual
machine
anymore
afterwards.
B
So
what
I
guess,
what
what
do
you
see?
Sorry,
the
relationship
between
the
virtual
machine
snapshot,
api
and
the
virtual
machine
api,
because
it's
on
the
way
I
view
it
as
sort
of
like
very
similar
and
and
like
the
virtual
machine
api
it
has.
There
are
sort
of
things
associated
that
you
can
do
with
it,
but
it's
it's
generally,
a
representation
of
a
virtual
machine
that
you
can
run.
H
D
We
have
more
on
it
like
it's.
A
vmi
is
also
kind
of
the
equivalent
of
a
part
like
you
can
have
different
controllers.
One
of
them
is
a
vm
which
adds
some
features
and
the
other
one
which
you
have
is
very
nice
virtual
machine
instance
replica
set
which
can
create
multiple
running
games
for
you
out
of
a
single
entry
point
and
manage
it
for
you
and
scale
it
for
you
and
yeah.
That's
also
there.
So
it's
not
just
that.
There's
only
the
virtual
machine.
B
Understand
so
this
is
so
you
have
an
api
that
can
sort
of
isn't
necessarily
a
representation
of
a
running
machine.
A
running
virtual
machine
with
a
virtual
machine
replica
set,
is
kind
of
what
I'm
understanding
and
then
you
have
a
virtual
machine
api
which
is
kind
of
similarly
holds
some
of
that
ground
as
well,
and
just
the
virtual
machine
instance
itself
is
a
single
representation,
and
so
when
we
shut
it
down,
it's
technically
no
longer
a
bmi
yeah.
I
think
I
understand
that.
I
guess
the
thing
that
I'm
missing,
though,
is
like.
B
So
I
guess.
Maybe
this
is
a
discussion.
The
direction
here,
like
the
one
that
I
describe
in
in
this
document,
is
I'm
talking
about
like
it's
really
it's
an
api
that
I
know
michael
worked
on
for
the
for
the
snapshot
I
sort
of
viewed
as
sort
of
a
way
that
holds
all
the
information
of
a
formerly
running
bmi.
But
technically
I
could
see
how
a
virtual
machine
is
also
can
be
considered
a
formally
run,
a
snapshot
of
a
formally
run
api
or
sorry,
a
formerly
run
virtual
machine.
B
E
The
virtual
machine
snapshot
is
a
point
in
time
of
that
vm
object
and
it
can
be
restored
to
that
previous
point
in
time.
We're
talking
about
restoring
the
vm
on
just
the
higher
level
object.
It
only
works
in
the
higher
level
object
right
now.
So
let's
say
it's
like
think
of
it
like
a
restore
point
for
like
your
laptop
or
something
where
you
can
restore
it
to
the
previous
state.
E
A
D
B
Do
do
you
mind
if
we
cover
that
in
like
a
few
minutes?
Sorry,
I
don't
know
who's
talking.
I
do
you
mind
if
we
cover
that
in
a
few
minutes-
and
we
just
just
finished
like
the
kind
of
the
api
discussion
here.
First,
let
me
come
back
to
that.
Is
that
okay,
because
I
think
that's
a
I
do
want
to
answer
that
too.
B
D
E
That's
strange:
when
we
look
at
the
virtual
machine
replica
virtual
machine
instance
replica
set.
The
thing
that's
strange
is
how
do
we
represent
individual
state
of
vmis?
So
so
right
now,
it's
all
ephemeral.
If
somebody
has
a
pvc
that
they
have
in
their
virtual
machine
instance,
replica
set
it's
read-only
and
the
femoral
state
is
stored
on
disk
with
the
vmi
in
the
in
that
container.
D
I
mean
that's
what
you
have
to
do
anyway.
I
mean:
what
do
you
have?
What
do
you
have
with
this
shared
storage?
Is
that
you,
anyway
right
into
overlays
right
in
your
vms,
so
you
have
a
read,
only
base
image,
which
is
in
the
pcs,
so
you
can
just
snapshot
it
at
any
time
with
including
the
overlay
where's.
D
D
E
D
D
D
E
Not
a
per
vmi,
oh
there's!
No!
When
we
talk
about
the
virtual
machine
instance,
replica
set
sorry
we're
getting
a
tangent
here.
The
point
I'm
trying
to
make
is
ryan.
If
you
end
up
moving
to
something
like
that
virtual
machine
instance
replica
set,
then
we're
going
to
have
issues
trying
to
even
save
and
restore
a
vmi,
because
a
portion
of
that
vmi's
data
at
the
disk
is
on
an
overlay.
E
B
Is
this
something
that,
like
with
the
virtual
machine
instance
replica
set,
is
it
something
that
sort
of
I
mean?
Is
there
a
way
to
sort
of
that
we
can
make
it
like
incorporate
this
as
part
of
like,
like
I
don't
like?
How
would
I
how
would
I
get
like?
Is
it
was
kind
of
what
you're
telling
me
that,
like
there
isn't
really
a
way
we
can
make
this
work,
or
is
it
that
we
started
to
change
some,
do
some
major
changes
to
make
it
work.
D
B
Okay,
I
guess
so
let
me
before
I
don't
want
to
take
too
much
time.
I
guess
I'm
going
through
this,
I
mean,
would
would
one
of
you
guys
be
able
to
like,
maybe
summarize
this
in
the
doc?
I
don't
know.
Can
you
do
me
a
favor?
Maybe
I
don't
know
like
is.
Is
it
on
the
thread
like
kind
of
because
I
do
want
to
capture
this?
I
guess
maybe
it's
part
of
this
or
something
like
a
caveat
and
then,
but
I
think
like
and
then
kind
of
move
on
with.
E
E
B
I'll
make
a
note,
okay,
all
right,
so
I
think
to
kind
of
conclude
here
what
so
I
I
do.
I
do
like
the
idea
of
okay,
we
go
from
vmi
and
we
follow
the
chain
of
going
to
vm
and
then
vm
snapshot.
I
don't
know,
is
there,
so
does
anyone
object
to
that?
Like?
I
don't
think.
That's
like
the
wrong
path.
I
think
that
seems
seems
reasonable
to
me
because.
E
E
B
E
B
F
Yeah,
I'm
just
trying
to
understand
what
solver,
what
problem
are
we
solving?
I
mean,
even
if
we'll
create
the
vm
or
anything
like
this
it,
it
will
still
stay
on
this
system
on
the
system
that
we
actually
took.
The
snapshot
and
what
you're
describing
in
the
use
case
is
that
you
will
want
to
export
this
and
then
someone
on
another
system
with
another
cluster
when
another
set
of
nodes
will
have
to
restore
this,
and
I'm
not
entirely
sure.
How
realistic
is
this
and.
B
So
the
the
general
sort
of
principle,
I'm
kind
of
looking
to
apply
is
that
is
sort
of
that.
I
could
have
that
once
I
take
this
virtual
machine,
it's
it's
now
mobile.
Now
I
guess
you
could
say
like
how
could
I
take
this
virtual
machine?
That's
sort
of
snapshot
in
a
ppc,
that's
in
a
crd
in
a
kubernetes
cluster
and
then
offload
it
put
it
on
a
usb,
stick
and
move
it
to
like.
You
know
I
don't
know
another
another
state
and
then
plug
it
into
my
home
lab
or
something
yeah.
B
I
understand
that,
like.
I
guess,
that's
not
necessarily
like
what
I'm
after
it's
more
like
the
idea
that
that
this,
the
mobility
of
this
of
this
virtual
machine
can
go
beyond
just
where
it
currently
sits
on
the
current
host
that
it's
in
it
can
somehow
go.
I
don't
know
slightly
to
a
different
name
space.
B
At
the
very
least
I
mean
possibly,
I
don't
know
like
the
other
side
of
that.
I
think
sort
of
is
not
really
like
what
like
I
want
to
cover
like,
because
I
think
you
know
maybe
there
can
always
some
system
and
stuff.
I
can
always
work
out,
but
mostly
the
idea
that
I
can
take
it
offline
and
I
can
move
it
like.
It
is
snapchatted
in
this
place
that
I
can
move
it
around
in
an
object.
F
I'm
just
saying
that
when
we
are
when
we
are
saving-
and
we
are
when
we
are
saving
memory,
we
need
to
know
what
kind
of
cpus
were
used.
You
know
the
specifics
of
a
hardware.
So
basically,
when
you
restore
this,
it
has
to
be
restored
in
the
same
kind
of
a
node
and
then
yeah.
What
I'm
trying
to
get
it
is
that
maybe
what
we?
What
you're
after,
is
really
some
kind
of
a
import,
export
or
export
import,
and
maybe
that's
what
we
need
to
really
implement.
B
H
H
F
F
H
H
B
B
Oh,
so,
oh
sorry,
I
I'm
maybe
missing
okay,
so
I
yeah
so
there
there
is
yes
like
this
is
sort
of
this
is
the
case
in
an
existing
system.
Yeah,
it's
it's
sort
of
not
like.
I
I
don't
know.
I
guess
my
perspective
on
this.
Is
that,
like
I
could
think
of
ways
to
get
like
the
files
off
like
for
me.
What
I'm
after
is
like
getting
this
state
stored.
H
H
The
customer
service
of
that
appliance
once
wants
me
to
d
wants
to
debug
it.
So
I
can
just
take
a
snapshot
or
something
similar
and
send
it
to
him
and
he
can
evaluate
it.
Obviously
it
cannot
work
on
everything.
For
example,
if
you
have
hardware
dependencies
or
like
your
cpu
is
not
emulated
or
something
uses,
some
kind
of
is
based
on
your
hardware.
That
will
be
impossible
to
restore
what,
but
maybe
we
can
add
these
limitations.
H
B
D
I
think
it's,
the
initial
idea
is
pretty
clear.
Now:
okay,
we
can.
We
can
probably
refine
more
on
what
to
do
with
it
than
like.
Edward
and
larry
hinted
a
little
bit
like
once.
You
have
snapshotted
it.
What
would
be
the
kind
of
variations
you
would
want
to
do
with
it
like,
like
mentioned
cordon
brand,
you
may
want
to
add
starting
it
in
the
same
name,
space
or
another
namespace.
D
B
Yeah,
those
are
things
yeah
the
concern
we
can
add
on
over
time.
Okay,
all
right.
What
was
the
second
thing
now?
I
forgot
device
management
okay,
so
I
added
another
section
in
here
about
oh
actually,
there's
so
two
things
in
here
so
last
time,
there's
a
question
about
whether
based
on
the
flags
that
we
could
provide
what
will
happen
to
the
virtual
machine.
B
So
I
just
added
a
section
with
the
two
functions
that
I
found
at
lever
that
do
the
save
and
here
are
some
examples
of
what
they
do
so
I'll
leave
those
there
whenever
you
want
to
read
them,
but
the
main
thing
I'm
looking
for
is
this
and
then
at
live
doing,
live
at
a
later
point.
We
can
do
this
and
then
there's
obviously
a
bunch
of
other
things
that
we
could
do
so.
That's
cool
all
right
devices.
B
So
one
of
the
things
that
I
have
had
brought
up
or
mentioned
a
few
times
here
is
devices.
And
what
happens
you
know
when
you
save
restore
and
you
have
devices
attached,
so
one
of
the
things
is
and
dan
baron
j
was
the
one
who
commented
on
this.
It's
somewhere
in
this,
I
think
it's
below
and
sort
of
the
expectations
of
what
happens
when
you
do
a
save.
B
That's
what
I
was
reading
and
essentially
what
we
need
to
do
is
do
some
sort
of
hot
unplug
of
the
devices,
and
I
can
tell
kubernetes-
does
not
support
this,
but
I
think
that's
okay.
This
is
essentially
hot
unplugged
with
kubernetes,
since
kubernetes
makes
those
devices
available
to
the
pods
hot
unplugging
would
be
removing
it
from
the
pods.
So
one
way
around
this
would
actually,
since
we
have
the
vert
launcher
there,
maybe
we
can
have
the
launcher
sort
of
call
it
delivered
and
say:
hey
just
unplug
these
devices.
F
Brian,
just
a
question
yeah:
what
kind
of
benefit
is
it
for
you?
Then?
For
example,
you
were
debugging
some
kind
of
a
system
with
the
with
the
gpu
attached
and
it
was
misbehaving
yep
and
then
and
then
in
order
to
save
this
the
memory
and
restore
it
later,
for
example,
you
will
need
to
to
detach
this
gpu
and
then
so
I
mean.
Is
there
still
a
benefit,
because
I
mean
the
system
doesn't
run.
I
mean
the
the
memory
snapshot
that
you
are
taking.
It
will
be
without
gpu.
B
Yeah
so
like
well
minor
sydney
is
that
yeah
you're
right
it
is
without
gpu.
I
don't
know
if
I
don't
think
it
affects
the
use
case.
I
mean,
I
believe,
the
operations
or
whatever
it
basically
like
the
idea
is
that
the
the
devices
need
to
be
shut
down
so
that
nothing,
I
guess
I
don't
know
liver,
maybe
doesn't
understand
what
the
internal
operations
of
it
are.
So
they
need
to
be
removed.
B
H
B
Well,
the
that
side
of
things,
I
think
I
think,
would
be
okay,
I'm
gonna
talk
about
it
down
here,
but
and
the
the
store
side,
but
I
think,
like
we,
we
heard
what
flat
what
was
saying
is
that
what
is
this
virtual
machine
exactly
like?
Is
it?
Is
it
in
that
sort
of
problematic
state
if
we
detach
the
device
right?
Is
that
that
what
you're
saying
like
is
it?
Is
it
actually?
E
That
would
be
my
expectation,
but
I
I
don't
know
I
would
expect
that
it
gets
paused.
We
remove
devices,
I'm
not
entirely
sure
why
that
needs
to
happen
still,
but
that's
okay,
and
then
we
snapshot
and
then,
when
we
restore
you're
kind
of
putting
everything
back
the
way
it
was
and
then
kind
of
hitting
the
button
to
unpause
it
so
yeah.
I
guess
I'm
unclear.
H
F
David,
the
only
thing
that
I
mean
the
the
reason
for
this
is
that
some
of
the
memory
that
the
vm
is
using
is
being
stored
inside
the
device,
so
the
device
state
and
some
of
the
caching
and
some
of
the
things
that
are
going
on
at
that
particular
time.
It's
it's
being
stored
in
the
device.
If
you
don't
have
that
specific
device
right
with
that
cache,
I
mean
it
will
not
yeah.
So.
F
E
E
B
H
F
E
B
E
Okay,
so
for
your
use
case,
what
would
would
you
still
have
the
same
benefits
if
you
shut
down
the
vm
entirely
and
did
an
offline
snapshot
like
I'm
trying
to
understand
how
important
is
it
that
you
capture
it
right
at
that
moment
like
the
live
state
everything?
Is
it
possible
to
reboot
it
and
get
back
into
that
state
or
I
I
don't
fully
understand
the
applications
that
you're
running.
B
No,
so
it
it's
specifically
yeah
and
once
you
shut
it
down,
you
sort
of
the
idea
would
be
that
we
lose
where
the
execution
is
like.
Like
a
good
example,
be,
like
I
mean
yeah,
I
mean
I
mean
this,
this
kind
of
sums
it
up.
I
mean
like
what
I
have
here.
It's
it's
really
that
yeah,
you
have
your
virtual
machine
running,
I
mean
you
can
say
like
it's
a
game
or
something
and
and
it's
behaving
wrong
and
we
need
to
diagnose
it.
B
B
D
B
Okay,
I
think
it'll
probably
offer
me
I
think,
yeah
we
don't
say
what
was
the
last
pvcs
yeah
we
can.
We
can
kind
of
talk
about
that
in
the
time.
Then.
Let
me
take
this
this
item
and
kind
of
do
some
more
investigation,
and
then
we
can
talk
about
some
of
the
other
items.
I
think
there's
probably
even
more
topics
we
can
cover
too,
as
well
as
long
as
I
get
the.
Let
me
get
some
more
information
on
this
and
get
back.