►
From YouTube: 2021-03-01 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
Hello,
everyone,
let's
get
started
today
is
2021
march
1st.
This
is
the
multi-large
working
group
weekly
meeting
and
let's
get
started
from
the
first
item
in
the
agenda.
First
lines
was
from
me:
basically
that's
a
follow-up
from
the
last
meeting.
There
was
a
request
of
additional
hands
on
the
pages
of
migration.
A
A
Just
verbalized
the
first
item:
you
want
to
verbalize
your
comment
under
that.
C
Yes,
so
thank
you,
john,
like
we,
we
managed
to
talk
today
with
the
at
the
end
that
is
gonna
working
with
us
and
actually
like.
We
started
discussing
like
how
to
approach
that,
but
I
think,
like
the
general
idea
is
like
that,
maybe
we
just
improve
over
our
borrowed.
C
Our
storage
configuration
to
kind
of
provide
a
disabled
type
of
the
switch
to
truly
like
disable.
This
type
of
the
access
for
the
cloud
native,
at
least
this
is
like
the
current
intent
behind
the
the
stuff
that
we
talked
today
that,
because,
like
with
the
current
storages,
we
don't
really
have
a
way
to
ensure
that
we
never
store
data
locally.
C
There
is
no
such
config
option
or
like
the
such
way
to
disable
that,
so
there
is
like
some
sense
that,
if
the
with
the
help
of
the
atm
may
approach
that
in
a
generic
way
and
like
propagate
that
elsewhere
to
all
the
environments,
that
would
benefit
from
that,
presumably
mostly
cloud
native,
where
you
don't
have
short
storage,
only
the
orbic
store.
D
This
is
a
follow-up
from
last
week.
Do
you
have
the
three
items
on
the
kubernetes
service
migration
blockers
a
is
done.
Thank
you.
I
think
it
was
jason.
If
not
thank
you
remember
who
did
it?
It's
already
finished
two
b
will
be
picked
up
by
the
delivery
team.
Thank
you
for
contributing
that
and
c
was
determined
to
not
be
as
important
as
the
other
two,
and
so
we
tend
to
schedule
for
13
and
11..
D
Hopefully
we'll
be
able
to
get
the
openshift
operator
beta
out
in
1310,
which
will
free
up
some
time
at
1511.
We
can
pick
it
up.
D
Yep,
this
is
also
an
outcome
of
last
week
said
your
concerns
around
dog
fooding
opened
up
this
epic.
Definitely
a
good
call
out
that
we
don't
have
this
today,
so
I
tried
to
enter
some
items
that
I
was
aware
of
others.
Please
do
take
a
look
at
that
list
and,
let's
make
sure
it's
relatively
complete
and
we
can
start
tracking
some
of
these
items.
D
One
item,
just
I
think,
based
on
your
concern,
sit
around
dog
fooding
is.
I
do
want
to
highlight
that
we
have
had
a
lot
of
success
with
the
delivery
team
contributing
to
the
helmet
sharks.
You
saw
this
above.
D
We
also
have
john
alon,
who
has
43
merged
a
marge
to
the
charts,
which
has
been
great,
and
you
know
really
appreciate
all
the
efforts
that
the
team
is
making
here
and
all
the
you
know,
and
all
the
partnership
and
the
reviews
from
the
distribution
team
so
that
that
has
been
working
pretty
well.
I
I
think
that
that
model.
D
Yep
there's
a
couple
other
items
we're
discussing
like
switching
to
the
omnibus
provided
postgres,
maybe
in
the
pg12
time
frame.
So
there's
a
couple
issues
there
to
follow
up
on,
but.
B
Yeah,
just
thanks
for
me
too,
we
can
read
the
update,
though
we
can
move
on.
Okay,
come
here,
all
right.
C
So
we
actually
started
serving
the
migrated
data,
the
one
that
we
have,
which
is
like
excluding
like
the
expected
missing
public,
which
is
like
about
99
percent
of
all
the
projects
to
migrate.
We
actually
got
to
25
today,
but
we
roll
it
back
to
10
because
of
some
pages
capacity,
problems
that
seem
truly
unrelated,
but
just
to
be
on
the
safe
side,
we
decided
to
roll
back
for
a
second.
C
Actually,
we
are
kind
of
looking
into
why
it
is
happening,
but
it
appears
to
be
more
like
the
not
pages
itself
problem
or
like
the
system
level
configuration
that
limits
amount
of
the
connections
that
a
given
node
can
or
like
the
given
process
can
accept
at
the
given
time.
You
can
read
more
details
into
that.
B
Any
questions
or.
A
A
Okay,
then,
moving
on
to
next
section,
what's
happening
next
amy,
you
have
the
first
item.
E
Yeah,
so
thanks
to
distributions
efforts,
we
are
now
continuing
on
with
migrating
the
api
service.
We
have
got
some
new
errors,
but
it's
been
labeled
as
a
blocker,
but
we'll
unblock
those
within
delivery
so
hoping
to
make
it
through
to
canary
in
the
next
week
or
so.
B
A
I
also
want
to
say
thank
you
for
delivering
for
picking
up
some
the
development
of
work
as
the
distribution
team
is
stretched
at
this
point
for
the
13.10
release.
Thank
you
very
much.
F
Yeah,
so
it's
just
a
quick
update
on
the
discussion
that
we
had
last
week
about
helm,
support
in
the
the
gitlab
environment
toolkit
also
the
opinion
that
wasn't
really
viable
and
it
says
that
you
just
need
to
run
a
hell
command,
but
you
know
when
you
get
into
it
again,
you
you
start
to
remember
all
the
little
things
you
need
to
do
to
actually
get
to
that
point,
such
as
out
of
the
cluster
and
getting
the
config
just
right
and
everything
else
and
I
realized.
F
Actually,
there
is
quite
a
lot
of
things
we
can
do
here
to
help
the
automation
of
it,
so
I'm
working
on
it
literally
as
we
speak,
adding
health
support
in
and
obviously
I'll
take
some
time,
because
germany's
is
a
speeding.
Kubernetes
doesn't
go
when
it
comes
to
development,
so,
but
hopefully
I
have
something
to
share
next
week.
A
A
Okay,
camille,
you
have
the
last
item
on
the
agenda.
C
Yes,
so
like
last
week,
we
kind
of
had
the
capacity
problem
on
like
people
being
partially
unavailable,
so
we
didn't
manage
to
like
run
the
next
wave
of
the
migration
we
we
managed
to
validate
all
the
outstanding
five
years,
so
we
don't.
We
don't
know
exactly
what
it's
going
to
be
after
the
fourth
wave,
and
now
we
are
kind
of
waiting
for
the
fourth
wave
to
happen,
which
should
leave
us
with
the
109
projects
left
that
have
different
kind
of
like
sibling
violations,
failures
that
we
already
should
have
cover
for.
C
So
I
just
hope
that
this
week
we
just
get
to
109
projects
left
as
the
migration
goes,
and
I
just
hope
that
also
that
we
get
to
100
out
of
this
99
that
we
get
migrated
to
be
served
on
github
pages.
So
this
is
the
goal
for
this
weekend.
For
this
week,.
A
Thank
you,
camille.
That's
the.
B
A
Of
the
agenda,
any
other
topics
we
want
to
discuss.
A
G
A
A
Yeah,
so
these
two
boards,
I
said
sorry
as
I
highlight
here-
those
are
two
new
boards
as
the
the
boards
for
the
next
step,
the
second
step
which
is
moving
the
web
api
and
the
pages
knows
so.
Those
are
the
boards
we
are
currently
working
on.
The
master
board
is
still
there.
I
haven't
checked
if
that
board
needs
to
be
updated,
but
these
two
boards
are
the
other,
the
the
issues
we
need
to
work
on
from
development
perspective
and
infrastructure
perspective.
B
A
Reason
of
the
two
boards
is:
we
cannot
combine
these
two
two
projects
or
two
groups
in
one
board.
A
That
was
an
initial
board.
I
guess
that
would
say
that's
a
master
board,
but
for
now,
as
we
are
moving
towards
the
second
step,
moving
the
web
api
and
pages
notes,
these
two
boards
are
just
the
issues
we
need
to
pay
attention
at
this.
B
Stage
yeah.