[jira] [Closed] (TC-80) Add api/version/cachegroups/:id/parameters endpoint

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell closed TC-80.
-

> Add api/version/cachegroups/:id/parameters endpoint
> ---
>
> Key: TC-80
> URL: https://issues.apache.org/jira/browse/TC-80
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 1.9.0
>
>
> Provide the ability to fetch cachegroup parameters through the api such as
> api/version/cachegroups/:id/parameters
> Also, while you're in there, provide the ability to fetch cachegroup asns 
> through the api such as:
> api/version/asns?cachegroup=x
> and filter phys locations by region like:
> api/version/physLocations?region=x



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (TC-64) Experimental SPA application

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell closed TC-64.
-

> Experimental SPA application
> 
>
> Key: TC-64
> URL: https://issues.apache.org/jira/browse/TC-64
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops, Traffic Ops API, Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: spa
>
> At the 2016 Traffic Control summit, a prototype of a SPA application 
> developed by [~mitchell...@apache.org] using AngularJS was demo'd that works 
> entirely on top of the TO API.
> This issue is a placeholder for any work done to this prototype / 
> experimental UI. The goal is to replicate the functionality of the current 
> MVC TO UI. nothing more, nothing less.
> This will require some additions to the TO API. look for issues regarding 
> each API addition.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TC-64) Experimental SPA application

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell resolved TC-64.
---
Resolution: Fixed

> Experimental SPA application
> 
>
> Key: TC-64
> URL: https://issues.apache.org/jira/browse/TC-64
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops, Traffic Ops API, Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: spa
>
> At the 2016 Traffic Control summit, a prototype of a SPA application 
> developed by [~mitchell...@apache.org] using AngularJS was demo'd that works 
> entirely on top of the TO API.
> This issue is a placeholder for any work done to this prototype / 
> experimental UI. The goal is to replicate the functionality of the current 
> MVC TO UI. nothing more, nothing less.
> This will require some additions to the TO API. look for issues regarding 
> each API addition.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-60) CDN usage overview API always returns tps=0

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell commented on TC-60:
---

[~hbeatty] - no need to fix in 2.1

> CDN usage overview API always returns tps=0
> ---
>
> Key: TC-60
> URL: https://issues.apache.org/jira/browse/TC-60
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 1.7.0
>Reporter: Jeremy Mitchell
>Priority: Minor
>  Labels: api_usage
>
> /api/1.2/cdns/usage/overview always returns tps=0
> I suspect the problem lies in the usage_overview_tps_query() query
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/Extensions/TrafficStats/Delegate/CdnStatistics.pm#L104



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (TC-71) Remove hardcoded reference to ccr in UI/DeliveryService.pm

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell reassigned TC-71:
-

Assignee: Jeremy Mitchell

> Remove hardcoded reference to ccr in UI/DeliveryService.pm
> --
>
> Key: TC-71
> URL: https://issues.apache.org/jira/browse/TC-71
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: deliveryservice.pm, routing
>
> because the value of http.routing.name in applicationContext.xml can be 
> anything (defaults to tr), this needs to be dynamic rather than referencing 
> the hard-coded value of 'ccr'. So my suggestion would be:
> create a global parameter using a database migration file and name the 
> parameter http.routing.name and set the default value to 'tr'. then in the 
> code, fetch the value of http.routing.name and use that on line 147 & 150
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/UI/DeliveryService.pm#L147
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/UI/DeliveryService.pm#L150



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (TC-82) Eliminate duplicate implementations of deliveryservice, cachegroup and server api endpoints

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell closed TC-82.
-

> Eliminate duplicate implementations of deliveryservice, cachegroup and server 
> api endpoints
> ---
>
> Key: TC-82
> URL: https://issues.apache.org/jira/browse/TC-82
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: api_endpoints
>
> The following endpoints are duplicates and need to be reconciled:
> Delivery Services:
> GET /api/$version/deliveryservices
> GET /api/$version/deliveryservices/list <-- remove
> GET /api/$version/deliveryservices/:id
> GET /api/$version/deliveryservices/:id/get <-- remove
> POST /api/$version/deliveryservices
> POST /api/$version/deliveryservices/create <-- remove
> PUT /api/$version/deliveryservices/:id
> PUT /api/$version/deliveryservices/:id/update <-- remove
> Cache Groups:
> GET /api/$version/cachegroups
> GET /api/$version/cachegroups/list <-- remove
> POST /api/$version/cachegroups
> POST /api/$version/cachegroups/create <-- remove
> PUT /api/$version/cachegroups/:id
> PUT /api/$version/cachegroups/:id/update <-- remove
> DELETE /api/$version/cachegroups/:id
> DELETE /api/$version/cachegroups/:id/delete <-- remove
> Servers:
> POST /api/$version/servers
> POST /api/$version/servers/create <-- remove
> PUT /api/$version/servers/:id
> PUT /api/$version/servers/:id/update <-- remove



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (TC-71) Remove hardcoded reference to ccr in UI/DeliveryService.pm

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell reassigned TC-71:
-

Assignee: Rawlin Peters  (was: Jeremy Mitchell)

> Remove hardcoded reference to ccr in UI/DeliveryService.pm
> --
>
> Key: TC-71
> URL: https://issues.apache.org/jira/browse/TC-71
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops
>Reporter: Jeremy Mitchell
>Assignee: Rawlin Peters
>Priority: Minor
>  Labels: deliveryservice.pm, routing
>
> because the value of http.routing.name in applicationContext.xml can be 
> anything (defaults to tr), this needs to be dynamic rather than referencing 
> the hard-coded value of 'ccr'. So my suggestion would be:
> create a global parameter using a database migration file and name the 
> parameter http.routing.name and set the default value to 'tr'. then in the 
> code, fetch the value of http.routing.name and use that on line 147 & 150
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/UI/DeliveryService.pm#L147
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/UI/DeliveryService.pm#L150



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (TC-81) Add additional filters to collection apis

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell closed TC-81.
-

