►
From YouTube: OKD Working Group Documentation Mtg 2021 03 21
Description
OKD Working Group Documentation Mtg 2021 03 21
https://groups.google.com/forum/#!forum/okd-wg
https://okd.io
A
All
right
so
welcome
to
the
the
docs
meeting
of
the
okd
working
group
meeting,
so
hi
eric
and
hi
everybody,
and
I'm
going
to
put
everybody
on
camera
today,
just
so
that
we
there
and
I'm
sort
of
working
through
the
recap.
Blog
post.
I've
got
a
preliminary
one
in
the
okd.io
blog
this
morning
and
most
of
the
main
stage
videos
have
been
uploaded
and
separated
into
their
individual
talks.
So
there's
one
by
charo,
one
by
vadim,
one
by
jamie
and
one
by
joseph.
A
So
those
are
there
now,
plus
the
one
long
full-on
unedited
one,
and
there
goes
a
dog
behind
mike.
I
love
this.
I
don't
have
a
dog
anymore,
so
I'm
living
vicariously
to
everyone
else
in
zoom
lands
dogs
these
days,
so
that's
happening
I
just
had,
and
he
won't
be
able
to
join
us.
Jamie
from
umich
is-
has
another
obligation
at
this
time.
I
just
did
a
chat
with
him
he's.
I
have
run
completely
run
out
of
disk
space
on
all
of
my
hard
drives
and
the
session
our
sessions.
A
The
track
sessions
were
very
long,
so
I
managed
to
get
the
home
lab
one
edited
and
up
and
then
ran
out
of
disk
space
completely
and
now
so
it's
been
one
besides
losing
internet
access.
I
ran
out
of
disk
space
on
my
editing
machine.
It's
been
a
it's
been
a
fun
couple
of
days,
but
that
said,
I
got
the
home
lab
one
up,
I
just
retweeted
it
and
there
should
be
a
blog
post
shortly
on
okd.io.
A
I
just
have
to
add
in
the
links
to
the
individual
videos
as
they
go
up
and
jamie
from
umich
is
going
to
edit
the
the
other
three
sessions
and
upload
them
to
youtube
for
us,
and
I
am
forever
grateful
for
that
and
you
can
see
what
you're
doing
the
question
that
I
wanted
to
discuss
today
and
if
other
people
have
things
on
the
agenda,
let
me
know
was
now
that
we've
done
the
workshop
and
there's
a
number
of
stubs
and
eric
and
robert.
I
don't
think
you
were
there
this
weekend.
A
A
B
B
B
A
Yeah,
so
that's
probably
not
like
great
documentation
process,
so
it's
there
still
needs
to
be
some
cleanup
and
editing
on
this
on
these
configuration
guides
so
that
they
have
some
uniformity
to
them
and
and
to
be
quite
honest,
I'll
I'll,
say
what
I
said
to
jamie
earlier.
I
we
were
looking
at
the
openshift.com
blogs
and
the
home
lab
for
4.5.
That
craig
robinson
did
that
I
reposted
an
openshift.com
head
is
still
in
the
top
10
of
blog
things
that
get
hit
on
openshift.
A
B
A
B
Yeah
so
that
when
you
said
that
yeah,
like
jason
or
justin-
and
you
know
blinking
yeah
there
and
andrew
their
their
lab
yeah,
I
wouldn't
have
called
it
bare
metal.
So
much
as
I
might
have
called
it
libert.
You
know,
because
that's
really
they
were
exercising
the
libert
pieces
of
the
of
the
cluster
to
build
there.
D
A
I'm
just
going
to
go
back
in
the
chat
and
I'm
going
to
put
a
link.
It's
unless
so
don't
share
it.
Quite
yet
everybody
can
take
a
look
at
this
is
andrews
and
just
skim
past
the
first
10
minutes,
because
that's
all
them
trying
to
figure
out
how
to
set
up
their
screens
and
that's
what
has
to
be
edited
out,
but
that's
the
video.
If
bruce,
you
want
to
look
at
it
or
anybody
else
wants
to
look
at
it.
B
So
diane
I
wanted
to
step
back
for
a
second
though,
and
go
back
to
talking
about
the
configuration
note
or
guides
repo
cause.
I
agree
with
you,
like
you
know
the
more
I
was
thinking
about
it
over
the
weekend
and
the
more
we're
kind
of
like
you
know.
We
started
to
get
some
pull
requests
in
there.
You
know
yeah.
I
one
thing
I
would
love
to
have
is
like
a
template
that
we
could
use.
B
We
could
kind
of
say
here
you
know
and
and
I'll
look
at
the
sections
we
have
now
and
maybe
I'll
just
try
and
call
out
those
sections
and
say
you
should
have
like
a
hardware
section.
You
should
lecture
that,
but
then
also
like
really
the
shape
that
this
information
is
starting
to
take
is
yeah,
it's
much
more,
like
a
community
response,
it's
like
here's.
A
That
I
wanted
to
say
about
that
one
is,
is,
is
you're
absolutely
right
and
a
template
like
in
the
readme
file
at
the
beginning
of
the
configuration
guys
what
you
know,
what
should
be
in
your
your
stub
or
in
your
guide
and
then
to
figure
out
the
categories
better,
so
bare
metal
should
maybe
andrews
and
justin
should
get
shoved
into
something
called.
I
think
it's
libert.
A
Explain
what
I
mean
by
that
is
one
is
if
it's
in
the
open
shift
repo,
it
has
connotations
of
officialness,
and
it
also
means
that
we
have
to
follow
their
guidelines
for
merging
new
content
in
and
ask
their
ask
the
engineering
team
that
owns
the
repo
or
bug
vadim
or
bug
christian.
Whoever
has
merged
access,
and
frankly,
I
don't
even
want
merge
access
on
the
openshift
repo
at
this
juncture.
A
There
are,
you
know,
thousands
of
customers
relying
on
it
and
if
I
screw
up-
or
I
don't
want
my
name
on
the
front
page
of
the
wall
street
journal
for
introducing
some
bug.
However,
on
the
okd
dot
io
site-
I
do
own
that
and
there
are
a
couple
other
folks
there.
So
if
we
move
this
and
then
we
could
format
it
any
way
we
wanted,
we
could
make
it
as
beautiful
as
the
porter
dot
sh
site.
We
could
do
whatever
we
want.
A
So
what
I
you
know
and-
and
I
would
not
that
I
don't
love
you
mike,
but
I
would
love
to
move
it
over
there
sooner
than
later,
so
that
people
get
into
the
habit
of
pushing
stuff
there.
If
that's,
okay
and
yeah,
I'm
totally
happy
yeah
yeah,
and
so
I'm
gonna
pause
for
a
minute
and
bruce
you're
about
to
say
something
so
I'll
shut
up
for
a
minute
and
then
I'm
gonna
ask
eric
and
robert
because
they're
the
newbies
on
this
call
what
they
think.
B
B
What
this
repo
that
I
created
originally,
we
were
just
calling
it
notes,
because
what
we
wanted
to
do
was
we
wanted
to
collect
information
from
people
about
what
their
clusters
look
like
once
they
were
actually
deployed
right.
So
we
wanted
people
to
contribute
like
I
know,
I'm
running
vsphere
and
I
followed
the
standard.
B
Kind
of
I
don't
want
to
say
day
two,
but
once
they
get
to
day
1.5,
you
know
once
they've
passed
installation.
What
does
what
does
their
configuration
look
like
and
are
there
any
customizations
that
they've
had
to
do?
You
know
to
kind
of
get
there,
so
that
was
the
intention
on
on
creating
these
guides.
A
C
A
A
So
the
thing
is
to
try
and
get
them
to
come
to
see
okd.io
as
the
portal
into
that
links
to
everything
and-
and
I
think
we
can
do
that
and
I
think
the
deployment
configuration.
This
is
why
I've
been
so
hot
on
these
doing
the
okd
marathon
and
then
do
the
these
other
things
and
getting
up
on
youtube
is
to
keep
driving
awareness
of
ok,
d4
and
it's
been
semi-effective
and
probably
as
effective
as
the
sales
team
at
openshift
wants
it
to
be
it.
A
It
could
be
better
and
it
could
be
easier
to
to
maintain
so
what
I
was
gonna
and
now
I'm
gonna
stop
for
a
minute.
So,
robert
and
eric
you
are
guinea
pigs
here
today,
I
don't
know
where
either
of
you
are
from
what
companies,
whether
you're,
red,
hatters
or
not,
but
tell
me
what
you
think
of
that
idea.
Is
that
where
you
would
go
you're
the
I
see
the
red
hat
sneaking
out
there
eric!
Yes
behind
you
yeah!
I
have
one
over
there.
I'm
just
tilted
the
wrong
way
today.
E
So
what
I
like
is
the
idea
to
summarize
all
of
the
okd
related
content
on
the
okt
website.
I
also
like
that
we
have
this
new
word
okd
for
the
free
and
open
source
part
of
openshift,
because
it
is
where
it
sounds
very
different
and
there's
always
this
kind
of
confusion
between
the
product
and
the
actual
open
source
project
and
having
everything
as
okd
and
getting
the
okd
letters
more
into
the
faces
of
people
will
also
teach
people
more.
E
What
is
actually
the
difference
and
what
is
the
upstream
project
basically
and
yeah
with
the
documentation?
I
I
feel
like
there's
something
where
I
want
to
help,
so
I'm
personally
very
interested
in
the
single
note
area.
That's
also
why
I
bought
the
nook,
and
I
was
also
in
the
workshop
with
charo
and
also
afterwards.
E
We
had
to
have
a
call,
so
he
could
help
me
get
the
last
steps
done,
and
I
also
made
some
changes
to
his
scripts
and
would
have
some
small
changes
that
I
would
like
to
make
to
his
blog
post,
where
I
don't
know
where
I
can
hand
these
changes
in
and
having
a
central
place
where
we
put
all
these
documents
is
very
helpful
and
yeah.
It's
it's
really
a
little
bit
a
question.
There's
the
openshift
documentation
that
is
on
the
openshift
website
right.
E
What
we
want
to
have
in
each
and,
if
I
understand
mike
sorry
mike,
is
the
correct
name,
because
it
always
says
ambiko,
so
I'm
always
not
sure
how
I
should
go
either
one
works
either
works.
Then
then
I
call
you
mike
and
if
I
understand
you
correctly,
what
you
basically
want
to
show
in
the
okay,
okay
documentation
is
like
what
are
me.
What
is
the
result
of
what
people
are
making
out
of
the
documentation
right
and
there
are
also
some
individual
adaptations
and
to
present
different
scenarios,
basically
like
in
the
past.
E
C
A
F
F
A
Like
that's
one
of
the
things,
and
you
know
it
has
the
ability
to
tag
so
what
I,
if
you
look
at
the
read
me
and
I'll,
just
share
it,
share
that
to
do
something
like
if
you
can,
if
you
don't
mind
me
asking
you
to
do
this
is
to
to
create
sort
of
a
template
for
what
the
should
be
in
the
guide,
because
robert
you're
absolutely
right
these
things.
One
thing
that
I
really
despise
is
is
documentation
by
blogging.
A
You'll
always
hear
me
rant
about
that,
because
internally,
at
red
hat,
we've
had
this.
I
I've
been
at
red
hat
now
eight
years
and
we
get
a
lot
of
brownie
points
and
pats
on
the
back.
For
writing.
A
good
blog
and
just
like
craig
robinson's
home
lab
4.5
blog
is
in
the
top
10
it's
now
completely
out
of
date
or
not
completely,
but
just
enough
to
make
it
nasty
for
someone
trying
to
do
it.
A
So
if
we
had
a
revision
scheme
and
a
freshness
date
in
the
in
the
documentation,
I
think
that
would
help
in
the
in
if
it
were
in
the
okd,
so
that
people
would
it
would
trigger
people
instantly
to
go.
This
is
release
4.5.
This
is
the
version
of
it
and
then
you
could
have
sort
of
a
bit
of
a
hierarchy
of
that
and
and
then
we
could,
what
do
you
call
it
when
you
retire
something
an
older
version
yeah,
so
we
could
retire
deprecation.
A
Thank
you
very
much
for
that
word
today,
word
of
the
day
deprecation.
I
want
to
deprecate
myself
for
a
week
and
go
on
vacation,
but
I
think
that
robert
that's
a
really
good
point
and,
as
bruce
put
in
a
link
to
yet
another
set
of
documentation,
red
hat
is
famous,
I
think,
externally,
for
like
really
complicated
strategies
for
and
every
business
unit
within
red
hat,
even
though
externally
everybody
thinks
of
us
as
dark
red
hat
and
thinks
we
are
totally
coordinated
on
every
product
silo.
A
D
A
A
D
Well,
actually,
I
just
had
a
couple
of
comments,
although
you
know
eric
and
robert,
you
know
made
a
number
of
excellent
points
in
that
things.
Do
quickly
stop
working
and
you
get
to
where
often
something
if
you
tried
to
follow
it
exactly
it
wouldn't
work
for
a
variety
of
reasons.
So,
for
instance,
you
know
charo
has
some
excellent
guides.
D
Okay,
so
he's
his
cluster
version
was
based
on
a
you
know:
centos,
which
had
a
centos
minimal,
which
the
last
centos
eight
version
does
not
have,
and
then
that
breaks
everything
yeah,
and
so
he
for
about
the
last
year
he's
had
a
a
note.
You
know
going
to
centos
stream,
maybe
only
six
months,
but
you
know,
of
course
everybody
is
busy,
and
that
would
be
a
big
change.
D
A
D
D
You
have
to
dig
down
deeply
through
a
guide
before
you
know
whether
or
not
they're
requiring
command
line
access,
which
means
that
if
you're
developer
you're
not
going
to
have
that
for
your
company
because
they
won't
give
it
the
system
and
people
will
give
it
to
you.
If
you
have
a
home
lab,
then
you
do
okay
and
sort
of
in
passing
joseph
commented
that
you
know
he
bought
a
you
know:
vmware
license
et
cetera,
et
cetera,
that's
sort
of
thing
that
you
probably
want
to
make
explicit
up
front.
D
So
you
know
like,
I
think
that,
and
I
guess
charo
and
his
guys
was
pretty
good
up
front
saying
what
his
assumptions
were,
but
that's
not
something
you
know
I
mean,
like
our
assumptions
are
transparent
to
us,
we're
not
always
even
aware
of
them.
So
I
I
think
that
would
be
sort
of
a
useful
editorial
thing
for
somebody
to
look
at
these
and
say:
okay,
if
you're
going
to
go
through
this
guide,
this
is
what
you're
going
to
need
set
up,
or
this
is
who
it's
for
yeah.
E
There
are
also
some
problems
with
that
right
things
also
change
all
the
time
like
I'm
also
discussing
like.
Maybe
we
don't
need
the
bootstrap
note
with
the
next
version
of
openshift
anymore,
and
so
that
is
already
a
big
requirement
that
goes
away
and
maybe
in
in
this
single
node
installation,
we
still
create
two
vms,
because
we
need
the
bootstrap
node,
then
maybe
we
don't
even
need
to
create
vms
anymore.
We
can
just
install
it
purebear
metal
without
any
vms.
E
So
you
know
the
expectations
change
a
lot
and
we
don't
know
yet
how
they
change,
because
we
are
not
sure
how
the
development
will
progress
there
and
nobody
can
really
tell
you.
You
know
the
developer
who's
currently
working
on
it.
He
also
cannot
tell
you
everything
that
he
will
discover
during
the
development
so
yeah.
D
A
A
Take
it
to
the
bank
right
and
the
bank
of
canada
and
there
you
go
and
it's
recorded
here
so
I'm
gonna
move
back
again.
So
I
think
what
I
would
like
to
ask
mike
to
do,
and
maybe
work
with
eric,
because
eric
was
in
the
homelab
one
is
to
create
a
template
in
the
readme
file
in
the
okd.io,
much
like
the
blog
post
and
use
charo's
home
lab
example,
because
we
have
his
blog
post
and
retrofit
charos
into
that,
because
charo
is
pretty
good
at
helping
that
and
see.
A
If
we
can
get
one
and
and
folk,
not
I
shouldn't
say
home,
lab
single
node
cluster
approach
and
then
also
have,
and
we
we're
doing
it,
have
a
depreciation
tag
too
so
like
because
we
know
that
the
single
node
cluster
approach
of
charo's
is
going
to
get
depreciated,
so
some
workflow
of
like
this
is
the
time
stamp.
It's
version
4.8
and
if
I
share
I
mean
see
if
I
can
share
my
screen
again
for
a
second,
and
so
I'm
not
talking
out
my
here.
B
So
like
this
is
something
I
was
going
to
ask
like
I
mean
we
could
convert
the
deployment
guide
into
a
github
page.
You
know,
that's
like
jekyll,
head
matter
is
what
is
what's
going
on
there
so
like
we
could
convert
it
into
some
sort
of,
like
you
know,
static
site
generator.
If
you
want
and
use
git
and
then
we
can
just
have
like
you
know,
a
github
pages
site
where
all
this
information
will
be
assumed
in
there.
If
you
wanna,
if
you
wanna
go
that
route,
we
could
certainly
add
all
that
mark
down
there.
A
Yeah,
I
think
well
for
me-
and
this
is
diane
creating
a
blog
article
is,
is
wicked
simple
though
I
I
still
and
if
we
know
the
structure
of
what
we
want
and
everything
that's
in
those
things
we
should
be
able
to
do
it,
and
I
know
joseph
has
figured
out
all
of
the
ins
and
outs
of
adding
the
blog
into
the
the
okd.io
site.
So
it
should
be
just
rinse
and
repeat
what
we're
doing
for
the
blog,
but
using
the
structure.
B
B
We
want
in
the
template,
like
you,
know,
date
and
version
prerequisites
or
assumptions,
description,
hardware,
target
audience
and
then
some
of
the
information
we
have
already
and
then
maybe
we
also
want
to
move
this
at
some
point
over
and
so
like
do
we
want
to
just
you
know
I
can.
I
can
convert
that
to
be
to
look
more
like
what
the
blog
does,
structure
wise
and
use
like
one
of
these.
You
know
static
site
generators.
B
A
Yeah
we
already
have
that
for
the
site
itself
and
and
joseph
went
through
the
the
inc
so
just
reach
out
to
joseph
we're
using
middleman
and
there
I
think
they
are,
they
upgraded
to
jekyll
a
later
a
newer
version
of
it.
So
I
don't
think
we
have
to
pick
another
one.
I
think
we
can
use
what
we
use
for
the
site
so
and
we
can
have
that
conversation
separate
from
here,
but
I
think
we
already
have
what
we
need
for
the
build
process
for
the
site
to
do
it.
It's
just
I
would.
A
B
But
no,
no,
you
could
certainly
configure
it
to
bring
all
that
stuff
in.
I
guess
that's
kind
of
my
question
is
like:
do
you
just
want
the
files
in
the
guides
repo
to
kind
of
match
the
format
for
the
for
the
blog,
and
then
you
could
just
pull
them
in
later?
Is
that
would
that
be
the
best
way
to
do
this?.
A
A
D
B
I
mean
the
thing
is
in
some
ways:
the
the
guides
are
kind
of
different
from
even
like
charo's,
blog
and
whatnot.
You
know
the
guides
are
more
just
kind
of
data
that
you
could
look
at
and
kind
of
like
use
as
a
reference
they're,
not
necessarily
formatted.
In
a
way,
that's
meant
to
read,
like
you
know,
like
charo's
posted,
because
he
obviously
put
a
lot
of
time
into
structuring
it.
That
way,
so
I
mean
I
could
take
some.
B
I
could
take
some
first
stabs
at
kind
of
organizing
this
stuff
and
then
we
can
see
where
we
get
to,
and
maybe
you
know
kind
of
like
assess
at
that
point,
like
my
preference
at
this
point,
would
just
be
to
have
the
guides
as
plain
markdown
and
just
kind
of
like
doing
what
they're
supposed
to
do,
which
is
being
a
guide
for
how
a
certain
deployment
went
and
then
our
next
operation
will
be
to
figure
out
like
okay.
Do
you
want
to
pull
those
into
a
website
somewhere?
B
A
I
think
those
would
cover
out
a
lot
of
things
here
should
be
in
sections
pick
the
pick,
whichever
one
you
you
like,
I'm
going
to
lean
towards
single
node,
because
I
know
charo
has
time
right
now
and
eric
was
in
the
session,
and
it
is
one
that
we're
going
to
have
to
depreciate
soon,
so
we'll
go
through
the
whole
life
cycle
with
it.
So
we'll
in
my
head
take
that
one
and
format
it
the
way.
A
D
D
So
that's
you
know
that
like,
but
the
thing
is
liberates.
I
think.
Actually
you
almost
we're
almost
getting
enough
guides
that
you
need
a
taxonomy
or
a
decision
tree
of
what
you
want
yeah,
and
I
think
that
the
number
of
choices
is
actually
not
that
great
between
them,
so
you
could
actually
organize
them
fairly
easily.
So
that
would
be
a
lot
clearer.
D
D
D
Aha,
proxy
sort
of
thing
load
balancing
is
what
I
was
trying
to
think
of,
and
then
next
are
you
using
any
automation
tools?
Okay,
so
I
think
that
the
main
difference
between
charo's
and
andrews
was
the
automation
types
of
things
that
you're
doing
charo's
using
bare
bones
bash
scripts.
You
know
fantastic,
you
know
goes
way
back
into
antiquity
and
still
works.
A
A
A
D
A
A
A
D
D
A
A
It
it
would
be
lovely
if
all
of
them
were
that
verbose
and
that
detailed.
I
don't
expect
all
of
them
to
be
that
verbose
and
but
it
would
give
them
opportunity
for
other
community
like
if
somebody
wasn't
as
verbose
as
that
they
could
make
a
pull
request
and
add
verbosity
and
detail
so
like.
If
someone
just
put
a
one-liner
in
there
use,
you
know
f5
load,
balancer
and
someone
else
would
say
or
use
the
one
that
come.
A
You
know
this
other
one
whatever,
but
what
I'm
my
goal
is,
is
it's
not
just
verbosity,
but
it's
giving
people
a
place
to
put
their
guides
as
well
with
some
guidance
about
what
makes
a
good
guide
and
an
expiry
day.
You
know
so
so!
No,
no,
not
everybody
is
going
to
be
as
verbose
as
charo
and
I
don't
want
it
to
be
a
replacement
for
the
openshift,
docs
or
docs.okd.io.
A
So
I'm
not
expecting
you
know
super
human
efforts
and
as
I'll
go
back
to
the
beginning
of
this
conversation,
one
of
the
things
that
I'm
trying
to
do
is
drive
people
to
come
to
okd.io
for
content
blog,
be
it
blogs
or
these
kinds
of
got
community
guides.
And
but
I
don't
know
if
that
really
helps
you,
but.
B
It
it
does
to
some
extent,
I
mean
like
that.
The
other
thing,
though
I
have
to
be
completely
transparent
about
like
why
we
created
that
repo
and
what
our
intentions
were
when
we
created
it,
and
this
is
why
we
called
it
notes
originally,
because
we
really
wanted
to
capture.
You
know
where
we
were
addressing
a
problem
that
we're
seeing
internally,
which
is
that
you
know,
especially
for
things
like
vsphere
users,
have
an
incredible
number
of
options
that
they
can
exercise
when
deploying
their
cluster.
B
So,
like
here's,
the
hardware
that
I
had
set
up
and
like
here's
a
couple
notes
on
what
I
had
to
do
to
get
vmotion
working,
so
we
weren't
necessarily
trying
to
get
like
full
like
front
to
back
like
install
the
whole
cluster
guides.
We
wanted
just
a
place
where
someone
could
go
and
say:
well,
I'm
thinking
about
doing
a
home
lab.
Let's
say,
and
I
want
to
use
this
type
of
hardware,
what
what?
B
A
As
you
know,
if
it's
available
and
as
much
verbosity
as
you
can
with
and
and
and
that
I
think
and
then
and
then
we
can
also
when
a
new
release
comes
out
say
this
has
been
depreciated.
You
know
this
no
longer
works,
you
know
or,
and
then
then
we
could
also
add
in.
Maybe
you
know,
maybe
in
the
guide,
the
way
that
I
think
this
is
the
way
diane
thinks
is
an
appendix
of
like
notes
about
vmotion.
A
A
A
So
that's
that's
where
I'm
coming
from
and
nothing
in
your
repo
right
now
does
that
you
have
a
bare
metal
thing
and
you
don't
have
the
single
node
thing
so
those
those
little
structural
things.
I
would
love
to
see
that
done
in
the
next
couple
of
days,
so
that
I
could
put
a
blog
post
out
and
on
openshift.com
and
on
okd.io
that
drives
everybody
to
okd.io.
A
The
more
one
will
be
able
to
track
who's,
contributing,
as
opposed
to
contributing
to
okd
versus
contributing
to
mike's
repo,
which
is
important
to
me
as
a
community
person
and
also
give
credit
to
folks.
And
then
you
know
if
mike
gets
hit
by
a
bus
and
diane
gets
hit
by
a
bus.
Okay,
d.I.o
still
lives
on
and
diane
is
not
planning
for
either
of
those
things
to
happen.
A
A
If
you
want
to
weigh
in
and
help
him
with
the
home
lab
one
and
not
the
home
level,
the
single
node
cluster,
one
that
would
be
great
and
bruce
since
you
were
sitting
through
all
of
charo's
stuff,
that
one
fits
it
and
robert.
You
are
guinea,
pig
external
viewer
of
this
to
see
if
we
got
the
structure
right,
how's
that.
D
A
D
A
A
D
A
And
robert
and
eric
are
both
pointing
out.
A
good
thing
is:
what
license
are
we
going
to
put
all
this
under
and
let's
bring
that
one
up
at
the
meeting
next
week
and
I
will
poke
charo
about
it
between
now
and
then
about
why
why
he
chose
gpl3,
I
I
don't
know
and
if
that's
a
stopper
but
as
eric
points
out
it's
text,
and
maybe
we
just
need
to
put
creative
commons
there
somewhere,
but
yeah.
That
is
a
conversation
we
should
have
next
week.
So
we
have
30.
B
Minutes
because
I
had
a
similar
thought
to
eric's
when
I
was
looking
at
the
apache
license,
I
was
I
originally
just
put
the
apache
license
in
there
because
I
knew
it
would
be
yeah.
I
think,
like
a
cc
by
sa
or
something
would
probably
work
for
everything
there
yeah
charo's
gpl3,
notwithstanding
diane,
like
I
loud
and
clear,
I
hear
what
you're
saying
I'll
try
to
get
all
these
changes
made.
You
know
before
next
tuesday,
so
we
can
review
it
at
the
meeting.
B
I
think
you
know
most
of
the
stuff
should
be
straightforward.
I'd
like
to
change
a
little
bit
of
the
language
in
the
readme
and
kind
of
update
it
to
make
it
more
user-friendly
and
I'd
also
like
to
put
readme's
in
the
subdirectories
so
that
we
can
help
index
better
what
people
are
seeing
there
so
that,
just
if
people
come
and
look,
they
have
an
idea.
What's
going
on,
writing
rewriting
some
of
charo
stuff
is
going
to
be
like
difficult,
but
you
know
maybe
we
can
just
kind
of.
B
A
Yeah,
so
what
I
I,
what
I
really
like
to
do
is-
and
the
same
with
craig
robinson
is
like
like
putting
in
a
link.
A
link
in
the
template
is
a
link
to
the
a
video
walkthrough
I'll
link
to
the
original
source,
so
that
people
get
cross-referenced
and
we
get
some
flow
going
back
and
forth.
I
this
isn't
to
replace
a
medium
blog
post
or
an
openshift.com
or
the,
even
though
the
sysadmin
blog
post
that
bruce
shared
with
us.