►
From YouTube: GitLab 15.8 Kickoff - Enablement:Geo
Description
Planning issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5052
Geo group past kickoff Videos: https://www.youtube.com/playlist?list=PL05JrBw4t0KofRx080zwe0VxUEv5yG_nO
Presentation by: Sampath Ranasinghe, Sr. Product Manager, Geo
A
Hello:
everyone,
my
name,
is
sambad
ranasingha
and
I'm.
The
product
manager
for
group
Geo.
Today
we'll
look
at
the
15.8
outlook
for
the
group.
Let's
start
with
moving
existing
data
types
into
the
self-service
framework.
We've
been
on
this
journey
for
for
quite
some
time
and
it
spanned
a
number
of
Milestones.
During
that
time,
we've
been
able
to
move
a
number
of
existing
data
types
into
the
self-service
framework,
and
we've
got
two
two
outstanding
two
to
work
on
and
namely
projects
and
wikis
and
design
repositories.
A
A
On
the
replica
view,
these
capabilities
have
are
currently
missing
on
the
self-service
framework
and
we've
been
busily
adding
and
enhancing
the
self-service
framework
to
bring
those
into
into
operation.
Once
once
this,
this
capability
is
added
to
the
self-service
framework.
We
can
then
migrate.
Projects
and
wikis
without
noticeable
regressions
to
to
the
functionality
of
this
data
type
in
into
the
into
the
self-service
framework
next
is,
is
moving
design
repositories
into
the
self-service
framework.
A
A
Next
up
fixing
timeouts
when
pushing
via
SSH
to
secondary
there
is
currently
a
60
second
Timeout
on
proxied
push
request
it's
a
second
from
the
secondary
to
the
primary
site.
This
is
somewhat
limiting
for
large
push
requests,
as
can
be
expected,
and
our
goal
is
to
to
remove
this
limitation
altogether.
The
solution
will
likely
require
an
architectural
change
to
how
we
handle
SSH
proxy
in
between
the
primary
and
the
secondary
and
and
will
require
a
significant
effort
on
behalf
of
the
team.
A
Next,
up
supporting
multiple
backend
databases
in
support
of
decomposition,
so
the
the
database
team
have
successfully
deployed
a
decomposed
database
architecture
in
order
to
allow
the
backend
getlab
database
to
scale
better.
So
there
are
two
databases
now
Main
and
CI
and
Geo.
However,
Geo
is
currently
built
to
work
with
a
single
backend
database
in
order
to
support
the
future
state
of
GitHub
deployments.
A
Geo
needs
to
support
the
decomposed
two
database
model.
A
I
should
know
that
gitlab.com
is
already
operational
with
the
decomposed
database
architecture
and
in
the
first
phase
we
will
support
two
databases
on
this
on
a
single
postgres
instance.
In
future,
we
may
consider
supporting
two
databases
on
separate
postgres
instances,
but
for
now
we
will
focus
on
the
single
postgres
instance.
A
Next
up
we
want
to
deprecate
node
in
favor
of
sites.
This
is
a
just
an
alignment
on
terminology
that
that
we've
we've
undertaken
in
order
to
separate
and
distinguish
between
nodes
and
and
sites
with
the
within
the
context
of
Geo.
So
now
the
term
node
denoting
denotes
a
single
server
within
a
geo-deployment
and
and
a
site
now
denotes
a
collection
of
one
or
more
nodes
running
a
single
GitHub
application.
A
In
in
this
Milestone,
we
want
to
deprecate
Geo
node
name
in
favor
of
geosite
name
in
the
gitlab
RB
to
align
terminology
and
and
also
change
the
endpoint
name
from
Geo
node
Studio
sites
for
for
the
API,
and
there
are
a
number
of
ux
initiatives
and
and
some
some
bugs
that
that
we
will,
we
will
be
looking
to
address
in
this
in
this
Milestone
as
as
well
with
that,
we
conclude
the
15.8
outlook
for
fujio
and
I,
look
forward
to
seeing
you
next
time.
Thank
you.