Stable Counterpart/Resource for Tenant Cells Cluster-Wide Sequences
Request
What kind of support are you looking for?
-
Feature Group Stable Counterpart -
Dedicated team member/resource -
Advice on structure/performance/ect
What team?
- Handbook: https://handbook.gitlab.com/handbook/engineering/infrastructure/core-platform/data_stores/tenant-scale/
- Slack Channel: #g_tenant-scale
- Engineering Manager: @arturoherrero
- Label: grouptenant scale
Describe the feature or ongoing work that needs assistance
As a part of Cells 1.0, the team needs to establish "Cluster wide unique identifiers". This work is likely database intensive. Epic Here - gitlab-org&11006 (closed)
Also documented in this blueprint.
Per @tkuah below: I think Tenant Scale has sufficient experience with Rails, GDK, self-managed / charts. What we need support with is probably around:
- Database / PostgreSQL specifics
- Distributed system pitfalls
- Production specifics
Expectations for participating member(s) of the database group
Team member(s) will collaborate directly with member(s) of tenant cells group on developing the architecture for this feature.
groupdatabase member will:
- Be dedicated to this effort and not focused on other efforts except:
- groupdatabase member will continue to perform database reviews
- groupdatabase member will occiasionally participate in the database team triage rotation
- groupdatabase member will continue to respond to requests for help and support in pressing scenarios
- In the case of a pressing scalability issue, the groupdatabase member may be redirected to that effort.
- Report a status on this architecture on a weekly basis in a comment on the epic
- Have regular discussions and pairing time with a member of grouptenant scale to discuss the architecture design and considerations and trade offs.
- Produce an architecture document/epic in collaboration with a member of grouptenant scale
grouptenant scale member(s) will:
- Work on any POC we need to do resolve architectural questions
- Implement the final solution
Designated Group members:
- groupdatabase: @praba.m7n
- groupdatabase: @dfrazao-gitlab
- grouptenant scale: @OmarQunsulGitlab
- grouptenant scale: @rutgerwessels
Exit Criteria
What goal do we want to meet in order for this to be complete?
- Update Cells blueprint with the architectural changes
- Create, refine, and estimate all the necessary issues under Cells 1.0 - Data access layer: Cluster-unique i... (gitlab-org&11006 - closed)
- Update Google Sheet schedule accordingly
- Implement the solution
What date do we expect this to be done by?
- Due date to clarify the high-level work needed and estimation is March 01, 2024
- Blueprint update, mid-end April
- Implement the solution, before mid 2024
Checklist
Requesting Team
-
The issue has a descriptive title -
There are detailed answers to the questions above -
The issue is assigned to the database team manager -
If this is urgent, reach out to the team manager in slack
Database Team
-
There is enough information to prioritize the request -
The request has been assigned to a member of the team -
The priority of the request has been agreed by the stakeholders and author
Edited by Alex Ives