►
From YouTube: App Runtime Deployments Working Group [August 11, 2022]
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).
B
A
I
have
a
chat
with
ruben
scheduled
for
next
week,
just
to
talk
about
it,
so
I
guess
I'll
hear
more
about
what
the
tlc
is.
Thinking
from
that
and
we'll
figure
out
yeah,
I
don't
know
if
you
want
to
you're
on
vacation
custom.
That's
fine,
but
yeah,
we'll
see
what
what
comes
of
that
and
I'll
be
put
back
at
the
next
meeting,
yep
sure
yeah,
I
don't
know
I
I'm
still
very
hesitant
to
commit
to
this
working
group
taking
it
on.
B
Okay,
then,
next
next
meeting-
I
won't
be
here
but
john-
is
back
so
all
fine
good
other
updates
from
the
toc.
What
is
now
available
are
these
reviewers
groups
and
you
can
also
have
bots
per
working
group
area.
I
mean
we
have
don't
have
so
many
working
group
areas
yet
so
it's
maybe
not
that
important,
but
these
features
are
now
available
and
the
sc
should.
I
call
it-
doubles
by
cpr
now
open
to
really
remove
to
not
just
talk
about
removing
non-standard
teams
but
to
remove
the
non-standard
teams.
A
B
It
can
be
added
no
problem
that
can
be
then
also
done
on
the
fast
track.
I
guess
other
teams
will
have
similar
issues.
B
Yeah
and
then
there
was
a
general
question
regarding
botsw.
We
do
have
now
a
means
to
assign
existing
bot
users
to
the
github
teams,
and
then
they
have
the
necessary
rights
on
the
repos.
But
there
is
a
little
bit
information
lacking
about
how
should
bots
be
handled,
who
should
decide
whether
what
is
used
or
not?
B
Where
should
the
credentials
be
stored
of
the
spot
and
who
has
access
to
that
many
open
questions
and
there's
one
issue:
386
on
the
community
repo,
where
eric
actually
raised
the
number
of
questions
and
asks
the
different
working
groups
yeah
for
feedback
for
requirements,
so
that
we
can
come
here
to
a
let's
say:
recommended
management
of
bots.
So
I
don't
know
a
private
repo
or
setup
of
a
concourse
or
whatever
something
needs
to
come
up
so
that
the
credentials
are
not
hidden
and
that
yeah,
okay,
better
managed.
B
Okay,
yeah,
that
was
it
from
the
toc
pipeline
migration
yeah.
What
I
did
is
I
created
this
shortened
subdomain
so
that
let's
say
his
work
is
now
hopefully
unblocked.
Yeah.
A
A
Yeah,
it's
annoying
the
it's
the
common
name
of
the
certificates,
that's
causing
the
problem,
because
dns
names
could
be
253,
I
believe
or
255..
But
the
common
names
can
only
be
64.
and
unfortunately,
we
use
the
dns
name
as
the
common
name
in
a
lot
of
the
certificates
in
cpr.
A
B
C
A
B
B
C
B
B
A
Yeah
yeah,
that's
an
interesting
one:
we've
we've,
never
historic,
I
mean.
Historically,
we
don't
once
we've
moved
forward
on
something
whether
it
be
a
a
bash
release
version
or
a
stem
cell.
We
don't
generally
tend
to
keep
testing
with
anything
older.
That's
not
to
say
we
can't
do
it.
It
would
be
basically
the
same
as
the
the
jamie
stem
cell.
We
have
now.
A
I
think
carson
and
I
did
use
there's
an
internal
vmware
pool
of
cf
deployments
that
we
we
used
for
that
just
because
it
was
expedient.
We
didn't
have
to
stand
up
a
bosch
director.
So
if
we
wanted
to
keep
this
around
long
term
and
have
it
in
the
working
group,
we'd
probably
have
to
stand
up
a
new
bosch
director.
Instead.
A
Because
it
would
be
hard
to
change
the
the
main
pipeline
I
mean
one
thing:
is
I
don't
know
that
we
were
planning
on
having
an
ops
file
that
lets.
You
revert
back
to
bionic
now
that
if
we,
if
we
did
ga
with
with
jeremy.
B
A
So
yeah,
I
don't
know,
I
mean
that's
something
we
can.
We
can
look
at,
it's
definitely
more
work
and,
like
I
said
historically
the
the
we
haven't.
Okay,
we
have
not.
We
haven't
done
that.
We
didn't
do
that
with
zenio
and
we
didn't
do
that
recently
with
bionic
once
we
tested
it
and
said
yes,
this
works.
We
just
move
forward
so
that,
like
I
said,
that's
not
to
say
that
we
can't
do
it
if
the
need
is
high,
I'm
just
not
sure.
B
A
Yeah
yeah,
we
were
definitely
behind
on
bionic,
but
I
remember
xeno.
When
I
first
joined
release
integration,
we
didn't
you
know
we
were
always
forward.
Looking
we
didn't.
B
A
B
C
A
B
A
B
A
Cell
is
the
lunatic
stem
cell.
I
I
don't
have
a
good
historical
model
of
how
long
previous
stem
cells
were
overlapped,
so
that
okay.
A
B
The
bosch
I
could
imagine
that
they
will
do
it
until
april
next
year,
so
as
long
as
there's
a
regular
maintenance
window
for
bionic
after
that,
obviously
not
anymore,
but
the
earliest
point
in
time,
from
our
point
of
view,
would
be
when
all
let's
say
bosch
deployments
are
migrated
before
that
they
they
can't
and
they
wouldn't.
I
mean,
I
think
the
stem
cell
production
is
basically
in
our
hands
sap
hand.
B
B
Yeah
we
can
discuss
with
your
home,
but
then
maybe
we
make
here
some
compromises.
I
thought
more
or
less
it's
applying
an
ops
file
if
we
have
an
ops
file
or
writing
one
for
switching
back
to
bionic,
I
mean
that's
something:
that's
not
too
much
effort
and
then
apply
it
in
one
environment
and
that's
it.
But
if
it's
more
well.
A
I
guess
my
concern
was
doing
that
in
the
main
pipeline
would
be.
You
know
we
have
all
these
different
test
scenarios
for
refresh
and
upgrade,
and
the
different
ops
files
that
they're
testing
and,
if
we're
going
to
have
jammy
as
the
default
stamp
cell.
I'd
want
all
of
those
test
scenarios
to
be
testing.
Jeremy.
A
B
C
B
Who
knows
if
something
comes
up
with
jamie
stem
cell
and
c
of
linux,
fs3.
A
A
They
seem
to
have
handled
that
compatibility
quite
well,
so
I
think
we're
okay
there.
But,
yes,
you
never
know
what
changes
are
going
to
come
through
and
I
guess
the
big
one
would
be
cf
linux
fs4
on
bionic,
but
maybe
they're
they're
they're
just
not
expecting
that
to
work,
and
that's
is
oh.
You
have
to
have
the
jamie
stem
cell
to
use
that
yeah.
B
Least
of
a
migration
path,
where
you
don't
need
it,
it
would
be
sufficient
to
have
first
gemmy
and
c
of
limits
fs3
running,
and
then
we
need
to
switch
from
cf
linux
3
to
4,
but
on
one
stem
cell
of
course
yeah,
so
that
so
our
plan
would
be
as
soon
as
we
can
manage
it.
We
would
bring
jimmy
outside.
So
this,
even
if
cf
deployment
runs
on
jammy,
it
doesn't
necessarily
mean
that
all
our
additional
stuff
and
configuration
and
services
run.
That
has
to
be
then
checked.
C
B
Our
problem
is
that
we
need
to
be
on
the
latest
cf
deployment
version
and
that's
currently
stopped
because
of
early
cloud.
That's
but
okay,
that's
our
internal
problem
through
the
door.
We
will
do
that
yeah.
A
B
C
B
Let's
keep
it
open,
I
also
hand
it
over
to
johan
to
think
about
it,
but
if
it's
in
high
effort,
then
maybe
it's
more
important
to
go
on
with
the
migration
and
yeah
look
into
the
future
instead
of.
A
Yeah
we
can
plan
for
that
next
time.
I
definitely
would
like
sven
and
and
your
home
to
be
involved
rather
than.
B
C
A
Whether
we've
got
the
pipelines
migrated
first,
I
don't
know
but
we'll
see
how
that
goes,
but
I
think
it
should
be
relatively
straightforward.
We've
got
all
the
pieces
in
place,
so
the
automation
will
take
care
of
a
lot
of
it
for
us.
A
No,
I
think,
we're
I
think,
we're
good
carson's
going
to
be
out
so
yeah
I'll
be
available
to
help
with
the
with
the
pipeline
migration
as
as
needed
and
we'll
see
how
we
go.
A
C
Does
that
also
mean
we
gonna
migrate,
the
other
environment,
so
they
run
on
this
google
cloud
account
or.
A
And
that's
that's
an
open
question.
I
think
we're
we're
focusing
on
the
pipelines
first
and
then
we
can
start
moving
the
environments
one
at
a
time.
Okay,
I
think
the
big
issue
there
is
going
to
be
getting
the
the
quota
set
up
and
we're
going
to
have
to
look
at
the
cost,
as
as
we
move
environments
over
because
that's
where
the
big
cost
is
going
to
come
from
and
then
obviously
for
experimental,
that's
the
one
environment
that
runs
on
aws,
so
I
don't
know
how
we
get
a
working
group
aws
account
that.
B
Then
a
topic
for
the
toc
phrase
it
and
if
it's
needed
yeah,
I
could
try
to
find
the
solution.
So
I.
A
B
You
don't
have
any
azure
landscapes
right.
That's
not
no!.
A
We
we
don't
have
any
in
in
cf
deployment.
We
could
definitely
add
one
or
switch
one
to
use
azure.
If
we
want,
I
mean
there's,
nothing
is
specific,
pretty
much
in
cf
deployment
as
well.
Just
relying
on
on
on
bosch
doing
its
thing.
C
B
Earlier
but
I
mean
wishing
for
oil
gas
layers,
that's
unrealistic
and
I
think
I
guess
I'm
slightly.
B
B
It's
it's
not
the
copy,
vmware
team
that
is
testing
it.
It's
actually
us
okay,
who's
doing
the
test
because
we
do
have
let's
landscapes
and
the
others
accounts
on
early
cloud
and
can
can
run
the
test
right,
but
yeah
this
time
it
went
somehow
wrong.
B
In
two
weeks,
yeah,
that's
an
again
let
by
open,
yes,
yes
and
then
back
I'm
on
vacation
and
then
okay
enjoy
september.
I
will
show
up
again
all
right
sounds
good.
Yeah.
Thank.