►
From YouTube: 2020-10-05 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
Hey
everyone.
Sorry,
I'm
like
all
right,
so
we
got
started
first
of
all,
thanks
jason
for
last
week's
conversation
that
was
very
educational.
I
look
forward
to
our
follow-up
this
week
and
then
marin.
B
I
think
we
have
both
gigojin
camille
here
who
can
speak
for
my
items?
I
just
added
him
on
the
agenda
so
jaggers.
Do
you
want
to
share.
C
Yeah
sure
so
we
managed
to
make
some
good
progress
with
cloud
native
job
logs.
We
started
rollout
production,
gitlab
or
github
project
rollout
has
been
successful,
and
although
we
identified
a
couple
of
things
that
we
would
like
to
improve,
everything
seems
to
be
on
track
to
finish
like
to
proceed
with
the
rollout
in
this
milestone.
B
Cool
thanks
thanks
for
sharing
jacob
camille.
Do
you
want
to
talk
about
pages.
D
Yeah
so
like,
since
last
monday,
we
are
running
dogenitrop.com
on
github.com
in
the
zip
architecture.
It's
around
12
percent
of
the
requests
that
is
being
served
with
that.
Basically,
like
the
transfer
that
we
is
doing
percentage
rollout
of
what
we
have.
We
don't
really
have
all
the
pages
that
we
can
run
in
that
we
rather
have
something
about
up
to
the
50
percent,
but
this
allo
will
allow
us
to
basically
performance
optimize,
the
current
implementation.
D
While
we
work
on
the
data
persistency,
which
is
connected
with
json
commands
and
like
integrating
our
work
in
the
charts,
it's
also
integrating
like
provisioning
dedicated
bucket
for
the
for
the
pages
deployments,
and
things
like
that.
So
you
may
expect
from
us
some
issues
about
the
dedicated
pages
package
and
like
octopus,
spreading
the
configuration
to
omnibus
and
to
the
cloud
native
to
make
it
like
possible
to
run
that
on
interrupt.com
in
a
in
a
way
that
we
plan
to
run
that
in
the
future.
Right.
D
We
use
zip
artifacts
that
are
associated
with
the
ci
job.
It
gives
us
a
test,
but
it's
not
the
end
goal.
The
angle,
it's
like
dedicated
bucket
that
I
hope
that
we
conclude
the
development
work
in
this
release
on
the
right.
D
A
D
D
We
kind
of
like
concluding
the
data
persistency
work
on
the
right
side
right
now,
and
once
we
have
that
this
is
basically
when
we
start
persisting
these
pages
deployments
that
we
are
not
doing
now
once
we
start
doing
that,
and
we
confirm
that
this
is
working.
The
next
step
is
going
to
be
background,
migration
of
the
all
existing
data
into
this
architecture.
D
A
Yeah
I
had
a
question
about
what
the
plan
was
for
that
later,
but
we
can
talk
about
that
late
about
that
later,
all
right
and
then
I
had
a
question
about
the
blocker
that
marion
brought
up
last
week.
Jason.
Do
you
wanna
localize,
your
result.
E
Sure
I
just
wanted
to
point
out
that
we
should
be
following
2334
as
the
immediate
unblocker
that
will
be
the
work
that
we're
doing
to
have
it
be
a
generator
pattern
that
is
actively
being
worked
by
dj.
We're
finalizing
discovery
on
it
now,
so
that
technical
work
can
begin
very
shortly.
A
E
Actually,
let
me
add,
apologies
the
demo
last
week
I
actually
did
an
example:
hand
created
environment
for
this,
so
the
distribution
demo
from
america's
thursday
of
last
week
actually
has.
This
is
how
it
does
actually
function
to
split
the
load.
We
bumped
into
a
few
things
and
learnings.
While
we
were
doing
that,
so
we
can
actually
see
how
the
right
path
gets
used.
The
additional
flag
needed
for
nginx
for
regex.
A
All
right,
I
don't
see
steve
or
jarv
here.
B
I
can,
I
can
just
quickly
say
we
have
an
epic
tracking
this,
so
I
don't
know
whether
there
is
any
additional
actions
necessary
here,
so
we
will
remove
nfs
from
infra
once
once
the
blockers
are
removed
and
the
epic
I
linked
earlier
sorry
n1c,
it's
epic
98.
A
A
Okay,
okay,
so
the
next
point
it
was
a
question
on
the
pages
migration.
I
think
I
understand
at
least
the
general
idea
I'll
keep
an
eye
on
that
epic
to
see
when
we
add
more
details.
I
know
that
the
master
epic
has
a
what
I
would
call
a
guesstimate
that
december
2020.
A
B
B
Does
I
mean
just
to
highlight
here
us
migrating
things
on
gitlab.com
right,
like
the
background
migration
and
the
continuation
of
work
of
this
group
can
go
in
parallel
once
that
happens
as.
A
Yeah,
no,
the
original
alignment
was
that
once
the
product
supports
sip,
then
we
consider
that
here
and
then
that's
being
tracked
separately,
but
we
move
forward
because
that
wouldn't
affect
new
multi-large
instances
that
might
be
stood
up,
that
that
does
that
don't
have
this
legacy
to
to
contend
with
so
yeah
gitlab.com
was
always
going
to
be
treated
as
a
special
case.
I
think
it
will
always
be
a
special
case,
but
cool
jason.
E
A
Yeah,
that's
fine.
I
also
have
based
on
the
notes
that
I
took
from
our
last
chat.
I
need
to
turn
that
into
a
write-up
that
we
can
use
for
this
working
group,
because
we
did
talk
about
the
fact
that
we
need
to
take
the
reference,
implementations
and
map
them
to
what
they
would
look
like
in
in
the
cloud
native
world
versus
what
they
look
like
right
now,
so
cool
that
is
all
for
this
week.
Unless
there
are
any
other
topics,
anybody
wants
to
bring
up,
we'll
wrap
it
up.
Then.