►
Description
OpenShift Commons Gathering
Milan Italy 2019
Title: OKD: Current Status & Roadmap Version 4 and Beyond
Presenter: Christian Glombek
B
A
Of
the
engineering
liaison
for
wrote
for
Red
Hat
engineering,
maybe
we'll
start
off
well,
first
I
have
to
say
I.
Think
I've
never
done
a
presentation
in
front
of
that
many
people.
So
excuse
me
if
I'm
a
bit
jittery
I'll
start
this
off
with
a
little
explanation
of
what
okd
actually
means.
Does
anybody
know?
A
Ya
so
I
think
it's
the
OpenShift
community
distribution
part
by
kubernetes
officially,
but
it's
not
an
acronym,
so
okay,
Diane
is
probably
the
best
we've
got
so
far.
All
right,
let's
get
going
the
agenda
today,
will
be
okay
before
the
roadmap.
Then
I'll
tell
a
little
bit
about
the
current
status
where
we're
at
right
now
and
then
a
little
introduction
to
the
okd
working
group.
So.
A
Okay,
the
four
roadmap:
now
we
developed
a
few
guidelines
that
would
always
have
to
be
valid
for
okd
releases.
Everything
on
the
roadmap
is
still
not
formally
agreed
upon
and
may
be
subject
to
change,
but
these
are
the
things
we
thought
internally
and
also
with
some
community
members
would
make
sense
to
to.
A
To
always
have
have
have
be
true,
so
that
would
be
we
use
ignition
version
3
or
the
spec
version
3,
which
currently
OCP
runs
on
spec,
so
we'll
with
okd
will
start
from
spec
3
right
away
and
then
we'll
always
support
F
cross
as
a
bootstrapping
node
host
operating
system.
So
we
can
always
say
Oh
kitty
will
run
on
F
course.
That's
not
doesn't
have
to
be
exclusively,
but
it's
one
system
that
we
always
want
to
support
with.
Okay,
D
F
course
is
Fedora
core
OS,
so
the
OCP
platform
is
our
costs.
A
Red
Hat,
core,
OS
or
rel
cost,
there's
different
names
for
it
and
as
it's
not
the
standalone
product,
it's
not
really
a
thing,
but
in
fedora
world
we
have
the
Fedora
core
OS,
which
is
sort
of
the
Fedora
atomic
successor
yeah.
So
we
want
to
avoid
unnecessary
divergence
in
our
kitty
from
from
OCP.
We
want
to
at
least
for
our
initial
release.
A
So
that's
where
we're
at
right
now,
I'll
come
back
to
this
in
a
bit
in
the
midterm,
which
is
sort
of
the
the
end
of
that
term
will
be
the
first
general
release,
which
I
hope
we
can.
We
can
make
happen
in
the
first
quarter
of
next
year.
No
promise
but
I,
think
I
think
we
run
a
good
way
to
get
there
so
in
in
phase
one
we'll
just
do
a
little
bit
of
hardening
more
CI
testing,
adding
things
to
make
sure
that
our
release
is
actually
actually
working.
A
A
A
So
all
of
these
are
so
sort
of
to
facilitate
contributions
from
the
community
and
the
the
goal
behind
this
in
the
end
is
to
make
to
make
okd
is
super
set
a
functionality
that
flows
into
OCP
and
what
we
want
to
do
really
is
we
want
to
use
the
same
code,
so
we
don't
want
to
branch
and
diverge
too
much
from
from
OCP.
We
just
want
to
build
it
on
top
of
fedora,
for
the
initial
release
and
later
I'll
come
to
that
there
may
be
sub
working
groups.
That
will
do
that
will
enable
more
OSS.
A
So
we've
definitely
thought
of
that
and
want
to
make
want
to
facilitate
that
and
enable
that
help
enable
that
if
you
want
to
have
a
look
at
the
roadmap,
it
is
did
I
put
the
source
yeah,
there's
a
little
source
thing
down
here.
I'm
sure
you
can't
read
it
so
right
now
it's
a
draft
and
we're
gonna
propose
or
do
a
call
for
agreement
in
the
working
group.
So
I'll
link
to
the
working
group
Leila
you
can.
A
So
right
now
we're
setting
up
CI
for
rpm
builds
of
OC
and
hypercube.
Those
are
dependencies
on
the
our
cost
side.
On
the
OS
side
of
OCP-
and
we
want
to
package
them
continually
over
the
CI
system
for
fedora,
so
we
can
use
them
in
the
Fedora
core,
OS
composes
and
then
the
second
thing
that's
gonna
be
unblocked
very,
very
soon,
probably
next
week
it's
when
we
switch
to
4.3
master
branches.
We
can.
A
We
will
be
starting
to
work
on
the
readying
of
the
Installer
and
the
operators
for
the
ignitions
back
3,
which
is
especially
the
Installer
and
the
Machine
config
operator
will
have
to
be
yeah.
They
have
to.
They
have
to
be
ready
for
spec
3,
which
they
aren't
yet
so
there's
some
some
changes
in
there
coming
and
after
that,
we
can.
If
those
windows,
two
already
will
be
in
phase
one,
which
is
all
these,
things
should
be
ready
and
we'll
do
some
hardening
before
the
release.
A
Right,
the
next
point
on
the
agenda
is
I'd
like
to
very
shortly
introduce
the
ok
D
working
group,
I'm,
not
sure
I
wasn't
here
in
the
in
the
morning,
and
you
probably
introduced
the
working
group
a
little
bit.
I
thought
I'd
I
just
do
that
as
well
from
my
for
my
point
so
we're
right
now
we
formally
came
together
the
first
time
what
we
agreed
upon
a
charter
with
which
is
our
governing
document
last
week,
and
so
we're
formally
a
working
group.
Now
Diane
is
the
community
chair.
Then
we
have
Danny
come
Nayef.
A
A
We
have
the
repository
so
if
you're
interested
in
contributing
or
just
staying
up
to
date,
I'd
suggest
you
follow
that
repo,
because
all
the
agreements
will
be
at
will
be
made
as
issues
or
PRS.
On
that
repo.
We
also
have
Google
group,
which
serves,
as
our
mailing
list,
we'll
make
sure
to
always
send
out
the
information
on
the
other
mailing
list,
the
openshift
users
and
open
ship
deaf
mailing
list
as
well.
A
But
this
one
is
really
a
bit
more
focused
on
the
Oh
kitty
for
effort
right
now,
so
you're
also
invited
to
to
join
that
group,
and
then
we
have
a
slack
channel
as
well,
which
is
the
one
you
may
know
already
open
ship
deaf
on
on
the
kubernetes
slack.
We
also
have
a
biweekly
meeting
which
you're
invited
to
join
and
say
hello
to
as
well
I
think
we
don't
have
a
calendar
yet,
but
we'll
set
up
one
real
soon.
So
you
can
subscribe
to
that
and
you're
definitely
welcome
to
say
hello
on
the
meeting.
A
A
B
So,
okay,
D
and
Origen
have
been
around
for
a
long
time,
but
what
with
the
4.0
upgrade
to
the
operators
is
a
big
shift
in
the
way
that
we're
deploying
openshift
and
okay
D,
and
that
is
really
impacted
on
the
delivery
of
okay
D,
for
because
we
have
to
refactor
it
to
run
on
F
cause
or
Fedora
core
OS.
So
how
many
of
you
there
were
few
of
you
in
the
room
that
were
okay,
D
users?
It
was
a
couple
of
you
there
you
go
all
right,
all
of
you
good
folks.
B
We
love
you
all
and
we'd
really
love
to
have
you
take
a
look
at
the
Charter,
not
the
Charter,
but
the
roadmap
and
help
us
make
sure
that
we're
on
the
right
path
and
if
you
have
extras
engineering
cycles,
we'd
love
to
have
as
soon
as
we
get
these
first
rpms
out
and
this
first
delivery
of
phase
is
zero.
We'll
be
sending
an
announcement
out
to
the
openshift
Commons
list,
the
dev
lists
the
users
was
just
so
we
can
get
as
many
of
you
to
test
and
play
with
it
as
possible.
B
B
Will
be
a
version
of
Fedora
core
OS
that
that
we
can
work
with?
So
this
is
another
one
of
those
and
at
the
beginning
you
missed
it.
My
jellyfish
diagram,
the
interdependencies
of
open
source
projects,
really
come
into
play
in
coordinating,
so
we
have
people
from
Red
Hat
who
are
engineers
working
on
the
Fedora
core
OS
effort
on
the
okd
on
the
operators.
We
have
people
and
ignition
there's
a
lot
of
those
people
are
the
same
people
but
anyways.
A
B
Have
some
travel
issues
somebody's
going
on
PTO
and
yep?
They
usually
are
around
1700
UTC
that
we
may
shift
it
a
little
bit
earlier
to
do
that,
so
we're
trying
really
to
accommodate,
as
many
of
you
as
possible,
to
come
in
and
participate
and
give
us
feedback
on
this,
because
it
is
one
of
the
biggest
initiatives
that
we've
had
on
the
open
source
side
that
really
needs
as
much
community
support
as
possible.
So
we're
really
happy
there's.
B
A
Out
the
okd,
a
working
group
is
really
going
to
be
I.
Hope
is
really
gonna,
be
a
group,
a
platform
to
to
really
be
on
the
edge
of
development,
to
really
test
out
new
new
cool
stuff
and
get
that
into
okay,
D
first
and
actually
have
it.
Have
it
testable
and
so
yeah
I
think,
there's
lots
of
interesting
stuff
coming
like
supporting
more
platforms.
B
B
A
B
Other
thing
that
I
would
like
you
to
just
keep
holding
up
the
applause
ruin.
The
other
thing
that
I'm
going
to
mention
is
because
I
have
to.
We
have
5
minutes
before
lunch
is
ready,
so
I'm
just
going
to
keep
doing
this
so
walk
slowly
to
the
lunchroom.
The
code
ready
containers
we're
going
to
make
sure
that
that
they
we
have
a
version
of
that
that
supports
ok,
d4
when
we
come
up
with
a
release.
So
if
you
start
playing
with
okay,
D
containers
now
you'll
be
ready
to
work
with
that
on
ok,
t4
I'm.
A
Not
sure
we
can
make
the
quadratic
containers
release
for
the
initial
release,
but
it's
gonna
come
at
some
stage
with
the
quadratic
containers,
there's
just
some
things,
with
the
lipfird
support,
and
also
being
just
one
node
with
just
one
node
cluster
that
isn't
really
supported
too
well
by
it
by
the
operators
right
now.
But
we.
B
Will
get
there?
The
other
thing
is
everything
that
we
do
in
the
ok
D
working
group.
Again,
I
mentioned
it
earlier.
We
record
everything
is
open.
You
can
join
the
ok
D
working
group
on
Google
Groups,
it's
an
open
community,
but
all
of
the
video
every
meeting
is
recorded.
So
if
you're
not
in
the
right
time
zone-
or
you
want
to
watch
this
in
the
the
privacy
of
your
own
homes,
on
the
weekends,
because
it's
so
exciting,
you
can
go
to
our
H
OpenShift
on
YouTube
and
look
for
the
ok
D
working
group
playlist.
B
So
some
of
the
conversations
are
really
sort
of
bleeding
edge
and
really
interesting,
at
least
to
me
and
like
stuff
with
the
code
ready
in
the
libvirt
conversations
and
we've
been,
will
be
having
people
from
the
metal
cube
and
the
code
ready
team
coming
and
talking
at
the
next
one
about
how
to
make
these
things
all
happen.
Meet
new
people.