►
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
Yeah
I
already
did
a
few
improvements
this
morning
on.
A
B
D
B
A
D
A
B
Yeah
I
also
checked
that
it's
they
changed
something
in
the
pr
and
then
it's
just
the
documentation.
Links
within
the
Ruby
files.
A
Yeah,
oh!
That's
that
that's
the
person
from
Microsoft
doing
no.
C
C
A
B
Yeah
I
looked
at
it
quickly,
but
I
found
it
weird
that
it
was
just
for
basically
for
two
file
changes
and
then
240
file
changes
with
some
weird
version.
A
B
A
Yeah,
so
they
are
using
a
new
version
of
swagger
code,
gen
right
and
then
after
that,
it's
all
person,
oh
yeah,
so
it's
just
that
version,
but
I
don't
see
the
actual
timeouts
change
it.
A
A
A
B
I
I
understand,
but
maybe
this
all
these
Swagger's
stuff
should
be
in
a
completely
different,
commit
just
for
easier
readability.
B
A
A
You
know
I
mean
the
same
has
been
done.
The
other
way
around
right
now,
if
you've
had
comments
about
not
having
enough
commits
and
stuff
before.
A
A
B
I
was
looking
at
it
and
I
didn't
even
unders.
I
didn't
even
understand
it.
A
Wasn't
just
the
stuff
that
Benjamin
looked
into
like
a
long
time
ago,
yeah.
B
So
it's
basically
if
people
still
use
the
agent
the
agent
way
of
setting
the
bush
dot
agent
for
the
setting
the
blob
store,
stuff.
D
B
It's
just
a
bit
confused
because
I
was
looking
at
it
and
I
thought.
Why
are
we
deleting
everything.
A
B
Yeah
but
I
mean
it's
like
for
everyone
who
is
currently
who's,
not
using
Bosch
deployment,
and
is
configuring
like
an
AWS
external
bucket
for
the
blobs?
Should
they
use
the
m
dot
m.bosch.
B
B
And
it's
also
putting
into
the
Agent
M
bush.
A
Yeah,
so
the
the
problem
is
that
it's
Global
right.
So
this
these
settings
are
on
The
Voice
director
are
using
global
settings
and
then
we
have.
B
D
A
Provider
and
that's
why
we
had
to
set
properties
blob
store
here.
A
Because
these
settings
are
not
used
anymore
here
notches,
that's
required
by
some
cpis
yeah
right
these
these
lines,
that's
basically
the
problem.
Yeah.
A
A
B
D
C
A
C
Yeah
I
am
it's
good
stuff,
of
course,
this
is.
A
A
D
A
A
B
Yeah,
that's
the
Matthias
working
on
that.
D
B
Oh
yeah,
so
this
is
the
throughput
changes.
B
B
Yeah,
the
only
way
for
him
is
just
because
Bush
doesn't
care,
it's
not
go
when
you
do
a
deployment,
it's
not
going
to
check
the
throughput
only
when
it's
being
redeployed
or
literally
a
clean
deployment
for
the
disk,
which
is
probably
never
going
to
happen
for
him.
So
the
best
option
for
him
is
what
they're
currently
doing.
Also
for
the
gp2
to
gp3
migration
is.
They
are
just
using
Bosch
and
AWS
CLI
to
boss
to
retrieve
the
disk
type
and
then
go
to
the
AWS
client
for
Loop,
and
that's.
D
B
B
B
A
D
B
The
resize
function,
it's
it's
only
being
hit
when
the
when
the.
B
The
properties
are
the
same,
but
here
we
change
the
properties
and
the
size
is
the
same.
So
we
never
hit
that
native
resize.
We
never
hit
the
native
research,
so
it
never
goes
into
that
ghost
path.
B
D
D
A
You
see
that
there's
a
change
and
you
don't
call
the
the
you,
don't
fall
back
to
like
the
old
resize,
so
you're
not
going
to
create
a
new
disk
you're
just
going
to
make
it
a
problem
of
the
but
I
mean
like.
Ideally,
you
would
have
some
something
where
you
would
try
right
so.
A
Could
have
the
director
try
the
the
native
disc,
precise
and
then
or
not
yeah
the
native
display
size,
and
then
it
would
like
be
able
to
send
back
an
error
code.
Saying
I
cannot
process
this
requests
and
then
it
would
go
back
to
like
the
the
native
or
the
old
way.
Yeah.
B
D
B
It
goes
back
to
the
old
way
if
the
CPI
gives
an
error
or,
if
the
no,
if
this
the
resize
function
in
the
CPI
does
not
exist,
it
will
go
back
to
the
to
the
normal
copy
copy,
create
resize
disk.
B
B
I,
don't
think
we
can
say.
Okay,
then
we
don't
check,
we
don't
check
for
the
sizes,
and
then
we,
when
you
are
changing
Cloud
properties,.
D
B
There
you
go
into
the
then
you
need
to
go
a
shitload
of
array
of
possible
Cloud
properties
that
have
the
ability
to
natively,
because
AWS
has
only
for
only
for
the
gp2
to
gp3
disks.
They
have
like
a
zero
downtime
change.
The
the
throughput
is
one
of
them,
but
for
other
disks
other
disk
types
it
doesn't
work.
A
A
B
A
No,
you
wouldn't
so
we
would
the
director
would
the
director
would
need
to
change
right,
so
the
director
would,
if
only
the
so,
it
basically
would
always
try.
A
Also
that
yeah,
so
yeah
I
think
it's
way
too
big
walking
through.
A
No,
maybe
we
need
well.
We
need
a
disk
update
native
disk
updates.
B
Yeah,
okay,
yeah:
we
can
this.
A
A
A
So
we
it
would
be
update
this
native
update
this.
B
A
A
Like
that
function
should
also
error
to
say
like
this
is
not
like
be
able
to
respond,
but
not
support
it
right
like
if,
if
a
certain
update
is
not
supported,
and
then
the
the
old
flow
will
be
used
as
a
fallback.
B
Yes,
but
then
you
get
things
like
in
a
two-step,
so
if
if
the
disk
size
is
the
same
and
then
and
then
it
goes
to
the
next
phase,
if
properties
are
just
different,
so
you
have
like
everything
happens,
then,
in
a
two-step.
B
B
Yeah,
it's
going
to
adding
some
complexity
here
and
there
flexibility.
A
C
Disk
hint.
C
Methods
yeah
here
there
it
is.
A
D
C
A
B
D
B
B
A
Okay,
something
like
that
and
yeah
I
think
we
can
leave
it
at
that.
B
C
I
was
wondering
this
week.
I
was
looking
into
the
Bosch
IO
stuff.
It's
so
we
wanted
to
migrate
it
to
Cloud
Foundry.
C
A
B
For
deprecating
Bionic.
A
B
So
we
change
all
the
we
changed,
all
the
messages
that
for
Xenia
and
trustee
that
we're
pointing
to
bionic.
They
are
now
pointing
to
they're
now
pointing
to
Jimmy
and
I,
put
a
notification
now
a
notification
Banner
for
bionic
as
well.
A
B
Don't
have
direct
access
to
this,
it's
going
from
my
personal
GitHub
account
and
I.
Normally
don't
do
that.
C
A
Okay,
so
we
we
have
that
PR
that,
like
where
we
talked
about
like
the
naming
and
stuff
and
now
it
needs
to
be
done
right
and
that
hasn't
happened,
because
the
team
has
now
like
bandwidth
currently
to
to
look
at
it.
But.
C
Yeah
I
know
I,
remember
the
draft
PR
I
Know
It
yeah;
okay,
all
fine!
Yes,.