> Add additional filters to collection apis
> -
>
> Key: TC-81
> URL: https://issues.apache.org/jira/browse/TC-81
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 1.9.0
>
>
> Add the ability to filter the following collections as follows:
> /api/deliveryservices/:id/servers <-- retrieve all edge servers assigned to a 
> ds
> /api/servers/:id/deliveryservices <-- retrieve all ds's assigend to a server
> /api/parameters/:id/profiles <-- retrieve all profiles assigned to a parameter
> /api/users/:id/deliveryservices <-- retrieve all ds's assigned to a user
> /api/deliveryservices?cdn=x <-- to retrieve a cdn's ds's
> /api/regions?division=x <-- to retrieve a division's regions
> /api/servers?physLocation=x <-- to retrieve a phys location's servers
> /api/cachegroups?type=x <-- to retrieve cachegroups by type
> /api/deliveryservices?type=x <-- to retrieve deliveryservices by type
> The api already provides the ability to:
> - retrieve a cachegroup's asns
> - retrieve a cachegroup's parameters
> - retrieve a cachegroup's servers
> - retrieve a cdn's servers
> - retrieve a profile's parameters
> - retrieve a profile's servers
> - retrieve a region's phys locations
> By adding these additional filters, it provides the ability to navigate the 
> relationships in the database (i.e. provides drill-down capabilities)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-100) DELETE api/version/regions/:id should ensure no phys locs are in the region

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell commented on TC-100:


no need to fix in 2.1 [~hbeatty]


> DELETE api/version/regions/:id should ensure no phys locs are in the region
> ---
>
> Key: TC-100
> URL: https://issues.apache.org/jira/browse/TC-100
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Priority: Minor
>  Labels: api_regions
>
> Currently, you can attempt to delete a region that is employed by a phys 
> location which results in a database FK constraint error.
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::Pg::st execute 
> failed: ERROR:  update or delete on table region violates foreign 
> key constraint fk_phys_location_region on table 
> phys_location
> DETAIL:  Key (id)=(1) is still referenced from table 
> phys_location. [for Statement DELETE FROM region WHERE ( id 
> = ? ) with ParamValues: 1=1] at 
> /opt/traffic_ops/app/lib/API/Region.pm line 243
> the api needs to ensure that no phys locs use the region before attempting to 
> delete the region.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TC-82) Eliminate duplicate implementations of deliveryservice, cachegroup and server api endpoints

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell resolved TC-82.
---
Resolution: Fixed

> Eliminate duplicate implementations of deliveryservice, cachegroup and server 
> api endpoints
> ---
>
> Key: TC-82
> URL: https://issues.apache.org/jira/browse/TC-82
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>  Labels: api_endpoints
>
> The following endpoints are duplicates and need to be reconciled:
> Delivery Services:
> GET /api/$version/deliveryservices
> GET /api/$version/deliveryservices/list <-- remove
> GET /api/$version/deliveryservices/:id
> GET /api/$version/deliveryservices/:id/get <-- remove
> POST /api/$version/deliveryservices
> POST /api/$version/deliveryservices/create <-- remove
> PUT /api/$version/deliveryservices/:id
> PUT /api/$version/deliveryservices/:id/update <-- remove
> Cache Groups:
> GET /api/$version/cachegroups
> GET /api/$version/cachegroups/list <-- remove
> POST /api/$version/cachegroups
> POST /api/$version/cachegroups/create <-- remove
> PUT /api/$version/cachegroups/:id
> PUT /api/$version/cachegroups/:id/update <-- remove
> DELETE /api/$version/cachegroups/:id
> DELETE /api/$version/cachegroups/:id/delete <-- remove
> Servers:
> POST /api/$version/servers
> POST /api/$version/servers/create <-- remove
> PUT /api/$version/servers/:id
> PUT /api/$version/servers/:id/update <-- remove



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (TC-102) API changes to reflect true datatypes

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell closed TC-102.
--

> API changes to reflect true datatypes
> -
>
> Key: TC-102
> URL: https://issues.apache.org/jira/browse/TC-102
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops, Traffic Ops API
>Affects Versions: 2.0.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>  Labels: postgres
> Fix For: 2.0.0
>
>
> With the move from MySQL to Postgres, the API will reflect the true data 
> types of each value as represented in the database. For example, the Postgres 
> version of the TO database now has boolean columns (rather than using 
> smallint). These values should be represented in the API as booleans 
> (true|false) as opposed to "0"|"1" as before.
> Also, in the old MySQL TO, ints or numbers were represented as "age":"23" in 
> the API. That should change to "age":23
> These are the datatypes available in json and they should be taken advantage 
> of when possible:
> Boolean:  true|false
> String: double-quoted Unicode with backslash escaping
> Number: double- precision floating-point format
> Array: an ordered sequence of values
> Object: an unordered collection of key:value pairs
> Null
> I'm creating this issue as a catch-all for any changes required to reflect 
> the true data types in the api.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-123) UI route (/healthdatadeliveryservice) is broken as no related html template exists

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell commented on TC-123:


no need to fix in 2.1 [~hbeatty]

> UI route (/healthdatadeliveryservice) is broken as no related html template 
> exists
> --
>
> Key: TC-123
> URL: https://issues.apache.org/jira/browse/TC-123
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops, Traffic Ops API
>Affects Versions: 2.1.0, 2.0.0
>Reporter: Jeremy Mitchell
>Priority: Trivial
>  Labels: api_healthdatadeliveryservice
>
> /healthdatadeliveryservice returns a 404 as no related html template exists 
> for this route. My guess is this route can be deleted entirely but some 
> research is probably needed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (TC-123) UI route (/healthdatadeliveryservice) is broken as no related html template exists

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell updated TC-123:
---
Priority: Trivial  (was: Minor)

> UI route (/healthdatadeliveryservice) is broken as no related html template 
> exists
> --
>
> Key: TC-123
> URL: https://issues.apache.org/jira/browse/TC-123
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops, Traffic Ops API
>Affects Versions: 2.1.0, 2.0.0
>Reporter: Jeremy Mitchell
>Priority: Trivial
>  Labels: api_healthdatadeliveryservice
>
> /healthdatadeliveryservice returns a 404 as no related html template exists 
> for this route. My guess is this route can be deleted entirely but some 
> research is probably needed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (TC-149) GET api/1.2/deliveryservices/hostname/:hostname/sslkeys returns 400

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell closed TC-149.
--
Resolution: Cannot Reproduce

> GET api/1.2/deliveryservices/hostname/:hostname/sslkeys returns 400
> ---
>
> Key: TC-149
> URL: https://issues.apache.org/jira/browse/TC-149
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops, Traffic Ops API
>Reporter: Jeremy Mitchell
>Priority: Minor
>  Labels: api_deliveryservices
>
> GET api/1.2/deliveryservices/hostname/:hostname/sslkeys returns 400 even 
> though it can reach the Riak servers.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (TC-191) Steering DS API should use standard response codes as defined in API guidelines

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell reassigned TC-191:
--

