►
From YouTube: GitLab Kickoff meeting - Geo 12.3
Description
Fabian Zimmer (Product Manager, Geo) highlights new features and direction for GitLab Geo in 12.3.
Geo Product Strategy: https://about.gitlab.com/direction/geo/
Geo Roadmap: https://gitlab.com/groups/gitlab-org/-/roadmap?label_name%5B%5D=group%3A%3Ageo&label_name%5B%5D=maturity%3A%3Aviable&scope=all&sort=start_date_asc&state=opened&utf8=%E2%9C%93
A
Today,
I'm
going
to
give
you
a
quick
overview
of
where
we
are
at
with
Gio
and
I'm,
also
going
to
highlight
some
of
the
specific
items
for
12.3,
which
is
the
release
for
the
22nd
of
September.
So
what
I'll
do
is
I'll
walk
you
through
the
roadmap
and
then
I'll
highlight
a
few
specific
items
that
I
think
are
valuable
for
us,
our
users
to
actually
have
a
deep
understanding
of,
but
a
lot,
you
possibly
view
a
broader
context
of
what
is
happening.
So
the
first
thing
to
know
is
that
this
is
the
Geo
boat
night.
A
At
the
moment,
it
is
labeled
with
a
good
geo
label,
and
it
is
all
the
epics
that
we
believe
are
required
to
be
finished
up
to
increase
the
category
maturity,
maturity
for
both
gee
replication
and
for
disaster
recovery
from
minimal
to
viable.
So
this
is
not
all
epics
that
exist.
It
is
those
that
we
have
already
grouped
into
a
maturity
level,
and
so
I'll
walk
you
through
those,
if
you're
interested
in
actually
understanding
a
little
bit
more,
why
we
believe
these
these
epics
are
important
and
how
they
fit
into
our
longer-term
strategy.
A
You
can
also
check
out
the
category
strategy
for
geo
replication
here.
It
gives
you
an
overview
of
our
roadmap
where
we're
headed.
What's
next,
what
we're
thinking
about
and
I'll
try
to
keep
this
one
updated
so
that
it's
always
pointing
to
the
right
things.
The
same
for
the
category
category
strategy
for
disaster
recovery
just
have
a
read:
they're,
quite
informative,
but
back
to
the
roadmap.
A
So
the
first
thing
that
I
quickly
wanted
to
highlight
is
dogfooding
is
really
important
to
get
that
and
the
Geo
team
is
continuously
supporting
our
infrastructure
engineering
to
enable
and
further
Geo
use
at
github
comm.
So
I'm
not
going
to
go
into
too
much
detail
here,
but
this
is
an
ongoing
effort
and
we
still
have
a
little
bit
of
work
to
do
in
order
to
actually
and
people
all
parts
of
GU
on
em
kept
calm.
But
that
is
the
top
item,
and
I
will
probably
have
a
few
updates
on
this
or
another
release.
A
A
All
of
this
is
manual,
and
so,
if
you
look
at
the
long
list
of
items
here
that
we
are
working
on,
the
next
step
is
the
automation
of
their
education
for
those
parts.
So
this
is
one
item
that
I
wanted
to
highlight.
So
this
is
something
that
me
will
lose
weight:
West
Point
3,
where
we're
actually
looking
at
ensuring
that
all
the
necessary
verification
steps
are
by
properly
automated.
A
So
for
the
22nd
of
September
4th
point
3,
we
look
at
automation
and
you
see
that
in
the
release
talk
as
well.
The
next
item
here
is
automatically
choosing
the
geo
node
for
the
best
user
experience,
and
this
is
actually
something
that
I'm
really
excited
about.
I
did
a
little
bit
of
user
research
already
I
work
very
closely
with
one
of
our
engineers
on
understanding
what
we
can
do
to
actually
make
the
user
experience
for
geo
a
little
bit
better
and
one
of
the
pain
points
that
was
highlighted
is.
A
If
we
go
look
at
this
in
detail.
It
is
that
for
many
of
our
customers
who
use
geo,
they
may
have
more
than
one
secondary
and
at
that
point,
from
a
sort
of
systems,
administrative
perspective.
One
of
the
issues
is
that
they
then
are
in
a
position
where
they
have
to
maintain
several
different
URLs
for
for
the
grid
configurations,
so,
for
example,
us
don't
example,
comm,
EU
and
so
on
and
so
forth,
and
that
gets
quite
cumbersome
if
you
have
20
or
maybe
not
that
many,
but
quite
a
few
secondary
instances.
A
So
what
we
are
going
to
do
is
essentially
cover
two
parts
of
this.
The
first
one
is
working
towards
a
more
transparent,
deep
configuration
for
teal
so
that
there
is
a
single
URL
that
connects
you
automatically
to
the
white
geo
node.
The
second
bit
is,
and
I'll
talk
about
that
in
a
little
while
is
to
improving
the
web
interface
experience.
A
But
this
year
the
first
part
fully
transparent,
deep
configuration
is
something
that
you
actually
take
off
for
12.3.
If
I
go
to
this
in
a
little
bit
more
detail,
the
problem
here
is
really
one
of
configuration
and
documentation.
So
this
is
something
that
we
believe
we
can
do
already,
but
we
want
to
make
it
easier
for
our
customers
to
understand
what
steps
are
necessary
to
allow
geo,
for
example,
to
work
in
conjunction
with
a
geo
aware
in
a
service
for
it
you're
aware
load
balancer.
A
So
this
is
something
that,
when
they
configuration
much
easier
because
there's
only
one
URL
that
you
need
to
actually
add
to
your
configuration
and
if
the
DNS
service
or
load
balancer
can
figure
out
what
the
best
geo
node
is
to
actually
access
and
I
think
that
will
make
using
geo
along
easier.
And
so
this
is
one
of
the
items
that
we
go
to
tech
afford
for
12.3.
A
The
other
thing
that
we
are
going
to
do
some
user
research
in
collaboration
with
the
UX
department,
is
to
actually
understand
a
little
bit
more
how
users
are
using
the
secondary
and
primary
web
interfaces,
and
one
of
the
questions
that
we
are
trying
to
answer
is
if
the
user
experience
of
the
Geo
primary
web
interface
is
actually
acceptable
to
our
users.
That's
something
we
don't
know
so.
The
secondary
no
one's
actually
exposed
a
read-only
web
interface.
A
So
if
you
wanted
to
make
a
change,
you
have
to
go
to
the
primary
and
we're
interested
in
understanding
if
the
performance
and
user
experience
of
the
primary
web
interfaces
is
acceptable,
because
that
would
allow
us
to
make
some
choices
regarding
the
future
of
web
UI
is
in
the
secondary.
So
this
is
really
exciting
and
we
are
working
on
that
in
12.3
and
depending
on
the
outcomes
of
that,
we
may
be
in
a
better
position
to
actually
make
some
decisions
here.
So
that's
something
to
to
also
highlight
it
closely.
A
So
if
we
look
at
the
mode
map,
this
is
also
the
reason
why
we're
certain
that
this
epic
will
expand
or
extend
a
little
bit
further
than
to
12.3,
because
based
on
the
user
research
that
we're
doing
for
the
12.3
lease
in
September
based
on
those
findings,
we
will
need
to
do
something.
After
that
we
don't
quite
know
what,
but
that's
the
spirit
of
iteration.
We'll
do
a
follow-up
here.
So
obviously
the
further
here
in
the
future,
the
more
uncertain
things
get.
A
A
We
are
looking
at
simplification
of
the
G
upgrade
process,
so
this
is
really
in
recognition
that
there's
lots
of
manual
steps
for
upgrading
and
we
are
making
some
small
changes
actually
to
how
the
upgrade
procedure
works,
potentially
automating
some
menu
interventions,
but
it's
a
it's
an
iterative
process
and
at
the
moment
we
are
working
on
those
and
we
hope
that
it
makes
it
easier
to
actually
upgrade
based
on
how
this
code
this
code,
we
may
need
to
iterate
little
bit
further,
but
this
is
currently
ongoing.
The
same
is
true
for
improving
object,
storage.
A
So
these
are,
it
was
talk
to
items
here.
You
see
a
new
upgrade
and
object
storage
and,
lastly,
or
not.
Lastly,
but
next
is
adding
unreplicated
datatypes,
and
this
is
quite
important
for
disaster
recovery
and
other
reasons.
So
if
we
go
a
little
bit
more
into
detail
here,
we've
already
done
a
little
bit
of
work
and
this
will
also
come
part
of
the
documentation,
but
I
think
it's.
It's
really
important
to
try
like
this.
A
This
is
definitely
something
that
we
are
attempting
to
change
right
now,
because
from
our
perspectives
and
I
think
our
customers
also
agree.
It
is
really
important
that
some
of
the
new
features,
some
new
things
that
we
do
are
also
then
supported
by
fight
yield.
So
if
you
look
at
for
you
to
this
table,
I
believe
at
the
moment
we
replicate
9
out
of
19.
So
this
is
definitely
something
better
and
we're
already
working
on
this.
A
So
one
of
the
things
that
we
are
currently
doing
for
12.2
is
okay
custom
hooks,
but
for
12.3
we
focus
on
design
repositories.
So
this
is
something
that,
through
the
awesome
work
of
one
of
the
group
CIP
lab,
we
are
having
design
management
features
right
now,
which
then
I
designed
with
posit
or
ease
and
they'll,
can
go
a
little
bit
more
into
detail
here.
A
I
also
properly
replicated
using
geo
so
that
our
our
customers
can
actually
benefit
from
from
having
those
available
on
all
secretary
nodes,
and
so
there's
a
bunch
of
tickets
in
here
that
are
a
little
bit
too
too
detailed
to
go
into
right
now,
but
you
can
see
this
is
work
we
also
scheduled
for
12.3,
but
I
think,
looking
at
this
epoch
here
should
give
you
a
good
understand
of
what
we're
trying
to
achieve
and
pulling
back
to
the
roadmap.
So
this
year
the
design
repositories
actually
belong
to
the
add-on
replicated
data
types.
A
Unfortunately,
we
can
see
the
relationship
here,
the
roadmap,
that
we
can
imagine
these
these
things
they
belong
together
and
then
finally,
I
wanted
to
also
highlight
two
other
endeavors
that
we're
going
to
start
pretty
soon.
So
the
one
is
really
focusing
on
the
user
experience
of
deal
and
understanding
how
we
can
make
geo
simpler
to
install
and
there's
a
lot
of
interesting
ideas
and
at
the
moment
it
is
I
think
relatively
cumbersome
to
set
up
geo.
A
But
we
are
not
in
a
position
right
now,
where
we
have
a
good
enough
understanding
of
the
problem
and
good
enough
understanding
of
the
solution.
So
what
we
will
do
there
is
in
August
and
we're
starting
in
August
and
September
is
to
really
understand
you
know
what
are
the?
What
are
the
things
we
can
do
here?
What
are
the
the
problems
for
our
users?
Maybe
do
some
user
research
to
tackle
this?
A
We
expect
this
will
probably
extend
into
the
autumn,
but
that's
something
we
believe
is
important
for
for
you
and
then
lastly,
promotion,
emotion
and
failover,
so
this
is
at
the
moment,
the
relatively
large
epic
dealing
with
quite
a
few
different
concerns,
but
one
of
the
problems
here
for
our
disaster
recovery
strategy
is
really
to
improve
the
process
for
how
to
actually
recover,
promote
primate,
promote
the
secondary
to
primary
D
mode.
Failing
over.
A
We
are
attempting
here
to
you,
know,
really
do
some
planning
some
user
research
understand
this
and
then
update
you
in
the
in
the
next
call
on
whatever
our
progress
is
so
yeah
if
I,
if
I
have
to
summarize
this
again
for
this
item
here
automatically
choose
the
the
geo
node,
the
issue
that
I
think
will
deliver
a
lot
of
value
in
12.3
is
the
documentation
on
how
to
use
a
single
URL
so
making
making
geo?
Essentially
you
play
well
with
geo,
aware
DNS
service
or
something
similar.
A
So
this
is
one
of
the
Direction
items,
then
for
verification
of
all
replicated
data.
The
12.3
item
that
is
important
to
highlight
again
is
the
automation
effort
that
you
will
undergo.
So
this
is
essentially
the
next
iteration
after
verifying
all
of
the
energetic
objects
drop
artifacts.
So
this
is
this
one
I
think
this
is.
This
is
great,
because
the
better
we
automate
the
easier
it
will
be
for
everyone
to
use.
So
this
is
another
one
and
then
finally,
it
is
really
the
do
support
for
design
repositories.
A
It's
a
new,
interesting
and
cool
feature
that
we
hope
will
gain
a
lot
of
traction
and
we
want
to
make
sure
that
here
at
geo,
we
support
those
efforts
as
well-
and
this
is
the
the
other
item
that
we
are
going
to
push
for
game,
12.3
and
they're.
Obviously,
lots
of
like
other
issues
that
are
like
be
prepared
that
we
work
on.
So
this
is
a
selection
that
I
thought
was
interesting
and
should
give
you
a
good
idea
of
what
we
are
doing
in
12.3.
So
that's
it.