►
From YouTube: GitLab Kickoff meeting - Geo 12.4
Description
Fabian Zimmer (Product Manager, Geo) highlights new features and direction for GitLab Geo in 12.4.
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[]=maturity%3A%3Acomplete
A
Hello,
everyone,
this
is
Fabian
the
product
manager
for
a
good
lap,
Gio
and
I
am
going
to
give
you
a
quick
overview
of
the
road
map
and
what
we
are
going
to
do
for
a
twelve
point.
Four,
so
let
me
quickly
share
my
screen,
so
you
can
have
a
look
at
Gio,
okay,
so
the
first
thing
is:
I
spoke
about
what
we're
going
to
do
in
in
twelve
point
three
a
little
while
ago
and
I
just
wanted
to
quickly
recap
and
tell
you
where
we
are
at
right
now.
A
So
in
this
clip
of
meeting
they
are
not
too
many
completely
new
features
I'm
going
to
discuss
because
we
still
are
releasing
some
of
the
things
that
we
intended
to
release
in
twelve
point
to
late
twelve
point
three,
and
so
we
have
to
work
work
through
that.
The
two
items
that
were
a
little
bit
more
involved
than
initially
thought
we're
the
improved
object,
storage
support
so
allowing
the
replication
of
items
in
in
object,
storage
natively.
So
this
is
very
actively
being
worked
on
and
many
merge
request
already
filed.
A
So
we
hope
to
finish
this
by
twelve
point.
Three,
but
I'll
keep
you
posted
and
the
second
one
is-
and
this
is
the
support
for
replicating
docker
registries.
So
this
is
largely
merged.
We're
really
excited
to
release
this,
but
those
items
were
larger
than
we
initially
anticipated,
and
so
some
of
the
time
in
twelve
point
three
was
was
taken
up
by
our
engineers
and
the
team
to
actually
get
this
done,
because
we
didn't
want
to
release
something
that
we
don't
think
is
going
to
add
much
value.
A
Okay,
so
the
first
thing
I
would
like
to
actually
talk
about
is
enabling
geo
for
disaster
recovery
on
uncom
and
I
already
pointed
out
last
time
that
this
is
important
and
ongoing
effort
in
collaboration
with
infrastructure.
But
I
think
this
is
sort
of
the
the
main
thing
I
would
like
to
highlight
as
a
slight
shift
in
in
focus
for
the
team
as
well.
So
we
are
accelerating
our
efforts
inside
geo
to
actually
allow
us
to
enable
this
fully.
A
There
are
still
some
roadblocks,
but
at
the
moment
we
are
understanding
what
the
things
are
that
are
left
to
be
done,
so
that
we
can
actually
enable
this
basically
with
with
priority.
So
the
first
like
big
focus
for
12.4,
is
in
enabling
disaster
recovery,
and
there
are
many
good
reasons
for
doing
it.
One
of
them
is
is
dogfooding
s
and
we
want
to
use
geo
as
part
of
our
own
product
and
as
part
of
Luca,
Capcom
and
so
I
think.
This
is
something
that
that
is
really
really
important
to
us,
and
we
will.
A
We
will
double
down
on
that.
So
this
is
the
first
item,
but
we
are
still
a
little
bit
in.
We
have
a
couple
of
items
that
are
are
being
blocked
that
are
quite
technical
regarding
rake
tasks,
but
we're
also
working
on
breaking
this
down
little
bit
further.
So
the
next
time
when
I
speak
to
you,
we
have
a
better
detailed
understanding
of
this.
A
So
the
second
thing
is-
and
these
are
high-level
items-
I'll
talk
about
this
theme
again
to
remind
you.
So
there
is
an
ongoing
effort
to
verify
all
the
all
the
data
that
we
actually
have
in
NGO,
and
this
is
actually
quite
involved.
So
we
had
a
few
discussions
inside
the
team
on
how
we
can
break
this
down
further
and
in
12.3.
We
already
intended
to
do
a
little
bit
of
work
on
that,
but
going
forward
to
twelve
point
four,
we
are
also
going
to
focus
on
a
plate,
upload
verification.
A
A
The
closest
to
you
know,
I
think
this
is
something
that
we
will
be
able
to
deliver
in
in
12.4,
so
we
have
to.
We
had
to
postpone
this
a
little
bit
because
of
other
work,
but
we're
still
intending
to
do
that
and
also
we
are
in
the
process
of
gathering
more
information
from
our
users
and
understanding
how
they
use
geo.
So
this
is
something
that
that
we
actually
need
to
do,
but
this
is
again
that
was
postponed.
A
This
is
something
that
we
initially
thought
we
could
get
done
into
8.3
because
of
a
lot
of
the
sort
of
deeply
understanding
what
we
eat.
What
we
need
to
do
and
why
we
do
the
things
in
in
a
specific
way.
This
is
taking
a
little
bit
longer,
and
so
this
is
also
something
you
know
that
is
happening
in
12.4,
also
because
changing
the
way
we
perform
upgrades
has
a
lot
of
ramifications
and
implications
for
for
you.
A
So
we
want
to
make
sure
that
the
changes
that
we
was
here
robust-
and
you
know
that
we
really
understand
that
this
will
work
out.
So
this
is
work
that
is
happening
here
and
then,
finally,
as
an
effort
to
actually
add
more
data
sources
to
to
geo.
So
this
is
something
that
is
currently
definitely
a
limitation.
I
can
quickly
show
you
in
the
in
the
documentation,
so
the
unreplicated
data
types.
A
So
there
quite
a
few
data
types
that
currently
are
actually
not
replicated
using
using
geo,
and
so
the
next
item
that
we
actually
go
in
to
enable
here
are
designed
repositories
as
part
of
the
design
management,
and
this
is
this
is
a
recent
feature
that
is
still
in
an
early
stage.
But
we
would
like
to
demonstrate
that
we
can
actually
support
this
in
geo
as
well.
A
So
that
was
also
scheduled
for
for
12.3,
but
now
we
moved
it
into
into
12.4,
and
we
hope
that
by
by
the
end
for
the
release,
we
have
full
support
in
geo
for
for
those
design
repositories.
A
few
other
activities
that
we
wanted
to
start
a
little
bit
earlier,
making
doing
some
more
research
on
how
we
can
improve
the
installation
and
also
starting
to
think
about
promotion.
Promotion
and
failover
are
pushed
a
little
bit
back
because
we
have
to
you
know
finish
what
we
what
we
started
in
in
12.3
and
now
in
12.4.
A
But
this
is
definitely
still
an
area
that
we
are
very
interested
in
and
we
are
probably
going
to
be
able
to
start
thinking
about
this
a
little
bit
more
actively
after
12.4,
and
that's
that's
all
that
I
wanted
to
talk
to
you
about.
So
the
main
features
for
the
release
and
you'll
see
this
in
the
in
the
kickoff
document.
Are
the
support
for
the
design
repositories
more
active
work
here
on
the
upload
verification,
the
single
get
URL
for
for
all
of
geo,
which
would
make
it
a
lot
easier
to
use.
A
Excuse
me,
and
we
also
are
going
to
look
at
a
rake
task
for
automating
some
parts
of
the
the
geo
upgrade
process
and
yeah
other
than
that.
We
hope
to
finish
the
the
12.3
scheduled
tasks
will
be
soon.
The
12.2
scheduled
tasks
will
assume
both,
including
the
object,
storage,
replication
and
talk
of
registry
application.
So
that's
all
for
me.
Thank
you
very
much
and
see
you
next
time.