►
From YouTube: App Runtime Deployments Working Group [July 13, 2023]
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
So
sharing
my
screen
so
then
welcome
everyone.
It's
been
some
time
since
the
last
meeting,
May
25th
Goods,
let's
go
over
the
items
from
that
meeting
cloud.
Configs
of
Bosch
deployment
project
are
outdated,
yeah
I
simply
opened
an
issue
and
yeah
bayham
promised
to
review
the
m
and
disk
types,
but
I
think
not
much
more
has
happened
since
then.
A
Okay,
just
haven't
checked
if
this
made
it
into
bubble,
but
I
guess
in
one
of
the
next
public
releases.
We
should
have
that
okay,
Bubble,
AWS
DNS,
set
up
I
think
that
one
was
simply
accepted
and
merged
so
that
fixed
the
AWS
Route
53
configuration
enter.
Your
will
works
for
our
experimental
environment,
all
fine
plan
patch
for
DNS
parent
Zone,
wiring
I
opened
and
no
that's
not.
It
opened
another
pull
request
for
bubble
here.
It
was
also
merged
and
I
think
we
are
already
using
it
as
it
is.
A
A
Great
fantastic,
so
if
we
have
not
yet
forgotten
any
other
resources,
then
the
migration
should
now
be
really
done
after
a
year
or
so.
Okay,
good
back
in
the
branch
protection
rules
problems
here.
This
is
all
green,
okay,
fine
good!
Then,
let's
go
over
the
today's
items.
A
A
So
there
is
nothing
more
to
do,
I
think.
So
let
me
close
write
something
here:
details
out,
maybe
yeah.
We
link
to
the
release.
C
C
So,
let's
open
integration
of
CEOs,
Linux
fs5.
A
A
A
A
B
We
we
don't
have
the
app
is
the
worst
part
so
like
we
have
a
zip.
We
have
like
a
tar
of.
We
have
a
jar
file.
Sorry
and
as
far
as
I
can
tell,
the
jar
file
was
built
out
of
a
repo
that
no
longer
exists,
so
there's
no
way
to
look
at
what
this
app
actually
does
and
why
it
might
be
failing
and
then
update
it.
B
Okay,
so
the
like
I
think
there's
a
couple
different
approaches
that
I've
thought
about
and
haven't
and
and
one
is
to
try
and
use
some
kind
of
like
jar
unpacker,
which
there
exists.
Some
tools,
I,
think
someone
told
me
the
legality
of
them
is
a
little
questionable,
but
it's
like
this
is
our
I.
Don't
I
don't
really
get
the
point.
B
It's
like
this
is
our
jar
I,
don't
know
how
there's
a
legality
issue
of
us
unpacking
the
jar,
but
we
could
unpack
the
jar
and
try
and
like
figure
out
what's
in
it,
we
could
trace
back
all
the
things
we
actually
care
about.
B
The
things
we
actually
use
this
app
for
and
just
build
a
new
app
or
we
could
try
and
find
like
this
app
is
based
off
of.
As
far
as
we
can
tell
it's
probably
just
a
simple
example:
app
for
spring
sleuth.
Now.
One
problem
is
that
spring
sleuth
itself
is
deprecated,
but
if
we
can
find
a
new
example
app
for
the
new
like
Zipkin
Library,
then
we
could
probably
just
use
that
with
like
a
one
or
two
changes
and
be
good.
B
But
if
you
all
have
better
ideas,
please
lay
it
on
me.
This
is
I've
like
I
traced,
through
a
bunch
of
old
tracker
stories,
to
like
figure
out.
Why
there's
no
repo
anymore?
That's
that's!
That's
kind
of
where
we're
at
seven
years
old
I
think
it
might
just
be
not
a
good
app
to
be
using
anymore
yeah.
A
B
I
mean
it
might
be
timeout
setting
stuff
but
I
as
far
as
I
can
tell
it's
pushing
the
app
that's
failing,
and
then
the
app
just
intermittently
like
fails
to
push,
was
what
I've
been
seeing
in
the
errors.
The
issue
has
an
example
of
it.
If
you
expand
the
thing,
I
tried
to
be
clever
and
use
that,
like
little
app
report
thing
at
the
bottom
to
create
like
a
fold
out
a
little
bit,
yeah.
A
B
Could
increase
the
timeout
and
see
if
that
fixes
it,
but
we
didn't
touch
those
timeouts
right,
so
I
I
figured.
It
was
something
that
was
changing
over
time
like
something
about
the
Java,
build
packs
interactions.
With
this
thing
that
was
changing
it,
but
yeah
it
could
just
be
as
simple
as
changing
the
build
pick,
although
there
is
a
larger
problem
with
this
thing
is
seven
years
old
and
it's
going
to
break
us
eventually
yeah,
but
if
we
can
fix
the
flakiness
with
a
simple
change,
maybe
we
should.
B
There
was
that,
and
there
was
the
credit
Hub
service
broker
and
I
think
I
fixed
the
credhub
service
broker,
because
that
was
just
a
go
out.
But
this
one
yeah
this
one's
harder.
A
A
Yeah
we
have
a
few
more
assets
where
it's
unclear,
so
I
think
I
also
created
some
binary
checked
it
in,
but
with
a
comment
how
to
reproduce
that?
Yes,
okay,
good
yeah.
So
if
you
have
time,
then
please
try
to
continue
our
investigate
further,
because.
C
C
Okay,
nothing
helps
we
can
also
disable
this
single
test
right,
maybe
there's
a
flag
for
it
and
then
yeah
Build
It
Up
from
scratch.
Basically,
this.
B
A
Is
a
good
question
yeah
why
this
is
so
lock
lines.
C
That
we
also
did
some
adoptions
in
the
cloud
controller,
to
have
the
headers
everywhere.
C
A
A
A
Are
really
supported
and
yeah,
we
adopted
our
log
passing
rules
as
sap
internally
to
make
sure
that
these
headers
are
set
yes,
okay,
good,
then
I
will
check
the
documentation
and.
A
Good
heads,
oh
yeah,
Cuts,
release
process.
So
after
quite
some
time,
I
created
a
new
heads
release
but
also
removes
CF
Linux
fs3
support.
That
is
as
a
stack.
You
can
only
specify
see
Linux
fs4
now,
which
is
also
the
default.
A
B
It's
just
I
just
follow
a
similar
flow
to
the
the
cfd
release,
usually
yeah
like
look
at
the
commits
to
determine
whether
this
is
a
major
or
minor
and
then
cut
the
release
and
then
create
a
and
then
create
the
like,
or
if
I
cut
the
release.
I
mean
run
the
release,
the
corresponding
release
job
and
then
create
the
release
in
GitHub.
A
A
This
nice
feature
and
draft
draft
is
safe
right
sure,
draft
Yeah
generate
release
notes.
So
that's
the
main
difference.
We
don't
have
a
concourse
job
doing
this.
We
are
using
the
GitHub
feature
and
then
yeah
adapting
the
nodes
a
little
bit.
Okay,
could
you
write
a
few
or
maybe
start
a
very
simple
wiki
page
and
just
try
to
a
few
lines.
B
A
Be
done
so
that
everyone
knows
where
to
find
the
instructions
and
okay
that
would
be
great
yep.
B
A
B
A
B
A
So
when
we
deploy
something
to
gcp,
the
with
bubble
bubble
contains
post
deployment
as
submodule
and
Bosch
deployment.
Gcp
Cloud
config
specifies
used
external
ephemeral,
IPS
true
as
default.
That
means
that
that
each
VM,
so
this
is
a
cloud
Foundry
deployment-
gets
an
external
IP.
A
A
So
I
created
this
small
pull
request
to
create,
allow
bubble
to
create
a
not
Gateway
in
gcp.
This
feature
was
likely
introduced
later
and
so
historically,
we
were
using
external
IP
addresses
and
you
have
tested
it.
It
works.
So
if
you
switch
off
external
IPS
in
Cloud
config
deploy
again
so
that
you
only
have
internal
IPS
at
the
nut
Gateway
with
like
this
here
and
then
outgoing
traffic
works
again.
So
I
guess
this
should
be
the
preferred
setup.
B
I'm,
not
quite
sure,
I
understand
this
change.
Is
it
I
get
the
not
every
VM
needs
an
external
IP
that
makes
sense
to
me.
We
want
to
call
Save.
I
would
have
thought
then
that
we
just
take
the
external
IP
off
of
several
gateways
and
have
them
only
do
internal
traffic?
B
But
what
is
the
Nats
Gateway
part
of
it?
Why
do
we
need
that.
A
Some
Cloud
Foundry
VMS
need
access
to
the
internet,
for
example,
to
download
build
packs.
The
Diego
cells
must
be
able
to
download
build
packs,
and
this
is,
if
you
remove
the
external
IPS.
This
does
not
work
I've
tested
and
that's
why
they
need
a
nut
Gateway
so
that
they
can
use
the
gateway
to
access
to
for
for
outgoing
traffic.
B
A
A
And
you
see
quite
a
lot
of
external
IPS:
okay,
these
are
from
CF
deployment
630,
oh
no,
sorry,
sorry,
external
332
and
if
you
would
check
in
use
by
well
I
cleaned
this
up
already,
but
there
are
always
a
few
that
are
often
and
likely
just
costing
money.
B
A
C
C
Yeah
yeah,
that's
actually
I.
Remember
we
had
for
our
gcp
Landscapes,
some
audio.
B
A
A
Yeah,
okay,
good,
so
this
will
then
hopefully
come
in
a
new
bubble
release
and
and
then
we
still
have
yeah.
First,
we
need
a
new
bubble
release
with
nut
Gateway,
and
then
we
can
I
should
not
forget
this
here.
The
Bosch
deployment
needs
to
be
updated,
so
here
just
for
information,
push
deployment,
Cloud
config-
and
here
we
have
this
ephemeral,
external
IP
Drew
setting,
which
automatically
assigns
external
IPS
to
every
VM.
A
I
started
this
small
pull
request
here
to
to
print
error
information.
So
just
again
for
the
context,
when
we
do
a
update
release
job
to
update
a
single
Bosch
release,
we
Bubble
Up,
deploy
Cloud
Foundry
and
then
run
this
ensure
API
healthy
job,
which
just
checks
that
the
cloud
controller
is
properly
responding.
A
There
is
not
much
useful
information
here,
because
the
neither
the
HTTP
status
code
nor
the
response
body
is
printed,
so
you
don't
know
why
you
are
CF
deployment
is
not
working
and
I
proposed
this
little
change
here.
Just
to
print
this
information
and
yeah,
it's
evolved
into
a
very
Lively
technical
discussion.
How
to
correctly
handle
defer
function
at
the
deferral
close.
The
third
closest
in
go
with
many
proposals.
How
this
could
be
done
and
not
so
this
is
already
some
weeks
old.
A
The
latest
proposal
was
something
with
Anonymous
function
and
the
close
inside
so
that
the
HTTP
stream
is
really
close,
but
there
were
quite
a
lot
of
other
suggestions.
How
to
to
solve
this,
so
yeah
I,
don't
know,
would
Carson.
Would
you
want
to
do
a
final
review
with
Dave?
If
this
now
needs
a
change
or
not
yeah.
B
A
B
A
B
C
C
So
the
idea
was
here
to
have
a
the
these
three
flavors
of
the
cloud
native
Jimmy
stack
delivered.
So
that's
a
cloud
native
build
Tech
idea
can
somehow
be
added
to
CF
deployment,
of
course,
as
an
experimental
Ops
file.
Etc.
First,
let's
see
how
that
works
out,
but
it's
still
an
heavy
discussion.
If
that
is
the
right
way
or
something
else
should
be
done.
C
A
C
That's
a
good
question:
that's
it
can
only
be
validated
using
the
cloud
native,
build
packs,
there's
also
a
discussion
whether
we
could
offer
the
cloud
native
build
packs,
also
on
CF
Linux
fs4.
That
would
make
it
easier
also
for
for
users,
because
those
texts,
you
know
that
need
to
be
delivered,
but
the
additional
Stacks
there
are
at
least
also
a
few
stripped
down
Stacks,
which
have
much
less
packages
and
are
then
more
secure,
Etc,
but
that
can
be
then
left
to
the
operator
yeah.
C
Yeah,
it
will
be
like
a
build
pack
tests
that
you
can
push
a
hello
world
use
the
stack,
and
this
is
native
build
pack,
and
that
should
work,
and
maybe
it's
also
enough
to
use
the
smallest
one,
because
the
bigger
one
is
just
of
additional
packages
but
yeah
yeah.
As
I
said,
I
guess,
the
cloud
native
build
pack
team
will
come
up
with
proposals.
What
what
makes
sense
to
test,
and
maybe
we
don't
need
the
full
Matrix
but
too
much.