►
From YouTube: GitLab 12.8 Kickoff - Enablement:Geo
Description
Fabian Zimmer (Product Manager, Geo) highlights new features and direction for GitLab Geo in 12.8.
A
Wonderful,
hello,
everyone.
This
is
Fabian
the
product
manager
for
work,
it
lab
Gio
and
I'm,
giving
you
a
quick
overview
today
of
what
we
are
going
to
do
in
12.8.
First,
a
quick
overview
of
the
roadmap.
As
you
can
see,
we
have
quite
a
few
epics
in
flight
at
the
moment.
So,
if
you're
interested
in
the
hierarchy,
you
can
look
at
this
but
I'm
going
to
give
you
a
more
granular
sort
of
plan
for
for
12.8,
okay.
A
So
in
12.8
we
are
going
to
invest
time
to
deliver
some
valuable
features
to
you
and
three
areas,
and
the
first
one
I'm
going
to
talk
about
here
is
the
Geo
uncom.
So
I've
talked
about
that
quite
a
bit
in
the
past,
we
are
currently
undergoing
quite
a
bit
of
effort
to
enable
review
for
disaster
recovery
on
get
that
becomes
our
largest
instance
of
gitlab
and
so
actually
having
JIRA
enabled
uncom
will
essentially
ensure
that
any
kind
of
performance,
bottlenecks
or
issues
that
come
with
scale
are
exposed.
A
We
will
use
our
own
product
and
we
value
that
quite
highly
etiquette
lab.
So
what
we
are
doing
at
the
moment-
and
we
hope
to
accomplish
this
for
12.8-
is
rolling
out
Geo
to
the
staging
environment.
First.
So
specifically,
the
biggest
thing
that
we
are
attempting
to
finish
in
12.8
that
we
didn't
quite
finish
in
12.7
is
creating
the
secondary
node
for
for
staging
that's
the
most
important
first
step
and
following
that
there
are
other
tasks
but
monitoring
and
documenting
all
of
the
individual
steps.
A
A
So
what
we've
done
already
is
essentially
finish.
A
number
of
proof
of
concepts
to
actually
understand
is
what
we
have
in
mind
here
is
really
possible
and
those
were
were
actually
successful.
So
we've
closed
them
off.
We
have
established
that
we
believe
it
is
possible
to
create
sort
of
a
self-service
framework,
including
you
know,
developer
documentation,
and
you
know
a
system
that
allows
others
to
actually
contribute
geo
data
types
so
for
12.8.
What
we're
going
to
do
now
that
the
PCs
are
are
done?
A
We
will
likely
not
finish
all
of
these
items
here
in
12.8,
but
we
are
aiming
to
to
get
a
like
first
like
producing
the
create
events
for
new
package
files
done
and
consuming
the
create
events
for
packaged
files.
They
may
be
more,
but
the
we
are
starting
on
this
journey
right
now
and
I
think
it's
actually
quite
exciting.
A
The
the
thing
we
are
also
investigating
in
the
disaster
recovery
space
is
improving
support
for
a
planned
failover,
and
this
is
essentially
a
situation
where
you
would
like
to
use
a
G
or
secondary
to
say
over
to
in
case,
for
example,
data
center
maintenance
or
just
as
part
of
your
business
continuity
planning
and
for
12.8.
We
are
going
to
finish
investigating
causing
database
replication.
We've
started
this
in
12.7.
A
We
are
a
little
bit
overdue
with
this,
so
we
want
to
establish
how
easy
it
is
to
actually
cause
database
replication
on
the
secondary,
which
would
essentially
enable
us
to
you
know,
like
pause
replication
completely
on
a
secondary
and
isolated
from
a
primary,
which
is
quite
handy
and
if
you,
for
example,
upgrade
the
primary
or
you
need
to
roll
back
to
the
primary.
You
know
you
really
isolate
these
two
instances
from
other
another
thing
that
we're
going
to
actually
POC
in
12.8
is
a
maintenance
or
read-only
mode.
This
is
helpful
in
a
number
of
scenarios.
A
One
is
also
related
to
planned,
fail
overs.
Essentially,
what
we
need
to
guarantee
is
that
all
changes
that
we
made
on
the
primary
are
also
replicated
to
the
secondary,
and
in
order
to
do
this,
it
can
be
quite
valuable
for
our
customers
to
essentially
stop
at
users
from
making
changes
to
the
primary
then
waiting
until
all
changes
are
replicated,
and
at
that
point
we,
for
example,
can
can
continue
with
a
planned
failover.
So
this
is
one
of
the
scenarios
here.
That
is
quite
important.
A
Lastly,
there
are
two
items
with
gate
lab
13
point:
oh,
so
the
major
release
coming
up,
Postgres
11
will
be
supported
and
encouraged,
and
we
are
already
starting
to
investigate
the
upgrade
procedure
from
40
40,
oh
users
that
are
on
post
press
nine
point
six
or
Postgres
ten
to
eleven.
So
this
is
something
that
we're
pushing
for
this
release
that
will
ensure
that,
when
a
new
post,
with
version
is
becoming
available,
that
the
upgrading
is
smooth
and
doesn't
require
any
specific
changes.
A
Similarly,
we
need
to
install
that
Geo
installations
still
continue
to
work
with
post
press
eleven.
So
a
fresh
installation
should
work
with
post
question
out
of
the
box
and
in
twelve
point
eight
we
were
working
with
the
distribution
team
to
actually
make
sure
that
that
happens,
and
these
are
all
the
things
that
we
are
certainly
are
going
to
do.
In
twelve
point,
eight,
there
are
some
like
further
work,
that
is
in
the
validation
track,
some
things
that
are
maybe
a
little
bit
further
down
the
line.
So
the
first
one
is
improvements
to
the
administrator
experience.
A
We
are
hoping
to
schedule
some
interviews
to
work
with
systems
administrators
to
understand
the
tasks
they're
trying
to
perform
using
the
Geo
UI,
and
you
know
where
the
shortcomings
are
to
then
iterate
towards
the
better
user
experience.
We
are
also
going
to
work
on
some
initial
designs
for
how
a
maintenance
mode
could
look
like,
so
this
is
somewhat
dependent
on
the
proof-of-concept
I
talked
about,
so
this
is
going
to
start
off
soon
and
then
also
we
are
starting
to
review
with
the
Geo
installation
process
and
thanks
to
a
new
designer,
not
so
new.
A
A
That's
pretty
much
it.
Thank
you
for
joining.
We
forward
to
12.8
I
think
we
are
pretty
excited
about
all
of
those
items.
The
Toa
self-service
framework
is
a
significant
change
and
how
we
think
about
geo
and
I
think
it's
going
to
be
exciting
to
hear
how
how
this
goes
in
the
future.
This
should
hopefully
result
in
significantly
faster
iterations
and
move
to
you
closer
to
a
complete
solution.
So
thanks
for
joining.