►
From YouTube: Velero Community Meeting - July 19, 2023
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
Today
is
July
19th,
and
this
is
will
our
committee
meeting
and
first
and
last
look
look
through
some
overall
status,
for
we
will
create
one
partly
for
1.11,
that
is
room
1.1.1
and
we
have
closed
all
the
targeting
issues
and
the
attribute
will
be
around
there
tomorrow
and
we
we
can.
We
can
track
the
full
easy
list
here.
So
I
think
later
can
just
show
us
how
what
enhancement
had
the
issues
had
been
included
in
this
patch
release
and
for
with
1.12.
A
As
the
discussion
we
have
adjusted
the
FCD
days
to
July,
July
26,
so
I
think
the
members
are
trying
to
clothing
issue
that
he's
targeting
for
with
112
and
so
so
that
to
so
as
to
achieve
FC
and
for
the
little
more
feature
it
has
been
under
magnetized
and
nightly
automated
test
for
about
two
weeks
and
till
now
the
oral
titles
is
is
stable,
so
no
blocking
issues.
A
Is
found
for
for
FC
and
forward
1.13,
we
are
trying
to
trying
to
collect
the
requirements.
So
if
anyone
has
have
a
requirements
that
want
to
address
in
with
one
pointers,
are
13
but
just
open
the
issues
and
add
the
one
Constantine
candidate
tax,
except
for
the
overall
status
and
for
some
individual
updates.
A
Myself
is
working
on
the
more
functionality
tasks
and
also
fix
some
boxes
around
some
Corner
cases
and
I
also
continue
to
investigate
the
data,
the
requirements
that
to
have
the
data,
more
data
and
the
local
samples
coexist
and
and
right
now
we
have,
you,
know
several
projects
and
if
without
discuss
this
is
later
and
if
everything
is
is
ready,
we
will
create
a
another
design.
Talk.
B
A
Okay,
thanks
and
Daniel,
please.
C
I'm
fixing
the
usual
targeting
112
to
catch
up
with
the
progress
first.
Is
the
I'll
collect
the
summary
about
the
skipped,
the
PVS
that
skipped
snapshot
for
various
reasons
that
one
it's
probably
done,
and
I
I
submitted
the
pr
in
the
currently
in
the
progress
of
review
and
this
weekend
we're
also
working
on
the
a
removal
of
the
backup
after
data
mobile
data
movement
yeah.
That's
all.
D
First
I'm
doing
the
data
movers
bug
fix.
Second,
we
currently
have
the
ending
test,
but
we
lack
of
the
profound
test
and
now
I
am
doing
the
work
of
this
new
feature
and
the
distilling
progress.
Now,
that's
all.
A
Okay,
so
for
this
performance
automating
test,
it
means
about
a
view.
The
general
General
performance
has
a
framework.
Besides
it's
this
thing,
automation
nightly
test,
and
that
will
be
for
the
general
purpose
to
test
the
various
you
know,
operations
or
activities
that
involve
much
data
processing,
like
the
part
1,
backup,
restore
or
in
filter,
also
includes
the
data
movement.
A
Where
is
the
data
moment?
So
if
anyone
has
any
suggestions
or
years
experiences,
please
just
advice.
You
know,
through
the
slack
Channel
or
anyway
thanks
and
at
the
damn
phone.
Please.
E
Okay,
the
first
item
is
amber
I'm
prepared
prepared
on
B1
dot,
11,
Pipeline
and
I
run.
We
went,
we
went
on
1190.
One
thing
to
highlight
is
in
the
in
the
paper
in
this
pipeline.
We
have
covered
kubernetes,
we
1.27
version,
and
the
second
item
is
working
on
v1.12
test
plan.
That's
all
from
my
side.
A
Okay,
thanks
that's
for
the
stated
update
for
the
describing
topics
and
this
one
can
form
from
me.
It's
about
the
the
investigating
item.
I'm
working
on
that
is
a
little
more
local
seminar
coexist
right
now,
after
some
investigation
reaching
that
there
may
be
two
approaches.
A
Four
four:
four
one
of
the
approach:
we
want
to
build
a
separate
Logics.
You
know
separate
Logics
that
is
different
from
the
current
CSS
and
backup
and
result,
and-
and
we
believe
that
it
will
make
the
least
impact
to
the
existing
one
Central
backup
result,
but
that
will
inevitably
introduce
some.
You
know
some
some
redundancies
in
the
code,
since
we
have
two
different
set
of
Logics.
A
That
is
doing
that
are
doing
the
same
thing,
that
is
to
backup
or
restore
the
information
inside
the
volume
sub
shot
and
the
volume.
Some
short
content
of
that.
That
is
a
four
one
approach
for
the
other
approach.
We
want
to
build
this
implementation
for
this
requirement,
based
on
the
existing
volume,
control
of
the
dark,
Hopper
and
end
result,
but
we
have
read
that
we
will
need
some.
You
know
a
refactor
to
the
existing
or
coaching
to
the
existing
or
wanting
social
backup
and
CSS
and
backup
result.
A
So
we
don't
want
to
you
know,
bring
any.
You
know
the
blocking
issues
to
any
of
the
you
know
existing
functionality,
including
the
we
know
that
oidp
data
more,
is
using
this
volume
control
a
CSI,
some
backup
results,
so
especially
in
the
for,
depending
on
the
one
Saturn
and
one
Central
content
in
the
backup
double.
So
we
want
to
know
some
of
the
principle
or
or
or
practice
such
that
should
be
cave
in
order
not
to
bring
kind
of
the
existing
functionalities.
A
So
do
you
have
any
otherwise
so
Brown
Scott
for
this.
G
I
was
gonna
say
first
thing
is
that
the
the
volume
snapshot
that's
in
the
backup,
terrible,
that's
actually
right
now
something
that
we
are
relying
on,
because
when
we
do
restore,
we
use
the
volume
Snapshot
from
the
CSI
plugin.
You
know
the
CSI
plug-in
created,
and
then
we
update
the
volume
snapshot
content.
Rather
this
in
the
sap
handle
reference,
and
it
shows
them
to
point
to
the
new
volume
snapshot
content
created
by
the
data
mover.
G
So
two
of
them
I
think
that
means
that
the
volume
snapshot
content
in
the
backup
turbo.
We
don't
actually
need
it
all
right
or
am
I.
G
So
the
volume
content
in
the
terrible
if
that
disappeared,
wouldn't
affect
us.
If
the
volume
snapshot
the
one
created
by
the
CSI
a
plug-in,
we
would
need
that
with
the
current
code
base,
because
we
use
that
with
the
CSI
restore
and
then
we
update
it
in
one
of
our
data
mover
VSM
plugin
to
point
to
the
snap
handle
with
it.
In
the
new
newly
the
data
mover,
volume,
snapshot,
content
and
also
in
the
non-data
move,
a
regular
CSI
case.
I.
G
Think
you
still
need
that,
because,
when
you're,
restoring
that
comes
from
the
backup
and
when
you're,
not
using
data
mover
you'll
need
that
yeah
I
mean
I
think
from
from
Valero's
point
of
view.
I
guess
you
could
also
look
at
it.
Is
that
with
the
current
ODP
data
mover,
that's
all
outside
of
Valero,
so
that
that
really
would
be
considered
by
the
Valero
code
is
a
non-data
mover
case.
So
if.
F
G
A
Yeah,
so
the
volume
snapshot
that
we
need
is
it's
a
it's
already
known
that
from
the
workout,
the
namespace
right.
So,
okay
and
another
more
concrete
question
is,
like
you
know,
in
1.12,
we
have
to
add
some.
You
know
operations
or
waiting
for
the
volume
some
shot.
A
That
is
what
I'm
starting
to
be
ready
to
use
into
the
async
corporation,
so
that
is
one
as
incorporation
and,
as
the
other
part,
I
I,
think
the
data
mover
or
the
IDP
data
more
is
also
running
as
a
as
incorporation.
So
how
we
make
this
to
us
Inc
operation
together,
work
together,
because
I
think
the
later
one
will
relay
on
the
first
one
right,
because
the
later
one
will
also
need
to
wait
the
volume
some
problems
to
get
ready
to
use
before
it.
A
You
know,
move
some
data,
so
I
want
to
know
this.
Maybe
you
know
the
the
implemented
for
this.
Web
requirements
has
to
solve
solves
a
similar
problem.
G
Right,
yeah
and
that's
one
that
in
terms
of
the
using
the
updated
1.12,
CSI
plugin,
where
again
like
you
said
it's
now
asynchronous,
that's
not
something
that
we
have
yet
worked.
You
know
integrated
that
in
with
the
ODP
data
mover
so
again,
I
I,
don't
think.
I
have
a
clear
answer
right
now
as
to
how
that
fits
together.
We're
still
kind
of
investigating
kind
of
what
our
plans
are
around
that
you've
had
any
thoughts
about
or
not.
H
G
Well,
the
snapshot
to
be
ready
is
the
part.
That's
async
right
now
in
in
1.12,
for
this
plugin,
but
I
I
mean
so
I.
Guess
that
that's
one
difference
so
with
1.11
and
with
oedp,
when,
when
we
run
the
data
mover
related
plugins,
that
part
was
already
done
synchronously,
so
you
know
we
knew
it
was
ready.
G
I,
don't
know,
that's
something
that
we
would.
We
would
need
to.
You
know,
have
more
waiting
in
some
of
those
like
operations
where
that
would
fit,
and
but
but
the
the
framework
itself
for
Valero
and
asynchronous
plugins.
You
know
there
isn't
a
notion
of
multi-layers
and
levels
of
of
asynchronous.
You
know
it's.
Basically,
all
the
plugins
run
the
first
time
around
returning
all
those
operation
IDs
and
then,
when
we're
going
waiting
for
plug-in
operations,
if
you
have
two
different
kinds
of
plugins
that
are
both
asynchronous,
those
are
all
waiting.
G
Know
we
don't
have
if
it's
not
a
notion
of
oh
we're
gonna,
do
we're
going
to
wait,
asynchronously
for
all
of
the
CSI
results
and
once
those
come
in
then
we
have
another
stage
of
waiting
for
a
different
kind
of
plug-in.
You
know
because
the
API
does
not
have
a
spot
for
that.
A
A
Some
backup
results
need
to
wait,
the
the
volume
at
Central
to
get
ready
to
use
and
then
to
have
Valero
to
backup
the
latest
volume,
some
problems
and
throughout
the
content,
objects
into
the
turbo
in
the
finalizing
state.
That
is
as
a
I,
I
item
to
be
updated.
A
That's
it
for
one
thing
and
the
other
thing
is
the
data
more
also
need
so
so,
ideally,
the
the
data
model
need
to
wait,
and
you
need
to
wait
for
this
all
these
operations
to
to
be
finished
before
it
started
itself.
So
it
seems
it
just
as
you
mentioned
Scott
well,
we
we
have
separate
as
incorporation,
then
that
they
don't
know
each
other,
and
we
learn
into
wait
for
for
all
that
I
think
Corporation
to
finish.
A
But
right
now
we
are
facing
a
situation
that
we
have
relationship
with
of
two
I
think
corporations.
That
is
that
one
need
to
wait
the
other.
To
finish,
that
is
some
awkward
we
have
we
are
facing.
You
know
if
we
consider
all
these
things,
maybe
maybe
later
offline,
we
can
just
discard
together
this.
A
G
Yeah
I
mean
another
possibility
would
be
to
you
know
and
again:
I
I,
don't
know
how
long,
if
you,
if
you
want
to
compare
how
long
it
takes
for
a
volume
snapshot
to
be
ready
versus
how
long
the
daily
movement
takes,
is
that
it
may
be
that
when
we
still
want
the
async
part,
for
we
still
need
the
async
right
for
the
CSI
plugin,
because
we're
now
using
the
the
second
run
through
execute
to
clean
up
the
volume
snapshot.
G
So
but
I
don't
know
if
it
would
affect
performance
much
to
move
the
weight
for
the
the
waiting
for
the
volume
of
Snapchat
to
be
ready.
The
snap
handle
will
be
ready.
You
know
back
into
the
synchronous
portion
of
that
as
kind
of
a
you
know,
because
if
you
did
that,
then
the
data
movement
wouldn't
have
to
wait
because
it
would
already
be
there
it'll
work.
G
Another
thing
that
that
might
work
is
this:
having
the
the
data
movement
code
itself,
basically
one
of
the
things
that
you
had
before
you
start
the
upload
or
the
download.
You
know.
Definitely
you
you
check
to
see
if
that
snap
handle
is,
is
available
there
I,
don't
know.
A
Yeah,
actually,
the
in
the
with
our
building
data
more.
It
has
already
checked
the
included
the
code
to
check
the
status
of
the
volume
Center
chart,
and
that
is,
it
will
never
start
the
at
that
moment
before
and
until
the
the
the
samples
got
to
are
ready
to
use.
But
but
the
other
thing
is
the
you
know
the
athlete
for
a
velocity,
a
building
anymore.
A
If
I'll
make
some
modification
to
the
volume,
some
Charter
One
Central
content
created
by
the
by
the
CSL
plugin,
that
is,
it
will
transfer
the
objects
to
the
to
the
Valerian
place
and
also
need
to
modify
the
volume
sample
to
you
know
some
kind
of
main
head
really
10
mods
so
as
to
you
know
right
to
keep
them
something
like
that.
So
once.
A
Doesn't
do
anything
once
it
maintenance
to
the
to
this
one
example:
one
example
content
and
we
learn
well
have
no
way
to
find
the
objects
and
then
persisted
either
in
the
primary
workflow
or
in
the
finalizing
stage.
G
I
mean
the
finalizing
as
long
as
we
continue
to
return
the
volume
snapshot
content.
You
know
and
items
to
update
like
like,
like
it's
doing
right
now,
then,
when
finalize
gets
called,
that's
those
items
are
in
the
list,
those
those
will
get
updated
with
their.
You
know,
final
state.
A
G
Because
because
the
finalizing
hasn't
happened
until
all
of
the
asynchronous
operations
are
completed,
so
you
know
hopefully
that
so
so
at
that
point
anything
that's
going
to
modify
these
things
has
already
been
done,
so
we
should
be
ready
to
to
make
the
final
changes
and
final
updates.
You
know
into
the
firewall
Yeah.
A
Yeah,
you
mentioned
the
test,
but
that
means
you
know
the
CSL
plugin
tells
you
know
the
Valero
that
you
need
to
backup
this
to
object,
vs,
one
Snapchat
a
and
a
long
time.
No
content
would
be
a
but
later
I
win.
The
that
tomorrow
will
finish.
It
I
tend
to
warm
some
products
e
and
the
volume
some
content
of
that
b.
A
That's
that
well
I,
I!
Think.
If
we
don't
do
anything,
the
winner
will
not
be
able
to
to
find
the
the.
G
G
Those
weren't
added
by
anything
as
I
mean
how's
that
being
done
right
now,
then,
because
I
mean
that's.
A
Yes,
actually
for
the
current
building
data
more
at
the
very
you
know
earlier
stage,
that
is
when
the
data
mode
is
under
the
preparing
phase
the
volume.
Sometimes
environmental
content
will
be
modified.
A
Okay,
I
think
that
is,
that
is
the
situation
we
are
facing.
A
Maybe
we
can
discuss
this
a
little
together
to
include
the
both
the
requirement
of
that
from
another
part
and
from
oadp
did
the
more
part,
and
and
finally,
if
we
want
to
do
some
refactor
to
the
existing
CSS
and
product
backup
result,
we
want
we've
always
thought
that
it
only
not
only
to
to
to
meet
the
current
requirement
but
to
bring
us
it
has
it
for
its
own
good,
and
that
may
be
better.
So
maybe
we
can
discuss
this
later
offline.
H
A
That
is,
for
this
topics.
Do
any
other
any
other
topics.
A
Okay,
I
think
we
can
finish
the
meeting
here
and
thanks
everyone
for
joining
and
have
a
good
day
and
good
evening.
See
you
next
time
bye.