►
From YouTube: GitLab 15.4 Kickoff - Enablement:Geo
Description
Planning issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5041
Geo group past kickoff Videos: https://www.youtube.com/playlist?list...
Presentation by: Sampath Ranasinghe, Sr. Product Manager, Geo
A
Hello:
everyone,
my
name,
is
sambad
ramazinga
and
I'm.
The
product
manager
of
a
group
Geo
today
I'll
be
taking
you
through
the
15.4
outlook
for
the
group,
so
we'll
start
with
moving
existing
data
types
into
the
self-service
framework.
As
you
may
already
know,
the
self-service
framework
provides
a
well-defined
interface
and
a
consistent
logic
that
can
be
used
to
replicate
data
and
verify
data
between
geosites.
A
All
new
data
types
will
be
based
upon
replication
and
verification
will
be
based
upon
the
self-service
framework,
and
we
have
already
moved
a
number
of
existing
data
types
to
the
self-service
framework
and
we
continue
the
effort
to
remove
the
remaining
few
data
types
into
this
framework
as
well.
The
framework
provides
a
consistent
way
for
new
additional
data
types
to
be
added
quickly,
such
that
they
can
be
a
replicated
and
verified
across
geosites,
thus
accelerating
our
development
and
innovation.
A
Geo
I
said
well
the
first
item
on
the
list
of
date.
Existing
data
types
that
we
we've
been
working
on
is
wikis
and
projects
so
that
this
has
been
an
ongoing
piece
of
work
that
that's
that
started
a
couple
of
Milestones
ago.
We
continued
to
make
progress
on
this.
We've
decomposed
the
effort
into
a
number
of
issues
and
we'll
be
making
progress
within
this
Milestone,
we'll
also,
as
part
of
the
effort,
add
the
ability
to
sync
and
resync
and
verify
individual
items
in
the
replica
view.
A
This
is
a
capability
that
was
already
existing
for
projects
and
wikis
and,
as
we
make
progress
on
a
projects
and
wikis
in
the
self-service
framework,
all
replica
views
will
benefit
from
this
effort
as
as
well
next
up
we'll
be
moving,
it
will
continue
the
effort
to
move
the
container
registry
to
the
self-service
framework.
We've
made
very
good
progress
in
the
last
Milestone
and
we
are
hoping
to
complete
this
effort
in
the
next,
a
milestone
which
is
15.
A
form
on
the
ux
research
and
improvements
front
sunyung
is
pursuing
the
CM
scorecard
replication
exercise.
We
are
aiming
to
achieve
a
maturity
level
of
complete
in
this
quarter
for
for
application,
Geo
replication,
so
there'll
be
customer
interviews
to
help
us
back
up
a
statement
regarding
geo-reaching
majority
level
complete.
A
We
will
also,
as
part
of
this
effort,
revisit
the
the
information
on
the
Geo,
UI
and
Terminals,
and
this
is
largely
to
to
streamline
and
make
the
setup
and
operation
of
Geo
better.
Then
then,
we've
got
the
ux
scorecard
exercise
for
installation
and
configuration
experience
again
focused
around
the
replication
piece,
but
it
also
applies
to
the
disaster
recovery
as
well,
so
we'll
be
evaluating
the
The
Experience
typical
systems
administrator
will
go
through
and
identify
pain
points
and
then
insights
that
we
can
take
away
to.
A
You
know
to
improve
the
overall
experience
for
for
setting
up
Geo
and
then.
Lastly,
we
have
a
number
of
miscellaneous
items
that
are
largely
focused
around
bugs
and
then
defects
that
that
we
we
hope
to
address
in
this
Milestone
as
well,
and
that
essentially
concludes
the
outlook
for
15.0
for
the
group,
Geo
and
I
hope
to
see
you
in
the
next
update.
Thank
you.