Assignee: (was: Jeremy Mitchell)

> Steering DS API should use standard response codes as defined in API 
> guidelines
> ---
>
> Key: TC-191
> URL: https://issues.apache.org/jira/browse/TC-191
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Priority: Minor
>  Labels: steering
> Fix For: 2.2.0
>
>
> To keep the API consistent, API guidelines have been documented here: 
> https://cwiki.apache.org/confluence/display/TC/API+Guidelines
> See "Response Codes" section. Also, there are helper functions in 
> Utils/Helper.pm to return error response codes along with a message.
> By keeping response codes consistent, it makes it easier to consume the api 
> and respond to error scenarios.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (TC-308) hdr_rw_* gets inserted in profiles, but they don't get removed...

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell updated TC-308:
---
Reporter: Steve Malenfant  (was: Jeremy Mitchell)

> hdr_rw_* gets inserted in profiles, but they don't get removed...
> -
>
> Key: TC-308
> URL: https://issues.apache.org/jira/browse/TC-308
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Reporter: Steve Malenfant
>Priority: Minor
>  Labels: profile_parameters
>
> Moved from https://github.com/Comcast/traffic_control/issues/714
> Spend lots of time troubleshooting an config file generation issue which 
> referred to a delivery service that was deleted or renamed.
> If you look at the Profile Parameters, you'll notice there is entries you 
> probably never created yourselves. During configuration file generation, 
> looks like it looks for "^hdr_rw_mid" to see if needs to generate a file.
> If the parameter still exists and the delivery service doesn't, it throws an 
> error on either line 1210 or 1216 (looks like edge_header_rewrite is causing 
> a problem too).
> Removing the parameter does fix the problem. Do we really need to insert 
> those "locations" in the database?
> sub header_rewrite_dot_config {
> my $self = shift;
> my $id   = shift;
> my $file = shift;
> my $server= $self->server_data($id);
> my $text  = $self->header_comment( $server->host_name );
> my $ds_xml_id = undef;
> if ( $file =~ /^hdr_rw_mid_(.*)\.config$/ ) {
> $ds_xml_id = $1;
> my $ds = $self->db->resultset('Deliveryservice')->search( { xml_id => 
> $ds_xml_id }, { prefetch => [ 'type', 'profile' ] } )->single();
> my $actions = $ds->mid_header_rewrite;
> $text .= $actions . "\n";
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TC-423) TPv2 - add the ability to copy profiles

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell resolved TC-423.

   Resolution: Fixed
Fix Version/s: 2.1.0

> TPv2 - add the ability to copy profiles
> ---
>
> Key: TC-423
> URL: https://issues.apache.org/jira/browse/TC-423
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0
>
>
> In order to achieve feature parity with the existing TO UI, the ability to 
> copy profiles needs to be added to TP. This involves making a new profile 
> where you can define the name, description, cdn and type of the profile but 
> use the parameters of an existing profile.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (TC-419) TPv2 - enable auto-refresh for dashboard widgets

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell updated TC-419:
---
Fix Version/s: 2.1.0

> TPv2 - enable auto-refresh for dashboard widgets
> 
>
> Key: TC-419
> URL: https://issues.apache.org/jira/browse/TC-419
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0
>
>
> The widgets found on the Traffic Portal dashboard - 
> http://localhost:8080/#!/monitor/dashboard - should be set to auto-refresh at 
> a defined interval. This refresh should be configurable. I.e.
> dashboard: {
>   refresh: {
> enabled: true|false,
> interval: 3
>   }
> }



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TC-437) TPv2 - add the ability to generate ISO

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell resolved TC-437.

   Resolution: Fixed
Fix Version/s: 2.1.0

> TPv2 - add the ability to generate ISO
> --
>
> Key: TC-437
> URL: https://issues.apache.org/jira/browse/TC-437
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API, Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0
>
>
> add the ability to generate ISO



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (TC-423) TPv2 - add the ability to copy profiles

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell reassigned TC-423:
--

Assignee: Jeremy Mitchell

> TPv2 - add the ability to copy profiles
> ---
>
> Key: TC-423
> URL: https://issues.apache.org/jira/browse/TC-423
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> In order to achieve feature parity with the existing TO UI, the ability to 
> copy profiles needs to be added to TP. This involves making a new profile 
> where you can define the name, description, cdn and type of the profile but 
> use the parameters of an existing profile.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (TC-433) TPv2 - Add the ability to manage SSL keys for a delivery service

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell reassigned TC-433:
--

Assignee: Dylan Volz

> TPv2 - Add the ability to manage SSL keys for a delivery service
> 
>
> Key: TC-433
> URL: https://issues.apache.org/jira/browse/TC-433
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API, Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Dylan Volz
>Priority: Minor
>
> Add the ability to manage SSL keys for a delivery service



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (TC-437) TPv2 - add the ability to generate ISO

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell reassigned TC-437:
--

Assignee: Jeremy Mitchell

> TPv2 - add the ability to generate ISO
> --
>
> Key: TC-437
> URL: https://issues.apache.org/jira/browse/TC-437
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops API, Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> add the ability to generate ISO



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (TC-441) TPv2 - implement password reset functionality

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell reassigned TC-441:
--

Assignee: Jeremy Mitchell

> TPv2 - implement password reset functionality
> -
>
> Key: TC-441
> URL: https://issues.apache.org/jira/browse/TC-441
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> implement password reset functionality



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TC-453) TO API - change log entry not created when queuing updates on a cachegroup

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell resolved TC-453.

Resolution: Fixed

> TO API - change log entry not created when queuing updates on a cachegroup
> --
>
> Key: TC-453
> URL: https://issues.apache.org/jira/browse/TC-453
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0
>
>
> a change log entry should be created when queuing updates on a cache group.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (TC-480) TPv2 - show example URLs for delivery service

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell reopened TC-480:

  Assignee: Jeremy Mitchell

> TPv2 - show example URLs for delivery service
> -
>
> Key: TC-480
> URL: https://issues.apache.org/jira/browse/TC-480
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0
>
>
> On the deliveryservice view/edit page, show exampleUrls which should be 
> returned from the GET /api/*/deliveryservices/:id api



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TC-480) TPv2 - show example URLs for delivery service

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell resolved TC-480.

Resolution: Fixed

> TPv2 - show example URLs for delivery service
> -
>
> Key: TC-480
> URL: https://issues.apache.org/jira/browse/TC-480
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0
>
>
> On the deliveryservice view/edit page, show exampleUrls which should be 
> returned from the GET /api/*/deliveryservices/:id api



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TC-486) Add steering role to steering apis

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell resolved TC-486.

