►
From YouTube: 2021 12 02 Jenkins Infra Meeting
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
Welcome
to
the
jenkins
infra
team
meeting,
it's
the
2nd
of
december
2021.,
so
we
excuse
damian
deportal,
he's
stuck
in
traffic
at
the
moment.
I
think
we've
got
several
topics:
let's
go
through
them
and
talk
to
them
briefly,
so
we've
got
as
attendees.
A
So
in
terms
of
topics,
previous
weekly
build
failure,
apt-great
apt-get
upgrade
campaign,
outages,
kubernetes,
1.20
tls
certificate
for
repo
oracle.
B
A
Access
terraform
costs,
update
cli
domain
renewal,
fastly
wow,
we've
got
lots
of
topics
any
oh
and
I've
got
one
more
topic
to
add.
Oh
no,
here
it
is
it's
already
here,
okay,
so
it
was
a
new
test,
new
solutions
topic,
any
other
topics
than
what
are
listed
here
that
you
need
to
put
on
the
list.
I
think
we're
going
to
run
out
of
time.
Long
before
we
run
out
of
topics.
C
Maybe
stefan
next
week.
A
I
don't
know:
oh
yes,
newt,
okay,
we'll
have
a
new
team
member
joining
that's
good
right.
So
so
that's
an
announcement
thing.
Yes,
new
team
member
new
team
member
joining
at
cloudbees
on
infrastructure.
A
Okay,
all
right,
so
so
in
terms
of
previous
weekly
failure.
I
the
background
on
that
this
is,
is:
was
this
the
weekly
build?
So
I
assume
it
was
the
weekly
jenkins
build.
A
A
A
The
next
topic,
then,
was
this
apt-get
upgrade
campaign,
and
here
it
is
what
what
I
think
this
is
really
saying
is:
we've
got
a
number
of
machines
that
are
not
running
the
most
recent
patches
and
and
systematically.
We
need
to
get
them
up
to
it.
A
So
one
example
is
instances
that
wouldn't
reboot
another
that
we
don't
have
access
to
that
others
on
the
team.
Don't
have
access
to
that.
It's
only
olivier
in
me,
another
that
has
had
had
to
receive
major
rework
damian
you're
here
great,
so
we
can
let
we
can
switch
to
have
you
running
instead
of
me.
E
Sorry,
okay,
so
you
were
describing
the
issues
on
the
appetite.
A
A
E
E
So
we
had
an
issue
that
has
had
impact
on
the
weekly
release,
where
pkg
was
in
a
had
a
lot
of
held,
broken
packages
and
so
mark,
and
I
debugged
the
debts.
In
fact,
the
package
were
not
installed
correctly
because
it
was
a
mix
of
xenial
and
bionic
sources,
even
for
the
core
packages
and
most
of
the
packages
were
from
an
initial
ubuntu
non-server
image.
So
a
bunch
of
xmls
running
x7,
x11
running
and
yeah.
So
we
had
to
clean
mark
while
you're
there
or
maybe
team,
I'm
not
sure
what
is
the
service
census.
E
A
Census,
c-e-n-s-u-s-
and
I
thought
it
was
used
for
for
survey-
results
for
who's
who's
using
it.
How
mark
I
don't
have
access
either
so.
A
D
E
A
E
D
E
Use
the
same
as
ci
jenkins
or
whatever
the
machine
you
will
have
access
to.
Okay,
I
will
send
you
a
public
key
and
I
will
take
care
of
that
after
the
meeting.
If
it's
okay
for
you
yeah,
so
you
won't
waste
your
time
searching
for
the
correct
key.
E
E
So
in
fact
there
is
that
one
of
the
data
volumes
wanted
to
survey.
Bigger
usage
wasn't
remonded
after
the
reboot
because
it
was
not
written
on
fstab.
E
So
it's
an
old
issue,
so
I
took
care
of
that
and
andrew
opened
a
new
issue
with
the
issue
and
we
took
care
it's
a
kind
of
temporary
situation,
because
we
we
plan
to
move
that
virtual
machine
to
azure
or
even
better
to
kubernetes.
E
Yeah,
so
that's
all
so
we
will
have
some
work
to
do
in
the
future
to
to
ensure
that
this
campaign
of
epic,
the
upgrade,
are
not
exceptional.
I
will
say
we
should
have
a
weekly
at
least
upgrade
and
reboot
on
all
the
virtual
machines,
because
a
bunch
of
issues
are
cooked
and
it's
better.
If
we
control
when
we
could
have
the
issue,
so
that's
something
we
could
plan
for
the
short-term
future
we
could
use.
What's.
E
E
E
Okay,
a
point
on
the
recent
outages
so
jenkins,
io
postmortem,
has
been
published
last
week
right
after
the
team
weekly.
So
it's
going
to
be
frozen.
I
haven't
seen
any
comments
here
and
neither
did
I
receive
any
feedback.
A
E
Yeah,
I'm
gonna
wait
to
tomorrow
end
of
day
that.
E
There
has
been
an
issue
in
archive
monday,
so
erv
and
I
have
to
write
a
postmortem
for
that
one.
So
it
was
a
consequence
of
the
aptigate
upgrade
that
upgraded
the
kernel
and
some
low-level
modules
that
apache
relied
on
for
the
bandwidth
limitation.
E
So
it
sounds
like
that.
The
bandwidth
was
not
working
with
older
canal
and
it
started
working,
which
was
the
outage.
So
we
were
way
past.
The
bandwidth
and
the
calculation
for
the
bandwidth
was
done
for
rackspace,
which
is
not
an
issue
on
a
rocker
right
now
for
that
machine.
So
we
removed
that
after
confirmation
by
olivier
that
it
makes
no
sense
anymore.
E
E
Great,
so
I
mean
okay,
yes,
so
postmortem,
and
I
were
involved
on
that
one.
So
that's
also
a
good
thing.
That
means
that
we
are
trying
more
and
more
to
work
together
and
not
to
learn
great
kubernetes
1.20
upgrade
rv
mic
is
yours.
C
C
E
E
Because
they
are
the
bare
minimum
to
be
sure
that
we
can
start
using
kubernetes
for
real,
so
core
dns
is
the
is
an
example.
The
dns
implementation
depends
on
the
kubernetes
distribution
that
you
have
so
most
of
the
time
that
installation
is
managed
by
the
cloud
provider.
That's
the
goal
of
these
add-ons
and
we
were
not
aware
of
that
existence
because
they
were
installed
one
shot
and
not
managed
automatically
during
the
eks
installation.
E
We
think
that's
all.
That
was
quite
a
success,
a
great
job,
because
that
that
went
very
well.
The
preparation
and
the
communication
were
really
good
better
than
olivier
or
mines,
so
congrats
on
that
also
that's
a
good
thing
for
end
users.
E
And
for
the
next
one,
so
you
will
be
the
master
of
the
timeline
again
and
we
will
have
to
improve
a
bit
to
work
a
bit
more
on
terraform.
But
now
we
have
proved
that
you
have
the
ability
to
pull,
request
and
change
element
if
needed
on
terraform.
So
you
should
be
autonomous
and
I
can
be
there
either
pairing
with
you
or
as
a
backup
or
you
can
do
it
alone.
Your
choice.
E
E
A
E
I'll
take
care
of
that
then
oracle
cloud
we
need
access.
I
haven't
put
your
name
tim
because
I
was
sure
that
you
have
access
on
the
record
cloud
console.
E
Yep
and
I
propose
gave
in
at
the
same
time
as
well,
if
it's
okay
for
everyone
here.
D
A
I
don't
know
how
we
would
do
that,
but
it
sounds
great
tim.
Would
you
be
willing
to
work
with
me
on
it?
I
think
olivier
and
I
are
the
ones
who
have
access
to
it.
Currently,
it's
it's
too
much
of
a
one-off
right
now,
integrating
with
azure
ad
feels
like
a
big
win
to
not
not
have
it
be
such
a
one-off.
E
A
D
A
E
A
word
about
terraform
for
more
clouds,
so
work
in
progress.
There
is
a
new
epic
created
as
an
umbrella
to
follow
up
the
the
short-term
terraform
related
tasks.
E
E
It
was
15k
last
week,
so
that's
really
good.
I
hope
we
could
gain
way
more
by
moving
some
virtual
machines
almost
there
and
the
costs
on
azure
also
are
way
lower
than
10k.
So
congratulations
on
the
fourth
of
everyone.
There
are
still
some
improvements
that
we
can
do
on
the
cost,
but
that's
already
a
lot.
We
decreased.
E
A
word
on
the
update
cli
campaign,
unless
you
have
question
about
terraform
update
or
the
cost
okay,
so
rv
continued
the
the
big
effort
about
trying
to
put
update
cli
on
a
lot
of
repository
most
of
the
time
we
only
track
one
or
two
elements
on
our
repositories,
and
so
the
idea
was
to
track
as
much
as
possible.
E
E
E
Io
domain
renewal,
thanks
for
the
pointer
folks,
for
that
one,
that
means
we
should
start
renewal
before
end
of
year.
If
I
understand
correctly.
C
Yeah,
for
now,
the
the
renewal
price
have
an
increase,
but
I
don't
know
where
the
domain
is
thread.
What
is
a
registrar
for
jenkins
tatario?
A
I
and
I
would
have
to
double
check,
go
ahead,
tyler,
I'm
pretty
sure
yeah
tyler,
I
think
tyler
croy
had
it
and
the
one
that
the
one
that
is
expiring
soon
is
jenkinsci.org.
C
E
Yeah,
because
the
direction
it's
taking
with
the
private
company
behind
yeah,
the
price
will.
A
E
A
Oh,
that
would
be
great.
I
would
love
to
not
take
over
on
that
one.
I
had
had
this
conversation
last
year
with
tyler
about
jenkinsci.org
and
it
auto
renewed,
so
he
just
left
it
to
do
what
it
did,
but
in
this
case,
if
you
perceive
that
there's
a
cost
savings
by
changing
our
renewal
pattern,
certainly
nine
more
years
of
jenkins.io
is
a
predictable
thing.
We
want
right
right.
We
don't
want
to
lose
the
jenkins
domain.
E
That
would
be
also
interesting
to
have
tyler
feedbacks
on
that
part.
It
might
be
valuable
as
well.
A
E
Worst
case,
we
will
learn
something
about
how
it
works,
so
right
won't
be
a
waste
of
time.
Okay,
gavin
asked
about
fastly
as
code,
so
because,
right
now
the
fastly
configuration
for
the
domains
are
managed
by
the
first
ui.
That
means
you
need
access,
etc,
and
there
are
a
bunch
of
way
to
configure
it
remotely.
E
Here,
we've
put
an
example
of
terraform,
since
this
is
our
trend,
you
can
do
this
without
the
way,
but
that
will
that
will
be
interesting,
because
that
could
mean
maybe
less
management
to
access
and
we
could
propose
changes,
review
them
or
at
least
being
able
to
roll
back
with
shared
knowledge.
So,
honestly,
I
think
that's
a
good
idea,
but
there
might
be
downside.
I
don't
know
which
one
right
now,
I'm
not
sure
in
terms
of
security,
if
there
are
sensitive
elements
on
this
configuration.
E
So
that
could
be
interesting
to
to
share
that
so
thanksgiving.
That
will
be
an
item
to
take
it's
my
proper,
my
proposal.
If
there
are
no
voice
against
that,
I
will
take
care
of
adding
an
issue
to
the
terraform
umbrella
unless
someone
wants
to
manage
it
with
another
tool
which
I
don't
honestly
don't
mind.
A
Alfred
yep
I'd
say:
let's
just
continue
the
discussion
in
the
thread.
I
don't
think
we
need
to
discuss
it
here,
I'd
like
time
in
this
meeting
for
a
presentation
by
gradle
enterprise
and
probably
a
presentation
by
launchable,
but
this
will
wait
till
next
week
for
the
further
discussion.
D
E
Using
integrating
gradle
and
launchable
as
new
services
on
the
infrastructure
could
be
worth
it
for
the
contributor
developers
of
jenkins.
We
have
to
evaluate,
let's
say
the
overall
cost
in
term
of
time
and
techniques
right,
but
yeah.
There
is
no
strong
node.
That
could
be
a
good
idea
for,
but
okay,
please
thanks
tim
for
reminding
us
about
carpenter
that
has
been
presented
by
aws.
That's
also
something
to
check
if
it
could
be
valuable
to
to
improve
the
auto
scaling
of
the
kubernetes
cluster.
It's
not
amazon.
Only.
E
A
A
E
E
E
Cool
I'll
take
care
of
publishing
on
the
github
repository
and
if
it's
okay
for
everyone,
I
will
also
publish
this
note
on
this
course
on
the
community
as
well.
That
might
be
a.