►
From YouTube: GitLab 13.1 Kickoff - Enablement:Geo
Description
Fabian Zimmer (Product Manager, Geo) highlights new features and direction for GitLab Geo in 13.1.
A
Hello,
everyone-
this
is
Fabian
the
product
manager
for
kid
lab,
Gio
and
now
I'm,
going
to
walk
you
through
the
plant
work
for
the
13.1
release
and
start
the
top,
as
you
have
heard
before,
we
working
on
a
self-service
framework.
So
we
had
intentions
to
finish
most
of
this
work
here
for
package
file,
replication
30-point,
oh,
but
we're
not
quite
there
yet
so
we're
focusing
in
13.1
on
finishing
up
all
of
the
remaining
items.
So
we
can
close
our
package
file
replication.
A
There
are
a
few
remaining,
but
we
are
confident
that
that
will
close
in
thirteen
point
one
and
that's
one
of
the
two
main
focuses
of
this
release.
Secondly,
we
are
starting
more
and
more
work
on
the
disaster,
recovery
and
failover
side
of
things
so
promoting
a
secondary.
It
should
really
be
very
simple
for
our
users.
We've
mapped
out.
The
current
user
flow
has
all
of
the
different
steps
that
a
user
needs
to
take,
including
the
sort
of
pre-flight
steps,
and
our
goal
here
is
to
make
it
a
lot.
A
Simpler,
reduce
the
number
of
manual
interactions
for
user
and
in
13.1
we
are
going
to
start
working
on
automating.
A
lot
of
the
pre-flight
checks,
so
currently
we
ask
our
users
to
perform
many
manual
actions
and
we
can
actually-
and
we
have
a
number
of
very
small.
If
you
see
it,
we
can
start
working
on
automating
some
of
them
so
that
a
systems
administrator
no
longer
has
to
do
this
manually.
A
They
can
just
invoke
a
command
at
it,
we'll
check
and
provide
information
as
to
the
pre-flight
checks
having
failed
or
succeeded
in
the
same
realm,
we
are
also
working
on
some
planning.
Essentially,
what
we
are
interested
here
is
some
of
the
like
breakdown
for
creating
a
single
command
that
can
be
run
on
any
node
to
promote
a
secondary
to
a
primary.
So
this
is
just
planning
that
we're
currently
thinking
about
just
wanting
to
point
that
out
for
thirteen
point
once
or
implementation
may
not
necessarily
start,
but
we
are.
A
We
are
going
to
work
in
this
area,
something
that
is
in
flight
at
the
moment
and
getting
to
the
close.
So
we
had
hopes
to
deliver
this
in
13-point.
Oh,
but
this
will
be
pushed
into.
13.1
is
a
command-line
tool
that
pauses
and
assumes
all
replication
on
the
secondary.
So
this
is
quite
important
if
you
want
to
be
couple
a
secondary
completely
from
a
primary
so
that
anything
that
happens
on
the
primary
is
no
longer
replicated
on
to
the
secondary
we're
also
going
to
start
work
on
a
maintenance
mode.
Read-Only
mode.
A
We've
had
that
on
the
agenda
for
a
little
while,
so
we've
recently
broken
out
a
few
more
issues
to
make
it
more
iterative.
So
you
can
see
that
small
and
we
are
to
start
working
on
them.
This
requires
quite
a
bit
of
testing,
so
we
may
not
be
able
to
finish
all
of
it
in
13.1,
but
we're
going
to
try
and
make
it
both
here
other
than
those
features,
we're
also
working
on
simplifying
backfill
operations
for
geo.
A
This
is
mainly
for
performance
reasons
and
for
the
backend
to
be
simpler,
so
we're
essentially
trying
to
eliminate
the
foreign
data
records
out
of
geo,
which
has
made
geo
more
complex
and
harder
to
maintain.
So
that
is
ongoing,
and
some
of
these
features
are
landing
in
13
point
all
very
likely,
but
we
have
continuing
to
make
improvements
in
this
area
on
the
UI
and
you
excite
the
focus.
A
In
thirteen
point,
one
is
conforms
so
a
lot
of
the
forms
that
are
presented
to
systems
administrators
and
the
geo
UI
are
not
as
user-friendly,
so
we
are
adding
better
validations.
We
are
updating
a
lot
of
the
like
forms
themselves:
that
design,
for
example,
here
adding
more
user
friendly
error
messages.
We're
also
looking
at
updating
how
the
geo
forms
can
be
edited
and.
A
Sort
of
preparing
us
for
the
future
is
we
already
know
that
Postgres
12
will
become
the
standard
for
gitlab
and
because
geo
relies
very
heavily
on
Postgres
we're
going
to
perform
some
preliminary
research
on
what
is
needed
for
phosphorus
12
so
that
when
these
changes
land
in
13.3,
we
have
the
Geo
side
of
things
covered.
So
13.1
is
a
bit
more
focused.
A
We
may
also
work
a
little
bit
on
instrumenting
the
Northstar
metrics,
but
the
focus
this
time
around
is
really
to
finishing
the
first
situation
for
package
file
replication
making
improvements
in
the
planned
failover
Avena
continue
to
work
on
scalability
improvements
and
polish,
the
UI
even
further,
and
that's
it
from
go4
13.1.
Thank
you
very
much.