►
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
Max
I
saw
that
you
updated
to
the
version
with
the
Mad
nuts.
All
change,
Do
You
observe
anything
interesting.
C
We
finally
did
it
and
currently
roll
it
out
on
our
test.
Sims.
D
C
The
systems
and
that's
working
fine
so
far
so
don't
see
any
issues
looks
good.
D
A
D
D
B
B
I
know
like
we
have
to
walk
talk
way
too
much
about
like
one
line
change.
F
Yeah,
this
is
just
where
Joseph
was
commenting
on
and
then
nothing
happened
anymore.
B
Yeah
I
know,
but
your
Constantine
is
currently
doing
NSX
training,
so
the
the
VMware
overlay
networking
technology
thing
so
he's
becoming
an
expert
on
that
and
that's
in
a
different
time
zone
as
in,
like
probably
San
Francisco
time
zone.
So
he's
he's
doing
really
odd
hours
at
this.
One
I
think
it's
a
week
or
something
but
yeah,
but
that's
why
he
hasn't
respondent.
B
But
the
problem
is
not
the
tool.
The
problem
is
the
limits
here
for
12
and.
B
You
pushed
yourself
for
the
limit,
so
let's
get
this
up
again.
D
B
B
Right
so
the
board
that
we
have
here
all
the
things
that
are
on
here
are
populated
with
that
sync
Joe.
So
this
is
basically
we
use
the
working
group
definitions
to
get
a
list
of
repositories
and
then
sync,
it
sync,
those
to
a
specific
project.
E
B
Yeah
because
we
also
use
some
custom
Fields
right,
so
we
have
a
set
of
Fields
here
that
are
non-standard
like
area
right.
So
we
want
to
know
what
the
area
is,
so
that
we
populate
and
the
last
activity,
so
the
date
that
the
last
comment
was
given.
Those
things.
E
B
F
B
B
E
B
F
F
Yeah,
you
know
that
now
I
have
a
warning
with
within
Concourse.
I
saw
that
like
they
have
a
warning
now
for
because
I
was
looking
at
the
new
Concourse
and
I
didn't
know,
I
have
a
warning
for
if
you're,
using
Guardian
instead
of
container
d,
Guardian
doesn't
work
on
gemi
stem
cells
currently
because
of
the
whole
C
group,
stuff,
V2
features
V1.
F
F
Basically,
Garden
yeah.
F
F
F
F
B
This,
the
one
that's
last
month.
F
D
E
B
So
it's
more
of
a
they
change,
tlip
C
and
that's
why
they
have
like,
because
it's
Dynamic
it's
trying
to
load
a
dynamic
Library.
That's
why
it's
having
an
issue
I
believe
so
I,
don't
believe
this
is
related
to.
B
But
I'm
like
everybody,
is
now
trying
to
to
get
to
work
with
this
right
and
then
changing.
This
would
be
a
I,
don't
know
quite
a
big
breaking
change
this
point
so
I'd
rather
not
do
it.
B
If
we,
if
we
wanted
to
this,
should
have
been
a
great
change
if
we
we're
still
in
Alpha
for
bionic
right,
but
at
this
point.
F
F
B
E
B
E
Yeah,
the
question
is:
wait,
wait.
Does
it
hurt
kubernetes
kubernetes
detects,
maybe
the
wrong
version?
Yes,.
F
So
I,
don't
know
what
this
this
just
slipped
through.
Basically,
we
we
should,
we
should
have
I,
should
have
check
my
to-do
before
we
did
a
ga
jme
release,
but
we.
D
F
B
F
E
F
F
Don't
like
it
like,
because
it's
for
debugging
purposes,
I
cannot
do
stuff
that
I
like
to
do
I
can
I
can
I,
cannot
start
the
agent
and
restart
the
agent
when
I,
when
I'm
on
the
Bosch
agent,
because
it
doesn't
allow
me
to
because
my
user
is
not
I.
I
should
then
go
to
the
yeah,
basically
go
into
the
basically
yeah
mess
up
with
the
c
groups
and
say
that
I
I
am
allowed
and
then
I
need
to
circumvent
all
this
crap.
B
F
F
Like
access
issues.
F
F
B
No
I
mean
so
the
amount
of
access
helper.
The
thing
it
does
is
it
locks
down
who
can
access
the
Monet
API
yeah.
F
So
this
yeah
gets
all
the
C
group
stuff
and
it
uses
C
group
a
V1
stuff,
and
if
we
fix
this,
then
basically
for
stem
cell
wise
it
shouldn't
matter
anymore.
Then
the
only
thing
is
because
I
don't
know
what
else
is
relying
reliant
on
C
group
one
because
she
C
group
V2,
is
by
default
on
Jimmy.
B
F
Well
then,
we
need
to
go
at
some
point.
We
need
to
move
to
to
a
two
and
then
just
make
V1
deprecated
the
line
two
to
one
that
one
addicts
and
then
we
go
to
two
directs
major
version
and
put
some
documentation
together.
Yeah
can.
E
We
be
probably
an
impact
on
the
docker
basharies,
which
has
already
broken
in
the
past,
maybe
related
to
similar
changes,
and
they
are.
They
are
a
bunch
of
Dockery
disease
or
Docker
jobs
around
in
several
in
several
Bush
releases.
F
F
F
I
mean
the
impact
I
think
we
could
just
say:
okay.
Well,
let's
say
in
February
or
something
we
go
to
it:
2.x
version.
We
maintain
the
1X
version
for
another
I,
don't
know
I.
B
Sure,
but
from
a
VMware
per
interview
like
we
like,
even
if
the
community
don't
want
to
support
it,
we
will
have
to
support
it
for
another,
like
probably
two
years
or
something
contractually.
E
E
Vmware
has
adopted
JJ
for
Pas
and
PKS
and
stuff
like
that
I
thought
you
were
stuck
on
on
scenario.
B
No,
no,
we
have
just
like
a
few
months.
A
month
ago,
I
guess
we
have
released
a
Jimmy
based
CF
or
CF,
offering
is
based
on
Germany
now,
but
I
mean
we
still
have
a
lot
of
customers
on
Xenia
based
stuff.
All
right.
E
Mean
so
the
point
is
about
upgrading
this
and
supporting
so
that
it
works
with
super
P2
instead
of
requiring
C
group
V1.
But.
D
F
D
B
D
F
It
refuses
to
look
up
the
proper,
proper
C
group
in
how
kubernetes
probably
doesn't
have
an
if
statement
that
like
if
it
doesn't
exist
here,
check
the
other
one
for
the
version.
F
Yeah
but
I
think
Reuben.
You
were
putting
way
too
much
giving
way
too
much
weight
on
this
thing
on
the
C
group
thing,
because
I
I
only
think
that
kubernetes
and
maybe
Diego
is,
is
maybe
having
some
requirements
on
it,
but
that
should
we
should
just
ask
so.
B
Bpm
also
depends
on
it,
so
I
already
did
that
research
like
the
things
I
could
think
of
like
these
are
the
things
I
could
think
of,
and
they
are
the
support.
So
I
looked
at
Ron
C,
we,
our
C
group
V2
in
round
C
right
so
when
they
started
supporting
that,
and
that
was
here
and
that's
not
that
old
right.
So
it's
not
like
it
has
been
there
for
since
forever.
F
F
D
A
Reason
but
yeah
I
think
if
we
want
to
switch,
we
need
to
have
enough
time
that
others
can.
A
A
A
A
B
So
my
understanding
was
that
we
were
doing
that
and
that
was
forcing
V2,
but
maybe
I'm
misunderstanding
so
yeah.
Some
additional
research
would
be
great.
A
D
B
Yeah,
thanks
for
the
discussion,
I
will
do
that
and
I
also
look
into
that
same
job,
which
is
still
not
working
but
not
now,
but
they
did.
D
B
Okay,
shall
we
then
just
go
continue
with
this
burning.
E
F
B
Oh
I
I
remember
they
so
I
think
it's
the
White
House,
who
has
like
some
mandate
about
like
one
thing,
these
IPv6
everywhere,
but
the
everywhere
bit
is
a
bit
I
mean
up
for
discussion
like
what
does
everywhere
mean
right
and
so
I
think.
The
current
understanding
is
that
it's
at
the
like
until
the
loadback.
Basically,
it
ends
at
the
load
balancer.
So
if
your
load,
balancer
can
be
do
argue,
V6,
it's
fine
to
be
doing
ipv
or
internally
right
on
your
VPC.
It
doesn't
make
sense
to
the
ipp6.
B
B
Yeah
I
understand
I,
know,
but
I
mean,
like
the
reason
why
people
even
cared
about
this
was
because
of
that
the
whole
thing
from
The
Americans,
where
they
made
up
a
thing
guidelines
that
got
everybody
scared.
A
F
B
B
B
F
F
B
F
A
B
All
right
yeah
that
that's
a
lot
cleaner,
wow
I,
don't
even
have
to
scroll.
Now
we
can
have
everything
in
one
View.
B
Sure
we
still
have
that
proposal
for
a
common
steel
Bots,
but
I
haven't
done
that.
A
When
the
pop
store
is
not
accessible,
yeah.
F
I
think
you
need
to
mention
Matias,
because
he
worked
on
on
these
signed
URL
stuff.
Let.
B
F
Can
you
just
take
Matthias
if
he
or
or
we
can
just
max,
we
can
just
say
tomorrow.
F
F
D
B
Yeah,
except
for
this
person,
infinitely
bump
it,
but
it
seems
like
this
person
has
one
from
the
Bosch
admin
box,
which
happened
not
has
given
up.
F
F
Really
control.
B
E
B
A
B
B
B
C
Maybe
short
question
after
we
emerge
now,
they're,
not
strange.
We
in
we
also
checked
the
new
release
with
with
C
link,
and
we
tried
it
out
on
our
Devlin
systems
and
on
some
Posh
instances
currently
failing,
because
the
the
start
takes
too
long
at
first
we
invest
Ramon
and
I
investigated
it
already
a
little
bit
at
first.
We
saw
it's,
maybe
in
a
resource
issue
that
we
not
have
enough
capacity,
but
we
scaled
up
and
saw
the
same
issue
on
the
same
Bosch
director
again.
C
C
We
saw
it
on
different,
yes
providers
already,
but
yeah
I
don't
find
why.
B
E
We've
had
similar
problems
when
upgrading
cost
per
se
sessions.
It
was
blocked
because
the
the
postgres
was
improper
not
properly
shut
down
before
and
when
restarting
it
progress
was
saying.
Oh
I
wasn't
shut
down
properly,
so
I'm
not
going
to
to
start
up
so
easily
you,
you
should
check
the
the
that
consistency
and
stuff
before
I
can
properly
start
up
again.
E
B
F
I
I
think
it's
an
because
we
see
that
a
lot
of
we
see
that
in
the
in
the
resources
that
it
uses,
that
is
100
right.
It's.
C
F
E
B
C
I
know:
that's
that's
not
the
issue.
We
we
currently
yeah
comparing
the
systems
where
it
works
and
the
system
where
we
see
this
issue,
but
currently
it's
but
it's
it's
stable.
So
if
we
have
it
on
the
landscape
or
for
a
Bosch
director,
then
it
will,
of
course,
every
time
we
try
to
update
it.
It's
not
a
temporary
thing.
It's
really,
but
it's
only
happened
on
some
of
our
Bosch
directors.
After
that
we
see
that
the
performance
improves
a
lot,
so
CPU
usage
goes
down
and
everything
works
smooth,
but
yeah
on
some
directors.
We.
B
C
That
yeah
we
updated
in
Concourse
so
and
after
time
it
types
out
then
The
Concourse
tries
again
three
times
and
every
time
it's
failed.
So
if
it's
restart
the
process
and
again
it
failed
and
after
the
three
times
our
job
is
read
and
then
we
connected
and
saw
the
the
the
last
try.
The
did
we
understand
and
available
after
some
minutes,
but
yeah
The,
Concourse
drop
was
already
red.
F
B
Yeah,
but
every
time
you
keep
doing
the
Bosch
recreate
or
create
VM
it
takes
the
15
minutes
yeah,
so
it
I
I
was
wondering.
Is
it
something
like
in
the
postgres
database
that
it
needs
to
like?
Is
it
some
data
thing?
It
doesn't
need
to
get
through
that
and
then
after
it
gets
through,
that
it's
stable
or
is
it
and
maybe
like.
B
C
C
C
The
Bosch
version
for
our
service
for
Brick
deployment
yeah
but
yeah
currently
we're
comparing
what
is
the
difference
but
yeah.
Maybe
you
have
an
idea
well.
C
Very
very
strange
and
not
clear
what
happens
there.
C
276
sixes
the
last
version,
this
version
or
the
version
before
so
yeah.
F
D
D
C
B
B
Well,
yeah,
what
I
would
do
is
try
to.
If
you
have
an
environment
where
it's
reproducible
you
could
use
just
do
a
brush
create
end
and
try
to
ssh
in
Wild
Bosch,
create
anth
is
still
going
on
right
to
see
is
like
to
check
if
postgres
is
accessible.
Those
types
of
things.
C
Yeah
yeah:
we
must
test
it
again
and
find
it
out,
but
yeah,
it's
strange
but
I
think
it's
not
accessible
because
we
saw
analogs
that
it
started.
15
minutes
after
the
deploy
started.
B
D
B
Is
that
a
machine,
or
some
in
total,
the
machine
in
total
right?
So
it
could
be
that
doesn't
the
Ruby
process
is
taking
so
like
I
mean
I,
don't
even
know
if
it's
possible
but
say
like
the
c-line
Ruby
watch
directors
they
consuming
all
the
available
CPU
and
the
postgres
is
not
getting
any
CPU
and
the
Ruby
process
without
that
CPU
is
just
retrying
postgres
all
the
time
right.
So
it's
not
getting
anywhere,
but
it
does
also
doesn't
leave
any
like
CPU
cycles
for
the
postgres
process.