►
From YouTube: GitLab 12.9 Kickoff - Enablement:Geo
Description
Fabian Zimmer (Product Manager, Geo) highlights new features and direction for GitLab Geo in 12.9.
Geo Product Strategy: https://about.gitlab.com/direction/geo/
Geo Roadmap: https://gitlab.com/groups/gitlab-org/-/roadmap?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=group%3A%3Ageo&label_name[]=geo%3A%3Aactive
A
Hello,
everyone-
this
is
Fabian
the
product
manager
for
giblet,
Jill
and
I
am
going
to
talk
you
through.
What's
coming
next
in
12.9
and
update
you
a
little
bit
on
what
happened
in
in
12.8
I'll
just
walk
you
through
the
individual
epochs.
You
can
always
also
check
out
a
Geo
road
map
here,
but
move
through
a
little
bit
more
in
in
detail.
So,
as
we
spoke
about
last
time,
we
are
quite
active
at
the
moment
trying
to
bring
Gio
to
calm.
A
We
believe
in
dog
fooding-
and
this
is
one
of
the
important
areas
that
we
focus
on
right
now
or
to
test
G
or
at
the
largest
scale
possible.
At
the
moment
we
are
working
on
getting
Gio
on
staging
in
12.8,
we've
actually
enabled
good
lap
Gio
on
staging
via
node,
but
we
still
have
to
improve
the
monitoring
and
updating.
So
this
is
some
work
that
we
hope
to
finish
in
12.8,
but
it
is
a
little
bit
more
challenging,
so
those
items
are
rolling
over
from
twelve
point,
eight
into
twelve
point
nine.
A
A
We
had
some
ambition
to
actually
finish
a
few
more
items
here,
but
this
is
also
going
to
roll
over,
but
we
believe
that
in
12.9
as
a
initial
implementation
for
a
package,
file,
replication
will
be
finished
and
that's
the
main
ambition
here.
We'll
also
actually
have
a
workshop
at
the
contribute
conference.
A
We
are
also
not
only
looking
at
replication,
we're
also
looking
at
verification.
We
believe
that
if
we
replicate
something
is
worth
verifying,
and
so
this
is
sort
of
the
follow-on
from
the
work
that
we
we
started,
you
can
see
that
it's
quite
a
bit
still
outstanding
in
12.9,
we
will
make
further
inroads
and
actually
ensuring
checksums
are
checked
correctly
for
the
package
files
and
that
will
have
knock-on
effects
and
a
positive
impact
on
any
other
data
type
that
we're
going
to
increment
in
the
future.
A
The
last
piece
here
for
the
self-service
framework-
and
you
can
already
see
this
is
a
bit
of
a
theme
for
12.9-
is
to
implement
an
API
to
actually
surface
this
information
in
the
front
end.
So
this
is
something
that
we
are
quite
quite
keen
on.
We
have
already
some
capabilities
at
the
moment
with
the
GUI
administrator
interface,
but
we
are
going
to
actually
create
graphs.
Elap
is,
to
you
know,
surface
this
information
to
systems
administrators.
If
that's
also
scheduled
for
Fort
Worth
point
nine,
that's
concluding
the
section
for
the
Jima
self-service
framework.
A
We
are
also
working
on
improvements
on
disaster
recovery
and
so
for
12.9.
We
are
going
to
actually
now.
After
concluding
our
POC
for
pausing
database
replication,
we
are
going
to
create
a
first
MVC
to
allow
for
pausing
and
resuming
of
replication
to
secondary
nodes,
which
is
important
for
various
faster
recovery
use
cases,
and
the
first
thing
is
we're
going
to
create
a
command
line,
two
of
that
that
was
pausing
and
resuming
of
all
replication
for
a
secondary
node.
A
That's
something
we're
going
to
do
in
12.94,
the
maintenance
mode
or
read-only
mode,
we're
going
to
do
a
little
bit
more
discovery,
work
and
validation
of
initial
designs.
So,
given
that
we
are
already
doing
quite
a
bit
of
implementation
work
in
12.9,
we
are
not
going
to
start
implementing
this,
but
that
will
be
in
a
further
release,
maybe
12.10,
but
this
is
certainly
still
on
the
menu
yeah
I
spoke
about
this
another
like
big
change.
Coming
for,
kidnap
13
is
actually
upgrading
to
post
Chris
11
and
we
are
already
starting
to
test.
A
If
there
are
any
problems
with
Geo
on
a
new
post,
Chris
version,
we
wanted
to
do
this
in
twelve
point
eight.
But
this
is
still
ongoing.
So
in
twelve
point
nine
nine
we're
going
to
deliver
and
conclude
the
Geo
installation
for
Postgres
11
and
the
upgrade
procedure,
because
that's
important
to
give
reassurance
that
if
you
upgrade
to
a
newer
post
res
version
that
it
continues
to
work
with
a
deal,
then.
A
Lastly,
we're
going
to
work
on
the
first
iteration
on
a
selective
sync
improvement,
where
we
are
going
to
proxy
back
traffic
to
a
primary
if
the
projects
are
actually
not
replicated
to
a
secondary.
That's
a
user
experience
improvement
rather
than
providing
an
error
message
that
that
it
has
not
available
with
which
once
parity
proxy
and
for
12.9
we're
going
to
focus
on
the
first
iteration
here,
which
is
to
perform
this
via
HTTP
and
then
in
the
following
moment.
We're
going
to
focus
on
on
SSH.
So
you
can
see
for
12.9.