Geo 15.6 outlook

This is the current outlook for the 15.6 milestone. The Geo team schedules issues and works in a continuous Kanban manner, while still aligning with milestones. See our process page for more detail.

Last Updated: 21 October 2022

Geo: Move existing data types into the Self Service Framework

Who: Douglas, Javiera, Zack

Geo's Self Service Framework significantly simplifies Geo's codebase and ensures that all data types are replicated and verified. It also empowers other developers to contribute new data types. We've already moved over most data types but a few are still implemented using our legacy system. The remaining data types are

In %15.4 and the following milestones we should focus on finishing the migration of these data types so that we can increase the velocity of future feature develop and reduce the complexity of Geo.

Geo: Move Projects and Wiki to Self-Service Framework priority1

Who: Douglas, Javiera, Zack

We will split project and wiki replication and verification logic.

Fix timeouts when pushing via SSH to secondary priority2

Who: Valery

Currently there is 60 second timeout on the proxied push request from the secondary to the primary. For large push requests this is insufficient time for the request to complete and times out.

The solution will likely require a architectural change to how we handle SSH proxy requests and will be a significant effort.

The ultimate goal will be to remove the restriction on size of proxied SSH push requests.

Compliance related tasks priority2

  • Document APIs - Document Geo REST APIs in OpenAPI V2

Dependency proxypriority3

Who: Mike

GitLab dedicated will deploy Geo as their DR solution. The dependency proxy caches upstream images. This reduces the number of pull requests that are made to Docker Hub as a result. Docker Hub limits the number of pull requests per month. If the dependency proxy was not replicated, the number of pull requests to Docker Hub can potentially be rapidly exhausted after a failover to secondary site as new images will need to be retrieved from Docker Hub.

Validate CI runner registration and cloning from secondary sites - when using Unified URL onlypriority3

Who: Nick

We believe CI runner registration and cloning from Geo secondary sites is supported. This is only possible when using Unified URL. In this milestone we will validate correct operation under all use cases with the goal releasing this as a fully supported feature of Geo.

Deprecate node in favor of site priority3

We've revised most of the terminology in our documentation to align to the updated glossary of Geo terms from node to site to reflect. The term node now denoting a single server and site being a collection one or more nodes running a single GitLab application. In this milestone we want update the labels for values in the gitlab.rb file and API endpoints to the updated terms.

UX Research and Improvements

Bugs

Edited by Sampath Ranasinghe