►
From YouTube: Gitlab 16.2 Kickoff - Enablement:Geo
Description
Gitlab 15.9 Kickoff - Geo Group
Planning issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5087
Geo group past kickoff Videos: https://www.youtube.com/playlist?list=PL05JrBw4t0KoY_6FXXVgj7wPE9ZDS4cOw
Presentation by: Sampath Ranasinghe, Sr. Product Manager, Geo
A
Hello,
everyone
welcome
to
another
edition
of
Geo
groups:
Outlook
This,
Time,
It's,
For,
16.2
I
will
start
off
with
moving
existing
data
types
into
the
self-service
framework.
The
self-service
framework
provides
a
single
framework
to
which
you
can
manage
replication
and
verification
of
different
data
types
and
and
components.
A
This
has
enabled
this
will
enable
and
Empower
other
teams
or
to
also
easily
add
new
data
types
and
components
to
to
the
Geo,
replication
and
verification
process.
As
as
new
features
are
created,
there
will
be
new
new
data
types
that
that
need
to
be
replicated
in
order
to
protect
our
customers
against
data
loss.
In
the
event
of
failure,
we've
migrated
a
number
of
data
types,
Legacy
data
types
already
into
the
self-service
framework
and
in
fact
we
migrated.
A
So
we
continue
to
make
progress
on
projects
which
is
the
last
Legacy
data
type
to
be
migrated
to
the
self-service
framework,
and
this
is
by
far
the
most
complex
data
type
and
in
this
Milestone.
The
team
will
continue
to
make
progress
on
this
with
the
with
the
with
getting
us
with
having
all
the
data
types
under
a
single
single
self-service
framework.
A
Next
up
is
gitlab
silent
mode,
so
it
is
important
with
any
disaster
recovery
mechanism
process
to
test
the
mechanism
and
the
procedures
regularly
to
ensure
the
successful
recovery
from
a
failover
event.
One
way
to
achieve
this
is
to
actually
promote
one
of
the
secondary
sites
that
that
is
designated
as
your
Disaster
Recovery
site
and
perform
testing
against
that
against
that
site,
whilst
leaving
the
the
primary
site
operational
to
the
rest
of
the
business.
A
As
you
can
imagine,
promoting
a
performing
such
testing
against
against
a
site
will
generate
outbound
traffic,
such
as
email
notifications,
web
hook,
events
and
and
push
mirror
events.
This
can
be
undesirable
and
somewhat
confusing
for
the
users
when
they
are
receiving
these
from
an
instance
that
they
may
or
may
not
be
aware
of
so
silent
mode
will
allow
you
to
suppress
those
outbound
Communications
whilst
allowing
you
to
continue
testing
that
that
instance,
I
should
add
that
this
is
also
useful
when
you
are
restoring
from
a
backup.
A
If
you
want
to
test
your
backup
image,
for
example,
then
you
can
restore
the
backup
image
and
apply
silent
mode
which
will
suppress
those
outbound
Communications,
but
continue
to
allow
you
to
to
perform
any
particular
testing
that
you'd
like
to
to
do
in
order
to
test
the
viability
of
those
backups
viability
and
integrity.
I
should
add,
we've
already
completed
a
a
couple
of
steps
in
in
the
implementation
we've
added
an
API
control
and
implemented
blocking
off
outgoing
emails.
A
A
This
is
a
cross-stage
effort
and
our
colleagues
in
other
stage
groups
will
be
supporting
us
in
in
delivering
this
delivering
this
feature,
then
we
move
on
to
improving
backup,
restore
documentation
and
guidance
for
for
all
of
our
our
self-image.
Customers.
Backup
and
restore
is
an
important
part
of
any
disaster
recovery
strategy.
They
help
protect
against
militias
and
unintentional
data
corruption.
A
It
is
complementary.
I
should
add
to
the
geodr
solution,
helping
to
protect
against
corruption
that
may
be
replicated
in,
in
certain
cases,
from
the
primary
side
to
the
secondary
site.
The
backup
will
allow
you
to
go
back
in
time
and
and
find
a
copy
of
the
data
before
the
corruption
occurred.
A
Our
backup
and
restore
documentation
has
grown
over
time
and
that
we
have
a
number
of
solutions
accompanied
by
multiple
pages
of
documentation.
This
effort
will
be
to
consolidate
the
documentation,
provide
updated
guidance
on
best
practices
and
best
approaches
for
taking
your
backups
and
restoring
them.
We
will
also
look
at
improving
and
enhancing
the
documentation
for
customers
who
are
on
larger
reference,
architectures
and
and
or
or
that
may
have
large.
Large
data
sets
the
move.
A
We
will
also
be
looking
at
object,
storage,
verification,
we've
already
released,
gitlab,
managed
object,
storage
or
application
to
through
Geo,
so
that
Geo
will
manage
replication
between
the
primary
site
and
the
secondary
sites.
Object,
storage,
buckets
and
the
verification
will
complement
this
feature
by
by
allowing
to
allowing
you
to
check
the
Integrity
of
of
those
two
copies.
A
This
will
also
allow
the
asked
to
make
progress
towards
a
hundred
percent.
A
verification
of
gitlab
replicate
data
geo-replicated
data.
It
also
allows
the
the
speed
up
of
the
process
of
reattaching
a
demoted
primary
site
as
a
secondary
site
by
avoiding
the
need
to
re-reficate
all
of
the
data
instead,
just
running
verification
against
that
data
so
and
ensuring
that
they
are
the
same
between
the
primary
and
the
secondary
side.
A
Next
is
accelerating
Runners
from
from
via
VIA
secondary
geosecondary
sites.
This
isn't
supported
today,
but
our
goal
here
is
to
to
make
this
generally
available.
A
To
start
with,
we,
we
had
a
research
Spike
to
identify
the
gaps
that
would
prevent
us
from
being
able
to
support
this
capability,
and
we've
been
working
through
some
of
the
working
through
addressing
some
of
these
gaps
over
the
last
a
couple
of
milestones,
and
we
continue
to
make
progress
on
addressing
the
remaining
gaps
before
we
make
progress
towards
making
this
capability
generally
available
to
our
customers.
A
Next
is
a
verify
group
wikis,
so
verifying
the
group
Wick
is:
is
another
data
type
that
that
will
take
us
further
towards
being
able
to
verify
100
of
that
replicated
data
group
work
is
already
managed
via
the
self-service
framework.
However,
they
are.
The
verification.
Capability
had
not
been
added
so
in
this
Milestone
we'll
be
looking
to
add
that
capability.
A
Then,
lastly,
we
have
Gathering
monthly,
unique
secondary
site
users
for
forget
operations,
and
we
already
today
have
this
this
metric,
which
is
gathered
for
users
who
access
the
UI
via
the
secondary
site.
However,
this
metric
does
not
account
for
users
who
perform
git
operations
via
the
competitions,
such
as
clone,
pull
push
Etc
against
that
secondary
site.
So
knowing
this
metric
will
give
us
a
qualitative
quantitative
insight
into
how
much
the
secondary
sites
are
being
utilized
by
by
remote
teams
to
accelerate
their
bit
operations.
A
Visibility
into
this
area
will
inform
further
investment
in
in
the
in
the
accelerating
remote
teams
use
cases.
So
this
was
an
important
metric
that
will
complement
what
we
already
have
in
terms
of
you
need
monthly
secondary
site.
Shoes
is,
and
with
that
the
way
we
conclude
Geo
teams,
1612
Outlook.
Thank
you
and
I
look
forward
to
seeing
you
next
time.