►
From YouTube: 2019-11-11 :: 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).
B
Yep
just
open
question
us:
how
does
this
work
for
for
rook
and
I?
Don't
think
it
I.
A
B
A
C
A
Okay,
so
it's
in
the
other
item.
There,
then,
is
the
the
client
Python
as
a
dependency.
So
we
discussed
that
in
the
the
rook
community
meeting
last
week
and
I
think
like
we
discussed
before
that
know
how
about
if
we
go
ahead
and
bring
the
tool
into
the
rook
repo
and
have
the
Python
client
libraries
emitted
as
part
of
the
rook
repo
and.
C
A
B
A
A
B
B
B
B
What
about
the
Antilochus
Twitter?
There
was
some
a
new
guy
from
red
head
that
also
wanted
to
look
into
and
go
right
now,
if
I'm,
not
mistaken,
I.
C
I
was
home
with
yes,
I
was
working
on
on
danceable
of
his
data
and
what
it
was
decided
to
stop
with
that
in
him,
follower
of
the
SSH
of
the
stator
and
to
mover
for
Charlie
in
the
SS
age
of
the
stator.
A
lot
of
reasons
in
depend,
ridi,
independent
of
my
opinion,
I-
think
that
it
was
another
okay.
But
this
is
not
important.
Important
is
say
what
what
is
thinking
most
of
the
people
and
probably
what
is
thinking
the
more
the
more
powerful
people.
C
So
it's
clear
that
what
what
I
have
what
I
understand
and
am
I
feeling
about
this
is
that
we
are
only
going
to
have
two
orchestrators.
This
is
a
2
cos
theta
and
the
rotors
or
cos
theta,
and
this
okay
from
the
other
part
Danny.
Maybe
Daniel
people
got
ok,
it's
pissing
in
my
team,
but
I.
Don't
know
why
this
has
been
dry
set
up
and
I.
Don't
know
why?
Ok,
I
think
that
no
I
don't
know
I,
don't
know,
because
it's
something
that
I
think
that
it
was
clear
for
everybody.