Resolution: Fixed

> Add steering role to steering apis
> --
>
> Key: TC-486
> URL: https://issues.apache.org/jira/browse/TC-486
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0
>
>
> Create, update and delete of steering targets should be available to users 
> with the "steering" role.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TC-498) TO API - when updating current user, full name is required

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell resolved TC-498.

   Resolution: Fixed
Fix Version/s: 2.1.0

> TO API - when updating current user, full name is required
> --
>
> Key: TC-498
> URL: https://issues.apache.org/jira/browse/TC-498
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0
>
>
> case error caused validation to fail. see fullName vs full_name
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/API/User.pm#L646
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/API/User.pm#L653



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (TC-486) Add steering role to steering apis

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell reopened TC-486:


> Add steering role to steering apis
> --
>
> Key: TC-486
> URL: https://issues.apache.org/jira/browse/TC-486
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops API
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.1.0
>
>
> Create, update and delete of steering targets should be available to users 
> with the "steering" role.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TC-524) TP - popout button on TPv2 doesn't open new window/tab as intended

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell resolved TC-524.

Resolution: Fixed

> TP - popout button on TPv2 doesn't open new window/tab as intended
> --
>
> Key: TC-524
> URL: https://issues.apache.org/jira/browse/TC-524
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (TC-524) TP - popout button on TPv2 doesn't open new window/tab as intended

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell reopened TC-524:


> TP - popout button on TPv2 doesn't open new window/tab as intended
> --
>
> Key: TC-524
> URL: https://issues.apache.org/jira/browse/TC-524
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-521) TPv2 - http-parser dependency cannot be resolved

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/79/



> TPv2 - http-parser dependency cannot be resolved 
> -
>
> Key: TC-521
> URL: https://issues.apache.org/jira/browse/TC-521
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Blocker
> Fix For: 2.1.0
>
>
> Therefore the Traffic Portal build fails.
> More details of the error: https://bugs.centos.org/view.php?id=13669=1



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #821: [BACKPORT] [TC-521] TPv2 - accounts for...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/41/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-521) TPv2 - http-parser dependency cannot be resolved

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/41/



> TPv2 - http-parser dependency cannot be resolved 
> -
>
> Key: TC-521
> URL: https://issues.apache.org/jira/browse/TC-521
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Blocker
> Fix For: 2.1.0
>
>
> Therefore the Traffic Portal build fails.
> More details of the error: https://bugs.centos.org/view.php?id=13669=1



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-521) TPv2 - http-parser dependency cannot be resolved

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/39/



> TPv2 - http-parser dependency cannot be resolved 
> -
>
> Key: TC-521
> URL: https://issues.apache.org/jira/browse/TC-521
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Blocker
> Fix For: 2.1.0
>
>
> Therefore the Traffic Portal build fails.
> More details of the error: https://bugs.centos.org/view.php?id=13669=1



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #821: [BACKPORT] [TC-521] TPv2 - accounts for...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/39/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-521) TPv2 - http-parser dependency cannot be resolved

[ASF GitHub Bot (JIRA)]

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

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

GitHub user mitchell852 opened a pull request:

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

[BACKPORT] [TC-521] TPv2 - accounts for missing dependency that centos 7.3 
doesn't provide

… when centos 7.4 is available this dependency will be provided with the 
distro.

(cherry picked from commit 15901255c1847800bbd871e33c757017ec23f74f)

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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
2.1.x-tc-521

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

https://github.com/apache/incubator-trafficcontrol/pull/821.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 #821


commit 66eb0cae181e340ef3602de9917dab9d9c4d3dc2
Author: Jeremy Mitchell 
Date:   2017-08-15T16:44:56Z

accounts for missing dependency that centos 7.3 doesn't provide. when 
centos 7.4 is available this dependency will be provided with the distro.

(cherry picked from commit 15901255c1847800bbd871e33c757017ec23f74f)




> TPv2 - http-parser dependency cannot be resolved 
> -
>
> Key: TC-521
> URL: https://issues.apache.org/jira/browse/TC-521
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Blocker
> Fix For: 2.1.0
>
>
> Therefore the Traffic Portal build fails.
> More details of the error: https://bugs.centos.org/view.php?id=13669=1



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol pull request #821: [BACKPORT] [TC-521] TPv2 - accou...

[mitchell852]

GitHub user mitchell852 opened a pull request:

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

[BACKPORT] [TC-521] TPv2 - accounts for missing dependency that centos 7.3 
doesn't provide

… when centos 7.4 is available this dependency will be provided with the 
distro.

(cherry picked from commit 15901255c1847800bbd871e33c757017ec23f74f)

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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
2.1.x-tc-521

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

https://github.com/apache/incubator-trafficcontrol/pull/821.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 #821


commit 66eb0cae181e340ef3602de9917dab9d9c4d3dc2
Author: Jeremy Mitchell 
Date:   2017-08-15T16:44:56Z

accounts for missing dependency that centos 7.3 doesn't provide. when 
centos 7.4 is available this dependency will be provided with the distro.

(cherry picked from commit 15901255c1847800bbd871e33c757017ec23f74f)




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-157) Failed to restart tomcat in Traffic Router when failed to get SSL keys

[ASF GitHub Bot (JIRA)]

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

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

Github user zhilhuan commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/294
  
What's happening here? Is this due to build server not reachable any more?


> Failed to restart tomcat in Traffic Router when failed to get SSL keys
> --
>
> Key: TC-157
> URL: https://issues.apache.org/jira/browse/TC-157
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Router
>Affects Versions: 1.7.0
>Reporter: Zhilin Huang
>Assignee: Zhilin Huang
>  Labels: ssl, tomcat
> Attachments: text.html
>
>
> Stopping tomcat failed with the following log:
> WARN  2017-02-17T09:00:05.939 [main] 
> com.comcast.cdn.traffic_control.traffic_router.core.secure.CertificatesPublisher
>  - Detected destroy setting running to false
> INFO  2017-02-17T09:00:05.943 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.secure.CertificatesClient 
> - Interrupted while pausing for check of traffic ops config
> INFO  2017-02-17T09:00:05.943 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - POSTing: 
> https://192.168.122.181/api/1.1/user/login; timeout is 15000
> INFO  2017-02-17T09:00:06.005 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - GETing: 
> https://192.168.122.181/api/1.2/cdns/name/kabletown_cdn/sslkeys.jso
> n; timeout is 15000
> WARN  2017-02-17T09:00:06.040 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - Failed 
> Http Request to https://192.168.122.181/api/1.2/cdns/name/kabletown_
> cdn/sslkeys.json Status 400



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (TC-524) TP - popout button on TPv2 doesn't open new window/tab as intended

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell closed TC-524.
--

