►
From YouTube: GitLab 14.1 Kickoff - Enablement: Geo
Description
Geo 14.1 Planning Issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5011
A
A
Just
a
little
bit
of
context
here
in
14-0,
postgres
12
became
the
minimum
required
version
and
rep
manager
is
no
longer
supported
as
the
solution
for
managing
postgres
clusters
on
geosites,
so
petronia
is
going
to
be
required
and
with
the
introduction
of
petroni,
we
were
able
to
use
the
petroni
standby
cluster
functionality
to
support
postgres
clusters
on
geosecondary,
something
that
wasn't
that
we
weren't
able
to
support
before
with
the
version
of
rep
manager
that
we
were
shipping
with
omnibus.
A
A
Next,
we
want
to
continue
with
our
theme
of
moving
our
disaster
recovery
capabilities
from
viable
maturity
to
complete
one
of
the
big
components
of
this
is
to
increase
the
amount
of
data
types
that
geo
verifies
and
I'm
really
proud
of
the
team
making
great
progress
on
increasing
the
amount
of
data
that
we
verify
in
14.0.
We
released
verification
for
terraform
state
files.
A
We're
also
planning
to
verify
lfs
objects
in
14
1,
which
has
been
a
commonly
requested
feature,
and
a
lot
of
this
is
made
possible
now
by
the
geo
self
service
framework
that
we've
been
working
on
and
developing
over
the
last
year.
Things
that
would
before
take
up
to
three
months
to
add
replication
and
verification.
Support
for
now
can
take
under
a
release.
So
we're
really
happy
to
see
the
velocity
that
the
framework
has
enabled.
A
Site
we're
also
going
to
be
focusing
on
making
the
failover
experience
for
multi-node
geo
sites
a
lot
more
efficient
right
now
you
have
to
manually
edit,
get
lab
rb
file
and
run
if
you're
on
a
postgres
node,
you
have
to
run
get
lab,
pg
ctl
promote
you
have
to
run
a
command
to
set
secondary
as
primary,
and
we
just
want
to
make
it
so
that
you
only
need
a
single
command
to
that.
Automatically
can
tell
what
kind
of
node
you're
on
and
we'll
update
the
configuration
appropriately
and
then
promote
that
node
to
a
primary.
A
And
next,
if
time
allows,
there
are
a
couple
of
things
we'd
like
to
do
with
our
self-service
framework,
one
is
we'd
like
to
replicate
pages
deployments
via
the
cell
service
framework.
This
is
another
thing
that
has
been
commonly
requested
in
the
past,
but
has
been
prohibitive
to
actually
implement
until
recently.
A
So
in
1312
we
did
this
for
lfs
files
and
that
actually
ended
up
letting
us
delete
a
net
of
a
thousand
lines
of
code.
We
would
like
to
do
this
for
uploads
in
the
upcoming
release
and
allow
uploads
to
take
advantage
of
the
self-service
frameworks,
performance
and
maintainability
benefits,
as
well
as
the
as
well
as
making
it
easier
to
follow
up
with
verification
support,
and
that
does
it
for
the
walkthrough
of
our
priorities
for
14
1.