Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

global: move away from "experiment" paradigm to general "access scope" #14

Open
lukasheinrich opened this issue Feb 14, 2017 · 1 comment
Labels
Projects

Comments

@lukasheinrich
Copy link
Member

This wi;l need some discussion, but maybe we can seed it here. Right now the notion of an "experiment" (as in ATLAS, CMS, etc..) is used in a lot of the code. In order to be generic probably it's best to define a number of "access scopes" and use that name across the code. If we want REANA e.g. be installed on-premises elsewhere, a "scope" could be a specific professor's lab, where various labs use the same reana instance but have their own secrets, etc.

@tiborsimko tiborsimko added this to the Initial-Release milestone May 11, 2017
@tiborsimko
Copy link
Member

👍 Let's muse live about scope, tenant, etc.

@diegodelemos diegodelemos modified the milestones: Initial-Release, Client-server sprint, Client-Server May 24, 2017
@diegodelemos diegodelemos added this to To triage in Triage Oct 6, 2019
@diegodelemos diegodelemos removed this from the Someday milestone Oct 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Triage
To triage
Development

No branches or pull requests

3 participants