> TP - popout button on TPv2 doesn't open new window/tab as intended
> --
>
> Key: TC-524
> URL: https://issues.apache.org/jira/browse/TC-524
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (TC-524) TP - popout button on TPv2 doesn't open new window/tab as intended

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell resolved TC-524.

   Resolution: Fixed
Fix Version/s: 2.2.0

> TP - popout button on TPv2 doesn't open new window/tab as intended
> --
>
> Key: TC-524
> URL: https://issues.apache.org/jira/browse/TC-524
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Fix For: 2.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-531) Traffic Monitor does not pull new cr-config when all servers in in "ONLINE" and not "REPORTED"

[Matt Mills (JIRA)]

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

Matt Mills commented on TC-531:
---

>From what I've been told, this is by design, because "ONLINE" isn't a valid 
>state for caches... which admittedly is somewhat confusing. 

Perhaps this should turn into a feature request for limiting the states you can 
set caches to only those that are valid in the UI? (REPORTED, ADMIN_DOWN, 
OFFLINE as far as I understand).

> Traffic Monitor does not pull new cr-config when all servers in in "ONLINE" 
> and not "REPORTED" 
> ---
>
> Key: TC-531
> URL: https://issues.apache.org/jira/browse/TC-531
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Monitor (golang)
>Affects Versions: 2.1.0
>Reporter: Nir Sopher
>Priority: Minor
>
> When all cache servers are forced to be ONLINE, TM seems not to pull the cfg, 
> with the below message in the log
> "No REPORTED caches exist in Traffic Ops, nothing to poll."



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-515) Traffic Portal - Show human readable protocol on DS page

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/78/



> Traffic Portal - Show human readable protocol on DS page
> 
>
> Key: TC-515
> URL: https://issues.apache.org/jira/browse/TC-515
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Reporter: David Neuman
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> In the TO UI, the delivery service protocol is converted from an int (0,1,2) 
> to a human readable string (http, https, http and https, etc).  The new TO 
> portal just shows the int but it should show the human readable string.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #818: [TC-515] - TPv2 - adds human readable d...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/78/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-515) Traffic Portal - Show human readable protocol on DS page

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/40/



> Traffic Portal - Show human readable protocol on DS page
> 
>
> Key: TC-515
> URL: https://issues.apache.org/jira/browse/TC-515
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Reporter: David Neuman
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> In the TO UI, the delivery service protocol is converted from an int (0,1,2) 
> to a human readable string (http, https, http and https, etc).  The new TO 
> portal just shows the int but it should show the human readable string.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #818: [TC-515] - TPv2 - adds human readable d...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/40/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-515) Traffic Portal - Show human readable protocol on DS page

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/38/



> Traffic Portal - Show human readable protocol on DS page
> 
>
> Key: TC-515
> URL: https://issues.apache.org/jira/browse/TC-515
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Reporter: David Neuman
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> In the TO UI, the delivery service protocol is converted from an int (0,1,2) 
> to a human readable string (http, https, http and https, etc).  The new TO 
> portal just shows the int but it should show the human readable string.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #818: [TC-515] - TPv2 - adds human readable d...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/38/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #820: added a secure flag to start.pl

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/77/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #820: added a secure flag to start.pl

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/39/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #820: added a secure flag to start.pl

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/37/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol pull request #820: added a secure flag to start.pl

[dewrich]

GitHub user dewrich opened a pull request:

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

added a secure flag to start.pl



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

$ git pull https://github.com/dewrich/incubator-trafficcontrol 
to-start-pl-secure

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

https://github.com/apache/incubator-trafficcontrol/pull/820.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 #820


commit 5b04f9273abd93f77e32a9063e138ed595a32168
Author: Dewayne Richardson 
Date:   2017-08-15T21:07:37Z

added a secure flag to start.pl




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (TC-531) Traffic Monitor does not pull new cr-config when all servers in in "ONLINE" and not "REPORTED"

[Nir Sopher (JIRA)]

Nir Sopher created TC-531:
-

 Summary: Traffic Monitor does not pull new cr-config when all 
servers in in "ONLINE" and not "REPORTED" 
 Key: TC-531
 URL: https://issues.apache.org/jira/browse/TC-531
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Monitor (golang)
Affects Versions: 2.1.0
Reporter: Nir Sopher
Priority: Minor


When all cache servers are forced to be ONLINE, TM seems not to pull the cfg, 
with the below message in the log
"No REPORTED caches exist in Traffic Ops, nothing to poll."



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-530) TRAFFIC_ROUTER default profile points to non existing coverage-zone DB endpoint

[Nir Sopher (JIRA)]

Nir Sopher created TC-530:
-

 Summary: TRAFFIC_ROUTER default profile points to non existing 
coverage-zone DB endpoint
 Key: TC-530
 URL: https://issues.apache.org/jira/browse/TC-530
 Project: Traffic Control
  Issue Type: Improvement
  Components: Documentation
Affects Versions: 2.1.0
Reporter: Nir Sopher
Priority: Minor


The "coveragezone.polling.url" variable in the TRAFFIC_ROUTER default profile 
published at 
http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops
 is set to http://${toHostname}/cdn/CZF/current/czf-current.json

However, this path does not exists in my traffic ops.
However, the path "routing/coverage-zone.json" does exists



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (TC-526) TM does not pull configuration where no DS/Server assignment exists

[Nir Sopher (JIRA)]

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

