[GitHub] [trafficcontrol] ocket8888 commented on issue #1565: Configuration - Automate dscp setting based on rules

[GitBox <gi...@apache.org>]

ocket8888 commented on issue #1565:
URL: https://github.com/apache/trafficcontrol/issues/1565#issuecomment-870741103


   > _"... based on rules."_
   
   is a little vague. Here are my ideas:
   
   This could be implemented by adding a property to Tenants that defines their DSCP, with `null` representing the ability to choose your own. Tenants cannot be allowed to have permissions to edit their own DSCP, so we have as I see it two options for the permission to edit DSCP.
   
   * The parent of a Tenant can edit its DSCP value. As a special case, the root tenant (being its own parent) can edit its own DSCP. The problem with this is that it forces you to use a "flat" Tenant structure. For example, if I offer tenancy to company A which has divisions B and C, then I might make a Tenant structure like root -> A -> (B & C), however this means that users in A can change their company's DSCP values for B and C, so I'm forced to either remember to never put a user in A, or do something like root -> (A_B & A_C) which defeats the purpose of the nestable tenants in the first place.
   * Under the User Permissions described by #5848 a new Permission could be added when editing Tenants (e.g. "tenant-dscp-change") that would allow changing a DSCP. The problem with this is it conflates Tenancy with user-based Permissions, which could make it hard to keep the concepts straight. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org