►
From YouTube: CDS G/H (Day 1) - Wiki IA
Description
https://wiki.ceph.com/Planning/CDS/CDS_Giant_and_Hammer_(Jun_2014)
24 June 2014
Ceph Developer Summit G/H
Day 1
Wiki IA
A
All
right
here
we
are
at
the
last
the
last
gasp
of
day
one.
This
one
should
be
nice
and
short
I
just
wanted
to
throw
this
on
here.
It's
not
strictly
developer
related,
so
I'm
assuming
I'll,
see
you
know
the
number
of
people
from
participating
shrink
like
rats
from
a
sinking
ship,
but
I
did
want
to
talk
about
the
the
wiki
a
bit
because
I
know
a
lot
of
times
when
we're
out
in
the
community
we're
talking
about
various
resources
that
people
want
in
terms
of
informational
and
otherwise
a
lot
of
times.
A
The
answer
is:
oh
yeah,
hey,
that'd,
be
really
good
to
have
in
the
wiki
and
I
had
a
huge
massive
Billy
backlog
of
things
that
were
would
be
really
good
in
the
wiki
and
they
just
hadn't
made
it
there.
Yet,
due
to
you
know,
usually
busy
levels
of
people
so
I
wanted
to
get
all
of
those
things
kind
of
in
a
single
location
and
the
blueprint
sounded
like
the
best
place
for
that
figured
people
could
weigh
in
and
fill
in
the
gaps
and
or
shuffle
things
as
it
made
sense
for
other
people.
A
That
weren't
me
so
I
guess
I
can
run
through
the
the
quick
list
of
kind
of
what
we
were
looking
at
in
terms
of
resources
to
go
into
the
wiki.
In
addition
to
what
we
have,
that
also
needs
to
get.
You
know
fleshed
out
a
little
bit
more
and
then
from
there.
Maybe
we
can
add
a
few
things
and
I
can
start
plugging
some
stubs
into
the
wiki
and
beg
borrow,
steal
and
or
otherwise
forcibly
acquire
some
content
generation
resources
from
elsewhere,
though
I
guess
we'll
just
run
down
the
list.
A
A
Let's
see
the
event,
calendar
it'd
be
nice
to
have
everything
that's
going
on
in
the
community
posted
up
on
the
wiki
somewhere.
That
people
could
just
add
to
a
lot
of
this
is
already
there.
You
know
we
have
the
meetups.
We
have
some
event
calendar
stuff,
but
I
would
like
to
flesh
that
out
and
make
it
a
little
bit
easier
to
play
with.
A
Let's
see
what
else
steph
tools,
community
contributors
I'd
like
to
start
highlighting
things
that
are
going
into
SEF
for
plugging
into
SEF
things
that
are
not
necessarily
Red
Hat
created
various
other
things
that
are
going
into
it.
There
have
been
a
number
of
things
that
people
have
said:
hey
I'd
like
to
list
my
tool
or
my
plug-in
or
my
product
or
whatever
I-
think
the
wiki's,
probably
good
enough
place
to
do
that.
A
There's
a
lot
of
room
for
procedural
back
in
the
wiki
I'm
hardware
compatibility
guide,
I
think
we
already
took
a
good
swing
at
this
internally,
I'd
like
to
get
some
of
that
stuff
up
on
the
wiki,
so
that
you
know
some
of
our
hardware,
resellers
and
partners
and
stuff
can
edit
it
themselves
and
really
get
a
good
place
to
go
for
people
that
are
starting
off
with
their
stuff
cluster.
That's
usually
the
very
first
question
I
get
asked
I.
Think.
B
Yet
I
think
guess,
but
the
only
got
the
only
key
thing
is
there.
There
needs
to
be
like
some
sort
of
you
can
tell
how
many
people
have
validated
hardware
configuration,
because
otherwise
every
person
is
like
works
on
my
box
and
then
somebody's
gonna
say
it
sure
doesn't,
and
so
in
order
to
have
some
confidence
that
the
compatibility
thing
is.
You
know
that
more
people
successfully
running
apply
should
like
these
people,
use
it
and
vouch
for
it
or
something
like
that.
I,
don't
know
it's.
A
I'll
see
what
else
community
swag
we've
got
a
number
of
different
ways
that
you
can
get
swag.
We
even
had
a
t-shirt
store
at
one
point:
I,
just
don't
think
it
ever
went
public
I.
Various
people
asked
me
hey.
How
can
I
get
a
SEF
t-shirt
or
how
can
I
get
this
data?
A
The
other
thing
it'd
be
nice
if
we
could
have
a
resource
for
either
our
own
build
up
of
swag
and
or
if
anyone
else
wanted
to
you
know
print
t-shirts
or
whatever
we
could
do
license
and
whatnot
see
what
else,
but
why
we
contribute.
That
was
a
request
from
somebody.
I
just
put
it
in
here.
To
have,
for
completeness
sake,
don't
know,
I
won't
spend
a
lot
of
time
on
that
academic
outreach.
This
is
something
that
I've
long
really
wanted
to
do.
A
This
is
like
I
think
one
thing
I
talked
to
stage
about
like
before
I
got
hired.
You
know
I'd
really
like
to
turn
things
like
the
google
summer
of
code
into
pushing
SEF
towards
the
university
level,
whether
those
hackathons
or
curricula
or
whatever
I
know.
Red
Hat's
got
a
big
academic
outreach
program.
A
Maybe
we
could,
you
know,
ride
the
coattails
there,
but
it
would
be
nice
if
people
that
are
involved
in
academia
could
maybe
help
with
that,
but
be
a
good
place
to
start
is
on
the
wiki
orchestration
of
deployment.
There
are
a
million
in
four
different
orchestration
and
deployment
tools
and
recipe.
Flavor
things
it'd
be
nice
to
start
documenting
some
of
that
and
maybe
trying
to
consolidate
that
down.
A
What
else
a
committer
listing
I
know:
Loic
did
a
nice
job
with
the
he's
got
a
script
that
he
runs
for
each
release
so
that
we
know
which
committers
were
involved
in
which
release
it'd
be
nice
to
get
that
may
be
a
bit
more
publicly
visible.
I
I'd
really
like
to
start
making
our
devs
up
it
more
visible.
I
mean
one
of
the
first
steps
of
this
was
the
technical
committee.
If
the
tech
leads
those
kinds
of
things,
but
I
would
definitely
like
to
get
people
a
little
bit
more
recognition
for
their
work.
C
A
Okay,
yeah
that'd
be
good
start
I'd
like
to
see
that
I'll
see
what
else
road
map
stuff
sage.
This
is
probably
more
us
the
component.
The
technical
lead
folks,
is
to
get
the
roadmap
up
start
doing
more
visual,
like
representation
of
what
we're
doing
so
that
people
can
add
a
glance
see
what's
up
yeah.
B
C
B
B
A
B
A
Abstract
yeah.
B
A
B
A
But
yeah
it
would
be
nice
to
get
that
yeah
more
more
visible
and
then
oh
yeah,
the
the
Chum
Bucket
paper
cuts.
This
is
something
that's
kind
of
been
hanging
around
and
and
attempted
in
half
ass
variety.
A
couple
of
different
times
just
to
find
a
small
contained
feature
development
tasks.
You
know
small
coding
tasks,
they'll
contain
bugs
things
like
that.
A
Try
to
find
easy
ways
for
people
to
get
involved,
to
have
a
prepackaged
thing
and
just
say
yes,
go,
do
that
and
have
them
have
something
you
could
hand
them
and
then
what
else
Oh
identifying
and
abstracting
out
some
high-value
documentation
stuff,
like
especially
the
early
on
things
like
if
you
want
to
do,
come
up
to
speed
quickly
on
SEF.
These
are
the
dozen
things
that
you
need
to
read.
A
You
know
whether
it's
the
quick
start
or
a
tuning
guide
or
orchestration
deployment,
whatever
like
identifying
some
of
that
and
pulling
it
out
and
making
it
more
community
maintained,
then
having
it
get
lost
in
the
in
the
wash
of
SEF
docks,
though
I
mean
that's,
that's
the
big
list
of
what
I
think
is
important,
I
kind
of
fleshed
out
a
rough
structure
of
how
it
might
look
in
the
wiki.
Is
there
anything?
B
Took
it
at
a
high
level,
this
looks
good
I,
think
I
mean
looking
at
the
at
the
hierarchy
and
the
etherpad.
The
thing
that
stands
out
is
under
development,
there's
much
of
tasks
that
has
the
sideboard
Chum
Bucket
and
paper
cuts,
but
there's
all
so
planning
that
has
like
blueprint,
submissions
and
I
wonder
if
there's
a
way
it
seems
like
those
those
should
be
sort
of
together.
Somehow
I,
don't
know,
I'm
I'm,
not
sure.
B
A
I
mean
the
development
and
the
planning
sections
were
always
very
like
I,
don't
know
if
I
would
call
them
siblings,
but
definitely
close
cousins.
The
the
development
session
was
probably
more
of
like
the
seed
stuff
and
the
doc,
whereas
the
planning
was.
This
is
the
actual.
What's
going
down
right,
but
I
mean
you
know,
it
was
wasn't
terribly
well
in
a
thought-out
and
architected
at
the
very
beginning
it
was
just
kind
of
let's
plug
a
hole.
A
B
B
C
A
A
C
C
A
A
B
B
B
So
we
need
to
I
mean
I,
get
people
to
use
that
brag
yeah.
A
B
A
B
Just
dumps
the
whole
thing,
yeah,
maybe
a
little.
We.
A
B
C
B
A
A
I'll
be
the
first:
that's
not
something.
I
want
to
trail
blaze,
yeah,
all
right!
Well,
I'm
I'll,
help
promote
SEF
brag,
a
bit
yeah,
but
all
right
cool.
Well,
it
doesn't
sound
like
there's
a
whole
lot
of
feedback
on
the
wiki
stuff,
so
it
means
we
must
be
at
least
semi
on
the
right
track
or
at
least
doing
enough
work
that
people
don't
want
to
yell
at
me
too
loudly
so
I
guess
we'll
get
started
on
this.
A
They
can
always
you
know
it's
it's
a
living
thing,
so
we
can
always
hit
it
hard
later,
but
cool,
maybe
maybe
we'll
get
eric,
is
alan
suppose
Eric
stop
by
diddy.
Is
this
pretty
late?
Where
he's
at?
Isn't
it
Lois
where's
where's
Eric
from
by
the
way?
I
don't?
I
guess
I
never
knew
where
he
wear
his
geographic
location
was
Eric's.
The
new
user
committee
chair
yeah.
A
All
right,
well,
I,
guess
we'll
wrap
this
up
really.
At
least
it's
now
documented
in
video
format
and
people
can
poke
at
the
etherpad
and
the
blueprint
if
they
have
anything
truly
pressing
that
they
feel
like
weighing
it
on,
but
other
than
that
I
guess
we'll
we'll
start
plugging
away
and
then,
if
we
can't
get
something
on
alright.