Geo 15.10 outlook
This is the current outlook for the 15.10 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: 17 February 2023
Move existing data types into the Self Service Framework
Who: Douglas, Javiera, Zack, Aakriti
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.10 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.
Move Projects and Wiki to Self-Service Framework priority1
Who: Douglas, Javiera, Zack
- Split project and wiki separate tables (Complete)
- Implement Git repo housekeeping in SSF for Project Wikis, Group Wikis and Snippets (Complete)
- Migrate projects replication/verification to use SSF - (In progress)
- Migrate wikis replication/verification to use SSF - (In progress)
- Revisiting and consolidate the existing UI functionality for Geo replication views
We hit a few snags on the way to completing this and had to revert some changes that were causing verification challenges for customers. We believe we are now past this and are making progress to completing this migration in this milestone.
Move design repositories to the Self-Service Framework priority1
Who: Aakriti
Migrate the last legacy data type, design repositories, to the self-service framework.
Fix timeouts when pushing via SSH to secondary priority2
Who: Mike
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.
- We will start with a POC proxying the SSH connection (Complete)
- Send authorization headers to Gitlab Shell to perform Git over HTTPS to Primary (In progress)
- Cleanup unused Git Proxy endpoints
External dependencies :
- Move HTTP to SSH conversion from Rails to Gitlab Shell
- Perform Git over HTTP requests as a custom action instead of Proxy requests
Verification of container registry priority3
Add verification of container registry. This is part of our effort to increase verification coverage of replicated data types.