►
From YouTube: Gitlab 15.0 Kickoff - Enablement:Geo
Description
Gitlab 15.0 Kickoff - Geo Group
Planning issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5034
Geo group past kickoff Videos: https://www.youtube.com/playlist?list=PL05JrBw4t0KoY_6FXXVgj7wPE9ZDS4cOw
Presentation by: Sampath Ranasinghe, Sr. Product Manager, Geo
A
Hello,
everyone,
I'm
the
product
manager
for
geo
and
I'll,
be
taking
you
through
the
15.0
kickoff
video
for
jio
and
I've
been
joined
by
janis
rusos,
who
is
the
product
manager
for
the
database
and
memory
group?
A
Okay,
so
looking
at
15.0
in
14.10,
we
started
moving
existing
data
types
to
the
geoself-service
framework.
The
jio
self-service
framework
simplifies
integration
of
the
new
data
types
with
the
jio's
replication
logic.
A
We
have
moved
most
of
the
data
types
with
the
exception
of
a
few
already,
namely
we
have
leftover
projects
and
wikis
designs,
container
registry
and
ci
job
artifacts
now
ci
job
artifacts
are
almost
done
and
may
may
well
make
it
into
1410.
A
Next
up
is
ga
for
object,
storage
replication,
rather
than
relying
on
object,
storage,
replication
by
object,
storage
providers.
This
feature
provides
gitlab,
managed,
object,
storage,
replication
using
a
consolidated
object.
Storage
configuration
simplifies
the
gitlab
configuration
and
has
several
other
advantages.
A
Next
up
is
the
geo
proxy
feature.
Jio
introduced,
unified
urls
in
14.6
and
proxying
works
well
in
this
configuration
where
the
secondary
site
proxies
the
request
back
to
the
primary
site,
if
it
cannot
serve
it
locally.
However,
there
are
legitimate
use
cases
for
having
separate
urls
for
the
secondary
sites.
A
And
then,
lastly,
in
terms
of
the
large
large
features
that
we
hope
to
achieve
in
this
release,
we
will
be
following
best
practices
to
ensure
geo
is
up
to
date
and
compatible
with
the
latest
release
of
rails
with
rail
six
many
databases,
support
15.0,
is
also
a
major
release
and
a
key
milestone
where
we
make
deprecations
and
breaking
changes
and
geo
is
no
exception
to
this,
and
we
will
review
and
remove
these
in
this
release
details.
A
I
won't
go
into
on
this
on
this
recording,
but
you're
welcome
to
look
through
the
issues
here
in
the
in
the
deprecations
issue
and
there
are
quite
a
number
to
go
through.
Let
me
just
open
the
correct
page
here
I
run
quite
a
number
to
go
through
and
we'll
we'll
take
you
through
that.
A
Now,
a
couple
of
other
items
we
will
hope
to
be
looking
to
to
achieve
in
this
release
is
the
category
maturity
scorecard
for
disaster
recovery.
We
believe
disaster
recovery
has
reached
maturity.
However,
we
always
validate
this
with
customer
data
and
interviews
and
in
this
release.
As
part
of
this
release,
we
will
be
looking
to
achieve
that.
A
And
we
have
a
significant
performance
improvement
that
that
we
have
been
able
to
achieve.
In
the
first
time,
replication
for
git
data
geo
has
improved
the
first
time.
A
Experience
of
setting
up
a
secondary
site
by
switching
from
git
fetch
to
git
clone
we've
been
able
to
gain
approximately
27
performance
improvement
with
with
this
change,
and
this
feature
is
likely
to
make
1410,
but
we've
got
a
placeholder
in
150
in
case
there's
any
rollover
work
for
us
to
do
to
complete
this,
so
I'm
very
excited
about
15,
15,
0.
A
and
just
to
recap,
what
we'll
be
looking
to
achieve
with
15
15.00
continue
to
make
progress
with
migrating
all
existing
data
to
to
the
self
service
framework,
a
ga
object,
storage,
replication,
improve
the
proxying
feature
and
also
get
up
to
speed
with
the
rails.
Six
many
databases
update
as
well.