►
From YouTube: Geo Scheduling Call 2020-07-14
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
C
B
Last
part
to
make
the
hash
table
the
single
source
of
truth
for
our
projects
and
weeks
it
was
murdered
yesterday.
So
now,
I
enabled
a
feature
flag.
Is
this
behind
if
your
flag,
Randy
with
his
own
station
and
I,
run
some
tests
and
everything
is
working
as
expected?
I
own
a
big
metaphor
for
July
13
that
Jim.
A
B
D
D
E
A
Cool
so
yeah,
and
so
with
like
the
new
blob
data
types
we
have
like.
We
have
I
think
issues
in
those
epochs
to
add
like
the
details
ListView,
but
this
should
make
that
either
a
no
op
or
fairly
straightforward
to
do
right
is
there
any
additional
work
there
will
now
or
will
that
just
look
kind
of
come
out
of
the
box?
Well,.
A
D
A
D
A
A
A
A
D
A
So
yeah
I
think-
and
we
just
went
through
this
with
I-
think
a
bug
fix
that
Douglas
merged
in
last
week.
Yeah,
my
understanding
is,
is
like
you
can
add
those
pick
labels
and
if
they
decide
to
create
a
patch
release,
they
should
get
included
but
like
if
we
want
to,
but
then
they
might
not
create
decide
to
create
a
patch
release
and
so
like.
A
If
we
really
want
to
try
to
advocate
for
one,
we
should
open
that
issue
and
and
specifically
ask
for
it
so
I
guess
it
kind
of
depends
on
how
I
guess
how
yeah
like
how
strongly
you
want
to
advocate
for
for
a
release
like.
Are
we
okay,
just
kind
of
see?
You
know
if
there
is
one
that
it
gets
in,
or
do
we
want
to
like
actually
try
to
get
them
to
to
make
one.
D
A
They
were
saying
that
they
weren't
really
considering
13
no
and
they
they
it
did
it
end
up
doing
it
and
I
think
had
a
couple
items
in
there,
but
I
think
at
first
they
were
saying
like
it
might
not
be
likely
unless
there
was
more
more
demand
or
if
we
could,
unless
we
gave
him
a
good
reason.
Okay,
okay,
cool
yeah,
thanks
for
getting
that
in
and
and
opening
the
back
port
request
as
well.
A
A
F
F
A
Cool
yeah,
thanks
for
taking
care
that
I
saw
some
of
that
discussion
with
Stan
and
yeah.
There
was
yeah.
It
was
a.
It
was
an
interesting
good
back
and
forth
thanks
for
yeah
getting
this
fixed
yeah,
as
anyone
have
any
other
questions
about
this
one
before
we
move
on
all
right,
go
to
checking
that
geo
replication
verification
is
up-to-date.
A
Yeah,
let's
see
creaky
had
had
posted
some
updates
here
for
these
items.
So
thanks
for
that-
and
she
says
this
automated
check
is
now
part
of
the
promotion
command,
so
yeah
and
I
think
that
was
one
that
we
we
had
talked
about
trying
to
assign
before
for
review
before
she
got
back.
So
thanks
for
for
doing
that,
helping
that
along
as
well
Alex,
no
problem
yeah,
so
I
think
this
is
I.
Think
the
only
thing
this
kind
of
takes
care
of
the
release
post
item
for
for
this
check,
I
think
there's.
The
release.
A
E
E
Geo
sightings
forums
that
you
know
I
talked
about
a
couple
of
times
so
that
this
one
took
a
while
to
get
in,
but
we
I
rewrote
the
form
in
view
JavaScript
and
we
got
rid
of
the
old
Hamel
form,
which
gave
us
some
increased
flexibility
and
it
also
added
validations
to
the
forum.
So
now,
hopefully,
things
will
be
better.
There
also,
the
the
front
end
pretty
evaluates
the
IP
format.
So
what
should
this
help
the
users
from
submitting
like
incorrect
posts
yeah?
And
then
it's
all
done
for
the
API
now,
instead
of
the
rest
controller.
E
A
A
Yeah
I
I
think
I
think
that's
what
it
was
also
I
just
wanted
to
point
out
was
this.
We
were
kind
of
talking
about
this
example
of
you
trying
out
like
asking
the
same
reviewers
to
review
some
M
ours
in
like
a
series
of
like
related
M,
ours
and
I.
Think
this
was
kind
of
an
example
of
where
you
did
that
and
got
things
moving
fast.
E
Yes,
yeah
those
last
three
they're
geo
settings
form
that
foundations
and
revoke
code
nicolai
are
Niccolo
was
the
one
who
did
all
of
all
three
of
those.
It's
just
the
back
into
maintainer
ended
up
merging
it.
Oh
yeah,
so
those
last
three
went
in
really
quickly
because
those
last
three
I
used
the
same
set
of
reviewers,
which
is
really
nice
yeah.
A
E
E
We
got
this,
and
so
now
this
kind
of
goes
in
tandem
with
the
work
that
we
talked
about
with
Mike
did
just
recently
about
not
having
to
create
all
those
files.
The
front
end
also
was
gonna
at
the
time.
Gonna
need
a
new
file.
Every
time
a
new
data
type
was
traded
to
fetch
the
data,
and
so
now
we
have
a
generic
way
to
fetch
the
data
as
well
trace,
marginalization,.
A
A
Great
thanks
yeah.
It's
really
neat
to
see
like
as
a
result
of
all
of
all
the
work
that
you've
been
doing
here
now
now
being
able
to
see
you
be
able
to
kind
of
like
remove,
remove,
duplicated
or
no
longer
used
code.
Yeah
all
right,
Jenny
update
on
the
bus
configuration
for
get
labs,
geo
containers,
yeah.
A
A
It
was
yeah
kind
of
about
answering
these
questions
about
if
we
need
tests
for
additional
data
types
right,
yeah,
yeah,
thanks
for
thanks
for
this
response,
I
I
wasn't
really
aware
of
all
these
open
of
this
epic
and
that
was
open
so
that
that
really
or
yeah
this
improved
QA
and
testing
epic.
So
that
was
good
to
know
about
all
right,
we'll
go
to
the
in
Review
column.
So
I
think
this
one
just
got
added
put
in
review
by
tone.
A
So
that's
a
external,
mr
diffs
and
I
think,
will
common
theme
we'll
see
with
some
of
these.
Is
there
with
these
data
types?
Is
they're
they're,
all
sort
of
in
review
or
close
to
in
review,
and
I
think
there's
a
lot
of
collaboration
happening
here.
Has
anyone
have
anything
they
wanted
to
mention
about
external,
mr
diffs.
A
I
think
it's
really
close.
We've
had
I
think
several
like
a
Mars
like
smaller,
either
like
reef
actors
or
documentation.
Mrs
come
come
out
of
the
exploration
that
tone
has
has
done
there.
So
I
think
that's
been
super
helpful
and
it'll
be
nice
to
yeah
to
see
this
to
see
this
across
the
finish
line,
so
to
speak,
yeah,
maintenance,
mode
application,
settings
field,
I
think
this
is
very
close
as
well.
I
think
it's
just
been
has
to
ask
for
a
back-end
maintainer
review,
so
this
this
seems
very
close
as
well.
A
H
Know
that
they
are
suffering
from
a
pretty
serious
shortage
of
maintainer,
so
I've
noticed
that
just
putting
ready
for
a
review
on
there
means
that
it's
probably
gonna
sit
there
for
a
long
time,
just
because
their
maintainer
workload
is
so
large.
So
pretty
much.
The
only
way
I've
found
to
have
someone
review
omnibus
stuff
right
now
is
to
pick
either
ping
someone
directly
or
paying
a
group
label
that
they've
got
an
arm
embrace
like
the
district
leaders
paying
the
whole
distribution
team.
Someone
will
pick
it
up,
but
I've
been
I.
H
A
Yeah
I
think
that's.
That
seems
like
a
good
approach.
I
mean
they
are
pretty
responsive,
but
I
I
do
agree
that
it
seems
like
yeah,
it's
hard
to
know
exactly
with
this
label
workflow
like
when
you
know
if
it
might
slip
if
if
they
are
really
busy
with
reviews,
so
I
think
that's
a
good
approach
to
take
for.
For
these
items.
I
heard.
H
A
H
H
Hopefully,
that'll
get
a
rubber-stamp
tomorrow
or
something,
but
if
not,
then
I'll
keep
fixing
things
until
it
does,
but
I
think
it's
pretty
close
I
do
need
to
file
some
follow-ups
because
there
are
a
couple
of
I
I
wasn't
entirely
sure
which
things
got
included
in
this.
So
I
am
gonna
file,
follow-ups
to
add
the
metrics
and
finish
all
the
other
things.
A
That
sounds
good
yeah
I
did
want
to
kind
of
towards
the
end
of
the
call
go
over
our
13-3
planning
issue
and
I
think
some,
some
of
the
follow-up
that
we
can
have
some
little
discussion
about
what
the
follow-ups
there
are
and
that
might
be
it,
but
yeah
it
seems
like
either.
We
need
to
kind
of
specify
that
in
these
issues
or
break
them
out
so
yeah
thanks
for
that
update
yeah,
all
of
the
these
data
types
seem
close.
A
I
think
you
know
certainly
don't
think
we
should
like
unnecessarily
stress
ourselves
out
and
work
super
overtime
trying
to
get
them
in
for
the
release,
but
they
do
seem
like
they.
They
certainly
have
a
chance
of
making
it.
So
it
would
be
good
to
see,
but
if
not
I
think
it
would
still
yea
be
good
to
try
having
them
wrapped
up
like
soon
so
that
we
so
that
they're
not
so
that
we
just
kind
of
have
it
out
of
the
way
and
can
can
move
on
to
other
things.
A
H
D
A
A
We
feature
flag
package
files
through
to
kind
of
implementing
it
in
multiple
iterations
and
sort
of
you
know
doing
this
for
the
first
time
and
and
so
so,
maybe
in
creating
like
the
follow
up,
epics
Fabian
was
just
kind
of
assuming
that
we
that
we
were
confident
that
we
didn't
need
a
feature
flag,
but
I.
Think
if
there
is
enough
concern,
maybe
we
do
want
to
consider
that,
but
for.
D
Or
even
defaulted
to
true,
you
know
at
least
then
you
have
something
to
switch
it
off
or
whatever
yeah.
That
would
be.
Okay,
I!
Think
oh
I
have
another
question:
does
anybody
know
when
the
last
day
will
be
to
get
stuff
into
the
release
or
like
ish
like
likely
to
be
last
day.
A
H
A
H
If
something
goes
wrong,
at
the
very
least,
we
can
turn
it
off
and
if
nothing
goes
wrong,
we
can
just
remove
it
in
the
next
release
and
no
one
will
be
the
wiser,
but
we
can
still
look
like
I
feel
like
if
we
release
it
if
we
like,
if
we,
if
we
want
to
quote
unquote,
release
it
this
this
milestone
first
stuff
like
we
really
need
to
well
I,
don't
think
we
can
default
it
off
right,
because
otherwise
people
won't
actually
Shep
it.
But
I
don't
know.
Okay,.
A
A
I,
don't
know
cool
yeah,
I.
Think
that's
yeah,
thanks
for
bringing
that
up,
Mike
makes
sounds
like
a
good
idea
and
yeah.
So
if
no
one,
no
one
else,
I
guess
is
a
post
that
we
can,
after
this
just
chime
in
comment
on
these
issues
and
kind
of
maybe
just
just
bring
up
that
this
was
discussed
in
the
scheduling,
call
and
to
suggest
to
add
the
feature
flag
defaulted
to
to
true
there.
How
does
that
sound.
H
D
So
I,
since
were
very
close
to
the
last
few
days
that
we
can
get
something
into
the
release.
I
separated
this
into
two
parts
and
I'm
working
on
making
registry
consistency.
Worker
do
the
right
thing
so
that
even
if
the
create
events
come
through
and
you
know
the
secondary
tries
to
sink
and
it
fails
or
whatever.
Eventually
the
situation
will
correct
itself
and
yeah.
That's
the
more
that's
the
more
important
part,
so
I
have
an
Mr
in
review.
A
Okay
sounds
good,
I
guess
I'll
just
want
to
keep
an
eye
on
that.
Yeah
I
think
especially
around
this
time
to
like
a
since,
we
have
so
few
database,
maintainer
Zhai
I,
do
sort
of
wonder
you
know
if
there's
gonna
be
a
flood
of
reviews
for
for
him
to
look
at
so
might
just
be
something
to
keep
an
eye
on
yeah
cool
yeah,
thanks
for
ya,
gettin´
yeah,
trying
to
figure
out
like
what
was
what's
essential
to
get
into
the
release
and
getting
that
getting
that
interview
so
quickly.
D
A
G
A
A
A
This
small
moving
the
rake
geo
test
to
the
get
lab
geo
under
get
web
geo
to
try
to
get
that
in
before
the
release
and
then
and
then
he
still
has
to
do
some
investigation
on
this
bug.
I
think
yeah
I
think
we've
had
this
year
for
a
bit
and
he
was
out
for
a
week
a
while
ago
and
I
think
has
still
kind
of
been
dealing
with
some
computer
issues
and
trying
to
get
a
new
setup
going.
A
G
They're
related
so
yesterday,
Alex
Knight
an
upgrade
from
twelve
ten
to
thirteen,
and
we
had
some
additional
monitoring
and
some
real-time
feedback.
This
time
saw
some
interesting
things,
so
I
think
there's
about
three
areas.
We
want
to
look
at.
I
have
two
open
issues
for
those,
but
once
those
are
opened,
but
at
least
need
an
engineer,
because
it's
involves
I
can't
make
the
reconfigure
step
and
the
hub
step.
So
yeah.
H
G
A
D
H
A
E
So
I
missed
you
payment
a
couple
of
these
kind
of
older
issues
so
that
I
found
that
this
one
actually
still
is
a
problem.
So
it's
a
really
simple
fix,
so
I
actually
have
it
done,
but
I
am
actually
while
I'm
in
there
kind
of
refactoring
a
couple
of
the
legacy
things
can
I
get
him
up
to
date
since
I'm
already
touching
the
file
and
then
yeah.
E
A
Yeah
this
was
this
kind
of
came
about.
I.
Think
we've,
we've
discussed
this
a
bit
in
the
planning
issue
that
yeah
I
think
there's
that
there's
were
we're
waiting
on
some
some
designs
and
and
sort
of.
In
the
meantime,
there
and
that'll
be
a
big
project
once
once
it's
ready
for
for
Zack
to
work
on,
but
in
the
meantime
there
there
is
self
service
framework
stuff
to
do
but
they're
also,
some
like
back-end
dependencies
on
that.
A
So
is
trying
to
kind
of
go
through
and
see
if
there
any
like
standalone
front-end
issues
that
that
might
be
good
as
to
kind
of
queue
up.
Well,
you
know
if
there
is
any
time
in
between
these
items,
so
yeah,
thanks
for
looking
into
it
and
and
I
think
it's
always
fun
to
go
close
out
issues
that
have
been
open
for
over
six
months
to
a
year,
so
yeah.
G
I'm
so
glad
it's
some
options:
ticket
love,
QA,
where
you
can
run
it
locally
to
spin
up
to
containers
and
configure
it
for
geo
and
then
leave
those
those
containers
running
but
not
run
the
tests.
So
that's
something
will
be
helpful
for
the
quality
team.
When
we're
on
on
call,
they
don't
have
to
wait
for
me
to
look
into
it.
There's
a
lot
of
people.
They
don't
have
it
set
up
on
JDK,
so
good.
D
A
A
Great
and
I've
got
these
next
two
I'll
try
to
summarize
them
kind
of
quickly
this.
This
one
is
this,
this
one
kind
of
caught
me
by
surprise.
We
had
it
in
the
13
two
planning
issue,
but
I
think
it
was
still
labeled
group
distribution
and
so
I
wasn't
really
looking
at
it
when
I.
You
know
in
my
filter,
deliverables
view
and
hadn't
really,
and
we
didn't
have
it
on
the
Billboard.
A
So
basically,
we
want
to
just
verify
that
geo
works
with
with
patron
Ian
and
Postgres
11,
since
patronise
is
going
to
be
it's
been
available
in
omnibus
I
think
since
12:10,
but
we're
actually
going
to
be
announcing
that
omnibus
supports
it
in
13.
So
so
it's
kind
of
was
kind
of
like
a
last
minute.
You
know
have.
Can
we
verify
this
and
so
I
I
had
some
time
to
look
at
it.
I
was
able
to
use
Orchestrator
to
quickly
set
up
a
primary
cluster
that
was
managed
by
rep
manager
and
switched
that
over.
A
So
so
that's
what
I
kind
of
took
on
this
issue
as
well,
because
we
had
already
had
a
an
issue
for
moving
a
deployment
from
rep
manager
to
patronise
so
kind
of
I
guess
in
testing
it.
This
way,
I
kept
kind
of
able
to
I
guess
cover
a
couple
different
of
these
verification
issues.
It's
not
quite
the
same
as
a
fresh,
install
but
I
think
there
was
some
general
agreement
that
we
could
probably
test
what
we
needed
to
going.
A
This
route
and
Jeff
like
I,
was
able
to
get
it
to
work
and
just
a
main
issue
that
I
ran
into
is
that
Patroni
deletes
any
replication
slots
that
are
not
that
don't
belong
to
members
of
the
cluster.
So
that's
that's
definitely
gonna
be
up,
but
you
can
create
this
slot.
But
if
you
restart
Patroni,
it's
gonna,
it's
gonna
delete!
That's
that
slot,
so
we're
just
kind
of
waiting
on
someone
from
distribution
to
weigh
in
on
what
they
think
is
a
good
way
forward.
A
I
think
one
option
is
that
Patroni
does
allow
configuration
of
a
permanent
slot,
so
we
could
look
into
trying
to
support
that,
but
yeah
I
think
I.
Think
beyond
that
testing
sort
of
I
think
not
really
I,
think
sort
of
above
my
level
of
knowledge
here
about
what
the
best
way
to
proceed
is.
But
the
testing
was
very
was
very
insightful
and
and
I
learned
a
lot
doing
it
yeah
so
I
think
I've
picked
some
people
but
yeah.
If
anyone
has
thoughts
on
this
feel
free
to
take
a
look
and
and
chime
in
on
these.
A
Let's
see,
let's
see,
aqua
tea
is
working
on
the
vulnerability,
export
replication,
I
think
that's
pretty
close
to
review
as
how
she
reached
out
to
Alex
and
tone
for
some
to
pare
on
that.
So
I
think
that's
moving
along.
Maybe
since
it's
not
a
review
that
might
be
the
one.
That's
that's
at
least
likely
to
to
make
the
release
out
of
the
three.
B
F
F
A
A
Kind
of
in
the
same
place
that
we
were
last
week,
we've
we've
moved
quite
a
bit
over,
so
we
can
fill
it
up.
I
wanted
to
I
brought
a
couple
items
in
to
open
that
I'll
bring
over
specifically
just
these
items
to
finish
up
the
additional
data
types
of
getting
them
hooked
up
in
the
front
end
and
I
think
we
may
need
to
kind
of
look
at
these
issues
and
see
if
we
need
to
split
them
out
more
because,
if
I'm
understanding
correctly,
if
we
just
look
at
say
this
terraform
state
one
as
an
example.
A
We're
talking
about
adding
the
progress
bar
in
the
details
view,
but
my
understanding
is
maybe
the
details
of
you
might
just
kind
of
be
there
now
with
the
work
that
that
Mike
and
Zach
have
done
to
generalize
things,
but
yeah
I
mean.
Is
that
correct,
or
is
there
some
some
more?
That
would
need
to
be
done
there?
The.
D
D
A
D
H
A
Yeah
yeah,
so
you
know
make
sure
we
note
that
for
all
the
other
data
type
issues
as
well-
and
you
know
I-
think
if
yeah
this
is
that
it
it
would,
it
would
be,
of
course,
great
to
make
the
release,
but
if,
if
you
know
if
it
would
be
better
to
make
sure
we
release
with
all
of
these
concerns,
addressed
I.
Think
so,
thanks
for
raising
that.
A
Yeah,
so
so
I
also
added
I
think
this
is
maybe
the
first
one
that
we
can
work
on
for
snippet
replication,
but
please
weigh
in
on
the
planning
issue
or
just
anywhere
if
you
think
it
should
be
something
else.
I'd
like
to
yeah
start
adding
one
or
two
of
the
snippet
replication
epic
items
to
the
ready
for
development
column.
A
I.
Think
this
final
confirmation
for
the
promotion
script
came
out
of
the
pre-flight
checks,
work
and
is
kind
of
a
small
follow
up.
We
have
a
couple
of
small
bug:
investigation
items
but
yeah,
that
is
the
current
state
of
ready
for
development.
I
didn't
move
this
run
book
style
documentation
to
the
top.
We
were
hoping
to
get
to
that
and
13-2,
but
I
think
we've
also,
we
kind
of
acknowledged
that
it
might
there's
two
of
these
types
of
documentation,
issues
that
are
in
the
thirteen
three
planning
issue.
A
A
What,
as
it's
kind
of
a
very
different
I,
guess,
type
of
thing,
from
what
we've
been
working
on
so
I
didn't
want
to
just
put
that
to
the
top
to
get
some
attention
on
it,
but
other
than
that.
The
only
other
things
that
I
think
we'll
want
to
be
paying
attention
to
trying
to
start
making
progress
on
are
these
in
13-3
of
post
quest
12
will
be
available
in
the
thirteen
two
released,
so
we'll
want
to
verify
agio
installed
with
that.
A
So
it's
block
right
now,
but
I'll
once
thirteen
two
is
actually
released.
We
can
start
working
on
that
and
then
just
some
more
of
these
testing
issues
like
testing,
giddily,
cluster
and
and
then
starting
to
look
into
seeing
if
we
can
configure
a
Patroni
standby
cluster
on
the
secondary
I.
Think
I
will
be
other
big
priorities
for
four
thirteen.
A
Let
us
know
if,
if
there's
anything
that
we
should
remove,
because
maybe
it's
it's
doesn't
seem
feasible
for
for
the
release
or
maybe,
if
there's
anything,
we
should
add
that
we're
overlooking
and
all
I
think
the
plan
will
be
to
try
to
record
a
kickoff
video
in
the
next
day
or
two
I
guess
I
have
to
double-check
with
Josh
and
see.
If
see.
If
the
plan
was
for
me
to
do
that
or
if
he
had
someone
else
in
mind,
but
yeah
I
think
all
in
all
the
the
plan
is
looking
pretty
solid.