►
From YouTube: KubeVirt Meeting Meeting 2021-03-17
Description
KubeVirt Meeting Meeting 2021-03-17
B
A
A
A
C
Hi,
sorry,
I
guess
I'll
start.
First,
I'm
the
only
new
one,
I'm
sammy
walker,
I'm
a
infrastructure
consultant
in
red
hat,
I'm
coming
on
board
actually
from
a
person
with
slack
conversations
regarding
some
it
was
at
se
linux
and
we
do
testing
among
different
things.
So
I'm
trying
to
get
more
involved
with
keyboard
as
a
whole
too,
since
I've
been
using
it
late
before
openshift
adopted
it.
So
definitely
looking
forward
to
meeting
up
one
and
getting
to
this
community
here.
A
A
E
A
A
We
flat
out
missed
suzatan,
that
was
in
november.
I
believe
it
was
wasn't
even
on
our
radar,
and
that
was
I
think
that
was
a
a
big
mistake.
On
our
end
personally,
I
was
eyeballs
deep
into
getting
a
user
guide
migrated
into
from
docsify
over
to
make
docs
and
drop
the
ball
on
getting
out
to
events
in
the
fall.
A
A
A
A
A
And,
of
course,
volunteers
are
always
welcome
if
you
like
to
talk
with
people
in
chat
and
and
looks
like
the
platforms
are
going
to
have
a
some
kind
of
video
conferencing
feature.
So
if
you
like
to
talk
to
to
users
or
potential
users,
this
is
an
excellent
opportunity.
Please
reach
out
to
me
and
we
can
get
you.
C
A
A
F
Yeah,
just
just
a
quick
heads
up
to
the
community
that
we
have
now
something
in
place
to
make
transparent
and
automate
memberships
of
of
keyboard
contributors
and
also
for
management
of
repos
and
teams,
and
so
on
and
yeah.
I
put
together
yesterday's
small
document
on
just
where
to
file
prs
against
I.
This
is
not
exactly
completely
detailed
for
exactly
details.
F
A
F
G
H
H
It's
not
yet
merged,
but
we
are
basically
able
to
just
talk
to
podman
through
the
docker
api
and
then
start
our
clusters
through
that,
apart
from
taking
away
the
need
that
people
install
docker
locally
if
they
have
partner
already,
this
will
also
help
a
lot
with
ci,
because
podman
allow
is
demon
less
and
therefore
it
has
features
for
sharing
image
repositories
which
the
docker
demon
does
not.
This
will
allow
us
to
have
very
nice.
H
A
I
H
H
Three,
zero
one
is
released
since
first
and
honestly,
I
didn't
check
if
it
was
released
already.
I
just
went
with
the
assumption
that
latest
master
has
the
best
stock
api
support,
which
turned
out
to
be
true,
and
we
did
some
issue
reports
there.
Department
people
were
great
fixing,
fixing
them,
and
then
I
was
able
to
do
that.
A
H
H
I
H
D
D
H
H
Yeah,
so
for
for
a
few
days
now,
our
end-to-end
tests
don't
need
to
build
the
image
anymore,
because,
with
the
introduction
of
bazel
dnf,
we
can
now
build
all
containers
and
everything
and
use
the
shed
libraries
from
rpms
without
having
to
install
them.
So
for
just
make
cluster
up
cluster
sync
and
make
funk
tests.
There
is
no
need
for
the
builder
image
anymore
for
as
long
as
you
have
a
new
enough
glc
version
which
helps
us
to
just
not
have
to
load
or
pull
the
build
image
at
all
for
end-to-end
tests.
H
That
will
help
us
in
the
long
run.
Also,
this
report
on
getting
read
from
read
from
the
builder
image
also
means
that
steps
like
mac
generate
and
make
tests
and
make
funk
test
can
then
be
executed
without
the
image
which
makes
everything
more
sniffing,
more
light,
which
there
is,
by
the
way,
no
intent
to
remove
the
image
in
any
way.
This
is
really
just
to
have
better
hermetic
and
predictable,
builds
and
save
ci
load
and
make
maintenance
tasks
easier
like
not
having
to
keep.
H
A
A
It's
been
there
for
quite
a
while.
Now
I
have
a
meeting
with
the
red
hat
office
of
open
source
program
and
as
long
as
he
doesn't
have
any
more
concerns,
I'm
going
to
go
ahead
and
merge
that
please
review
it
add
comments
where
you
think
they're
needed
and
anything
in
the
future
will
just
create
a
an
issue
and
adjust.
A
C
So
yeah
this
kind
of
stems
around
some
conversations
I
had
in
slack
with
some
people
within
keyboard
community
and
the
keyboard
dev
channel.
I
you
know
I
ran
into
this
new
with
keywords
where
it
just
wouldn't
run
on
anything
cannot
coil
or
I
think
they'd
be
in
as
well,
and
this
was
because
of
a
missing
se
linux
resource-
and
you
know
everyone
knows
they
use
app
armor
versus
elegance
on
that
side
of
things.
C
So
you
know,
obviously
it
was
resolved
that
heroes
merged
and
it
was
fixed
quickly,
but
you
know
worst
case
scenario.
If
I
had
you
know,
say
there
was
some
enterprise
customers
and
they
were
running
production
and
they
were
running
conical
and
they
updated
okay,
no,
their
their
vm,
suddenly
stopped
working
after
this
family
figure
out.
So
I'm
I'm
wanting
to
you
know,
contribute
to
some
ci
testing
or
something
similar
to
where
we
can
kind
of
broaden
the
scope
of
this.
But
I'm
also
trying
to
learn
what
you
already
have
in
place.
C
So
I
can
know
how
to
contribute
properly,
because
I'm
you
know,
like
I
said
new
to
this
community.
While
I've
been
using
the
tooling
for
a
long
time-
and
I
love
it,
I'm
trying
to
figure
out
the
best
way
to
start
a
give
back
and
I'm
really
good
with
ci
cd.
So
I
figured
this
is
the
best
place
to
start.
H
So
I
think
yeah
we
were
talking
yeah
federico
is
also
on
the
call
here
I
think
federico
is
so
now
for
a
few
weeks
or
ci
leads.
So
I
think
federico
is
also
good
contact
to
talk
to-
and
I
think
regarding
to
the
issue
which
you
had
testing
keyboard
completely
fast
on
maybe
a
little
bit
farfetched,
but
I
could
think
that
we
could
start
we
could.
H
If
you've
spent
half
the
time
we
could
come
up
with
something
like
doing
limited
testing
on
different
operating
systems
with
periodic
job
or
something
so
that
we
have
basic
knowledge
that
we
don't
pay
break
core
assumptions.
We
have,
we
even
have
a
conformance
test,
suite
a
very
small
one
which
can
be
run.
So
maybe
you
can
also
add
your
voice
here.
We
could
add
something
like
starting
a
very
simplistic
kubernetes
cluster
on
on
ubuntu
and
just
run
the
10
performance
tests,
which
ref
right
now
just
to
be
sure
on
a
regular
basis.
K
C
C
H
And
I
would
see
various
ways
here
like
like:
we
can
probably
deploy
on
various
external
systems
or
do
it
similar,
like
we
do
with
keyboard
ci.
I
guess
it
also
depends
a
lot
on
on
what
you
can
contribute
and
and
how
permanent
your
engagement
would
be,
but
to
have
to
to
have
at
least
a
pc
up.
Pretty
quickly
is
probably
not
much
of
an
issue
if
it's
just
periodic
that
doesn't
block
anything.
Maybe
a
couple
already.
C
A
J
H
It's
it's:
it's
not
a
problem
for
keyword.
If
you
just
build
it
and
deploy
it,
it's
more
a
problem.
When
you
want
to
build
your
10
language
launcher
directly,
then
you
have
to
be
aware
that
you
need
to
put
in
the
vertender,
also
liberate
lip
rpm
dependencies
and
so
on,
just
to
have
the
key
more
user
present
there
or
somehow
differently
at
the
cumulus,
and
it's
not
really
necessary.
I
mean
we.
We
actually
want
to
look
invert
launcher
for
the
qemu
user
in
principle.
In
practice
it
doesn't
make
any
difference.
J
J
J
C
J
K
J
J
A
H
G
J
H
A
J
J
J
J
H
H
L
J
G
H
H
We
can
stop
doing
anything
at
all
in
this
case,
because
we
can
configure
bases
slightly
different
and
it
can
then
not
can
then
just
basically
directly
go
to
go
to
the
end
and
say
everything
is
good
or
just
download
for
the
two
tests
where
something
changed,
something
the
rest
just
isn't
the
cache,
so
it
should
be
planning
to
be
more
aggressive.
So
I
guess
I
have
to
talk
to
vasily
and
see
where
we
can
proceed
here,
because
that's
kind
of
that
the
two
requests
are
contradicting
put
it
this
way.
H
H
J
So
we
had
we
had
this
issue
where
we
wanted
to
merge
bug
fixes
first
for
the
flaky
ci,
but
instead
the
merge
queue
was
taking
other
pr
that
were
not
so
related
to
the
to
the
issue.
So
the
the
purpose
enhancement
on
this
issue
is
to
have
a
mechanism
that
allows
us
to
say
set
the
priority
of
a
pr
and
say
this
one
should
get
first,
that's
like
the
top
priority
pr
for
emerging,
like
makes
sense.
H
So
I
know
that
this
on
the
last
incident
in
the
last
two
weeks
we
had
over
three
weeks.
We
had
huge
issues
in
the
eye
and
in
the
past
mostly,
I
resolved
that
by
just
manually
merging
important
prs
when
they
were
ready
and
just
this
time
I
didn't
do
it
in
general.
I
was
fine
with
that.
If,
if
maintainers
just
do
manual
merges
I'm
not
sure
if
we
need
the
process,
I
mean,
maybe
it
would
have
helped
this
one
incident.
H
But
before
that
we
had
a
lot
of
other
incidents
and
we
resolved
it
without
it.
So
I'm
not
yet
convinced
that
this
process
is
needed.
I
mean
to
somehow
cut
out
other
pr's.
I
mean
I
mean
writing
something
to
people
deaf
and
insisting
that
maintainers
look,
which
did
not
happen
that
this
time
so
fast
of
course,
makes
sense.
J
H
J
J
J
H
I
would
prefer
that
we,
as
I
said,
and
we
didn't
do
it
this
time,
which
was
from
my
perspective,
a
mistake,
but
we
did
it
a
lot
of
times
before
and
it
worked
good
enough.
That's
why
I
would
not
go
for
a
more
strict
process
right
now,
but
if
we
will
do
it
again,
I'm
happy
to
discuss
this
again
from
my
perspective,
but
if
others
want
to
have
it
now
too,
you
can
also
discuss
it
now
or
in
a
better
form
than
this
crease
call.
J
J
J
A
A
Utf-8
characters
have
been
getting
into
into
user
guide
and
that
causes
our
html
proofer
app
to
crash.
So
I've
had
to
go
around
and
and
find
solutions
for
those
characters,
and
so
I'd
like
to
get
this
automated,
but
I
don't
want
to
create
too
many
surprises
for
people
on
on
their
keyboard
character
sets.
C
Enhancement,
it's
something
that
would
help
me
get
more
familiar
with
the
automation
and
testing.
I
would
be
more
than
happy
to
kind
of
look
into
that.
I
mean
it
sounds
simple
enough
on
paper
to
where
I
can
just
check
on
a
lot
of
markdown
files
and
say
what
kind
of
format
I'm
using.
I
could
try
for
it.
I
would
be
more
comfortable
if
I
just
make
sure
I
had
something
to
pair
with,
but
you
know
something
I
can
definitely
work
on.