Server tags and routing hints
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Trace the API handling of the meta_bbblb-select parameter and the server-selection entry point used when creating meetings. Verify how tenant-based call parameter overrides reach that selection logic. Done means admins can assign tags, matching tags are preferred or enforced according to the trailing !, and missing or empty metadata selects untagged servers only.
Written by the indexing model from the issue text.
Description
Allow admins to tag servers with a short string (e.g. a location or special configuration like eu or large), and then allow front-ends to request new meetings on a specific type of server via metadata.
Let's mimic the Scalelite API for now:
- The meta parameter
meta_server-tagcan contain a semicolon-separated list of tags, and an optional!at the end. - If the meta parameter is missing or empty, the meeting is created on untagged servers only.
- If the value ends with
!, only servers matching one of the requested tags are considered for new meetings. - If the value does not end with
!, matching servers are preferred, but untagged servers are also considered if no matching server is available.
Examples:
meta_bbblb-select=(or missing): Start new meetings on untagged servers only.meta_bbblb-select=large;verylarge!: Start new meetings on servers tagged withlargeorverylargeonly.meta_bbblb-select=large;verylarge: Start new meetings on servers tagged withlargeorverylarge, and fall back on untagged servers if no matching servers are available.
This can be used in combination with tenant based call parameter overrides to route specific tenants to specific servers only.
- Dominant language
- Python
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from defnull/bbblb
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
feature PR welcome
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·