►
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).
B
A
Welcome
to
the
foundation
infrastructure
working
group
meeting
yeah
before
we
started
recording
I
already
merged
the
postgres
15
one,
because
that
had
three
approvals
from
long.
A
That
has
been
merged.
We
have
still
this
one
all
right.
Six
minutes
minutes
ago,
I
sent
the
Bing
and
we'll
see
it's
named
for
this.
One
I
also
send
a
bing
here
so
short-lived
Nets
credentials.
I
did
a
review
here
and
I
had
some
trouble
with
the
naming,
so
I
think
it
would
be
better
if
we
at
least
have
bootstrap
somewhere
in
there
to
identify,
distinguish
or
like
explain
what
it
is
actually
used
for
and
yeah.
A
That
would
also
like
switch
the
logic
right
so
instead
of
adding
and
it's
currently
called
permanent,
credential
and
I
rather
have
a
bootstrap
credential,
be
the
exception
right,
so
the
permanent
credentials.
Basically,
but
you
don't
have
to
name
that,
that's
just
what
we
have
currently
and
the
bootstrap
credential
is
going
to
be
the
so
it's
basically
an
inverse
of
what's
currently
implemented,
but
it
shouldn't
be
like
it's
just
a
refactor
but
yeah
I
think
that
would
be
better.
C
Yeah
I
agree:
does
it
make
sense
for
me
talking
to
this
now
or
after.
A
That
I
would
wait
because
we
already
have
consensus
here
right,
so
I
did
the
initial
review
and
then
Daniel
just
got
back
that
he
liked
the
idea.
So
I
would
wait
for
that.
A
A
B
B
B
C
A
C
A
A
Yeah,
so
there
were
this
comments,
so
yeah
I
constantly
had
a
new
idea.
I
made
a
lot
of
changes,
Joseph
liked
the
idea
of
like
just
some
like
minor
nitpicks,
about
the
implementation,
like
some
Ruby
optimizations.
That
could
be
done.
A
And
those
changes
have
been
done
so
I'm
waiting
for
Joseph
to
ready,
review
and
approve
and
then
maybe
someone
else
can
also
add
a.
C
A
B
C
C
I
also
saw
a
PR
if
I'm
and
then
piaz.
If
you
go
up
to
PLS
yeah,
okay,.
A
C
That's
why
oh
okay,
but
he's
waiting
for
some
I
think
on
the
pr
he's
waiting
for
feedback.
C
A
I
will
just
respond
yeah.
C
A
B
Yeah,
so
we
we
see
a
lot
of
speed.
We
see
some
speed
up
of
the
template,
rendering
and
such,
but
there
is
a
bug
like
when
you
I
they
should.
They
should
create
a
PR
in
the
coming
week
or
another
PR.
An
issue
would
explain
everything,
but
basically,
in
the
simplest
thing,
what
happened
is
that
if
you
have
like
deploying
a
Bosch-
and
you
have
like
the
postgres
on
the
job
list
like
basically
on
the
latest
in.
B
Manifest
if
you
have
like
an
insane
amount
of
workers
like
sap,
has
like
they
have
25
workers
for
each
deployment,
Monet
does
not
when
it's
compiled
Ruby
with
silang
the
jobs,
don't
quit
fast
enough.
So
what
happens
is
that
they
get
in
a
Timeout
until
they
get
into
the
until
Monet
starts
postgres.
B
So
all
the
workers
are
started
first,
because
apparently
I
didn't
know
this,
but
apparently
it
seems
that
the
jobs
how
you
put
them
in
the
in
the
Manifest
is
is
setting
the
order
for
when
what
monets
needs
to
start
at
what
time.
B
A
I,
have
you
compare
it
like?
It
could
also
be
that
previously,
it
was
less
of
an
issue,
because
the
Ruby
processes
were
starting
slower,
so
they
would
never
have
to
time
out
because
they
would
like
still
be
in
their
starting
State
and
then
postgres
would
already
be
up
and
they
would
be
able
to
connect
to
postgres
the.
B
A
B
B
Yeah
but
I
I
thought
it
would
never
it
it.
Would
it
wouldn't
that
that
the
order
of
how
the
releases
were
set
in
the
Manifest
did
not
matter,
because
everything
was
started
at
once.
Anyways
yeah,
only
only
I
now
know
this
that
Monet
only
like
starts
10
jobs
at
a
time,
so
at
the
time
when
it
reaches
when
it
reaches
the
next,
the
next
job,
it's
already
timing
up
but
yeah.
This
is
just
one
thing
we
noticed
and
I
think
this
is
just
a
bigger
issue.
B
I
think
we
just
also
need
that
that
the
workers
just
need
to
quit
faster.
B
B
B
A
A
B
A
B
C
C
A
C
Is
now
this
continuous
VMS
check
I
thought?
Maybe
this
can
introduce
a
little
bit
of
CPU
over
overhead.
B
B
So
I
had
an
issue
like
but
three
days
ago,
when
they,
when
I
got
a
call
and
I
said
like
we
see
like
every
10
seconds,
we
see
a
scan
and
fix,
but
then
we
looked,
they
had
like
300
deployments
on
one
bush
and
there
were
a
few
VMS
that
had
some
failing
agents,
so
it
was
continuously
just
like
that.
It
was
like
for
for
five
days.
There
was
like
a
spike
going
on.
A
C
C
B
B
And
I
I,
don't
think
that
has
any
implication
with
Nets
I.
Don't
I,
don't
think
so.
But
that's
just
one
thing:
I
I
heard.
A
C
Much
traffic
yeah
yeah,
but
some
remote
call
invocations
at
them
passing
here
and
there
yeah.
A
Okay:
let's
go
over
the
inbox.
A
C
B
C
A
C
B
A
Don't
know
sure
but
I
don't
know
if
it's
a
limitation
of
Monet.
C
B
A
I
will
okay
I.
A
A
B
Not
yet
I
think,
but
it's
been
responded
three
days
ago.
So.
A
A
A
It
doesn't
work
that
way
so
I
need
a
PR,
like
the
one
I've
already
created
for
something
else.
So
I
already
created
this
one
to
move,
watch
packages
and
everything
into
the
clouds
on
your
repo.
C
A
C
B
A
A
C
A
B
Yeah,
this
was
something
because
I
was
working
with
the
AWS
CLI
to
do
the
cleanup
stuff.
A
C
B
B
A
I
think
there's
like
I,
think
Joseph
Palermo
is
also
experiencing
that
a
lot
because
he's
doing
a
lot
of
credential
rotations
now
so
he's
having
a
lot
of
places
where
he
has
to
go
through
a
PR
review
to
update
a
credential
somewhere
yeah
yeah
I
mean-
and
we
did
say
that
at
some
point,
that
we
wouldn't
that
we
didn't
want
to
enforce
reviews
on
CI
changes,
but
I
don't
think
we
have
a
way
to
make
an
exception
for
not,
except
for
in,
like
our
policy
as
and
we
can
just
merge
it.
B
A
A
Yeah
but
Dale
is
working
on
the
automation
to
and
for
put
this
Branch
protection
rules
in
place
everywhere.
So
I
mean
like
if
there's
still
repos,
where
you
can
push
your
stuff
to
master
that
won't
take
long
like
that,
will
go
away.
A
B
C
Have
we
can
have
customized
rules
for
some
repos,
for
example,
which
will
be.
A
C
B
C
C
Actually,
you
need
an
automation
which
watches
for
keep
push,
PR
creation
and
then
yeah.
C
Yeah,
okay
yeah
we
can,
we
can
have
Auto
proof,
slack
handle
something
occur
in
slack
to
Pink.
A
C
A
Can
even
have
like
we
can
have
a
GitHub
actions,
workflow
that
would
trigger
on
a
PR
and
if
the
pr
only
changes
files
that
are
related
to
CI
it
automatically.
Yes,.
A
We
need
to
figure
out
to
do
it
like
the.
The
problem
is
that
you
cannot
set
up
like
GitHub
actions
for
all
repos,
but
you
need
to
do
it
for
repo
I
would
love
it
if
we
have
like
events
in
an
orc,
so
you
get
like
can
trigger
a
workflow
on
every
PR
in
an
organization
yeah,
because
if
you
have
that,
then
it
would
be
pretty
easy
to
implement.
B
Yeah,
let's
see
if
we
even
need
to
put
effort
in
this,
let's
look
in
the
next
coming
few
months.
How
many
times
yeah.