►
From YouTube: 2021-06-29 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
All
right
recording
is
started,
and
this
is
the
june
29th
2021
rook
community
meeting
we've.
I
think
we've
got
a
couple
discussion
topics
that
we
added
to
the
bottom
here,
but
we
can
start
on
our
milestones
first
as
usual,
so
travis,
I
believe,
you've
updated
all
this
here
for
our
latest
patch
releases
and
there's
nothing
for
1.5.
I
believe
right.
I.
A
B
A
B
Right
so
that
one
well,
we
just
did
it
last
thursday,
so
bi-weekly
would
be
next
week,
but
I
think
there's
a
couple
of
important
fixes.
We
want
this
week
if
we
can
at
least
if
we're
ready,
so
one
of
them
in
the
blocking
column
there
is
blaine's
working
through
with
gpt
partitions
wayne.
Do
you
want
to
explain
that
one
briefly.
C
C
The
last
atari
system
was
made
in
1992,
but
it's
still,
it
still
supports
these
atari
partitions
and,
like
any
kind
of
modern
partition,
will
have
a
header
with
a
magic
string
that
says
I'm
fat32
or
I'm
you
know
ms-dos
or
whatever,
but
atari's
version
of
that
to
my
understanding
is,
is
just
three
bytes
and
so
it's
very
easy
for
random
information
to
appear
as
though
it's
an
atari
partition.
C
If
the
kernel
is
built
with
atari
support,
so
we
were
seeing
with
like
the
switch
to
raw
mode.
We
were
seeing
then
the
the
kernel
is
detecting
that
there
is
an
atari
partition.
C
And
then,
when
rook
goes
to
like
run
the
provisioner
again,
it
sees
that
there
is
a
partition,
ls
block
and
yeah
ls
block
and
some
versions
of
like
block
id.
Don't
support
atari,
just
because
it's
so
old
and
then
they
see
that
it's
empty
because
it
doesn't
have
a
partition
type.
It's
assumed
to
be
empty,
and
then
we
deploy
an
osd
on
it.
C
But
there's
already
no
sd
on
the
disk,
and
so
we
end
up
getting
a
full
disk
osd
and
then
a
provision
or
a
partition,
osd
and
then
sometimes
that
partition
also
appears
as
an
atari
partition.
And
so
there
can
be
a
kind
of
an
arbitrarily
long
string
of
apparent
partitions
that
have
osds
deployed
on
them.
C
And
it
is
yeah,
it's
really
bizarre.
Ultimately,
the
the
solution
we
decided
to
go
with
is
to
only
support
gpt
partitions,
which
is,
I
think,
pretty
safe.
The
only
other
kind
of
modern
choice
we
have
is
to
support
gbt
or
ms-dos,
but
gpt
supports
disks
larger
than
like
two
terabytes
or
or
whatever
it
is
that
I
mean
really
like
there
are
so
many
modern,
hard
disks
that
are
larger
than
two
terabytes
that
I
I
don't
know
that
anyone
is
going
to
be
using
anything
other
than
gpt
anyway.
C
C
It
just
means
that
if
there
are
users
who
are
used
to
just
like
creating
partitions
that
are
untyped,
they
will
have
to
like
make
the
gpt
labels
on
on
those
partitions.
First-
and
I
have
yeah-
hit
a
snag
late
yesterday
with
some
of
this
volume
validation
which
doesn't
want
to
install
if
there
are
gpt
headers
on
a
thing
or
on
a
partition,
but
I
think
that's
something
we
will
probably
just
ignore.
C
I
updated
our
ci
environment
to
create
gpt
headers
on
the
partitions
and
to
reload
the
partitions
in
the
kernel.
So
I
think
now
it
is
the
issue
we're
hitting.
Is
the
ceph
volume
doesn't
like
gpd
partitions
either
it
just
wants
them
to
be
blank.
I
guess.
D
D
D
C
Yeah,
I
think
the
other.
The
other
option
we
have
is
to
is
to
use
parted,
to
figure
out
if
a
partition
is
atari.
In
my
like
first
iteration,
I
just
looked
to
see
like
I
looked
at
a
disk
and
then
tried
to
find
out
if
it
was
a
atari
using
the
tool
that
does
support
it,
which
is
parted.
C
D
Because
we
no
no
no,
we
we
own
that
code
instead
volume,
so
we
we
don't
do
anything
special
with
it.
D
Sections
yeah
from
a
few
fights,
I
guess.
B
A
It's
is
it
so
is
it
clear
for,
for
you
know,
blaine
and
travis,
to
hear
about
about
no
longer
using
sefolium
for
the
validation
phase
there
is
that
is
that
government's
pretty
aligned
on
that
one.
A
A
All
right
do,
maybe
maybe
we
want
to
table
that
for
for
right
now
and
kind
of
get
to
the
rest
of
the
milestones
and
and
other
agenda
items,
and
then,
if
we
want
to
at
the
end,
we
can
come
back
and
have
more
of
a
deeper
discussion
on
on
the
decision.
Around
self
volume.
D
A
Cool
all
right,
but
yeah,
it
sounds
like
a
good
fix
to
get
in
there
and
have
so
that
plane
is
to
get
that
in
1.6.
We've
got
tracking
it
as
and
blocking
the
release
there
too.
So
we'll
continue
making
progress
on
that
one.
Thanks
for
the
that
sounds
like
a
bit
of
a
journey
there
blaine
thanks
for
taking
us
down
that
journey.
That
was
interesting.
C
A
Cool
all
right,
okay
and
then,
and
then
1.7
coming
up
as
well
too
about
another
another
month
left
on
that
one
it
looks
like
so
who
wants
to
go
over
some
highlights
important
things
here:
progress
on
1.7
with
about
a
month
out.
B
Well,
the
I
guess
the
dates
proposal.
First
of
all,
I
think
we
brought
it
up
at
the
last
meeting,
but
just
since
you
were
out
I'll
cover
that
again,
I
think
if
we
get
the
beta
release
out
around
july
21st
and
then
shoot
for
the
release
a
week
later
on
the
28th
that
just
seemed
reasonable,
keep
us
on
the
cadence
of
about
every
quarter.
B
I
think
our
last
release
was
what
april
early
april
april
15th.
So
that's
just
over
three
months,
which
seems
fine
as
far
as
the
highlights,
so
I
didn't
get
a
chance
to
update
the
board
this
morning.
I
ended
up
having
all
sorts
of
meetings
that
were
unexpected
thanks
them,
but.
B
Yeah,
what
do
we
have
in
the
board
here?
Let's
see
stuff,
that's
mirroring!
Oh
there's
a
couple
of
things
fixes
I
think
we're
just
waiting
on
the
next
step,
release
for
16.2.5,
which
hopefully
will
be
any
day
now,
and
then
we
can
get
that
stuff
defense
mirroring
done.
Is
this
the
one?
This
is
the
1.7
board,
okay,
because
I
think
that
we're
going
to
put
that
in
the
1.6
board
or
project
the.
B
I
feel
like
there
may
not
be
a
lot
of
huge
new
features,
but
I'm
probably
forgetting
some
too
seb.
What
comes
to
your
mind
for
features
for
1.7.
D
D
B
D
D
Yeah,
it's
not
so
much
one
seven,
but
yeah,
I'm
really
hoping
to
get
the
smearing
as
well.
Well,
no!
Actually
it
is
one
seven.
What
am
I
saying?
The
first
mirroring
is
yeah,
it's
actually
in
review,
so
yeah
yeah.
This
is
a
big
highlight
for
for
one
seven,
just
waiting
for
for
seth
16.2.5.
B
D
Updates
yeah,
this
one
is
like
auto
configuration
of
it.
One
sex
was
more
like
you
can
deploy
this
first
mirror
demon
which,
later
on
we
realized
that
it
wasn't
really
working
because
of
some
internal
bugs,
for
this
mirror
so
yeah.
Definitely
this
one
is
the
real
like
implementation,
working,
end-to-end,
right
and
yeah,
hopefully,
key
rotation
for
cluster
encryption
as
well.
D
B
Oh
and
then
playing
all
of
your
work
around
dependencies
making
sure
we're
blocking
uninstall.
If,
if
you
have
dependencies
installed
a
bunch
of
that
work
using
that
to
do
column
or.
C
Yeah
yeah,
I
I
think
it
probably
will
also
spill
into
1.8.
I
don't
think
all
of
that's
gonna
gonna
be
quite
ready.
C
Yeah
but
potentially
I
also
think
that's,
okay,
I
think
we
we
have
the
core
like
we,
we
protect
the
stuff,
the
stuff
cluster
of
cr,
which
is
kind
of
the
most
important
thing
to
protect
anyway,.
D
A
Yeah,
that
sounds
good
and
progress
is
being
made
on
that
and
we've
kind
of
got
a
timeline
set
for
when
we'll
be
getting
to
the
release
and
depending
on
these
branches
and
stuff
like
that,
so,
okay,
all
that
makes
sense
any
other
comments
on
milestones
or
upcoming.
A
Releases
all
right,
let's,
let's
move
on
into
the
community
topics
section
here,
so
our
continued
progress
on
on
no
longer
needing
jenkins.
B
B
You
can
trigger
a
github
action
manually,
which
is
exactly
what
we
need
to
do
basically
to
go,
create
the
tags
and
then,
but
that
should
be
pretty
straightforward
other
than
that,
then
we
just
enable
you
to
enable
the
github
actions
to
build
and
release
from
the
release
branch,
which
is
already
working
in
master,
we'll
just
need
to
flip
the
switch
basically
for
doing
it
in
release,
builds
and
yeah.
I
don't
know,
I
think,
that's
about
it.
A
Other
service
for
the
tag
pipeline,
you
know
it's
creating
release
branch
and
pushing
a
tag.
Do
you
would
would
the
would
it
also
cover
scenarios
where
you
don't
need
to
create
a
release
branch?
You
want
to
tag
the
latest
patch,
like
1.677,
to
run
the
same
workflow
same
action.
B
A
D
A
Awesome,
that's
amazing,
but
that
might
if
there's
no
other
questions
on
that
that
might
segue
nicely
into
this
whole
milk
jenkins
account.
A
A
It's
so
is
it
brooke
jenkins?
That's
only
that's
only
being
used
like
for
the
jenkins
server
to
do
operations
with
github
right,
there's
not
is
that
being
used
in
any
other
tools
or
any
other
locations
that
you
were
aware
of.
B
A
Or
do
like
write
operations
like
create
tags
and
stuff
like
that
that
you
know
you
think
you
have
to
be
able
to
do
true
yeah,
it
should
be
really
limited
yeah
if
it's
only
being
used
in
the
like
within
jenkins,
is
the
only
like
originator
of
requests
or
operations
that
are
using
that
account.
Then
that's
might
be
able
to
just
sunset
that
account
too
and
not
really
have
it
around
like.
I
would
not
do
that
immediately.
I
would
keep
it
around
for
you
know.
A
B
D
A
A
Okay,
that
sounds
good
to
me
and
then
fossa,
lovely
fossa.
Did
we
trust
you
and
I
started
a
conversation
I
forgot.
Maybe
you
were
asking
about:
should
we
even
keep
using
it
like?
Do
we
need
foster
security
scanning?
Is
it
so?
Is
that
part
of
the
core
infrastructure
initiatives
badge
that
we
have,
that
we
need
to
keep
up
that
up
to
date
and
maintain
that
and
stuff
like
that?.
B
I
don't
remember
the
history
exactly,
but
I'm
pretty
sure
they've
wanted
it
and
it
makes
sense
to
have
a
passing
license
check
right.
It's
just
a
question
of
well.
This
thing
just
gets
so
many
false
positives,
because
it
goes
so
deep
into
all
the
repos
which
we
pull
in,
but
don't
even
reference,
really
the
things
or
use
the
code
that
it
thinks
we
might
be
using.
So
we
just
have
to
add
all
of
these
exceptions
or
disable
everything
it
finds.
B
A
B
And
I
need
to
look
again
at
their
last
response.
Their
support
did
respond,
but
I
don't
think
it
answered
the
problem
which,
which
is
well.
How
do
I
log
in
with
an
account
that
has
access
to
update
that
repo
the
exceptions,
because
every
time
it's
like
it
wants
to
force
me
to
log
in
with
my
github
token
and
okay,
when
I
do
that,
then
it
just
takes
me
to
my
private
forks
version
of
that
faucet
scan
which,
for
a
long
time,
I'd
been
adding
those
exceptions
or
silencing
those
things,
and
I'm
all.
B
Right,
geez
and
so
yeah,
I
feel
like
their
sport
has
responded
a
couple
times.
I
need
to
get
back
to
them
and
say:
well,
it's
still
not
working
and
and
then
ultimately
I
guess
the
question
is:
does
it
make
sense
to
keep
the
badge
if
it's
just
always
red?
We
don't
want
the
badge
if
it's
just
red
for
no.
For
a
reason,
we
don't
think
it's
good.
A
It
and
one
thing
that
their
support
had
said
to
me
on
not
for
rook
was
that,
like
their
their
go,
go-based
source
code,
repository
support
is
was
still
being
improved
or
built
out
better.
A
So
they
like
that,
you
know
they
recommend
like
doing
like
a
manual
scan
like
with
the
like
the
local
foster
cli
tool
to
get
started
for
a
repo
that,
like
is
able
to
just
do
direct
dependencies
and
as
opposed
to
going
through
like
the
entire
20,
something
k,
dependency
graph,
and
then
you
know
slowing
down
and
breaking
the
ui
and
all
that
sort
of
stuff.
That's
what
they
say
to
do.
A
I
don't
it
sounds
like
they
haven't,
really
improved
much
since
then,
if
they're
still
having
problems
with
like
the
dependency
graph
and
managing
that
and
sort
of
stuff
like
that,
so
it's
like
yeah,
like
there's,
there's
a
lot
of
issues
with
fossa
that
I
think
are.
I
haven't
seen
much
improvement
on
in
a
long
time.
B
A
What
oh
yeah
it
did,
do
we
have
a
stick
up
with
them
soon
looks.
A
A
Okay,
cool
well,
that
sounds
good,
so
that
blaine
you
added
this
issue
about
the
is
that
to
to
capture
the
discussion
from
earlier
on
the
crazy
atari
petitions.
Or
is
this
to
continue
the
discussion
with
stuff
volume
and
stuff.
A
Yeah
cool
all
right.
Well,
so
I
think
that's
most
everything
on
the
agenda.
If
folks
wanted
to
stick
around
to
talk
more
about
how
we
use
sapphium-
and
if
you
know
we
can
continue
relying
on
validation
or
updates,
we
want
to
make
etc.
A
We
continue
brainstorming
on
that
one,
but
otherwise,
though
we
can
see,
if
there's
any
other
issues
to
talk
about
and
adjourn
dude
you
you
all
like,
like
seven
blender,
I
think
they're
the
main
main
contributors
there
do
you
want
to
continue
talking
about
the
cephalium
usage
related
to
partition,
validation?
That
is.
C
Yeah
I
I
have
interest.
I
know
it's
also
getting
late
for
seb,
so
I
don't
want
to
like.
C
Okay,
I
don't
know
if
I
have
a
strong
preference,
it
might
I
mean
it'll
be
pretty
technical,
it
might
be
better
just
to.
A
Right
that
sounds
good,
then
you
guys
can
find
each
other
on
on
slack
or
whatever
get
that
get.
That
conversation
going
then
sounds.
Sounds
fine
to
me:
cool,
okay,
cool!
Are
there
any
other
items
that
folks
wanted
to
bring
up
with
the
group
here.
A
Okay,
sweet
all
right.
Well,
thanks
for
everybody
meeting
today,
we'll
keep
on
working
towards
the
1.7
and
then
hopefully
get
the
1.6
out.
Blanen
said
we'll
talk
more
about
atari
fun
times
and
good
to
see
everybody
this
week
take
care,
sounds
good,
yeah.