You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/24 19:07:04 UTC

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

    [ https://issues.apache.org/jira/browse/TC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023464#comment-16023464 ] 

ASF GitHub Bot commented on TC-200:
-----------------------------------

GitHub user dneuman64 opened a pull request:

    https://github.com/apache/incubator-trafficcontrol/pull/610

    [TC-200] The CCR DNS TTL field is now visible and editable in the UI

    This fixes [TC-200](https://issues.apache.org/jira/browse/TC-200)

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dneuman64/incubator-trafficcontrol tc-200

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafficcontrol/pull/610.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #610
    
----
commit 9c2f5a9070050c422ccf5b097eda7ec198441f4b
Author: David Neuman <da...@gmail.com>
Date:   2017-05-24T19:05:38Z

    The CCR DNS TTL field is now visible and editable in the UI

----


> 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.1.0
>            Reporter: Jeff Elsloo
>            Assignee: David Neuman
>            Priority: Minor
>
> 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)