►
From YouTube: 2019-09-11:: Ceph DocUBetter Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
Sure
so
a
LinkedIn
either
pad
document
as
a
success
team
is
been
working
on
just
gotten
started
on
it.
Really
terms
of
changes
were
making
initially
right.
Now
we
want
to
address
the
introductory
material
to
self-assess
and
any
related
information
as
to
how
it
works
from
an
architectural
standpoint
to
help
improve
understanding
among
our
user
base.
How
success
works
with
a
time
to
consult
the
ancient
papers
that
were
written
about
it
about
15
years
ago.
So.
B
So
far,
we've
had
two
meetings
on
it.
The
team
is
just
getting
started
with
doesn
t
if
they're
starting
tests
in
terms
of
what
documentation
will
be
written,
but
this
is
going
to
be
a
regular
thing.
We
do
every
two
weeks
we
evaluate
how
we
can
make
it
better
and
what
gaps?
There
are
the
mean
filled.
B
There's
the
introductory
page
for
Stefan
fest,
which
currently
doesn't
have
a
lot
of
information
about
what's
emphasize,
is,
and
it's
using
a
pretty
old
diagram
that
was
just
showing
the
user
space
all
or
block
diagrams,
for
we
talked
to
the
chef,
that's
being
reworked
in
a
pull
request
linked
at
the
bottom
of
the
etherpad
three:
zero
zero
one.
Four
and
there's
a
doc
render
available
I'll
just
go
ahead
and
into
that.
B
The
links
chat
so
right
now
we're
improving
the
so
this
improves
the
the
description
of
what's
emphases
and
how
it
works
and
then
also
provides
an
architecture.
Diagram
might
not
be
completely
happy
with
how
this
diagram
looks,
because
it
maybe
is
a
little
too
specific
to
how
the
metadata
works,
but
I
know
I,
think
I'm.
Okay
with
it,
we
will
think
about
changing
in
the
future.
B
B
Let's
see
one
of
the
issues
we
identified
it
additionally,
is
that
there's
also
two
table
of
contents
force
ffs,
there's
one
at
the
bottom
and
there's
one
on
the
left
and
they're
kind
of
redundant
or
this
the
one
on
the
bottom
is
kind
of
redundant.
Although
it's
organized
a
little
better
than
the
one
on
the
left,
so
I've
asked
Melin
to
reorganize
that
or
to
use
the
standard
table
contents
on
the
left.
Try
to
organize
it
so
that
it's
easier
to
digest
by
users.
B
There's
also
an
effort
by
Varsha
to
improve
the
high-level
requirements
or
communicated
users.
Mainly
that's
just
that's
fine,
this
user
or
the
operator
needs
to
have
some
MDS
is
available.
They
need
to
pools
in
the
Anthes
that
have
ease
for
the
clients
they're
going
to
connect
to
the
cluster
I.
Believe
that's
going
to
be
I.
B
The
ratio
is
working
on
improving
the
Quick
Start
document.
There
were
number
of
issues
relating
to
that
I
think
in
particular,
it's
still
referencing
SEP
deploy,
which
is
on
life
support
and
not
something
I
think
we
generally
recommend
to
new
users.
So
we
want
to
try
to
avoid
mentioning
that
and
also
make
sure
that
the
current
QuickStart
actually
works.
I
think
he's
already
found
several
problems
with
it,
though
even
the
process
about
being
that
I.
A
B
These
would
these
are
things
we
normally
reference
from
papers,
but
we
want
to
have
that
also
as
part
of
the
inter
documentation,
so
that
it's
current
there's
a
few
differences
with
house
ffs
used
to
be
implemented
in
particular,
hard
links
are
no
longer
kept
in
the
table
they're
now
in
lined,
and
we
have
primary
and
remote
entries
and
directories,
which
is
quite
a
bit
different
from
how
it
is
described
in
this
FS
papers.
So
we're
going
to
be.
B
B
B
Jeong
is
going
to
be
talking
about
the
clients.
Direct
access
to
the
data
pool
that'll
be
include
how
files
are
striped
and
what
kind
of
authentication
permissions
are
required
by
clients
in
order
to
access
the
data
pool,
I'll
touch
on
rathaus
namespace
usage,
for
example,
by
Manila
and
soon
SEP
CSI,
and
how
you
can
create
credentials
which
give
clients
only
access
to
the
part
of
the
data
pool
that
they
should
have
permission
to
use.
B
B
B
The
then
Joss
is
also
documenting
me
on
this
format
of
I
knows
it's
something:
that's
a
somewhat
of
a
big
gap
within
which
chef
has
documentation.
I,
don't
think
we
have
anything
that
really
goes
through
the
Howey,
how
anything
is
actually
represented
on
disk,
so
this
will
go
a
long
way
towards
improving
onboarding
developers
with
how
the
automated
is
actually
stored
in
rows
and
then
Ramon
Ramon
has
been
working
on
the
manager
volume
plug-in
volumes
plugin,
which
is
used
by
Chef,
Geoscience
and
vanilla.
B
B
A
There's
one
thing
that
I
wanted
to
bring
to
your
attention:
there
are
than
some
documentation
parts
that
have
been
reported
already
by
users
and
I
think
you're
already
addressing
it.
But
there
are
just
fighting
a
couple
of
sacrifice:
items
on
this
etherpad
that
I
just
shared
with
you.
So
if
you're
addressing
edges
feel
free
to
blink
the
pull
request
or
whatever
tracker
or
something
do
those
there's
one
about
a
quick
dart
thing
which
you
just
mentioned,
that
Rishabh
is
working
on
and
I
think
there's
something
about
self
is
Korres.
A
A
B
A
All
right
well,
then,
I
think
this
looks
great.
Maybe
we
should
just
I
know
you
were
tracking
that
separately
in
other
meetings.
Maybe
we
can
follow
up
on
this
after
a
month
of
one
and
a
half
months
to
just
see
where
we
are
and
what
else
got
added,
and
we
can
discuss
that
in
a
public
forum
like
this.
A
Okay,
all
right,
well,
I
think
the
next
thing
we
have
on
the
agenda,
but
I
don't
see
anybody
else
from
graders
here
it
Sam
just
left.
So
we
discussed
a
bunch
of
things
and
we
almost
fell
short
of
time
in
that
last
meeting.
So
we
did
write
down
a
bunch
of
gaps
and
Rados
care
documentation,
but
we
haven't
assigned
them
or
created
trapper
issues
for
them.
So
that's
one
thing
that's
pending
on
us.
We
can
probably
do
that
offline
and
give
an
update
in
our
next
meeting.