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

Legacy Naming Conventions (Rascal, RIAK, CCR et. al.) #2564

Closed
ocket8888 opened this issue Jul 19, 2018 · 1 comment · Fixed by #7068
Closed

Legacy Naming Conventions (Rascal, RIAK, CCR et. al.) #2564

ocket8888 opened this issue Jul 19, 2018 · 1 comment · Fixed by #7068
Labels
low difficulty the estimated level of effort to resolve this issue is low low impact affects only a small portion of a CDN, and cannot itself break one new feature A new feature, capability or behavior tech debt rework due to choosing easy/limited solution Traffic Monitor related to Traffic Monitor Traffic Ops related to Traffic Ops Traffic Router related to Traffic Router Traffic Vault related to Traffic Vault

Comments

@ocket8888
Copy link
Contributor

It's super confusing that Traffic Monitor is referred to in hundreds of places as "Rascal", Traffic Vault as "RIAK" and Traffic Router as CCR. We should change those.

That would also entail removing legacy constraints related to those names, e.g. Traffic Monitor profiles currently must start with a "RASCAL" prefix for no good reason I've ever heard. Database tables and columns ought to be renamed as well (if applicable, I'm not sure), but that probably would make production upgrades much more complicated.
@mitchell852 mitchell852 added Traffic Router related to Traffic Router Traffic Monitor related to Traffic Monitor Traffic Ops API Traffic Vault related to Traffic Vault new feature A new feature, capability or behavior tech debt rework due to choosing easy/limited solution labels Jul 19, 2018
@mitchell852 mitchell852 added Traffic Ops related to Traffic Ops and removed Traffic Ops related to Traffic Ops Traffic Ops API (golang) labels Oct 17, 2018
This was referenced Dec 1, 2021
Merged
Merged
@ocket8888 ocket8888 added low difficulty the estimated level of effort to resolve this issue is low low impact affects only a small portion of a CDN, and cannot itself break one labels Dec 1, 2021
@mitchell852
Copy link
Member

"low effort" @ocket8888 ?

@rimashah25 rimashah25 mentioned this issue Oct 31, 2022
Merged
4 tasks
This was referenced Nov 14, 2022
Merged
Draft
@asf-ci asf-ci mentioned this issue Dec 1, 2022
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
low difficulty the estimated level of effort to resolve this issue is low low impact affects only a small portion of a CDN, and cannot itself break one new feature A new feature, capability or behavior tech debt rework due to choosing easy/limited solution Traffic Monitor related to Traffic Monitor Traffic Ops related to Traffic Ops Traffic Router related to Traffic Router Traffic Vault related to Traffic Vault
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Renamed rascal to tm/traffic_monitor rimashah25/trafficcontrol
2 participants
@mitchell852 @ocket8888