►
From YouTube: 2019-04-15:: Ceph Orchestration 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
A
Actually,
a
video
yeah,
the
select
image
is
a
bit
yeah
misleading.
If
you
click
on
the
link
and
absolutely
video
yeah
I
I
would
like
to
incorporate
that
into
the
drug
course
dates.
When
in
the
CIT
meeting
last
week,
post
me
a
bit
to
get
it
a
bit
done
a
bit
quicker,
so
I
looked
into
it
again
made
lots
of
look
Orchestrator
for
requests,
but
now
I
think
we
are
in
good
shape,
even
though
not
everything
will
end
up
in
the
next
naughty.
That's
really.
B
Did
your
or
read
I'm
talking
about
that
the
video
you
have
yeah,
so
they
oh,
yes,
policy,
so
that
just
to
summarize
what's
happening
so
that
you've
got
a
cluster
started
with
one
managers,
one
Mon
and
then
you're
just
you're!
Writing
these
commands
that
go,
create
OS
D's
on
disks,
which
updates
the
stuff
cluster
custom
resource
and
then
the
operator
goes
and
makes
it
happen.
Yep.
B
A
That's
everything
from
within
the
toolbox
and
then
yeah
I'm
we're
creating
or
modifying
the
surf
class
society
and
creating
a
safe
fire
systems,
yeah
CID,
and
not
not
the
definition
that
resource
itself
and
everything
ends
up
being
working
at
the
end,
even
though
I
haven't
really
test
that
place
itself.
So
it
might
not
work
in
the
end.
But
at
least
the
demons
are
starting.
A
Think
users
will
end
up
facing
some
issues,
but
in
general
it
is
working,
I.
Think,
for
example,
the
routers
gateways
done
nothing
to
be
shown
in
service
LS
in
the
end
and
I
think
also
the
routers
gateway
pulls
are
not
properly
created,
so
I
think
especially
the
rat.
The
raddest
gateway
is
not
properly
working
for
users,
but
the
Kurtis
error
just
needs
to
be
fixed
and
the
pull
requests
are
much
involving
okay.
B
C
A
So
melting
a
little
bit
and
by
new
B
by
using
for
the
next
note,
it
was
released
so
yeah
it's
going
to
get
much,
but
it's
not
yet
merged,
but
it
was
tagged
and
everything
it's
tagged
as
Nautilus
and
it's
right
now
still
attacked
with
URI
testing.
So
yeah
it's
going
to
get
merged
for
point
release
of
modulus.
B
A
B
B
A
A
B
A
B
B
C
B
One
upgrade
issue
that
ran
into
a
couple
days
ago
is
that
after
we
upgrade
from
mimic,
so
this
is
a
setup
grade,
not
that
rookie
upgrade.
So
if
you
upgrade
from
pre
Nautilus
to
Nautilus,
it
looks
like
there's
a
command.
We
need
to
run
to
enable
messenger
to
their
wise,
the
the
Mons
aren't
or
the
operator
isn't
able
to
communicate
with
Deb.
Did
you
see
that
issue
by
chance,
yeah.
B
D
D
B
Yeah,
it
goes
that
since
right
now
it
doesn't
block
on
one
Mon
at
a
time.
It
just
updates
all
three
months
and
then
I
still
buy
the
quorum.
That
and
thats
related
to
your
other
PR
that
you
already
have
in
front.
But
yeah
when
it
tries
to
validate
quorum,
looks
like
yeah.
It's
got
the
messenger
to
config
in
the
safe
Kampf,
but
then
the
bonds
are
only
enabled
on
messenger.
One
still
I.
A
B
F
D
F
B
Okay,
so
look
to
me
like
the
Mons
can
connect
to
each
other.
Just
fine.
Okay,
like
from
the
toolbox,
I
ran
SEF
status
and
it
says
everything's
in
quorum.
All
the
moms
are
healthy
and
in
quorum,
but
the
operator,
but
that
well,
interestingly,
the
toolbox
was
still
using
the
messenger
one
chef
comp
and
we
should
probably
reply
need
to
affixed
to
the
toolbox.
So
it
will
generate
the
messenger
to
left
calm,
but
the
operator
is
using
the
messenger
to
accept
calm,
so
they
can't
connect
until
we
enable
messenger
to
you.
But
is
it.
A
B
B
A
D
B
E
B
B
F
F
F
I
need
to
make
sure
and
see
if
there
are
any
updates
now
to
like
set
file,
system
or
SF
object,
store
and
I
want
to
go
through
and
apply
a
pod
security
policy
to
the
cluster
and
see,
if
anything
needs
to
change
there.
I
still
have
things
I
want
to
do,
but
the
like,
the
main
chunk
of
the
upgrade
is
has
been
that
and
the
documentation
updated.
F
B
B
Major
issues
found
so
far,
there's
definitely
some
are
a
bunch
of
things
we
need
to
get
in.
There's
a
backlog
still
like
to
get
get
in
in
the
next
few
days,
and
basically
we
want
to
walk
down
as
far
as
new
features
getting
committed
if
possible
and
just
call
it
bug
fixes
whatever
we
need
make
sure
we're
not
destabilizing
other
things,
but
we're
pretty
flexible,
though,
if
we
need
to
get
something
in
maybe
chief
Lori.
B
F
B
Then
one
other
issue
with
the
manager.
So
a
couple
times
in
the
last
week,
I've
seen
this
issue
where
the
manager
came
to
hang,
the
pod
was
still
running,
but
now
the
manager
is
down
according
to
SEF
status
and
I,
don't
think
we're
able
to
get
manager
logs
in
either
case,
unfortunately,
but
then
that
kind
of
raised
another
questions
of
well.
Should
we
be
running
to
manager
pods
in
rooks.
B
A
A
A
A
Another
meeting
yeah
I've
tried
to
contact
and
someone
from
F
I've
made
a
Scott
and
Jeff
from
redhead
regarding
a
meeting
on
the
Barcelona
Saturday
OSF
Alec
on
Saturday
haven't
got
the
rest
month.
Yet,
though,
if
we
want
to
do
a
meeting
in
Barcelona,
then
we
are
going
to
need
a
meeting
room,
possibly
or
hopefully
in
the
red
head
offices
possible.
I.
C
C
E
C
E
C
Not
too
much
to
add,
as
week
was
devoted
basically
to
downstream
issues,
okay
and
one
for
this
week.
That
is
going
to
be
very
short
for
me,
because
there
are
holidays
days
in
Spain.
So
I
think
what
my
plan
is
is
to
check
all
the
current
functionality
of
the
orchestrator
with
a
new
anti
runner
service
at
the
Mukasey
state
or
external
stator.
C
A
Financial,
okay,
do
do
we
have
any
other
topics
for
today.