►
From YouTube: 2022 05 24 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
A
And
the
the
image
is
okay
on
our
side
and
we
are
waiting
to
fix
the
show
library
bugs
before
delivering
to
infrastructure.
So
no
problem,
whatever.
A
A
First
of
all,
we
are
now
using
docker
community
engine
on
the
azure
virtual
machines
for
windows,
containers
that
wasn't
emergency,
but
thanks
to
team
jacob.
We
know
that
by
default,
azure
is
gonna.
Stop
updating
the
windows,
server
images
on
azure,
because
their
partnership
with
mirantis
is
going
to
stop
and
we
were
using
the
result
of
that
partnership
by
default,
which
is
docker
enterprise
edition.
We
don't
need
these
features,
so
our
process
is
now
building
and
installing
docker
using
windows,
core
version
with
the
community
edition
no
versioning.
A
It's
the
same
way
like
we
do
on
the
ubuntu
images.
We
use
the
latest
version,
we
could
version,
but
that's
we
don't
see
a
reason
for
doing
that
right
now.
It
works
very
well
and
that's
also
opened
a
side
effect
which
is
not
part
of
the
team
priority.
But
now
we
have
a
first
version
of
the
windows,
server,
2022
images,
so
the
next
step
will
be
to
test
these
images
next
to
the
actual
windows,
server
2009.
A
Second
task:
close
windows,
virtual
machine
agents
were
slower
and
available
on
sea
h.
You
can
say
during
the
weekend
there
was
an
incident
that
has
been
fixed.
I
don't
remember
the
issue,
but
it
was
quite
straightforward.
A
There
were
some
issues,
so
I've
tried
to
document
the
diagnostics,
the
troubleshooting
process,
no
logs
on
jenkins
side
that
were
useful,
except
high
failure
to
deploy
the
virtual
machines,
but
on
other
side
there
were
useful
errors.
Are
the
disk
size?
That's
a
side
effect
of
the
previous
tasks
with
the
new
windows
server.
Is
that
with
the
new
templates
base
image
that
we're
using
you
need
127
gigabyte,
which
is
the
default,
and
we
were
using
19
gigabytes.
A
It
was
only
on
cige
and
king's
iu.
That
fix
was
already
in
place
since
months
is
untrusted
saving.
So
just
fixing
that
configuration
item
was
able
to
solve
the
problem.
The
issue
wasn't
blocking
the
users
and
the
slow.
It
was
just
only
scheduling
virtual
machine
agent
on
amazon
and
not
on
azure.
It
was
not
a
mix
of
the
two,
so
we
still
have
working
workloads
for
our
end
users.
A
Finally,
thanks
mark,
so
we
gave
access
to
vanson
at
home
to
the
vpn.
A
Initially,
the
goal
was
to
allow
him
to
trigger
release
of
the
remote
team,
so
the
release
of
the
remoting
was
another
subject
treated
by
team
and
you
mark,
as
I
understand
so,
the
song
closed
prematurely.
The
issue
still
I
took
on
myself
to
give
him
the
virtual
the
vpn
access,
because
vancouver
is
someone
helping
us
a
lot
of
time
and
we
will
need
his
help
to
troubleshoot
the
kubernetes
plugin
with
basil,
so
the
vpn
access
was
more
than
needed.
In
that
case,.
A
One
two,
three:
okay,
first,
one
permanent
redirect
jenkins
is
the
way
that
iu
the
former
domain.
Two
stories
jenkins
say:
stefan,
can
you
give
us
a
head
up.
C
Yes,
we
we
did
end
chart
for
the
http
already
returns
that
we'll
be
able
to
handle
all
the
redirection
we
want,
and
I
updated
the
kubernetes
configuration
from
for
fraud
cavites
to
handle
that
specific
redirection
jenkins
is
the
way
that
io,
but
we
need
now
that
the
cname-
that's
the
redirection
or
dns
point-
has
a
cname
and
the
ip
on
the
domain.
Sorry
for
that
public,
heavy
test
to
be
able
to
handle
that.
A
Okay,
so
the
radiation
works.
If
you
use
the
customer
tc
posts,
yes,
and
we
are
waiting
for
alissa
gavin,
I'm
not
sure
it
looks
like
because
alisa
told
us
to
see
with
you
mark-
and
I
remember
that
gavin
at
some
time
was
created
the
thing
initially
so
not
sure
who
is
the
owner.
B
Of
the
domain
yeah
I'll
double
check
with
alyssa,
I
believe
she's
actually
the
owner,
but
that's
putting
ownership
of
a
domain
into
the
hands
of
someone
who
isn't
typically
doing
domain
ownership.
So
let
me
talk
with
her,
we'll
we'll
work
it
out
and
be
sure
that
we
coordinate
how
to
make
that
transition.
A
B
B
A
Sounds
good,
so
almost
almost
closed
next
step
is
giving
access
to
brazil.
Since
this
is
an
internal
cut,
this
process
there
isn't
a
detailed
status
on
the
issue
I
sent
in
the
information
and
I'm
waiting
for
feedback
from
him
I
didn't
had,
but
I
only
sent
it
yesterday
or
two
days
ago,
so
it
took
me
some
time
so,
no
expectation
there.
A
I
propose
for
the
next
iteration
that
we
don't
keep
that
issue
and
we
wait
for
brazil
to
give
us
feedback.
If
we
get
feedback,
I
will
put
it
back
in
the
next
iteration.
Otherwise
we
let
them
rot
somewhere
until
busy
disabled
garvey.
We
have
the
auto
notified
people
based
on
service
floating
rooms.
I
assume
we
didn't
have
time.
No.
I
have
to
work
on.
D
A
Okay,
are
you
do
you
think
you
can
work
on
it
next
week,
or
should
we
put
it
back
to
the
backbone?
I
should
have
time
to
open
it.
Okay,
so
we'll
keep
one
for
next
week
mirrors
jenkins,
so
we
had
an
incident
last
friday
when
we
changed
the
cname
for
the
mirrors
to
the
new
machine,
so
mirrors
successfully
switched
to
the
gauge
in
kinsaio.
It
worked.
We
didn't
hear
from
an
issue
in
that
area.
A
However,
we
had
the
side
effects.
The
domain
update
that
you
need
to
tell
you
was
c
named
university
and
the
ttl
of
the
dns
was
one
hour.
So
during
one
hour
we
had
to
wait
with
broken
update
center
everywhere
until
the
dns
went
back
to
the
original
machine
160..
A
So
sorry
for
the
impact
for
the
people
used
on
that
area,
and
we
will
have
to
take
care,
but
it
works
very
well.
The
mirror
the
mirror
orbits
is
now
the
only
mirror
system.
It
seems
to
work
very
well.
We
didn't
see
a
big
pixel
changes,
so
the
next
step
for
the
upcoming
iteration
will
be
cleaning
up
the
puppet
code,
ensuring
that
there
isn't
any
upcoming
request
to
the
actual
virtual
machine
and
then
converge,
remove
postgresql,
mirror
brain
the
virtual
host
and
put
it
on
the
puppet
management
again
once
neural
file
is
removed.
A
A
No
question
digital
ocean,
they
went
back
to
us
and
I
are
going
to
take
appointments
with
them.
They
are
interested
in
continuing
the
partnership,
but
they
want
to
discuss
feedbacks
and
evaluating
the
needs
for
the
upcoming
year.
So
we
were,
we
have
to
work
on
preparing
ourselves
on
measuring
same
rate
as
the
rate
we
were
burning
money
since
the
beginning
of
the
sponsorship.
A
Ideally,
if
we
could
envision
moving,
the
goal
will
be
trying
to
say
what,
if
we
stop
using
e-caps,
what
if
we
stop
using
kubernetes
cluster
on
amazon
and
using
only
digital,
also,
that's
the
scenario
I
will
want
to
get
as
a
baseline,
and
then
we
see
if
the
cost
is
too
much,
then
we
can
negotiate,
but
that
would
be
a
safe
word
for
us
because
we
wouldn't
be.
We
wouldn't
have
to
depend
on
your
native
best,
for
that
part
sounds
good
for
you.
A
A
Questions
datadog
depreciation
of
on-call
anders
in
monitors.
B
D
A
It
sounds
like
that.
It's
working
because
of
that
one
so
we'll
see
the
worst
case
is
that
by
removing
atom
cool
we
we
disable
that
feature,
and
we
cannot
enable
it
again
because
it's
depleted,
because
maybe
it's
deprecated
but
still
running
for
us,
that's
the
thing
we
are
not
sure.
So
we
need
to
be
sure.
A
Mirror
in
singapore,
so
now
we
have
all
the
information
required.
Now
one
book
has
to
be
written.
We
took
the
opportunity
to
meet
with
olivier
today
and
he
shared
some
information.
We
have
some
information
on
different
areas
and
some
are
on
code
that
we
deleted
a
few
months
ago,
so
just
have
to
dig,
but
the
idea
is
that
it's
only
finding
the
correct
mirror
url
to
give
to
the
people.
So
they
can
everything
from.
A
I
don't
know
mark.
If
you
remember
it's
one
of
the
two
osseocells,
but
I
don't
remember
if
it's
the
chi
or
the
new
york,
one
I'm
not
sure
which
which
one
maybe
we
can
send
an
email
towards
yourself,
I'm
not
sure
who's
the
contact
to
ask
them
or
could
we
measure
if
we
are
not
breaking
one
of
these
mirrors
because
of
the
daily
air
sync
doing
by
all
the
other
ones?.
B
Well
so
so
shouldn't
they
be
able
to
rsync
from
any
mirror.
They
should
be
able
to
rsync.
From
from
I
mean
it's,
it's
not
a.
They
are
truly
intended
to
be
mirrors
of
each
other,
so
all
we're
doing
is
latency,
so
either
of
them
is
fine
or
the
one
in
archives
that
jenkins
dot
io
or
the
one
in
singapore
or
not
singapore,
the
one
in
china
I
mean
any
of
them
should
be
viable,
as
mirrors
shouldn't.
They
that's
a
good
point.
B
Is
my
understanding
correct?
Well
I
mean
it,
it
does
introduce
latency
if
we
could
say
hey
our
sync
from
some
from
the
first
one
selected
and
for
me
either
of
the
two
at
osu
sl
is
are
are
quite
good,
so
I'm
not
I'm
not
worried
about
which
of
those
two
is
is
faster.
I
would
assume
they're
already
getting
lots
of
rsync
traffic
from
plenty
of
people.
Like
me,
one
more
rsync
consumer
is
probably
not
going
to
overload
them.
A
Nice
work:
we
will
have
two
test
cases
once
it's
deployed
on
release
and
infra
ci,
that
new
image
will
be
used
for
the
upcoming
weekly
release.
So
next
tuesday,
it's
important
to
have
this
in
mind.
That's
the
windows
server
curve,
that's
literally
the
same
image,
so
that
shouldn't
be
an
issue,
but
that's
the
first
step
and
for
c.I
jenkins
sayo
I
mean
we
have
only
have
to
be
careful
proposal.
Is:
are
you
okay?
A
A
D
A
Finally,
the
two
last
ones
ci
jenkins
sayo,
so
I've
published
the
note
from
the
postmortem
and
share
the
recording
link
between
the
four
five
of
us,
including
bazel.
So
I
need
a
review
from
everyone
before
publishing
it
and
closing
these
issues.
A
We
didn't
add
any
any
issue
on
cigarette
due
to
rate
limiting
so
right
now,
no
emergency,
that's
a
risk
that
still
exists
until
we
are
fully
unripe
limited.
A
A
C
C
A
So,
as
you
might
remember,
the
jenkins,
ci
and
chanting
sierra
engineered
forever
organization
under
the
hub
are
open
source
and
they
are
not
rate
limited.
So
I'm
I'm
writing
something
on
the
docker
open
source
program
issue.
I
will
put
it
on
the
next
iteration
our
end.
Users
are
not
api
right,
limiting
and
that's
a
good
thing,
and
that's
why
cijn
kinzario
is
safe
because
jenkins
see
identify
you
only
pull
images
in
jenkins,
yeah,
so
no
more
height
limit
for
these
images.
A
Since
10
days
roughly,
however,
our
account
is
still
facing
some
time
to
times
api
rate
limit
when
we
have
machines,
building
all
the
docker
image
for
the
jenkins
controller
or
agents,
because
they
they
build
from
official
docker
images,
which
are
api
rate
limits.
Most
of
the
bandwidth
so
makes
sense
for
docker
to
api
recommend
this.
A
A
D
A
C
B
B
4.13.1
is
an
exception
because
it
had
to
be
released
from
with
the
code
signing
and
therefore
had
to
be
done.
Untrusted,
and
so
the
change
was
surprisingly
easy.
It
worked
well,
but
if
someone
were
to
need
to
release
some
other
old
patch
version,
we
would
have
to
make
a
similar
change
there
and
then
it
needs
more
discussion.
B
A
Nice,
nice,
nice
now
about
the
afra
next
release
with
the
next
next
next.
So
I've
put
two
topics:
first,
one
the
caller
tools
metadata
generator.
So
he
understands
I'm
not
sure
my
knowledge
is
quite
limited,
but
it
sounds
like
that
that
job,
the
crawler
generate
a
bunch
of
files,
statics
files
push
somewhere
and
when
you
are
on
jenkins-
and
you
add
new
tools-
installation,
if
you
have
an
automatic
installer
that
plugin
used
the
files
to
configure
or
to
have
the
list
of
installer,
is
my
understanding,
correct.
Mark
your.
A
A
I
don't
remember
exactly
the
yeah
14th
of
june,
so
it's
not
emergency,
but
it's
important
and
there
is
a
kind
of
failsafe
mechanism
that
makes
that
job
failing
for
us,
so
good
thing
that
the
kind
of
notification,
but
we
need
to
rotate
that
so
I
propose
to
add
that
to
the
next
upcoming
release
and
we
have
to
ask
or
find
information
about
how
to
renew
that
one
between
team
danielle-
and
maybe
you
mark-
I
don't
know
if
you're
at
ease
with
that
part.
A
A
So
I
propose
to
add
that
one
for
the
upcoming
milestone,
if
it's
okay
for
everyone-
yes,
yes,
absolutely!
Is
there
someone
interested
or
can
I
pick
it
or.
C
A
A
A
Open
by
basil,
there
has
been
a
long
discussion
mainly
about
english
semantic.
Sorry,
it's
java
11
requirement
for
the
infrastructure
I
mentioned
it.
I
don't
think
there
are
action
for
us
right
now
sounds
like
they
are
on
the
right
on
whatever
direction
the
thing
for
us
infrastructure
is
to
follow
up
if
they
need
something
I
proposed.
We
keep
that
because
it
sounds
like
there
are
a
lot
of
different
ways
of
doing
that.
I'm
not
sure
that
basil
and
team
have
a
consensual
ideas
on
how
to
do
it.
A
A
B
A
Okay-
and
I
think
that
was
the
last
tournament,
so
we
already
have
a
pretty
packed
milestone.
I'm
doing
one
last
sanity
check
on
the
upcoming
to
see,
if
I
don't
forget,
we
clear
release
key
close
upgrade
to
gc
aws
all
night
sunday
back
burner,
so
it's
only
issues
that
are
involved.
I've
created
to
track
duplicate
tmg
in
favor
of
docker.
A
That's
the
discussion
that
one
is
an
easy
one
propose.
We
add
it
to
the
upcoming.
The
goal
is
to
build
using
docker
everywhere,
so
we
will
be
able
to
dump
emg
in
the
future.