►
From YouTube: 2023-09-19 Rook Community 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
So
I'll
do
a
quick,
Milestone
checkup
here
so
1.11
we
did
the
1.11.11
release.
Last
week.
That's
a
lucky
number
11111.
A
B
A
Everything's
in
the
done
column,
nothing
really
planned
for
1.11
but
again
yeah
the
1.11
project.
It's
for
that
release
is
still
in
the
phase
where
we
we
can
backboard
fixes,
if
needed,
but
generally
we'll
just
focus
on
1.12
as
far
as
the
fixes,
yeah,
okay
and
then
1.12
and
moving
on
to
that,
so
we
had
a
1.12.4
release
last
Thursday
as
well,
and
those
release
notes
are
out
here.
I,
don't
know
that
we
need
to
call
any
of
them
out.
A
A
And
so
1.12
oops
type
of
dot,
five
would
tentatively
be
in
two
more
weeks,
so
we'll
keep
on
the
bi-weekly
release
Cadence
for
now,
and
that's
tentatively
next
week
on
the
28th.
A
Okay,
moving
along,
if
there's
no
questions,
the
1.13
project
report
is
created
so
that
hadn't
been
created
as
of
our
last
meeting,
but
we
have
a
few
things.
A
A
The
road
map
was
updated,
I
guess
I
could
put
a
link
to
that.
But
just
briefly
I'll
take
a
glance
at
that.
The
road
map
or
1.13
is
here
just
a
few
high-level
features
were
included
here
just
so
we
can
have
an
idea
of
where
we're
going,
but
it's
still
open.
If
people
want
to
request
features
in
that
list
or
we
can
plan
others.
A
Yeah
always
open
to
feedback
on
what
will
be
an
upcoming
releases
were
if
we
look
back
at
the
Timeline,
where
were
we
so
the
standard
timeline?
It's
it's
really
still
TBD,
but
currently
thinking
mid
to
end
November,
maybe
even
into
December
just
depends
on.
If,
if
there
are
any
features
that
we
feel
like,
we
need
to
get
in,
I
feel
like
it'll,
be
more
of
a
Cadence
release
where
we'll
be
just
releasing
at
the
around
that
four
month
mark.
A
A
All
right,
then,
moving
into
the
community
topics
and
that
are
in
the
agenda.
So
if
we
first
one
I
just
wanted
to
bring
up
is
that
we
have
ours,
Nick
the
Snickers,
the
security
scan
tool
that
we
have
run
with
our
CI
and
every
time
we
merge
something
it
scans,
the
latest
code
to
make
sure
we're
up
to
date.
A
As
of
recently,
we
started
getting
a
failure
from
it
around
the
new
hashicorp
license
with
mpl2o,
so
I've
looked
into
this
briefly,
but
need
to
to
finalize
kind
of
what
we
need
to
do
about
this
I
believe
that
Upstream
were
not
really
affected
by
the
new
license,
because
we're
just
using
the
libraries-
and
we
don't
have
a
competing
product
if
there
are
downstreams
around
Rook.
A
What
I'm
not
clear
yet
is
if
there's
any
issues
with
that
license
or
or
Downstream
products
and
So
based
on
investigation
that
still
really
needs
to
be
flushed
out,
then
either
we
suppress
this
error
from
the
Ci
or
or
we
need
to
fix
it,
which
may
mean
removing
features.
I'm,
not
sure
I
haven't
looked
into
Alternatives
either.
For
that.
B
Okay
for
feedback
yeah,
I
I
haven't
looked
into
it
specifically
from
the
case
of
Rook,
but
I
have
looked
into
the
the
terraform
licensing
or
the
I
guess.
This
is
hashicorp.
License
changes.
B
So
I
believe
the
greater
like,
like
the
Highway
like
hasher
Corp
community,
essentially
just
forked
everything
and
made
the
what's.
It
called
the
open
TF.
B
Entity
which
is
now
part
of
the
Linux
Foundation
I,
think
this
all
happened
extremely
quickly.
B
So
here's
like
their
Manifesto,
which
is
I
I,
don't
and
not
the
word
I
would
choose,
but
there's
that's
like
what
they
call
it
there's
the
manifesto
that
they
published
and
how
they
they
break
things
down,
and
it
essentially
I
think
they
they've
just
like
forked
all
these
things
and
continue
using
I
think
the
Apache
license
I
forget
exactly,
but
this
is
this
should
be
like.
Everyone
can
use
these
Forks
that
were
like
basically
the
moment
before
they
changed
the
licensing
over
and
I.
B
Think
the
thing
from
here
is
probably
to
see
what
hashicorp,
as
a
company
does
like.
Do
they
roll
back
their
decision
and
then
also
seeing
what
the
community
does?
Does
the
community
really
just
stop
using
the
Hashi
for
like
stuff
and
keep
using
the
like
the
stuff
that
is
actually
upstream
and
Upstream
licensable?
B
What
else
yeah
I
think
there
is
an
amount
of
wait
and
see
and
I
I
think
at
least
that
IBM
also
do
we
want
to
kick
out
Sasha's
autopilot
here
we
keep
getting
this
this
person
or
this
automated
bot
and
weekends.
A
Okay,
yep.
B
Repeated
the
situation
is
the
larger
situation.
That's
driving.
The
discussion
is
that
hacky
Corp
changed
from
an
open
source
license
to
the
the
business
license,
which
my
my
understanding
of
it
in
brief,
is
that
they
say
you
can
look
at
the
code
for
free,
but
if
you're
a
competitor,
you
cannot
use
the
code
in
your
product,
so
I
mean
the
without.
B
Essentially
yeah,
the
discussion,
that's
like
happening
on
like
Reddit
and
elsewhere
is
people
are
like
okay,
like
what
does
this
mean,
and
it's
like
well
hashicorp
wants
their
cake
and
wants
to
eat
it
too.
They
want
to
say
we're
open
source,
but
not
actually
have
an
open
source
license.
It's
really
just
a
if
a
source
available
for
viewing
license
yeah
they
just
like.
B
Did
this
suddenly
one
day
and
naturally
something
going
from
open
source
to
you
know
this
sort
of
middle
Place
license
is
not
one
people
are
happy
about,
and
then
anyone
you
know
like
can
change
what
their
definition
of
a
like
competing.
Like
a
you
know,
quote-unquote
competing
businesses
at
any
time.
C
Okay,
thank
you
Blaine
for
the
explanation,
so
I
do
have
some
thoughts
about
licenses
in
general,
which
I
would
like
to
share
in
in
a
few
seconds
so,
and
how
does
this
harsh
coupling
affect
us?
Probably
it
does
because
we
are
using
some
of
the
libraries
as
dependencies
is
that
correct.
B
It's
just
it's
legally,
very
unclear
and
partly
just
because,
like
the
Fairly
short
amount
of
time
that
has
you
know,
that's
gone
on.
It's
been
like
a
month
or
maybe
five
weeks
since
this
license
change.
It's
like
how
Apache
verb
is
going
to
be
legally
going
after
entities
if
at
all
and
yeah,
so
I
I
guess
like
the
best
suggestion
that
I
have
currently
is
to
use
things
from
the
open
TF
like
I
guess
like
open,
terraform,
Foundation,
okay,
they
use
things
from
their
Fork.
So.
B
E
Right
and
I
don't
think
they
have
any
plans
to
I.
I
think
that
a
pragmatic
thing
to
do
immediately
would
be
to
change
the
depth
to
a
previous
version
to
still
under
an
OSI
approved,
license
and
pin
the
version
for
now
I
mean
I.
Think
the
issue
was
caused
by
you
know:
gaps
getting
bumped
in
go.mod,
so
we
could
just
back
right
back
to
a
version
of
Vault
prior
to
license
change.
That
kind
of
fixes.
The
stick
error
for
the
moment.
E
C
Even
I
mean
not
knowing
details
about
the
energy
Corp
license
here,
it
doesn't
really
matter
because
we
still
need
to
use
licenses
or
code
in
a
way
that
is
licensed,
compatible.
I
fully
agree
with
that,
and
so
that's
what
we
need
to
do
and
so
address
sounds
very
reasonable
and
a
good
approach
to
do
with
that
essentially
essentially
fix
the
versions
of
the
dependent
libraries
in
the
go
mod
file
and
then
update
those
versions
once
they
hopefully
have
adjusted
their
license
to
be
compatible
again
either
get
you
right
there
Josh.
A
A
Thanks
for
all
that
input,
then,
with
that
I
think
we
have
a
number
of
topics
around
kukon
and
presentations,
just
a
note
on
Thursday,
so
I'll
be
presenting
at
the
data
on
kubernetes
Town
Hall.
So
there's
a
link
in
the
the
agenda
there
to
that,
if
you'd
like
to
RSVP
to
that,
it's
yeah
Thursday
at
10,
A.M,
Pacific
I'm
just
going
to
talk
about
maybe
an
intro
to
rook
and
what
we
do.
A
So
the
dok,
the
data
on
kubernetes,
it's
okay,
yeah,
it's
kind
of
an
open
working
group,
around
storage
for
kubernetes
and
very
cool
yeah,
so
they
have
they
have
kind
of
their
own
community
and
and
everything
so
there
they
coordinated.
This
are
people
interested
in
storage.
E
A
Right
then,
I'll
really
be
official
video,
exactly
CTO
Brooke
got
it.
Okay,
that
might
be
might
be
good
on
my
license.
Plate
too
I've
got
a
rook
license
plate,
but
maybe
I
should
say:
Rook,
CTO,
okay,
all
right
yeah
moving
on
then
for
kubecons,
so
for
Yukon,
North
America
in
Chicago
there
is
a
keynote
video,
that's
completed
and
kind
of
cool,
with
the
that
their
team
did
with
making
that.
A
A
A
Let's
see,
kubecon
our
Coupe
de
India
coming
up.
I,
don't
think
grab
is
in
this
meeting
today,
but
I
know.
Several
talks
were
submitted
for
that
and
they'll
be
waiting
to
hear
if
those
were
accepted
and
then
finally
kubecon
EU
I.
Just
saw
an
email
today
that
that
event
for
March
in
Paris
France
the
cfp
is
open.
If
anybody
would
like
to
submit
talks,
play
direct
happy
to
review
them
and
that's
separate
from
The
Rook
maintainers
talk,
which
we
usually
get
essentially
for
free
by
being
a
graduated
project.
A
C
D
Don't
have
yeah
I,
don't
have
permission
to
edit,
maybe
I'm,
using
different
email,
ID
all
right
I'm
using
my
personal
email,
ID,
so
yeah
I
was
thinking
to
to
do
new
release
of
the
plugin
once
once,
I
restore
terminating
or
deleting
CRT
command
is.
Must
it's
been
few
like
I
think
one
or
two
months
since
last,
two
release
so
I
think
this
is
a
good
time.
Yeah
July
6th
was
the
last.
A
Yeah
definitely
sounds
good,
so,
after
after
merging
the
restore
command
yeah
delete,
it
deleted
restore
command.
C
A
A
C
E
If
this
is
the
yeah
I,
don't
even
know
if
it's
the
appropriate
venue,
but
I
saw
something
odd
last
night
and
I
haven't
even
dug
into
it
yet,
but
might
be
useful
to
know
if
anybody
else
has
seen
this
so
I've
been
talking
to
Mark
Nelson
and
he
said,
stop
using
a
bunch
of
or
stop
running,
multiple
osvs
per
nvme.
E
It
kills
the
enlarged
systems
so
switch
to
using
one
OSD
and
said:
okay,
fine
and
so
I
tried,
adding
some
new
drives
into
the
system
and
setting
the
config
value,
one
one
OSD
per
per
device,
and
it
does
not
work.
It
blows
up
with
a
bunch
of
back
traces
from
ceph
python
commands
which
I
haven't
dug
into
yet
a
bunch
of
weird
ones
about
not
being
able
to
open
the
admin
socket,
and
it
looks
like
partitioning
failures.
It's
weird:
it
works
at
two.
It
works
at
three.
E
It
works
at
four,
but
one
blows
up
so
like
five
minutes
before
the
meeting,
I
started
digging
through
GitHub
issues
and
there
may
be
something
related
I'm
curious.
If
anyone
has
seen
this
I'm
sort
of
I'm
really
suspicious
that
there's
nobody
in
the
world
who's
running
one
OSD
per
device,
so.
D
A
Never
heard
of
that,
you
know
a
difference
if
I
remembering
correctly
a
difference.
If
you
had
multiple
lsds
that
will
use
lvm
for
each
of
them
mostly,
and
if
and
if
it's
one
OSD
or
the
device,
then
it
will
just
use
raw
mode.
So
perhaps
there's
something
in
raw
mode.
That's
affecting
those
affected
by
the
devices,
but
usually
raw
mode
is
more
reliable
than
lbm,
so
that
that's
still.
E
A
A
C
I
was
trying
to
like
it
when
I
tried,
since
I
don't
have
a
DOT
IO
in
jail,
it
wasn't
letting
you
join
the
spot.
A
B
Oh
I
feel
like
I've
encountered
that
issue
and
it's
you
have
to
use
like
the
right
link
to
like
get
the
invite.
E
F
Maybe
it's
outdated
now.
F
I
don't
know
Travis
if
you
can
generate
a
new
invite
link.
I
can
update
the
index.html
for
the
website.