►
Description
Jan 19, 2021
Status Updates
carlisia
Almost done with addressing reviews for Download Request (https://github.com/vmware-tanzu/velero/pull/3004)
bridget
Released v1.5.3
Helped out with some internal build processes
Working on POC for multiple credentials
Need to review outstanding PRs
nrb
Internal build updates for Velero v1.5.x series (build changes taking a while)
Reviewed timeout design w/ Phuong
My notes: https://hackmd.io/rGQuMa3XRDm7BW-CVVLAsg
dave
E2E tests running in AWS, Azure clouds
Working on next tests, CI/CD integration
Discussion Topics
carlisia
We are using GH Discussions for community support now (and other topics): https://github.com/vmware-tanzu/velero/discussions
bridget
Multiple credentials POC demo
Velero PR: https://github.com/vmware-tanzu/velero/pull/3299
AWS plugin PR: https://github.com/vmware-tanzu/velero-plugin-for-aws/pull/69
phuong: quick update on the plugin timeout design
Step 1. Add golang contexts into the plugin interfaces
Uses new WithContext variations to each fuction for backwards compatibility
Step 2. Determine timeouts & cancellation behavior
Plugin versioning: https://github.com/vmware-tanzu/velero/issues/3285
Helps with modifying plugin interfaces without requiring everyone upgrading in lock step
High level: looking for a pod-level timeout that covers ALL PVs connected.
Nolan’s notes: https://hackmd.io/rGQuMa3XRDm7BW-CVVLAsg
Recording of the meeting: https://Dell.zoom.us/rec/share/EtlVa0vDa_fM0pzxArc9Izbq1LJwNpc1v5bfWcIwjCGzC4KDkjBqkudCWAGZqqI.e01a98H7-RO0y2_q Passcode: xH.vY3D5
Nolan & Dave will be doing a presentation on Velero at the Data Protection Working Group on Wednesday 1/26, 9am Pacific time
#wg-data-protection on the kubernetes slack
A
B
Trying
to
put
my
notes
together,
I
am
almost
done
with
the
addressing
the
code
reviews
for
the
download
requests,
migration
to
controller
and
time
pr.
What
I'm
going
to
do
is
finish
addressing.
I
have
one
two,
three
four
prs:
I'm
going
to
finish
addressing
the
code
reviews
for
all
of
them.
Then
I'm
going
to
look
at.
What's
what
I,
if
there
is
anything
I
can
do
for
the
secrets
on
bridgespr
and
then
review
vrs,
we
have
a
lot
of
them,
which
is
great.
C
D
D
I
was
helped
out
with
some
of
the
internal
build
processes
here
that
we
have
for
our
internal
builds
at
vmware,
so
I
was
helping
out
with
some
of
that,
and
I've
also
been
working
on
a
poc
for
multiple
credentials.
I
got
a
draft
pr
up
for
that
which
I'm
happy
to
talk
about
in
a
little
bit
more
depth,
maybe
during
the
the
discussion
topics,
but
we're
making
making
some
progress
there
to
maintain
your
scene.
D
I
picked
one
of
them
and
kind
of
ran
with
it
to
see
how
it
would
go
and
so
I'll
get
some
feedback
and
from
folks
later
and
like
carly's
yeah.
I
also
owe
a
lot
of
reviews,
so
I
think
there
was
one
there
were
a
few
pr's.
I
said
that
I
was
gonna
review
last
week
and
I
didn't
get
around
to
it,
but
that
is
on
my
list
for
this
week.
That's
me.
D
A
Okay,
cool
for
my
update.
I'm
gonna
go
back
to
this,
so
I've
been
working
on
some
getting
valero
1.5
series
into
our
internal
build
system.
Since
we
switched
over
to
docker
build
x,
it's
been
a
little
touchy
on
our
internal
build
system,
so
I've
been
fixing
up
our
build
scripts
that
wrapped
the
valero
make
builds.
A
E
Hey
yeah
so
got
the
ed
tests
working
in
the
various
clouds,
so
we
had
it
so
we
could
run
it
in
kind
with
the
different
back-end
providers
and
I
got
it
running
with
the
install
and
everything
in
aws
and
azure
and
I'll
work
on
vsphere
a
bit
and
then
next
steps
are
more
tests.
So
this
is
the
very
basic
backup
test
and
also
getting
some
kind
of
a
cicd
integration.
So
we
can
get
everything
run
automatically.
E
A
A
E
A
A
There
we
go
yep
so
for
folks
who
are
not
aware,
this
is
a
proposal
for
adding
a
layer
in,
I
think,
actually,
not
I'm
thinking
about
it.
We
did
talk
about
this,
but
as
part
of
the
new
architecture,
we
want
to
pull
in
a
new
layer
that
lets
folks
swap
out
rustic
and
send
to
different
types
of
repositories
and
use
different
tools
for
the
file
system
movement.
A
This
is
going
to
be
on
a
two
point,
the
I
ideally
this
will
be
part
of
2.0,
but
it
may
come
in
a
release
somewhere
in
there,
but
it's
a
this
is
essentially
an
epic
and
kind
of
where
we're
going
so
more
of
that
architecture.
Stuff
will
be
coming
out,
but
I
think
this
piece
is
fairly
independent
and
some
of
that
may
be
coming
from
the
vsphere
plug-in,
which
dave
and
his
team
have
already
implemented.
A
sort
of
data
mover.
B
Just
wanted
to
let
everybody
know
we
are
using
github
discussions.
Now
we
are
using
it
for
different
topics.
You
can
see
there
on
the
left.
We
have
a
list
of
categories,
and
one
big
change
is
that
we
are
trying
to
shift
the
community
support
to
the
discussions
and
to
make
it
maybe
make
it
easier
for
other
people
to
also
jump
in
and
help
so
anything
when
people
come
and
ask
open
an
issue
and
ask
a
question:
if
we
have
to
ask
them
hey
what
is
this?
B
If
we
do
find
that
it's
a
bug
or
something
that
needs
to
be
fixed,
something
that
needs
to
fix
the
bug
like
or
an
enhancement,
then
we'll
open
an
issue
and
link
to
it,
but
any
all
the
back
and
forth
that
we've
been
doing
on
issues.
We
are
going
to
be
moving
to
discussions.
Now
we're
going
to
be
asking
people
to
start
a
discussion
when
they
ask
us
questions
instead
of
asking
them
to
open
an
issue.
D
B
Yeah
and
in
if
you
are,
if
you
have
the
right
answer,
if
either
I
don't
know
if
the
original
poster
can
mark
an
answer
as
the
right
answer,
I'm
not.
I
don't
know
that
yet,
but
we
can
definitely
mark
any
answer
as
the
right
answer
and
when
people
who
answer
the
right
with
the
right
answer
gets
that
check
mark
it
counts
as
a
contribution
for
as
far
as
the
github
profile
goes,
it's
a
little
incentive.
B
Yeah
exactly
and
in
actually
we
haven't
like
we
did
this
really
quickly.
The
community
shout
outs
category
I
I
was
the
one
who
suggested
the
category.
What
I
was
thinking
was
to
in
addition
to
to
having
the
shower
outs
here
we
can.
We
should
paste
that
list
of
contributors
in
that,
as
opposed
on
that
category,
just
it
stays
there
for
prosperity.
It's
easy
to
see,
and
we
can
also
add
contributions.
That
is
just
not
codes
like
if
any
someone
helped
out
on
the
pr.
A
D
Hello
again,
so
I
mentioned
that
I
I'd
be
happy
to
chat
about
the
poc
that
has
been
done
so
far,
but
multiple
credentials
work.
So
there's
an
existing
pr
with
the
design
dock
and
we
haven't
decided
yet
on
the
approach
that
is
going
to
be
taken.
So
there
were
two
kind
of
main
approaches
that
that
had
that
we
team
had
discussed
and
then
also
that
have
been
written
into
the
design
dock.
D
D
D
D
Oh
there's
a
lot
of
stuff
in
this
pr
knowledge.
I
know
that
you're
scrolling
through
it.
If
you
go
to
the
set
of
commits
the
change
that
I've
added,
is
the
the
latest
or
sorry
the
the
last
commit
in
that
list,
because
I
have
based
off
a
couple
of
branches,
because
carlos
had
already
done
the
the
work
to
change
the
cli
to
be
able
to
accept
a
credential
argument.
D
B
D
D
Yes,
that's
correct,
okay,
yeah,
so
so
I
mentioned
on
the
pr
that
it
doesn't
yet
take
into
account
the
volume
snapshot,
locations
or
drastic,
but
but
I've
got
it
working
such
that
you
can
create
a
bsl
with
the
credential
argument
and
that
was
added
to
the
cli
and
then
it'll.
Do
some
validation
on
that
credential
to
say:
does
it
exist
or
is
it
valid
and
then
it
will
write
it
to
a
file
and
then
pass
it
through?
D
Yeah,
I
think
there
might
be-
I
haven't-
looked
into
it
yet,
but
I'm
kind
of
hoping
that
rasik
might
have
some
different
command
line
options
that
you
could
pass
in
the
the
config
file
that
you
want
to
use.
Or
if
it's
just
the
environment
thing
yeah,
like
you
say
we
can
set
it
and
unset
it
before
invoking
the
the
rustic
command.
I
think
that'll
be
easier
to
do
than
it
would
be
for
the
plugins,
because
we
create
the
plugin
processes
using
the
go.
D
But
I
think
that
if
I
understood
correctly,
I
can't
remember
if
it
was
the
shisha
mentioned
it
or
you
know.
I
think
we
spoke
about
before
the
break.
Is
that
the
for
the
azure
plugin
it
doesn't
actually
have
a
it
doesn't
have
a
a
way
to
to
pass
in
a
file.
So
what
we
do
instead
is
write
all
those
it's
essentially
a
collection
of
environment
variables.
We
write
that
to
a
file
and
then
load
all
of
the
environment
variables
in
that
file
into
the
environment
before
creating
the
azure
client.
D
D
A
A
The
azure
setup
was
hey,
go
define
all
these
environment
variables,
and
so,
instead,
what
we
said
is
define
all
these
environment
variables
in
one
file
and
then
we
essentially
use
the
equivalent
of
batch
sourcing
to
get
them
into
the
environment.
There's
a
there's
a
go
library
that
can
pull
it
in,
but
it
sounds
like
what
dave
might
be
saying
here.
Is
you
don't
just
need
the
credentials
file?
You
need
the
name
that
it
would
get
put
into.
E
D
Yeah,
so
I
think,
like
the
way,
the
way
I
think
in
the
design
dock
that
we
intended
this
to
work,
is
that
we
will
leave
the
existing
environment
variables
there.
So
if
you
already
have
a
deployment
and
you're
relying
on
those
environment
variables
that
will
all
still
continue
to
work,
it's
only
if
you're,
creating
new
backup
storage
locations,
where
you
explicitly
specify
that
you
want
a
particular
secret
to
be
used.
D
Yes,
it
still
needs,
it
still
needs
more
discussion,
more
work,
but
it's
kind
of
it
was
more.
I
wanted
to
make
sure
that
what
I
had
in
my
head
would
make
sense
and
would
actually
work,
and
so
I
got
to
the
stage
where
I
got
a
bsl.
That
said
it
was
available,
so
it
correctly
validated
so
awesome.
There's
some
progress.
Oh.
F
A
F
D
Yes,
so
so
this,
so
this
is
essentially
the
work
that
is
going
to
enable
that
so
that
whenever
you
will
allow
you,
as
a
user
blower
to
have
multiple
backup
storage
locations
and
each
one
of
those
can
be
configured
to
use
a
separate
set
of
credentials.
So
you
could
have
one
bsl,
which
talks
one
aws,
a
kind
another
one
that
talks
a
different
one.
Okay,.
F
A
So
I
think
the
the
kind
of
key
thing
here
is
that
the
we're
coupling
the
backup
store
and
the
convention
computer
kind
of
together
you
know
in
a
way
at
certain
levels
of
the
code,
so
that,
like
the
bsl,
has
a
pointer
to
a
secret
kubernetes
secret
so
that
you
can
do
different
secrets
per
bsl.
Instead
of
one
for
all
of
aws
or
one
for
all
of
azure,
one
for
all
of
gcp
or
open
ebs
or.
C
Yeah,
can
you
guys
hear
me
so
basically,
it's
similar
to
what
nolan
has
talked
about
at
the
beginning
of
our
meaning,
that
we
decide
to
split
the
issues,
the
problem
into
two
separate
major
topics
and
one
minor
topic,
so
the
the
primitive
one
we
want
to
enhance
the
plugin
interface
so
that
it
will
able
to
take
in
the
go
line,
context
object
and
we
will.
If
we
do
need
to
do
timer,
we
will
need
to
do
camera
on
that
contact
object.
C
So
that
brings
our
question
whether
we
should
enhance
the
interface.
How
do
we
enhance
the
interface
so
that
it
will
not
disrupt
the
current
provider
right?
So
we
propose
that
to
add
another
control,
each
of
the
function
in
the
interface
we
add
another
function,
let's
just
say:
if
it
is,
let's
just
say
execute,
then
we
will
enhance.
We
have
another
function
called
execute
with
context,
for
example,
and
so
that
if
the
provider
only
provide
the
function
execute
then
we're
still
able
to
run
it.
C
If
the
provider
decides
to
support
the
contacts,
then
we
will
execute
the
execute
with
contact
function
so
that
this
way
that
even
the
I
mean,
everyone
can
be
able
to
work
their
list
and
you
know
backwards
compatibility
with
the
old
version.
So
that
brings
up
to
the
second
topic,
which
is
the
versioning
right.
So
I
think
dave
and
bring
out
this
point
that
we
need
to
a
way
to
start
versioning.
The
the.
C
Plugin
interface,
so
that
we
can
check
the
version
to
make
sure
you
know
the
the
the
code
that
we
are
currently
running
would
be
compatible
with
specific
version
of
the
plugin
and
so
on
so
forth.
That
is
a
long
term
one
because
I
think
dave
has
pointed
out
that
as
of
right
now
we
don't
have
many
plastic
and
we
only
have
a
very
handful
of
plugins.
C
So
if
we
need
to
update
an
interface,
the
blog
interface,
we
can
force
everyone
to
upgrade
at
once,
but
that
is
not
going
to
be.
You
know
work
well
in
the
future.
In
the
long
term,
we
will
have
more
valero,
plug-in
add-in
and
so
on
so
forth,
so
he
proposed
that
we
should
start
talking
about
versioning,
creating
a
version
so
that
if
this
course
can
check
these
kind
of
versioning
to
make
sure
to
call
the
appropriate
function
accordingly.
C
C
So
those
are
the
first
set
of
topics
that
we
decided
on
last
friday,
and
the
second
topic
that
we
decide
on
is
that
my
original
desire
to
enhance
the
backup,
the
backup
plugin
with
the
the
amount
you
have
to
change,
so
that
everyone
who
wants
to
enhance
specific
workflow,
for
example.
In
my
case,
I
want
to
enhance
the
backup
logic.
D
C
Workflow,
for
example,
in
my
case,
my
ultimate
goal
is
not
just
for
the
timeout
of
this
specific
pvc,
but
my
ultimate
goal
is
that
I
want
to
have
a
timeout
for
everything
everything
inside
that
specific
part
when
I
actually
execute
the
the
the
crease
of
the
part
and
then
do
everything
to
back
up
inside
that
part
and
then
at
the
end
I
uncreate
that
one.
So
that
is
the
timer,
the
ultimate
hammer
that
I
want.
C
So
these
kind
of
high
level
timeline
objects
will
be
created
separately
by
each
of
the
interests
if
it
is
a
company
or
a
vendor
that
has
interest
in
that
topic.
So
basically
that
is
the
summary
of
what
we
discussed
on
last
friday.
I
have
a
re.
I
have
the
report
about
the
meeting
and
nolan
have
captured
it
in
the
haka
and
in
the
hack.
C
A
A
A
So
yeah
in
terms
of
getting
this
high-level
pod
timeout
we're
gonna,
get
the
go
lane
contact
context
into
the
plug-in
interfaces
and
to
get
moving
on
that
soon.
We're
going
to
use
new
with
context,
variations
for
each
function
and
then
once
we
have
the
context
kind
of
available
to
everything,
then
we're
going
to
take
step.
D
A
A
It's
not
on
the
board.
Okay,
I
need
to
fix
that
the
multiple
credentials
support
for
valero,
that's
kind
of
our
big
ticket
item
for
one
six,
and
we
obviously
need
to
get
back
to
this.
So
I'll
get
this
back
on
the
board.
We
also
have
the
end-to-end
testing,
which
is
moving
along.
Those
are
kind
of
our
huge
things.
A
D
A
I
think
we
need
to
pull
yeah.
I
think
we
need
to
revisit
our
prioritization
and
get
a
1
6
out
and
move
a
lot
of
stuff
to
one
seven.
So
I
need
to
go
back
over
this
board
and
see
what
we
can
bump.
But
my
main
concern
is
getting
this
multiple
credential
support
and,
at
this
point,
getting
multiple
credential
support
and
then
fixing
any
really
important
stuff
out
of
here
like
restoring.
D
A
Yeah
and
some
of
these
tech
debt
items
right
here,
I'm
guessing
we're
not
going
to
be
able
to
get
to
you
just
for
timeliness,
so
we
may
have
to
bump
them
a
bunch
of
these
aren't
me
but
yeah.
I
think
I
think
I
need
to
revisit
this
stuff,
but
I
don't
think
everything
in
this
to-do
column
will
get
just
out
of
timeliness
we
wanted
to.
We
wanted
160
to
be
out
in
december.
A
A
Oh,
thank
you
fong
for
adding
and
recording
all
right.
If
there's
no
more
discussion
topics
I
have
to
apologize.
This
is
on
me
the
as
was
mentioned
earlier.
There
is
a
big
build-up
of
prs,
and
so
I
do
have
planning
for
the
next
tkg
release
this
week,
but
I'm
going
to
prioritize
over
other
things,
pr
reviews
in
this
week,
so
other
codings
things
I
have
that
are
going
to
be
put
on
the
back
like
my
internal
build
stuff.
So
apologies
to
everyone
who
has
pr
is
waiting
on
us.