►
From YouTube: OKD Working Group 2019 12 10 Full Meeting Recording
Description
x3
A
A
A
A
A
A
A
With
the
first
note,
that's
on
the
proposed
agenda
items
here
for
those
of
you
who
are
coming
to
Def
Con
and
the
Bruno.
We
did
get
our
talk
accepted,
which
is
great
and
we
did
get
a
meeting
room
assigned
to
us
what
we
still
don't
have
a
date
for
that.
We
also
got
a
table
to
do
outreach
at
in
the
lobbying.
If
any
of
you
have
been
to
dev
comp,
that's
sort
of
where
everybody
congregates
in
between
sessions,
so
that's
and
it
will
be
next
to
the
kubernetes
table
as
well.
A
So
we
can
share
and
cross
populate
and
have
other
people
come.
So
if
you
are
planning
on
coming
to
Def
Con,
please
let
me
know-
and
we
will
incorporate
you
into
all
of
that,
so
we'll
have
a
face-to-face
meeting
there,
a
Fishman
official
one
and
put
that
out
over
blue
jeans.
As
well,
so
if
anyone
needs
links
to
that,
that
is
a
really
easy
link.
I'll
put
that
in
chat.
Well,
yeah
you've
got
it
there.
Did
we
get
a
room
too?
Let's
see
what
that
one
is.
Yes,.
B
B
C
A
Let
me
just
see
if
I
can
find
the
London
Bolton
shift
Coleman's
gathering
here
and
in
San
Diego
we
did
a
very
nice
or
Christian
who's.
Just
bumping
on
on
and
off
did
a
very
nice
lightning
talk
before
the
lunch,
and
so
we
wanted
to
get
I,
think
Christian
and
it
and
Danny
just
gave
regrets
he's
in
another
meeting.
So
he
can't
come
if
anyone
is
planning
on
going
on
January
29th
or
is
in
the
London
area
on
January
29th.
A
So
that's
the
next
Commons
event
that
we
have
that
I
have
that
I
can
offer
up
if
people
have
other
events
that
they'd
like
or
that
they're
attending
that
they
want
to
promote
okay,
D
or
Fedora
core
OS,
please
let
me
know,
and
I
will
do
what
I
can
to
support
you
and
and
get
get
us.
You
know
schwag
or
whatever
else
it
is.
We
need
to
that
event.
B
A
A
So
there
will
be
that's
I,
think
March,
thirtieth,
twenty
twenty,
so
there'll
be
an
okay
d
presence
there
and
we'll
probably
do
a
pretty
much
a
full-court
press
there
for
okay
d
and
we're
working
on
getting
like
I,
don't
know
little
pandas
with
okay
D
stitched
on
it
swag
to
promote
okay,
D,
so
hopefully
by
March
30th.
We've
got
all
of
our
ducks
in
a
row
and
a
nice
stable
for
release
to
promote
and
and
get
some
talk.
So
that's
my
quick
outreach
and
announcements.
A
B
D
B
B
Think
much
has
changed
on
that
board,
though.
So
what
I've
been
doing?
The
past
we
of
the
past
two
weeks,
every
day's,
the
the
MCO
F
cross
branch,
so
we're
a
little
bit
more
up-to-date
there,
unfortunately,
we've
been
having
troubles
with
CI
and
we
couldn't
really
get
anything
merged
elsewhere,
which
is
why
there's
been
lots
of
things
getting
prepared,
but
we
haven't
really
gotten
them
in
so
far.
B
B
So
once
these
two
things-
land,
I
think
which
is
hopefully
before
end
of
year
of
very
early
on
next
year,
we'll
be
able
to
cut
it.
I
think
I
call
that
a
beta
release
then
already
so
there
is
progress.
It's
not
really.
It
can't
really
be
used
at
the
moment
because
of
our
CI
troubles,
but
then
I
hope
we'll
be
able
to
resolve
that
very
shortly.
A
B
So
yeah
it's
it's
ok,
d,
specific
in
that
case,
and
I
think
it's
just
some
configuration
issues
that
we
promoted
the
wrong
images
and
you
know
we're
building
on
on
the
wrong
images.
So
we've
unblocked
all
of
these
issues
actually
but
I
think
my
team
today
found
another
issue
in.
Was
it
Prometheus
I'm,
not
sure
what
what
component?
It
was.
Some
component
that
now
blocks
the
eye
for
us
and
that
might
may
actually
be
be
important
for
all
of
open
shifts.
Ti.
B
Maybe
madam,
can
give
a
little
bit
more
detail
on
that
yeah
other
than
that.
So
the
in
review
thing
yeah,
the
in
review
column,
hasn't
really
changed
because
we
weren't
able
to
move
anything
from
the
review
stage
to
to
done
because
it
hasn't
been
merged
you
to
do
to
that
yeah,
the
rebase
in
the
rebase
f.cuz
branches
of
MCO
that
has
been
done
and
the
Installer
branch
is
still
in
a
PR,
that's
waiting
to
get
merged
and
then
the
second
thing
there
is
the
thing
I'll
tackle
next
I
I
hope
I'll
get
to
that.
B
Yeah
I'll
probably
start
with
that
tomorrow,
because
the
Installer
thing
is
also
ready.
Now,
but
it
needs
to
be
reviewed
and
there's
some
pending
PRS
in
dependencies
that
get
I
have
to
get
merged
before
I,
so
I'll
tackle
that
next
and
yeah
I
think
that's
once
we
have
that
second
card.
There
are
the
well
that's
actually
the
PR,
the
ignition
spec
v2
conversion
and
I'll.
Add
to
that
also
spec
3
conversion.
B
A
E
Can
elaborate
more
on
tests
and
some
more
status?
So
the
issue
now
is
that
the
fresh
content
from
Oh
kitty
4
is
failing
to
test,
which
we
depend
on
and
we're
lucky
that
those
tests
are
reflecting
OCP
as
well,
the
ones
these
are
fixed
by
our
developers.
We
would
get
them
automatically
in
LGD
and
would
move
on
further.
So
during
this
week's
mean
clades
and
were
working
on
release
promotion,
our
oak,
it
is
now
also
tracking
the
future
foreign
tour.
E
So
we
don't
need
additional
work
here
and
builds,
and
four
and
four
and
four
three
should
automatically
get
fresh
update
from
Knightley's
of
open
shifts
and
another
area
I
worked
on
was
adding
new
platforms,
so
we
have
two
PRS
for
vSphere
and
live
birth
support.
Our
platforms
would
need
a
little
bit
more
work
of
using
the
upstream
repos
other
than
rail
repos,
but
we'll
get
there
soon
and.
B
B
A
B
For
testing-
and
it
should
also
reflect
like
there
won't
be
huge
changes
in
the
structure
of
anything
after
that,
because
with
then
we're,
then,
in
a
place
where
we
just
have
one
MCO
branch.
We
use
for
everything
and
the
Installer
branches
shouldn't
diverge
too
much
so
it'll
be
easy
to
rebase
them
regularly
and
even
maybe
even
we'll
get
to
somewhere,
where
we
can
sort
of
add
a
flag
to
installer,
which,
which
tells
it
to
either
use
the
Archos
base
for
OCP
or
the
F
cos
base
for
okay,
D
and
yeah.
F
A
B
A
B
Is
a
PR
open
on
the
okd
repository
right
now,
which
is
sort
of
troubleshooting
I,
think
which
will
help
get
get
people
started?
I
hope
we
should
definitely
flash
everything
out
a
little
further,
but
maybe
that
is
that'll
suffice
in
the
in
the
short
term
yeah
and
then
because
it
we
do
have
a
lot
of
documentation
for
OCP,
and
most
of
that
is
also
valid
for
okay
D.
A
A
I'll
tell
you
Gleason
I
will
reach
out
to
you
and
and
we'll
see
this
so
that
you
know.
Basically
what
I'm
looking
to
do
is
get
this
run-through
and
make
sure
that
it's
appropriate
for
and
I,
don't
think
it
is
because
I'm
pretty
sure
what's
new
is
here
is
the
overview,
is
a
three
dot,
something
or
other
stuff
yeah
b3.
A
A
A
A
A
A
B
A
So
the
idea
behind
this
was,
if
you
are
testing
on
OpenStack,
to
add
your
comments
and
feedback
in
these
areas
so
that
we
can
track
them
by
the
platform
that
you're
testing
on,
and
we
know
that
someone
is
testing
on
that.
So
I
know
Neil
and
others
have
had
specific
things.
If
your
type
of
platform
isn't
there,
let
us
know
and
we'll
do
that,
but
we
would
love
you
to
start
adding
any
feedback.
Positive
is
good
and
into
into
here.
If
you
could,
that
would
be
helpful.
A
So
I'm
gonna
go
back
to
the
agenda
and
see
if
I
can
find
it
again
wondering
what
else
we
need
to
cover
off
today
I
mean
we
talked
about
the
documentation,
I
started
a
draft
with
Neil
and
other
folks
on
the
Fedora
magazine.
It
hasn't
gotten
very
far
but
I
think
that's
our
Christmas
holiday
thing
and
then
once
we
have
an
outline,
we
can
propose
it.
I
took
a
look
at
the
Fedora
process
magazine
process
and
basically
you
proposed
it
and
if
they
say
yeah,
then
they'll,
then
you
continue.
A
D
D
D
The
first
attempt:
I
check
it
logs
on
distillation
and
check
out
the
terraform
output,
and
it's
pretty
much
the
same
as
we
would
get
on
an
OCD
installation
and
getting
to
the
console
and
checking
the
resources
and
everything
seemed
quite
far
with
what
we
would
get
from
an
Asif
installation.
So
I
I
didn't
prepare
anything
for
this
week,
but
I'm
happy
to
prepare
like
a
walkthrough
for
next
time.
You
would
like
dying
yeah.
A
That
would
be
great,
and
what
I'd
like
to
do
is
is
record
it
as
a
video
on
how
to
you
know,
basically
how
to
deploy
ok,
d4
on
AWS
and
have
you
talked
through
it,
so
we
can
have
some
of
that
content
and
maybe
even
just
transcribe
it
in
some
way.
But
that
would
be
wonderful
if
we
could
do
that
for
the
next
one.
I
noted
that.
A
And
if
we
don't
do
it
in
the
context
of
the
okd
working
group
meeting,
you
and
I
can
do
it
as
a
blue
jeans
thing
separately.
If
it
doesn't
work
out,
maybe
as
soon
as
you're
ready
and
then
we'll
have
the
video
and
people
can,
we
can
watch
it
together
on
the
okd
working
group
meeting,
but
that
anytime,
that
you
have
I'm
on
West,
Coast
time
and
I
know
your
East
Coast
Brazil
time.
So
we
can
figure
out
something
and
record
that
beforehand
sooner
the
better.
D
A
B
Me
throw
in
here
Thank
You
glades
and
thank
you
all
so
Joseph
for
reporting
errors
and
everybody
else.
Who's
who's
reported
back
with
their
troubles
or
successes.
That's
awesome,
and
you
need
more
of
that.
So
thank
you
very
much
for
all
the
feedback,
it's
very
valuable
to
us
and
keep
on
doing
it.
Please.
A
G
F
A
A
A
A
F
B
So
with
the
rebase
or
with
ego
module
migration
I'm
doing
and
once
we
rebase
the
installer
F
Coast
branch.
On
top
of
that,
we
should
read
p.m.
to
re-enable
all
the
platforms
that
are
also
available
with
OCP
right
now
we
had
to
rip
out
the
azure
support
to
get
okd
going
and
yeah
once
once.
That
is
done.
I
hope
very
shortly.
I
hope
this
month,
it'll
get
in.
We
will
be
able
to
really
have
at
the
Installer
branches
branches
closer
to
each
other
and
have
all
the
same
platforms
in
OCP
and
ok
d,
yeah.
F
So
the
big
one
free
for
my
personal
usage
for
using
over
our
sorry,
open,
ok,
D
on
my
personal
systems,
my
personal
systems
are
overt
and
that's
I.
Would
that's
the
one
that
I
intend
to
do
a
lot
of
my
testing
and
experimentation
with
here
at
work?
We're
we're
looking
at
rolling
out.
Ok
D
on
OpenStack,
so
both
of
those
are
things
that
that
I
care
about
very
deeply
and
OpenStack
is
kind
of
broken
right
now,
the
last
time
I
checked
so
I
need
to.
E
Openstack
needs
would
be
rebuilt
basically
because
currently
the
OCP
uses
the
red
have
supported
OpenStack
packages
and
we
cannot
use
it.
You
know
this
have
to
be
revealed
based
on
our
deal.
That's
on
the
table.
That's
apparently
the
only
blocking
thing
to
roll
out
the
OpenStack
support,
Inoki,
okay,.
B
F
H
F
E
C
B
We
may
actually
lead
the
OpenShift
support
on
the
AR.
Do
support
with
okay
d
on
on
that,
because
yeah,
once
we
have
the
installer
rebase
on
the
second
one
that's
coming
now
we
have
one
rebase
sort
of
in
the
in
the
pipeline
right
now
from
a
team
and
then
with
eco
module
migration.
There
will
be
another
one
yeah
late
this
year
or
early
next
year
and
from
there
on
I
think
we
can
actually
lead,
because
we
don't
really
we
can.
B
A
A
little
bit
of
arranging
them
things
and
then
is
char
on
the
call
this
time
no
wasn't
able
to
like
to
check
and
see
with
this.
Oh
he's
done
the
middle
three
stuff
as
well,
so
hopefully
they're
getting
most
of
these
things
going
I
think
what
else
we
should
be
talking
about
today.
We
still
have
an
open
request:
a
working
group
liaison
another
someone's
woman
and
drive
this
along
with
Christian
and
that
hasn't
been
resolved,
yet
so
from
the
Red
Hat
side,
but
we're
working
on
it
moving
through
the
open.
B
Yeah
I
think
maybe
we'll
get
get
past
needing
needing
those.
Actually,
once
we
re
the
MCO
branch
and
there
won't
be
much
extra
work
there
and
on
the
Installer
side
I'll,
my
buddy
Matt
I
will
probably
handle
that
and
I
don't
know
what
other
teams,
maybe
the
are
do
team
now
I
need
to
be
involved.
Maybe
the
for
the
are
do
team.
It
would
make
sense
now.
A
Those
people
then
get
that
get
a
meeting
set
up
about
that
I'm
wondering
what
else
we
should
be
doing
in
terms
of
outreach
and
getting
more
getting
more
things
tested.
Scuse
me
getting
more
Tom
feedback
on
testing.
If
there's
a
platform
that
we
didn't
cover
today
and
that
I
should
be
trying
to
track
someone
down
to
do
I
think
maybe
in
January
prior
to
dev
comp.
What
I'd
like
to
do
is
host
an
okay,
D
working
group
meeting.
A
We
get
a
we're
sure
that
the
the
documentation
and
we've
got
a
steady,
that
a
preview
that
Christian
is
is
looking
is
looking
good
is
to
do
a
call
out
to
all
of
the
Commons
members
to
the
main
mailing
list
to
to
take
a
look
at
the
install
stuff
and
if
they
are
interested
in
it
and
then
have
them,
maybe
come
to
a
meeting.
That's
just
for
people
who
want
to
do
testing
if
in
early
January,
maybe
this
second
week
when
everybody's
back
and
try
and
focus
people's
attention
on
ok
D
for
beta
testing.
A
A
B
B
A
B
I
No,
we
do
not
have
a
Fedora
core
OS
on
sure,
I.
Think
I,
don't
know
if
we
are
outputting
it
in
our
artifact
list,
but
if
you
build
it
and
upload
it
yourself,
I
think
it
should
work.
Our
problem
is
that
we
cannot
right
now
because
of
terms
and
conditions,
upload
images
for
everybody
to
use,
so
we're
working
we're
trying
to
get
access
to
be
able
to
do
that
through
bread,
athlete
I'm,
not.
A
D
I
B
A
B
Not
really
help,
but
there's
one
one
thing
that
Mohan
booth
from
the
Fedora
community
when
I
met
him
last
month
in
in
Boston,
suggested
that
we
set
up
an
okay
plaster
for
the
Fedora
community
to
use
and-
and
you
know,
tinker
with
or
run
essentially
run
their
own
stuff
on,
and
he
I
think
he
offered
some
help
with
that
and
I'd
be
interested
as
well
in
in
setting
that
up
and
maybe
maintaining
it
as
well.
So
at
Def
Con
in
Bruno,
we
were
going
to
meet
and
talk
about
that.
So
anybody
who's.
B
F
And
I,
just
in
general,
I'd,
be
happier
seeing
less
and
stuff
on
in
the
Fedora
community,
dependent
on
rel
and
more
self
hosting,
because
we're
kind
like
it's
just
kind
of
bad
when
we
can't
even
find
out
that
we're
causing
with
that,
we
can't
even
think
our
own
problems
so
being
on
platform
being
able
to
run
our
infrastructure
on
our
own
distribution,
makes
it
so
much
easier
for
us
to
fix
their
own
problems
because,
quite
frankly,
the
rel
guys
don't
care
enough
about
our
problems.
So
it's
nicer
when
we
can
fix
them.
B
A
A
Won't
be
too
bad
for
you,
then
I
think
it
was
three
to
four
three
to
five
or
something
like
that
so
cool.
So
our
next
meeting,
if
we
were
on
a
two-week
cadence,
was
going
to
be
the
week.
That's
shut
down
for
everybody
here
at
Red,
Hat
and
full
tilt
into
the
holiday
season,
and
so
I
would
propose
I
think
the
next
one
we
were
thinking
about
doing,
destroy
January
seventh.
A
If
I
can
move
that
conversation,
quick
least
and
and
gather
people's
thoughts
about
helping
with
the
documentation,
there
might
be
a
little
education
process
on
how
to
make
pull
requests
and
stuff
like
that.
That
needs
to
happen,
but
otherwise
January
7th
will
be
a
will,
be
our
next
meeting
unless
someone
objects
strenuously
to
that,
and
so
don't
I
come
back
to
work
on
the
six
I
think
most
of
most
Red
Hatters
do
mmm-hmm
so
and
think.
A
That's
all
we
have
now
or
today,
unless
someone
wants
to
jump
in
and
ask
another
question
or
offer
more
resources,
thanks
Tim
for
that
offer
and
just
keep.
If
you
can
put
your
issues
into
the
okay
D
under
the
category,
for
whatever
platform
you're
playing
on,
including
maybe
the
Azure
thing
or
the
Fedora
core
OS,
that
would
probably
be
a
good
place
to
keep
track
of
it
for
now
or
dusty,
somewhere
in
Medora,
core
OS
or
blend
issues
as
well.
So
we
can
keep
track
of
that.
One.
A
If
you
can
in
this
note,
if
you
end
up
logging,
an
issue,
if
you
can
just
put
the
link
to
the
issue
in
here-
and
this
note,
that
would
be
great
okay
and
then
we
can
track
it.
Alright,
folks,
I,
don't
want
to
keep
you
longer
than
we
have
to,
and
hopefully
we'll
just
keep
motoring
on
in
Christian
and
daddy
won't
burn
out
on
us,
so
I'll
just
keep
using
the
the
chat
and
the
and
the
mailing
list
to
reach
out.