►
From YouTube: Geo Scheduling Call - 2020-02-28
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
B
That's
right,
it
wasn't
me
this
thought
this
one,
the
checksum
package
on
primary,
but
that's
the
primary.
This
is
the
create
offense
I
think
this
was
linked
to
a
separate
issue.
To
be
honest,
all
right,
this
is
mainly
the
doc
stuff.
Okay.
Well,
it's
in
there
I'm,
also
really
enjoying
the
new
board,
pull
looking
on
the
labels
that
made
total
sense,
I'm
enjoying
them
yet
the
way
the
new
labels
book
I.
B
A
B
B
Okay,
let's
continue
improve
the
reference
counter,
and
this
was
the
one
that
Gabriel
found
on
production
after
looking
into
the
migration
stuff,
and
that
has
been
raised
and
sorted
out
off
the
back
of
this.
Maybe
not
actually
that's
a
completely
separate
things
we
can
discuss
it
separately.
So
I'll
take
these
off.
It's
done,
okay,
investigate
orphaned
registries.
B
D
D
D
B
B
B
We've
seen
their
replication
failures
and
staging
it
might
be
the
case.
We
need
to
run
rake
tasks
to
clean
the
uploads,
but
this
is
today
so
I
think
I'm
just
going
to
leave
this
in
verification.
While
that
is
figured
out,
I
says:
blocked.
Valerie
took
a
look
over
the
blocking
mr
and
didn't
find
anything
in
it.
So
we're
just
waiting
for
that,
mr
to
be
merged
in.
A
I'm
not
so
worried
right
now,
because
threat
1/9
is
a
long
time
off,
but
I
also
yeah
I
leave
it
sit
for
a
couple
days.
I
think
my
main
worry
is.
It
has
had
to
be
reverted
once
because
of
issues
when
it
was
rolled
out
to
production,
and
you
know
I
think
it
would
be.
It's
really
important
that
this
time
around
we
actually
able
to
ship
this
yeah.
Oh,
my
goodness,.
B
A
A
B
Adding
the
service
to
check
some
the
package
files
on
the
primary
it's
work
in
progress.
I
will
leave
that
alone.
Yeah
perform
a
plan
failover.
You
and
I
both
been
on
a
discussion
on
this
one
today
about
the
fact
that
10k
might
have
been
a
bit
of
a
challenge
to
do
so.
We
will
trim
that
back.
So
hopefully
they
between
genia
Nash,
they
can
be
taken
care
of
next
week.
I
think.
B
B
In
a
sense,
you
know
that
work
was
going
to
come
at
some
point
and
what
this
is
showing
us
is
it's
just.
It's
just
highlighted
the
fact
again
that
doing
fail,
overs
or
doing
stuff
year
related
on
very
big
installations
is
hard
and
we
can
do
it
on
a
simple
one
to
unblock
this
issue
so
that
we
can
get
the
information
we
need
to
inform
that
epoch,
but
the
general
doing
stuff
on
10k
is
hard.
We're
going
to
have
to
address
it
at
some
point.
I
think.
A
B
Okay,
implementing
the
monitoring
on
staging
Turner's
gone
through
and
updated
the
description.
Well
now
that
Douglas
is
back
he's
going
to
review
it
as
well
and
just
confirm
what
he
thinks
we
should
do
next.
I'll
also
add
my
thoughts
here.
Just
that
do
we
need
to
just
put
in
what
we
need
to
know
if
it's
healthy
or
not,
we
don't
need
to
make
it
do
everything
but
I'll
comment
on
that
issue.
Yeah.
A
I
would
say
it's
probably
good
enough
if
we
just
like
enable
what
we
have
right
and
then
highlight
the
things
that
we
still
need
to
do
right,
but
I
I,
think
I.
You
know,
for
example,
if
we
don't
have
information
for
design
repositories
or
something
like
this.
You
know
that
is
actually
valuable
information
to
hide
out
that
we
should
have
this,
but
I
I'm,
really
quite
keen
to
like
close
out
the
staging.
Oh
good,
yeah
and
minimal,
but
sufficient
is
sort
of
what
I'm
like
I
haven't
like
yeah.
B
B
Think
that
we
can,
whatever
we
learned
up
doing
about
this
issue,
all
of
those
pieces
need
to
either
land
up
as
their
own
separate
issues
as
a
part
of
a
separate
epic.
But
it's
nice
to
have
all
the
detail
there.
Yes,
verifying
the
installation
with
protagoras
I
saw
that
Tony
had
done
some
testing
and
was
now
doing
another
clean
setting
up
a
new
cluster
to
do
the
test
again
team.
So
that's
a
nice
of
this
progress
being
made
there
improving
the
logging
of
sync
services.
I!
A
A
B
A
B
B
A
B
A
B
B
B
B
B
B
B
B
A
B
A
B
A
B
A
A
A
B
A
E
A
So
we're
worried
20
minutes
a
year
right
yeah.
This
is
still
important.
This
is
actually
really
important
because
of
the
timeline
associated
with
post
wrestling
babies.
So
I
think
what
I
main
concern
here
is.
If
this
is
something
that
can
be
like
that
can
be
paralyzed.
If
tone
has
too
much
on
his
plate,
you
know
we
can
find
this
out,
but
for
now
I'll
just
leave
it
here.
A
B
A
A
A
A
A
A
That's
fine
like
this.
One
here
is
quite
important.
That's
the
follow-up
to
what
ash
is
working
on
here.
So
I'd
like
to
see
this
finished
as
soon
as
possible,
so
that
we
can
actually
ship
it
and
I
believe
this
is
the
next
deliverable
for
12.9,
which
is
the
pass
resume
bit
I'm
inclined
to
not
move
it
in
yet
because
we
still
have.
We
already
have
like
17
wait
here
for
a
week
and
we
have
18
in
flight
but
sort
of
as
a
backup
if
magically
all
of
those
things
happen.
You
know.
B
D
A
Plenty
so
I
feel
I'll,
stop
sharing,
but
I
think
we're
in
good
state
here.
One
thing
that
I
would
like
to
discuss
with
syndrome
when
she's
back
next
week,
it's
just
as
a
little
bit
of
colour
regarding
the
surface
of
this
framework
and
I
think
we
are
very
close
to
I
just
go
in
here
to
have
the
first
implementation
of
package
file
replication
done
from
a
back-end
perspective
like
I'm
like
these
three
things
here,
I
anticipate
closing
relative
issue,
and
so
the
decision
here
is
that's
not
shippable.
A
I
mean
it
is
typical,
but
the
front
end
is
still
missing
right
and
so
InDesign
repositories.
What
we've
done
is
we've
sort
of
bolted
on
the
design
repositories
as
an
additional
page,
where
you
know
that's
fine,
we
can
do
exactly
the
same
thing
again
for
for
package
files,
but
given
that
we
are
working
on
the
like
graph,
QL
API,
hopefully
at
some
point,
that
also
opens
an
opportunity
here
to
actually
like
work
with
sintering
to.
A
Sort
of
redefine
how
the
front-end
should
look
for
the
detailed
views
for
it.
You
know,
like
all
of
those
classes
and
Zack,
brought
that
up
and
I
just
need
to
discuss
with
you.
If
we
are
confident
enough
to
make
that
call,
because
then
you
know
which
actually
do
that
I
think
sort
of
next.
That's
fine,
yeah.
B
And
I
think
that's
because
it's
this
is
the
start
of
the
new
way
of
doing
things.
If
there
needs
to
be
something
I
think
it
does
need
to
be
different.
On
the
front
end
I
mean
even
from
a
user's
perspective.
They
don't
know
that
that
under
the
hood
is
different.
Yes,
but
for
us
we
at
least
need
to
be
doing
this
in
whatever
the
new
way
is
going
to
be.
A
And
I
think,
but
then
this
is
a
missing
piece
here
right
and
we
I
need
to
discuss
with
this
enjoyment.
I
also
need
to
discuss
with
Zack
beginning
of
next
week.
It's
like
what
still
is
missing
in
order
to
actually
do
this
right
and
but
I
also
think
that
package
files
should
be
sort
of
the
beginning
of
the
new
way
of
doing
things
and
so
I'm
willing
to
do
it
to
do
it
right.
Yeah,.
A
Yeah,
the
systems
administrators
that
use
this
screen
right.
They
like
not
having
sort
of
an
interface
to
like
resync
a
file,
is
clearly
a
problem
right
so
having
this
the
same
functionality
across
all
data
types
where
it
makes
sense
right
goodbye,
we
try,
we
sing.
You
know
like
see
that
information,
that's
really
I,
think
quite
important
having
them
in
different
individual
views
makes
I
think
very
little
sense.
A
I
think
having
a
filter
to
say,
like
I,
go
to
sort
of
the
details,
page
right
or
whatever
you
want
to
call
it,
and
so
like
I'm
interested
in
looking
at,
like
everything
or
at
like
repositories,
is
allowing
them
to
see.
The
things
are
wrong.
First
is
also
I.
Think
the
way
to
go
here,
I
can
tell
us
like
people
are
generally
not
very
interested
in
like
seeing
that
their
3568,
a
positive
or
ease
are
all
fine
right.