Nir Sopher updated TC-526:
--
Description: 
When DSes and Servers are already configured in traffic-ops, cr-config can be 
generated.
However, TM (and therefore the TR) ignores the cr-config if there is no 
DS/Server assignment ("MonitorConfigPoller: skipping this iteration, Session is 
nil").
As the cr-config hold much more than this mapping, I would like to suggest the 
configuration would not be ignored.

> TM does not pull configuration where no DS/Server assignment exists
> ---
>
> Key: TC-526
> URL: https://issues.apache.org/jira/browse/TC-526
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Monitor (golang)
>Affects Versions: 2.1.0
>Reporter: Nir Sopher
>Priority: Minor
>
> When DSes and Servers are already configured in traffic-ops, cr-config can be 
> generated.
> However, TM (and therefore the TR) ignores the cr-config if there is no 
> DS/Server assignment ("MonitorConfigPoller: skipping this iteration, Session 
> is nil").
> As the cr-config hold much more than this mapping, I would like to suggest 
> the configuration would not be ignored.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (TC-527) Traffic_Router Default Profile - Uses unsupported pattern (${toHostname})

[Nir Sopher (JIRA)]

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

Nir Sopher updated TC-527:
--
Description: 
Few variables in the TRAFFIC_ROUTER default profile published at 
http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops
 uses the pattern ${toHostname}, however, at least till commit  
3980b41797c8f2b616277df4b74e73a011c48869, traffic router does not replace this 
pattern with the ops hostname.

I would suggest to add a "README" besides the default profile, with 
instructions to replace this pattern manually (until TR supports it)

> Traffic_Router Default Profile - Uses unsupported pattern (${toHostname})
> -
>
> Key: TC-527
> URL: https://issues.apache.org/jira/browse/TC-527
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Documentation
>Affects Versions: 2.1.0
> Environment: Few variables in the TRAFFIC_ROUTER default profile 
> published at 
> http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops
>  uses the pattern ${toHostname}, however, at least till commit  
> 3980b41797c8f2b616277df4b74e73a011c48869, traffic router does not replace 
> this pattern with the ops hostname.
> I would suggest to add a "README" besides the default profile, with 
> instructions to replace this pattern manually (until TR supports it)
>Reporter: Nir Sopher
>Priority: Minor
>
> Few variables in the TRAFFIC_ROUTER default profile published at 
> http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops
>  uses the pattern ${toHostname}, however, at least till commit  
> 3980b41797c8f2b616277df4b74e73a011c48869, traffic router does not replace 
> this pattern with the ops hostname.
> I would suggest to add a "README" besides the default profile, with 
> instructions to replace this pattern manually (until TR supports it)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (TC-526) TM does not pull configuration where no DS/Server assignment exists

[Nir Sopher (JIRA)]

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

Nir Sopher updated TC-526:
--
Environment: (was: When DSes and Servers are already configured in 
traffic-ops, cr-config can be generated.
However, TM (and therefore the TR) ignores the cr-config if there is no 
DS/Server assignment ("MonitorConfigPoller: skipping this iteration, Session is 
nil").
As the cr-config hold much more than this mapping, I would like to suggest the 
configuration would not be ignored.)

> TM does not pull configuration where no DS/Server assignment exists
> ---
>
> Key: TC-526
> URL: https://issues.apache.org/jira/browse/TC-526
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Monitor (golang)
>Affects Versions: 2.1.0
>Reporter: Nir Sopher
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (TC-528) Traffic Router - To support the ${toHostname} pattern when parsing the cr-config

[Nir Sopher (JIRA)]

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

Nir Sopher updated TC-528:
--
Description: 
Few variables in the TRAFFIC_ROUTER default profile published at 
http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops
 use the pattern ${toHostname}, however, at least till commit  
3980b41797c8f2b616277df4b74e73a011c48869, traffic router does not replace this 
pattern with the ops hostname.


> Traffic Router - To support the ${toHostname} pattern when parsing the 
> cr-config
> 
>
> Key: TC-528
> URL: https://issues.apache.org/jira/browse/TC-528
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Router
>Affects Versions: 2.1.0
>Reporter: Nir Sopher
>Priority: Minor
>
> Few variables in the TRAFFIC_ROUTER default profile published at 
> http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops
>  use the pattern ${toHostname}, however, at least till commit  
> 3980b41797c8f2b616277df4b74e73a011c48869, traffic router does not replace 
> this pattern with the ops hostname.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (TC-528) Traffic Router - To support the ${toHostname} pattern when parsing the cr-config

[Nir Sopher (JIRA)]

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

Nir Sopher updated TC-528:
--
Environment: (was: Few variables in the TRAFFIC_ROUTER default profile 
published at 
http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops
 use the pattern ${toHostname}, however, at least till commit  
3980b41797c8f2b616277df4b74e73a011c48869, traffic router does not replace this 
pattern with the ops hostname.
)

> Traffic Router - To support the ${toHostname} pattern when parsing the 
> cr-config
> 
>
> Key: TC-528
> URL: https://issues.apache.org/jira/browse/TC-528
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Router
>Affects Versions: 2.1.0
>Reporter: Nir Sopher
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (TC-529) TRAFFIC_ROUTER default profile points to non existing geolocation DB endpoint

[Nir Sopher (JIRA)]

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

Nir Sopher updated TC-529:
--
Description: 
The "geolocation.polling.url" variable in the TRAFFIC_ROUTER default profile 
published at 
http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops
 is set to http://${toHostname}/MaxMind/auto/GeoIP2-City.mmdb.gz.

However, this path does not exists in my traffic ops.
However, the path  "routing/GeoLite2-City.mmdb.gz" does exists

  was:
The "eolocation.polling.url" variable in the TRAFFIC_ROUTER default profile 
published at 
http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops
 is set to http://${toHostname}/MaxMind/auto/GeoIP2-City.mmdb.gz.

However, this path does not exists in my traffic ops.
However, the path  "routing/GeoLite2-City.mmdb.gz" does exists


> TRAFFIC_ROUTER default profile points to non existing geolocation DB endpoint
> -
>
> Key: TC-529
> URL: https://issues.apache.org/jira/browse/TC-529
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Router
>Affects Versions: 2.1.0
>Reporter: Nir Sopher
>Priority: Minor
>
> The "geolocation.polling.url" variable in the TRAFFIC_ROUTER default profile 
> published at 
> http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops
>  is set to http://${toHostname}/MaxMind/auto/GeoIP2-City.mmdb.gz.
> However, this path does not exists in my traffic ops.
> However, the path  "routing/GeoLite2-City.mmdb.gz" does exists



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (TC-529) TRAFFIC_ROUTER default profile points to non existing geolocation DB endpoint

[Nir Sopher (JIRA)]

Nir Sopher created TC-529:
-

 Summary: TRAFFIC_ROUTER default profile points to non existing 
geolocation DB endpoint
 Key: TC-529
 URL: https://issues.apache.org/jira/browse/TC-529
 Project: Traffic Control
  Issue Type: Improvement
  Components: Traffic Router
Affects Versions: 2.1.0
Reporter: Nir Sopher
Priority: Minor


The "eolocation.polling.url" variable in the TRAFFIC_ROUTER default profile 
published at 
http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops
 is set to http://${toHostname}/MaxMind/auto/GeoIP2-City.mmdb.gz.

However, this path does not exists in my traffic ops.
However, the path  "routing/GeoLite2-City.mmdb.gz" does exists



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #108: Multi delivery services with same domai...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/35/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #819: Modified the default config to reflect ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/36/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #819: Modified the default config to reflect ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR/76/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-115) ATS sometimes does not reload the config while receiving a "traffic_line -x"

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/32/



> ATS sometimes does not reload the config while receiving a "traffic_line -x"
> 
>
> Key: TC-115
> URL: https://issues.apache.org/jira/browse/TC-115
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops, Traffic Ops ORT
>Reporter: John Shen
>Assignee: John Shen
>Priority: Minor
>  Labels: traffic_line-x
>
> If the owner of a config file (e.g. ssl_multicert.config) is not ats.ats, ATS 
> does not reload the config while receiving a "traffic_line -x".



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-161) ort does not restart ATS when it should

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/30/



> ort does not restart ATS when it should
> ---
>
> Key: TC-161
> URL: https://issues.apache.org/jira/browse/TC-161
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops ORT
>Affects Versions: 2.1.0
>Reporter: John Shen
>Assignee: John Shen
> Fix For: 2.1.0
>
>
> ort does not restart ATS when ATS is already running



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-166) lastConfigCheck stat should be updated if CrConfigs have a different checksum but the same timestamp

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/29/



> lastConfigCheck stat should be updated if CrConfigs have a different checksum 
> but the same timestamp
> 
>
> Key: TC-166
> URL: https://issues.apache.org/jira/browse/TC-166
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Router
>Affects Versions: 2.0.0
>Reporter: David Neuman
>Priority: Minor
>  Labels: crconfig
>
> When Traffic Router checks for a new CrConfig it first checks to see if the 
> CrConfig returned from Traffic Monitor has the same checksum as it's current 
> version, if it doesn't then Traffic Router attempts to process it.  During 
> processing, if the new CrConfig has the same timestamp as the current 
> CrConfig, Traffic Router logs and info message and returns false.  A warning 
> is then logged saying CrConfig has been rejected.  This is ok, however, the 
> lastConfigCheck stat is not updated.  Since the CrConfigs are the same, the 
> lastConfigCheck stat should be updated.
> This is basically an edge case that we came across because we are running 
> javaTM and goTM in parallel.  The lastConfigCheck stat was only being updated 
> once every other poll, which cause our alarms to go off.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-157) Failed to restart tomcat in Traffic Router when failed to get SSL keys

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/31/



