►
From YouTube: Gitlab 15.9 Kickoff - Enablement:Geo
Description
Gitlab 15.9 Kickoff - Geo Group
Planning issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5055
Geo group past kickoff Videos: https://www.youtube.com/playlist?list=PL05JrBw4t0KoY_6FXXVgj7wPE9ZDS4cOw
Presentation by: Sampath Ranasinghe, Sr. Product Manager, Geo
A
Hello,
my
name
is
sambadranasinger
I'm,
the
product
manager
for
group
Geo
and
today,
we'll
take
a
look
at
the
15.9
outlook
for
the
group.
Let's
take
a
look
at
moving
existing
data
types
into
the
self-service
framework.
This
has
been
a
long-running
task
for
us
to
move
the
existing
Legacy
data
types
into
our
new
self-service
framework.
We
had
two
outstanding
data
types
two
to
move
across,
namely
projects
and
wikis
and
design
repositories.
A
We've
made
good
progress
in
the
last
Milestone
on
on
both
of
these
items
and
we're
looking
forward
to
wrapping
this
up
in
this
milestone.
A
As
part
of
the
ongoing
work
here,
we
will
see
additional
capabilities
arriving
for
the
other
data
types
that
are
in
within
the
self-service
framework,
as
we
enhance
a
self-service
framework
to
bring
in
the
capabilities
that
were
available
for
projects
and
wikis.
Some
of
the
capabilities
include
being
able
to
search
by
a
keyword
through
the
through
the
objects.
A
So
that's
moving
projects
and
wikis
and
design
repositories
to
the
self-service
framework.
A
With
that
effort,
we
will
be
concluding
the
the
migration
to
the
self-service
framework
and
we
will
have
a
hundred
percent
of
the
geodata
managed
by
the
self-service
framework.
A
Next
is
the
fixing
the
timeouts
when
pushing
via
SSH
to
to
a
secondary
site.
Currently
there
is
a
60
second
timeout
related
to
this
operation,
and
this
affects
customers
with
large
push
requests
that
are
accelerating
their
remote
users
using
Geo
like
this
well,
this
likely
requires
some
architectural
changes
and
a
fair
amount
of
work
on
our
on
our
side,
with
respect
to
Geo.
A
So
we're
going
to
start
off
with
a
proof
of
concept
that
will
proxy
the
SSH
connection
to
to
the
primary
site
and
we'll
we'll
evaluate
the
success
of
this
improved
concept,
and
we
will
decide
on
what
next
steps
are
based
on
the
based
on
the
outcomes.
A
We
also
have
migrating
go
away
from
using
rename
repository
RPC.
This
is
a
RPC
that
is
part
of
the
the
gitly
apis,
and
the
calling
of
this
RPC
has
negative
effects
on
on
the
gitly
code
itself,
gitly
side
and
therefore
we
are
looking
to
move
Geo
away
from
this.
Rpc
Geo
performs
the
rename
repository
after
the
initial
clone
of
the
repository
when
the
secondary
site
begins
replication.
A
This
should
help
with
the
performance
impacts
that
are
related
to
renaming.
Next
up
is
deprecating
node
in
favor
of
site.
Again
this
is
a
lower
priority
item,
but
we
do
want
to
get
out
of
the
the
the
switch
or
complete
conclude
the
switch
from
a
node
to
to
site.
In
this
context,
the
term
node
now
denotes
a
single
server
and
a
site
being
a
collection
of
one
or
more
nodes
running
a
single
gitlab
application.
A
We
have
a
couple
of
configurations
and
in
apis
that
that
still
carry
the
the
node
connotation,
we
will
be
looking
to
update
those
as
part
of
this
milestone
and
then,
finally,
we
are
looking
to
support
a
multiple
database
as
the
databases
in
support
of
of
decomposition.
The
database
team
or
the
scalability
team
at
gitlab
helped
a
split
the
day.
A
good
primary
database
into
into
two
separate
databases,
Main
and
CI
this
this
helped
improve
the
scalability
of
the
database
itself.
A
In
this
Milestone,
we
hope
to
be
working
on
are
supporting
multiple
databases.
Inside
of
a
single
postgres
instance,
we
will
be
making
progress
towards
this
this
this
end,
however,
we
are
awaiting
completion
of
some
some
work
related
to
PG
bouncer.
A
That
will
allow
us
to
test
a
multi-node
setup,
in
particular
we're
targeting
the
3K
reference
architecture
and
once
the
the
particular
issue
related
to
the
PG
bounces
included,
we
will
pick
up
the
the
testing
again
with
respect
to
multi-node
setups
and
then,
to
conclude,
we
have
a
number
of
bugs
and
some
miscellaneous
items
that
we
hope
to
work
on
as
well.
A
We
make
good
progress
on
squashing
a
number
of
bugs
in
the
in
the
previous
release
and
and
we
will
be
looking
to
do
the
same
in
this
release,
and
that
concludes
the
15.9
outlook
for
group,
Geo
and
I.
Look
forward
to
seeing
you
next
time.