►
From YouTube: Geo Scheduling Call - 2019-10-11
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
C
B
Okay,
in
the
closed
column,
today
we
have
fall,
which
is
still
pretty
good,
considering
we
did
this
last
on
the
neck,
so
number
one
refactor
the
checksum
code.
This
was
a
community
contribution
that
Brian
put
forward,
which
was
wonderful,
I'm,
very
happy
that
this
sin
I'm
going
to
take
active
and
in
your
heel,
offsets
done
now.
B
This
is
good
to
see.
Ok
repose
with
after
recent
commits
are
flagged
and
it's
invalid.
So
this
was
closed
because
we're
not
able
to
reproduce
with
what
they've
opened
on
the
same
version
feel
free
to
reopen
if
needed.
Ok,
so
unfortunately
we
didn't
get
to
the
bottom
of
the
problem,
but
we
have
gotten
to
a
point
that
we
can't
go
any
further.
So
look
at
rid
of
the
issues
that
we
don't
need.
I.
A
B
Right
backwater
to
fix
the
sink
I
was
so
happy
that
this
has
been
finished
as
well,
and
many
thanks
to
delivery.
If
they
are
listening
for
doing
this,
for
us
not
ideal
that
we
had
to
go
through
this
process,
but
at
least
it
was
done,
and
there
is
an
RCA
that
is
completed
and
and
I
think
the
biggest
learnings
from
the
our
CIO
that
we
need
to
get
this
thing.
We
need
to
get
you
your
in
production,
and
so
we
can
make
that
part
of
the
second
half
of
this
quote
and.
A
B
I'm
working
with
him
on
it,
I
want
to
make
sure
that
it
is
regimented,
but
also
that
sometimes
Gio
can
be
special,
but
I
want
to
make
sure
that
we're
not
so
special.
That
is
completely
different.
Just
why
so
we
need
to
still
fit
in
with
what
the
actual
process
is,
but
I
want
to
just
make
sure
that
they're,
considering
that
there
is
differences
inside
of
the
engineering
department
system
and.
A
I
spoke
with
marine
as
well,
and
I
actually
need
to
create
an
issue
for
this.
He
asked
me
to
create
an
issue
template
for
backporting,
because
I
think,
even
though
there
is
a
process,
I
think
they
should
also
be
sort
of
an
issue
template
for
if
you
want
something
back
ported.
This
is
the
template
that
you
need
to
fill
out
in.
B
B
B
B
B
B
B
B
C
B
A
A
Create
geo
upgrade
documentation
and
just
out
of
interest,
so
I
shared
it
with
them
and
I
shared
it
with
come
here,
because
I
think
he
realized
that
this
is
a
rather
involved
sort
of
piece
of
documentation.
So
always
look
nice
because
maybe
you'll
have
a
look
or
people
and
his
team
would
have
a
look,
and
maybe
it
would
catch
something.
A
Also
asked
to
chair
these
queries
with
the
customer,
so
I
already
put
it
in
the
support
ticket
and
asked
Eric
to
make
sure
that
this
gets
across
I'm
very
impressed.
Just
looking
at
the
statistics,
it
looks
like
the
queries,
execute
yeah
a
few
factors
faster,
like
from
timing
out
at
5
minutes
to
6
seconds.
So
thank
you
if
this
is
if
this
holds
right,
I
think
this
this
may
work
out.
Obviously
this
looks
like
magic
to
me.
I
don't
understand
anything,
but
I
am
really
happy
that
this
is.
A
This
is
being
picked
up
and
also
some
feedback.
There
was
a
representative
of
the
customer
that
is
affected
at
commit
and
I
didn't
get
a
chance
to
actually
speak
with
that
person
directly,
but
I
heard
from
from
Timo
who
works
with
them
that
they
appreciate
us
being
active
in
those
issues
and
actually
posting
updates,
because
they
can
follow
and
they
can
see
what
what
is
happening
so
I
think
that's.
It's
really
nice
nice.
B
A
But
this
may
need
to
be
back
ported,
so
I
may
not
do
that,
because
that's
distributions
playground
I
just
asked,
because
I
got
an
inkling
because
I
think
there's
a
lot
of
things
that
are
changing
so
I.
Think
the
question
is,
you
know
like
what
will
happen
with
this
once
it
s
is
actually
accepted
and.
A
A
B
C
B
B
I
think
I'll
get
it
I'll
give
it
today
in
Monday,
because,
if
he's
been
busy
on
other
things
in
it
make
sense
why
it
hasn't
been
picked
up
yet,
but
if
something
else
new
gets
picked
up,
then
there's
a
question
there.
Why
isn't
it
not
this
one,
so,
okay,
verification
of
design
repositories
valerie's
on
this
one
yeah,
there's
nothing
much
to
report
I
think.
A
Does
it
make
sense
to
implement
design
repository
verification
right
now,
and
is
there
a
good
way
forward
or
I
haven't
really
dug
into
this,
or
is
the
given
what
we
know
now?
Are
we
basically
saying
like
hey,
you
know
all
of
these
localized
solutions?
They
are
insufficient.
What
we
should
push
forward
for
is
a
sort
of
firm,
it's
more
standardized
verification
framework
and
so
I,
don't
I,
don't
know
what
the
state
of
that
discussion
is
so.
B
I
did
try
to
pull
this
one
into
a
more
unified
discussion,
because
there
is
a
similar,
somewhat
similar
discussion
happening
about
the
replication
frame,
a
framework
for
replication
as
well,
and
the
reason
that
I'm
trying
to
pull
them
into
one
conversation
is
because
they
are
I
mean
I,
know
that
they're
there
there
are
big
technical
differences,
but
I'm
wondering
if
there
is
a
similar
method
that
can
solve
both
of
the
problems
using
using
messaging,
so
I'm
trying
to
pull
the
conversation
together.
Just
because
I
want
to
see.
B
I'm
doing
these
I'm.
Looking
at
this,
these
adjustments
to
creating
frameworks
here
and
can
other
people
be
dedicated
onto
getting
this
on
staging,
and
can
these
people
be
dedicated
on
to
getting
them
on
to
do
give
come
whether
they
all
have
to
happen
in
parallel?
Is
another
question,
but
I
think
that
having
sets
of
people
that
are
focused
on
these
things
might
be
helpful
to
get
them.
You
know.
A
I
I
kind
of
I
agree,
and
maybe
we
can
talk
about
sort
of
capacity
allocation
in
like
in
general,
for
sort
of
12.5
and
and
what
we're
going
to
do,
because
but
I
do
agree
that
it
may
make
sense
to
have
sort
of
a
little
bit
more
of
dedicated
focus
for
a
couple
of
of
folks
on
an
area
just
to
make
sure
that
it
actually
moves
forward
and
that
there
is
also
it's
easier
to
see.
You
know
what
what
is
happening
but
then
I
get
pay.
A
I
would
hesitate
to
have
more
than
three
things
going
on
in
parallel,
because
then
it
gets
really
tricky
right,
so
I
would
I
think
that's,
maybe
something
we
can
sort
of
come
back
to
at
the
end
of
the
call
sort
of
with
scheduling.
What's
next,
because
I
think
some
of
those
things
are
more
important
and
more
urgent
than
others.
So
we
can
I'm
happy
to
drop
some
things
for
for
now,
if
we
can
focus
on
getting
some
other
things
to
move.
Okay.
B
B
A
A
B
B
B
B
A
A
So
this
is
something
that
that
tone
proposed
to
minimize
the
steps
to
run
an
upgrade
without
posted
for
migrations.
I
really
like
that
idea,
and
it
fits
pretty
well
with
with
the
other
work
we're
doing
in
in
upgrades
at
the
moment.
So
I
think
this
should
be
picked
up
so
I'm
happy
with
this,
be
here
then,
and
it's
also
I
think
it's
something
that
is
small
enough
to
actually
move
relatively
quickly.
Hopefully
so
that's
nice,
the
refresh
for
tables
on
on
reconfigure.
B
B
A
Bug
so
I
think
this
is
something
we
we
should
do
so
I'm
happy
and
also,
if
we
look
at
this
other
than
these
two
things
which
may
not
happen
in
12.4
I
have
to
actually
I
have
to
follow
up
on
those
I.
Think
there's
a
lot
of
like
good
work
being
done
here.
So
potentially
this
is
something
that
can
can
be
so
that
is
released
with
12.4,
but
then
we
hold
my
neighborhood
on
release
post
until
all
of
those
things
are
done,
let's
see
how
it
goes.
A
Then
the
Postgres
upgrade
I
think
this
is
I
mean
we
we
rescheduled
to
do
the
upgrade
of
the
version
first
and
then
do
host
press
I.
Think
that's,
that's
still
fine,
but
I
I
do
this.
So
it
needs
to
happen.
I
think
upgrades
are
important.
We
should
figure
out
how
to
do
this.
Handle
design
uploads
on
admin
area.
So
I
think
this
is
something
that
Zack
may
pick
up.
Yes,.
B
This
is
sitting
behind
another
ticket
that
he
has,
which
is
a
dessert
documentation,
only
change
the
thing
is
he
to
get
his
GDK
running
and
geo
running
in
GCP
to
get
through
those
ones.
So
this
isn't
I,
don't
think
this
is
going
to
be
picked
up
immediately
and
I.
Don't
know
if
this
is
gonna
make
it
into
12.4.
B
A
B
B
A
I'll
bring
in
the
stuff
with
Josh,
because
I
think
this
is
a
little
bit
of
discussion
in
the
product
team.
But
I
could
you
know
I
could
reasonably
put
all
of
those
little
little
issues
as
merged
into
the
the
release
post,
but
I
don't
see
any
point
in
doing
that
because
I
don't
think
that
has
any
value
for
our
customers
now.
B
A
B
B
B
B
A
Yep
but
I
am
quite
I,
think
you
know
if
we,
if
we
can
accelerate
the
documentation,
a
tiny
bit
and
I,
don't
think
like
I
would
say.
I
would
I
would
like
this
to
be
done
by
Friday
and
I.
Think
it
should
be
possible
if
we
prioritize
it
correctly,
because
the
documentation
is
written
right
and
if,
if
Gabriel
comes
back,
I
think
we
should
just
say:
hey.
Can
you
please
have
a
look
at
this,
so
we
can
get
it
in
because
then
it's
actually
out
and
I
think
that
would
be
a
major
achievement.
B
B
B
B
A
B
A
B
B
So
what
I'd
like
to
quickly
do
is
just
to
if
we
can
I
want
to
be
able
to
paint
a
picture
about.
This
is
where
we
are
right
now,
and
this
is
why
we're
gonna
schedule
in
these
things
and
then
bounce
over
to
the
Geo
and
get
that
comm
project
or
what
what
else
we
need
to
be
doing
next
so
because
it
feels
like
we're,
so
we're
actually
really
close
to
finishing
a
whole
bunch
of
things.
I.
A
A
A
A
A
We
will
not.
We
will
not
I
think
what
we
have
to
decide
is
I'm
happy
to
leave
this
large
epic
open,
because
there's
potentially
more
work
to
do,
but
there
are
these
two.
Oh,
this
is
all
new.
Oh
I
love
this
view.
Yes,
so
here
the
Geo
upgrade
demos
are,
is
sort
of
the
mini
epic
of
all
of
the
operator
moves
and
then
I'm.
B
A
A
I'm,
not
sure
we
will
be
able
to
do
this
in
12.4
just
because
of
the
like
review
intensity
right,
but
that's
okay,
but
I
think
this
year
should
be
closed.
Just
closed
off
as
a
first
iteration
say
like
we
have
the
documentation,
we've
thought
about
it.
A
lot
just
make
sure
that
we
find
sort
of
a
good
point
at
which,
if
this
is
done
and
then
we
can,
we
can
think
about
the
next
thing.
So
I'm
I'm
happy
with
this.
A
The
foreign
data
table
updates
it's
kind
of
the
same
thing,
so
this
requires
maybe
a
little
bit
of
follow-up
from
me
specifically
about
those
two
items
here.
If
they
actually
need
to
happen
or
not
right,
but
I
would
also
like
to
just
close
out
this
sort
of
mini
mini
epic
and
be
done
with
it,
because
then
it's
actually
done
right
and
that's
that
these
things
here,
the
testing
I
have
not
much
visibility.
I
know
this
is
this
Jenny's
work.
A
B
B
A
From
that's,
okay,
I
put
it
in
here,
because
I
guess
related
I
think.
The
summary
is
we're
really
close
to
closing
this.
One
I
think
we're
pretty
close
to
closing
that
one
here,
essentially
either
by
deciding
to
do
some
things
very
quickly
or
by
just
deciding
to
not
do
some
things,
which
is
also
fine.
A
A
A
It
lives
there
for
now,
because
it
is
it's
not
a
documentation,
improvement
and
it's
not
to
do
with
making
foreign
data
table
updates
better.
So
it's
really
its
own
own
thing
and
those
two
things
here.
We
can
definitely
I,
think,
postpone
or
spin
them
out.
I,
don't
say
like
hey:
let's
create
a
new
epic
for
for
those.
B
So
the
so
on
the
sorry
Fabian,
would
you
mind
opening
the
epic
itself
that
lists
the
sub
epics
as
well.
Yep.
A
B
B
A
I
would
actually
say
that,
just
if
we,
if
we
look
at
this
some
sort
of
top
to
bottom
in
terms
of
scheduling
where
we
are
this
one
here
is
in
development
right
now.
That's
what
stone
is
doing
this
one
here
is
scheduled
already
as
in
it's
in
ready
for
development,
and
this
one
here
I
think,
is
in
scheduling,
so
I
think
these
things
will
happen
over
the
next
couple
of
weeks.
A
I
think
this
is
I'm
not
concerned
about
sort
of,
let's
say,
closing
out
the
upgrade
demos
right
and
it's
arguable
that
it
may
need
to
go
into
different
ethic
as
well,
so
I
think
and
also
I
I.
Don't
know,
I
I
think
it's
nice
to
capture
this
work
here
in
in
issues
because
I'm
giving
look
at
it
all
right.
Yeah.
A
Next
thing
is
improved
geo
update
documentation.
So
if
we
just
look
at
this,
this
here
is
in
review
and
I.
Think
if
there's
a
cross
dependency
from
this
one
to
the
upgrade
demos,
because
we
need
to
test
this
and
then
I
also
think
that
this
has
a
lot
of
potential
customer
impact
right.
So
there's
probably
another
round
of
reviews,
maybe
letting
stem
or
or
come
you
look
at
this
as
well
alright,
so
this
may
take
a
little
while
longer,
but
it
is
certainly
on
the
way
and
I
I
want
this
to
be
really
robust
right.
A
A
And
then
this
one
here
add
section
to
the
our
documentation
describing
upgrade
impact
on
secondary
I
think
this
is
also
a
documentation,
only
change
that
essentially
says
when
you
upgrade.
What
is
the
potential
impact
on
a
on
a
secondary
and
that's
the
documentation
change?
This
is
weighted
and
also
in
scheduling,
but
I
would
say
if
we
want
to
just
close
out
these
three
things,
we
should
probably
also
just
accelerate
that
a
little
bit
to
get
it
done
well,.
B
A
B
A
A
A
B
D
A
B
A
We
and
that's
my
last
question:
yep
this
year
resolved
programmatically
foreign
table
table
refresh
and
geo
for
zero
downtime
upgrades
I
think
these
are
with
this
one
here,
I'm,
not
100%
sure,
if
we
will
actually
do
this
right,
so
I
think
this
requires
just
follow-up
for
me
to
say
like
what.
What
are
we
doing?
We
want
to
finish
this
one
here.
This
is
an
hour
standing
issue.
A
B
So
I
just
want
to
put
a
summary
in
that
section
about
the
foreign
data
tables
that
we
need
to
come
to
a
conclusion
about
about
both
of
those
always
adjust
the
route,
because
the
second
one
doesn't
have
much
discussion
on
it.
All
it's
just
it's
the
first
that
the
one
resolve
the
resolve
foreign.
This.
A
A
D
D
A
So
I
think
my
I
think
what
we're
essentially
saying
is.
We
are
so
close
to
finishing
almost
all
the
work
that
we
intended
to
do
in
this
iteration
for
simplifying
geo
upgrade
the
Jeevika
process
so
before
starting
something
new,
let's
just
flush,
all
of
that
stuff
out
close
it
down
and
then
move
on,
I
think.
B
That
that's
the
right
thing
like
as
I
as
I,
read
over
what
what
I've
written
here
or
what
we
have
written
here
in
the
scheduling
pool
summary.
There
are
essentially
three
things
that
we
are
close
to
finishing:
the
object,
storage,
simplifying
the
upgrade
process
and
the
replication
of
design
uploads,
with
the
exception
of
the
verification,
third
and
I,
think
that
the
message
at
the
end
of
this
scheduling
core
needs
to
be.
B
These
are
three
epochs
that
we
want
to
draw
a
line
under
and
complete,
and
then
the
next
two
things
are
that
we
need
to
pick
up
far
around
how
we
think
about
this
replication
and
verification
in
terms
of
a
framework
making
it
easier
to
add
more
data
types.
So
the
the
it's
almost
like
the
base
that
we
want
to
work
from
when
adding
more
data
types
and
the
second.
C
B
The
side
and
I
want
to
just
close
the
the
thought
there
and
the
second
thing
is
around
the
gon
get
lab
calm.
So
the
reason
why
I
think
that
those
two
things
become
related
is
because
it
sounds
like
there
is,
but
one
it
sounds
like
it's
difficult
to
add
more
data
types
because
of
certain
things
that
are
missing
and
that
some
of
the
queries
land
of
being
slower
because
of
the
way
that
the
system
is
working
at
the
moment.
B
A
Think
picking
up
the
planning
of
this
right
with
sort
of
in
mind
that
we
are,
we
are
focusing
on
actual
implementation
of
geo
for
the
our
purposes
on
comm,
right
and
I.
Think
I
now
understand
a
little
bit
better.
Why
the
very
sort
of
a
new
framework
of
replicating
data
and
very
fine
data
may
be
needed
in
order
to
enable
this
for
performance
purposes,
but
I
think
then
let's
say
we
get
the
Geo
comm
stuff
done
and
we
get
it
done
sort
of
very
quickly.
A
B
C
B
B
Calm,
I
mean
obviously,
with
the
infrastructures
help
but
I
think
there
from
a
product
perspective,
there's
not
going
to
be
as
much
I'm,
not
saying
we're
not
going
to
need
you
for
those
projects,
but
I
think
we
will
need
you
less
than
the
promotion
demotion
and
fail
of
us.
I
think
that
you
have
yet
then
gives
you
more
some
more
brain
space
to
get
ahead
of
that
project.
While
we
continue
on
getting
it,
I'll
forget
that
come
hey.
C
A
B
Ok,
so
I
think,
but
I
think
we've
got
to
go.
I
think
this.
This
is
a
good
place
for
us
to
be
in
I
mean
it's
always
a
good
place
for
a
spin
but
I
like
the
fact
that
we're
at
the
end
of
three
epochs
and
we
didn't
actually
have
more
than
that
in
progress-
I
mean
I,
know:
we've
had
other
smaller
pieces.
You
know,
we've
been
helping
customers
with
certain
problems
and
there's
always
going
to
be
stuff.
B
A
A
So
I
need
a
little
bit
more
cleanup,
but
I
think
this
is
you
know
the
fully
transparent
kit
configuration
this
is
kind
of
done
and
they
improved
with
you
I
use.
The
experience
here
is
something
in
the
future
right.
So
they
say
like
this
is
awkward
like,
like
I
just
need
to
sort
this
a
little
bit
more,
but
I.
A
A
You
know,
there's
more
concrete
work
to
be
done
about,
like
the
architecture
rollout
and
the
rolling
out
is
to
staging,
but
that
will
be
the
main
focus.
Then
we
will
also
and
I
think
this
requires
the
creation
of
a
new
epic.
You
know
the
sort
of
work
on
other
verification
and
replication
framework
right
in
support
of
the
disaster,
recovery
grids
and
then,
lastly,
the
promotion,
demotion
and
failover
the
planning.
For
that.
A
We're
also
not
going
to
work
specifically
on
upload
verification
right.
That's
also
going
to
be
postponed,
so
we're
sort
of
saying,
let's
take
a
step
back
and
do
some
sort
of
groundwork
for
the
verification
and
replication
and
just
make
sure
that
that
is
performant
and
easier
to
do,
because
at
the
moment
it's
not
that
sort
of
fear.
B
B
A
So
I
think
actually
like
it
was
we're.
Not
the
let's
say
most
milestone,
driven
like
the
process
is
more
continuous
right,
so
I
think
actually
we're
saying
is
before
doing
any
of
this.
We
are
going
to
close
out
these
three
three
epochs
alright,
and
that
is
the.
That
is
the
focus,
so
we
will
like
just
make
sure
we
we
just
have
closure
on
those
once
that
happens,
you
know,
which
will
very
likely
happen
in
12.5,
right
and
forward.
We
are
going
to
in
full
force
focus
on
those
three
things.
There's.
B
B
A
Me
it
doesn't
make
sense,
and
you
know
it
sounds
like
more
than
it
actually
is
I
think
because
we're
so
close,
but
I
think
it
also
is
really
good,
because
we
can
then
say,
as
a
team
we've
actually
closed
out.
These
really
large
pieces
of
work
honestly,
like
I,
think
this
view
here
makes
me
if
I
go
to
simplify
to
you
up
their
process.
The
new
trees
for
epics
makes
me
so
happy
because
I'm.
B
A
B
A
B
We're
ten
minutes
over
so
I've
written
well,
we
have
all
together
written
in
the
shaded
and
call
summary
everything
can
I.
Please
ask
you
to
just
have
one
final,
read
of
that
and
check
that
you're
happy
and
then,
when
I
upload,
this
video
later
on
I
will
just
dunk
the
summary
into
the
spec
Channel
yeah.
A
I
think
one
thing
that
I
would
probably
write
is
like
a
three
sentence
summary.
You
know
that
essentially
says
we
are
going
to
finish.
There
was
four
things
first
and
then
we
are
going
to
like
check
out
those
three
things.
Next
right,
that
is
essentially
the
plan,
so
that
and
then
we
have
lots
of
details.
Yeah.
B
A
I
feel
the
same
because
I
the
last
three
days,
I
obviously
had
no
time
to
write
down
anything,
but
I
had
a
little
bit
of
sort
of
down
time
to
think,
and
sometimes
at
least
I
get
this
sort
of
clogged
head
feeling
when
I
need
to
hold
a
lot
of
this
information
and
thought
process
in
my
head
and
then
having
the
opportunity
today
to
talk
through
this
and
crystallize
it
and
get
alignment
is
really.
This
is
great,
really
fun.
Awesome.