> Failed to restart tomcat in Traffic Router when failed to get SSL keys
> --
>
> Key: TC-157
> URL: https://issues.apache.org/jira/browse/TC-157
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Router
>Affects Versions: 1.7.0
>Reporter: Zhilin Huang
>Assignee: Zhilin Huang
>  Labels: ssl, tomcat
> Attachments: text.html
>
>
> Stopping tomcat failed with the following log:
> WARN  2017-02-17T09:00:05.939 [main] 
> com.comcast.cdn.traffic_control.traffic_router.core.secure.CertificatesPublisher
>  - Detected destroy setting running to false
> INFO  2017-02-17T09:00:05.943 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.secure.CertificatesClient 
> - Interrupted while pausing for check of traffic ops config
> INFO  2017-02-17T09:00:05.943 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - POSTing: 
> https://192.168.122.181/api/1.1/user/login; timeout is 15000
> INFO  2017-02-17T09:00:06.005 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - GETing: 
> https://192.168.122.181/api/1.2/cdns/name/kabletown_cdn/sslkeys.jso
> n; timeout is 15000
> WARN  2017-02-17T09:00:06.040 [pool-2-thread-1] 
> com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - Failed 
> Http Request to https://192.168.122.181/api/1.2/cdns/name/kabletown_
> cdn/sslkeys.json Status 400



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #211: [TC-115] make sure ats config files are...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/32/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #151: Add experimental Go ATS config

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/34/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #298: [TC-161] ort does not restart ATS when ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/30/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #294: [TC-157] router fail to restart due to ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/31/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #312: [TC-166] Traffic Router now updates the...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/29/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-169) TR download the RGB file continuously when the same RGB file on server

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/28/



> TR download the RGB file continuously when the same RGB file on server 
> ---
>
> Key: TC-169
> URL: https://issues.apache.org/jira/browse/TC-169
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Router
>Affects Versions: 1.7.0
>Reporter: Zhilin Huang
>Assignee: Zhilin Huang
>  Labels: rgb
>
> If the RGB file on server is: 
> 1. completely the same with the RGB file on TR
> 2. last modified time is later than the RGB file on TR
> TR will download the RGB file from server at every polling interval. 
> Expected behavior is that TR should not download the RGB file any longer when 
> the RGB file on server has been downloaded to TR and it was unmodified since 
> then.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #567: API GW phase 0 (replaces #551, depends ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/24/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #159: Should use "dest_ip" instead of "dest_d...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/33/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #315: [TC-169] update last modified time if f...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/28/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #643: Initial commit for Simple Session Track...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/21/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-519) TP - tenants menu item mistakenly removed from TP

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/4/



> TP - tenants menu item mistakenly removed from TP
> -
>
> Key: TC-519
> URL: https://issues.apache.org/jira/browse/TC-519
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
> Fix For: 2.1.0
>
>
> Somehow the tenants menu was mistakenly removed from TP.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-192) Java TM and Go TM get build with exact same RPM Name

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/731
  
Can one of the admins verify this patch?


> Java TM and Go TM get build with exact same RPM Name
> 
>
> Key: TC-192
> URL: https://issues.apache.org/jira/browse/TC-192
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Monitor, Traffic Monitor (golang)
>Affects Versions: 2.1.0, 2.0.0
>Reporter: David Neuman
>  Labels: build, gotm, javatm
>
> When building Traffic Control, goTM and javaTM get build with the exact same 
> rpm name.  This means that if you are building all projects you only get one 
> TM RPM and its whichever one built last.  The names should be updated so that 
> they are not the same.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #738: make delivery service `MultiSiteOrigin`...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/16/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-262) Merge https://github.com/apache/incubator-trafficcontrol/pull/497 into next release

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/27/



