[
https://issues.apache.org/jira/browse/TC-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hank Beatty updated TC-298:
---------------------------
Fix Version/s: 2.2.0
2.1.0
> Health params.json updated with certain Profile names Github Issue #896
> -----------------------------------------------------------------------
>
> Key: TC-298
> URL: https://issues.apache.org/jira/browse/TC-298
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
> Affects Versions: 2.1.0, 2.0.0, 2.2.0
> Reporter: Dewayne Richardson
> Labels: heath_params.json, profile
> Fix For: 2.1.0, 2.2.0
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
