►
From YouTube: KubeVirt Community Meeting 2023-05-17
Description
Meeting Notes: https://docs.google.com/document/d/1nE09vQWcCTW-9Ohe9oCldWrE0he-T_YFJ5D1xNzMtg4/
A
Alrighty
we
have
four
past
the
hour.
Welcome
everybody
wherever
you
are
to
May
17th,
2023
cubert
community
meeting
to
start
us
off.
Do
we
have
any
new
people
here
today
that
would
like
to
introduce
themselves.
It
was
kind
of
struggling
with
about
yourselves.
B
Yeah
today
my
name
is
Vic.
Turtle
I
watched
one
of
your
presentation
lately
they're
just
interested
in
how
it
works,
especially
the
the
API
Machinery
related
just
the
architecture.
A
Wonderful
welcome
victim,
we'll
if
you've
got
any
any
questions
in
particular
welcome
to
throw
them
into
the
open
floor
down
here.
Otherwise,
at
the
end,
I'll
leave
a
bit
of
time
once
I've
gone
through
the
agenda
and
you're
welcome
to
ask
any
questions
or
anything
like
that.
If
you,
if
you'd
like
so
yeah
for
those
that
haven't
had
to
bear
with
me
hosting
one
of
these
meetings
when
I
share
my
screen
for
whatever
reason,
I
can't
see
my
mouse
cursing
so
I'm
going
to
have
to
just
drag
and
drop
tabs.
A
So
we're
having
a
look
at
the
Qbert
1.0
release
schedule.
We
must
have
tagged
a
beta
which
I
think
might
be
what
Daniel's
going
to
be
talking
about
and
he's
got
a
few
points
on
the
agenda.
So
I'm
going
to
pass
it
over
to
him.
C
Not
really
talking
about
the
about
the
cube
root
of
the
1.0
itself,
I'm
just
trying
to
capture
a
little
bit
about
the
qvci
updates
that
we
need
for
enabling
this.
So
you
so
you're
not
completely
wrong,
but
just
partially
right.
C
Let's
say
like
that:
I'll
take
what
I
can
get
okay,
so
I
want
to
talk
today
about
how
where
we
stand
regarding
Cupid
CI,
so
the
general
process
most
of
the
time
is
that
we
are
always
trying
to
align
in
terms
of
kubernetes
with
having
some
kubernetes
provider
that
we
are
using
for
testing
to
have
the
latest
version
of
kubernetes
itself
available,
which
we
with
which
we
run
our
functional
tests
and
that's
what
puberty
is
about.
C
So
to
give
you
a
little
overview
in
the
nutshell,
where
we
stand
at
the
moment
is
that
we
are
at
least
I
I.
Think
that
probably
Ryan
last
week
told
you
already
that
we
had
a
problem
with
namespace
deletion
on
the
latest
kubernetes
1.27
provider,
which
actually
got
fixed
by
a
PR
brought
up
by
lubo.
Thanks
for
that,
so
the
periodics
look
pretty
good
now,
so
we
have
on
all
Lanes
on
all
21s
27,
Lanes,
pretty
good
or
even
completely
green
runs.
C
The
pre-submits
haven't
been
enabled
yet,
but
actually
we
have
a
PR
in
the
in
the
works
that
should
be
merged
at
least
soon
or
maybe
has
already
been
merged.
I'm
not
exactly
sure,
but
it
should
be
emerged
by
end
of
the
day
today.
C
That
will
actually
then
enable
to
run
all
pre-submits
for
the
four
six
that
we
have,
which
is
compute
operator,
Network
and
storage,
so
that
you
will
probably
see
some
failing
pre-submits
on
your
PRS.
Don't
get
confused
by
that.
We
are
just
trying
to
collect
some
data
on
that,
so
so
that
we
know
how
where
we
are
standing
regarding
compatibility
to
the
latest
kubernetes
release
other
than
that
we
are
still
waiting
regarding
cuperti
updates,
so
I
guess
you're
not
aware
of
that.
C
But
currently,
our
latest
stupid
provider
for
127
is
still
based
on
the
RC,
which
of
course,
is
not
really
good,
because
we
are
already
I,
think
the
minor
version
should
already
be
or
or
the
the
release
version
should
already
be
dot
one,
but
we
are
still
blocked
right
now
on
a
problem
that
we
have
itself
on
Cupid
CI,
which
is
based
on
a
kernel
on
a
kernel
block.
But
we
are
waiting
this.
This
kernel
update
should
come
in
any
minute.
C
We
have
decided
to
wait
at
until
the
end
of
the
week
if
it
still
doesn't
get
into
Central
stream
8,
which
is
the
base
for
our
nodes
that
we
are
running
kubernetes
with.
C
We
are
going
to
downgrade
the
kernel
version
on
the
on
the
Note
OS
so
that
we
can
fix
this
yeah.
That's
in
a
nutshell,
what
what
I
can
present
regarding
qpci
updates?
Any
questions
on
that.
C
Thanks
everyone
for
bearing
with
me
and
my
long
talking,
okay,
thank
you.
A
Thank
you
very
much
Daniel
and
thanks
for
staying
on
top
of
all
that
Howard
I
believe
you've
got
the
next
point.
D
Okay,
hi
everyone.
My
plot
is
a
little
bit
long.
D
So
here
is
some
update
on
QB
words
on
64.
I
have
read
written
down
the
documents
for
QP
verse,
I'm
64.,
as
we
discussed
on
what
we
need
to
do
to
make
qbivert
officially
release
I'm
64
image.
D
D
D
S
so
maybe
I
can
put
it
into
our
email
and
send
that
to
the
email
group
group.
A
I
think
that's
an
excellent
idea.
Yeah.
D
D
Okay
and
the
next
tip
I
want
to
do,
is
to
enable
conformance
tests
on
64
Grant
form
and
because
the
image
Fedora
will
test
test.
Twittering
image
are
needed,
and
now
we
don't
have
m64
version
Fedora
with
test
tour
linked
image,
so
I
submit
a
patch
server
to
build
matiac
images.
D
Yeah-
and
my
question
is
if
we
like
the
e2e
conformance
test,
runs
well
on
64
platform.
What
else
we
need
to
do
before?
We
can
officially
release
the
m64.
E
Hi
Howard
I
think
that
we
don't
have
an
immediate
answer
for
that.
That
is
because
that
is
why
the
silence
so
I
believe,
let's
take
it
either
offline
or
to
give
you
the
mailing
list,
so
we
can
discuss
it
further.
E
A
That's
great,
so
it
really
sounds
like
we're
we're
coming
close
to
having
a
people
around
64
release.
A
And
hopefully
he
had
some
comments,
questions
and
support
on
the
mailing
list
threat
once
you've
got
back
out
there
and
if
not,
we'll
we'll
raise
again
this
meeting
and
see
if
we
can
get
traction
on
this.
This
is
awesome.
Thank
you
very
much.
Howard.
E
Yeah
hi
everyone,
so
yeah
I
wanted
to
just
to
update
you
that
we
are.
We
want
to
push
forward
the
design
proposal
about
the
CPU
hot
plug,
and
you
are
more
than
welcome
to
chime
in
to
discuss
the
design
or
and
or
and
close
possible
gaps
if
there
are
any
yeah,
and
hopefully
we
are
looking
forward
to
marriage.
E
I,
don't
know
by
the
end
of
this
week.
I
was
starting
the
next
week
and
for
your
information
we
already
have
a
working
POC,
which
will
be
also
published
soon.
E
Yeah-
and
this
is
this-
will
be
actually
a
cool
feature.
You
will
be
able
to
increase
the
number
of
your
virtual
CPUs
during
virtual
machine
runtime
yeah,
and
that's
it
basically
for
me.
Thank
you.
Everyone.
A
Great
the
CPU
hot
plug
and
64
has
seem
like
long-term
features
that
I
know
I've
been
hearing
about
and
reading
about,
for
a
long
time
very
nice
to
see
them
kind
of
coming
towards
the
finish
line
now.
A
Well
done.
Everyone
I've
got
a
quick
Point
here
before
we
move
on,
which
is
both
kubecon
and
open
source
summer
China
in
2023
in
kubecon,
North,
America
2023,
their
cfp
is
open
and
they
both
close
at
the
same
time,
which
is
June
18th,
which
is
one
month
and
one
day
from
now.
A
The
the
one
in
China
is
at
the
end
of
September
I
think
the
involves
the
23rd,
maybe
that's
just
the
year,
and
the
one
in
North
America,
which
is
in
Chicago,
is
the
start
of
November
yeah.
So
by
all
means,
if
you
need
any
help,
support
reviews
if
you've
got
any
questions,
please
hit
me
up,
but
also
I'll,
be
away
for
the
next
couple
of
weeks.
So
that
gives
you
a
couple
weeks
to
to
think
a
lot
about
potential
proposals.
A
I've
also
sent
an
email
about
this
last
week
with
a
lot
more
details
and
also
a
call
for
if
anyone
has
any
ideas
for
a
like
a
hackathon,
they
call
it
contribfest
at
kubecon
they've
got
any
ideas
for
a
kubecon
one.
Then
it
would
be
great
to
submit
and
we
need
a
relatively
well-rounded
proposal
for
him
to
do
that.
So
I'll
leave
that
with
everyone.
E
A
C
Actually,
yeah,
that's
absolutely
true
what
you're
saying
this
is
an
automated
automatically
created
VR
that
we
don't
that.
Of
course
we
need
to
look
at
that,
but
we
don't
need
to
discuss
this
here.
I
say.
A
D
Yes,
when
I
were
firing,
the
future
cage
I
found
these
future
Gates.
There
is
no
code
related
to
this
future
gauge,
so
I
think
if
we
can
remove
it
or
put
it
in
the
fabricate
list,.
A
A
All
right,
I
can't
navigate
around
that,
but
I'll
look
at
that
for
someone
to
take
a
look
at
and
this
third
or
does
anyone
else
want
to
have
a
comment
on
that
or
while
we're
here
and
how
it's
it.
A
All
righty
that
third
one
looks
like
Corel
and
Lee
have
both
jumped
onto
so
we're
going
to
look
at
that.
The
mailing
list
review
I
think
there's
at
least
comments
on
all
of
the
threads
from
last
week,
so
we
don't
need
to
jump
into
them,
but
if
anyone
has
anything,
they'd
like
to
anything
from
the
threads
I
did
notice,
there's
a
monitoring
design
proposal.
A
A
All
righty
well,
we've
got
two
bugs,
then
all
right
problem
signing
bgpu
has
mediated
device.
A
Here
this
actually
looks
like
it's
an
open
ship
bug,
rather
than
is
it
fair
enough
comment.
D
Yes,
this
is
a
list
of
all
future
Gates,
the
status
of
all
future
guitar
I'm
64.
there's
some
support
and
the
some
are
not
support.
The
answer.
Unsupports
naming
caused
by
two
reasons.
One
is
a
CPU
future,
like
some
future
only
supports
x86
CPU
and
some
some
future
Gates
not
support
because
of
the
dependency
like,
for
example,
the.
D
Let
me
see
a
hot
pack
volume
sketch
this
one.
It's
rely
relies
on
the
CPI
project,
but
the
CBI
projects
does
not
support,
have
not
supported
yet
yes,
so
we
don't
support
this
future
gate.
A
A
Wonderful,
thank
you.
That
brings
us
to
the
end
of
our
bug.
Scrub
Howard
you're,
going
to
include
this
in
the
mailing
list
thread
that
you
create
I,
presume.
D
Yeah
I
have
created
a
document
for
each
and
user
guide.
Yeah
awesome.
A
Thing
just
making
sure
that
nothing's
been
added
alrighty
there's
before
we
close
out.
Does
anyone
have
anything
that
they
wish
to
add
any
questions,
any
comments,
any
celebrations
for
anyone.
B
Yeah
I
have
some
question:
if
there's
no
other
topic
sure
thing,
yeah,
I
I
said:
wait,
watch
Join,
one
of
the
call
where
Kilt
work
was
discussed.
My
understanding
is
covert
from
my
talk
is
actually
a
separate
infrastructure.
It's
not
part
of
the
I,
don't
know
even
it
runs.
B
I
I
haven't
looking
in
details
like
it
doesn't
work
run
on
a
separate
kubernetes
cluster
or
it
doesn't
even
run
kubernetes
cluster,
so
yeah
I'm
just
trying
to
get
more
information
about
how
it
works
in
relation
to
the
overall,
the
API
Machinery
or
the
kubernetes
API
infrastructure.
Is
there
any
I
guess,
first
of
all,
I
guess,
there's
any
any
videos
or
documentation
regarding
this.
A
Yes,
there
is
I
I
kind
of
see
my
message
when
I
share
my
screen,
but
perhaps
I
can
connect
with
you
offline
on
Slack.
If
you
want
to
ping
me
in
the
kubernetes
workspace,
I'm
a
burden
and
I
can
directly
to
a
couple
of
articles,
blogs
and
some
some
videos.
Some
of
them
might
be
a
little
bit
old,
but
I
I
think
they'll
sufficiently
explain
what
you
have
to.
A
All
righty
does
anyone
else
have
anything
that
we
should
add
before
we
close
out.