[jira] [Commented] (TC-51) build creates rpm with more than one `.el6` in rpm file name
[ https://issues.apache.org/jira/browse/TC-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705543#comment-15705543 ] ASF GitHub Bot commented on TC-51: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/106 > build creates rpm with more than one `.el6` in rpm file name > > > Key: TC-51 > URL: https://issues.apache.org/jira/browse/TC-51 > Project: Traffic Control > Issue Type: Bug > Components: all >Affects Versions: 1.8.0, 1.9.0 > Environment: rhel 6 build environment >Reporter: Dan Kirkwood >Assignee: Dan Kirkwood > Labels: easyfix > Fix For: 1.8.0 > > Original Estimate: 1h > Remaining Estimate: 1h > > did a new build in rhel 6, and following rpm names appeared in ./dist > directory (note .el6.el6. in all file names) : > traffic_monitor-1.8.0-4563.a2e71259.el6.x86_64.rpm > traffic_ops-1.8.0-4563.a2e71259.el6.el6.src.rpm > traffic_ops-1.8.0-4563.a2e71259.el6.el6.x86_64.rpm > traffic_ops_ort-1.8.0-4563.a2e71259.el6.el6.src.rpm > traffic_ops_ort-1.8.0-4563.a2e71259.el6.el6.x86_64.rpm > traffic_portal-1.8.0-4563.a2e71259.el6.el6.src.rpm > traffic_portal-1.8.0-4563.a2e71259.el6.el6.x86_64.rpm > traffic_router-1.8.0-4563.a2e71259.el6.el6.el6.x86_64.rpm > traffic_stats-1.8.0-4563.a2e71259.el6.el6.src.rpm > traffic_stats-1.8.0-4563.a2e71259.el6.el6.x86_64.rpm -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-56) traffic_monitor build from top fails to update version
Dan Kirkwood created TC-56: -- Summary: traffic_monitor build from top fails to update version Key: TC-56 URL: https://issues.apache.org/jira/browse/TC-56 Project: Traffic Control Issue Type: Bug Components: Traffic Monitor Affects Versions: 1.8.0 Environment: build from top-level of incubator-trafficcontrol Reporter: Dan Kirkwood Assignee: Dan Kirkwood Priority: Trivial Fix For: 1.8.0 `$ ./build/build.sh traffic_monitor` [ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.2:set (default-cli): Goal requires a project to execute but there is no POM in this directory (/vagrant/dangogh). Please verify you invoked Maven from the correct directory. -> [Help 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-56) traffic_monitor build from top fails to update version
[ https://issues.apache.org/jira/browse/TC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705797#comment-15705797 ] ASF GitHub Bot commented on TC-56: -- GitHub user dangogh opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/109 [TC-56] cd to traffic_monitor prior to mvn call mvn command to set version for traffic_monitor must run from traffic_monitor directory. That doesn't happen if you're running from the top-level directory.. This change explicitly cd's to correct directory to run the mvn command. You can merge this pull request into a Git repository by running: $ git pull https://github.com/dangogh/incubator-trafficcontrol tm-build Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/109.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 #109 commit 6a3f52f56608b0796d20ec38d78594420b06e125 Author: Dan Kirkwood Date: 2016-11-29T16:18:55Z cd to traffic_monitor prior to mvn call > traffic_monitor build from top fails to update version > -- > > Key: TC-56 > URL: https://issues.apache.org/jira/browse/TC-56 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Monitor >Affects Versions: 1.8.0 > Environment: build from top-level of incubator-trafficcontrol >Reporter: Dan Kirkwood >Assignee: Dan Kirkwood >Priority: Trivial > Fix For: 1.8.0 > > > `$ ./build/build.sh traffic_monitor` > [ERROR] Failed to execute goal > org.codehaus.mojo:versions-maven-plugin:2.2:set (default-cli): Goal requires > a project to execute but there is no POM in this directory > (/vagrant/dangogh). Please verify you invoked Maven from the correct > directory. -> [Help 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-57) Build process not changing directory and reading configuration file
Steve Malenfant created TC-57: - Summary: Build process not changing directory and reading configuration file Key: TC-57 URL: https://issues.apache.org/jira/browse/TC-57 Project: Traffic Control Issue Type: Bug Components: Traffic Monitor Affects Versions: 1.9.0 Environment: Vagrant + Centos 6.8 or Centos 7.2 Reporter: Steve Malenfant Priority: Minor Followed direction posted on the Traffic Monitor Developer’s Guide but I couldn't seem to get Traffic Monitor test to work. Using ~/build/build.sh fails to build Traffic Monitor Using ~/build/build.sh traffic_monitor works but tests aren't working Using cd traffic_monitor; ./build/build/build_rpm.sh seems to compile maven but fails to find valid configuration file I don't think I've successfully been able to run Traffic Monitor tests in the past and my environment might be incorrect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-55) Multi Delivery Services With Same Domain Name and Different Path Prefixes
[ https://issues.apache.org/jira/browse/TC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705828#comment-15705828 ] Dewayne Richardson commented on TC-55: -- This feature seems to be in high demand, but we need to facilitate some discussion regarding the problem and the proposed solution. Once we have consensus about the design, typically the implementation is then started, which will result in a pull request. Once the PR has been reviewed and changed (if needed), then we will accept the PR. Please send future requirement requests and your design documents to the d...@trafficcontrol.incubator.apache.org mailing list so the discussion can begin. Thanks, -Dewayne > Multi Delivery Services With Same Domain Name and Different Path Prefixes > - > > Key: TC-55 > URL: https://issues.apache.org/jira/browse/TC-55 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops, Traffic Ops API >Affects Versions: 1.7.0 >Reporter: Jifeng Yang > > Enhance TC to support: > Multi Delivery Services With Same Domain Name and Different Path Prefixes > Details please ref the link: > https://docs.google.com/document/d/19-TZ6ODla_vdiYqZajbpRiOpLvpbJxil1SvIm44zb-0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TC-56) traffic_monitor build from top fails to update version
[ https://issues.apache.org/jira/browse/TC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Kirkwood updated TC-56: --- Fix Version/s: (was: 1.8.0) 1.9.0 > traffic_monitor build from top fails to update version > -- > > Key: TC-56 > URL: https://issues.apache.org/jira/browse/TC-56 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Monitor >Affects Versions: 1.8.0 > Environment: build from top-level of incubator-trafficcontrol >Reporter: Dan Kirkwood >Assignee: Dan Kirkwood >Priority: Trivial > Fix For: 1.9.0 > > > `$ ./build/build.sh traffic_monitor` > [ERROR] Failed to execute goal > org.codehaus.mojo:versions-maven-plugin:2.2:set (default-cli): Goal requires > a project to execute but there is no POM in this directory > (/vagrant/dangogh). Please verify you invoked Maven from the correct > directory. -> [Help 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-56) traffic_monitor build from top fails to update version
[ https://issues.apache.org/jira/browse/TC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705847#comment-15705847 ] ASF GitHub Bot commented on TC-56: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/109 > traffic_monitor build from top fails to update version > -- > > Key: TC-56 > URL: https://issues.apache.org/jira/browse/TC-56 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Monitor >Affects Versions: 1.8.0 > Environment: build from top-level of incubator-trafficcontrol >Reporter: Dan Kirkwood >Assignee: Dan Kirkwood >Priority: Trivial > Fix For: 1.9.0 > > > `$ ./build/build.sh traffic_monitor` > [ERROR] Failed to execute goal > org.codehaus.mojo:versions-maven-plugin:2.2:set (default-cli): Goal requires > a project to execute but there is no POM in this directory > (/vagrant/dangogh). Please verify you invoked Maven from the correct > directory. -> [Help 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-56) traffic_monitor build from top fails to update version
[ https://issues.apache.org/jira/browse/TC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705844#comment-15705844 ] Dan Kirkwood commented on TC-56: hard-coded version is 1.8.0 in traffic_monitor/pom.xml -- no need to fix in this version, but should be fixed for subsequent versions.. > traffic_monitor build from top fails to update version > -- > > Key: TC-56 > URL: https://issues.apache.org/jira/browse/TC-56 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Monitor >Affects Versions: 1.8.0 > Environment: build from top-level of incubator-trafficcontrol >Reporter: Dan Kirkwood >Assignee: Dan Kirkwood >Priority: Trivial > Fix For: 1.9.0 > > > `$ ./build/build.sh traffic_monitor` > [ERROR] Failed to execute goal > org.codehaus.mojo:versions-maven-plugin:2.2:set (default-cli): Goal requires > a project to execute but there is no POM in this directory > (/vagrant/dangogh). Please verify you invoked Maven from the correct > directory. -> [Help 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-54) Initial ORT fails due to missing ats UID
[ https://issues.apache.org/jira/browse/TC-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705854#comment-15705854 ] ASF GitHub Bot commented on TC-54: -- Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/107 > Initial ORT fails due to missing ats UID > > > Key: TC-54 > URL: https://issues.apache.org/jira/browse/TC-54 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops ORT >Affects Versions: 1.8.0 >Reporter: Jeff Elsloo >Priority: Minor > Fix For: 1.9.0 > > Original Estimate: 5m > Remaining Estimate: 5m > > When using ORT to perform an initial/clean install of ATS, the "ats" user is > missing at the time we attempt to seed a global variable with its UID. > Subsequently, the "trafficserver" package is installed, and operations > requiring the UID (config files) fail. > The fix is to simply move the line of code that defines the global variable > to occur after any package installation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-57) Build process not changing directory and reading configuration file
[ https://issues.apache.org/jira/browse/TC-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705848#comment-15705848 ] Dan Kirkwood commented on TC-57: First part (Using ~/build/build.sh fails to build Traffic Monitor) addressed by https://issues.apache.org/jira/browse/TC-56 > Build process not changing directory and reading configuration file > --- > > Key: TC-57 > URL: https://issues.apache.org/jira/browse/TC-57 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Monitor >Affects Versions: 1.9.0 > Environment: Vagrant + Centos 6.8 or Centos 7.2 >Reporter: Steve Malenfant >Priority: Minor > > Followed direction posted on the Traffic Monitor Developer’s Guide but I > couldn't seem to get Traffic Monitor test to work. > Using ~/build/build.sh fails to build Traffic Monitor > Using ~/build/build.sh traffic_monitor works but tests aren't working > Using cd traffic_monitor; ./build/build/build_rpm.sh seems to compile maven > but fails to find valid configuration file > I don't think I've successfully been able to run Traffic Monitor tests in the > past and my environment might be incorrect. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-58) Remove dependency of JDNSSEC library
Trevor Ackerman created TC-58: - Summary: Remove dependency of JDNSSEC library Key: TC-58 URL: https://issues.apache.org/jira/browse/TC-58 Project: Traffic Control Issue Type: Bug Components: Traffic Router Affects Versions: 1.8.0 Reporter: Trevor Ackerman Fix For: 1.9.0 The JDNSSEC library used by Traffic Router is not compliant with the Apache License -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-58) Remove dependency of JDNSSEC library
[ https://issues.apache.org/jira/browse/TC-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706060#comment-15706060 ] ASF GitHub Bot commented on TC-58: -- GitHub user trevorackerman opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/110 [TC-58] TR able to work without JDNSSEC Traffic Router will still use JDNSSEC by default. Add parameter 'usejdnssec=false' to the config section of CR Config and snapshot to make Traffic Router use only the dnsjava library that is compliant with the Apache License This goes towards being able to remove JDNSSEC dependency The next step is to simply remove it altogether and collapse some of the interfaces that allow using either JDNSSEC or dnsjava You can merge this pull request into a Git repository by running: $ git pull https://github.com/trevorackerman/incubator-trafficcontrol alt-wrapper Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/110.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 #110 > Remove dependency of JDNSSEC library > > > Key: TC-58 > URL: https://issues.apache.org/jira/browse/TC-58 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Router >Affects Versions: 1.8.0 >Reporter: Trevor Ackerman > Labels: triaged > Fix For: 1.9.0 > > > The JDNSSEC library used by Traffic Router is not compliant with the Apache > License -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-59) Traffic Ops Client should return HTTP body on Error response
David Neuman created TC-59: -- Summary: Traffic Ops Client should return HTTP body on Error response Key: TC-59 URL: https://issues.apache.org/jira/browse/TC-59 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Client Reporter: David Neuman Currently, if the Traffic Ops client gets back an Error response from TO, the calling method is returned a struct containing the StatusCode and Status (https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/client/traffic_ops.go#L180). Sometimes there is useful information in the body of the response as well - such as why an error occured -- so it would be useful to return the body to the calling method as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-56) traffic_monitor build from top fails to update version
[ https://issues.apache.org/jira/browse/TC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706520#comment-15706520 ] ASF GitHub Bot commented on TC-56: -- GitHub user dangogh opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/111 [TC-56] get rpm version names right on traffic_monitor and traffic_router You can merge this pull request into a Git repository by running: $ git pull https://github.com/dangogh/incubator-trafficcontrol pom-versions Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/111.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 #111 commit 8365629b8a8583b8b6996d2c75ca8a27ab539c21 Author: Dan Kirkwood Date: 2016-11-29T20:38:43Z use env BUILD_NUMBER and RHEL_NUMBER for release name commit 396e6b9c340abc19f33eeddc1e6c4d69a4630e35 Author: Dan Kirkwood Date: 2016-11-29T20:47:47Z up traffic_monitor and traffic_router to version 1.9.0 > traffic_monitor build from top fails to update version > -- > > Key: TC-56 > URL: https://issues.apache.org/jira/browse/TC-56 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Monitor >Affects Versions: 1.8.0 > Environment: build from top-level of incubator-trafficcontrol >Reporter: Dan Kirkwood >Assignee: Dan Kirkwood >Priority: Trivial > Fix For: 1.9.0 > > > `$ ./build/build.sh traffic_monitor` > [ERROR] Failed to execute goal > org.codehaus.mojo:versions-maven-plugin:2.2:set (default-cli): Goal requires > a project to execute but there is no POM in this directory > (/vagrant/dangogh). Please verify you invoked Maven from the correct > directory. -> [Help 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-29) Traffic Router TPS for HTTPS requests diminishes when reloading certificates
[ https://issues.apache.org/jira/browse/TC-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706634#comment-15706634 ] ASF GitHub Bot commented on TC-29: -- GitHub user trevorackerman opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/112 [TC-29] TR can now use NIO tomcat connectors NIO is now used by default as the tomcat connector The blocking version is still available, just update /opt/tomcat/conf/server.xml after install You can merge this pull request into a Git repository by running: $ git pull https://github.com/trevorackerman/incubator-trafficcontrol tr-nio-nosync Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/112.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 #112 commit 8859aabf4e5ef70b2bb9d939ad274887168c67b9 Author: trevorackerman Date: 2016-11-22T18:32:42Z TR - add ability to use NIO for custom tomcat connector (cherry picked from commit d069d9dd8ee814cf9c559e2ff78e0312b52a17ca) commit 73c14d95418836b57a6b10f519964da7135222d8 Author: Trevor Ackerman Date: 2016-11-22T17:31:53Z TR - avoid unnecessary synchronization for https cert registry (cherry picked from commit 8d1732dc14ec98d075bdecc3866298def8dd0ef4) > Traffic Router TPS for HTTPS requests diminishes when reloading certificates > > > Key: TC-29 > URL: https://issues.apache.org/jira/browse/TC-29 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Router >Reporter: David Neuman > > When Traffic Router reloads SSL certificates while processing HTTPS > transactions, the TPS drops significantly. > Example Log output during the drop in TPS: > INFO 2016-11-07T14:05:23.363 [pool-2-thread-1] > com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - GETing: > https://to.kabletown.net/api/1.2/cdns/name/test-xc > r/sslkeys.json; timeout is 15000 > INFO 2016-11-07T14:05:23.500 [New I/O worker #8] > com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - > Entered processConfig > INFO 2016-11-07T14:05:23.500 [New I/O worker #8] > com.comcast.cdn.traffic_control.traffic_router.core.config.ConfigHandler - > Exiting processConfig: No json data to process > ERROR 2016-11-07T14:05:24.760 [Thread-5] > com.comcast.cdn.traffic_control.traffic_router.core.config.CertificateChecker > - No certificate data for https cdn-ds-02 domain ds-02.cdn.kabletown.net.net > ERROR 2016-11-07T14:05:24.760 [Thread-5] > com.comcast.cdn.traffic_control.traffic_router.core.config.CertificateChecker > - No certificate data for https cdn-ds-01 domain ds-01.cdn.kabletown.net.net > ERROR 2016-11-07T14:05:24.760 [Thread-5] > com.comcast.cdn.traffic_control.traffic_router.core.config.CertificateChecker > - No certificate data for https cdn-ds-05 domain ds-05.cdn.kabletown.net.net > ERROR 2016-11-07T14:05:24.760 [Thread-5] > com.comcast.cdn.traffic_control.traffic_router.core.config.CertificateChecker > - No certificate data for https cdn-ds-04 domain ds-04.cdn.kabletown.net.net > ERROR 2016-11-07T14:05:24.760 [Thread-5] > com.comcast.cdn.traffic_control.traffic_router.core.config.CertificateChecker > - No certificate data for https cdn-ds-03 domain ds-03.cdn.kabletown.net.net > INFO 2016-11-07T14:05:43.399 [pool-17-thread-1] > com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - GETing: > https://to.kabletown.net/api/1.1/cdns/name/test-xcr/dnsseckeys.json; timeout > is 3 > INFO 2016-11-07T14:06:23.339 [pool-5-thread-1] > com.comcast.cdn.traffic_control.traffic_router.core.monitor.TrafficMonitorWatcher > - Loading properties from /opt/traffic_router/conf/traffic_monitor.properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-55) Multi Delivery Services With Same Domain Name and Different Path Prefixes
[ https://issues.apache.org/jira/browse/TC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706891#comment-15706891 ] Jan van Doorn commented on TC-55: - I'm very confused. Need to really look at the doc, just skimmed it, but... Why not use the existing regex table and the existing UI for that? It just needs the 'plumbing' in Topology.pm and Configfiles.pm, I think? > Multi Delivery Services With Same Domain Name and Different Path Prefixes > - > > Key: TC-55 > URL: https://issues.apache.org/jira/browse/TC-55 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops, Traffic Ops API >Affects Versions: 1.7.0 >Reporter: Jifeng Yang > > Enhance TC to support: > Multi Delivery Services With Same Domain Name and Different Path Prefixes > Details please ref the link: > https://docs.google.com/document/d/19-TZ6ODla_vdiYqZajbpRiOpLvpbJxil1SvIm44zb-0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TC-55) Multi Delivery Services With Same Domain Name and Different Path Prefixes
[ https://issues.apache.org/jira/browse/TC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan van Doorn updated TC-55: Attachment: screenshot-1.png > Multi Delivery Services With Same Domain Name and Different Path Prefixes > - > > Key: TC-55 > URL: https://issues.apache.org/jira/browse/TC-55 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops, Traffic Ops API >Affects Versions: 1.7.0 >Reporter: Jifeng Yang > Attachments: screenshot-1.png > > > Enhance TC to support: > Multi Delivery Services With Same Domain Name and Different Path Prefixes > Details please ref the link: > https://docs.google.com/document/d/19-TZ6ODla_vdiYqZajbpRiOpLvpbJxil1SvIm44zb-0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-55) Multi Delivery Services With Same Domain Name and Different Path Prefixes
[ https://issues.apache.org/jira/browse/TC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706894#comment-15706894 ] Jan van Doorn commented on TC-55: - See also attachment (https://issues.apache.org/jira/secure/attachment/12840948/screenshot-1.png ) i just added. > Multi Delivery Services With Same Domain Name and Different Path Prefixes > - > > Key: TC-55 > URL: https://issues.apache.org/jira/browse/TC-55 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops, Traffic Ops API >Affects Versions: 1.7.0 >Reporter: Jifeng Yang > Attachments: screenshot-1.png > > > Enhance TC to support: > Multi Delivery Services With Same Domain Name and Different Path Prefixes > Details please ref the link: > https://docs.google.com/document/d/19-TZ6ODla_vdiYqZajbpRiOpLvpbJxil1SvIm44zb-0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-55) Multi Delivery Services With Same Domain Name and Different Path Prefixes
[ https://issues.apache.org/jira/browse/TC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707140#comment-15707140 ] Eric Friedrich commented on TC-55: -- The existing PATH_REGEXP can't be used as a remap rule on Traffic Server because the remap.config file does not support regex's, only path prefixes (which this PR proposes to add). > Multi Delivery Services With Same Domain Name and Different Path Prefixes > - > > Key: TC-55 > URL: https://issues.apache.org/jira/browse/TC-55 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops, Traffic Ops API >Affects Versions: 1.7.0 >Reporter: Jifeng Yang > Attachments: screenshot-1.png > > > Enhance TC to support: > Multi Delivery Services With Same Domain Name and Different Path Prefixes > Details please ref the link: > https://docs.google.com/document/d/19-TZ6ODla_vdiYqZajbpRiOpLvpbJxil1SvIm44zb-0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-55) Multi Delivery Services With Same Domain Name and Different Path Prefixes
[ https://issues.apache.org/jira/browse/TC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707157#comment-15707157 ] Jan van Doorn commented on TC-55: - So from a TR perspective, nothing changes - it'll still decide delivery service on the HOST_REGEXP, and route within it on the path. Then on on ATS, we allow for different cache treatment (storage volume assignment, header rewrites, other remap plugins) for different paths, but always to the same origin? > Multi Delivery Services With Same Domain Name and Different Path Prefixes > - > > Key: TC-55 > URL: https://issues.apache.org/jira/browse/TC-55 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops, Traffic Ops API >Affects Versions: 1.7.0 >Reporter: Jifeng Yang > Attachments: screenshot-1.png > > > Enhance TC to support: > Multi Delivery Services With Same Domain Name and Different Path Prefixes > Details please ref the link: > https://docs.google.com/document/d/19-TZ6ODla_vdiYqZajbpRiOpLvpbJxil1SvIm44zb-0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
