Adds cells.sequence_ranges
What does this merge request do and why?
This is a dependency for Updates sequence range validation (gitlab-org/cells/topology-service!188 - merged).
It includes cells.sequence_ranges and updates the range to be 100 billion IDs, to be inline with the changes in TS.
Also cells.sequence_range is left in-place to not break the current TS, it will be removed once gitlab-org/cells/topology-service!188 (merged) gets merged.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
-
Be in the GDK root directory.
-
cd gitlab-topology-serviceand git checkout tosequence-range-validation-v1branch (to have changes from gitlab-org/cells/topology-service!188 (merged)). -
Make sure cells is enabled in the gdk and has non-zero cells.instance_count.
-
gdk reconfigure -
gdk start -
gdk cells up -
gitlab-topology-service should be up and running
2025-04-22_22:38:56.89735 gitlab-topology-service : gRPC Insecure server running at port [::]:9095 2025-04-22_22:38:56.89756 gitlab-topology-service : REST Insecure server running at port [::]:9096 -
Go to gitlab-topology-service repo, run
grpcurl -proto proto/claim_service.proto \ -plaintext \ -d '{}' \ 127.0.0.1:9095 \ gitlab.cells.topology_service.ClaimService/GetCellssequence_rangesshould listed out{ "cells": [ { "id": "1", "address": "gdk.test:3333", "sessionPrefix": "cell-1", "sequenceRange": { "minval": "1", "maxval": "100000000000" }, "sequenceRanges": [ { "minval": "1", "maxval": "100000000000" } ] }, { "id": "2", "address": "gdk.test:12002", "sessionPrefix": "cell-2", "sequenceRange": { "minval": "100000000001", "maxval": "200000000000" }, "sequenceRanges": [ { "minval": "100000000001", "maxval": "200000000000" } ] }, { "id": "3", "address": "gdk.test:12152", "sessionPrefix": "cell-3", "sequenceRange": { "minval": "200000000001", "maxval": "300000000000" }, "sequenceRanges": [ { "minval": "200000000001", "maxval": "300000000000" } ] } ] }
Impacted categories
The following categories relate to this merge request:
-
gdk-reliability - e.g. When a GDK action fails to complete. -
gdk-usability - e.g. Improvements or suggestions around how the GDK functions. -
gdk-performance - e.g. When a GDK action is slow or times out.
Merge request checklist
-
This MR references an issue describing the change. -
This change is backward compatible. If not, please include steps to communicate to our users. -
Tests added for new functionality. If not, please raise an issue to follow-up. -
Documentation added/updated, if needed. -
Announcement added, if change is notable. -
gdk doctortest added, if needed.
Closes #2578 (closed)