►
From YouTube: OKD Working Group 2020 01 07 Full Meeting Recording
Description
OKD Working Group 2020 01 07 Full Meeting Recording
A
A
We
do
have
the
dates
and
times
now
for
the
dev
cops,
easy,
ok,
D
working
group
presence.
So
if
you're
coming
to
dev
comp,
which
is
the
conference
in
Reno
at
the
end
of
January,
there
will
be
a
talk
that
Christian
will
be
driving
and
I'll
be
hanging
around
and
adding
living
ad-libbing
to
hopefully
on
the
26.
But
the
okd
working
group
is
actually
on
the
very
first
day
on
January,
24th
and
I
will
set
up.
A
A
to
talk
about
the
okd
relays,
so
that
is
a
free
event
and
it's
open
to
the
public.
So
you
just
have
to
make
sure
you
register,
though,
if
you
want
to
come
come,
and
we
can
all
hang
out
at
lunchtime
together
and
chat
and
have
some
face
time
there
as
well.
So
that's
my
quick
update
if
anyone
else
has
managed
to
get
an
OK,
D
working
group
or
an
OK
D
related
talk,
please
just
let
me
know
at
any
other
conference
and
I'll
do
that.
A
We
should
probably
Christian
also
record
an
open
shift,
Commons
briefing
on
ok
D,
for
once
the
beta
is
out
the
door,
but
that's
a
good
way
to
segue
into
getting
a
update
on
where
we're
at
with
ok
D
for
getting
to
beta
or
any
Christian
so
Christian.
If
you'd
like
to
take
it
away
and
if
you
have
any
slides
or
things
that
you
want
to
drive
through,
please
feel
free
to
take
over
the
screen.
B
Yeah
I
think
we
can
just
just
have
a
look
at
the
engineering
Kanban
board
in
the
open
shift
compared
openshift
organization
on
github.
That
is,
the
ID
had
the
second
one
not
too
much
has
changed
there,
but
we've
been
we've
been
merging
some
PRS
today
of
Adam
and
I,
and
so
there's
progress.
I
hope
we'll
have
most
of
our
CI
issues
fixed
very
soon.
B
A
B
So
there
is
a
test
that
keeps
on
failing
on
on
the
Fedora
base,
OS
Fedora,
core
OS
and
also
on
on
Red
Hat,
us
rel,
seven
I
think
so
it's
it's
a
yeah
I.
Don't
really
know
why
why
that
keeps
on
failing
we've,
we've
escalated
it
to
the
to
the
right
people,
the
right
team,
and
they
should
be
tackling
it
soon.
I
hope
yeah.
But
him
do
you
have
any
update
on
that.
That
was
the
the
networking
thing
that
wouldn't
work
on.
Of
course,.
C
This
one
is
fun,
this
is
about
as
the
NIV
tables
and
I
ICMP.
So,
if
somebody
understands
those
words,
I
could
guide
the
person
to
help
us
fix
the
bug.
But
at
this
point
it's
a
sign,
Thursday
and
theme,
and
we
are
urging
the
SDN
team
to
have
a
look
and
point
us
to
the
right
direction,
but
these
are
the
failing
tests.
C
A
C
A
Okay,
so
Oh
is
there
anything
that
that
I
can
do
to
help
facilitate
or
raise
the
visibility
of
that
is
there.
Somebody
I
should
be
pushing
fight
so.
B
B
B
What
we've
done
right
now
or
until
so
far,
is
just
replace
the
back
to
support
with
spec
free
support,
but
we
will
be
going
away
of
dual
support
where
we,
where
we
can
do
both
yeah
spec,
two
and
also
spec
three
support
I'm
working
on
that
and
that
should
unify
or
help
us
move
one
step
closer
to
unifying
these
the
F
course
and
master
branches
on
the
in
the
MCO
again,
which
would
be
really
nice.
I
I
would
like
to
get
that
into
the
beta
as
well,
but
it's
not
really
a
blocker
right
now.
B
It
would
just
make
things
a
little
bit
easier
in
the
future
yeah
but
I,
but
I'm
not
not
super
confident
we
can
get
the
dual
support
stuff
merged
in
in
master
in
before
the
next
code.
Freeze
just
I
think
yeah
on
the
24th
or
something
24th
of
of
January,
it
might
be
possible,
may
may
have
to
wait
till
the
second
beta
but
yeah
that
that's
really
just
reorganizing
some
code,
making
it
easier
to
work
with
the
OCP
parts
there
and
yeah.
It's
not
nothing
that
should
really
yeah
have
an
effect
on
the
okay
d
clusters.
A
Well,
clean
that
up
a
little
bit,
I
had
one
question
myself,
and
it
is
pretty
basic
here.
I'm
just
want
to
go
in
here
on
the
okay
D
website,
I.
Have
it
written
down
and
I
wrote
this
ages
ago
that
okay
D
release
corresponds
to
kubernetes
distribution
book
ad
1.1
and
we've
been
calling
it
okay
D,
for
whenever
we
talk
about
it,
what
what
is
a
better
phrase?
B
Kind
of
inter
thing
with
yeah,
we
also
need
to
find
just
a
just
a
way
of
describing
okay
D.
Should
it
be
okay,
the
far
or
should
it
be
okay,
the
far
point
x,
4.3,
4.4
or
is
it
just
for
for
me?
I,
don't
really
have
a
strong
opinion
on
this,
because
I
hope
we'll
we'll
get
to
something
like
a
rolling
release
and
then
the
real
version
will
be
will
be
encoded
in
and
in
like
a
pseudo
semantic
version
like
yeah,
like
our
costs
and
f
costs.
D
Something
like
that
with
the
four
dot
family
and
then
probably
just
have
somewhere
in
a
relevant
place
in
the
documentation
which
kubernetes
version
a
you
know.
4.3
includes,
for
example,
because
the
the
text
that
you
have
highlighted
there
has
actually
been
incorrect
for
a
long
time,
because,
okay
d
3.11,
obviously
it's
kubernetes
1.11,
but
we're
not
calling
it
okay,
d
1.11,
for
example,
yeah.
A
C
D
Reference
in
documentation
that
was
actually
more
specific
to
the
branch
and
yeah,
and
just
put
a
note
here
that
you
know
if
you're
working
off
of
the
4.3
if
any
branch
you're
looking
off
of
look
at
the
readme,
that's
specific
to
that
branch
2
you
see
the
corresponding
kubernetes
release.
That's
been
rebased
into
it.
E
A
F
C
C
Have
available,
it
doesn't
mean
we
have
to
change
the
versioning
which
is
being
controlled
by
a
release
controller,
and
you
would
have
to
convince
Clayton
that
it's
important
I,
just
it's
changed
once
during
release
time.
Also.
Yes,
it
changes
during
the
release
time
you
weeks
ago,
for
the
for
has
still
been
based
on
1/16
I
would
really
not
over
complicates
this
I.
E
C
E
B
A
So
what
I'm,
looking
for
and
not
what
I'm
gonna
go
with,
is
what's
in
the
chat
right
now
without
my
typos,
because
I'm
going
to
replace
that
phrase,
that's
on
the
landing
page
with
that.
B
Sounds
good
to
me,
yeah
I
would
also
not
not
overcomplicate
the
versioning
team
right
now.
I
do
think
it's
important
to
know
what
version
of
kubernetes
you're
running
when
you
install
something
but
yeah,
that's
I,
think
the
only
really
important
info
year
and
if
we
can
just
spell
it
out
there
I
like
this
I'm
fine
with
it.
B
A
There
and
and
I
think
it
I
agree
with
Neil
I,
think
it's
in
and
James
and
other
people
I
think
it's
very
important
for
people
to
know
that
quickly
and
easily
what
version
of
kubernetes
that
they're
running
when
they're
running
okay
Dee.
So
that's
you
know
to
me
that
that's
one
of
the
key
things
and
so
I'm
gonna,
just
kind
of
put
in
the
note
here.
A
That
will
get
done
today
and,
let's
see
the
one
back
to
the
I,
didn't
I
lost
that
link.
Sorry
folks,
I.
A
A
Here
ad,
the
latest
okay
d
release-
there's
nothing
in
here
yet
because
we're
not
beyond
beta,
but
is
anyone
working
on
that
yet
or
is
that
just
auto-generated
I
knew
there
was
some
pieces
that
we
had
talked
about
earlier
that
needed
to
get
updated,
okay
D?
Does
anyone
been
working
on
that
to
go
with
the
beta.
C
So
this
one
is
generated
from
open
ship
docks
and
they
ought
to
replace
OCP
with
oak
it
even
the
way
they
had
generate
it.
So
essentially,
we
would
have
the
same
documentation
for
both
products,
which
is
pretty
pretty
much.
What
we
want
I
just,
don't
think
it
needs
to
be
updated
before
we
go
better.
Yes,
yeah.
A
E
I'm
not
sure
I
agree
that
there
should
be
no
okay
documentation
or
for
the
Alpha,
because
one
of
my
friends
actually
over
the
holidays
attempted
to
set
up
okay
D
for
on
bare
metal,
and
he
was
supremely
confused.
There
was
no
documentation
for
it
and
he
got
really
frustrated
until
I
pointed
out
just
go:
read
doctored
open
ship
calm
and
ignore
the
fact
that
that
there
is
no
mapping
of
the
versions
at
all
to
the
okay
t
alphas,
and
that
worked
like
it's
not
intuitive
or
obvious.
A
E
A
A
toss-up
because
it's
a
timing,
issue
too
and
resources
issue,
but
I
think
what
I'm
trying
to
get
at
is
in
the
okay
d1
there's
going
to
be
some
variation
from
the
O's
OCP
stuff
because
of
F
cause
and
I'm.
Just
there's
gotta
be
some
mention
of
that
and
I'm,
not
sure
where
that
goes
in
here.
So
I'll
I'll.
Take
that
as
a
to
do
to
look
at
but
I
I
just
wanted
to
see.
D
Pieces
there'll
be
a
few
more
deployment
options
too
right,
like
the
the
work
that's
being
based
on
metal
cubed
and
live
based
installations
that
right
now
those
are
called
out
as
experimental.
Would
we
expect
that
documentation
to
show
up
in
here,
or
would
we
just
leave
that
in
github
for
folks
that
will
work
in
those
more
edge
cases,
I.
A
Would
I
would
say
for
edge
cases,
I
mean
this
is
Diane's
opinion,
not
read
hats
or
anything,
but
I
would
say
that
metal
cube
in
libvirt
would
remain
for
now
is
edge
cases
and
being
live
in
github,
but
that's
that's
kind
of
what
I'd
liked
it,
and
maybe
we
can
tease
this
out
on
the
mailing
list
a
little
bit
further
to
and
and
I'll
start
a
thread
there
but
I.
That's
that's
my
concern
is
that
I
think
there
is
not
sufficient,
but
a
good
starting
point
in
the
readme
on.
A
B
A
F
D
A
D
Don't
know
I
know
they're,
sharing
a
lot
of
technology
like
ironic
and
some
other
components,
yes,
because
I
haven't
have
done
very
little
with
OpenStack
we're
particularly
interested
in
this
bare
metal
ipi,
because
because
currently
most
of
our
technology
is
still
on
Prem,
we
have
not,
for
various
reasons,
adopted
cloud.
Something
like
this
gets
hypervisor
management
out
of
the
way
for
our
kubernetes
deployments.
D
F
D
A
E
Well,
we
hadn't
actually
started
working
on
the
the
marketing
things
about
the
blog
person
that
for
we're
talking
about
okay,
Dion
F
cos
and
things
like
that.
The
other
thing
is
is
where
what
are
we
looking
for
in
inter
may
have
missed
this?
This
might
have
happened
earlier
and
I
wasn't
here,
but
where
are
we
looking
for
timeline
wise
for
the
okay
T
for
beta.
B
So
the
beta
I
hope
we
can
get
it
out
before
Def
Con
at
the
end
of
this
month.
Okay,
so
we're
looking
at
three
weeks
yeah,
it
really
just
depends
on
how
how
quickly
the
installer
team
can
review
the
Eco
module
migration,
and
then
we
can
rebase
the
F
cos
branch
on
top
of
that,
and
that
would
be
it
yeah.
Okay,
even.
E
B
That's
that
is
very
important
for
the
four
vendor
in
ignition
V,
2
and
V
three.
At
the
same
time,
so
we
need
to
we've
already
moved
to
go
modules
with
the
F
course
branch,
but
we
needed
to
do
it
in
a
way
that
that
didn't
rip
out
any
of
the
existing
infrastructure
providers.
So
that's
why,
in
on
the
F
course
branch
right
now,
we
don't
have
as
your
support
for
it.
A
So
if
we
can
have
all
of
these
documentation
links-
and
so
we
can
start
using
that
as
a
jumping-off
point
for
doing
some
marketing
of
this
release
to
get
more
eyeballs
on
it,
so
writing
that
Fedora,
magazine
blog
posts
and
doing
another
briefing
will
come
from
me.
I
think
that
needs
to
be
the
focus
for
the
first
weeks
of
February,
and
so
that's,
if
you
and
I've
just
come
back
yesterday
from
winter
break,
so
Neal
I'll
I'll
start
me
up
and
working
on
that
fedora
magazine,
post,
I.
G
A
H
F
A
B
B
The
LCP
4.4
is
planned
for
the
summer,
but
we
don't
really
need
to
couple
our
versioning
of
okay
D
with
those
so
that
the
aim
would
definitely
be
to
get
okay,
D,
GA,
okay,
T
for
GA
out
as
soon
as
possible,
and
that
may
even
be
before
OCP
4.4
could
be
around
the
same
time.
I'm
not
really
sure
it
also
just
depends
on
on
the
progress
we're
making
and
on
the
hurdles
we
will
have
to
jump
over,
but
yeah
I
believe
we
could
possibly
do
it
before.
A
This
pegs
the
question
and
I'm.
Sorry
if
I
keep
hammering
on
this
is,
if
I
put
this
phrase,
the
current
alpha,
okay
D
for
release,
which
corresponds
to
this,
should
I
also
put
a
second
line
in
that
says,
something
about
which
version
of
OCP
it
relates
to,
or
is
that
just
utterly
confusing
to
everyone?
Yeah.
B
I
think
that's
just
confusing,
because
okd
is
essentially
the
master
built
from
the
master
branches
of
of
OSI
of
open
shift
and
opened
the
master
branches
of
OpenShift
yeah
I
used
to
build
okd
while
the
well.
The
virgin
branch
is
4.1,
4.2,
4.3
and
so
on
or
release
4.3
am
I
used
for
the
OCP
product.
While
we
build
okd
from
master.
B
B
Yeah,
that
would
be
that's
our
aim.
So
right
now
we
have
orc
or
branched
the
Installer
and
the
MCO
and
they're
not
doing
that
they're.
Actually
we're
actually
trailing
the
master
branches
with
our
F
cross
branches
a
little
bit
because
we
don't
rebase
them
very
very
frequently,
but
that
is
definitely
an
aspirational
goal,
but
I
don't
yeah
I!
Think!
Okay,
do
you
spell
from
yeah
I?
Don't
really
think
we
need
to
say,
but
if
anything
then
okay
D
is
built
from
from
the
master
branches
off
of
openshift
yep.
A
A
E
A
A
Again
I
think
of
it
and
as
James
is
saying
and
I'm
not
James,
you
can
always
unmute
and
say
it
out.
Loud
I
was
talking
to
to
read
things
for
you,
I
think
I
would
love
to
have
a
cent
OS
thing,
but
I
also
would
love
to
have
all
the
resources
coming
to
bear
on
one
operating
just
core
OS
rather
than
multiples,
but
that's
Diane's
aspirational
goal.
A
A
Perfect
all
right,
then
anything
else
people
want
to
bring
up
I
will
get
everything
that
we're
all
the
talks
recorded
at
the
end
of
January
and
up
on
YouTube
for
use
in
blog
posts
and
stuff
and
then
February.
Really
besides
getting
feedback
on
the
beta
to
your
question.
Neil
will
be
the
month
that
we
spend
time
doing
some
outreach
and
publicity
for
okd
for
then
getting
getting
the
word
out
I'm
having
the
documentation,
I.
E
A
I
think
we're
gonna
I
think
this.
This
is
a
much
anticipated
release
and
you
will
be
surprised
at
how
many
people
are
going
to
pay
attention
to
this
and
and
hopefully,
what
that
will
do
will
drive
more
eyeballs
and
engineering
resources
to
both
F
cause
and
an
OK
D
itself,
and
and
then
those
people
who
would
like
the
scent
OS
stuff
that
will
come
here.
A
So
that's
what
I
have
if
there's
nothing
else
for
today,
I
would
ask
if
we
could
start
a
thread
on
around
documentation
on
the
email
list.
I'll
just
make
a
basic
one
asking
for
what
updates
I
should
make
to
the
okay
di
Oh
site
in
terms
of
documentation
and
where
I
should
link
to.
We
can
have
a
debate
about
that
online
and
move
it
forward
that
way
and
I'll
make
some
updates
that
the
okay
di
Oh
site
and
if
anybody
sees
other
things
that
I
should
put
on
the
okd
web
site.
A
E
E
E
H
H
A
Are
the
ones
that
I
don't
stop
working
on
until
til
that
that's
how
I
know
my
day
is
ended
when
I
get
the
ones
on
that
list
done
so
yeah
I
can't
go
home
until
that's
it,
but
actually
I've
worked
from
home
so
I'm
always.
This
Joseph
is
asking
a
dusty
a
couple
of
Korus
questions
here
you
want
to
like.
A
H
I'm
sorry
I'll,
look
at
this
I'll.
Look
at
the
questions
go
away,
it's
in
the
chat.
So
as
far
as
when
will
it
be
released,
I
think
all
we
can
say
right
now
is
soon
we're
doing
some
enable
Network
for
the
stable
stream,
but
we've
always
had
a
policy
of
not
really
giving
exact
dates
for
things,
because
it's
community
right
so
dude
on
that
one
and
joined
our
weekly
meetings.
If
you
want
to
see
progress
updates
on
that
those
happen
on
Wednesdays
and
1630
to
check.
A
H
Yeah
another
thing
to
so
I
think
there
was
one
other
ticket
that
you
had
in
there.
That
was
related
to
me.
I
think
it
was
related
to
GCP
and
I.
Don't
have
access
to
edit
this
board,
so
I
I
try,
I
was
gonna,
go
in
and
then
I
I
can't
actually
go
in
and
auger
questions
I
won't
be
able
to
update
this
one
either.
H
H
A
A
D
A
H
G
A
Adora
world,
if
you
like
perfectly
this,
is
the
one
that
I
use
to
set
the
agendas
for
meetings
all
right,
guys,
I'm
gonna.
Let
you
go
back
to
your
days
and
again
welcome
to
2020
and
it's
gonna
be
a
big
year
for
okay,
d4
and
I
am
looking
forward
to
seeing
as
many
of
you
as
possible
in
this
next
year.
Peon
tour
I'm
at
Def,
Con
fan
in
London.
So
if
you
are
coming,
please
let
me
know,
and
let's
hang
out
and
get
some
based
on
yeah.