►
From YouTube: 2019-03-13 :: 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).
B
In
the
pool
request
now,
I
only
on
the
meet
up,
I
wanted
to
share
some
methods
and
comments
which
are
used
while
I
back
working
and
updating
the
10
version
of
tough
documentation.
I
prepared
some
snippets
for
demonstration,
I
guess
I
will
push
it
to
repository,
and
then
you
will
decide
to
work
with
or
not
and
how
to
perfect
better,
because
I
don't
have
too
much
time
to
contribute.
B
A
B
A
B
C
C
C
B
If
you
manage
to
figure
out
how
to
resolve
the
conflict
with
bash
script,
you
can
put
some
comments
here
and
resolve
both
then
cherry-picks
automatically.
After
all,
conflicts
are
done.
We
just
passed
forwarding
the
branch
name,
commit
to
the
release
branch
and
remove
the
temporary
branch.
If
something
goes
wrong,
you
just
remove
that
release
branch.
Can
it
from
your
repository
and
for
convenient
at
the
end,
I
put
the
loop
to
push
all
commits
to
the
target
repository.
Do
not
do
it
so.
A
B
A
B
I'm
not
completely
understand
I
try
to
rephrase,
so
we
have
some
changes
in
the
master
branch
about
the
commentation
and
we
want
to
move
that
and
meet
park
to
the
attendant
releases
branch.
Back
yes,
for
these
goals,
you
will
like
check
out
to
that
branch
and
do
charity
X
money
from
the
master,
and
this
clip
exactly
do
that
you
will
do
manually,
but
it
kind
of
semi
manual
the
instrument
to
do
it
automatically,
because
if
you
don't
have
some
conflicts
with
old
branches,
it
will
it
will
cherry
pick.
B
A
B
B
Yes,
so
you
can
rethink
and
just
remove
all
the
temporary
branch
and
think
how
you
can
look
for
different
changes
in
a
little
bit
different
day.
That's
happened
with
me
when
I
have
a
lot
of
conflicts
which
I
cannot
back
port
correctly
because
they
don't
understand
how
to
do
it
during
the
days
cherry
picking,
yes,.
B
B
B
So
this
it
called
bull
bulldog
and
all
that
is.
Does
it
just
go
through
that
releases
check
out
and
try
to
build?
The
commentation
are
the
mind,
think
what
should
be
done
is
just
clean
completely
the
depositor,
a
repository
to
install
instant,
install
exactly
that
version
of
libraries
on
of
instincts
or
whatever
and
I
have
some
problems
that
are
not
all.
B
Packages
was
removed
from
build
dog
directory,
so
I
had
to
put
some
parameter
from
that
and
then
I
ran
just
admin,
build
dog
and
copy
the
build
documentation
to
build
full
dog
which
I
exclude
from
cleaning
and
a
repository.
Yes,
that's
all
for
building
the
commentation
in
bunch,
but
I
actually
spent
a
lot
of
time
for
doing
that,
because
one
version
of
documentations
is
building
about
15
minutes
and
completely
rebuilt
pool
ten
releases
it's
about
hours
in
my
computer.
B
So
that's
why
I
spent
about
day
and
night
to
finish
that
concept,
not
because
of
it
was
too
difficult,
but
because
of
a
lot
of
time
where
I
just
had
to
read
some
loved
books
and
wait
for
when
the
documentation
will
build,
and
sometimes
it
didn't
build
because
of
some
mistakes,
and
it's
actually
painful
a
little
bit.
So
you
have
to
think
a
lot
to
avoid
this
situation.
B
B
Development
process
because
that
to
script
was
not
enough,
so
I
put
it
here,
for
example,
like
a
demonstration
on
flow.
How
I
made
it
so
we
add
some
snippets
to
the
master,
and
now
we
want
to
cherry-pick
it
to
all
10
comments.
We
will
not
do
it
if
there
will
a
lot
of
conflict,
but
let's
try.
Oh
I
see
my
commit
I
get
the
hash
of
commit
and
I.
Do
admin
apply
to
all
dogs
and
clash
of
commit.
B
B
Think
it's
not
good
idea
to
just
add
it.
You
should
take
in
consideration
so
I
just
keep
cherry
berry,
big
console,
no,
not
continue
our
abort.
This
cherry
pick
get
back
to
a
moisture.
B
This
snippet
I
used
for
monitoring
of
building
documentation
and
you
can
estimate
by
the
changing
time
and
directory
how
fast
you're
building
and
this
snippet
I
used
to
rebuild,
for
example,
master
branch.
So
if
I
in
master
and
I
want
to
rebuild
documentation
include
rebuild
documentation
in
master
first
to
command
a
Korean
or
the
directories
run
the
build
script,
remove
previous
master
documentation
and
put
your
building
documentation
again.
B
So
if
I
want
to
build,
for
example,
quintero
I
will
replace
here
in
there
and
put
it
common
to
common
shelf
and
the
last
one
was
for
resolving
the
cherry-picks.
Let's,
let's
go,
for
example,
brain
get
shipped
out
for
in
terror,
and
we
want
to
back
port
some
information.
But
we
want
see
not
only
the
conflicts
which
were
made
by
our
comment,
but
we
want
to
give
the
difference
between
master
and
admin.
I
setup,
my
gift
to
use
melt
as
gift
tools.
B
B
Light,
let's
do
like
Arab
dog.
Oh,
we
see
that
the
exactly
difference
it's
on
the
printing
and
I
guess
you
will
mock,
though,
or
more
than
enough
it
just
old
five
hundred.
That's
all
and
you
can
analyze
this.
Actually.
I
am
NOT
an
expert
in
things
in
any
case,
so
I
as
I
write
in
pull,
request
description,
I
have
the
pebbles
feel
poor,
pull
request,
I!
B
Guess
it's
jewel
on
our
giant
and
Firefly,
but
I
write
it
anyway.
You
will
see
it
I
guess
in
file,
F
releases,
yeah
yeah,
so
dumpling
infernals,
travel
and
crackin.
So
there
are
some
obsolete
rings
and
you
had
to
back
port
and
restore
it
also
when
I
poured
back
the
select
and
the
color
line,
I,
not
I,
guess
I
not
considered
the
pink
model,
torture
and
just
put
back
maybe
some
extra
content.
Maybe
I
not
put
some
required
content
so
review
that
in
that
then
all
requests
before
merging.
B
A
B
Because?
Because
because
they
really
are
not
sure
about
sinking
sinks
and
think
structure,
I
just
wanted
to
achieve
that.
It's
work
when
they
see
that
select
is
done
I.
It
was
okay
for
me
and
I
changed
their
code
and
sphynx
config
file
slightly
randomly
just
to
put
it
work.
Yes
and
it
yes.
I
have
the
last
notice
about
the
commendation.
I
heard
that
Google
started.
B
You
action
about
isn't
of
dogs.
Maybe
you
should
apply
or
somehow
engage
documentation
collaborators,
because
in
some
part
of
documentation,
it's
kind
of
untrustable
and
should
be
checked
in
a
lot
of
a
lot
of
ways.
For
example,
we
have
been
telegram
or
Russian
I
chat
and
first
I
read
about
the
blue
story.
That
is
awesome.
B
It's
thin
provisioning
and
then
I
went
to
that
chat
and
I
found
out
that
sometimes
in
a
lot
of
situations,
file,
FS
backend,
it's
work
better
than
booster
because
of
some
nice
optimization
that
it
will
be
better
in
next
releases
of
them
and
not
in
meaning.
So
some
points
are
questionable
in
some
documentation
sometimes,
but
I
cannot
manage,
which
exactly
now,
just
don't
notice
it
I
guess
that's
all
what
I
wanted
to
say:
okay,.
B
A
B
And
one
I
remember
one
more
thing
which
I
wanted
to
tell
it
think
about
torture,
because
maybe
that
solution,
it
still
can
be
like
a
workaround
which
work
here
and
right
now.
But
maybe
it's
better
to
split
that
self
development
repository
and
some
documentation,
repository
and
use
the
development
of
visitorial
as
just
get
sub
model.
B
But
you
should
kind
of
experiment
about
that
and
understand
how
its
usable
and
comfortable-
because
maybe
it's
not
worth
or
spent
too
much
time
to
manage
these
two
repositories
and
this
cooperation
and
just
use
that
way
and
while
I
am
putting
my
salad,
also
I
apparent
eventually
fixed
that
warning,
which
actually
not
told
in
I.
Guess
dogs
kept
calm,
for
example.
B
Yeah
I
know
I
know:
III
wanted
to
just
show
your
the
concept,
because
I
don't
have
too
much
time.
I
just
want
to
show
your
way
and
you
can
just
take
over
and
fix
it
from
your
side.
It
will
be
great
if
you
do
it
in
one
two
days:
I
guess
maybe
three
days
we
have
some
collaboration
issues.
It
looks
like
not
too
difficult,
but
I.
A
C
B
Sorry,
sorry,
just
do
it
from
your
site:
I
don't
have
time,
and
you
can
just
put
my
stand
off
and
everything
that
will
be
fine.
I
just
wanted
to
make
the
documentation
better
I
not
have
too
much
interest
in
it,
but
it's
really.
It
will
be
really
useful
to
not
get
confusing
candid
and
exactly
I'm
here,
I,
just
ranked
and
forced
you
to
get
over
that
concept
and
penalizing
as
soon
as
possible.
A
B
B
When
I
already
found
that
script,
he
was
already
prepared.
I
pulled
a
lot
of
comment
reference
about
the
names
because
somewhere
it
was
easy
to
hard-code
the
colors
mode,
for
example.
Then
somehow
generate
this.
The
range
itself
just
gets
from
that
JSON
that
Kimmy
rates
from
your
llamo,
while
I
yeah,
I,
guess
I.
Let's
go
to
that
release.
B
A
C
A
B
B
B
Yes-
and
here
you
add
this
file
already
all
this
JavaScript
and
first
time
when
I
add
the
select
I,
try
to
figure
out.
Why
there's
well
three
losses
in
that
select
because
it
was
advice
and
first
time,
I
removed
this
one
and
just
put
here
the
relative
reference.
But
then
they
realized
that
I
way
is
booted
in
the
quantify
and
you
need
just
fixed
there.
All
previous
releases
and
configuration
of
the
schemes
and
also
generation
of
our
previous
swings
releases.