►
From YouTube: GitLab 13.8 Kickoff - Enablement:Geo
Description
Geo's PM walks through the team's upcoming 13.8 release plans. For more information, check out Geo's 13.8 planning issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/4990
A
Okay,
before
I
go
into
the
details,
I
just
wanted
to
give
you
a
high
level
overview
of
the
area
that
we're
working
in
so
we're
currently
working
on
increasing
the
majority
of
our
disaster
recovery,
category
and
all
of
the
epics.
The
larger
themes
of
that
work
are
grouped
in
the
disaster.
Recovery
complete
maturity,
epic,
so
you
can
follow
that
if
you're
interested
in
our
broader
direction
and
I'm
going
to
talk
about
a
few
of
these
sub
epics
that
we're
going
to
work
on
in
13.8.
A
A
A
So
in
30
13.8
we
are
going
to
work
on
a
few
items.
The
one
that
mike
is
already
working
on
is
automatically
verifying
packages
on
secondaries
so
automatically
generating
checksums
and
also
then,
with
the
goal
in
mind,
to
compare
the
compare
them
between
the
secondary
and
the
primary
side.
So
that's
happening.
This
is
a
larger
effort.
We
hope
that
we
will
be
able
to
ship
this
in
13.8
so
that
all
the
data
types
can
benefit
from
it.
A
The
next
item
here
is
petroni
support,
so
this
is
part
of
our
effort
to
provide
a
high
availability
solution
for
postgres
on
our
secondary
site.
That's
important
for
disaster
recovery.
So
when
you
have
to
fail
over
to
your
secondary
site,
you
have
a
highly
available
postgres
cluster
right
when
you
do
that,
rather
than
having
to
do
extra
work
to
restore
those
so
we're
working
on
releasing
this
as
an
alpha
feature,
we've
done
some
work
in
13.7.
That
is
great
to
finish
in
13.8.
A
A
Already
so
this
is
a
larger
feature
where
we
are
specifically
interested
in
creating
a
read-only
mode
or
a
maintenance
mode,
as
we
call
it
right
now
that
essentially
takes
your
primary
git
website
and
allows
users
to
still
log
in
and
perform
read
operations,
so
they
can
clone
repositories,
pull
them
and
they
can
look
at
the
web
page,
but
they
can't
make
any
changes
and
for
us
this
is
really
important,
because
this
would
allow
a
secondary
site
to
fully
replicate
and
be
completely
in
sync
with
the
primary.
So
no
data
is
lost.
A
That
is
important
for
planned
failovers,
but
it's
also
the
preferred
strategy
in
in
other
scenarios.
If
you
can
do
this,
you
are
very
sure
that
everything
that
is
in
the
primary
gets
copied
over
to
a
secondary
as
well,
so
in
13.8
we're
going
to
focus
on
fixing
some
bugs
doing
a
lot
of
quality
control,
work,
making
sure
that
everything
works
as
expected,
testing
it
and
then
hopefully
releasing
it.
So
this
is
an
ambitious
target.
13.8
will
keep
you
posted.
A
Another
thing
that
I'm
quite
excited
about
is
to
move
our
lfs
file,
implementation
to
the
self-service
framework,
lfs
files.
Large
files
and
git
repositories
are
important
to
customers
that
work
with
large
binary
files.
Images,
videos
and
geo
is
particularly
useful
in
some
of
those
cases
to
bring
that
data
closer
to
them,
but
also
in
disaster
recovery
situations.
A
A
So
this
is
the
outcome
of
a
lot
of
user
research
and
work
to
you
know
provide
a
more
user-friendly
overview
across
different
geo
sites
and
we've
broken
this
down
in
13.7
and
we're
going
to
start
on
the
implementation
in
13.8
thanks
to
zach.
This
is
really
nicely
broken
into
little
little
pieces
and
we
are
going
to
make
headway
in
13.8
I'll,
keep
you
posted,
and,
lastly,
something
that
I
think
I
mentioned
last
time
around
as
well
that
we
didn't
quite
get
to.
A
We
are
interested
in
tracking
git
operations
on
secondary
sites
for
our
user
ping
usage
ping.
This
is
important
to
us
because
we
want
to
understand
how
folks
are
using
secondary
sites
and
how
we
can
improve
them
overall.
So
this
is
not
personalized
data.
We
are
only
interested
in
how
many
people
are
actually
using
it
on
secondary
sites
to
get
a
feeling
for
the
usage
overall
and
we're
going
to
address
that
in
13.8.