►
From YouTube: 2020-07-20 Multi Large Working Group
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
All
right,
it's
5
30
we're
going
to
get
started.
I
demonstrated
the
prior
meeting
invite
which
you
obviously
got
the
new
one,
because
you're
here
so
yay
I
did
calendar
right
steve.
Let
me
know
that
he's
the
new
executive
stakeholder,
so
I've
updated
the
workgroup
page
to
reflect
that
change
and
then
updates
for
this
week
in
terms
of
deliverables.
Let's
see
my
glasses
are
getting
a
little.
A
There
was
a
sync
meeting
last
week
for
removing
nfs
from
I
guess
marin.
It
didn't
happen.
C
It
it
happened
just
a
bit
ago:
okay,
we
we
think
on,
we
think
on
what
actions
are
going
to
be
taken.
So
I
was
not
aware
that
there
is
an
additional
epic
that
kind
of
lists
all
the
dependencies
and
it
kind
of
organized
this
work.
So
basically,
we
agreed
to
have
scalability
take
3905
epic,
which
is
removing
the
immediate
blocker
and
then,
in
parallel,
the
release.
C
Orchestration
team
is
going
to
tackle
the
preparation
for
the
migration
investigation
of
all
of
the
dependencies
there
and
we'll
we'll
think
once
we
know
a
bit
more
on
the
progress.
What
timelines
we
are
talking
about.
A
A
A
All
right
I'll
focus
on
those
and
then
for
the
actually,
I
miss
label
this.
This
is
the
the
life
crisis.
A
I
spoke
with
gregors
today
to
understand
that,
and
he's
also
he's
a
dri
for
that
work,
so
he
gave
me
an
overview
and
the
same
thing.
I
will
focus
on
the
stuff
that
is
intended
to
remove
nfs,
because
that
is
the
real,
meaningful
stuff
for
us.
A
What
is
the
life
traces
feature?
So
that
is
a
question
that
I
asked
records.
Essentially,
is
all
this
data
gets
collected
when
pipelines
are
running
that
today
is
being
written
to
nfs
and
also
to
reddits,
where
it
is
stored
in
chunks
and
then
put
together
and
then
put
into
files.
A
So
they
need
to
do
the
work
to
alleviate
some
of
the
pressure
on
reddit's
and
there
is
a
suspicion
that
we
are
actually
missing
some
traces,
meaning,
there's
stuff
that
we
may
write
to
redis,
but
not
collect
properly
later,
to
write
to
a
file
so
he's
investigating
that.
But
really
the
focus
of
the
work
is
to,
instead
of
writing
to
nfs,
to
put
that
in
object,
storage
and
therefore
removing
effects.
D
C
So
so,
basically
I
don't
know:
what's
the
history
behind
this
being
named,
live
traces,
but
job
log
output
has
been
renamed
at
certain
point
to
live
traces
to
remove
the
confusion
with
gitlab
logs.
I
recall
so
that
is
the
reason
why
it
was
named,
live
traces
because,
because.
D
D
D
No,
no,
I
know
what
the
feature
does
like.
We
used
to
just
dump
that
all
to
storage,
and
now
we
have
redis
as
an
intermediate,
so
we
don't
have
to
have
a
right
load.
No
and
this
feature's
been
around
for
years.
This
is
why
I
call
it
a
trace.
A
trace.
The
whole
meaning
is
that
it
passes
multiple
services,
and
this
doesn't.
D
Sure
yeah,
but
it's
not
like
a
trace
in
kind
of
the
jaeger
cloud
native
sense
of
it
is
like
hey.
You
have
a
web
request
and
you
want
the
debugging
output,
but
this
we're
talking
about
the
same.
Of
course
it's.
It
has
multiple.
Every
request
in
gitlab
hits
like
the
database,
well,
the
redis
layer
and
real
stack,
and
maybe
a
database
and
stuff
like
that.
It's
not
about
that!
It's
about
like
where
is
it
coming
from?
It's
all,
coming
from
the
same
ci
job,
that's
emitting
stuff.
A
Yeah,
I
think
it's
a
tracing
aspect.
That
is
that's
the
confusion
because
it
just
like
you
said
it
made
me
think
of
jaeger,
and
I
was
like
I
don't
understand
what
this
is
and
then,
when
gregors
told
me,
I'm
like,
oh
okay,
that
makes
no
sense,
but
all
right,
I'll
I'll
figure
this
one
out
all
right
on
to
the
next
point.
I
will
create
epics
and
issues
for
all
the
deliverables
that
do
not
have
them
some
of
them.
A
These
may
just
be
placeholders,
while
I
find
where
they're
gonna
land
and
what
they
actually
mean,
I
think
as
deliverables
they're
really
clear,
but
some
of
this
is
not
slated
as
issues
or
epic,
so
I
will
take
on
fleshing
that
out
this
week,.
B
A
Right,
the
one
that
was
added
last
week,
I
was
out,
but
I
can't
remember
who
the
ceo,
whoever
ceo
shadow,
was
nice
and
took
that
and
put
it
in
the
page.
So
it's
just
some
of
them
already
have
issues
and
an
epics
associated
with
them.
I
just
want
to
make
sure
that
all
that
work
is
being
tracked
somewhere,
so
I'll
take
care
of,
creating
all
that
and
then
figuring
out
where
those
things
need
to
land
across
the
organization.
A
All
right,
marin.
C
Yeah,
just
an
fyi
item
that
we
updated
a
bit
to
gitlab
common
kubernetes
handbook
page
just
to
give
a
high
level
overview
of
what
the
current
state
is.
What
the
current
architecture
is.
So
this
is
not
going
into
details
too
deeply,
but
it
should
allow
anyone
who
wants
to
follow
what
kind
of
moving
pieces
we
have.
C
C
That
all
right,
just.
A
An
announcement
that
I'm
up
next
monday
as
well
with
my
daughter,
so
I
will
make
sure
that
updates
for
next
week
already
by
friday,
so
they're
available
before
the
meeting
and
then
ask
someone
hint
marin
unless
he's
out
to
run
the
meeting
next
week.
And
then
I
thought
about
moving
the
meeting.
But
just
aligning
everybody's
schedule
is
it's
quite
painful
and
someone
else
is
going
to
miss
the
meeting.
So
it
just
seems
easier
to
to
do,
go
async
and
then
have
someone
else
represent.
A
B
So
I
I'm
kind
of
joining
in
here
and
thanks
for
for
mentioning
that
jerry,
so
I'm
really
interested
in
being
engaged
in
this
going
forward.
I
was
just.
I
was
curious
because
you're
refactoring
kind
of
the
discussion
here
getting
the
new
invites
out
landed
on
the
new
work
group
page.
I
was
just
going
to
kind
of
ask
the
question:
is
the?
B
A
B
Are
you
asking
me
specifically
yeah?
Oh
okay,
I
mean
I'll
I'll
look
through
a
little
bit.
All
right,
I
mean
initially.
Some
of
my
thoughts
went
to
kind
of
maybe
the
step
after
this,
and
so
I
need
to
kind
of
pull
myself
back
in
and
say
you
know,
let's,
let's
iterate
on
things
you
know
once
we're
once
we're
able
to
operate
multiple
large
sites.
You
know
the
next
things
are
going
to
be
kind
of
initially
going
to
be
right
away.
B
Questions
from
customers
about
you
know
how
they
move
from
one
site
to
another
and
all
those
sorts
of
things,
and
so
there's
a
whole
sequence
of
other
kind
of
control
plane
issues
there,
but
but
I
think
it's
good
to
have
this
scoped
into
getting
to
that
point
and
then
and
then
maybe
there's
another
set
of
work.
That
is,
you
know,
distinct
from
that
afterwards,
but
but
I
I
still
want
to
kind
of
jump
into
or
get
into
more
of
the
the
background
on
this
and
everything
to
understand
more.
A
Yeah,
I
would
say
probably
what
happens
after
is
probably
out
of
scope
for
the
working
group,
because
generally
the
idea
as
a
working
group
is,
is
put
together.
So
we
we
can
quickly
stand
this
new
thing
that
the
working
group
is
supposed
to
be,
and
then
there
is
this
sort
of
gets
migrated
into
the
organization,
so
it
just
becomes
something
else
that
we
as
an
orc
do.
A
So
I
would
imagine
that
it
would
probably
not
be
a
working
group
to
figure
out
migrations
and
all
that,
but
that
would
be
either
something
that
infra
figures
out
or
you
know
we
do
some
development
on
the
on
git
lab
itself
to
be
able
to
handle
that
much
like
we
move
re-books
today
through
the
app
and
all
that
yeah,
but
again
we'll
revisit.
This
is
going
to
be
a
long-lived
working
group
anyway.
So
I
expect
we'll
find
some
new
and
interesting
things,
and
this
is
kind
of
like
I
guess
it
was
two
weeks
ago
said.
B
Cool,
I
don't
see
anyone
else
raising
their
hand,
so
it
sounds
like
sounds
like
scope
is
well
defined.
Cool
thanks.