[jira] [Closed] (TC-200) Unable to modify Traffic Router TTLs on Delivery Services

["David Neuman (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Neuman closed TC-200.
---------------------------
    Resolution: Fixed

> Unable to modify Traffic Router TTLs on Delivery Services
> ---------------------------------------------------------
>
>                 Key: TC-200
>                 URL: https://issues.apache.org/jira/browse/TC-200
>             Project: Traffic Control
>          Issue Type: Bug
>          Components: Traffic Ops
>    Affects Versions: 2.0.0, 2.1.0
>            Reporter: Jeff Elsloo
>            Assignee: David Neuman
>            Priority: Minor
>             Fix For: 2.0.0, 2.1.0
>
>
> It appears that we have no means to modify the {{ccr_dns_ttl}} field on delivery services. We have fields that are not being shown and are defaulted to 30 and 3600 seconds for DNS and HTTP, respectively. We need to be able to edit this field primarily because we need the control, but secondarily because if the type changes the value might not.
> For example, in the DS "add" template (note lack of {{.show(speed)}}):
> {code}
>         if (type_selected.match(/^HTTP/)) {
>             $("#regexp_selector :nth-child(3)").removeAttr('disabled');
>             $("#regexp_selector :nth-child(4)").removeAttr('disabled');
>             $('#ccr_dns_ttl').val(3600);
>             $('#protocoli_row').show(speed);
>             $('#dscp_row').show(speed);
> ...
>         else if (type_selected.match(/^DNS/)) {
>             $("#regexp_selector :nth-child(3)").attr('disabled','disabled');
>             $("#regexp_selector :nth-child(4)").attr('disabled','disabled');
>             $('#ccr_dns_ttl').val(30);
>             $('#protocoli_row').show(speed);
>             $('#dscp_row').show(speed);
> {code}
> From TC-254 (duplicate):
> There is currently no way to edit the ccr_dns_ttl field on a delivery service. This needs to be fixed, and additionally, we should scour the interface to ensure that all fields are editable, for all delivery service types. This includes not only DNS, but all DNS types and all HTTP types.
> From the dev list:
> We might want to use the values that appear in config->ttls in the CRConfig as the defaults, which are "CCR" profile parameters. If they are not present, suitable defaults should be used for the delivery service. Currently, as shown above, the values are hardcoded in a template.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)