►
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
Hi,
everyone
welcome
to
the
valero
community
meeting
today
is
tuesday
may
11th
2021
and
let's
kick
things
off
so
just
before
we
get
started.
If
you
haven't
done
so
already,
please
join
the
hack,
md
and
add
your
name
and
affiliation
to
our
candies
list.
That's
really
helpful,
just
so
that
we
know
everyone
who
is
here,
okay,
great,
so,
let's
start
things
off
as
we
usually
do
with
status
updates,
so
nolan
you're
up
first.
B
Yeah,
hello,
everyone,
I'm
sorry,
I'm
just
tossing
a
link
in
okay,
so
I
wanted
to
let
everyone
know
that,
as
of
june
1st,
I
will
be
working
on
a
different
team
in
vmware.
B
It's
been
great
working
on
valero
for
the
last
three
and
a
half
years,
but
there's
a
great
team
around
it
now
and
we've
got
some
new
external
core
maintainers.
So
I
think
the
project
is
in
great
shape.
I
can't
talk
about
the
group
I'm
going
to
quite
yet,
but
their
work
will
be
public
sometime.
I
I
don't
want
to
say
any
dates
and
get
trouble
so
yeah.
I
will
be
here
for
the
remainder
of
may
and
you'll
probably
see
me
around
I'll,
be
working
on
related
things.
B
With
that
in
mind,
I'm
committed
to
working
on
the
valero
debug
command
and
the
manifest
design
dock
that
I've
already
gotten
started.
So
those
are
going
to
be
my
big
objectives
for
the
month
of
may.
B
C
C
Yeah
right
after
right
after
yeah,
that's
like
two
and
a
half,
because
yeah
yeah
you're.
B
C
A
Yeah
definitely,
and
thank
you
for
for
everything
and
helping
me
as
a
new
member
get
up
to
speed.
I've
really
learned
a
lot
and
yeah
yeah
we're
definitely
gonna
miss
you.
A
Okay,
we'll
move
on
okay,
so
as
for
me,
I
was
like
on
pto
last
week,
so
I've
been
catching
up
after
that.
Apologies
to
folks
that
I
promise
a
design
doc
for
plug-in.
Versioning
too
I've
been
delayed
in
getting
that
out.
A
Things
have
been
a
bit
hectic
because
I've
been
moving
house,
so
that
is
my
focus
for
this
week.
I'm
going
to
try
and
get
that
out
to
everyone
as
soon
as
possible.
So
apologies
for
that.
C
Yeah,
so
let's
see
so,
we
spent
a
lot
of
time
going
through
the
issue.
Back
blog
we're
closing
some
things
prioritizing
some
things
found
some
things
that
had
been
fixed
and
you
know
hadn't
closed
the
issue,
so
that's
good,
and
so
we're
going
to
continue
working
through
that
eleanor
is
going
to
speak
a
little
bit
more
about
exactly.
C
What's
going
on
there,
I
tossed
in
a
test
that
I
had
floating
around,
that
did
multiple
name
spaces,
so
this
will
do
there's
a
basic
test
and
a
scale
test,
so
it
does
like
two
namespaces.
It
also
does
2500
spaces,
both
of
which
work
at
the
moment,
which
is
good,
and
then
I've
been
working
on
the
mythical
astrolabe
demo
for
a
bit
hopefully
should
have
something
to
show
in
june,
where
all
the
different
pieces
parts
fit
together.
C
So
working
on
getting
copia
in
getting
aws
block
volumes
in
and
getting
the
at
least
a
poc
of
the
valero
serializer
into
a
protected
entity.
So
we'll
have
more
on
that
soon
and
then
I'm
off
for
the
following
two
weeks
of
17th
to
the
28th
and
nolan
will
be
actually
taking
back.
The
tech
lead
hat
for
those
two
weeks.
B
Oh
and-
and
speaking
of
I
I
forgot
to
put
it
in
my
own
status-
I'm
doing
allergy
testing
next
week
over
the
over
the
community
meeting.
So
I
will
miss
the
community
meeting
next
week.
A
D
Eleanor
you're
up
next
sure
I
think
everyone's
seen
this,
but
I
just
want
to
quickly
advertise
it
here
as
well.
Last
week
we
ended
up
splitting
the
valero
channel
on
the
kubernetes
slack
because
we
had
like
a
lot
of
kind
of
it,
wasn't
clear
what
the
purpose
was.
So
now
we
have
valero
users,
which
is
for
users
to
help
each
other,
and
we
really
love
seeing
that.
D
D
We
always
like
to
see
you
ask
at
the
github
community
q
a
and
there's
pin
posts
on
either
channel
helping
you
with
that
or
just
ping
me,
and
I
can
help
you
with
how
to
find
that
also,
as
dave
said,
we're
doing
a
massive
backlog,
grooming,
particularly
well
time,
because
I'm
now
getting
on
to
the
project
but
understanding
need
help.
Seeing
all
the
issues
know
with
nolan
leaving.
We
want
to
take
all
the
history
he
has
on
them,
and
so
just
you
might
see
us
doing
this
in
the
next
week.
D
We're
dividing
we're
triaging
into
three
categories.
Current
is
something
that
we
may
address
in
1.7
or
1.8,
roughly
in
2021
icebox,
which
will
have
a
label
might
be
addressed
in
2.0
or
later
so
that's
2022,
very
roughly,
and
then,
of
course,
we're
closing
issues.
D
We
certainly
don't
love
closing
issues,
especially
those
that
have
merit,
but
we
think
it's
better
than
having
them
sit
in
kind
of
a
purgatory
where
just
with
411
issues,
we
cannot
get
to
all
of
them,
so
we're
hoping
to
close
the
ones
that
are
quite
old
or
that
we
just
don't
feel
like
there's
enough
demand
relative
to
the
work
needed
to
be
put
into
them,
but
feel
free
to
talk
to
me,
especially
if
you
are
willing
to
do
the
work
yourself
and
just
if
you're,
if
you
like
numbers,
we
started
a
week
ago
with
411
issues,
we
triage
134
over
about
four
or
five
hours
of
work
and
of
those
134
31
were
staying
as
current
42
are
I
spock
and
61
were
closed.
D
We
have
about
twice
that
to
go
277
and
we're
hoping
to
finish
by
the
end
of
the
week
of
the
triage.
Then
we'll
go
back
and
review
the
current
and
ice
box
more
closely,
so
you'll
keep
hearing
more
updates,
but,
as
always,
please
ask
questions
privately
or
here
if
you
want
to
know
how
we're
making
our
decisions.
So
that's
my
update
great
thanks.
Eleanor.
B
I'll
throw
out
that
we
also
for
our
own
sanity.
We
used
like
a
reviewed
in
q2
2021
label.
So
if
you
see
that
it
has
that
label
and
it's
been
left
open,
then
awesome
it's
something
we
we
looked
at.
It
doesn't
have
that
label.
We
haven't
gotten
to
it.
Yet.
A
Okay,
now,
let's
move
on
to
the
discussion
topics,
so
we
have
an
exciting
announcement,
which
is
that
scott
sego
has
joined
the
core
maintainer
team,
so
welcome
to
the
maintainer
team.
Scott
css
went
through
just
under
two
weeks
ago,
so
it
we
weren't,
didn't
have
the
community
last
week
so
didn't
announce.
A
It
then
yeah
welcome
scott
and,
if
you're
interested
in
what's
involved
in
becoming
a
maintainer
for
the
any
of
the
blair
projects,
we
do
have
a
governance
document
in
the
repository
which
you
can
take
a
look
at
which
gives
details
about
the
the
process
and
the
different
rules.
A
Okay,
next
up,
we
have
frankie
and
pradeep
to
talk
about
a
blog
post
for
the
website.
E
Yep
yep
first,
I
want
to
say,
welcome
scott
well,
I
mean
you've
been
with
valero
as
far
as
long
as
I
know,
and
really
glad
you
joined
really
sad
to
see
nolan
leaving,
but
it
sounds
like
you're
leaving
to
some
cool.
You
know
top
secret
project.
That
sounds
awesome
so
best
of
luck
there
I
for
the
short
amount
of
time
I've
been
here
for
what's
like
half
a
year,
nolan's
just
been
such
great
help
throughout
that
time.
So
I
definitely
wish
you
best
of
luck.
E
As
for
the
discussion
topic
yep,
the
blog,
I
I
will
like
to
introduce
pradeep
he's.
Actually
the
one
who's
been
working
on
it,
it's
a
it's!
It's
a
pr
status
right
now
kind
of
I
think
he'll
be
the
best
person
to
talk
about
it.
So
pretty
take
it
away.
Yeah.
F
F
A
Yeah,
so
this
is
so
the
auto
revere
action
that
we
have
at
the
moment.
There
is
an
issue
with
it
which
carlesia
has
already
looked
into,
and
there
is
another
pull
request
open
to
fix
that
so
I'll
I'll
go
through
and
and
design
some
reviews
to
look
at
that,
so
that
the
someone
from
the
team
can
can
take
a
look.
But
thank
you
very
much
pradeep
for
for
for
adding
this
thanks.
A
So
it's
really
helpful
to
get
more
input,
especially
for
someone
if,
if
you're
new
to
the
project
as
well
you'll,
always
I've
always
find
a
newcomers
to
the
project,
we'll
we'll
find
areas
that
maybe
aren't
clear
in
our
documentation.
So
I
think
yeah,
we'll
review
this
and
yeah,
hopefully
it'll,
be
very
useful
to
other
newcomers
to
the
project.
A
Okay,
okay,
so
another
discussion,
topic's
just
been
added
by
ali.
C
A
Yeah,
I
I'm
sorry
I'm
terrible
at
like
checking
this
admit,
because
soon,
whenever
I
do
screen
share
is
like
pretty
laggy
and
slow.
So
I'm
trying
to
like
scroll
through
and
and
see
where
everyone
is
so
well.
Should
we
move
on
and
do
the
contributing
shout
outs,
then
we
can
come
back
to
it
once
those
issues
are
resolved.
A
Okay,
okay,
so
we
have.
I
think
this
is
going
to
be
a.
A
A
contribution
to
the
helm
charts,
so
this
is
from
frederick,
who
has
added
a
pr
to
customize
the
upgrade
crds
job
in
the
helm,
charts
so
yeah.
Thank
you
very
much
for
that
change.
A
This
is
a
new
job
that
was
added
to
the
helm
chart
recently,
which
means
that
when
you
upgrade
valero,
you
can
upgrade
this
your
geese
along
with
that
to
supply
some
further
customizations
there.
Thank
you.
A
A
Sorry
can
someone
else
check
to
see
if
there's
any
other
message
regarding
whether
you'll
be
able
to.
A
A
Yeah,
this
is
another
thing
with
that.
Unfortunately,
I
can't
open
the
chat,
so
I
I'm
really
sorry,
I'm
probably
the
not
the
best
choice
to
leave
this
name,
but
we'll
wait
for
another
minute.
Anyone
else
have
any
other
discussion
topics
or
anything
else
they
want
to
raise.
In
the
meantime,.
G
H
I'm
all
I
am
working
with
scott's
team
at
reddit,
using
valero
for
migration
purposes,
and
so
we
in
our
configuration
setup,
we
used
valero
with
a
custom
s3
back
end,
and
we
hit
an
issue
where
that
s3
back-end
did
not
respond
to
the
list.
Objects.
B2
call
the
way
it
was
supposed
to
so.
Just
to
give
a
background.
H
The
backup
sync
controller
uses
list
objects.
We
do
pages,
sd,
aws
sdk
function
to
make
a
list
object,
v2
called
to
the
s3
server.
The
difference
between
this
list
objects,
v2
and
list
object.
V1
is
subtle,
and
because
of
this
subtle
risk
difference,
the
server
did
not
respond
with
a
valid
v2
response.
Instead,
it
returned
with
a
v1
response
because
of
the
v1
response
missing
a
particular
field
in
the
response
called
marker,
which
actually
indicates
the
next
page
in
the
in
the
pagination
request
the
the
valero
code
base.
H
Well,
the
sdk
prematurely
decided
that
this
is
end
of
pages
and
returned
only
a
small
subset
of
backups
that
were
actually
present
in
the
s3
market.
So
out
of
788
backups,
we
were
seeing
only
555
or
something
listed
in
valero,
and
we
were
seeing
this
mismatch
between
the
s3,
cmd,
cli
and
balero
back
account.
H
So
I
have
raised
this
issue
on
the
aws
sdk
as
well
that
it
would
be
great
if
the
list
objects.
V2
can
return
an
error
type
that
says
that
this
is
not
a
valid
video
response,
but
in
the
intrine
where
this
gets
triaged
in
upstream
sdk
code
base,
there
could
be
a
way
where
v,
where
valero
implements
this
in
its
own
logic,
like
in
its
own
branch
and
then
once
it
is
of
implemented
upstream,
we
can
morph
it
to
accept
that
change
through
the
awa
sdk
api.
H
So
I
was
just
wondering
if,
if
you
guys
have
thoughts
on
handling
this
issue,
is
this
something
users
of
valero
hate?
Would
you
guys
welcome
this
change
on
things
like
that.
C
So
we
could
certainly
consider
the
pr
can
you
tell
us
which
object
store
is
showing
the
problem.
H
Yes,
so
we
are
still
confirming
the
object
store.
I
think
it
was
ceph
or
another
custom
implementation.
I
keep
forgetting
name,
but
it
was
not
confirmed
from
the
client
side
yet
so
we
don't
have
100
authority
on,
say
answering
that
question
yeah.
C
Right
yeah,
so
I
would
encourage
feedback
to
the
object,
store
people
as
well,
like
hey
you're,
not
implementing
the
v2
api
properly
so
yeah.
So
I
look
took
a
quick
look
at
the
pr
that
you
referenced
there
and
in
the
current
implementation
this
will
work.
So
it
looks
like
you've
got
a
global,
that's
saying
we
should
go.
We
should
move
to
the
v1
api
and
in
the
current
implementation
we
restart
the
plug-in
on
a
regular
basis
and
we
don't
really
run
multiple
things
in
parallel.
C
C
I
don't
know
we
could
either
make
it
a
config
option
for
that
particular
object,
store,
slash,
backup,
storage,
location
or
you
know
eventually
we'll
have
to
think
about
something
that
tags
it
to
that
particular
connection
and
not
just
kind
of
a
global
right
now
it'll
work,
but
eventually
that's
going
to
work.
H
C
H
Right
that
return
call
is
for
the
the
the
list
objects.
We
do
pagination
to
return
all
right,
yeah.
C
Okay
yeah,
then
that
should
probably
be
okay,
long
message.
H
Yeah
sure
we
can
add
a
long
message
message
there
definitely
and
yeah.
So
the
first
time
v2
call
goes
to
lc
figure
out.
This
is
not
a
valid
v2
response,
we'll
try
again
with
v1,
so
this
will
certainly
not
break
anything
in
the
current
code
base
like
everything
that's
working
with
v2
as
it
is,
will
work
so
we'll
update
that
and
paste
it
against.
Upstream
thanks.
H
C
H
I
did
recall
the
name
was
swift
object
store.
That
was
so
it's
either
self
based
or
swift.
I
think
we
are
in
conversation
with
this
week,
guys
already,
but
it
has
not
been
confirmed
from
the
client,
so
it
will
let
you
know
as
soon
as
possible.
A
Okay,
any
other
discussion
topics
or
anything
else,
folks
want
to
race.
B
This
is
a
couple
weeks
old
at
this
point,
I'm
going
to
jump
in
here
because
I
just
remembered
it
today:
mineo
re-licensed
under
the
agpl,
and
that
happened
late
may
so
there
may
be
a
switch
in
the
example
s3
repository
we
use
vmware
just
pulling
the
curtain
back
a
little
bit.
Vmware
doesn't
really
like
agpl
licensing.
So
as
a
vmware
product
project
we
may
be
having
to
switch
which
one
we
use
but
we'll.
I
think,
we'll
talk
more
about
that
later.
B
And
I'm
not
a
lawyer,
so
I
don't
know
what
all
the
linking
and
all
that
has
and
what
those
implications
are
within
like
kubernetes
manifests
not
it's
not
even
in
the
containers,
but
we
we
use
mineo
in
our
examples
and
for
folks
that
are
trying
to
be
on-prem.
A
A
Okay,
if
there's
nothing
else,
I
think
then
we
can
end
the
meeting
earlier
today.
I'm
just
going
to
stop
share.
A
Okay,
thanks
very
much
everyone
thanks,
everyone
yeah
thanks
for
joining
and
we'll
see
you
next
week,
see
you
next
week.
Bye,
bye,.