►
From YouTube: GitLab Kickoff 13.4 - Enablement:Geo
Description
Learn what the Geo team has in store for the GitLab 13.4 release.
Planning issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/4974
A
Hello
and
welcome
to
the
13
for
kickoff
video
for
the
geo
team.
This
is
nick
engineering
manager
for
geo
filling
in
one
more
time
for
our
product
manager.
Fabian
we've
made
some
nice
progress
towards
our
goal
of
disaster
recovery,
viable
maturity
in
13-3
and
in
13-4.
We
are
going
to
continue
to
work
towards
completion
of
our
dr
viable
maturity.
Epic.
A
We
are
also
going
to
begin
working
on
some
exciting
features
that
we
consider
part
of
disaster
recovery,
complete
maturity,
one
notable
achievement
from
13
3
that
I
wanted
to
highlight
is
that
we've
removed
the
reliance
on
foreign
data
wrappers
form
data
wrappers
were
originally
implemented
to
perform
cross
database
queries
between
the
primary
and
secondary
geo
nodes.
Despite
the
technical
elegance
of
this
approach,
these
queries
have
led
to
a
number
of
problems
for
geo
and
with
fdw
removed
in
133
in
favor
of
a
new
backfill
implementation.
A
In
13
3,
we
made
a
lot
of
progress
on
replication
for
terraform
state
files
and
external
merge
request
diffs,
and
we
plan
to
wrap
up
this
work
early
in
thirteen
four
in
working
through
replication.
For
these
additional
blob
data
types,
we
found
opportunities
to
improve
the
geo
self
service
framework.
A
We've
also
started
on
supporting
replication
for
snippets
via
the
self-service
framework.
This
requires
us
to
implement
a
new
replication
strategy
for
repository
data
types
once
we've
shipped
replication
for
terraform
state
files,
external
mr
diffs
and
snippets
geo
will
replicate
nearly
90
of
the
data
types
that
we
plan
to
support.
A
Now
I'm
going
to
talk
about
some
work
that
we're
considering
as
part
of
our
disaster
recovery,
complete
maturity
in
13
4.
We
are
going
to
continue
working
to
support
postcrest
ql
high
availability
on
geosecondaries
using
a
petroni
standby
cluster
petroni
is
currently
an
experimental
feature
in
omnibus,
and
we
expect
that
support
for
a
petroni
cluster
on
a
geosecondary
will
involve
iterative
updates
to
omnibus
and
the
documentation
to
improve
the
ease
of
setup
and
maintenance.
A
A
A
A
We
also
have
to
ensure
that
the
upgrade
process
from
postgres
11
to
12
is
properly
documented
and
that
we
fix
any
potential
issues.
So
until
this
work
is
done
in
13
4,
we
do
not
recommend
customers
use
postgres
12
with
geo
in
13
3.,
so
that
does
it
for
our
walkthrough
of
thirteen
four.
The
team
is
excited
to
continue
working
on
improvements
to
our
disaster
recovery
capabilities,
I'll
end
with
the
usual
disclaimer
that
we
plan
ambitiously
and
work
in
a
continuous
iterative,
kanban
style.