lablup / lablup/backend.ai

Migrate Resource Group (Scaling Group) scope ownership data to the Virtual Scope model

Open
#12,479 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
670
Forks
183
Avg merge
15h 13m
Merged PRs (30d)
368

Description

Migrate existing Resource Group (Scaling Group) scope ownership rows in association_scopes_entities into the Virtual Scope chain: backfill virtual_scopes rows for existing Resource Group (Scaling Group) owners, a self scope_binding per owner VS, scope_bindings for existing scope->Resource Group (Scaling Group) links, and entity_memberships for existing Resource Group (Scaling Group)->child ownership. Verify no ownership/permission regressions after migration.

[Aligned to BEP-1062 (#12842): correct table names are virtual_scopes / scope_bindings / entity_memberships (previously scope_virtual / virtual_entity, which do not exist in code). Resolution is non-recursive; ownership resolves via the self scope_binding.]

JIRA Issue: BA-6665

Contributor guide

Open the contributing guide

Research direction

Start by tracing the existing association_scopes_entities ownership data and the schema or migration definitions for virtual_scopes, scope_bindings, and entity_memberships. Verify that the backfill creates the specified self and link bindings and child memberships, then check that ownership and permissions remain unchanged after migration.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, databases
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.