lablup / lablup/backend.ai

Migrate Domain scope ownership data to the Virtual Scope model

Open
#12,475 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
670
Forks
183
Avg merge
17h 7m
Merged PRs (30d)
358

Description

Migrate existing Domain scope ownership rows in association_scopes_entities into the Virtual Scope chain: backfill virtual_scopes rows for existing Domain owners, a self scope_binding per owner VS, scope_bindings for existing scope->Domain links, and entity_memberships for existing Domain->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-6662

Contributor guide

Open the contributing guide

Research direction

Start by locating the migration or data-access code for association_scopes_entities and the virtual_scopes, scope_bindings, and entity_memberships tables. Verify the backfilled rows, self scope_bindings, existing scope-to-Domain links, and Domain-to-child memberships, then check for ownership and permission regressions.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend-api-design, 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.