►
From YouTube: Gitlab 16.0 Kickoff - Enablement:Geo
Description
Gitlab 16.0 Kickoff - Geo Group
Planning issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5069
Geo group past kickoff Videos: https://www.youtube.com/playlist?list=PL05JrBw4t0KoY_6FXXVgj7wPE9ZDS4cOw
Presentation by: Sampath Ranasinghe, Sr. Product Manager, Geo
A
We'll
start
with
moving
existing
data
types
into
the
self-service
framework,
as
we've
highlighted
in
the
past,
the
self-service
framework
provides
a
single
framework
around
which
we
can
add
new
data
types
for
replication
and
and
verification.
A
It
provides
a
template
for
for
adding
new
types,
and
it
also
enables
other
teams
within
gitlab,
and
you
know,
Community
contributors
to
add
new
data
types
that
can
leverage
Geo's,
replication
and
verification
capabilities
in
this
Milestone,
we'll
be
focusing
on
completing
the
migration
of
projects
into
the
self-service
framework.
This
is
the
last
data
type
Legacy
data
type
that
we
are
hoping
to
migrate
over
to
the
self-service
framework,
by
which
time
we
will
have
all
of
our
different
data
types
replicated
and
verified
through
the
self-service
framework.
A
This
allows
us
to
maintain
the
verification
of
a
replication
logic
much
much
more
easily
and
also
allow
us
to
develop
new
features
at
a
lower
cost
around
the
replication
of
verification
in
in
future.
Iterations
next
up
is
gitlab
silent
mode.
A
When
it
comes
to
Disaster
Recovery,
it
is
important
that
it
is
important
to
test
the
disaster
recovery
mechanisms,
the
infrastructure
and
and
procedures
regularly
to
ensure
successful
recovery.
After
a
failure
event,
one
way
to
achieve
this
is
to
promote
the
secondary
site
secondary
geosite
and
perform
testing
against
this
this
site.
You
can.
A
We
might
appreciate
that
when
you,
when
you
do
this,
it
can
generate
undesired
Communications
towards
end
users
from
this
site,
as
the
testing
is
performed
and
also
create
outbound
Communication,
in
addition
to
to
emails,
for
example,
due
to
other
sites
through
web
Hooks
and
pushmares
for
example.
A
So
the
idea
behind
silent
mode
is
to
suppress
these
outbound
Communications
from
this
site,
which
is
under
test,
so
that
procedures
and
tests
can
be
performed
without
impacting
the
ongoing
business
activities,
while
the
the
main
primary
site
continues
to
serve
the
business
as
usual.
A
A
Next
we're
making
improvements
to
the
backup
and
restore
documentation
for
our
self-managed
customers.
Our
backup
and
restore
documentation
has
grown
over
the
years
and
we've.
We
also
have
multiple
solutions
that
are
documented
in
across
multiple
Pages
within
within
the
gitlab
documentation.
The
the
effort
here
is
to
consolidate
the
documentation
and
provide
improved
guidance
for
our
self-managed
customers.
In
addition,
we
have
a
focus
on
improving
the
guidance
and
documentation
for
our
customers
who
leverage
a
large
reference.
A
Architectures
with
large
data
sets,
we'll
be
doing
some
validation
and
with
respect
to
the
instructions
before
we
update
the
the
documentation
where
we
also
continue
working
on
fixing
the
SSH
timeout
issue
we've
had
when
you
make
pushes
from
the
secondary
site.
There
is
a
60
second
timer,
that
on
on
pushes
from
secondary
sites
towards
primary
sites
that
prevent
customers
from
being
able
to
make
large
push
requests
via
that
secondary
site.
This
prevents
some
some
customers
from
being
able
to
leverage
Geo
to
accelerate
their
remote
teams.
A
However,
we've
hit
a
couple
of
snags
that
we've
been
investigating
and
therefore
will
continue
to
investigate
those
and
try
and
address
those
in
in
this
upcoming
Milestone,
with
a
with
a
goal
to
get
this
across
the
line
and
into
our
customers,
and
so
that
they
can
accelerate
their
remote
teams.
In
particular.
Those
that
have
large
push
requests
next
will
be
allowing
verification
of
object.
Storage
via
in
geo
geo,
already
supports
replication
of
object,
storage
natively
through
through
its
own
framework,
as
opposed
to
leveraging
the
object,
storage
providers
replication
mechanisms.
A
However,
we
do
not
verify
this
replication
today,
so
in
order
to
complete
the
circle,
we'll
be
adding
the
capability
to
verify
object:
storage
as
as
well
through
through
the
Geo
geologic.
A
Next
up
is
a
verifying
group.
Wikis
group
wikis
are
already
migrated
to
the
self-service
framework.
However,
the
verification
capability
is
is
not
currently
present
on
on
cell
types
framework
group
wikis.
So
as
an
in
our
effort
to
get
to
100
verification
of
replicated
geodata,
we
will
be
also
adding
this
capability
to
to
the
studio
in
this
milestone
and
that
completes
our
outlook
for
Milestone
16
for
the
Geo
Group
and
I.
Look
forward
to
seeing
you
next
time.