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-298] Health params.json updated with certain Profile names Github Issue #896 #910

Open
limited opened this issue Aug 29, 2017 · 1 comment
Labels
medium impact impacts a significant portion of a CDN, or has the potential to do so new feature A new feature, capability or behavior tech debt rework due to choosing easy/limited solution Traffic Ops related to Traffic Ops

Comments

@limited
Copy link
Contributor

limited commented Aug 29, 2017

Create Profile names in the Traffic_OPs with names such as Edge and Mid for Edge and Mid cache profiles, these don't get updated in the heath_params.json on the Traffic monitor.

In the current implementation of traffic ops, there is no "type" for a profile. When generating the health-params.json for traffic monitor, ops do not know which profile is for edge or middle or router, etc. So in traffic ops code, it use the convention that:
profile starting with "RASCAL" is a traffic monitor profile
profile starting with "CCR" is a traffic router profile
profile starting with "EDGE" is an edge server profile
profile starting with "MID" is a middle server profile

It is better to add a type for each profile, or make a restriction for the profile name.

Author: Dewayne Richardson
JIRA Link: https://issues.apache.org/jira/browse/TC-298
Found Version: 2.1.0

@limited limited added this to the 2.1.0 milestone Aug 29, 2017
@limited limited added Improvement high impact impacts the basic function, deployment, or operation of a CDN Traffic Ops related to Traffic Ops labels Aug 29, 2017
@hbeatty hbeatty modified the milestones: 2.2.0, 2.1.0 Aug 30, 2017
@rob05c rob05c added new feature A new feature, capability or behavior and removed improvement labels Jan 26, 2018
@rob05c rob05c modified the milestones: 2.2.0, 2.3 Jan 29, 2018
@mitchell852
Copy link
Member

profiles have types now but that doesn't address the issue of keying off of profile type rather than profile name convention. I think this is tech debt.

@mitchell852 mitchell852 added the tech debt rework due to choosing easy/limited solution label Oct 18, 2018
@mitchell852 mitchell852 added medium impact impacts a significant portion of a CDN, or has the potential to do so and removed high impact impacts the basic function, deployment, or operation of a CDN labels Aug 19, 2019
@dneuman64 dneuman64 removed this from the 2.3 milestone Apr 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
medium impact impacts a significant portion of a CDN, or has the potential to do so new feature A new feature, capability or behavior tech debt rework due to choosing easy/limited solution Traffic Ops related to Traffic Ops
Projects
None yet
Development

No branches or pull requests

5 participants