►
From YouTube: OKD Working Group 2021 03 30 Full Meeting Recording
Description
OKD Working Group 2021 03 30 Full Meeting Recording
https://okd.io
https://groups.google.com/forum/#!forum/okd-wg
A
A
Another
one
nope
nope
nope
nope,
okay,
the
working
group
link
back
to
stirring-
and
this
is
the
bit
that
I
always
end
up,
cutting
off
at
the
beginning.
While
we
get
ourselves
set
up,
but
if
you
could
sign
in
that
would
be
great,
and
I
will
motor
on
here
and
share
my
screen.
We've
got
quite
kind
of
a
few
people
coming
summertime,
maybe
killing
a
few
things.
Hey
neil
welcome.
A
Joined
an
hour
early,
you
get
the
prize
for
not
getting
with
the
daylight
savings
time
still
so
welcome
philip,
and
I
this
time
I
decided
not
to
open
a
second
an
earlier
session
just
to
catch
all
of
you
but
hey
you
still
came
so
yeah.
Today
we
have
a
a
new,
stable
release
out,
I'm
going
to
share
my
screen,
so
we
just
sort
of
drive
through
the
team
working
group
meeting.
A
C
C
C
Another
issue
with
head
was
that
during
upgrade
process,
if
you're
using
a
fake
ball
secret
machine,
config
demon
would
first
attempt
to
use
oc,
and
if
the
pull
secret
is
invalid,
as
in
you're
not
using
a
base64
part
in
the
authentication
section,
it
would
fall
back
to
podman
and
try
to
do
the
podman
copy
again.
That
would
fail.
So
we
have
a
bug
file
to
that
and
the
workaround
is
simply
to
use
a
valid
base64
part
in
the
secret.
A
C
E
F
B
E
B
B
C
B
E
E
B
G
G
B
G
B
C
A
So
quick,
quick
question
is
this
something,
and
maybe
joseph
can
answer
for
me
I'll
suggest
that
joseph
is
this
something
that
we
should
with
the
release
put
in
a
blog
post
like
which,
which
is
the
stable,
fedora
core
os
and
this
pull
secret,
or
is
there
a
note
somewhere
in
the
issues
with
this
release?
That
has
this
information
in
it
so
that
people
are.
E
So
the
f
cost
thing,
though
it
looks
like
the
back
port
request,
has
been
verified
and
is
basically
being
prioritized
to
be
pushed
out.
So
I
don't
know
whether
it
will
last
the
week
really
that
that's
if
they
decide
to
prioritize,
you
know
pulling
in
an
updated
pod
man
and
then
just
recomposing
march.
The
march
update,
I
don't
know
if
it
matters
anymore.
After
that
point,.
B
E
A
A
Yep,
I'm
here
yeah,
so
you're
you're
hearing
some
of
our
pain
here
so-
and
I
think
this
was
part
of
the
conversation
last
time
too,
is
how
how
we
get
flagged
when
these
things
and
and
I'm
you
know,
vadim
just
from
my
understanding,
when
did
you
figure
out
that
the
new
pod
man
was
coming?
What
was
the
communication
around
this
odd
man?
3
thing?
How
did
that
work?
Did
you
find
out
just.
C
C
We
knew
this
like
about
a
week
ago,
because
what
we
do
is
we
pick
a
version
of
the
darker
os
in
our
installer.
Any
api
installation
is
bound
to
a
particular
version.
The
upis
have
the
liberty
of
using
whatever,
so
what
we
do
is
fedora
coreos
has
a
tracker
and
they
post
when
they
release
a
new,
stable
version.
C
Usually
at
this
point,
I
bump
the
installer
make
a
build
and
make
a
test
run
and
that
usually
either
passes
perfectly
and
then
I
just
keep
an
eye
on
nightlys
or
it
horribly
fails,
and
I
reported
it
back
to
federal
court's
table
to
federal
request
folks
saying
that
table
is
broken
for
some
reason
and
so
on
yeah.
Sometimes
some
users
are
faster
than
I
am
and
they
report
issues
just
like.
In
this
case
it
was
reported
right
at
the
middle
when
I
was
building
a
new
installer.
C
D
D
B
It
seems
to
be
a
four
six
issue,
because
I
haven't
seen
that
on
four
seven,
but
it
looked
like
it
was
pretty
pretty
common
in
four
six.
I
remember
seeing
it
in
four
six,
but
also
I
I
know
that
we
do
this
all
the
time,
but
I
want
to
give
kudos
to
vadim
again
because
he
is
a
very
patient
man,
even
when
it's
late,
it
is
like
he's
very
kind,
and
I
need
to
remember
that
he's
five
hours
ahead
of
me.
B
E
A
There's
it
seems
like
there's
always
something
little
thing
and
I'm
wondering
how
we
what
we
need
to
do
to
be
more,
maybe
involved
in
the
fedora
core
west
decision
making
tree
around
what
goes
into
fedora
core
os.
If
there's
something
we
should
be
doing
from
our
point
of
view,
you
know
you
have
thoughts
on
that.
C
I
don't
think
we
need
some
active
investigation
or
constant
pressure
and
fedora
courage,
folks
to
look
into
kitty
bugs,
because
what
we
can
do
is
we
can
have
more
testing
and
we
can
always
fall
back
to
any
particular
stable
release.
We
can
do
yeah,
we
are
keeping
an
eye
on
what's
happening
in
federal
crossland
and
I
think
we're
mostly
aware
of
any
changes
coming.
For
instance,
parade
is
already
using
the
door
f34.
C
H
Well,
I
think
testing
is
a
really
core
thing
is
to
get
peop
pardon.
The
pun
is
to
get
things
tested
out
of
the
other
streams
of
fedora
core
os
streams,
and
I
think
if
we
can
make
it
easy
to
sort
of
do
a
testing
matrix.
So,
for
example,
last
week
I
just
incorporated
some
functionality
into
my
script
that
pulls
from
the
different
streams
the
latest
release
and
incorporates
that
into
an
okd
build.
H
If
we
could
do
that
across
the
board
and
then
basically
have
a
matrix
of
okay,
here's
this
release,
here's
this
version
of
okd
the
the
community
could
be
able
to
test
these
things
quite
easily.
We
just
needed
the
same
thing
on
the
other
platforms,
so
I
got
vcr
covered,
but
we
need
something
similar,
some
sort
of
testing
matrix,
basically
for
the
other
platforms.
A
Yeah,
I
would
just
from
my
point
of
view
it
sound.
It
sounds
like
there's
mechanisms
in
place,
vadim
that
you
have
to
you
know,
for
awareness
and
and
we
can
use
the
earlier
release.
I
was
just
wondering
from
a
community
liaison
role,
what
what
we
should
be
doing
with
the
fedora
core
os
and
if
there's
more
resources,
that
we
should
be
from
okd
putting
on
fedora
core
west,
or
you
know
what
else
we
can
do
to
help
here.
I
So
from
the
federacra
side,
I
would
say
the
easiest
way
to
make
sure
that
we
are
not
breaking
okd
is
to
make
sure
that
we
are
testing
the
the
thing
that
you
use
so
here.
Apparently
that
was
one
of
the
features
of
podman
and
we
are
probably
not
testing
that
right
now
in
the
federal
core
sei
and
if
we
have
a
test
for
that,
then
it
won't
break
so
and
we
won't
release
with
that
broken.
I
So
I'll
say
I
don't
know
how
much
of
the
coverage
we
have
regarding
bondman
and
things
like
that
in
in
fedrak
or
sci,
but
yeah.
If
specific
things
are
really
important
for
kd,
then
we
could
have
that
info
drive
or
sci
yeah
and
there's
already
initiative
to
bring
more
tests
more
application
tests
to
federal
res.
But
this
is
definitely
a
work
in
progress.
C
C
I'm
thinking
that
we
shouldn't
push
on
ci
too
much.
We
have
a
lot
automated
and
I
would
rather
have
upi
installs
covered
and
all
of
them
are
snowflakes
anyway.
So
if
we
manage
to
find
a
bunch
of
problems
with
promiscuous
mode,
we
shouldn't
be
adding
a
test
which
verifies
this,
because
we
will
have
this
covered
when
community
tests
anyway,
and
their
results
are
always
evolving
and
changing
in
time.
So
we
always
know
that
these
are
always
active,
valid
and
somehow
relevant.
D
That's
that's
what
happened
to
us
and
it
was
completely
random
that
we
saw
that
because
we
didn't
did
not
know
that
promiscuous
mode
was
on
yeah.
A
colleague
of
mine
has
enabled
it
because
of
a
cube
test
months
ago.
Maybe
we
don't
know
it,
but
we
stumbled
on
lots
of
problems,
and
I
think
I
know
that
you
say
a
test
has
to
produce
a
deterministic
result,
yeah,
absolutely
correct,
but
with
these
reboots
you
find
so
much.
You
can't
find
much
so
it
can
find
so
much
effect.
C
I
get
it.
What
we
have
instead
is
at
least
for
recipes
for
sure
we
have
endurance
test,
meaning
a
cluster
is
left
for
like
a
couple
of
days,
at
least
I
think,
even
for
weeks
with
effectively
serial
tests
running
here
and
there
that
includes
upgrades
language
running
payloads
there
that
actually
includes
restarts,
and
so
on
it's
not
a
standard
job.
So
I
don't
have
a
good
definition
for
that.
All
we
could
have
is
a
similar
test
for
okd
that
might
be
very
valuable
yeah
we
could.
C
We
could
work
on
that
if
we
need,
if
we
could
dedicate
one
of
the
communities
clusters
to
that
and
try
a
similar
schema
to
find
out
more
bugs.
That
would
be
incredibly
useful
because
all
our
of
these
field
clusters
are
shared.
There
is
no
way
we
can
dedicate
one
psphere
cluster
for
ogd
test
and
watch.
C
H
Jamie
I
feel
like
this
is
pointing
back
to
the
need
for
a
testing
matrix
and
a
resource
identification
matrix,
so
who
do
we
have
in
the
community
that
can
run
stuff
on
a
vsphere
cluster
to
do
testing
who
has
access
to
aws
resources
to
do
testing
etc?
Ultimately,
I
don't
think
this
is
going
to
come
from
internal
to
red,
hat's
resources.
H
If
the
fcos
unit
succeeds
and
doesn't
error
out,
then
actually
it's
it-
the
opposite
happens
with
opd.
So
for
but
things
like
that,
it's
hard
to
duplicate
right.
So
we
need
to
be
able
to
say:
okay,
I'm
having
this
problem,
who
has
a
v
sphere
that
can
test
this
to
see
if
you
can
duplicate
it
as
well.
So
how
we
do
that
in
terms
of
narrowing
communication-
I
don't
know,
but
I
think
the
first
thing
would
be
is
to
get
everyone
in
the
working
group
or
external
folks
to
actually
say
okay.
H
H
D
Address,
if
not,
if
not
sean,
had
raised
his
hand
that
he
also
has
seen
that
in
kai
uber
rommel
yeah,
I
I
was
completely
allo,
I
I
thought
I
was
crazy
and
seeing
ghosts
and
white
mice
until
jon
has
said
he
has
seen
the
same.
Sometimes
it's
rather
crazy
to
debug
things.
If
you
are
the
only
one
who
sees
that.
A
A
So,
just
sort
of
to
pull
this
back
to
tease
something
out
of
this
here,
the
the
vsphere
group
meeting
that
we
had,
I
thought
was
really
good
and
we
didn't
really.
I
don't
think
we
repeated
it.
I
think
we
only
did
it
once
maybe
twice
and
maybe
trying
to
do
this
test,
matrix
external
resources
for
vsphere,
even
though
el
mike
you're
saying
there's
vsphere
has
too
many
options,
that's
just
life.
Maybe
we
should
try
and
and
I'll
just
doing
doing
it
for
vsphere,
creating
the
test
matrix.
A
Each
of
these
releases
that
that
I
think
is
is
would
be
incredibly
valuable
and,
and
I
know
we
could
do
it
because
we
have
enough
vsphere
people
here,
we
might
not
be
able
to
do
it
for
aws
and
gke
and
or
wherever
else
people
are
running.
But
but
I
think
we
have
enough
vsphere
interest
to
do
something
like
that,
so
that
that's
how
I
would
capture
this
conversation
and
try
and
move
it
forward
if
people
are
willing
and
I'll.
A
A
A
So
hopefully
the
word
gets
out
a
little
bit
wider
and
people
use
and
see
these
videos
and
thank
you
jamie
for
chopping
up
the
two
hour
long
sessions,
because
my
server
died
and
I
ran
out
of
space
and
memory
to
render
those
videos.
So
thanks-
and
I
think
I
figured
out
my
problem
jamie
so-
but
I'll
still
use
you
as
a
resource
for
that
that
that
said,
I
would
like
to
pause
for
a
minute
and
get
some
feedback
on
what
worked
and
what
didn't
work
on
that
workshop.
A
For
us-
and
I
know
someone
mentioned
the
screen
size
in
hopkin-
was
kind
of
small
for
a
few
of
the
workshops.
I
think
that
was
charo's
comment
and
he's
not
here
because
he's
had
a
family
emergency,
so
I
do
know
how
to
fix
that.
That's
to
take
your
faces
off
when
you're
presenting
in
hop
in
then
the
screen
is
full,
and
if
we
did
that,
then
the
screen
would
be
full
and
it
wouldn't
be
as
as
blurry
and
tiny
text
as
as
it
was
on
some
of
the
video
output.
A
So
I
know
I
know
that
one
issue,
but
I'm
going
to
stop
talking
for
a
minute
and
ask
people
for
their
feedback
on
it
and
then
move
to
next
steps.
What
do
we,
you
know?
Where
are
we
at
with
the
documentation
and
documentation
strategies?
What
I'd
like
to
take
up
some
time
today?
Talking
about
so
I'm
gonna?
A
H
H
We
got
it
together
at
the
end
and
it
it
ended
up
flowing
nicely,
but
I
felt
like
there
was
some
pain
points
and
folks
figuring
out
what
our
real
intent
was
and
who
really
wanted
to
talk
about
this
and
getting
people
to
to
get
into
slots
that
we
needed
people
to
talk
about
stuff
with.
So
maybe
that's
just
a
question
of
timing
like
if
we're
gonna
plan.
H
One
of
these-
maybe
you
know
earlier
on
in
the
process,
say:
okay
identify
who
is
going
to
speak
about
what
and
if
we
don't
have
someone
for
that,
reach
out
right
away,
so
that
it's
not
a
couple
days
like
just
before
the
event
and
stuff
like
that,
and
that's
not
a
criticism
of
any
individual
or
anything.
That's
just
the
process.
Yeah.
A
It
may
have
gotten
much
more
lurkers
and-
and
that's
not
meant
to
be
derogatory
if
you're
out
there
listening
and
lurking.
That's
a
good
thing
to
do,
because
we
know
the
content
is
getting
listened
to,
but
trying
to
get
from
my
point
of
view
trying
to
get
more
people
external
people,
from
red
hat,
to
contribute
to
these
conversations
and
to
be
resources
on
on
different
topics
and
is
is
one
of
my
goals.
A
It
may
not
be
the
goal
of
everybody
else,
so
that
for
me
that
felt
like
something
that
we
quite
didn't
quite
manage
to
do
and
again.
I
also
think
that
I
didn't
quite
do
enough
outreach
because
of
some
of
the
stuff
on
there,
but
as
as
philip
points
out.
One
of
the
things
that
I
always
console
myself
with
is
the
videos,
because
it's
the
long
tail
of
people
watching
this
content.
A
The
same
is
true
with
the
okd
marathon
that
we
had
the
previous
year,
which
is
this
in
my
head,
is
sort
of
the
follow-on
to
that
thing.
So
I
would
definitely
want
to
do
it
again,
but
I
think
the
next
phase
of
the
what's
next
step
is
yeah
and
and
re-broadcasting
it
over
all.
We
we
could
have
done
that
pretty
easily.
I
think
that
would
have
been
easy,
but
asking
someone
to
do
that
on
their
saturday
is
always
problematic
too.
So
I
have
to
be
cognizant
of
that.
A
K
Sorry,
I
know
I
just
want
like,
since
you
were
talking
about
the
broadcasting
I
was
thinking
like
simulcasting,
because,
like
hopkin
is
great
but
like
I
think,
if
you
talk
to
chris,
you
know
like
having
a
broadcast
on
twitch
and
youtube
like
using
their
live
broadcasting.
At
the
same
time
would
make
it
accessible
to
like
people
who
are
searching
for
content
to
watch
on
any
given
saturday,
and
I
think
you
have
a
good
chance
of
like
getting
it
in
front
of
people
who
are,
basically,
you
know
stream
clicking
and
just
looking
for
content
to
watch.
A
The
the
reality
is
by
doing
it
in
tracks.
You
couldn't
simultaneously
do
the
four
tracks.
That
was
one
of
the
limitations
and
also
to
be
quite
honest.
Openshift
tv
doesn't
have
that
big
of
a
an
audience.
Yet
it's
coming.
You
know
it
will
come
for
me.
It's
always,
including
with
the
stuff
that
I
do
in
briefings
and
stuff
that
I
do
on
openshift
tv.
It's
always
about
the
long
tail
watchers
the
people
who
watch
the
videos
afterwards.
A
But
that
brings
me
to
the
documentation
because
the
videos
are
great,
but
without
the
good
documentation
and
the
follow-up
with
the
documentation
and
the
work
that
mike
you
did
and
jamie
and
everybody
else
getting
that
taxonomy
in
place
in
your
repo
was
awesome,
I'm
wondering
what's
what
the
status
of
that
is
right
now
and
maybe,
if
jamie
and
mike,
if
you
could
take
a
minute
and
say
you
know,
what's
missing
what
what
do
you
want
to
do
with
that
repo's
worth
of
content
and
where?
Where
should
that
be
next.
H
You
want
to
go
ahead
and
lead
off
either
way
either
you
can
go
first,
jamie
sure,
so
I
think
you
know-
and
I
regrettably
couldn't
make
it
to
the
meeting
last
week,
because
I
showed
up
early
for
the
documentation.
I
think
you
know-
and
some
of
this
was
covered
in
the
meeting-
is
that
there's
been
a
lot
of
duplication
of
effort
in
terms
of
the
guides
that
were
created
last
year,
some
of
the
stuff
that
was
created
this
year,
etc?
H
I
don't
know-
and
mike
can
speak
to
this
more
if
mike's
repo
is
ultimately
the
landing
place
where
we
want
people
for
that
type
of
stuff
right.
So
eventually
we
want
to
move
it.
So
we
need
to
clear
a
path,
that's
sort
of
more
directly
to
it.
I
my
sense
is
that
we
are
getting
better
at
writing
documentation,
but
it's
sort
of
insular.
H
What
I'm
seeing
is
that
a
lot
of
questions
that
we
had
at
the
workshop
with
stuff
that
wasn't
covered
in
the
documentation
that
comes
from
people
out
in
the
world,
and
so
it
might
be
helpful
for
us
to
come
up
with
a
way
of
gleaning
questions.
Out
of
the
community
and
then
writing
documentation
based
on
our
answers-
and
you
know
I
had
done
some
of
discussion
of
that
and
blog
posts
right
and
done
some
discussion
of
that
early
on
with
vadim
and
a
couple
other
folks
about
okay.
H
What
are
some
common
questions
to
put
in
the
faqs
and
stuff
like
that?
But
it
might
just
be
like
committing
one
of
us.
Maybe
we
rotate
once
a
week,
look
through
the
channels
of
slag
find
out
what
people
are
asking
repeatedly
and
then
create
documentation
on
it.
You
know,
and
if
we
have
a
rotation
of
people
you
so-and-so
is
responsible
today
or
this
week
or
whatever
we'll
always
have
someone
getting
that's
calling
that
stuff
from
questions
and
then
either
incorporating
it
into
existing
documentation
or
creating
new
documentation.
H
A
Yeah
so,
and
and
my
question
to
to
the
two
of
you
and
probably
anyone
else
who
wants
to
pipe
in,
is
the
status
because
a
couple
of
things
were
still
stubs
in
mike's
repo,
like
links
out
to
charo's
thing
and
and
the
home
labs
stuff,
we're
all
stubs
and
or
pointers
to
places,
and
I
honestly
haven't
looked
recently
at
the
at
the
hierarchy.
What
it?
Where
are
we
at
in
terms
of
getting
enough
content
to
move
it?
A
A
H
There
are
still
stubs,
charo's
stuff
hasn't
been
moved
into
a
singular
page
or
anything
like
that.
I
I
haven't
pushed
it
because
my
thought
was
that
we
were
going
to
have
the
conversation
about
duplication
of
effort
and
what
goes
where
first,
but
maybe
that's
just
maybe
you
and
I
looking
at
this
differently
or
other
people
looking
at
this
differently.
A
D
We
could
we
could
immediately
put
that
to
to
okdio
in
blocks,
because
there
you
have
tags,
you
have
a
search,
I
mean
you
can
group
articles
together.
We
can
make
a
create
a
home
lab
tag
and
write
blog
posts.
It's
still
everything
is
still
in
in
get
repos
yeah.
If
people
want
to
have
something,
they
cannot
create
requests,
but
I
think
the
entry,
if
you
search
for
okd
okdio,
is
one
of
the
first
hits
and
I
think
the
simple.
A
H
H
K
Me
follow
up
with
status
then,
where
we
got
to
after
that,
because,
like
last
tuesday,
we
met
up,
we
talked
about
a
bunch
of
action
items
to
do
on
the
repo.
Since
then
we
put
a
template
in
there
we
started
to
we
changed
the.
There
were
two
bare
metal
directories.
We
changed
one
of
them
to
be
called
a
home
lab
now
and
that's
where
we've
put
you
know,
vadim
and
sri's
instructions
are
there.
I've
got
a
pr
open
to
rename
the
directory
that
charo's
is
in
to
single
node,
which
we
had
agreed
on.
K
We
wanted
to
have
a
distinction
between
single
node
and
home
lab.
I
I
pinged
jamie.
I
was
just
and
and
char.
I
was
just
waiting
to
hear
back
from
them
before,
like
approving
that
eric
was
able
to
help
me
out
a
bunch
and
we
got
the
template
merged.
I
think
today
I
also
went
back
and
redid
all
the
like
the
ipi
defaults.
K
I
put
those
in
the
format
of
the
template.
The
next
steps
that
I
was
going
to
do
was
to
rewrite
the
outstanding.
You
know
like
trees
and
vadims
and
charos.
I
was
going
to
rewrite
those
and
format
them
under
the
template
so
that
they
at
least
looked
similar.
Even
if
the
deployment
section
in
the
case
of
charo's
linked
out
to
an
external
you
know
his
page,
we
would
kind
of
like
fill
it
up
a
little
bit
so
that
it
looked
like
that.
K
K
People
like
deploying
with
so
that
we
could
start
to
get
a
picture
of
what
what
kind
of
various
deployments
were
looking
like,
and
a
lot
of
this
was
around
vsphere
activity,
because,
like
internally
and
I'll,
just
I'll
call
back
to
something
diane
was
talking
about
earlier,
like
having
this
group.
Do
vsphere
work
is
amazing,
like
getting
more
community.
K
But
we
see
a
ton
of
people
showing
up
who
want
to
use
vsphere,
and
I
think
the
popularity
of
vsphere
in
the
community
is
so
large
that
it's
difficult
for
us
as
a
product
team
to
actually
like
service
all
the
requests
that
are
happening
around
vsphere.
So
it's
like
it's
very
easy
for
us
to
do
aws
and
gcp,
and
we
have
like
a
good
handle
on
those
things
but
vsphere
because
of
the
explosion
of
options
for
the
way
you
can
deploy.
K
You
know
if
you
want
to
use
it
for
a
collection
of
deployment
guides.
I
think
that'd
be
great.
Eric
had
a
great
suggestion
in
one
of
the
pr
the
template
pr.
You
know
the
notion
of
we
might
have
an
install
guide,
that's
kind
of
like
a
base
for
a
certain
thing.
Like,
let's
say
aws,
you
know
upi
install
guide
or
something,
and
that
would
be
a
base
template
that
others
could
refer
to.
K
So
if
you
were
just
doing
something
like
hey,
I'm
installing
to
aws
I'm
using
upi,
but
I'm
also
using
a
cluster-wide
proxy.
You
know
you
could
have
a
guide.
That
would
say
like
yeah
point
to
the
base
guide,
which
has
all
the
basic
information.
All
it
needs
to
do
is
add
this
little
extra
blurb.
So
I
think
there's
this
idea
of
like
modularity
to
the
guides
as
we
start
to
build
them
up.
So
those
are
some
of
the
ideas
that
we
had
talked
about.
A
Yeah
and-
and
it's
good
I
mean
I
I'm
totally
thrilled
with
the
vsphere
content
and
the
community-
that's
coming
around
v
spirit
and
and
gelling
too,
I
think
that's
going
to
be
huge
for
us
and
it's
one
of
the
big
things
that
we
can
offer
back
to
the
engineering
teams
is
that
the
community
will
will
help.
You
know
parse
out,
what's
going
on
with
vcr
and
the
different
releases,
and
I
think
that's
a
huge
selling
point
when
I
have
to
go
back
and
vadim
has
to
go
back
and
get
engineering
resources
put
on
okd.
A
If
we
say
not
only
are
we
helping
you
with
the
future
of
rel,
but
we're
also
helping
manage
all
this
vsphere
stuff.
So
when
you
think
of
me
and
other
folks,
internal
to
red
hat,
who
have
to
argue
and
fight
for
resources
for
this
project-
and
these
are
the
things
these
are
the
arguments
that
we
we
have
to
keep
doing,
and
it's
not
that
we
argue
yeah,
it's
just
it's.
The
the
pull
and
tug
for
resources
is.
G
A
K
I'm
pushing
I'm
trying
to
push
the
okd
message
internally
as
well,
because
like
what
I'm
trying
to
take
back
to
our
team
and
the
stakeholders
that
we
have
involved
in,
like
especially
the
bugzilla
process
around
what
we're
doing
like
I'm
trying
to
point
out
how
valuable
the
okd
community
has
been.
You
know
for
us
in
terms
of
okay
yeah.
There
is
this
easing
of
pressure
around
the
bug,
reporting
and
fixing
that's
happening
in
the
community.
A
E
It's
making
sure
everyone
is
bought
in
to
recognize
the
value
that's
happening.
Some
people
may
have
it,
but
not
necessarily
everybody
knows
right,
like
another
subtle
effect
of
what
we're
doing
here
is
we're
making
it
easier
for
okd
to
move
faster
like
because
things
are
actually
happening
and
people
are
actually
using
it
and
we're
plugged
into
fedora
core
os
rather
than
using
centos
or
rel4
os
or
whatever.
E
We
also
have
the
opportunity
to
be
able
to
do
things
like
test
new
modes,
see
how
well
defaults
and
and
opinions
that
openshift
is
trying
out
whether
they
work
out
in
practice
or
not
building.
You
know
those
sorts
of
things
that
I
don't
think
there's
another
avenue
in
which
that
could
be
done
like
I
think
crc
would
be
in
a
much
worse
spot
today,
if
it
weren't
for
for
a
lot
of
the
things
that
we've
been
trying
to
do
and
figure
out.
K
Okay,
there's
kind
of
another
angle
to
this
to
neil,
which
is
you
know
that,
like
as
the
community
here,
is
doing
a
lot
of
work
and
starting
to
do
more
work
like
one
of
the
things
that
I'm
trying
to
do
internally
is
change
our
language
from
you
know
in
the
past,
it's
all
been
like.
We
all
talk
about
open
shift,
open
shift,
open
shift,
every
tool,
we're
creating,
is
open
shift.
K
This
open
shift
that
and
what
I'm
trying
to
do
is
shift
the
discussion
internally
to
say:
let's
look
if
we
want
okd
to
be
this
upstream,
you
know
this
mythical
upstream
to
open
shift
or
to
ocp.
Let's
adjust
our
language
and
start
talking
about
okd
like
if
I'm
going
to
make
a
new
tool.
I
don't
want
to
call
it
the
open
shift
this
that
the
other
thing
I
want
it
to
be
the
okd
this
that
the
other
thing,
because
I
want
to
push
towards
the
community
first.
K
A
A
I
think
he
did
4.5
in
his
last
home
lab
right
up
and
now
it's
for
4.7
or
eight
seven
that
he
did
the
demo
with
so
so
that
that
would
be.
You
know,
get
that.
So
I'd
like
to
get
it
to
a
point
in
your
repo,
because
I
know
it's
easier
and
quicker
for
you
to
do
stuff
over
there
and
and
maybe
we'll
wait
till
next
week
and
in
the
docs
meeting
and
have
another
conversation
and
see
where
we're
at
and
then
after
that
do
the
pull.
A
I
think
the
other
thing
and
jamie
keeps
harping
on
it,
and
I
and
I
know-
and
I
am-
and
I'm
also
going
to
say
right
up
front-
I
am
not
a
doc
specialist.
I
just
know
good
docs
when
I
see
it
and
I'm
also
not
a
process
specialist.
So
if
there
are
other
people
on
the
call
who
are
docs
people-
and
I
know
our
one
person
who
amy
who
was
on
had
to
leave
at
10
30
so
and
she
does
all
the
rdo
docs.
A
But
if
there's
someone
else
who
wants
to
take
on
building
a
cohesive
docs
strategy
and
process,
I'm
I'm
I'd
be
thrilled
to
work
with
you
on
that,
and
I
can
see
jamie
raising
his
hand
jamie,
keep
you
keep
raising
your
hands
editing.
My
videos,
editing,
you
know,
do
this,
but
I
think
we
do
need
to
step
back
and
figure
out
what
we
have
like
an
audit
of
what
we
have
in
the
system.
Right
now,
I
love
the
idea
jamie
about
the
f8.
A
You
know
sort
of
the
faq
stuff
from
the
whatever
the
current
conversation
is
one
of
the
things
joseph,
though
that
I
would
coach
that
I
know,
because
I'm
old
as
dirt
is
that
documentation
by
blogging.
Doesn't
it
isn't
sustainable?
Everything
goes
out
of
date,
just
like
you
know,
craig
robinson's
4.5,
home
lab
blog.
A
A
A
If
any
of
you
have
experience
or
have
people
working
on
your
teams
who
have
experience
with
docs
that
you
can
drag
into
this
conversation,
it
would
be
lovely
to
have
more
docs
help.
So,
but
I
don't
want,
I
know
jamie.
You
already
raised
your
hands
about
the
testing
stuff
to
testing
matrixes,
but
I
think
if
we,
if
I
do
something
like
continue
the
docs
meetings
every
other
week
and
then
come
up
with,
we
had
talked
about
office
hours
community
office
hours
on
a
thursday.
A
But
if
maybe
we
re
jig
that
to
be
every
bi-weekly
office
hours
and
on
the
other
week,
do
a
vsphere
group
which
may
end
up
being
the
same
thing
as
community
office
hours.
But
it's
the
same
people,
but
that
regular
cadence
of
this
week
we're
going
to
talk
about
vsphere
and
testing
on
vsphere
and
the
agenda
is
about
you
know,
external
resources
and
how
we
can
do
that
and
communicate
our
results
back
effectively
and
then
have
office
hours
on
thursdays
as
well
and
use
openshift
tv.
A
You
know
I
I
get
that
I
really
do
that,
but
I
you
know-
and
I
think
the
other
thing-
that
it's
really
important,
because
it's
the
long
tail
watching
of
this
content
that
people
are
doing.
I
get
more
feedback
from
people
in
strange
parts
of
the
universe
and
different
time
zones
that
you
know
they're
watching.
I
never
think
anyone
ever
watches
these
recordings
until
I
don't
upload
the
last
three
and
get
behind
and
then
someone
knocks
on
my
door
and
says
hey.
A
C
A
It
always
is
and
docs
make
a
community
is
what
I
I
kind
of
say,
and
until
we
have
a
good
doc
strategy,
we're
always
going
to
be
in
this
recursive
loop
of
having
these
conversations
about
stuff.
So
I
think
it's
time
and
it
would
be
lovely
to
do
so.
On
that
note,
is
there
anything
else
we
missed
today
that
we
should
have
done
any
other
feedback.
B
John
had
a
question
then
yeah
so
vadim,
and
I
were
talking
earlier
on
one
of
our
slack
things
and
the
question
we
raise
is:
where
are
we
tracking
bugs
or
whatever
you
want
to
call
them
well
enough
or
do
we
need
something
else
in
order
to
track
bugs
or
to
do's,
or
something
else
is
that
a
is
that
a
fair
statement?
Vadim
a
restatement.
C
C
Should
we
be
using
something
like
a
blog?
It's
a
pretty
much
open
discussion.
We
probably
should
use
mailing
lists
for
that,
but
any
ideas
how
to
improve
our
workflow
are
greatly
appreciated
because
well
there
is
always
a
room
for
improvement
and
I'm
not
very
happy
with
what
we
have
right
now.
There
are
lots
of
things
the
community
could
participate,
but
probably
it's
locked
behind
all
the
labels
that
we
use
for
issue
tracking
and
things
like
that.
A
lot
of
folks
are
asking
for
a
good
first
issue
to
get
started.
C
We
don't
have
that
because
that
includes
getting
hands
dirty,
but
we
have
a
lot
of
jobs
and
things
to
do
to
clean
up
documentation
to
clean
up
issues
that
are
active
to
clean
up
a
list
of
releases.
We
have,
and
probably
backtracking
is
not
a
great
place
to
discuss
that.
So
overall
workflow
improvement,
probably
a
good
topic
to
to
have
a
discussion
upon.
A
B
A
A
I
think
when
I
think
our
presence
there
is
really
important
to
keep
the
conversation
about
openshift,
open
and
and
having
an
open
source
angle
to
the
awareness
of
that
people
are
using
okd
on
the
part
of
everybody
in
the
universe,
not
just
red
hatters
but
the
rest
of
the
universe,
that's
lurking
in
there.
So
you
know
yeah,
I'm
I'm
leaning
towards
staying
where
we
are,
but.
B
C
B
That
we
want
to
do
as
a
community,
so
I
mean
I
I
I
know
neil
doesn't
like
slack,
but
you
know.
I
think
that
there
is
a
good
community
there
and
a
lot
of
people
watch
it.
But
you
know
I'm
I'm
up
for
other
things
too,
but
I
think
I
agree
with
vadim.
You
know
we
need
to
have
something
where
we
can
might
as
well,
where
we
can.
You
know
kind
of
track
that
kind
of
stuff
yeah.
A
The
other
thing
I
think
that
we
could
use
is
that
the
thing
that
I
use
not
to
talk
to
the
agenda
page,
the
projects
page
as
well,
and
that's
in
github
and
and
pretty
public,
but
I
don't
think
we
have
it
in
the
right
place
because,
obviously
not
everybody
can
add
to
it,
because
you
don't
have
rights
to
do
so,
so
maybe
creating
the
project
page
in
up
the
okd
dot.
Io
repo,
that
was
public,
might
be
another
alternative.
E
E
A
Well
hold
that
thought,
because
I
have
to
kick
you
all
out
of
here
now,
because
I
have
another
meeting
coming
up
in
this
same
url.
Let's
have
that
discussion
on
what's
available
for
this
and
yeah.
This
is
my
public
forum
here
for
everything
I
do
with
openshift.
So
thank
you.
For
today.
This
was
really
good.