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

t3c log messages, variable names and flags assume only ATS is used #7723

Open
AbdelrahmanElawady opened this issue Aug 16, 2023 · 0 comments
Labels
cache-config Cache config generation improvement The functionality exists but it could be improved in some way. 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 Varnish related to Varnish

Comments

@AbdelrahmanElawady
Copy link
Contributor

This Improvement request (usability, performance, tech debt, etc.) affects these Traffic Control components:

  • Traffic Control Cache Config (t3c, formerly ORT)

Current behavior:

t3c variables like tsConfigDir, flags like trafficserver-home and log messages are based on ATS being the cache server used. However, this is not the case any more with Varnish support.

New behavior:

A more generic names like cacheConfigDir or cache-home with logs using trafficserver or varnish based on what cache server type is using t3c would be more suitable.

@AbdelrahmanElawady AbdelrahmanElawady added the improvement The functionality exists but it could be improved in some way. label Aug 16, 2023
@AbdelrahmanElawady AbdelrahmanElawady added low impact affects only a small portion of a CDN, and cannot itself break one cache-config Cache config generation low difficulty the estimated level of effort to resolve this issue is low Varnish related to Varnish labels Aug 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cache-config Cache config generation improvement The functionality exists but it could be improved in some way. 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 Varnish related to Varnish
Projects
Status: To do
Development

No branches or pull requests

1 participant