►
From YouTube: KubeVirt Community Weekly Meeting - 2018-07-04
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
B
During
the
last
two
weeks,
we
had
multiple
issues
regarding
to
testability
because
of
the
device,
plugin
merge
and
fortification
device
and
a
very
annoying
network
test,
which
was
flaky
all
the
time
and
both
should
not
be
resolved
and
the
test
burns
look
much
better.
Now,
still,
as
always,
there
is
always
one
test
which
which
makes
sure
that
they
don't
get
the
perfect
run,
but
it's
pretty
reliable
again.
A
Yeah,
thank
you
very
much.
Actually
so
quite
a
few
Pat
just
not
a
why
I
thought
it's
worth
to
put
it
there
and
yes,
the
device,
plugins
cost
them.
Instability,
I
hope
it's
worth
it
well,
I
I
know
it's
worth
it
and
we'll
just
take
some
time
till
it's
really
stable
and
then
I
saw
awesome
great
that
you
put
the
agenda
item
on
it.
Cpu
model
patches
I
saw
some
stuff
being
merged
for
Secret
models.
Maybe
you
can
share
a
few
words
on
it.
C
A
D
A
Yeah
I
mean
what
we
know
is
that
if
the
model
does
not
fit
very
good
to
the
host
CPU,
then
you
have
performance.
Degradations,
actually,
I
wonder,
does
liver
complain
about
that?
No,
it
doesn't
right.
We
just
notice
it
when
I
don't
know
were
delivered
signaling.
That
I
think
some
of
you
take
it
I
know.
F
Yeah,
okay,
so
the
slurp
interface
was
imagine
a
few
weeks
ago,
and
now
we
also
will
merge
thanks
to
Roman
the
new,
the
new
interface
struct.
It
contain
the
port.
Inside
of
it
and
not
inside
of
it's
clear
configuration
it's
gotta,
it's
gotta
merge
an
hour
ago
right
now.
I'm
also
also
finished,
if
your
PLC,
so
you
can
check
it
and
I
would
like
to
get
somewhere
review.
The
name
of
hopefully
merge
it,
and
now
I
am
working
on
to
two
different
things.
One
is
that
unique,
an
interface
name
right?
Now?
We
don't
have
it.
F
You
can
create
a
several
interface
with
the
same
bacon
name
and
they
were
just
with
drop
and
the
other.
The
other
issue
8
right
now
working
it
with
the
weird
CTL
expose,
and
it's
allows
you
today
to
a
configure
target
port,
but
only
a
in
number,
only
int,
and
now
we
can
use
it
with
a
string.
So
it
will
connect
to
the
service
automatically.
We
create
on
the
virtual
machine.
A
Sounds
nifty
cool
and
can
you
please
add
the
link
for
the
EcoP?
You
see
what
you
do
sure.
Please
add
it
to
the
end
to
the
document,
so
Petter
update
from
hooks
awesome,
Pattinson
Pinterest,
not
here,
so
let
me
cover
for
him.
So
what
Penner
did
is
and
Petter,
please
add
a
link
header
and
worked
on
on
actually
hooks
support
on
the
launch
level
so
that
we
can
modify
the
Dom
extend
well
before
it's
passed
to
differed
and
that's
pretty
nifty,
because
we
can
Pusey
some
stuff
before
it's
really
implemented
in
Qbert
I.
A
A
So
until
the
woman
finds
the
unmute
button,
this
hooks
in
a
container
in
that
container
is
speaking
to
the
launcher
by
our
gr.
Pc
I
think
that's
very
convenient.
Actually,
it
should
fit
well
with
a
lot
of
other
things
like
device
plugins,
which
also
uses
similar
mechanism
and
I.
Wonder
now,
a
woman
if
she
found
the
only
button,
oh
yeah,
so
what.
E
B
A
B
A
A
E
E
The
easy
solution
was
just
don't
under
find
the
domain
when
it's
shutting
down
and
keep
it
because
when
the
ver
10th
Laporte
is
shutting
down,
then
everything
will
be
cleaned
up
automatically.
So
we
don't
need
to
undefined
zero
mind
our
selves
that
worked
so
far.
But
then
the
next
problem
was
when
we
stopped
a
VM
and
immediately
restarted,
we
could
find
an
old
domain.
So
that
was
one
case
which
need
to
need
to
be
handled.
E
A
Ok,
cool
and
the
reason
why
I
put
it
here
is
because
it
was
a
really
visible
thing
of
the
UI,
so
the
problem
was
there
in
the
UI,
as
we
did.
Audition
was
irritated
by
that.
That's
actually
cool
to
see
that
being
fixed,
and
actually
it's
interesting
that
it's
that
the
naive
solution
does
not
work
and
that
it
requires
love.
Love
is
required
always
right.
Well,.
E
A
Cool
then
the
next
thing
I
think
was
worth
mentioning,
but
you
saw
smart
here
is
device
wagons
for
a
VM,
so
we
merged
that
device
plug
in
qiyam
work
few
weeks
ago
to
drop
the
privileges
from
the
pod.
Oh
actually
that
follow
our
topic
and
we
see
it,
but
that
cost
some
magical
changes
so
now
that
we
need
to
explicitly
enable
software
emulation.
C
A
A
B
The
final
solution
which
I
would
prefer
would
be
that
so
one
thing
is
that
a
pretty
common
thing
is
that
the
sockets
can't
community
that
the
listeners
and
the
receiver
from
the
subjects
can't
communicate
easily
because
of
acedemic
styles.
That
should
be
possible
to
be
fixed
without
needing
us
to
do.
Something
like
distributing.
B
A
Wonder
you
said
the
socket
issue:
how
would
you
solve
that
without
this
narrows
it.
C
B
A
Books
in
cubelet
yeah,
so
the
problem
is
that
with
motors
let
or
cute
or
whatever
it
could
help
us
to
set
up
the
devices
the
problem
is,
it
would
depend
on
the
on
the
plug-in.
So
you
know
the
plug-in
would
need
to
have
the
support
to
set
that
up,
and
that
is
what
is
formatting.
What
I
wonder?
Maybe
we
can
have
a
helper
container,
you
know
container,
who
is
already
privileged
a
long
way
after
I
think.
A
There
we
can't
oh,
yes,
I,
didn't
ring
it,
I
mean
the
launcher,
should
be
I
mean
the
launcher.
The
goal
is
ultimate,
you
have
the
launcher
to
be
unprivileged,
but
maybe
we
can
have
a
sidecar
to
the
launcher,
which
is
privileged
to
do
this
setup
in
the
namespace,
because
you
know,
then
we
don't
depend
on
the
network
plug-in.
To
do
I
mean
that
would
mean
that.
B
A
B
Yeah
but
I
mean
I'm,
not
sure
if
you
can
have
set
up
security
constraints,
or
you
can
say
this
container
is
privileged
and
afterwards,
so
this
size
could
contain
is
privileged,
but
the
user
is
not
allowed
to
do
anything
else.
Realism
or
is
I
think
that
it's
fine,
if
you're
Kendall,
is
privileged
in
general,
and
a
lot
of
primitive
Cheeks
extras
can
happen
from
there
on
I
mean
it's
the
same
like
with
the
burdens
on
their
chests
wrote
yet.
B
A
You
know
I
still
try
to
yeah
I,
know,
okay
cool,
but
the
goal
is
still
the
same.
To
see
that
we
can
make
the
lot,
because
that
I
think
is
really
the
goal
with
D.
The
launcher
needs
to
be
unprivileged
in
the
end.
It
must
not
allow
a
user
to
to
do
anything
anything
without
privileges.
Then
you
could
do
from
the
VM
itself
all
right.
A
All
right,
okay,
then,
in
my
own
site,
design
Docs,
so
it
was
offline.
We
discussed
a
few
things
which,
which
we
want
to
see
q''-word
beyond
that
was
word,
are
you
are,
and
she
watchdog
and
PCI
addresses
or
priests,
really
PCI,
dress,
related
topics.
In
the
last
week,
over
the
last
few
days,
I
send
out
the
or
shared
the
documents
on
the
mailing
list
to
give
more
people
insight
into
that
yeah.
E
A
Yeah
indeed,
I
mean
specifically
in
the
port
REO
oranjee
device
designed
on
the
hard
warranty
was
covered
as
a
next
item
outside
of
scope
over
tayo
RG,
but
device
banking
for
aqua
RG
is
definitely
the
way
to
go.
Maya
PB
cos,
it
is
no
dependent
and
device
ring
is
exactly
for
that
to
set
up
something
inside
the
know
who
has
needs
required.
A
Privileges
so
feel
free
to
open
an
issue
to
track
it
and
keep
your
branch
there,
and
you
might
want
to
look
at
better
oranjee
as
well,
but
yeah,
that's
what
you
guys
came
up
with
and
actually
I
think
it's
interesting
beyond
Qbert
hardware.
Rg
is
also
interesting
for
other
workloads,
so
for
the
communities
device
plugins
repository
there.
D
D
A
So
first,
yes,
we
also
and
I
just
edit
that
I'll
add
that
to
the
open
for
to
update
our
live.
Word
I
mean
the
base
image
which
is
currently
Fedora,
317
or
48,
and
actually
also
I've
delivered
four,
which
will
include
an
update
of
Quirino,
and
then
we
should
pretty
much
be
on
on
the
state
of
the
art,
and
that
means
that
we'll
have,
as
watched
over
to
our
G
device,
but
our
RG,
that
we
only
have
the
the
the
Verdi
or
device
right
to
pass
through
a
hardware
number
generator.
But
there's
nothing
else.
B
A
D
I
was
so
the
whole
I
think
that
the
way
that
the
/
test
random
is
done
because
the
like
for
VMs
this
is
in
general
for
a
vm,
so
the
via
the
word
it
it's
down
the
middle
is
that
there's
some
current
module
that
goes
and
picked
up
all
kind
of
numbers
coming
from
physical
things.
You
know
that
you
have
the
enough
entropy
to
generate
right
now
in
the
VM
in
a
VM,
you
don't
have
you
don't
have.
D
With
the
cold
devices
that
you
can
go
and
read
stuff
from
it
can
generate
enough
entropy
so
and-
and
also
you
don't
want,
like
you-
have
the
here-
random,
which
is
not
blocking
but
doesn't
guarantee
entropy
at
the
random
that
it's
blocking,
you
can
get
stuck
there
if
you
want
so
in
the
one
of
the
latest
versions
of
QM,
I
think
what
they
add.
They
have
software
that
create
the
entropy
and
Benandonner
and
running.
You
know
it
sounds
like
slips
like
it's
softer
running
inside
QML
and
emulates
the
physical
world.
D
A
G
Apparently
so
was
completely
redesigned
I
mean
that,
according
the
discussions
with
Nellie
know
recently,
it's
ready
for
being
able
to
test
several
templates.
I
mean
given
their
the
goal
is
to
test
at
least
Santos
and
Ralph's
template
and
in
the
in
downstream
and
the
upstream
at
least
Fedora
and
Sanders.
I
would
like
to
do
it.
Why
skipping
the
Ralph
or
the
upstream,
because
the
community
is
not
important.
G
Nevertheless,
I'm
doesn't
over
there.
It
will
just
skipped
by
default
because
it
does
not
have
raw
image
and
a
local
storage.
So
that's,
and
currently
the
code
is
already
ready.
For
extension,
I
am
breaking
on
the
adding
the
rel
image
to
the
local
storage.
So
it's
done
in
collaboration
with
the
automation
team.
A
Very
good
yeah,
it's
good
that
the
infrastructure,
if
I
understood
correctly
the
infrastructures
no
place
to
make
template
testing
easier.
That's
awesome
because
I
think
I
can
just
highlight
important.
It
is
that
we
test
all
of
our
stuff.
Ideally,
if
I
dream
at
night,
then
I'm
dreaming
a
world
where
we
have
tests
for
all
the
features
we
have
no
seriously
because
especially
presets
and
templates
the
stuff
that
people
are
working
with
and
so
I
think
it's
really
important
that
we
I
mean
for
us
ourselves.
A
So
let
me
praise
the
testing
of
templates
and
presets,
just
because
I
think
it's
really
important
and
oh
yeah.
By
the
way
the
next
step
is
really
I
would
like
to
make
the
templates
increase
paths.
That's
the
proposal
for
me
to
make
it
real
release
content.
So
currently
it's
in
a
demo
content
package,
but
I
would
really
like
to
make
it
release
content.
A
Yeah
last
time
from
or
for
me
today
or
tomorrow,
I
plan
to
do
the
release
zero.
Seven
zero
I
mainly
waited
for
some
stabilization,
because
I
saw
that
some
touches.
What
about
the
CPU
model
and
the
device
plug-in
fix
from
from
studious
turday.
So
I
wanted
to
get
that
in
and
then
I
plan
to
do
a
release
today
or
tomorrow,
just
head
that
that
there
will
be
new
side
release
any
objections.
A
A
We
want
to
discuss
that,
but
then,
on
the
long
run,
I
wonder
if
we
want
to
also
test
container
images
built
on
centroids,
because
I
can
share
that
as
retinas
we
are
going
to
build.
The
containers
based
on
realm
and
sent
to
us
is
closer
to
rel
than
Fedora
is
Tyrell.
So
for
me,
as
a
redhead
er,
it
makes
sense
to
have
images
built
with
the
center
space
and
upstream
and
run
the
CI
against
it,
be
sure
that
it
is
good
for
for
us
and
downstream.
A
B
Okay,
yes,
I
would
prefer
CentOS
or
fedora,
but
in
general,
but
in
general
and-
and
you
know,
my
my
perfect
solution
would
be-
would
be
with
going
for
this
yeah
and
for
that
purpose
also
created
human
static,
builds,
for
instance,
and
the
neutron
test
any
show
any
more
than
you
have
then
you're
building
your
chemo
and
putting
it
in
a
container
I,
don't
have
to
care
what's
below
it.
I.
A
Want
to
say
to
Mia
what
without
going
too
much
into
this
or
less
the
problem
I
have
with
Santos.
Is
that
for
me
as
a
veteran,
it
doesn't
make
much
sense,
because
the
problem
with
centaurs
is
it
is
always
released
after
L.
So
in
order
to
prepare
ourselves
or
Cubert
for
rail
release,
because
we
know
it
is
surfacing
there,
that's
no
secret.
A
A
Can't
speak
about
relayed
I,
don't
know
if
that
name
was
even
mentioned
somewhere.
So
I
cannot
answer
it
at
the
moment,
but
I
can
tell
that
so
far
for
real
self
and
we
saw
that
Fedora
was
a
base
and
so
I
think
features
will
land
there,
and
we
I
mean
it's
also
pretty
obvious
that
features
which
go
to
Vera's
Nora
sooner
or
later,
land
and
rail.
So
that
is
why
I
see
always
Fedora
is
the
base
to
prepare
for
an
upcoming
release
and
then
have
Santo
s
in
the
aftermath
as
the
stable
base.
A
After
all,
the
features
went
in
to
have
that
stable
base.
So,
for
example,
what
I
could
imagine
is
then
we
use
fedora
to
develop
our
master,
but
when
we
have,
for
example,
q''-word
1.0
that
Cubert
1.0
is
based
on
sensuous,
because
then
we
really
want
a
lot
of
stability,
also
inside
the
container
images.
So
what
I
don't.
B
A
Oh
good
yeah,
there
I
think
it
will
be
two
streams
shows
you
know
it's
like
you
know.
We
have
mastered
for
fedoras
so
that
we
can
continue
to
develop
against
upcoming
features
and
then
base
this
stable
release
on
Centaurus,
which
my
Oracle
might
require
a
just
analytics
from
our
respective
issues.
Also.
A
C
A
That
is
a
good
point.
I
think
that
is
what
we
can
sort
out
internally
to
see
at
what
perspective
the
respective
team
has
on
that
okay,
but
that
was
roughly
why
I
think,
indeed
we
might
have
two
streams,
but
it's
too
far,
yet
I
think
that
would
be
something
for
for
one
of
the
eurozone's
like
that,
but
for
now
I
would
love
to
do
if
you
know
twenty-eight
rebase
after
his
release
of
zero.
Seven
at
some
point:
okay,.
B
Okay,
any
there
is
also
overt
and
OpenStack,
and
I
mean
you
can
also
run
them
on
CentOS
or
l
and
so
on
and
normally
I
mean.
So
if
so,
we're
a
pretty
new
project
we're
still
behind.
We
don't
still
don't
have
most
of
the
features
anyway,
so
I
really
want
to
refer
miss
much
if
we
right
now,
so
we
don't
get.
A
So,
to
be
honest,
I
end
up
going
to
send
to
us
at
all
so
they're
well
to
the
official
repo,
it's
actually
special
group
in
Santa
Rosa,
which
is
building
humic
APM
Rev
from
redheads
Rev
product,
which
is
then
delivered
alongside
centrist,
because
Santo
s
itself
has
just
the
plain
cooler
package,
which
does
not
have
all
the
features
enabled
which,
for
example,
over
needs
so
over
this
building
from
the
sources
that
reddit
provides
communicating
Rev
in
order
to
have
the
communitarian
rev
version,
that's
use
for
Rev.
Oh.
A
B
B
There
are
a
lot
of
cherry-picks
expected
for
sale
releases
and
it's
kind
of
annoying
to
do
all
this.
You
know
push
through
that
branch
again
and
created
a
new
pull
request
against
new
source
and,
as
it
turns
out,
Pro
has
already
a
robot
for
that
and
we
could
enable
it.
Then
you
can
write,
slash
cherry
pick
and
the
branch
name,
and
then
it
will
go
there.
Pull
request
for
you
might
pick
up
for,
if
you
like,
you
can
any
with
the
next
day's
gonna
find
a
few
minutes.
I.
A
A
It
so
you
will
see,
then
that
you
know
it's,
then
you
edit,
you
can
just
work
from
there.
So
to
me,
I
would
give
it
a
try.
No
to
me
I
need
to
see,
but
really
or
if
it
works.
For
me,
okay,
but
general
would
be
helpful,
because
cherry
picking
is
a
little
bit
annoying
reminds
me
autumn.
Did
you
do
the
charity.