►
From YouTube: KubeVirt Community Meeting 2019-11-06
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
everybody:
this
is
the
Kubrick
community
meeting
November
6th
2019
been
a
few
weeks
since
we've
recorded,
unfortunately,
but
this
one
we
can
and
as
far
as
the
agenda
today,
let's
start
with
release
0.23
we
have
a
few
changes
here:
guest
OS
information
is
now
available,
we've
updated,
go
to
1.12
go
yeah
mole
has
been
updated
as
well.
We've
cleaned
up
and
fixed
the
CRT
scheme,
registration
and
a
few
bug
bug
fixes.
So
I
don't
know
if
there's
any
questions,
but
that's
the
basic
gist
of
this
release.
A
B
Yeah,
okay,
that
was
almost
too
fast,
and
you
prefer
already
so
yeah
just
admit
it
I
think
so
for
some
time
now,
actually
I
think
until
every
release
after
serious
17,
we
have
reports
from
people
that
we
in
see
connections
are
not
working
so
great
and
yeah.
It
got
even
worse
when
we,
when
we
did
the
last
two
or
three
years
releases
where
we're
effective
in
see
connections
and
finally,
I
found
the
issue
for
it.
B
C
Just
a
quick
note:
I
just
sent
an
email
right
before
this
meeting
to
the
mailing
list
with
more
details,
but
we
will
have
face-to-face
meet
up
for
anyone
attending
keep
con
and
in
a
couple
of
weeks.
Anyone
interested
in
keep
birds
is
very
welcome
to
get
all
together
face
to
face.
We
have
a
registration
page
just
to
help
us
determine
the
capacity
of
the
venue
and
also
where
is
a
sponsoring
some
food.
So
we
would
like
to
know
how
many
people
will
be
there,
but
other
than
that
yeah.
C
A
If
that's
not
an
enticing
enough
to
everybody,
if
you
haven't
been
to
San
Diego,
there's
an
absolutely
beautiful
city
and
for
no
other
reason
you
should
go
for
that.
So
please
do
attend.
It's
wonderful
and
one
more
note
and
that's
dev
comps,
easy
and
FOSDEM
2020
are
coming
up
so
I.
Imagine
we'll
have
CFP
windows
for
those
soon.
Actually.
C
The
deadline
for
DEFCON
proposals
is
today
so
get
these
those
were
mentioned,
but
we
are
planning
to
propose
we.
We
are
trying
to
suggest
some
presents
for
key
birth
there
as
well,
so
it
will
be.
We
hopefully
will
get
a
booth
accepted.
Lexie,
including
you
know,
Cooper,
for
that
comp.
The
four
papers
ends
later
keep
earth
belongs
I'd,
say
to
the
visualization
and
infrastructure-as-a-service
Deb
room
I'm,
looking
from
memory,
I
think
the
deadline
for
this.
That
room
is
1st
of
December.
C
C
We
will
see
if
that
gets
accepted,
and
now
that
we
mentioned
open
call
for
papers,
you
know,
maybe
you
might
not
be
able
to
make
it
San,
Diego
or
even
if
you
are
able
to
make
it
to
San
Diego.
The
next
skip
con
will
happen
in
Europe
in
Amsterdam
last
day
of
March,
beginning
of
April
and
the
call
for
papers
for
that
one
is
open
right
now
and
I.
Don't
remember
the
deadline
for
submission.
There's
still
some
time.
C
A
D
Sorry
I
was
looking
for
there
for
the
window.
I
was
just
I,
was
working
on
the
on
a
PR
to
introduce
a
way
to
isolate
emulator
thread
and
pin
it
to
separate
CPU.
This
should
provide
us
with
when
we
do.
The
CPU
pinning
basically
provide
the
way
to
pin
all
the
virtual
CPUs
to
physical
CPUs,
but
we
don't
do
anything
with
there
with
the
emulator
thread
that
basically
takes
care
of
all
the
all
the
work,
all
the
threads
that
are.
They
belong
to
key
mu
so
in
in
order
to
provide
a
better
real-time
support.
D
Let's,
let's
put
it
this
way,
and
just
we
will
allocate
additional
additional
virtual
Sippy,
sorry
I,
just
don't
physical
CPU
and
we'll
open
the
they
mailed
emulator
thread
on
it.
So
there's
a
PR
and
there
I'm
finishing
up
with
the
functional
test,
so
we
have
before
reviews,
there's
another
PR
that
I
put
up
for
for
a
time
sync,
and
basically,
when
the
lab
migrations,
are
you
taking
too
much
time?
D
What
can
happen
is
that
the
clock
inside
the
it
can
get
skewed,
and
we
basically
need
to
do
sync
when
the
lab
migration
is
over
and
so
I
put
a
repair
for
this.
This
also
applies
for
the
for
the
pause
and
unpause,
and
basically,
if
you
pause
for
too
long,
NTP
cannot
overcome
this
large
gap
and
will
need
to
do
the
sync
after
that,
as
well.
So,
and
the
market
is
working
on
this
pair
and
they
will
just
need
to
the
the
time
sync
after
the
PR
is
done.
A
That's
it
cool
thanks.
No
I
was
re
rephrasing
again
and
again
how
to
phrase
the
fact
that
NTP
just
doesn't
support
it.
I
mean
it's
part
of
NT
piece
design,
but
if
exelon
jump
is
too
big,
it
just
throws
it
out
and
quits
because
something's
wrong,
so
that's
by
design,
but
thank
you
for
noticing
and
fixing
that
are
there
other
questions
on
that.
A
All
right,
I
think:
are
there
any
other
things
to
bring
up
I
think
we've
covered
it
all,
because
we
sort
of
jumped
around
but
I,
don't
see
anything
that
we
didn't
discuss
at
this
point.