►
From YouTube: GitLab 14.5 Kickoff - Enablement:Geo
Description
Planning issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5018
A
Hello
and
welcome
to
the
14
5
kickoff
video
for
getlab
geo,
I'm
nick
nguyen
engineering
manager
and
acting
product
manager
for
the
geo
team.
There
are
two
main
themes
for
14
14.5
that
I
want
to
highlight
today.
The
first
theme
is
that
we
are
working
towards
beta
releases
of
two
high
impact
projects
that
have
been
in
development
for
the
last
few
milestones.
A
These
are
secondary
proxy
to
support
a
single
url
and
simplified
failovers
with
a
single
command
to
promote
any
secondary,
node
type
to
a
primary.
While
we've
mentioned
these
in
recent
kickoff
videos.
I'll
briefly
summarize,
the
importance
of
these
two
efforts
with
secondary
proxying
will
solve
a
major
usability
pain
point
for
geo
customers
with
distributed
developers
who
want
to
use
the
web
ui
and
api
of
the
geo
site
closest
to
them
right
now.
A
A
developer
would
have
to
intentionally
use
the
primary
geosite
to
do
anything
that
requires
writing
to
the
database,
such
as
commenting
on
an
issue
or
opening
a
merge
request
with
secondary
proxying
administrators
can
set
up
a
single
gitlab
url
with
location,
aware
load.
Balancing
that
selects
the
best
geosite
for
a
developer
developers
will
no
longer
need
to
remember
different
gitlab
urls
and
they'll
gain
performance
benefits
of
read
operations
from
a
geosecondary
site
while
having
write
operations
proxy
to
the
primary
site.
Behind
the
scenes.
A
Our
work
to
provide
a
single
promotion
command
is
also
close
to
beta
release
and
undergoing
thorough
testing
on
our
reference.
Architectures,
the
single
command
to
promote
any
secondary
site
node,
will
greatly
simplify
the
steps
needed
to
fail
over
to
larger
geosecondary
sites
that
utilize
many
nodes
for
high
availability.
A
The
second
theme
that
I
want
to
highlight
today
is
that
we're
expanding
verification
of
the
data
data
types
that
geo
replicates
since
14
3
geo
replicates
100
of
the
currently
planned
data
types.
However,
we
only
verify
50
verification
is
important
so
that
administrators
can
ensure
the
integrity
of
all
the
data
that
has
been
replicated
to
a
geosecondary
site
with
recent
work
to
improve
the
performance
of
our
verification
process,
combined
with
the
power
of
geoself-service
framework,
we
plan
to
add
verification
for
four
more
data
types.