►
From YouTube: 2021-03-22 Multi-Large Working Group Weekly
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
Good
morning,
good
afternoon,
good
evening,
everyone
today
is
2021
march
22nd.
This
is
the
weekly
meeting
for
our
multi-large
working
group
and
let's
go
to
our
agenda
first.
What
has
been
done
right
now
is
blank
anything
to
add
for
from
the
team.
A
I
know
we
have
been
very.
A
lot
of
teams
have
been
very
busy
with
the
recent
rapid
actions
to
mitigate
the
dot-com
incidents,
so
probably
that's
a
side
effect
of
this
working
group.
If
nothing
else
here,
let's
move
on
to
what's
happening
next
amy
you
have
the
first
item.
B
B
If
everything
looks
okay
and
I
think
logs
are
probably
our
biggest
question
mark,
which
we
haven't
yet
seen,
but
if
the
logs
look
okay,
we're
hoping
to
move
through
to
canary
this
week,
so
good
progress,
I
say:
we've
as
john
says,
like
we've
been
caught
up
in
incidents,
so
not
moving
as
quickly
as
we
had
hoped,
but
moving
along.
Nevertheless,.
A
Thank
you.
Thank
you.
Amy
great
progress
and
josh
has
an
item
is
josh
here.
No
stephen,
would
you
mind
to
verbalize
for
josh.
C
Yes,
we
just
recently
spoke
about
this
earlier
this
morning.
We
are
going
to
go
ahead
and
schedule
this.
I
believe
it's
a
p1
s1,
so
it's
been
added
to
our
1311
1311
deliverables,
jason's
assigned
to
it.
Now
we're
probably
going
to
get
some
additional
resources
from
the
team
to
help
get
this
knocked
out
quickly.
A
Questions:
okay,
then,
moving
on
to
blockers,
I'm
actually
a
proxy
for
the
db
team.
Some
background
to
share
here
there
is
a
blocker
on
the
db
side,
because
the
db
team
is
stretched
on
multiple
fronts,
owing
all
the
teammates
in
urgent
efforts
to
mitigate
the
dot
com,
incidents
about
the
db
saturation
and
also
then
followed
by
the
db
database.
A
Scalability
working
group,
which
there
are
a
few
items,
needs
to
be
done
as
soon
as
possible,
like
the
primary
key
overflow
migration
or
of
primary
key
overflow
mitigation,
and
also
the
blueprints
for
that
working
group
and
coupled
with
a
couple
people
were
leaving
on
paternity
going
on
the
paternity
leave
in
short
term.
So
we
are
asking
for
a
headcount
reset
for
to
mitigate
the
staffing
gap
in
short
term,
but
meanwhile
this
means
that
the
t,
the
db
team,
will
not
be
able
to
work
on
anything.
A
That's
out
of
the
scope
mentioned
above.
So
I
called
out
one
issue
here
this
one
we
talked
about
it
last
week,
but
the
db
team.
This
is
right
now
very
high,
a
very
low
in
the
order
of
the
priority
at
the
db
team,
or
at
least
they
are
not
able
to
make
progress
here.
So
the
question
is
here:
is
distribution
team
would
be
able
to
pick
up
and
jason.
You
have
a
question.
A
Yeah
so
I
just
quoted
amy's
comment
from
last
week.
Expectation
is
13.11,
but
I
think
we
also
need
a
priority
label
here
to
indicate
what
the
priority
expectation
here
is.
B
B
I
think
that
seems
fair,
like
what
what
are
the
options
we
have
for,
so,
if
we're
saying
that
database
definitely
can't
pick
this
up
like
what
other
options
are
there
like?
Who,
which
teams
are
we
sort
of
seeing
as
possible
teams
who
could
pick
this
up?.
A
That's
a
good
question.
I
was
thinking
about
that.
It
looks
like
it's
about
the
the
service,
provisioning
and
the
service.
You
know
after
after
deployment
you,
you
start
the
services
and
the
service
endpoints
check
the
endpoints
availability.
A
A
B
Okay,
let's
ask
around
then
I'm
I'm
a
little
worried
about.
I
know
infrastructure
is
super
busy
with
incidents.
So
when
I
say
infrastructure
I
mean
the
reliability
teams.
B
Let
let
me
see
what
I
can
do
and
see
if
we
can
like.
Maybe
we
just
schedule
this
in
delivery
and
that's
the
best
we
can
do.
A
Yeah,
but
I
also
asked
the
distribution
team:
if
they
can,
you
know
step
in
here
to
help
out.
C
B
B
Okay,
well,
let
me
see
if
we
can
make
any
progress
on
it
in
delivery.
It's
such
a
question
mark
right
that
way.
I
guess
we're
not
we
don't
know
if
we're
blocked,
we
don't
know
if
it
causes
incidents.
I
suspect
it's
probably
causing
something,
but
it's
not
like
everything
is
going
to
well,
not
as
far
as
we
know,
everything's
going
to
break
so
yeah.
Let's
see
I'll
see
what
delivery
can
do
with
that.
A
This
okay,
moving
on
to
discussion,
see
you
have
one
question
there.
E
Yeah
thanks,
I
wonder
how
kind
of
gitlab
private
relates
to
this
working
group,
and
if
we
do
something
like
get
lab
private,
we
will
have
you
know
multiple
large
installations,
which
is
the
name
of
this
working
group.
On
the
other
hand,
it
also
feels
like
a
separate
project,
as
I
I
don't
have
a
preconceived
idea.
I
just
I'm
wondering
whether
people
have
a
take
on
that.
D
F
Private
yeah,
I'm
not
streaming
my
insurance
private,
but
I
agree
they're
related
how
I've
been
thinking
of
these
has
been
that
we
are
focused
on
the
near
term,
released
on
completing
the
kubernetes
migration,
which
will
help
us
derive
operational
efficiencies
and
other
areas
that
will
help
us
become
more
efficient
at
running.
Multiple
large
instances
and
gitlab
private
would
be
taking
advantage
of
some
of
this
work,
at
least
to
help
improve
our
ability
to
run
multiple
instances.
E
It
feels
also
like
this
working
group
is
like
at
the
the
finish
near
the
finish
line
and
get
like
private
is
starting
to
gear
up,
but
for
clarity
we
should
might
as
well
make
it
live
private,
something
else.
In
case
we
decide
to
do
a
working
group.
There.
F
Yeah,
I
think
he
is
currently
driving
on
kubernetes
and
I
think
I
think
it's
been
good
to
have
that
focus
on
continuing
the
progress
on
tracking
updates
there.
I
feel,
like
gitlab
private
will,
if,
if
we
fund
it
and
launch
it
we'll
be
a
lot
focused
on
like
some
like
get
and
automation
around
key
management
and
kind
of
those
areas
will
take
priority.
F
A
Yeah
see
you
want
to
move
on
to
your
next
question
there,
or
we
already
covered
that.
E
Yeah,
I
think
some
of
the
shadows
were
enthusiastic
and
putting
in
notes.
But
okay,
that's
not
a
question
thanks.
Thank
you.
Okay,
amy.
B
Yeah,
I
was
just
gonna,
follow
up
on
josh's
discussion
point
last
week,
italy
in
kubernetes-
since
I
see
we
have
mark
here,
so
I
mean
yeah
josh.
Do
you
want
to
take
the
discussion
point
since
it
was
yours
originally
last
week.
F
Oh
yeah,
no
thanks
for
this,
and
thanks
for
joining
mark
appreciate
it,
as
we
kind
of
you
may
have
gotten.
I
think
the
working
group
is
focused
on
decriminal
migration
and
getting
operational
efficiencies
out
of
being
able
to
run
more
of
these
without
a
linear
increase
in
staffing,
and
one
of
the
areas
that
we're
currently
running
on
vms
is
is
the
gitly
service,
and
so
it
feels
like
to
me.
F
That's
probably
the
next
one
up
to
consider
being
migrated,
I'm
not
sure
amy
what
you
would
think,
but
it
also
would
help
other
projects
in
the
sense
that
you
know
if
you're
a
self,
a
self
managed
customer
who
wants
to
use
cloud
native,
it's
really
the
only
stateful
service
that
get
lab
runs
that
can't
be
replaced
by
a
managed
service,
ala,
rds,
elastic
cache
and
so
on,
and
so
there's
a
couple
reasons
behind
this.
F
I
think
that
make
it
quite
interesting
to
to
look
into
so
yeah
and-
and
I
think
we
can
highlight
here-
but
we
refer
from
the
customers-
I
think
some
of
the
that
it
right
now
doesn't
run
super
well
in
kubernetes.
Some
folks
are
doing
it,
but
it'd
be
good
to
maybe
perhaps
get
ahead
of
this
a
little
bit
between
maybe
distribution
and
and
generally
so
that,
when
delivery
is
ready
to,
you
know
to
pick
up
and
consider
gili
itself
for
migration.
F
G
Yeah,
thank
you
so
much
for
the
invitation
to
this
group.
I
mean,
I
think
it's
a
really
interesting
problem
to
tackle.
I've
had
some
discussions
with
zj
about
it.
I
know
he
had
wished
to
join
as
well,
but
I
think
this
is
a
little
bit
beyond
his
working
time
for
the
day
right
now,
we
see
no
distinct
reasons
why
it
shouldn't
work
in
kubernetes,
we're
very
open
to
supporting
that
migration
and
understanding
where
the
problems
arise
so
yeah.
Thank
you
so
much
for
the
invitation
and
look
forward
to
helping
out.
F
Awesome
thanks
mark,
I
think,
maybe
next
steps
here.
Just
the
art,
distribution
and
guillotine
can
work
together
and
just
compare
notes
on
what
we've
seen
and
then
we
can
figure
out
the
best
way
to
proceed
here
and
open
up
more
specific
issues,
and
then
we
can
then
prioritize
them
as
we
need
to.
A
Okay,
cool:
that's
the
end
of
the
agenda
items.
Anything
else.