►
From YouTube: 2019-06-17:: 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
A
Let
me
share
the
link
all
the
links
in
our
welcome
to
place
Orchestra
meeting.
This
is
general
as
a
pad
and.
A
Yeah,
we
mainly
talked
about
the
SSH
Orchestra
and
less
about
the
rock
Orchestrator.
There
is
an
API
breakage
looming
in
the
rook,
so
the
idea
was
to
wait
until
that
API
breakage
is
known
or
resolved,
or
we
have
a
time
frame,
or
we
can
really
think
about
that
changes
in
the
Rope
Orchestrator
until
then,
I
think
it
make
doesn't
make
really
sense
to
look
into
the
Rajah.
The
meeting
itself
was
not
recorded,
so
the
only
thing
we
have
is
the
other
pet
food
burgers,
of
course,
welcome.
A
A
B
A
A
B
B
B
A
A
Yeah
Joshua.
E
I'm,
a
fellow
colleague
of
Sebastian,
also
work
in
Sousa,
so
far,
I
was
mainly
working
on
the
deep-sea
side
of
things.
So
that's
the
student
deployment
tool
as
you
may
know,
and
we
would
like
to
go
more
into
the
orchestrator
kind
of
side
of
things,
which
basically
means
that
we
would
like
to
port
all
of
our
core
functionality
in
upstream
land,
but
and
as
far
as
I
understood,
is
that
the
architecture
behind
this
is
not
quite
yet
ready.
So
that's
why
I
will
be
joining
this
meeting
in
the
future
and
also
would
like
to
contribute.
A
Daddy
yeah,
don't
think
that
we
have
anything
more
for
the
orchestrator
at
least
today,.
A
Just
dodging
about
up
great
testing,
so
we
now
have
a
text
in
the
upgrades
routes.
2019
is
a
patch.
That's
well
doesn't
look
so
bright
right
now,
so
we
really
have
to
make
sure
that
we
have
proper
testing
for
all
the
different
organs
with
applicants.
A
E
E
B
F
B
As
well
as
the
other
resources
know
how
it's
gonna
also
work
on
rook,
we
have,
we
have
a
lot
of
things
to
do
at
this
point.
For
the
next
release.
We
have
significant
amount
of
bugs
and
features
we
have
to
drive
to
so
I
think
our
side,
noise,
also
kind
of
focus
and
look,
that's
that's
that's
the
only
thing
I
can
tell
for
sure
yeah.
D
F
My
hope
is
that
some
of
the
more
interesting
parts
of
the
deployment
automation
that
defensible
is
doing
like
matching
devices
by
size
and
ID
and
making
sure
you
nodes
are
uniform
and
all
that
sort
of
stuff
that
eventually
we
can
move
that
up
into
maybe
not
into
the
orchestrator
layer
but
above
it
so
that
it
can
be
applied
both
to
rook
and
other
deployments.
I.
B
B
F
F
Or
having
the,
even,
if
there
is
like
a
set
bootstrap
script,
it
would
be
really
simple
and
it
would
just
call
out
to
take
the
set
theme
into
or
leverage
all
that
heavy
lifting
whatever
it
does.
Whatever
you
do,
blue
strap
with
ends
up
in
the
same
state
that
something
that
you
later
to
put
via
the
orchestrator
via
a
day
to
operation.
What
also
whatever
it
be
consistent,
yeah
and.
D
F
Yes,
yeah
that
might
be
yeah.
Maybe
we
don't
have
that
right
now.
The
idea
with
V
start
point
I
was
slightly
different.
The
idea
would
be
that
it
would
in
your
source
directory,
it
would
run
it
would
create
a
bunch
of
containers
and
run
the
cluster
so
that
inside
the
container
it
looked
like
it
was
a
bit
of
a
basic
install,
but
that
container
would
contain
all
the
stuff
that
you
just
locally
built.
D
F
But
Dan
does
have
a
pull
request
that
I
think
is
know
how
I
don't
know
how
close
to
this
is
done,
but
basically
that
will
just
it
just
like
make
container
that
just
builds
a
container
image
from
your
source
tree.
It
looks
very
similar
to
what
you'd
get
from
the
stuff
container
rich,
so
you
could
use
it
with
Brooke
or
with
this
or
whatever
else.
That
might
be
the
picture
and.
B
B
A
F
Don't
like
searching
around
for
other
container
registries,
we
can
or
should,
use
and
have
basically
struck
out
everywhere.
I've
tried,
so
I
think
we
just
need
a
runner
on
registry
wherever
on
whatever
machine
or
set
of
machines,
or
that
the
current
shaman
stuff
is
being
dumped
so
that
when
you
push
this
FCI,
you
get
all
the
Deb's
rpms
and
you
get
container
images
unofficial,
stuff
container
image
for
a
little
bit.
I
think
the
integration
with
the
Jenkins
stuff
actually
built
a
container
and
push
it
and
then
remove
it
when
it
gets
cleaned
up.
F
F
F
C
F
F
They
said
that
there's
also
a
way
that
you
can
just
instead
of
generating,
instead
of
using
a
I,
can
actually
actual
registry.
You
can
also
just
like
ticket
said
I
think
it
said
at
our
file
or
something
you
can
also
just
like
put
the
image
somewhere,
give
it
to
you
or
something
like
that.
Is
anybody
familiar
with
the
non
registry
workflow
for
bowling
an
image
you.