►
From YouTube: Velero Community Meeting - Jan 4, 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).
D
Hello,
everyone
sorry
I,
have
some
problem
with
my
hazard,
and
so
this
is
the
large
community
meeting
on
January
4th,
2023.
and
first
I'll
do
some
stated.
Update
myself
is
working
on
some
Works
around.
D
There
are
1.11
and
the
first
is
like
to
investigate
the
academic
issues
and
some
of
them
had
found
the
solution,
and
so
I
put
them
into
the
1.11
milestone
and
the
other
work
is
to
to
build
a
POC
for
the
weather
building
data
movement
for
CSI,
and
the
current
PLC
is
based
on
the
the
this
design
that
we
have
this
as
a
little
bit
in
the
previous
meeting,
and
we
want
to
prove
that
the
it
generally
work.
D
But
meanwhile,
without
still,
we
will
continue
to
discuss
the
details
of
the
design
so
for
for
about
this
result.
But
this
will
work
together
with
the
POC,
because
for
the
POC
we
want
only
one
to
prove
that
the
basic
points
I
didn't
work.
So
we
can
adjust
the
final
solution
anytime.
E
One
item
is
also
investigating
the
candidate
issue
from
1.11
that
is
assigned
to
me,
and
another
item
is
trying
to
enable
more
linkers
for
Valero
and
the
first
one
is
static
chat
and
by
far
after
it
is
enabled
there's
a
lot
of
issues
reported
are
reported
and
is
investing
in
is
is
investigating
on
that.
That's
all
from
my
part.
D
Okay,
thanks
and
Daniel,
please
yeah.
A
I'm
pretty
much
of
the
same
status
as
last
meeting,
because
there's
only
a
one
or
two
working
days
between
these
two
meetings,
I'm
also
charting
the
issue
targeting
for
1.11
and
debugging.
An
error
handle
issue
in
Valero's,
probably
in
framework
I,
just
noticed
that
that
the
error
handling
of
Valero
plugin
seems
to
be
heavily
depending
on
the
Legacy
PKG,
slash
arrows
Library.
A
B
Yeah,
so
it's
same
for
me:
not
a
lot,
not
a
whole
lot
of
updates,
because
I
was
out
last
week,
but
we
discussed
two
PRS
of
mine
that
we
were
considering
high
priority
to
get
merged
in.
We
got
one
of
those
merged
in
which
was
the
the
news,
backup
and
restore
phases,
and
then
there's
the
one
then
link
I
linked
to
here.
B
I
did
see
some
feedback.
I
did
respond
to
that
the
questions.
So
let's
just
continue
to
discuss
this
and
hopefully
get
that
merge
this
week.
D
Okay,
thanks
Scott
and
I
will
tag
the
comments
and
to
add
more
comments
or
add
some
feedback
on
that.
Okay,.
F
Yeah
I'm
also
do
some
investigation
for
the
11th
Canada
you
should
send
to
me,
and
the
second
item
is
I
will
continue
to
review
the
error.
Plugin
PR.
This
PR
is
moved
out
from
London
and
we
want
to
merge
It
Again
by
11.
G
D
D
D
Okay,
that's
it
for
the
second
update
and
for
the
discussion
topics.
I
added
one
I
do
about
this
design
and
we
have
discussed
a
little
bit
from
last
session
or
meeting
and
I'm.
Just
thinking
about.
Do
I
need
to
schedule
some
time
to
discuss
the
century
piece
by
piece,
because
you
know
we
have
discusses
locally
in
the
team
force.
D
You
know
one
or
two
rounds
and
we
found
that
there
are
still
some
details
need
to
cover,
and
so
I
want
to
ask
what
is
a
bad
way
to
normal.
It
forward.
B
C
B
Kind
of
cover
that
as
well,
we
might
be
able
to
do
it
in
the
meeting
two
weeks
from
today
at
the
same
time
period.
If
we
wanted
to
set
something
up
outside
of
the
meeting
time.
That
would
be
fine
as
well.
We
didn't
coordinate
that
with
Shiva
and
his
availability.
B
Working
but
he's
he's
not
in
Eastern
time,
I
think
he's
still
in
India
right
now,
so
he's
so
it's
like
three
in
the
morning
for
him
at
the
moment
or
four
in
the
morning.
So
he
can.
You
know,
he's
able
for
he's
available
for
the
U.S
Centric
meeting,
but
not
this
one,
but
that's
just
this
week
is
the
end
of
that
he'll
be
back
in
his
usual
eastern
time.
Us
next
week.
A
The
only
issue-
okay
and
also
a
quick
question,
because
currently
the
design
driven
by
jungkoi
is
based
on
the
part
volume
backup.
Essentially
it
means
we
want
to
restore
the
snapshot
and
somehow
move
the
data
from
the
restored
volume
to
the
object
store.
So
I
believe
when
you
are
a
level
leveraging
the
tool
called
both
Sync
It's,
essentially
doing
the
similar
thing
right.
Yeah.
B
Right
we're
using
those
things,
but
the
difference
is
that,
instead
of
using
the
the
Pod
volume,
backups.
B
Approach
we've
taken
is
is
basically
off
the
CSI
plug-in
so,
but
so
basically
this
we,
the
CSI
plug-in,
creates
the
volume
snapshots
and
volume
snapshot
contents.
And
then
we,
in
addition
to
that,
for
each
volume
snapshot
created,
we
create
a
CR,
that's
going
to
tell
valsync.
B
Know
copy
this
so
so.
B
It's
based
on
a
different
part
of
the
Valero
infrastructure,
but
but
it's
the
same
basic
idea
is
that
once
you
have
a
CSI
snapshot
in
the
cluster,
we
then
copy
this
using
ballsync
out
of
the
cluster
into
the
object,
storage,
yeah.
A
So
so
I'm
curious
about
the
performance,
so
it
should
be
on
par
with
the.
If
you
rely
on
rustic
for
both
sync,
this
will
be
on
par
with
you
know,
doing
the
files
frequent
based
backup
using
rasic
if
I.
B
Would
think
so
and
shubham
might
have
some
more
information
on
because
I.
B
That's
the
thing
one
thing
we're
talking
about
as
well
is
kind
of,
but
but
you're
right
as
long
as
we're
using
rustic
it'll
be
a
similar
performance.
Well,
Sync
has
some
other
back-end
support
other
than
The
Rustic,
which
we
have
not
tried
using
yet,
but
that's
another.
B
You
know
using
something
other
than
rustic
on
the
back.
End
obviously
would
affect
the
performance
as
well,
but
right
now
we're
currently
using
it
with
rustic.
A
Well,
I
think
we
we
should.
We
should
talk
to
subang
somehow
via
the
Valero
Dev
Channel,
and
see
what
time
he's
more
comfortable.
Maybe.
A
D
I
remember
seeing
how
to
set
up
the
channel
slack
channel
for
the
data
moment.
So
maybe
we
can
use
that
channel
to
arrange
the
time
and
for
and
to
discuss
any
details,
because
that
one
should
work
too
yeah.
F
D
So
you
can
put
the
maybe
the
slack
information
here
or.
D
Okay,
this
is
the
first
meeting
and
in
the
2023
and
people
have
just
come
back
from
the
holiday,
so
Happy
New
Year,
and
if
we
don't
have
more
things
to
discuss
a
significant
financial
of
here
right
so
see
you
next
time.