►
From YouTube: GitLab 13.0 Kickoff - Enablement:Geo
Description
Fabian Zimmer (Product Manager, Geo) highlights new features and direction for GitLab Geo in 13.0.
Geo Product Strategy: https://about.gitlab.com/direction/geo/
A
You
hello
everyone.
This
is
Fabia
I'm,
the
product
manager,
for
it.
Good
luck
to
you
and
I'll
quickly
run
you
through
some
of
the
features
that
we
are
going
to
deliver
for
a
certain
point
over
the
next
get
lab
release.
So
this
release
is
really
about
two
major
efforts.
One
is
the
Geo
self-service
framework.
The
other
one
is
thought
provements
to
Ark
land
sale.
All
those
uses
geo,
so
I
run
you
through
what
we
are
intending
to
do.
A
The
first
one
is
about
the
geo
self-service
framework
and
we
are
currently
implementing
the
first
iteration
of
this
for
package
files,
both
for
the
application
and
verification.
The
self-service
framework
is
something
in
iterating
on
for
a
little
while
it's
really
important
as
the
foundational
basis
for
how
we
replicate
and
verify
data
using
github
geo
and
the
self
service
framework
will
allow
us
to
do
this
in
a
more
standardized
foundational
in
the
past
way
and
also
allow
other
developers
inside
gitlab
and
the
wider
gate
lab
community
to
contribute
and
then
ultimately
accelerate
how
we
replicate
data.
A
So,
in
thirteen
point
o
we
are
going
to
ship
our
first
implementation
for
a
package
file
application.
We
had
attentions
to
finish
this
by
1210,
but
we
decided
to
push
this
out
a
little
bit
just
to
ensure
that
all
of
the
items
for
the
framework
are
in
place
and
that
should
accelerate
us
further.
So
there's
quite
a
few
things
that
are
scheduled
for
the
next
release
and
we're
excited
to
deliver
this
thirteen
point.
O
is
also
going
to
feature
package
fire
there,
education,
the
first
iteration
on
this.
A
We
have
quite
a
few
issues
that
we
need
to
deliver
in
order
to
verify
this
type
of
data.
So
these
are
two
of
the
major
efforts
here.
The
next
two
features
are
really
to
improve
how
our
plans
fail.
Overs
can
operate.
The
first
one
is
to
create
a
command
line
tool
that
pauses
and
resumes
all
replication
on
the
secondary.
This
is
particularly
interesting,
for
example,
during
an
upgrade
when
you
want
to
make
sure
that
your
secondary
gets
completely
separated
from
prime
and
no
changes
to
the
database
replicated
mildly
perform
some
other
operation
of
the
primary.
A
Lastly,
we're
going
to
deliver
a
read-only
mode
or
maintenance
mode
for
the
primary.
The
main
intention
here
is
to
allow
gitlab
to
be
put
into
this
read
only
mode
where
regular
users
can
still
access
most
of
the
data.
They
can't
make
any
changes.
This
is
important
to
allow
a
primary
to
replicate
all
data
to
a
secondary
so
that
they
can
be
in
a
completely
synced
State,
and
this
is
important
in
the
plant
failover
scenario
when
you
may
actually
intend
to
switch
over
from
a
primary
to
a
secondary,
and
you
don't
want
to
lose
any
data.
A
A
Lastly,
we've
been
busy
getting
deal
on
to
the
staging
environment
for
the
comm
and,
as
a
consequence
of
this,
we've
discovered
some
scalability
improvements
that
we
can
make
by
simplifying
backfill
operations.
We've
already
delivered
iterations
on
this
for
some
data
types
in
2010
and
we
are
going
to
actually
continue
making
these
changes
in
13.0
and
close
out
these
performance
optimizations,
which
would
make
to
you
a
lot
more
robust
and
fast.
A
We
are
also
continuing
to
make
changes
in
the
user
interface
for
administrators,
and
one
thing
that
came
out
of
introduced
that
we
had
with
systems
administrators
is
that
it
is
a
little
bit
difficult
to
find
where
specific
replicated
items
are.
At
the
moment,
we
have
many
different
pages,
that
sort
of
replicate
same
interface
over
and
over
we're
going
to
actually
merge
this
into
a
unified
single
review
for
the
Geo
application
overview,
and
this
is
one
of
the
bigger
changes
that
use
smaller
ones.
A
That
I
don't
have
time
to
highlight
right
now
and
in
terms
of
deprecations.
There
are
two
things
that
are
off
note,
so
the
first
thing
is
that
hash
storage
is
the
default
for
gitlab.
Since
12
point,
oh
and
in
13
point
oh,
we
will
no
longer
allow
systems
at
ministers
to
revert
back
to
non
hath
storage,
so
you
can
obviously
still
migrate,
and
you
will
need
to
do
this.
For
thirteen
point.
A
Oh,
but
you
know
we
won't
allow
simply
going
back
to
the
old
one
hat
storage
in
a
tiny
note
is
that
we've
announced
this
a
while
ago.
The
Geo
settings
will
now
live
in
the
geo,
navigation
menu
and
they're
no
longer
part
of
the
rest
and
like
the
overall
settings,
for
instance.
At
the
moment
we
maintain
both
links
so
not
much
to
change,
but
I
just
wanted
to
highlight
this.
A
That
is
mainly
yet.
We
are
also
going
to
investigate
a
little
bit
further,
how
we
can
simplify
the
disaster
recovery
process,
work
on
the
gene
installation
process
and
from
an
internal
node.
We
are
thinking
about
North,
Star
metrics,
so
the
most
important
things
that
you
can
measure
for
geo
and
we
will
do
a
little
bit
of
work
in
that
area
starting
point.
So
thank
you
very
much.
That's
all
of
it
and
have
a
great
rest
of
your
days.