►
From YouTube: Geo Scheduling Call 2021-03-23
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
All
right
does
anyone
want
to
share
their
screen
today.
B
Issue,
oh
yeah
group
by
epic.
B
Oh
so
intro
to
recording
this
is
the
geo
scheduling,
call
we're
gonna
go
over
our
build
board,
we
go
by
epic
and
we
start
from
issues
that
are
closed
and
work
backwards
in
the
process
based
on
how
far
they
are
okay,
so
the
first
epic
here
is
self-service
framework
verify
all
blog
replicators.
C
Yeah,
I
can
talk
about
this,
so
I'm
working
on
the
first
issue
in
this.
I
have
an
mr
open,
but
there
is
a
lot
there's
some
more
work
to
do
there.
I
have
kind
of
paused
it
right
now
to
work
on
a
database,
query,
improvement
and
once
that
is
done
I'll
get
back
to
this.
C
Oh
yeah.
I
just
saw
mike's
email.
There
is
a
similar,
mr
that
he's
already
I'm
actually
not
sure
if
he
has,
but
I
think
there's
already
a
similar
mr
to
this
that
he's
working
on.
So
it
should
be
easier
to
get
it
done.
B
Yeah
we're
doing
the
snippet
one.
B
A
Cool
yeah
thanks
thanks
for
yeah,
taking
a
look
at
the
the
db
performance
issues,
we'll
talk
some
more
about
that
after
we've,
we've
walked
the
board.
I
think
I
think
most
of
you
are
aware,
but
we
can
talk
some
more
about
that
yeah
later.
B
B
D
Yeah
see
I
was
talking
about
this
with
tiny
earlier,
I
think
functionally.
I
think
it's
done
so
within
gt.
I've
been
running
through
the
process
a
few
times
and
following
the
documentation,
we
have
a
process
that
starts
and
ends
with
an
upgraded
environment
through
that
follows
our
zero
downtime
docs.
D
The
hardest
part
is
truly
confirming
that,
like
even
running
some
of
our
tests,
it's
hard
to
say
that,
whilst
running
through
the
the
sidekick
upgrade
that
sidekick
is
fully
100,
not
gonna,
throw
any
errors
like.
If
you
don't,
I
mean
it's
easy,
we
can
run
our
ui
test,
but
how
do
we
know
at
the
point
of
the
ui
test
running
that
we're
actually
exercising
the
correct
part?
That's
currently
being
updated?
D
So
that's
the
kind
of
issue
of
actually
saying
that
it's
tested
and
we
have
a
way
of
testing
it,
so
this
is
kind
of
where
I'm
I'm
at
with
at
the
moment.
But
I
say
it's
within
the
get
live
environment
toolkit.
D
B
D
D
B
Yeah,
I
think
so
so
I
think
it
sounds
like
you're
going
kind
of
like
above
and
beyond
this
particular
issue.
Yeah,
like
you're,
concerned
more
about
like
the
whole
epic
in
general,
but
like
this
one,
you've
kind
of
solved
the
problems
basically
and
adding
more
assurance.
That.
B
Is
completely
zero
down
time
that
might
be
more
like
additional
assurance.
On
top
of
this.
D
Yeah,
I
can
raise
some
issues
just
against
the
documentation
like
just
like.
We
call
out.
I
think
that
the
hub
doesn't
truly
do
anything
and
I
think
there
was
a
couple
of
other
minor
issues,
but
nothing
major
in
there
that
breaks
the
process.
D
I
think
we
just
need
to
be.
We
need
to
clarify
a
few
extra
points
in
the
geo
part
of
it,
where
we
don't
quite
align
with
the
the
non-geo
part
where
we
just
don't
we
don't
we
just
say,
update
all
the
other
nodes.
We
don't
say
that
they
have
to
be
done.
Sequentially,
we
just
say
do
this
on
every
other
box
yeah,
which
isn't
correct
so
minor
things
like
that.
D
So
I'll
raise
issues
for
that,
and
then
I
feel
like
we
can
close
this
issue
and
I
can
create
a
new
one
for
the
the
broader
part
of
testing
it.
I
think
that.
B
Makes
sense
if
that's
cool
with.
A
Yeah
that
that
sounds
good,
and
it's
really
exciting
to
see
this
in
in
the
get.
I'm
wondering
if
you
think
we,
if,
if
it
would
be
good
to
like,
do
a
demo
of
this
sometime
and
and
record
that
what
are
your
thoughts
or
is
it
not
quite
quite
there
yet.
D
I
can
do
a
not
a
demo,
but
I
can
do
a
kind
of
discussion
on
what
it's
doing
and
maybe,
if
there's
better
ways
of
doing
what
it's
doing,
but
yeah
like
a
demo
would
be
sure
now.
That's
that
for
three
hours.
A
Yeah,
I
I
think
I
think
something
like
that
would
would
be-
would
be
useful
just
just
for
everybody
to
have
some
visibility
into
what's
what's
happening
there
and
in
case
they
ever
you
know,
need
to
yet
need
to
run
it
for
some
reason
to
test
something,
and
I
think
it'd
be
good
to
share
that
knowledge.
A
Okay,
yeah
I'll
coordinate
with
you
after
the
call.
Thank
you.
B
A
Yeah,
I
couldn't
lose
you
just
yeah
yeah.
I
can
provide
an
update
here
yeah,
so
I
think
yeah
douglas
is
out
this
week.
I
I
don't
think
there's
been
any
any
update
for
the
standby
cluster.
I
think
he
had
had
that
on
hold.
While
he
was
looking
into
the
that
other
s2.
A
What
is
it
yeah
deleting
the
issue
with
deleting
remote
branches
via
the
geosecondary
gabriel,
is,
if
we
go
to
yeah
this
one
yeah
gabriel's
working
on
this
he's
been
refactoring
the
postgres
cookbooks
in
omnibus,
which
has
kind
of
helped
him
to
to
uncover
this
issue.
It's
one
of
those
investigation,
things
where
there's
like
a
really
tricky
order
of
operations.
A
Problem
that's
happening
and
so
he's
he's
kind
of
like
refactoring
these
cookbooks
and
to
help
him
narrow
in
on
on
what's
going
on
here,
and
so
he
he's
made
some
updates
to
that
and
and
seems
to
be
pretty
close
to
to
figuring
out,
what's
what's
going
on
and
and
fixing
it,
but
it's
just
kind
of
taken
a
while
because
of
of
the
nature
of
the
investigation.
A
But
I
think
after
this
it's
kind
of
a
pretty
significant
improvement
into
the
the
setup
of
the
petroni
standby
cluster,
and
then
we
think
that
or
he
thinks
that
the
other
setup
issue,
that's
in
ready
for
development,
may
be
resolved
when
he
when,
after
this
this
issue,
is
this
fixed
one?
Okay
yep.
A
B
E
Yep,
yes,
this
is
going
through
the
review
cycles.
If
you
scroll
down,
let's
see
what
mr,
I
think
we're
on
mr6
now.
Yes,
this
is
a
maintainer
review,
yeah
and
then
it's
just
it's
just
chugging
along
kind
of
lots
of
lots
of
follow-up,
so
I
think
the
most
significant
update
since
the
last
time
I
talked
about
this
was,
if
you
see
the
three
issues
that
are
blocked
by
this
issue
now,
so
the
validation
was
always
there.
E
But
then
we
have
now
kind
of
this
bucket
of
css
exploration,
follow-ups
and
ui
backstage
follow-up,
so
just
kind
of
as
a
symptom
of
breaking
these
changes
up
every
time
you
get
a
review,
you
get
different
feedback
and
different
learning
experience
opportunities,
and
then
they
apply
to
some
of
the
stuff.
That's
already
merged,
so
kind
of
just
striking
all
that
in
there
so
there'll
be
kind
of
like
one.
A
couple
like
minor,
like
weight,
one,
mrs
that'll
kind
of
get
pushed
out
after
this
is
all
done.
E
But
then,
as
far
as
status
wise,
there
was
a
blocker
that
got
brought
up
in
the
front.
End
call
today
that
slowed
the
most
recent
mr
down,
but
that
has
now
been
since
addressed
and
kind
of
opened
up
to
the
broader
front-end
department,
but
yeah
I,
the
rest
of
these
should
go
pretty
smoothly.
I
the
first
couple
were
kind
of
like
larger
in
size,
but
the
rest
had
kind
of
broken
down
to
a
pretty
good
set,
but
yeah.
So
no
updates.
Besides
that
cool.
A
All
right
yeah,
I
I
kind
of
picked
this
one
up,
because
it
was
something
that
I
think
you
know
could
kind
of
be
done
outside
of
the
the
critical
path.
So
just
yeah
sort
of
you
know,
sort
of
in
between
things,
I've
just
kind
of
been
choosing
a
page
and
making
these
these
terminology
updates.
It's
actually
kind
of
interesting,
because
I
think
in
some
cases
it's
really
easy.
A
You
just
replace
node
with
site
and
and
it's
that's
what
it
means,
but
I
think
in
in
some
places
it's
been
a
little
trickier
to
sort
of
like
decide.
If
we're
you
know
talking
about
like
a
single
node
geo
site
or
multi-node
or
or
maybe
the
instructions
could
apply
to
both.
So
I've
tried
to
figure
out
the
best
way
to
sort
of
clarify
that-
and
I
think,
but
it's
taken
a
bit
of
time,
just
to
kind
of
think
about
the
the
right
wording
there.
A
So
it's
it's
one
of
those
things
that
sounds
really
easy,
but
but
actually
you
can
kind
of
run
into
some
some
kind
of
tricky
things
in
in
trying
to
understand
what
the
dots
are
actually
saying
and
and
thinking
about
the
different
cases
that
it
could
apply
to.
But
yeah
made
some
good
progress
had
some
a
couple
of
these,
mrs
merged
already.
B
A
One
other
thing,
yeah
kind
of
something
I'm
noticing,
even
though
we're
changing
this
there
will
still
be
it'll,
still
be
referencing
stuff
in
the
actual
admin
ui.
You
know
where
we're
referring
to
nodes,
when
maybe
we
mean
site
so
we'll
we'll
have
to
follow
up
eventually
with.
I
think
some
changes
in
in
the
ui
as.
B
Well:
okay:
the
next
issue
here
in.
D
D
Yep,
so
I
was
working
through
this
bit
today
and
callum
was
helping
me.
I've
hit
a
bit
of
a
wall
in
that
I,
so
I
really
I've
been
trying
to
set
this
up,
how
I've
set
up
other
kubernetes
environments
like
they
say
you
have
to
have
a
domain
and
you
have
to
have
https,
but
you
don't.
You
can
turn
them
off.
D
D
So
I've
asked
if
that
can
be
fulfilled
now,
like
tax
managers
to
see
if
they
can
do
that,
and
I've
asked
if
they
can
add
a
domain
to
it
as
well.
So
I
can
actually
do
this
because
I've
been
getting
issues
and
it
does
just
not
like
it's
because
I'm
trying
I
haven't
got
those
things.
I
haven't
got
a
domain
to
do
this
as
we
document
so
hopefully
I
can
get
that
soon.
A
Well,
let
me
know
if
you
need
any
help
escalating
that
request.
I
I
thought
we
we
maybe
without
mentioning
it.
This
is,
has
become
a
little
higher
priority
because
of
a
customer
proof
of
concept
and-
and
I
I
just
found
out
that
the
timeline
I
think
is
that
that
this
made
that
this
may,
the
failover
testing
may
be
happening
is
maybe
a
little
sooner
than
than
we
thought
it
might
be
so
yeah.
Just
let
me
know
how
we
can
help
with
that.
D
I
can
seize
you
on
the
the
issue
that
I've
got
where
I've
asked
for
the
project
creation.
Just
you
can
see
as
well.
G
I
did
make
some
progress
last
week.
I
think
I've
tracked
down
most
of
the
spec
failures.
The
remaining
ones
look
appear
to
be
not
related,
but
they
are
consistently
failing
on
the
ci
pipeline
a
little
bit
and
then,
thanks
to
mike,
I
did
get
some
good
pointers
on.
I
was
dealing
with
some
scopes
overriding.
G
B
B
I
was
gonna
say
maybe
just
close
one
yeah
yeah,
okay
anyway,
anyways
yeah.
We
don't
have
to
do
that
here,
but
if
you
think
that
makes
sense
cool
the
next
epic
is
snippet
verification.
B
That's
me,
so
we
recently
released
verification
of
package
files
and
I
I
didn't
finish,
updating
the
developer
documentation
for
adding
verification.
So
I
started
looking
at
that
and
then
I
realized
that
it'd
be
easier
to
write
it.
If
we
have
an
example
that
we
just
add
verification
to,
rather
than
like
package
files,
which
is
like
the
work
had
been
done
all
over
the
place
like
as
part
of
implementing
it
in
the
self-service
framework.
B
So
I'm
doing
the
snippet,
the
main
part
of
the
snippet
verification-
and
I
oh
and
I
just
so
the
tests
passed.
B
So
this
is
now
in
review
rather
than
in
dev,
and
I
think
it's
coming
along.
A
Cool
yeah
thanks
mike
and
yeah,
just
just
wanna
call
out.
I
think
fabian
pointed
this
out
in
the
geo
channel,
but
the
the
package
file
replication
that
that
released
in
1310
was
highlighted
in
the
the
opening
paragraph
of
the
1310
release
post.
So
just
kind
of
highlights
how
important
this
this
is
to
dr
and
just
how
yeah,
how
important
dr
is
that
it
has
that
it
got
highlighted
like
that
in
the
release
post.
A
So
I
think
this
is
yeah
exciting
to
see
us
quickly,
following
up
with
with
more
more
verification,
work,
yeah,
cool.
B
Okay
yeah,
so
this
was
with
jenny,
but
she
had
to
go
on
leave.
B
B
E
D
Look
at
it
okay
and
address
the
feedback
and
test
it
and
check
it.
I
just
haven't
planned
to
do
it
yet
sorry,.
D
If
it's,
what
I'm
thinking
of
because
there
is
I
do
have
I
got
an
email
today
about
an
mr
that
is
literally
got
some
feedback
on
it
for
personal
debits,
so
yeah
so
yeah.
There
is
an
mr
open
for
this
and
I'll
I'll.
Look
at
addressing
the
comments.
B
All
right,
thanks
nick
the
next
epic
we
have
here,
is
secondary
mimicry.
B
It's
it
kind
of
yeah
it
kind
of
blocks
the
the
next
step.
There's
there's
only
two
steps
to
implementing
the
mvp
for
that
epic.
So
this
is
the
first
step
and
it's
not
it's
not
too
big.
I
just
need
to.
I
just
need
to
get
through
it
and
add
the
end
point,
and
then
creepy
is
going
to
work
on
the
workhorse
side
to
implement
that
feature
so
yeah.
I
just
pushed
an
update
and
I
think
I
should
be
able
to
get
it
into
review
this
week.
A
Well,
do
we
have
the
other
workhorse
issue
on
the
board
yet,
or
is
that?
Is
that
ready
to
be.
A
B
Okay,
we
could,
like
I
said
it's
kind
of
blocked
by
that
one.
B
Should
we
add
it
to
just
scheduling
or
something.
A
Sure
yeah
that
sounds
good
yeah.
I
I
I
don't
think
this
is
one
of
those
ones,
we'll
we'll
necessarily
lose
track
of
or
sorry
not
scheduling,
ready
for
development,
yeah,
yeah
yeah
with
geoactive
yeah
perfect.
Thank
you.
A
B
Okay
and
that's
it
for
the
epics
wow,
we
didn't
have
anything
close
to
this
one.
There
was
a
family
and
friends
day
last
week.
A
D
A
B
B
So
so
jenny
posted
that
when
the
personal
snippets,
mr
that
we
already
talked
about,
is
merged-
and
this
can
be
closed.
B
Would
it
be
worth
like
adding
this
issue
link
into
here
nick
whispering.
D
B
B
Okay,
so
yeah
this
issue
is
it's
possible
for
registry
records
to
get
stuck
thinking
like
that,
they're
being
synced
currently
like
if
you,
but
if
you
kill
sidekick
or
something,
then
they
can
get
stuck
there.
B
So
I
know
valerie
had
a
merge,
request,
open
and
it
seems
to
be
in
review.
Remove
this.
We
only
need
those
on
the
issues
right.
The
workflow
label.
B
Oh,
this
was
I,
I
have
a
merge,
request
open
to
change
some
developer
guidelines
or
add
something
to
the
developer
guidelines.
That's
just
something
I'm
doing
on
the
side.
It
is
in
review.
I
just
need
to
probably
ping
somebody
and
then
in
dev
we
have
the
leading
remote
branches.
A
Yep
yeah,
I
think
valerie
has
taken
this
on.
I
haven't
seen
in
mr,
yet
I
think
it's
it's
still
he's
still
working
on
it.
He
picked
it
up
from
douglas.
Who
was
doing
the
investigation
before
I
think
we
could
probably
ping
valerie
for
for
an
update
here.
B
B
And
that's
it
for
things
in
development
or
beyond,
so
yeah
nick.
Do
you
want
to
take
ready
for
development.