►
From YouTube: Geo Scheduling Call - Monday Edition (with tea)
Description
Pity we didn't record the tea part...
B
B
A
A
A
A
A
Before
I
close,
this
one
I
think
they
were
related
to
this,
but
I
just
want
to
double
check.
I
feel
like
there
was
something
related
to
this.
That
was
in
the
block
column,
but
I
might
be
wrong,
I'm,
just
double
checking.
If
my
memory
is
bad,
no,
it
was
so
completely
different.
My
memory
is
terrible.
Okay,
this
one
is
fine,
which
was
that
okay
misaligned
a
secondary,
read-only
better.
Yes,
this
was
falling
all
over
the
place
and
kachelle
closest,
as
the
book
was
fixed
by
Stefan.
B
A
B
A
Okay,
I'm
gonna,
refresh
the
board
and
all
the
clothes
things
should
be
gone.
No
because
I
can't
click
on
the
last
three
that
didn't
work
from
okay,
three
more
right,
lock,
who
said
never
exits.
This
was
connected
to
the
helm.
Chart
work
that
has
been
done.
I've
opened
a
different
thing:
that's
been
merged,
that's
the
way
to
go,
but
this
really
merged
she's,
great
sweet,
entice,
sonnets.
B
A
A
B
A
A
B
B
A
C
A
A
A
B
B
B
A
C
A
Okay
and
then
the
three
that
are
blocked
yeah
that
we've
just
we
had
recently
open
that
one,
but
let's
just
double
check.
What's
in
there
again
and
this
one,
we
were
waiting
on
some
decisions
about
the
others
that
have
come
since
ashes.
After,
don't
think
we're
going
to
be
able
to
resolve
any
questions
we
have
on
that
anyway,
the
Romans.
B
A
B
Yeah
so
I
think
that
the
last
state
as
of
thirteen
minutes
ago,
which
I
have
not
seen
because
I'm
in
this
car,
let
me
read
okay,
so
I
think
here.
The
the
next
step
is
to
actually
decide
on
one
of
the
two
paths
towards
resolution,
which
is
I,
think
partially
equal
decision,
so
I
would
like
to
get
some
input
from
the
team
like
which
workflow
is
preferable.
My
only
comment
was
that
one
of
those
proposed
workflow
is
essentially
limits.
B
Our
our
capabilities
and
I
think
that
to
me
suggests
that
we
should
do
that
like
if
you
upgrade
the
the
secondary
before
you
upgrade
the
primary.
Then,
if
you
break
your
secondary,
your
primary
all
of
a
sudden
is
without
a
working
replica,
which
is
maybe
not
preferred
like
you
would
like
to
have
you
your
a
secondary,
definitely
working
or
have
at
least
two
secondaries,
and
so.
A
B
A
C
A
A
A
C
A
B
B
A
A
A
B
A
B
Okay,
so
I
took
the
liberty
and
I
already
so
what
I
did
is
you
can
see
this
here
as
well,
because
you
were
out
on
Friday
I
essentially
went
through
some
of
the
things
already
and
like
sort
of
pre
schedule
them
like
the
things
that
I
think
actually
need
to
be
done.
So
we
can
do
two
things.
We
can
either
like
go
through
this
board
here,
or
we
can
just
pick
it
up
from
here,
which
may
be
a
little
bit
easier.
I
can't.
A
B
So
the
first
one
here
is
customizable
get
HTTP
clone,
who
you
are
L.
So
this
is
a
sort
of
companion
issue
that
came
out
of
the
like
work
to
document
how
to
use
a
single
get
URL
and
the
proposition
here
is
currently
we.
We
can
customize
this
URL
here
for
SSH,
but
we
can't
for
HTTPS
and
that
defies
the
purpose
of
like
a
single
URL
a
little
bit
so
Mike
proposed
to
do
this
to
do
this
now.
That
would
essentially
mean
that
you
can.
You
can
set
these
URLs
here
to
one
location
everywhere
and
I.
B
Think
that
makes
sense
to
just
do
it
in
tandem
with
the
other
work
that's
going
on,
because
otherwise
it
feels
a
little
bit
like
you
know.
We
can
push
out
the
documentation
already
and
that's
okay,
but
I.
Think
then,
once
we
have
this,
it
actually
makes
a
lot
more
sense
for
for
customers,
I
think
I.
B
I'll
move
this
over
fix
refresh
foreign
cables
gonna
be
configured,
so
this
is
so
what
I've
done,
and
now
this
should
make
sense.
We
closed
one
of
the
issues,
which
was
the
p2
bug
report
about,
like
foreign
data
record,
not
working
correctly
and
actually,
when
I
went
through
this
on
Friday
I
realize
that
there
are
a
lot
of
small
items
that
have
to
do
with
foreign
data
repair,
not
being
you
know,
updated
correctly
and
certain
certain
issues
in
not
giving
the
actual
state,
and
it's
all
a
little
bit.
B
You
know
like
ready
for
improvement,
so
what
I
did
is
I
actually
created
an
epic
and
then
grouped
all
of
those
like
tiny
items
out
which
spun
out
of
discussions
from
this
big
issue
right,
and
so
what
I'm
doing
now
is
essentially
saying,
let's
start
moving
through
those
little
issues,
because
they
are
actually
nicely
broken
down.
That's
not
so
big
and
ill-defined
anymore
makes.
A
B
So
the
first
one
is
fix,
refresh
form
tables
and
reconfigure.
This
is
the
I
think
the
most
important
one
because
it
actually
remove
its
weight.
This
is
the
issue
that
we
see
when
updating.
Where
you
know
you
update
your
geo
instance
and
then
you
are
presented
with
a
foreign
data.
Wrapper
schema
is
out-of-date
and
that
should
just
be
handled
automatically
and
not
doesn't
should
require,
like
many
of
intervention,
so
I'm
happy
to
schedule
this
yet
and
then
here
these.
B
B
Where
you
know
he
running
it
lab
check
and
it
actually
doesn't
give
you
the
correct
status
for
the
like
FTW
and
that
could
be
confusing
and
that's
just
a
small
tag
on
to
the
other
issues.
So
I
leave
this
in
here.
Maybe
this
one
is
maybe
more
important.
This
is
about
fixing
the
race
condition,
fixing.
A
B
In
yes,
ish
so
I
think
resolving
the
Omnibus
upgrade
issue
is
the
most
important
thing
that
we
we
should
just
get
out
of
the
way
because
it
affects
upgrades
and
these
like
small
items
they
they're,
maybe
not
the
most
important
things.
We
need
to
do
right
now,
but
I
also
think
they
are
relatively
small
and
I.
B
We
worked
on
making
upgrades
for
foreign
data
cables
more
robust
right,
and
in
order
to
achieve
this,
you
need
to
do
all
of
those
different
things
and
that
forms
a
nice
package
where's
the
most
important
like
this
just
by
itself,
is
probably
not
as
meaningful.
So
that's
my
my
thinking
behind
that
I
like.
B
So
and
then
I
think
this
year
is
sort
of
like
similar.
These
are
like
the
instructions
for
this
is
essentially
like.
Also
this
text
here
is
not
quite
right
right,
and
that
should
also
not
be
a
lot
of
work,
because
I
think
this
is
maybe
something
we
can
just
you
know
like
do
in
conjunction
right
and
then
like
have
a
like
a
little
bit
of
a
clean-up
operation
in
that
regard.
B
A
B
A
That's
the
first.
The
first
thing
is,
we
need
to
figure
out
an
actual
number
for
the
upgrade
calls
I
mean.
Oh
one
is:
is
it
a
one?
Is
supposed
to
be
one
ideal
day
of
work?
You
know
if
you
did
nothing
else
for
the
whole
day,
would
take
you
this
time
and
I
guess
an
upgrade
is
only
a
one,
because
it's
a
call
right.
Yes,
okay,
so
one
is
fine
yeah.
So.
B
I
mean
this
is
essentially
I.
Think
what
I
would
like
to
do
is
schedule
those
and
then
actually
upgrade
the
Postgres
version,
which
requires
a
little
bit
of
Investigation
with
a
distribution
team
on
how
to
actually
do
that
and
maybe
raising
some
follow-up
issues.
If
this
is
not
well
documented
right.
B
But
that
is
a
separate
thing
and
then
the
other
bit
is
to
actually
then
upgrade
from
twelve
point,
one
nine
to
twelve
point
two,
which
you
can
probably
do
together
in
one
call
or
you
can
also
split
them,
which
is
why
I
put
two
different
things.
But
I
would
like
to
continue
with
this
because
it
is,
you
know,
I,
think
it's
important
and
we're
sort
of
in
the
middle
of
it.
So
we
should
do.
A
A
B
B
For
both
of
them,
I
actually
sort
of
make
a
little
sense
just
so
that
when
we
continue
to
do
those,
we
actually
perform
similar
steps
right
and
just
go
through
this
and
say
like
okay,
you
know,
like
I've,
I've,
read
the
instructions
I've
checked.
You
know
like
a
few
things
which
may
be
helpful
if
this
is
helpful
for
the
people
operating
beverage.
B
A
One
thing
I
can
think
of
at
the
end
of
this
is
that
it
feels
like
the
next
one
should
be
scheduled
at
the
at
the
same
time.
Is
that
the
call
completes
that's
becomes
a
cycle,
and
even
if
it's
not
even
it's
not
scheduled
just
that
the
next
person
in
the
list
is
pinged
like
it.
Maybe
the
maybe,
the
the
order
of
engineers
just
needs
to
be
set,
and
then
whoever's
the
next
in
the
list
gets
ping
to
create
the
next
upgrade
yeah.
B
We
didn't
think
about
it.
The
way
I'd,
like
I
I,
tried
to
make
this
as
an
issue,
because
I
felt-
and
we
can
essentially
just
do
what
we're
doing
now,
which
is
just
put
it
on
the
board,
and
then
somebody
needs
to
pick
it
up
and
it
becomes
doesn't
come
sort
of
an
extra
activity
that
you
know.
People
need
to
like
be
informed
about
it's
it's
something
that
we
that
it's
just
a
regular
like
thing,
yeah.
B
We
can
I
mean
that's,
maybe
your
follow-up
discussion,
yeah,
okay,
so
I
think
that's
a
good
amount
of
stuff
to
work
through
to
the
like
rest
of
the
scheduling
board,
I'll
be
freshness,
so
I've
done
quite
a
bit
of
work
with
the
the.com
epic
I'd
have
actually
added
descriptions
and
tasks
to
do
this,
and
I
would
really
like
to
do
this
next,
but
I'm
also
I
think
ashes
on
vacation
for
two
weeks.
No,
the.
B
A
That
determine
if
we
need
to
include
deployment
to
Canary,
assign
that
to
me
and
put
it
into
ending
for
development,
and
what
I
can
do
is
I
can
start
the
discussion
with
infrastructure
about
whether
or
not
we
should
do
this
and
because
determine
is
just
you
know,
ask
the
question:
have
the
discussion
and
make
the
decision
so
I
think
that
that
doesn't
have
to
go
through
the
planning
stage?
We
just
do
it.
We
just
start
that
discussion
and
I
think
also
for
creating
the
diagrams.
A
B
A
It
also
just
confirms
I
mean
having
these
diagrams
confirms,
that
we
are
going
to
do
what
infrastructure
wants
us
to
do
rather
than
guessing,
and
then
both
of
us
being
disappointed.
That's
just
it's
managing
expectations
between
them
and
between
us,
so
for
this
I
think
this
is
something
that
I
can
pick
up
with
them
without
loading
with
that
placing
additional
load
on
the
team
and
without
having
to
wait
for
deveneux
ash.
So
if
we
can
put
those
both
in
the
in
the
backlog
and
and
I'll
actually
do
some
work
for
a
change
I
like.
B
A
B
Know
if
that
hasn't
even
but
I
think
what
what
I
would
I
know
that
ash
has
talked
to
people,
but
I
would
like
to
have
like
a
written
down.
These
are
the
things
that
we're
done
before
right,
and
these
were
the
people
who
were
involved
right.
The
information
has
been
actually
shared
right
and
this
is
written
down
somewhere
and
say
like
this
is
the
state
of
things
at
this
moment.
B
We
understand
it
and
now
we're
going
to
do
the
next
things
and
I
think
this
is
more
of
an
incentive
to
say
like
yes,
we've
actually
like
kind
of
handed
over,
you
know
from
infer
to
to
geo
on
some
level,
and
the
information
is
not
lost
in
between
we've
at
least
met
once
and
talked
about
it.
They
don't
even
know,
if
has
maybe
has
done
that
already
so.
A
Maybe
what
we
do
as
part
of
the
conversations
that
I
have
about
getting
those
diagrams
drawn
up,
I'll
get
the
diagrams
drawn
up,
and
then,
when
we
go
and
share
this
back
with
infrastructure
to
say,
did
we
do
it
right?
We
also
share
with
them.
This
is
everything
else
that
we
have.
This
is
how
we're
going
to
communicate
with
you
like,
rather
than
treating
it
as
a
handover
from
them.
It's
more
of
a
we
take
ownership
of
it.
A
If
they're
not
handing
it
over
we're
taking
it
I
mean
it's
the
same
thing,
but
it's
from
it's
more
from
a
perspective
of
we're.
Gonna
drive
it
from
here,
so
I
think,
leaving
in
his
hand
over
is
fine,
but
I
think
we
just
need
to
treat.
The
issue
is
they're,
not
handing
it
over
we're
taking
it
away.
I
don't
know,
did
does
that
make
sense.
I'm.
B
A
B
No
that's
true,
but
like
us
driving,
it
will
involve
organizing
a
meeting
with
them
right
then
actually
documenting
our
plans
documenting
documenting
the
steps
taken
right,
like
all
of
those
like
I
think
this
is
this
was
more
me.
Thinking
was
like
right.
Let's
make
sure
you
know,
like
infrastructure
understands
what
we
try
to
do.
You
know
we've.
We
are
coming
in
we're
doing
this,
but
also
that
we
understand
you
know
what
they've
done
and
then
we're
not
like
losing
out
on
previous
work
or
like
on
previous
discussions.
Then.
A
Maybe
what
this
should
actually
be,
because
I
think
that
sort
of
handover
has
already
happened
between
ash
and
Devon
I
think
what
this
needs
to
rather
be
is
like
a
checkpoint
meeting
with
them,
and
it
just
needs
to
be
a
checkpoint
that
what
we
plan
to
do
matches
their
expectations.
So
we
show
them
the
documents
we
we
collect.
If
there's
anything
else
that
we
don't
have
from
them.
We
tell
them
how
we're
going
to
keep
them
informed.
Yeah.
B
B
B
We
still
have
a
few
sort
of
small
small
tasks
and
bug
reports
and
I'm
happy
to
do
them,
but
actually
another
thing
that
that
is
in
here
that
I'm,
we'll
probably
after
looking
at
it
now
probably,
which
is
a
little
bit
more,
is
the
verification
work
for
for
uploads,
which
we
haven't
really
started
on
yet
and
that's
okay,
but
I
think
we
should.
We
should
start
on
the
relatively
soon
because
that's
I
think
a
hefty
piece
of
of
work.
So
that's
I
think
the
next
big
thing
that
is
some
sort
of
removing
here.
Okay,.
B
One
one
thing
that
I
sometimes
struggle
with
is
I,
have
I
have
quite
a
few
items
here
in
my
sort
of
long
pile
of
things
to
schedule
that
are
already
sort
of
ready,
and
it's
sometimes
a
little
bit
difficult
to
see.
So
here
at
the
bottom
of
things,
you
know
like
what
is
the
actual
priority
order,
so
are.
C
B
A
B
B
B
So,
for
example
like
this
one
here,
the
SQL
statement-
that
is
something
that
was
customer
relevant
where
this
times
out
but
I,
don't
really
know
exactly
what
the
next
steps
are,
and
you
know
what
work
really
needs
to
happen.
So
I
think
before
the
weekend,
I'm
waiting
to
hear
back
here,
but
that
may
be
something
that
we
need
to
accelerate
based
on
based
of
like
on
the
customer
people
hitting
this.
B
Yep,
essentially
like
two
more
bugs
that
I
think
are
sort
of
in
the
same
category
had
recently
surfaced
because
they
were
hitting
customers.
The
rest
in
in
the
planning
bit
here
is
essentially
because
for
me
to
like
actually
add
somebody
to
to
the
geo,
dr
epic,
so
this
is
a
long
list
of
things
that
I
just
need
to
like
work
through
in
the
next
couple
of
days,
and
then
here
this
is
NFS
object
and
drop.
Artifact
clarification.
This
is
okay,
but
it
depends
on
uploads
refactoring
of
data
types.
B
I
think
we
talked
about
that
last
time
in
solution
very
validation.
This
is
the
like
work
that
that
bus
has
been
doing
guard
rails
for
versions
changes.
This
is
something
I
need
to
speak
to
you
about
with
Larissa
the
selective
sync,
so
we've
shipped
docker
registries
in
12.3
I've
spoken
to
a
customer
about
this,
but
I
haven't
heard
back
yet
so
reach
out
to
Ken
to
do
a
little
bit
more
work
here
and
then
this
is
really
like.
There's
a
bunch
of
things
in
here
that
I
just
need
to
do
to
go
through.
B
My
port
is
pretty
full
at
the
moment.
So
I
have
my
Wednesday
blocked
out
to
work
through
this
and
then
in
problem
validation.
There's
not
much
change
from
the
from
the
last
best
time.
So
I
need
to
schedule
the
customer
interviews
which
I
haven't
done
yet
some
work
on
garbage
collection
in
registries
I
think
this
year,
I'm
almost
done
with,
because
I
think
they
are
technical
sort
of
reasons
for
not
accelerating
that
at
the
moment,
but
I'm,
not
100%
sure
and
some
discussions
I
think
that
happened
in
the
in
there
to
be
cheaply.
Yeah.
B
A
A
Like
reading
results,
a
reading
from
reading,
we
were
travel
again,
read
from
secondary
by
streaming
results
and
considering
how
each
process
event
information
to
use,
inventing
or
messaging
that
it's
its
architecture,
/
technical
debt
work
that
needs
to
take
place,
but
we
need
to
have
a
conversation
in
a
sing
conversation
about
how
to
do
this
and
when
to
do
it
and
what
else
needs
to
be
done
alongside
it,
and
those
conversations
need
to
somehow
be
taking
place
at
on
a
regular,
regular
interval.
I.
B
Agree
I
mean
honestly,
like
one
observation,
I
also
had
is
I
mean
some
technical
debt
gets
taken.
Actually,
when
it's
a
part
of
like
other
other
work,
I,
think
that's
a
preferred
way
of
sort
of
packaging
it,
but
some
other
technical
that
may
never
be
touched
by
itself.
Right
and
I
think
that
that
still
then
accumulates
yeah.
A
And
it's
just
it's
it's
another.
It's
just
a
different
set
of
backlog
grooming
that
has
to
happen.
It's
just
grooming,
the
backlog
that
has
all
of
those
labels
attached
yep,
so
I
actually
need
it's
been
on
my
list
and
I
haven't
gotten
to
it.
We
need
to
raise
a
discussion,
make
sure
about
how
we're
going
to
do
that.
B
No
I
think
that's
true
and
at
the
moment,
like
I'm
I,
think
a
lot
of
this
also
is
early
days.
So
that's
actually
it's
okay,
but
there's
not
that
much
movement
here,
but
I
I
think
in
a
way,
if
I
look
at
like
how
would
I
like
if
you
look
at
the
flow
of
issues,
I
sometimes
find
that
the
the
planning
flow
here
is
a
little
bit
slower
than
I
would
like.
B
But
then
once
it
comes
to
the
point
where,
yes,
we
have
solution,
we
are
like
in
the
breakout
breakdown,
says
all
of
a
sudden
sort
of
accelerates
and
I
found
out
a
lot
of
issues
which
then
get
taken
up
pretty
quickly,
but
that's
also
okay,
anyways.
My
my
roadmap
is
in
disgrace
and
exploded
because
I
I
added
a
lot
of
sub
epics
I'll
fix
that.
B
Well,
let's,
let's
focus
on
on
verification,
so
I
think
that's
that's
quite
quite
nice
and
then
finally,
it's
great
to
see
more
movement
on
the
on
the
billboard
I.
That
makes
me
be
happy
and
I
hope
that
that's
the
same
for
the
team,
because
I
I
feel
it
feels
like
nice
velocity
right.
We
today
we
actually
scheduled
new
things
for
this
column
and
yeah,
see
in
a
week
how
it
goes
and
I.
A
Think
is
I,
think
part
of
that
is
to
do
with
having
to
we've
closed
to
long-running
issues.
The
the
push
messages
on
HTTP
and
the
docker
registry,
replication
and
I
think
once
we
close
that,
like
the
third
and
final
one
about
object,
storage
that
that
opens
up
Gabriel
to
be
part
of
this,
this
small
iterative
cycle
that
we
put
in
place
now
so
hopefully
it
keeps
it
keeps
accelerating.
I
mean
he's
the
last
person
so
then
join
in
on
this
on
this
way,
so
yeah.