►
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
Okay,
good
morning,
good
afternoon,
good
evening,
everyone
today
is
march
29th.
This
is
the
multi-large
working
group
weekly
meeting.
Let's
come
to
the
agenda
first,
I
have
most
from
me
just
a
heads
up
that
we
are
trying
to
get
some
help
for
the
db
team.
Once
that
had
come,
the
request
reset
is
approved.
A
A
Okay,
josh.
B
Yep
just
quick
note
here
that
nicola
actually
merged
in
the
changes
for
proposed,
mr
to
allow
psychic
jobs
to
utilize
the
original
ambition,
because
so
that
was
merged
in
and
yeah.
I
just
wanted
to
say
that
this
was
configured
on
staging
today,
so
we're
making
great
progress
for
this.
That's
all.
C
Yes,
so
we
are
continuing
to
test
out
the
api
service
running
on
kubernetes
on
staging
that's
going
well
so
far.
C
We
are
now
serving
traffic
there
and
we'll
be
continuing
to
test
out
mostly
we're
testing
with
deployment
right
now
and
then
planning
to
move
to
canary.
So
we
are
clear
through
testing
to
to
go
there.
A
Thank
you
any
questions
about
this.
A
Okay,
then
I'm
the
next.
The
infrastructure
team
continues
to
investigate
the
name
server
resolution
problem
in
that
issue.
So
yeah,
if
you
have
some
clue
or
can
help,
please
share
the
feedbacks
there.
A
Thank
you-
and
the
next
item
is
also
from
me,
so
I
took
a
look
at
our
next
steps
after
we
finished
the
pages
migration,
so
this
epic,
actually
all
the
issues
under
this
epic
have
been
marked
as
closed.
So
I'm
just
wondering
if
we
have
finished
all
the
required
work
here.
A
Of
course,
if
us
is,
is
this
epic
is
done?
We
can
move
on
to
the
next
topic,
which
is
migrating.
The
nose
pages
knows
to
find
out
the
required
work.
If
not
yet
we
may
need
to
add
the
remaining
works
under
this
epic
and
continue
the
effort
for
the
api
web
and
api
knows
migration.
C
A
Thank
you
so
web
there
will
be
new
issues
created
for
the
web
knows.
D
I
assume
this
working
group
will
keep
going
until
get
lab
to
get
the
lead
to.
Kubernetes
is
done.
If
this
working
group
doesn't
do
get
left
private,
then
that's
fine
with
me.
We
discussed
it
last
time,
then
I
won't
attend
future
meetings
by
default,
happy
to
hop
on
any
call
and
feel
free
to
ping
me
on
slack
with
anything.
I
don't
think
anybody
asked
me
to
join
this
working
group,
so
I
don't
think
anybody
will
make
me
leave
him.
I
just
thought
I'd
say
something.
A
Okay,
any
sea
house.