> Merge https://github.com/apache/incubator-trafficcontrol/pull/497 into next 
> release
> ---
>
> Key: TC-262
> URL: https://issues.apache.org/jira/browse/TC-262
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops
>Reporter: John Schmerge
>Priority: Minor
>
> This patch adds three new parameters to control/configure the seed
> strings for the consistent hash used for cachekey->drive mapping in
> ATS... This allows an arbitrary string to be assigned as the key for
> drives instead of relying on the OS's device node name as the seed for
> the hash. The three parameters added are:
> Drive_Hash_Id
> RAM_Drive_Hash_Id
> SSD_Drive_Hash_Id
> And they specify the id keys for spinning, ram, and ssd devices.
> If this parameter is missing from the TO config for a server, the
> generated file ommits any specification of the id parameter (preserving
> the previous file generation behavior).
> Also note that the csv id strings for these three new parameters should
> order their entries to match the order of the Drive_Letters parameter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #621: Enhanced IPV6 handling in astats

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/22/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-373) Traffic Stats Has Connection Leak

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/20/



> Traffic Stats Has Connection Leak 
> --
>
> Key: TC-373
> URL: https://issues.apache.org/jira/browse/TC-373
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Stats
>Reporter: Zhilin Huang
>Assignee: Zhilin Huang
>  Labels: connections
>
> Happens when TO not response 200 OK to traffic stats:
> [ERROR] 2017-06-08 09:54:40 500 Internal Server Error[500] - Error requesting 
> Traffic Ops https://coffee-ops-a.coffee.com/api/1.2/stats_summary/create
> $ sudo netstat -tunp|grep traffic_stats|head 
> tcp   32  0 10.63.115.225:39667 10.63.115.224:443   
> CLOSE_WAIT  795/traffic_stats   
> tcp   32  0 10.63.115.225:50388 10.63.115.224:443   
> CLOSE_WAIT  795/traffic_stats   
> tcp   32  0 10.63.115.225:46896 10.63.115.224:443   
> CLOSE_WAIT  795/traffic_stats   
> tcp   32  0 10.63.115.225:38896 10.63.115.224:443   
> CLOSE_WAIT  795/traffic_stats   
> tcp1  0 10.63.115.225:53682 10.63.115.224:443   
> CLOSE_WAIT  795/traffic_stats   
> tcp   32  0 10.63.115.225:42324 10.63.115.224:443   
> CLOSE_WAIT  795/traffic_stats   
> tcp   32  0 10.63.115.225:39618 10.63.115.224:443   
> CLOSE_WAIT  795/traffic_stats   
> tcp   32  0 10.63.115.225:36613 10.63.115.224:443   
> CLOSE_WAIT  795/traffic_stats   
> tcp   32  0 10.63.115.225:51851 10.63.115.224:443   
> CLOSE_WAIT  795/traffic_stats   
> tcp   32  0 10.63.115.225:52842 10.63.115.224:443   
> CLOSE_WAIT  795/traffic_stats 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #497: [TC-262] Allow specification of the 'id...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/27/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #502: Add Multiple custom access logs and Hea...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/26/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #780: Traffic Ops Golang cacheconfig

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/11/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #527: modify storage.config to match PR 497

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/25/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #617: Updates and bugfixes for ToDSCPCheck.pl

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/23/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #695: TrafficMonitor IPV6 improvements

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/18/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #660: [TC-373] fix traffic stats connection l...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/20/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #801: Add Traffic Ops Golang Endpoint Convers...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/8/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #736: [WIP] Anonymous IP TR Implementation

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/17/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #814: [BACKPORT] [TC-519] - adds back missing...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/4/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #819: Modified the default config to reflect ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-traffic_ops-test-PR/38/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (TC-518) ToCDUCheck and ToCHRCheck: Value formatted as float instead of int

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/7/



> ToCDUCheck and ToCHRCheck: Value formatted as float instead of int
> --
>
> Key: TC-518
> URL: https://issues.apache.org/jira/browse/TC-518
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0, 2.0.0, 2.2.0
>Reporter: Steve Malenfant
>Priority: Trivial
> Fix For: 2.2.0
>
>
> CDU check return value are formatted as a float while the database values 
> were stored as int (mysql) and bigint (postgresql).
> This check fails against 2.0+



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-353) Can't use CNAME hostname with "ccr" prefix

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/5/



> Can't use CNAME hostname with "ccr" prefix
> --
>
> Key: TC-353
> URL: https://issues.apache.org/jira/browse/TC-353
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.1.0, 2.0.0, 1.8.0
>Reporter: Steve Malenfant
>Priority: Minor
>  Labels: cname, configuration, host_regex
>
> If you put a HOST_REGEX of "ccr.example.kabletown.net", it will expand to the 
> server hostname like "edge01.example.kabletown.net". This makes the 
> remap.config to have the wrong hostname. This might not affect anything but 
> it should be changed to something unrelated to a specific prefix.
> The code ConfigFile.pm is causing the current behavior :
> {code}
>   my $hname = $ds_type =~ /^DNS/ ? "edge" : "ccr";
>   my $portstr = "";
> ...
>   $map_from =~ s/ccr/$host_name/;
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-336) Add ability to copy url_sig keys from one DS to another GH #1540

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/9/



> Add ability to copy url_sig keys from one DS to another GH #1540
> 
>
> Key: TC-336
> URL: https://issues.apache.org/jira/browse/TC-336
> Project: Traffic Control
>  Issue Type: Improvement
>  Components: Traffic Ops, Traffic Vault
>Reporter: Dewayne Richardson
>Assignee: Dylan Volz
>Priority: Minor
>  Labels: keys, url_signing
>
> There are some cases where we want to use the same URL sig keys for multiple 
> delivery services. Currently this is handled by using cURL and other manual 
> processes. Traffic Ops should support the ability to copy url sig keys from 
> one DS to another. When this happens Traffic Ops should also create the 
> necessary parameters for the target DS so that URL signing works.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] incubator-trafficcontrol issue #746: Add TenantID field to delivery service ...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/15/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-trafficcontrol issue #772: Fix Traffic Monitor to startup when cac...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 

https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/12/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---