►
From YouTube: Gitlab 15.1 Kickoff - Enablement:Geo
Description
Planning issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5036
Geo group past kickoff Videos: https://www.youtube.com/playlist?list...
Presentation by: Sampath Ranasinghe, Sr. Product Manager, Geo
A
So,
let's
start
with
the
first
item
on
the
list,
will
we
will
continue
moving
existing
legacy
data
types
into
the
self-service
framework?
The
self-service
framework
provides
a
consistent
interface
for
adding
new
data
types
in
into
the
geo
replication
logic
and
also
allows
other
teams
to
leverage
the
replication
logic
as
well
for
their
data
types.
A
In
this
milestone,
we'll
be
looking
to
move
projects
and
wikis
to
the
self-service
framework.
We
may
well,
as
we
decompose
this
issue,
separate
it
into
two
efforts,
starting
with
projects
followed
by
wikis,
we'll
also
look
to
tackle
moving
container
registry
to
the
self-service
framework
as
well.
A
We're
also
looking
to
ga
git
lab
objects,
geo
object,
storage,
replication
in
this
milestone.
If
you,
you
might
remember
that
we
were
looking
to
ga
this
in
the
150
milestone.
However,
we
found
some
issues
with
the
with
with
the
effort
and
we
want
to
address
those
prior
to
making
this
ga
also.
In
addition,
we've
decided
to
split
this
effort
into
two
one
being
replication,
two
being
verification,
verification
will
be
tackled
in
a
separate
milestone
later.
A
We
also
continue
to
add
capabilities
to
to
the
secondary
site
proxy
proxy
to
the
primary
side.
In
this
particular
case,
we've
been
looking
at
adding
secondary
sites
with
separate
urls
the
ability
to
give
them
the
ability
to
proxy
to
the
primary
site
in
the
15-0
milestone.
A
We'll
also
look
to
conclude
the
cm
scorecard
for
disaster
recovery
in
in
this
milestone.
Initially,
this
was
targeted
for
the
15-0
milestone.
A
However,
we've
had
some
challenges
with
recruiting
volunteers
to
complete
this
exercise
and
we
will
be
looking
to
complete
it
if
not
in
15-0,
in
15-1,
we'll
also
make
a
few
other
ui
enhancements
around
the
unboxing,
so
we'll
remove
some
of
the
boxing
around
the
ui
components
in
this
release
and
finally,
we've
we've
decided
we
we
found
that
we
there
is
a
significant
benefit
in
switching
the
initial
replication
from
using
git
fetch
to
git
clone.
Actually,
we've
seen
a
27
performance
improvement
with
the
switchover
and
we
were
hoping
to
make
this
available
in
15.00.