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

[TC-184] Tenant Hierarchy Creation #931

Closed
limited opened this issue Aug 29, 2017 · 2 comments
Closed

[TC-184] Tenant Hierarchy Creation #931

limited opened this issue Aug 29, 2017 · 2 comments
Labels
high impact impacts the basic function, deployment, or operation of a CDN new feature A new feature, capability or behavior Traffic Ops related to Traffic Ops

Comments

@limited
Copy link
Contributor

limited commented Aug 29, 2017

Design under discussion here: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68715910

The requirements below are seed requirements and final design guidance should defer to the evolving wiki page discussion referenced above.

Overview
The goal of this system is to create a hierarchical tenancy system which is very simple to understand and administer and is highly expandable so that large organizations with many subsidiaries have the flexibility to create child-tenants to their liking.

General Seed Requirements
1. Provide a structure to create a hierarchy of Tenants where each Tenant has a single parent-Tenant and can have multiple child-Tenants
2. Provide the ability to group multiple Delivery Services, Users, and child- Tenants under each Tenant
3. Provide the ability to create at least 10 child-Tenant layers within the system
4. Make it easy to assign a User to a single Tenant so that they inherit their permissions to all child-Tenants and Delivery Services.
5. Adding child-Tenants or Delivery Services anywhere in an existing tenant hierarchy does not require re-assigning users. Users inherit pre-defined permissions to new tenants and services added below their assigned layer in the tenancy tree.
6. Allow Users to be assigned multiple Tenants, each with different Roles. While a user would inherit their access to all services and child Tenants below them, they may need more restrictive access further up the Tenant hierarchy or they may want different access to another branch of the tenant tree.

Author: Ryan Durfey
JIRA Link: https://issues.apache.org/jira/browse/TC-184

@limited limited added high impact impacts the basic function, deployment, or operation of a CDN New Feature Traffic Ops related to Traffic Ops labels Aug 29, 2017
@ryandurfey
Copy link
Contributor

@mitchell852 This can be closed.

@rob05c rob05c added new feature A new feature, capability or behavior and removed new feature labels Jan 26, 2018
@ashish-timilsina
Copy link
Contributor

@ryandurfey
@ashish-timilsina
@mitchell852 per Ryan's comment, you can close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high impact impacts the basic function, deployment, or operation of a CDN new feature A new feature, capability or behavior Traffic Ops related to Traffic Ops
Projects
None yet
Development

No branches or pull requests

5 participants