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.

Sign up for GitHub

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

Jump to bottom

Remove the "ALL" cdn #3355

Open
mitchell852 opened this issue Feb 20, 2019 · 0 comments
Open

Remove the "ALL" cdn #3355

mitchell852 opened this issue Feb 20, 2019 · 0 comments
Labels
help wanted high difficulty the estimated level of effort to resolve this issue is high low impact affects only a small portion of a CDN, and cannot itself break one tech debt rework due to choosing easy/limited solution Traffic Ops related to Traffic Ops

Comments

@mitchell852
Copy link
Member

Because our server table is overloaded with caches AND infrastructure servers (TP, TO, TM, etc) and the cdn attribute is required for all "servers" the ALL cdn was introduced to help satisfy this requirement for servers where a cdn doesn't make sense (infrastructure servers).

imo either the server table should be broken into 2 tables - caches and servers? or maybe it's as simple as making cdn nullable for certain server types? not sure of the solution.
@mitchell852 mitchell852 added Traffic Ops related to Traffic Ops tech debt rework due to choosing easy/limited solution labels Feb 20, 2019
@mitchell852 mitchell852 added high difficulty the estimated level of effort to resolve this issue is high low impact affects only a small portion of a CDN, and cannot itself break one labels Nov 30, 2021
@mitchell852 mitchell852 mentioned this issue Dec 17, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted high difficulty the estimated level of effort to resolve this issue is high low impact affects only a small portion of a CDN, and cannot itself break one tech debt rework due to choosing easy/limited solution Traffic Ops related to Traffic Ops
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mitchell852 @zrhoffman