►
From YouTube: Geo Scheduling Call 2020-10-20
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
It's
yeah
there's
a
group
by
option
next
to
add
list
there.
Sorry,
I
was.
B
Messing
with
the
zoom
control.
B
B
Okay,
so
in
the
closed
column,
thanks
nick
for
suggesting
that
this
should
be
closed,
it
should
be.
I
had
put
resolves
and
then
the
issue
number
but
apparently
resolves
is
not
one
of
the
keywords
so
yeah.
That's
that's
closed.
It
was
kind
of
like
a
long-running
thing.
I
was
doing
on
the
side
so
happy,
that's
close.
Just
just
improving.
C
The
query
is
it,
you
know
sorry,
just
off
topic.
Does
anyone
know
if
there
was
an
issue
out
there
that
changed?
Those
keywords
because
closes
doesn't
work
either
anymore
and
it's.
I
want
to
know
what
why
and
maybe
like
what
I
should.
It
is
a
little
frustrating.
I've
been
like
finding
issues
all
over
the
place
that
weren't
closing.
B
I
don't
know
that
sounds
like
a
regression
or
something.
C
Yeah,
I'm
not
sure
so
I
don't
know
I
just
wanted
to
call
it.
It
seems
like
maybe
those
keyboards
aren't
doing
what
they're
intended
to
do
anymore.
Also,
if
you
like,
if
you
used
to
create
a
branch
with
your
issue
number
in
it
at
the
very
bottom,
the
mr
template
would
default
and
say
closes
now.
It
just
says
related
to
so
they
like
removed.
That.
B
Logic,
actually,
I
do
remember
talk
about
making
it
like
the
default
behavior
in
for
git
lab
for
like
get
lab
org,
maybe
or
something
like
like
people
wanted
to
stop
things
from
closing
automatically.
So
maybe
that's
maybe
that
was
intentional.
I
don't
know.
B
This
one
is
something
that
tone
is
working
on.
It
was
just
kind
of
follow
up
from
the
merge
request.
B
Diffs
replication,
epic
and
I
am
currently
reviewing
his
merger
quest
and
it's
not
too
big,
but
it's
a
small.
A
Yeah,
I
can
talk
about
this
one
real,
quick,
so
yeah,
this
proof
of
concept
for
a
single
command
to
promote
a
secondary
to
primary
was
merged.
It
works
for
single
node
secondaries
and
douglas
also
followed
up
with
a
little
piece
of
documentation
for
for
single
node
secondaries.
A
I
went
ahead
and
took
one
of
the
issues
there's
a
bunch
of
issues
in
that
epic
kind
of
listing
out
the
different,
the
different
node
types
to
support,
and
I
from
what
I
understand
the
work
to
extend
that
support
should
should
apply
to
all
of
those
and
then
it's
just
kind
of
a
matter
of
going
down
and
checking
off
that
list.
A
So
if
we
look
at
the
billboard
and
just
the
open
column
for
that
epic,
I
took
one
of
those
node
one
of
those
issues
to
support
a
node
rails
application
node
and
put
it
into
open
just
to
signify
the
the
next
step
in
this.
So
I'm
not
sure
if
that's
the
appropriate
issue
to
have
next,
but
just
wanted
to
have
something
there
to
kind
of
show
that
extending
that
support
is
is
next
in
the
epic.
A
Yeah,
I
I
just
added
like
a:
we
have
an
epic
for
it,
but
we
didn't
have
any
issues
in
it
so,
but
it
is
an
upcoming
priority,
and
so
I
just
have
created
a
placeholder
issue,
but
I
think
it
would
be
great
yeah.
I
think
we
could
use
in
an
engineering
owner
for
the
epic
and
I'm
not
really
sure
and
then
to
help
break
down
what
needs
to
be
done.
A
I
I
don't
really
have
a
good
sense
of
like
if
this
is
something
that
can
all
be
done
in
one,
mr,
if
there
will
be
multiple
steps
to
it,
but
if
someone
wants
to
assign
themselves
and
then
flesh
out
the
the
epic
that'd
be
awesome
yay
thanks
alex.
I
see
you
raise
your
hand,
okay,.
A
Yeah
I'll
just
one
other
thing,
I'll
also
note
that
moving
these
is,
of
course,
we
were
already
talking
about
doing
it,
but
I
think
it's
it's
even
more
important
to
prioritize
now
that
we've
determined
that
moving
existing
data
types
over
to
the
self-service
framework
is
a
blocker
for
some
of
the
redesigned
stuff
that
we
want
to
do
some
of
the
redesign
that
we
want
to
do
for
the
replication
views.
A
So
we
were
already
prioritizing
it,
but
I
think
we'll
just
want
to
keep
that
in
mind
and
make
sure
fabian
knows
that
that
those
should
continue
to
be
prioritized
highly
if
we
want
to
save
ourselves
some
work
when
it
comes
to
the
redesign.
B
Yeah,
thank
you
that
makes
sense,
yeah
just
thinking
out
loud,
like
moving
lfs
files
to
it's
going
to
be
the
same.
It's
going
to
start
with
the
same
amount
of
effort
as
it
is
to
add
something
because
you
got
to
add
all
the
ssf
code
for
lfs
files.
B
B
A
Yeah
yeah
sounds
like
maybe
even
a
little
more
involved
than
just
adding
a
new
data
type
since
it's
since
it's
not
just
a
matter
of
following
the
yeah
in
some
ways:
yeah,
okay,.
B
Cool
thanks
so
we're
on
to
snippet
replication.
B
B
We
were
going
to
remove
it
from
quarantine
in
a
separate,
merge
request
that
one
hasn't
gone
in,
especially
because
over
the
weekend
staging
was
broken
and
I
think
it's
working
now.
So
maybe
that
can
progress
again,
but
yeah.
The
thing
is
fixed.
I
believe
it's
just
the
test
is
still
quarantined.
So
that's
all
that's
happening
in
this.
B
I
don't
know
where
the
api
thing
is:
oh,
it's
in
ready
for
development,
so
nobody's
working
on
that.
Yet.
A
Yeah,
I
can
talk
about
this
one
so
yeah
the
the
standby
cluster
work
merged
and
I
think
it
yeah.
I
think
it's
made
the
release.
So
that's
exciting.
A
I
we
didn't
really
merge
it
with
with
docs,
which
I
I
think
is
something
that
we
we
can
definitely
do
do
a
better
job
of
keeping
an
eye
on,
but
in
the
future.
But
I
think
in
in
this
case,
gabriel
is
going
to
work
on
some
minimal
docs
in
in
the
geo
admin
docs.
So
I
guess
that's
a
separate
repo
anyways
and
then
we'll
point
to
that
and
get
the
release
posts
merged.
A
I
kind
of
held
off
since
we
needed
that
documentation
link
so
we'll
we'll
merge
it
with
some
kind
of
minimal
docs
that
say:
okay,
assuming
that
you,
you
know,
you've
set
up,
console
and
a
patrony
cluster,
and
all
that,
like
here's,
the
configuration
to
enable
a
standby
cluster
and
then
we
can,
we
can
go
into
more
more
detail
in
the
future.
I
think
maybe
a
walk-through
video
would
be
would
be
nice
to
sit
down
and
do
at
some
point.
E
Yeah
yeah,
I
could
talk
about
maintenance
mode.
I
am
done
with
the
work
on
the
saying,
a
banner
message.
That's
the
other
issue
to
the
right.
I
just
have
to
assign
it
for
a
review
and
the
code
is
there.
E
I
started
working
on
the
other
issue,
the
one
on
the
left,
which
is
about
blocking
non-get
http
requests,
and
I
dug
a
bit
more
into
the
other
discussions
that
happened
around
which
it
was
also
participating
in
one
and
looks
like
there
are
a
lot
more
things
to
consider
other
than
just
the
non-collections
requested.
For
example,
if
you
block
all
of
these
requests,
the
admin
cannot
sign
in.
They
cannot
test,
for
example,
if
everything
is
going
to
sign,
so
I
saw
that
there
were
some
discussions
around
this
already
a
year
ago.
E
B
B
E
B
E
Yeah,
so
once
we
have
something
more
done
for
government
mode,
I
will
start
documenting
it
so
that
they
have
something
to
release
for
this
release,
but
I'm
not
working
on
this
right
now
I
disappeared.
The
other
issue
with
one
conversation,
that's
going
on.
B
B
So
this
is
like
continuing
that
effort
and
I
started
to
work
on
automatically
verified
packages
on
secondaries
and
while
doing
that,
I
realized
that,
like
the
background
workers
and
like
how
that
happens,
it
can
it
can
be
reused
across
primary
and
secondary.
So
I
also
took
this
issue
assigned
it
to
myself
ensure
package
file
checksum
on
primary
yeah,
so
I'm
kind
of
I've
been
working
on
that.
I
hope
to
get
some
mrs
up
for
for
those
issues
this
week.
B
B
Yeah
I
did
see
there
were
some
failures
over
like
over
the
weekend
yeah,
but.
B
I
know
I
know
I
I
I
found
one
like
unrelated
issue
that
was
kind
of
breaking.
B
I
think
the
the
secondary
being
set
up
in
the
qa
tests,
or
at
least
part
of
it
like
having
to
do
with
repositories.
So
I
think
that
needs
to
be
fixed
for
some
of
those
failures
to
go
away,
but
I
don't
know
if
that's
all
of
them.
A
Okay,
yeah:
I
do
see
that
this,
mr
for
adding
the
tests,
is
merged.
So
I
just
had
this
question
to
jenny
if
it,
if
it's
okay
to
close
but
yeah,
probably
good
to
leave
open
until
we
can
figure
out
the
staging
yeah
as
well.
Yeah.
B
Actually,
those
are
probably
the
the
staging
failure
that
accrety
fixed
by
restarting
the
secondary
it
just
wasn't
working.
It
was
showing
a
blank
page
yeah.
B
B
B
Okay,
so
adding
an
end-to-end
test
for
personal
snippets
replication
is
blocked
on
that
other
test
being
quarantined.
So
I
think
that
should
be
unlocked
soon.
B
In
the
mr
but
like
I
said,
the
tests
were
breaking
due
to
possibly
unrelated
things,
so
I'm
gonna
follow
up
there
or
maybe
jenny
will
before
I
do,
and
hopefully
that
will
close
okay.
So
that's
it
for
test
caps
in
geo
group
improve
ui
ux
on
administrator
panel.
B
C
B
C
Yeah
yeah,
so
this
one's
ultimately
blocked
kind
of
based
on
what
nick
alluded
to
a
little
earlier.
Just
the
fact
that
we're
kind
of
in
this
weird
space,
where
you
know
we
support
different
feature
functionality
between
the
different
replica
replicable
types
and
before
we
start
going
down
this
rabbit
hole
of
adding
all
these
features
and
all
this
new
stuff.
I'd
really
like
to
start
seeing
that
we
can
get
everything
kind
of
into
self-service.
C
That
way,
we
could
build
this,
build
this
functionality
once
out
in
self-service,
and
we
don't
have
to
worry
about
it
anywhere
else,
so
otherwise,
we'll
have
to
build
it
into
our
restful
api
and
we'll
have
to
build
it
into
our
rails
controllers
to
support
it
on
projects
uploads
and
designs.
Right
now,
as
is.
B
B
B
C
There's
another
redesign
that
I
don't
know
where
it's
kind
of
located
as
far
as
like
our
board
right
now,
but
so
we
have
the
redesign
of
what
we
call
like
the
replication
details,
which
is
where
you
go
and
you
filter
through
like
the
status
of
each
individual
reputable
item.
And
then
we
have
the
node
status
page,
which
has
a
kind
of
the
overview.
Everything
and
so
sun
june
also
has
a
node
status
page,
that's
going
through
a
redesign
in
ux
research
right
now
and
that
one's
good
to
go,
as
is
so.
C
C
This
I'd
say
like
this:
half
of
the
ui
redesign
is
blocked
by
the
individual
data
types
not
being
there,
but
as
far
as
the
general
node
status
page,
we
serve
that
all
from
our
our
kind
of
older
restful
geo
status
page-
and
I
think
like
over,
like
13
3,
13
4
mike
and
I
kind
of
worked
together
and
got
a
lot
of
that
stuff,
generalized
from
the
rails
controller
and
so
all
that's
kind
of
good.
C
To
go
and
generalized
already
and
working
as
in
with
no
extra
work
really
from
what
it
seems
on
self-service
now,
like
cell
services,
handles
it
so.
B
A
Yeah
I'm
wondering
if
it's
it's
probably
going
to
be
sitting
in
that
workflow
blocked
column
for
a
while.
Then
until
we
can
get
all
those
back
end
items
done,
I'm
wondering
if
we
just
want
to
move
it.
I
mean
we
yeah,
just
just
move
it
off
the
board
for
now
and
add
the
blocking
relationships
to
to
the
issue
when
we,
when
we
have
those.
B
A
Is
there
an
issue?
You
said
that
the
status
the
status
view
work
is
is
ready
to
go.
Do
we
have
an
issue
for
the
front
end
implementation
of
that
that
we
can
put
on
the
board.
C
I
know
that
there
were
some
design
issues
somewhere
and
I
I
I've
lost
track
of
them.
I
don't
know
what
happened
to
him:
okay,
I'll
yeah.
I
can
just
make
a
note
to
follow
up,
also,
not
quite
sure
where
they're
at
with
the
ux
research,
I
can't
I
can
say
like
tech
from
like
a
technical
standpoint.
Everything
seems
to
be
in
order,
but
I'm
not
quite
sure
where
we
are
with
the
customers.
C
C
Yeah,
so
I
might
be
a
good
follow-up
for
june,
while
fabian's
out
sounds
good.
B
B
Down
here
in
the
closed
column,
oh
this
issue
was
moved
actually,
so
I
suppose
we
want
to
put
geoactive
on
the
new
issue.
Is
it
all
ready
on
there?
No
okay.
B
Yeah,
I
guess
it
copies
all
the
same
labels.
So
oh
yeah,
here
it
is
okay,
so
in
review.
D
Yeah,
so
I
reviewed
this
just
the
other
day.
Basically,
valerie
has
it
set
up
so
that
we
can
use
point
in
time
recovery.
D
So
when
you
pop,
when
you
pause
replication,
it
creates
a
restore
point
and
then,
when
we
do
the
promotion
it
restores
to
that
location
instead
of
trying
to
mess
with
any
of
the
other
stuff.
So
it
looks
pretty
good.
A
Yeah,
I
think
yeah
we'll
definitely
it
seems
close
and
there's
a
lot
of
hard
work
to
try
to
get
it
in
for
13.5,
but
it
it
missed,
but
hopefully
it'll
get
in
soon
and
we
can.
We
can
get
it
into
the
the
earliest
patch.
For
that
and
whatever
other
versions
we
can,
you
can
patch
as
well.
D
I
was
going
to
say
we
had
talked
about
back
porting
this
to
the
to
what
like
13
years.
I
don't
know,
I
don't
know
how
far
back
we
backboard
thing.
A
F
Is
this
the
promotion
after
pause,
or
is
this
this
rake
backup
bug?
Oh
sorry,.
B
All
right
so
yeah
regarding
the
rake
backup
bug
the
community
contributor
has
been
pushing
commits
kind
of
every
every
day
for
the
last
two
days,
so
I
think
they're
still
kind
of
working
on
it.
The
last
that
I
saw
yeah
seven
hours
ago,
so
I
think
they
might
be
kind
of
relying
on
the
ci
for
running
tests.
I
think,
might
be
part
of
what's
happening
so
anyways.
Actually,
it's
green
though
now
so
that's
good.
A
It's
cool
to
see
them
still,
sticking
sticking
with
the
mr
and
continuing
to
to
work
through
the
feedback,
thanks
for
working
with
them
on
that
mike
and
ocratee.
So
pretty
cool
to
see.
B
Yeah,
so
that's
it
for
in
review
and
we're
over
to
in
dev
this
one
performance,
environment
builder,
as
far
as
I
know,
is
still
being
worked
on
by
nick
westberry.
A
A
D
Yeah,
so
I
just
started
working
on
this
yesterday
and
I
mostly
have
been
going
through
the
background
and
just
trying
to
understand
the
work.
D
That's
already
been
done
and
what's
already
been
looked
into,
and
my
my
gut
feeling
for
this
right
now
is
that
probably
this
is
this
should
turn
into
an
epic,
and
we
should
get
a
couple
of
smaller,
discrete
issues
out
from
under
it
and
from
those
try
to
identify
what
we
can
make,
what
we
can
fit
into
eleven
six
or
thirteen
six,
whatever
number
we're
working
on
right
now,
thirteen
six
joshua!
I
know
you
have
a
lot
of
feelings
about.
D
D
Yeah
and
see
what
your
thoughts.
F
Are
yeah
just
just
real,
quick,
the
overall
importance
of
this?
You
know:
there's
there's
multiple
okrs,
that
okay,
our
last
quarter,
okay,
this
quarter
across
the
whole
organization
to
get
kind
of
group
based
adoption,
metrics
or
other
primary
performance,
metrics
and
so
yeah.
This
is
a
great
indicator.
We
can
use
to
track
adoption
and
utilization
of
geos
and
we
can.
F
Do
know
that
you
know
geo
tends
to
have
conservative
customers
that
are
bigger,
and
so
a
few
of
them
have
usage
being
turned
on,
but
we
can,
I
think,
still
get
some
good
data
and
usage
out
of
this.
So,
for
example,
if
we
introduce
like
you
know
some
improvements
to
the
single
url
experience,
it'd
be
interesting
to
see
if
we
get
more
people
utilizing
the
utilizing.
The
secondaries,
for
example,
for
sure
data
is
great
but
yeah.
F
A
A
A
Ask
for
okay,
so
maybe
this
is
the
the
mr.
That's
that's
open
for
this.
B
Yeah
cool
yep,
so
it
seems
like
it's
a
review.
B
I'll
I'll
just
change
this
to
end
review.
B
A
Okay,
yeah,
I
think
gabriel,
provided
an
update
here,
but
basically
he's
working
on
something
that
will
prevent
prevent
a
migration
from
from
getting
stuck
in
the
situation
that
was
encountered
in
in
this
issue.
There
will
so
so.
Basically,
it
will,
if
yeah,
if,
if
this
issue
is
detected,
it'll
roll
back
the
hash
storage
migration.
But
I
think
there
will
need
to
be
some
work
on
the
getaway
side
to
actually
fix
the
the
root
cause.
That's
preventing
the
migration
to
hash
stored.
A
So
so
so
there
will
probably
be
some.
I
don't
think
that
will
be
work
that
that's
done
in
geo,
but
we'll
just
need
to
make
sure
we're
we're
properly
escalating
that
to
italy
and
working
working
with
them
to
to
yeah
to
get
that
prioritized,
because
I
think
we
have
a
little
time,
but
I
think
we're
talking
about
removing
removing
hash
storage
or
removing
legacy
storage
in
fortino.
So
so,
whatever
needs
to
happen,
there
will
will
have
to
be
prioritized
before
14.0.
A
A
B
A
B
A
Just
yeah
I
can,
I
can
just
yeah
if
you
wanna,
share
your
screen,
I
can
just
talk
through
it:
real,
quick,
nothing
too
much
has
changed
with
the
ready
for
development
column
use
usage
ping
was
at
the
top
and
alex
has
taken
that.
So
thank
you
yeah,
but
everything
else
is
there
kind
of
in
the
same
order.
Yeah
we
still
want
to
fix,
fix
the
replicate
geodatabase
command
to
account
for
the
seed
project.
It's
it's.
A
A
So
I
think
we
should
still
still
account
for
still
do
the
work
to
account
for
that
seed
project,
and
then
we
want
to
investigate
the
downtime
issues
that
were
discovered
a
while
back
by
alex
and
jenny,
and
that's
so
that
we
can
get
back
to
resuming
our
our
regular
upgrade
tests
and
then
a
couple
of
bug
fixes
and
investigations
down
below
kind
of
the
same
as
what's
been
there.
A
The
last
couple
weeks
yeah
and
I
I
think
it's
one
of
those
things
where
we
just
need
to
somehow
carve
out
some
time
for
these,
because
things
kind
of
keep
keep
coming
up
in
and
pushing
back
those
investigations.
A
So
we'll
keep
them
there
in
the
ready
for
development
column,
and
I
think,
just
try
to
try
to
carve
out
some
some
time.
For
those.
A
A
I
think
likely
that
probably
won't
won't
have
much
progress
on
it
until
douglas's
is
back
from
vacation
with
with
everything
else
that
we've
got
going
on
and
then,
of
course,
the
first
iteration
for
for
moving
lfs
files
to
self-service
framework
and
that
placeholder
alex
has
volunteered
to
to
take
on
going
through
that
and
breaking
out
issues
for
it.
So
yeah.
Those
are
the
other
big
kind
of
the
new
items
in
in
the
ready
for
development,
open
or
almost
ready
for
development
area.