►
From YouTube: Velero Community Meeting/Open Discussion - May 25, 2021
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
Hello,
everyone
and
welcome
to
the
valero
community
meeting
today
is:
may
25th
2021
and
per
usual.
We
get
a
bunch
of
status
updates
and
maybe
some
discussion
topics
as
well.
I
would
please
urge
everyone
to
add
their
name
and
affiliation
into
the
attendees
list
here
in
the
hakimdi.
That
would
be
super
lovely
of
you
to
do
so.
We
can
see
who's
joining
in
the
meetings
and
who's
being
active
here.
B
B
B
I'm
running,
I
might
be
having
another
issue
now,
but
after
that,
so
I
just
want
to
test
before
I
hit
the
request.
Another
review
for
both
of
you
and
so
next
after
this
I
want
to
review
bridget's
plugin
version
in
dark
and
there's
another
pr
on
the
hook
for
reviewing
that.
I
want
to
tackle
and
also
I
need
to
update
the
carville
configuration
stuff.
B
B
C
Nolan
yeah,
I
don't
have
a
whole
lot
to
share
this
week.
I
have
a
google
doc
draft
of
the
velara
debug
command
that
should
be
open
for
comment
to
the
world.
If
it's
not
please
yell
and
I'll
fix
that
this
is
mostly
getting
what
was
in
my
brain
down.
I
still,
I
still
need
to
work
on
this
there's.
I
have
a
crash
diagnostic
script
that
I
need
to
toss
in
here
and
when
I
make
the
pr
it
will
be
a
an
extra
file.
C
So
whoever
takes
this
on
will
be
able
to
start
from
there.
I
don't
think
it's
going
to
be
a
huge
change.
In
fact,
I
don't
even
think
it's
going
to
be
a
huge
change
to
the
build
process
because
of
how
go
embeds
things
so
yeah,
that's
out
there.
I
welcome
comments,
but
this
is
an
early
early
draft
when
it
gets
a
little
bit
more
final,
I'm
gonna
convert
it
to
markdown,
I'm
also.
I
also
need
to
get
some
more
research
done
on
for
my
next
item.
C
C
I
think
I
can
do
that
based
on
schema
information
in
crds
now,
but
I
need
to
confirm
that
and
get
it
in
the
doc
and
then
reminding
folks.
This
is
my
last
week
as
a
full-time
valero
contributor.
C
I
suspect,
with
this
sprint
coming
to
an
end.
We
have
scheduled
sprints
every
two
weeks
and
this
one's
ending
this
week.
I
suspect
these
design
docs
may
run
over
and
I'll
commit
to
shepherding
those
forward,
but
then
my
focus
is
going
to
be
moved
on
to
other
things.
A
I'm
going
to
miss
you
here,
nolan,
thank
you
so
much
for
for
everything,
you've
done
for
the
the
project
and
everything
you
do
here
for
the
community.
D
Maybe
just
a
sad
face
for
no
one,
but
thank
you
again
for
everything
yeah,
so
I
feel,
like
last
week
was,
was
pretty
distracting
for
me
just
dealing
with
some
final
stuff
as
part
of
heist
move,
but
I
I've
been
trying
to
catch
up
on
pr
reviews
and
I'd
like
to
request
some
feedback
on
the
plug-in
versioning
design
dock
that
I
shared
last
week.
D
I
was
hoping,
maybe
that
we
could
talk
about
it
as
part
of
the
discussion
topics
today,
but
fong
is
not
on
the
call-
and
I
know
he's
he's
really
interested
in
this
work.
So
I'd
like
to
do
within
presents
maybe
I'll
set
up
a
different
meeting
for
interested
parties
to
discuss
and
also
ashish
is
just
back
from
pto
as
well,
and
I
know
he
had
feedback
to
give
not
necessarily,
but
I
know
he
was
interested
in
this
particular
work
that
was
going
on.
D
So
I'd
really
like
input
from
him
as
well
or
at
least
to
have
had
some
time
to
review
the
talk
before
we
discuss
it.
So
I'll
defer
that
to
another
day,
and
that's
it
from
me.
A
Sounds
good,
do
you
want
to
send
that
out
to
the
valero
group,
or
do
you
want
to
just
have
a
few
select
people
invited
to
the
discussion
here.
D
I
can
send
it
out
to
the
group
in
case
there
are
others
that
would
be
impacted
by
this.
That
would
like
to
to
contribute
yeah,
I'm
not
really
sure
like
for
for
setting
up
other
meetings
like
what
is
the
best
way
to
do
it
in
terms
of
making
sure
that
you
pick
like
an
appropriate
time.
I
know
we've
done
this
for
for
other
pieces
work
before,
but
jones
was
just
wondering
if
he
had
some
input.
A
We
do
have
the
office
hours
already
scheduled.
We
could
use
the
office
hours
for
this
yeah.
That
would
work
as
well
yeah.
I
think
that
could
make
sense
just
send
out
an
a
notification
out
to
the
mailing
list.
A
Saying
hey
we're
doing
this
at
this
time,
so
we
can
send
out
a
an
extra
invite
just
for
that
date
as
well,
which
is
on
the
at
the
same
time
as
the
office
hours.
C
I
I
would
also
if,
if
that
doesn't
work,
I
think
you
should
start
there,
but
also
like
maybe
I
know,
scott's
interested
in
this
work
and
fong
is
so
maybe
double
check
with
them
to
see
what
time
is
good
for
them
and
then
schedule
it
and
who
can
make
it
can
make
it
otherwise
record.
A
Okay,
all
right
and
I
see
ashish
you
just
got
back
from
pto,
I'm
guessing
you
don't
have
a
lot
of
status
updates.
No,
I
don't
sounds
good
and
I
see
scott
on
the
call
as
well.
I
don't
know
if
you
have
any
any
status
updates
caught.
E
Nothing
for
this
week,
just
just
to
the
previous
point,
if
you're
talking
about
the
meeting
to
schedule
that
for,
for
example,
the
office
hours
this
thursday
that
works
for
me
just
let
you
know
that.
A
All
right
since
we're
postponing
the
plug-in
versioning
conversation
to
a
different
meeting,
do
we
have
any
other
discussion
topics
for.
A
Today,
nolan
or
kalisia,
were
you
able
to
run
the
contributor
script
for
this.
C
I
did
let
me
copy
that
in
there
is
actually
pretty
short.
It's
abby
and
scott.
C
So
abby
helped
flesh
out
our
document
documentation
on
compression
in
valero,
which
is
to
say
it
doesn't
do
a
whole
lot.
That's
worth
noting,
but
this
is
a.
This
is
a
thing
that's
helpful
for
us,
so
we
can
refer
people
back
to
it
and
if
we
need
to
link
folks
to
it
and
then
scott
updated
some
of
the
rustic
crds
to
be
correctly
identified,
where
they
weren't
being
they
weren't
being
associated
before,
and
I
think
this
is
for
conveyor.
If
I
see
here.
E
As
I
said,
that's
right,
we
already
had
that
uid
label
on
the
backup
and
valero
uses
that
internally,
for
you
know,
figuring
out
things.
I
just
added
this
and
we
were.
We
have
some
debug
code,
where
we're
kind
of
connecting
the
pod
volume
backup
and
restore
with
pvcs
to
kind
of
show
the
user
what
what
was
connected,
and
so
we
were
already
using
that
on
the
backup
side,
and
so
I
just
added
the
same
label
on
the
restore
site.
E
A
All
right
looks
like
we
do
have
one.
D
A
I
think
that's
a
that's
an
awesome
awesome
way
to
finish
up
the
the
community
meeting
end
on
a
high
note.
Again,
congratulations,
bridget
and
thank
you
so
much
nolan
for
for
everything.
E
A
Done
here
with
that,
thank
you
all
and
have
a
fantastic
rest
of
the
week.
See
you
all
next
week.