►
From YouTube: Gitlab 16.5 Kickoff - Enablement:Geo
Description
Gitlab 16.5 Kickoff - Geo Group
Planning issue: https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/5094
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
the
16.5
outlook
for
group
Geo.
My
name
is
sampat
Rana
singha
I'm,
the
product
manager
for
the
group.
Let's
start
with
get
lifestyle
info
get
lap,
Silo
mode
suppresses
outbound
Communications
when
enabled
on
a
gitlab
instance,
outbound
Communications
such
as
emails
and
Integrations
into
things
like
Slack.
A
You
restore
a
backup
copy
onto
a
new
event,
instance,
and
and
put
that
instance,
into
silent
mode
and
start
start
your
testing
without
actually
generating
traffic
towards
towards
your
users.
This
has
been
a
cross-stage
effort
with
a
number
of
number
of
groups
helping
for
us
helping
us
to
get
get
this
completed.
We're
we're
nearing
the
end
of
of
the
journey
here,
which
we've
been
on
for
a
couple
of
Milestones.
So
we're
we're
finishing
off
the
UI
elements
in
in
16-5
Milestone
with
the
Outlook
to
GA.
A
Next
up
is
the
backup
enhancements
backup.
We
have
a
number
of
backup
tools
from
from
gitlab
for
their
targeting
various
different
environments.
A
Each
Backup
Tool
has
a
different
CLI
different
different
capabilities
as
as
well
so
one
of
the
improvements
we
are
looking
to
make
in
this
Milestone
is
to
unify
the
backups
in
in
into
a
single
CLI,
so,
whether
that
be
a
Linux
package
environment,
a
cloud
native,
hybrid
environment
or
or
any
any
one
of
our
reference
architectures,
we
will
have
a
single
single
CLI
that
supports
this
it'll,
improve
the
experience
overall
experience
for
our
customers
and
and
ultimate
streamline,
also
streamline
that
experience
and
through
through
a
consistent,
consistent
interface.
A
We'll
also
take
a
look
at
improving
the
the
scalability
of
backups
by
leveraging
modern
multi-core
processes,
specifically
targeting
the
compression
element
of
the
backup
we
will.
We
will
leverage
multi
parallel
compression
algorithm
to
accelerate
the
compression
component
of
backups,
allowing
the
backups
to
complete
faster.
A
Next
up
is
gain
Runner
acceleration,
and
today
we
we
already
support
accelerating
remote
users,
so
Geo
secondary
sites
will
serve
a
read
request
from
remote
users
by
by
using
using
the
data
that's
available
locally
on
the
site.
However,
we
don't
accelerate
CI
Runners.
Why
would
what
does
accelerating
CA
Runners
provide
in
terms
of
like
enhancements
to
to
your
setup?
It
allows
the
load
from
CI
Runners
to
be
distributed.
The
load
on
the
primary
can
mean
can
now
be
distributed
across
multiple
secondary
sites.
A
A
We've
been
working
on
this
feature
for
a
couple
of
Milestones
again
we're
we're
getting
close
to
close
to
getting
this
across
the
line
and
and
and
we'll
continue
to
work
on
this.
In
this
current,
milestone,
supporting
sync
all
and
verify
all
bulk
actions
for
components
is,
is
something
that
we
already
had
supported
for
projects
with
this
in
this
Milestone
we're
going
to
make
that
available
for
all
components
through
the
self-service
framework
by
essentially
leveling
up
the
self-service
framework
making
this
action
available
to
all
all
the
components.
A
This
helps
users
kick
off
these
bulk
actions.
For
example,
we
assume
you
made
a
large
configuration
change,
and
now
you
want
to
reset
your
synchronization
or
replication,
or
you
want
to
re-verify
all
of
the
components
that
all
of
the
data
that
has
been
replicated
to
that
secondary
site.
You
can
now
do
this
through
through
the
UI.
Instead
of
having
to
delve
into
the
rails,
console.
A
A
Next,
we
proxy
and
git
Fetch
and
clone
over
SSH
via
gitlab
shell.
In
a
previous
recent
Milestone,
we
had
changed
the
call
Flow
for
proxy
and
get
a
push
request
to
go
over
the
gitlab
shell.
We've
seen
improvements
in
in
performance
through
that,
but
it's
also
helped
us
in
remove
a
number
of
limitations.
A
So,
in
order
to
consolidate
behind
the
gitlab
shell
for
call
Flow,
we
are
also
moving
to
get
fetch
and
clone
operations
to
go
over
getlab
gitlab
shell,
and
so
this
is
the
effort
to
have
both
pull
and
push
operations.
Proxy
operations
go
through
the
the
gitlab
shell.
A
And
then,
last
but
not
least,
we'll
be
undertaking
a
number
of
documentation
improvements
during
this
Milestone.
This
will
be
a
collective
effort
from
amongst
the
the
Geo
team.
The
Geo
documentation
has
a
needs,
needs
some
cleanup
and
updating,
and
there
are
several
specific
areas
we
want
to
add
and
update
instructions
for
multi-node
scenarios
in
particular,
so
we'll
be
tackling
these
as
a
group
and
looking
to
update
the
the
documentation
over
the
next
next
couple
of
milestones.
A
That
concludes
the
16.5
outlook
for
group.
Geo
I
look
forward
to
catching
you
next
time.
Thank
you
very
much.