►
From YouTube: INFRA Weekly Meeting 2020 03 03
Description
Jenkins Infrastructure Project Meeting - 2020-03-03
Notes - http://bit.ly/2T0oZ9v
A
A
This
is
something
that
we
should
do
more
systematically
because
it's
quite
easy
to
upgrade
to
the
same
version:
I'm
a
major
version
but
yeah.
That's
that
we've
basically
were
affected
by
security
issues,
but
now
it's
fixed
and
otherwise
accepted.
That's
I
think
we
can
just
look
at
for
each
the
peaks.
So
the
first
one
is
the
IBM
infrastructure
Jim.
Do
you
want
to.
B
B
B
2018
and
and
I
think
they
still
supports
power,
but
in
a
limited
capacity,
as
it
looks
like
it
only
applies
to
Ubuntu.
1604
does
not
help
us,
since
the
image
that
you
guys
got
for
power
is
Ubuntu
1804,
which
is
lovely,
so
I
guess.
The
discussion
we
need
to
have
is
how
we're
gonna
proceed
with
managing
the
configuration
management.
Basically
on
that
machine.
I
know
briefly
in
the
email
you
guys
mentioned,
maybe
wanting
to
use
and
before
it
and
she
kind
of
address
any
of
the
concerns
ants
will
does
work
fine
on
s/390
and
people.
B
You
see
that's
what
we
use
to
manage
all
our
infrastructure
over
here,
but
puppet
does
not.
So
how
do
you
guys
want
to
kind
of
proceed
with
that,
since
we
could
port
puppet,
but
that
will
require
a
lot
of
additional
work
and
might
not
be
one's
been
sustainable
in
terms
of
like,
if
you
guys
need
to
update
your
main
puppet
master,
then
it
might
fall
out
of
sync
I.
Don't
really
use
puppet
that
much
so
I
can't
really
speak
to
all
the
Enzo
now,
but
I
know
that
it
will
require
a
great
deal
of
work.
B
A
So
the
reason
why
I
mentioned
using
Pathet
was
because
we
already
have
the
puppet
code
to
configure
the
Jenkins
agents,
but
in
the
end
the
idea
is
just
to
simplify
the
management
of
those
machines.
If
puppet
is
not
correctly
supported,
I'm
totally
fine
to
use
ansible
or
any
other
tools,
and
the
thing
is,
we
just
need
to
create
a
new
git
repository,
for
example,
if
we
decide
to
use
ansible
for
that,
we're
going
to
create
a
new
get
repository
with
the
unseeable
code
used
to
to
configure
those
machines.
A
So
I
think
mark
is
doing
some
testing
right
now
with
those
infrastructure.
So
I
think
we
can,
because
it
does
not
I
mean
we
don't
have
a
lot
of
configuration
for
those
roles.
So
it
should
be
really
easy
to
put
that
in
place,
but
yeah
I'm,
just
wondering
if
mark
you
are
working
on
that.
If
you
Mark
you're
familiar
with
ansible
or
not
at
all,
because
I
have
no.
C
A
Absolutely
so
yeah
I
did
a
lot
of
unstable
code
three
years
in
the
past,
so
if
you
can
at
least
work
on
the
scripts,
if
you
can
at
least
work
on
a
script
that
we
can
use,
so
we
can
first
configure
those
machine
and
then
once
I
have
some
times,
I
will
I
will
write
unstable
codes.
So
we
can
even
if
it's
needed,
we
can
redeploy
those
machine
in
the
future
and
can
reconfigure
those
machine
in
the
future.
B
I'm
all
for
configuration,
management,
I,
definitely
know
the
benefits
and
I
applaud
you
guys
for
even
doing
it,
because
it's
really
awesome
and
I
think
well.
Sooner
than
later,
we'll
also
see
the
issues
with
all
right.
We'll
see
the
use
case
for
having
this
kind
of
ansible
code
is
you
know
the
the
power
PVC
server
yeah.
We
gave
you
guys
that
isn't
the
long-term
solution,
that's
just
a
temporary
server
for
you,
guys
and
I.
B
Think
I
have
a
talk
on
Friday
of
going
to
legal
to
get
that
terms
of
sheep
terms
of
use
sheet
for
you
guys
for
PVC
I.
Have
you
guys,
son
off
of
that
cuz?
You
did
sign
off
on
the
Linux
one,
but
we'll
need
to
have
you
guys
sign
off
on
the
power
one?
Okay,
so
they'll
be
perfect.
If
we
develop
some
sort
of
ansible
playbooks
and
then
we're
able
just
to
snap
your
fingers
redeploy
all
the
ants
will
play
books
on
this
new
server.
B
A
B
Yeah
I
mean
we
have
experience
with
getting
puppet.
The
kind
of
work
did
a
couple
clients
we're
interested
in
puppet,
but
the
big
problem
is
the
dependency
kind
of
hole.
You
kind
of
go
down
into
puppet
is
a
colossal
I'm,
not
saying
Ansel
isn't,
but
it's
it's.
We
we
looked
at
it
and
we
started
working
with
it,
but
it
requires
to
go
to
like
pretty
much
every
open
source
community
Under
the
Sun
and
be
like
hey.
Can
you
guys
start
producing?
C
B
A
B
And
we
might
be
able
to
I,
don't
know
how
good
the
ansible
scripts
are.
I
haven't
personally
looked
at
them.
We
might
be
able
to
actually
use
the
adopts
open,
JDK
ansible
scripts,
because
I
think
they
have
to
manage
their
infrastructure,
the
Jenkins
infrastructure
they
use
ansible
to
reconfigure.
You
know
you
know
workers
and
stuff
like
that,
so
they
might
actually
have
some
Ansel
playbooks
and
roles
that
we
might
be
able
to
utilize
for
installing
the
tops
you
know
do
all
that
good
stuff.
B
C
Yeah
and
and
I've
got
swell
you've
been
talking,
I've
been
compiling
and
I've
seen
evidence
to
support
exactly
what
you
said
Jim.
So
it
looks
like
the
most
compelling
thing
to
use
on.
Z
is
open
j9
and
it
feels
dramatically
faster
than
either
adopt
open
JDK
with
hotspot
or
the
okay,
that's
bundled
with
Ubuntu
on
Z.
So
so
it's
pretty
simple.
In
this
case
she
was
open,
j9
I'll
run
it
once
or
a
bunch
more
tests,
but
the
execution
performance
is
visibly
and
dramatically
different.
Using
open,
j9,
yeah.
B
And
there's
actually
issue
I
linked
you
to
on
adopts
github
page
where
they
kind
of
go
over
I.
Think
someone
actually
ran
it's
a
similar
aspect
of
you.
They
were
using
open,
adopt
JDK,
just
clean
hot
spot
and
with
no
JIT
the
JIT
is
just
in
time.
Compiler
pains
what's
happening.
We
explain
the
slowdown
issue
that
you're
experiencing
is
the
Java
8
from
Oracle
is
not
shipped
with
the
JIT
compiler.
B
But
this
is
the
exact
problem.
I
guess
you
know
I
originally
came
to
you
guys
to
solve,
is
getting
you
guys,
your
doctor
images,
switching
from
open
JDK
to
adopt
open
JDK,
because
this
is
like
all
my
Z
friends
and
IBM
co-workers
when
they
go
to
compile
your
docker
repositories,
they
spin
up
Jenkins,
it
works,
but
then
it
just
terribly
sluggish
and
slow
and
like
it's
not
Jenkins,
Jenkins
is
falling.
It
works
very
well.
C
So,
just
to
be
clear,
I
didn't
see,
visibly
different
performance
from
adopt
versus
Oracle
versus
open
JDK
as
bundled
with
Ubuntu
I.
Don't
know
if
that's
Oracle's
or
not,
but
open
JDK
is
bundled
with
Ubuntu
on
s/390
feels
now.
I
haven't
done
precise
benchmarks,
but
my
perception
was:
it's
not
dramatically
faster,
whereas
if
I
use
open
j9,
it
is
dramatically
faster,
no
I!
Yes,
yes
got
some
test
failures
that
hint
that
open,
Jana
and
Jana
and
may
have
have
things
that
need
more
investigation
as
well,
but
but
yeah.
B
It's
definitely
not
perfect,
yeah
yeah
I
know.
In
the
past,
people
ran
issues
with
the
the
bundled
JD
case
they
come
with
canonical
or
even
rail
or
stuff.
Like
that,
the
doctor
official
repo
someone
raised
the
issue
in.
Hence
why
we
don't
see
Alpine,
we
don't
see
other
kind
of
base
distributions
in
the
adopt
official
image
right
now
is
because
they
were
pulling
from
originally
they
were
pulling
from
and
also
I
think
Oracle.
B
This
is
why
open
JDK
official
image
doesn't
support
s/390
rain,
the
other
ones
anymore,
is
because
they
were
pulling
from
Canonical's
or
you
know.
Basically,
you
know
Ubuntu
is
built
binaries,
which
the
official
image
team
didn't
feel
comfortable
with,
because
they
don't
know
100%
what
canonical
did
change
with
it,
so
they
want
to
basically
keep
propagating
that
out
to
all
their
users
right
yeah.
B
A
B
C
A
A
C
A
But
usually
when
we
decide
to
upgrade
see
I,
don't
think
you
know
it's
either,
because
there
is
a
new
is
available
for
security
reason
whatever,
but
regarding
the
plugins,
it's
usually
like,
if
you
want
to
plug
in
just
think
just
think
with
Danielle
or
if
you
know
that
we
needs,
we
need
to
either
Jake.
You
stay
of
course,
basic
reason,
because
we
know
that
we
want
to
test.
A
You
know
whatever
it's
usually
best
to
just
ask
if
you
can
do
it,
but
most
of
the
time,
if
you
know
that
you
have
enough
time
to
these
issues,
then
just
under
imaginary
business.
The
Jenkinson
project
is
more
like
a
Vesta
course.
So
if
you
have
the
time
to
fix
something,
just
fix
it,
but
that's
really
how
I
work
if
I
can
plan
something,
I've
learned,
planets
and
otherwise
I
just.
A
C
A
The
best
way,
because
if
nobody
complains
about
that's
yeah,
just
just
a
grid,
the
system
I
mean
it's
way
better,
to
have
every
everything
always
up-to-date,
then
just
fear
and
to
break
things.
So
yeah
next
topic
is
regarding
the
backer
image,
so
Tim
job,
which
is
not
here
today,
so
Tim
Jacob
work
on
backer
images
for
Sierra
drink
is
at
I/o.
So
right
now
we
are
just
generating
open
image.
A
The
good
thing
is
it
speed
up
the
process
Lots
because
which,
once
once
the
carry
me
once
the
the
filter
machine
started
it's
already
ready
to
to
work.
We
still
have
to.
We
still
have
to
three
control
the
process.
It
seems
like
each
time
we
changed
the
image.
We
have
to
update
the
strategy
to
that
IO
configuration,
which
is
that
Sri
convenience,
basically
iin
abled
those
images
last
Friday.
Something
like
that.
So
that's
why
we
had
issues
over
the
weekend.
A
We
see
a
detective
that
I
own
another
change
that
deeds
regarding
see
other
changes
that
IO
was
to
update
the
credentials.
So
in
the
past
we
had
one
user
who
had
owner
access
to
the
azure
accounts,
and
so
now
I
just
changed
that
to
have
contribute
or
access.
So
we
can
just
manage
resources,
but
we
cannot
access
the
resource
themselves
and
the
next
time
that
I
work
on
permission,
I
would
just
run,
reduce
so
I'm
sure.
That's
credentials,
configure
and
see
other
changes
that
you
only
have
access
to
specific
things.
A
Instead
of
having
access
to
the
to
the
wool
accounts.
But
yeah
I
did
some
work
on
the
permission,
management
ins
on
their
accounts
and
the
other
thing
that
I
also
did
is
I
started
working
on
groups.
So
the
idea
is
to
have
some
immediately
see
if
I
can
share
my
screen
with
you
recording.
C
So,
while
you're
doing
that,
Olivia
I
was
more
concerned
about
the
making
sure
that
we
understood
what
happened
that
caused
it.
So
it's
sounds
like
you
made
a
switch
to
Packer.
The
switch
to
Packer
had
positive
results
in
the
things
start
faster
now
they
start
cleaner
because
we've
got
more
initiation,
initialization
done
in
the
in
the
virtual
machine
and
that's
great
we
were.
There
was
a
an
error
in
the
docker
compose
installation,
a
mixing
between
docker,
calm
and
others.
C
A
Serene
so
the
the
change
I
did
regarding
the
Packer
images,
the
way
CID
changes
that
I
yo
was
configured
and
fast.
It
was
just
each
time
we
need
a
new
virtual
machine.
We
use
default
into
image
and
run
scripts,
and
in
that
scripts
we
install
docker.
We
install
all
the
things
that
we
needed,
so
we
just
have
test
scripts
and
know
that
script
is
executed
directly
from
the
Packer
image.
A
So
once
we
start
instead
of
using
the
default
window
image,
we
used
the
Packer
image
generated
on
CID
Jenkins
at
I/o,
and
so
everything
is
up
and
running.
So
it
does
not
mean
the
doctor.
The
doctor
compost
issue
is
may
be
related
to
the
Packer
because
we
are
maybe
not
using
the
same
image
but
yeah.
It's
not
related
to
the
work
that
I
did
last
week.
A
Let's
see
my
screen,
yes,
so
basically
what
I
did
is
I
started,
I
created
at
the
moment
two
different
groups,
one
for
with
special
permission,
and
so
every
person
in
that
group
can
read
the
resource
group
that
contained
a
image
and
I
created.
A
second
group
was
for
two
big
communities,
and
that
is
if
someone
is
in
that
group
that
person
can
also
access
the
resource
group
that
contained
the
communities
cluster.
A
A
That's
something
that
I
would
like
to
see
more
election
in
the
coming
weeks,
but
I
still
need
more
testing.
To
be
sure
that
I
mean
it's
tedious
who
have
any
question
regarding
this.
E
A
So
this
normally
should
be
removed.
It
was
just
a
workaround.
So
if
you
look
at
the
scripts
used
but
pakora,
it
did
install
a
bunch
of
things
and
then
remove
the
user
Jenkins.
And
so
what
happened
when
at
the
first
iteration,
we
were
not
able
to
use
those
parker
images
because
we
didn't
have
the
right
permissions.
So
basically
the
scripts
that
I
configure
the
last
two
equations
to
say
ensure
that
the
Jenkins
user
is
there
and
just
put
the
right
permission
and
Norman
Norman.
A
Now
it
should
be
fixed,
but
because
because
because
the
Packer
images
is
generated
from
scenes
that
I
know
if
she
I,
don't
think
you
that
you
cannot
provision
machines,
then
we
cannot
generate
your
putter
image.
You
see
the
gotcha,
that's
why
we
do
yeah,
but
normally
normally.
Normally
we
should
be
able
to
remove
this.
It
has
been
fixed
last
Friday,
okay,
cool.
A
Yeah,
let's
continue
so
regarding
the
Packer
issues,
so
yeah,
as
I
mentioned
regarding
vector
images
as
I
mentioned,
it
would
be
nice
to
have
Windows
image
as
well.
The
main
reason
to
this
is
because
yeah,
when
you
want
to
be
the
Windows
machine
are
started,
it
take
quite
a
lot
of
time.
The
thing
is,
if
you
have
some
time
to
look
at
it,
it
would
be
nice
I
think
yeah.
A
E
C
A
A
Then
so
I
can
check.
The
good
thing
is:
if
the
user
certificate
is
not
working,
it
will
be
automatically
generated,
so
I'm
not
concerned
about
that
I
have
to
check
if
it's
the
right
certificates,
the
reason
I
mean
so
basically
what
we
are
using
a
tool
called
cert
manager
to
generate
the
certificates,
and
so
each
time
you
go
on
one
of
the
websites
are
running
on
communities.
If
we
have
a
valid
certificate,
if
there's
nothing
was
generating
new
certain
traits.
Okay,.
C
A
F
A
C
E
D
C
F
A
I
would
just
these
are
motion
screw
this
one.
So
basically
it
each
time
so
there
is
mega.
So
you
just
go
to
the
resource
group,
so
just
search
for
a
state
worker
working
from
yes,
it's
here.
So
if
you
search
tracker
there
is
a
group
called
Packer
images
and
inside
you
have
multiple
images,
and
so
basically
you
just
need
to
use
the
latest
one
which
is
in
this
case.
So
there
is
a
times
time.
So
this
one
seems
to
be
the
latest
one,
and
so
you
have
an
IDE.
A
Will
not
begin
now,
but
you
just
have
to
go
to
the
cloud
configuration
and
then
you
can
update
the
ID
so
the
next
time
the
virtual
machine
is
provision.
It
will
use
a
new
Packer
image
so
something
that
happened.
That
may
happen.
If
you
know
that's
one.
One
future
machine
is
totally
broken
you
you
can
try
to
for
speed
it.
So
that's
something
that
I
did
last
weekend.
So
you
go
to
virtual
machines.
You
have
to
use
the
right
resource
group
so
either
you
look
in
the
sky.
A
Agents
lean
so
agent
three,
so
this
is
the
resource
group
used
for
the
CID
Jenkins,
that
I
use
drum
machines,
and
so
you
have
a
list
of
machines
here
and,
as
you
can
see,
we
are
creating
or
right
now
so
it's
in
the
status.
But
if
you
know
that
you
changed
the
biker
image
and
you
really
want
to
use
those
biker
image,
something
that
I
do
is
I
just
look
and
see
either
Jenkins
at
I/o
and
if
I
see
knows
that
are
not
used.
A
I
just
delete
those
nodes
from
here
on
the
edge,
so
I'm
sure
that
the
next
time
I'd
need
a
new
virtual
machine.
It
would
provision
anyone,
so
that's,
gradual
about
a
week
ends
so
first.
First
updates
that
I
you
with
the
right
resource
ID
and
then
ensure
that
you
don't
have
machine
available
too
and
so
did
all
old
machines.
And
then
our
Sierra
drinking's
will
create
new
machines,
and
does
that
answer
your
question
does.
Thank
you.
Yeah
awesome!