►
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
The
migration
of
the
experimental
account
to
our
own
AWS
account
is
in
progress
as
usual.
There's
a
lot
of
fun
with
domains
and
DNS,
but
at
least
the
bubble
part
is
working.
So
this
is
our
AWS
account.
Credentials
are
also
in
password
and
yeah
we'll.
As
you
see,
there
is
not
really
that
much
to
see
at
the
moment,
because
I
just
had
to
destroy.
B
A
Landscape
again
and
set
it
up
from
scratch,
but
this
should
work
fine,
the
only
problem.
Well,
the
biggest
challenge
was
the
correct
permissions
for
the
bootstrap
user.
A
Bootstrap
user
that
we
use
for
bubble,
so
here
we
have
somewhere
here
here
we
are
here.
We
have
the
credentials
which
we
passed
to
Bubble
permissions
was
very
tricky
because
neither
the
bubble
documentation
nor
Will's
amendments
were
sufficient,
so
Bubble
says
use
IAM,
colon
Star
as
permission,
but
this
would
be
very
broad.
Then
you
can
basically
escalate
your
permissions,
so
instead
we
try
to
add,
for
at
least
for
IAM
each
required
permission
individually,
which
is
quite
a
longer
list,
but
with
that
creation
and
destruction
of
the
landscape
works.
A
A
And
yeah
this
one
is
wrong.
I
think
I
can
delete
it
already
that
was
and
yeah.
The
rest
will
then
be
here
in
Route
53
automatically
created
by
bubble
and
honestly
I
cannot
get
to
tell
if
things
work
as
intended,
but
we
can
ask
Carson
for
assistance
here,
so
they
also
managed
to
get
this
running
somehow.
A
What
is
then
still
left
to
do
is
still
one
environment
which
has
not
been
migrated.
This
is
the
green
grass
one
yeah
three
years
ago.
A
This
one
is
used
for
the
stem
cell
validation
pipeline,
so
somewhere
around
here,
I
think
for
this
one
stem
cell
minor,
and
it
is
also
used
to
upload
Bosch
locks
from
failed
Bosch
deploy
drops.
A
So
if
a
release
is
updated
and
no,
for
example,
here
if
if
a
release
is
updated
and
the
CF
deployment
fails,
then
there
is
a
nice
feature.
I
forgot
to
show
in
our
Tech
session.
A
This
is
retrieve
Posh
locks,
so
here
and-
and
these
are
then
put
into
a
GCS
bucket
for
later
analysis,
because
the
Bosch
environment
is
torn
down
again
so
yeah,
okay,
so
green
grass
also
needs
to
be
migrated,
and
that
should
then
really
be
the
last
one.
But
yeah
who
knows
foreign?
A
Okay,
there
is
still
a
rate
validate
certificate
drop,
but
this
is
only
for
this
specific
environment
which
I
think
Carson
wanted
to
delete.
It's
an
old
Concourse
instance,
which
is
not
in
use
anymore,
everything
there
are
no
alerts
for
any
other
certificates.
A
B
A
Yeah
for
our
main
mission,
I
think
there
is
no
update
at
least
I
didn't
see
any
changes
here
in
the
single
build
pack
issues
for
the
Sea
of
Linux
fs4
update,
so
yeah.
B
Tickets
on
the
build
pack
release,
they
are
not
really
monitored.
We.
A
Are
then,
maybe
not
so
well
monitored,
so
what
we
see
is,
let
me
pick
an
older
one
smoke
tests,
so
you
mean
I'm
looking
for
one
before
release,
I
think
we
should
see
here
if
there
are
new
build
packages.
B
A
Mean
in
yeah,
yes,
of
course,
when
there
is
a
new
build
pack
release
and
it
makes
it
through
the
full
CF
deployment,
Pipeline
and
validation.
We
would
see
it
here
and.
A
This
one
is
flaky,
but
here
we
see
which
of
the
build
packs
do
not
yet
support
or
which
of
the
six
remaining
build
packs,
do
not
get
supported
as
well.
Yeah
HP.
A
B
A
Okay,
yeah
not
much.
We
can
do
in
this
yeah
here,
there's
one
more
thing
which
we
may
have
to
delegate
to
the
routing
team:
here's
a
new
change
in
CF
deployment.
A
A
The
routing
API
Indigo
router,
so
don't
get
confused
okay,
so
this
is
then
pointing
to
the
cloud
controller
nodes
and
on
that
we
have
a
routing
API
process
running
and
since
this
changed
boss,
backup
and
Recovery
tests
are
very
flaky
and
they
fail
in
one
router
group
test
case
where
a
router
group
is
created
forgot
before
or
after
the
backup,
and
then
they
do
the
restore
and
check.
A
If
the
group
is
there
again
or
something
so,
I
I
cut
it
green
only
once,
but
it
is
failing
really
very
often
and
it
looks
like
yeah.
A
The
routing
process
is
not
responding
and
then
you
get
to
502
when
you
try
to
call
the
registered
URL.
Something
like
this.
A
A
Yeah
I
mean
it's
really
succeeding
very
rarely,
and
this
may
block
further
future
commits,
so
they
won't
make
it
to
the
end.
But
I
really
can't
see
anything
that
suspicious
here.
A
Don't
get
anything
green
again,
then
yes,
but
I
also
notified
Japanese
and
well.
Everyone
is
already
in
Christmas
holidays.
Then
yeah.
B
Yeah
I
guess
there
won't
be
any
releases
between
now
and
next.
A
Yeah
good
so.
A
Okay
setup
is
at
least
green
okay,
so
I
will
try
to
finish
this
tomorrow.
The
AWS
migration,
anything
from
your
side.