►
From YouTube: 2020-11-09 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
I
will
be
your
dj
today
or
mc
in
this
case,
and
jerry
had
to
run
out
has
an
emergency
to
handle.
I
hope
I
won't
have
to
say
anything
apart
from
handing
it
over
to
jason
on,
what's
being
done,.
B
Sure
so,
first
off
we
do
officially
have
the
capability
to
configure
gitlab
pages
as
a
part
of
the
charts.
At
this
time,
documentation
on
this
will
be
coming
soon.
There
remains
a
specific
target
to
use
it
in
a
hybrid
fashion.
Until
we
have
gitlab
pages
in
the
container
and
everything
is
confirmed
and
functional
as
a
chart
of
its
own.
B
There
remains
the
challenge
of
doing
automation,
of
the
oauth
integration
due
to
the
nature
of
you
have
to
have
rails
functioning
in
order
to
actually
do
oauth
setup
that
won't
specifically
affect
gitlab.com.
However,
as
we
already
have
all
of
that
in
play
with
the
various
secrets-
or
I
don't
believe
it
will,
I
could
always
be
corrected.
B
A
B
If
you
look
at
those
graphs,
you'll
see
in
the
center
there's
a
memory
usage
and
what
you'll
see
is
at
200
rps,
the
api
behaves
very
well,
and
then
we
switch
to
the
20
rps
web
requests
as
a
part
of
the
gpt,
and
all
of
a
sudden
memory
is
fluctuating
all
over
the
place.
This
is
primarily
due
to
get
data,
rendering
large
chunks
things
like
that.
They
have
a
significant
impact
on
the
behavior
there.
B
B
Camille
is
unable
to
be
here,
but
he
did
say
that
we
can
read
the
notes
below.
Would
anybody
like
to
read
those
or
should
I
just
keep
talking.
B
C
B
In
regards
to
following
up
on
the
blockers
that
we
have
coming
at
13
7,
I
wanted
to
note
that
we
have
scheduled
two
out
of
three
the
major
action
items
regarding
unified
structured
logging
across
the
cloud
native
they're
set
up
for
13.7,
and
it
basically
comes
down
to
identifying
and
implementing
the
logger
so
that
we
actually
get
structured
json
out
of
everything,
that's
consumable
through
our
fleet.
B
As
as
it
stands,
it
is
proving
out
and
balancing
the
fleets
of
ponds
are
working
out
fairly
well.
Some
further
testing
and
load
testing
will
be
interesting
to
see.
B
D
Yeah
a
couple
quick
updates
here.
One
is,
I
just
want
to
circle
back
on
the
discussion
from
last
week
on
the
the
customer
one
item,
and
so
we
are
meeting
with
the
count
team
later
today
and
we'll
get
a
kind
of
initial
call
going
and
they
reached
out
so
we'll
see
what
that'll
say
and
and
we'll
update
more
on
on
the
team
on
how
that
goes.
A
Cool
thanks,
josh
blockers.
We
don't
seem
to
have
any
at
the
moment,
so
work
is
ongoing.
So
I'll
move
to
discussion,
stephen
or
jason
about
meeting
recording.
E
D
Yep,
sorry,
I
have
a
co-pilot
here,
so
I
want
to
circle
back
just
real
briefly
on
the
update
on
nsfest.
There
was
this
garden
last
week
and
just
wanted
to
get
a
real
crisp
answer
on
where
we
are
at
so
just
confirming
for
sure
that
nfs
for
git
repos
are
in
fact
documented
as
clearly
being
deprecated.
The
current
plan
from
the
gilly
team
is
to
make
them
is
to
remove
support
entirely
in
14.0
so
may
of
next
year,
and
we
also
had
don't
recommend
people
to
use
nfs
with
the
exception
of
pages.
D
So
if
you
look
at
the
various
reference,
architectures
and
other
documentation,
you
will
see
pages,
that's
not
recommended,
or
netflix
isn't
recommended,
with
the
exception
of,
unless
you
want
to
use
pages,
so
I
think
we're
pretty
good
shape
there
and
once
obviously
pages
no
longer
require
nfs.
We
can
further
change
that
language
and
I
tentatively
scheduled
the
investigation
into
mineo
and
13
at
eight.
D
We
can
see
where
that
goes,
but
we
have
some
pretty
big
items
here
need
to
finish
up
and
stabilize
petroni,
and
then
we
also
are
working
on
the
operator
as
well.
So
probably
a
little
bit
difficult
to
get
that
to
too
soon,
but
we
can
start
looking
at
that
and
doing
this
investigation
here
shortly.