►
From YouTube: 2019-11-05 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
A
B
C
A
A
A
B
A
B
B
Maybe
there
wasn't
an
issue
anyway,
there's
a
backward
PR
open
that
should
be
ready
and
nothing
at
all
told
us
to
have
the
PR
to
the
board.
So
we
can
see
it.
How.
A
B
C
B
A
A
C
B
A
Seems
like
we're
we're
tracking
a
lot
more
or
including
a
lot
more
pull
requests
on
the
board.
Then
we
had
before
you
know
like
previously.
Historically
speaking,
we
have.
This
just
been
in.
You
know
tracking
issues
on
the
board
only,
but
if
you
see
a
fair
amount
of
pull
requests
now,
does
that
mean
that
we
don't
have
issues
for
these,
or
is
this
just
we're
putting
the
pull
request
into
the
load
to
the
board?
That's.
C
C
B
C
B
All
right
and
yeah
I
guess
the.
If
there
is
an
all,
my
approach
has
been
if
there's
an
issue,
let's
make
sure
it's
on
the
board,
not
the
pull
requests,
but
occasionally
there
are
smaller
fixes
where
law
requests
just
gets
opened
without
an
issue
and
the
poor
quest
describes
everything
you
know
just
as
as
an
issue
would
so
you
know
those
from
my
perspective
tracking
it
with
the
pull
request
has
been
fine
mm-hmm.
C
B
A
B
A
B
B
It's
not
so
much
about
the
board.
I
mean
overall
we're
talking
about
one
month
until
roughly
a
month
until
we
release
so
we're
and
with
holidays
and
coming
up
were
coop
con.
We're
really.
We
don't
really
have
a
lot
of
time.
Honestly,
I
think
it's
time
to
start
finishing
things
up
and
getting
ready
for
that.
We
did
have
the
feature
freeze
just
before
Thanksgiving
the
last
week
in
November
I
wanted
to
propose,
since
we
don't
have
a
lot
of
features
coming
in
that's
the
last
moment.
A
B
D
C
B
B
A
Yeah
one
thing
that
I
found
that
works
that
has
worked
fairly
well
is
like
when
you
do
a
feature
freeze
that
you
that's
the
same
time
at
which
you
branch,
you
create
the
release
branch
as
well,
so
that
which
essentially
opens
up
master
again
for
for
future
work
on
the
next
release,
but
and
then
up
fixes
or
reliability,
stability,
etcetera.
It
just
goes.
A
A
Alright
ready,
then,
let's,
let's
move
on
down
to
the
the
community
topics
here
so
cube.
Con
is
in
two
weeks
basically
super
exciting
times
down
here
in
San,
Diego
I've
been
I've,
been
doing.
Everything
I
can
to
make
sure
San.
Diego
is
ready
for
you
all
right.
So
when
you
guys
show
up
here,
we
should
be
ready.
A
It's
a
note
here
is
that
the
next
community
meeting
is
scheduled
for
to
the
Tuesday
that
basically,
the
first
official
day
of
coop
con
Monday
is
the
zero
day
events
and
then
Tuesday
is
the
official
kickoff
of
the
conference,
and
so
we
will
not
have
a
community
meeting
that
day.
People
can
we'll
just
skip
that
one
and
go
and
have
the
next
one,
but
we
do
have
a
rook
booth.
It
is
hosted
in
the
CN
CF
s--
project
pavilion
area,
so
we
can
have
plenty
of
conversations
at
that
rook
booth.
A
B
A
A
B
C
E
A
Cool
good
good
good.
Thank
you.
What
great
thing
one
thing
interesting
I
noticed
in
the
language
used
by
the
CN
CF
and
in
talking
about
the
project
pavilion
that
it's
they
said
specifically
that
people
that
the
booth
should
be
the
since
the
project:
maintainer
Zoar
ambassadors,
first
I,
haven't
even
heard
the
term
ambassadors
into
the
CN
CF
and
second,
that's
a
requirement
that
I
don't
feel
very
strongly
about.
Honestly,
if
coding
once
is
involved
in
the
project-
and
they
want
to
be
there
talking
about
the
project,
then
I
have
no
qualms
with
that
whatsoever.
Yeah.
C
You
know
I
agree
to
the
it's
just
a
catch-all
word.
Cuz
I
was
like
what
does
that
actually
mean?
It
doesn't
mean
anything.
It
means
so
long
as
you
are
knowledgeable
about
rook
about
the
open-source
project.
Can
do
it
in
an
open,
user-facing
community
way.
You
can
be
an
ambassador
for
rook,
so
be
great
to
have
some
maintainer
zon
there.
But
anybody
like
anybody
on
this
call
would
be
totally
fine
on
there.
In
my
opinion
and
I,
don't
think
the
CN
CF
for
the
object.
I
think
that's
what
that
is,
somebody
that
knows
about
it.
C
A
B
A
I
have
no
hang-ups
on
their
language
to
use
their
I
thought.
It
was
interesting
but
yeah
like
let's,
let's
have
folks
there
that
are
interested
engaged
in
knowledgeable,
and
you
know,
let's,
let's
connect
with
people
at
the
conference.
That's
fine
of
me
sweets,
yet
only
two
weeks
so
excited
about
it.
God,
I
love,
cube
cons,
probably
more
than
I
should
I
get
under
rationally
excited
about
I
love
it
alright,
so
CI
stuff.
So
we're
we've
been
talking
on
the
tests
channel
with
Chris
Meyer
and
Adam
and
Travis.
A
So
we
need
to
copy
the
ami
over
to
the
rook
account.
It
looks
like
Adam
just
added
a
link
for
how
to
copy
a.m.
eyes
across
accounts,
so
I
have
access
to
both.
So
I
can
follow
up
on
that
and
get
the
ami
over
there.
Perhaps
can
you
help
me
understand
what
that
what
that's
blocking
right
now,
it's
a
priority
for
me
to
do,
but
I
just
want
to
understand
better.
What's
the
what
part
of
the
flow
breaks
without
that
am
I
right
now
well.
B
A
A
A
That's
what
my
understanding
has
been
is
that
if
you
want
to
change
it
and
add
it,
you're
gonna
have
to
build
stuff.
So
you'll
need,
like
you,
know
the
process
around
that,
as
opposed
to
just
having
the
am
the
product,
the
artifact
I
I,
don't
know
how
useful
that
is.
If
you
want
to
make
updates
in
a
repeatable
way,
at
least.
C
A
B
B
Our
security
reports
so
tomorrow,
assuming
the
patch
release
goes
out
today,
potentially
tomorrow,
he's
gonna,
try
and
remove
the
ones
that
we
mentioned
in
in
slack
a
couple
days
ago
and
run
the
build
and
if
it,
if
something
fails,
then
let's
revert
to
a
previous
snapshot.
So
we
can
not
be
down
if
something
was
wrong.
What's
removing
those
plugins.
A
The
sorry
Travis
Lee
had
the
the
plugins
for
the
rock
Jenkins
like
there.
There
is
some
Croft
in
there
I
was
mean
you
sent
that
list
of
plugins
over
I
was
kind
of
surprised
about
the
historical
you
know
legacy
that
this
was
demonstrated
in
there.
So
there's
a
lot
of
things.
I
think
we
can
clean
up
and
keep
updated.
We
hear
that's
something
we
haven't
not
done.
A
good
job
is
updating
the
chicken's
plugins
and
version,
etc.
B
And
just
a
note
that
our
build
was
broken
on
Friday,
because
a
tool
we
were
depending
on
changed
its
process
for
how
its
it's
published-
and
this
is
a
as
a
y/q
tool
for
gamal
processing,
so
it
was
fixed,
but
it
was
kind
of
disturbing
that
we
were
bringing
something
external.
So
we
should
look
through
ways
to
prevent
these
things
when
we're
pulling
in
extra
external
tools.
So
we
had
to
pull
in
the
tool
instead
of
building
it,
because
it's
build
relied
on
going
1.13
with
the
new
modules
support.
I.
B
Just
open
that
last
night
so
got
a
few
general
changes
in
there
and
tried
to
get
things
in
there
force
F
that
I'm
aware
of
the
other
storage
providers,
I'm,
not
aware
of
what
needs
to
be
in
there.
I've
like
we
can
go
ahead.
I
pinged
storage
providers
to
ask
for
input
on
it.
I
haven't
heard
anything
yet
so
I'll
I'll
do
one
more
pain,
and
but
people
can
now
open
the
yard
separately
to
you.
There's
no
real
need
to
get
into
the
same
one
but
yeah.
B
A
B
This
is
Sebastian,
Wagner
I,
don't
see
him
on
the
call,
so
this
is
so
for
a
while
Sebastian
has
been
generating
a
Python
client,
basically
for
a
rook,
so
I
can
use
it
from
manager
modules
in
SEF
and
it's
like
Oh
every
time
something
changes
and
rook
well.
He'd
have
to
go
generate
this
separately
and
well
kind
of
makes
sense
to
just.
Let's
just
do
this
in
the
rook
repo
we're
generating
the
going
client
with
you
know
that
make
code
gen
come
in.
It
just
makes
sense.
B
I
think
further
make
code
gen
to
also
generate
the
Python
client,
and
then
it's
solve
version
at
the
same
time
that
no
need
for
a
separate
process
here
so
I
mean
this
is
the
first
instance
of
anything
really
Python
related
we've
gotten
the
repo.
So
if
there's
I
can't
think
of
any
reason
not
to
do
this,
but
do
let
us
know
if
there's
any
any
thoughts
around
this.
B
C
B
A
So
do
you
think
that
that's
something
that
you
know
if
there's
value
in
this
that
could
be
done
in
it
in
a
general
way
like,
however,
so
we're
generating
going
clients
for
all
the
storage
providers
that
we
could
do
that
for
a
Python
one
for
all
the
storage
spreaders
as
well
or
as
you
know,
we
could
do
that.
Do
you
think
it's
better
to
do
that
on.
A
B
A
B
Yeah
I
need
to
remind
myself
if
this
is
just
implemented
first
stuff
right
now
or
had
a
change
for
Cassandra
I.
Think
in
there
too,
but
yeah.
Oh,
this
PR,
actually
right
now
is
still
just
using
his
referencing,
his
his
other
Python
client
generator.
So
there's
a
comment
about
changing
it
so
that
we
would
bring
his
library
in
to
rogue
basically
for
this
generator
in
Tobruk.
So
that's
not
done
yet
in
this
peer
is.
A
A
Okay,
yeah,
it
simply
can't
be.
It
would
be
ideal
if
you
know
to
have
some
sort
of
upstream
convergence
there
that
you
know
Python
client
generators,
I
thought
thought
there
was
one
for
you
know
just
general
kubernetes
usage
and
if
there's
deficiencies
in
that
one,
it
would
be
nice
for
the
upstream
ones
to
get
the
same
benefits
or
functionality
that
we
would.
You
know
we
would
be
needing
and
using
for
ourselves.
D
D
This
topic
of
moving
T
NFS
operator
to
operator
SDK
I
mean
I,
am
doing
hydrant
discussion
and
we
thought
that
moving
to
the
operator,
SDK
will
be
a
better
option
for
Dirac
I
guess
because
the
operator
kit,
I,
don't
think
much
development
is
happening
over
there
and
operator.
Sdk
has
a
good
community
support
currently
and
as
most
of
the
operators
running
operate,
openshift
or
using
the
operator
SDK,
and
it
also
solves
some
of
the
real
life
problems
like
upgrading
and
they
basically
be
oil,
import
oil,
timbrels,
so
I
guess:
ok,
moving
it
to
operators.
D
A
Yeah
I've
definitely
been
a
fan
of
the
controller
runtime
and
the
framework
and
approach
they
used
for
writing.
Scalable,
reliable
controllers
in
kubernetes,
I
love
the
controller
runtime
I've
been
using
in
a
couple
different
places,
but
I'm
not
as
familiar
and
intimately
knowledgeable
about
like
other
parts
of
the
operator.
Sdk
like
the
owner
operator
operator,
lifecycle,
management,
OLM
stuff,
so
I
would
need
to
have
a
little
more
education
on
that
I
think
er
yeah.
D
D
D
D
C
A
Awesome
all
right,
yes,
so
I
got
a
couple
action
items
here
that
I'll
follow
up
on.
We
put
my
name
next.
Were
there
any
other
pull
requests
or
community
topics
that
folks
wanted
to
bring
up
today?
Here.
D
Yeah
so
I
had
a
topic,
so
I
mean
I
was
thinking
of
adding
a
go
report
card
kind
of
schools
for
a
VP
R,
because
I
was
actually
thinking
of
so
I
mean
we
don't
have
any
torii
that
actually
gives
us
the
quality
control
or
the
code
quality
control
for
little
project.
Like
I
mean
we
should
have
a
mechanism
to
actually
take
the
piace
absolutely
gates.
The
food
quality
and
I
mean
I
just
started
a
check.
The
go
report,
third
of
our
looks
and
I
think
that
we
can
actually
improve
the
quality
of.
A
A
C
A
B
A
E
D
A
I
think
in
general
you
know
an
engineering
best
practices
or
engineering
quality
standards
is
always
a
good
idea.
The
trade-off
is
often
around
finding
the
right
set
of
standards
that
are
appropriate
for
a
project
that
you
know
translate
into
measurable
or
actual
gains
in
quality
versus
restrictive
Ness
to
contributor
years.
So
it's
always
a
trade-off
that
needs
to
be
thought
through,
but
in
general
you
know,
having
taking
steps
to
improve
quality
and
quality
is
always
a
good
thing
in.
E
Regards
to
like
fixing
your
current
issues,
I'm
a
finger
musing
like
a
set
of
flint
us
in
visual
studio
like
well
default.
I
think
this
would
be
kind
of
one
of
those
actions
like
if
the
documentation
where
we
would
basically
have
someone
like
prolly.
You
have
to
go
through
all
files
and
fix
the
lint
issues
that
we
have
then
agreed
on.
So
I
think
Travis
likes
to
read
some
more
just.
B
A
Those
those
have
the
lot
of
value
when
you
like,
for
when
you
generate
documentation
from
like
api
documentation
like
on,
go
docs
or
if
you
generate
other
documentation
in
some
way
than
that
you
use
those
to
generate
your
documentation
for
having
those
always
updated
or
always
existing
basically
gives
you
free
documentation,
which
is
really
useful.
Yeah.
E
I
think
it's
not
only
about
having
like
go
dug
or
something
or
like
what
I'm
trying
to
do
like
the
automatic
ce
o--
year,
documentation
generation.
It's
also
that,
if
I'm
going
through
the
code
and
then
for
some
reason
using
a
value
or
something
off,
the
struct
I
can
just
like
jump
to
it
and
see
the
comment.
What
it
does.
Yeah.