[jira] (TC-104) httpsPort key is missing in the CRConfig contentRouters section for 1.8

Title: Message Title Nir Sopher commented on TC-104

[jira] [Created] (TC-121) Parametrized traffic-server configuration

Nir Sopher created TC-121: - Summary: Parametrized traffic-server configuration Key: TC-121 URL: https://issues.apache.org/jira/browse/TC-121 Project: Traffic Control Issue Type: Improvement

[jira] [Commented] (TC-217) Self Service - CRUD Sub Tenant

[ https://issues.apache.org/jira/browse/TC-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944602#comment-15944602 ] Nir Sopher commented on TC-217: --- Hi, Please let me know if the below satisfy you need: Adding an api whose

[jira] [Commented] (TC-215) SSL Automate Standard Cert Generation and Application

[ https://issues.apache.org/jira/browse/TC-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15944597#comment-15944597 ] Nir Sopher commented on TC-215: --- Please note that the solution proposed in TC-55 practically allows you to use

[jira] [Commented] (TC-184) Tenant Hierarchy

[ https://issues.apache.org/jira/browse/TC-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15926224#comment-15926224 ] Nir Sopher commented on TC-184: --- Hi Ryan, I'm currently working on a PR focusing on items 1-4 of the JIRA

[jira] [Comment Edited] (TC-217) Self Service - CRUD Sub Tenant

[ https://issues.apache.org/jira/browse/TC-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954994#comment-15954994 ] Nir Sopher edited comment on TC-217 at 4/5/17 8:59 AM: --- Further thinking of the issue I

[jira] [Comment Edited] (TC-217) Self Service - CRUD Sub Tenant

[ https://issues.apache.org/jira/browse/TC-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954994#comment-15954994 ] Nir Sopher edited comment on TC-217 at 4/5/17 8:57 AM: --- Further thinking of the issue I

[jira] [Commented] (TC-217) Self Service - CRUD Sub Tenant

[ https://issues.apache.org/jira/browse/TC-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15955009#comment-15955009 ] Nir Sopher commented on TC-217: --- Ryan, Per your comment, please see my comments and edits to

[jira] [Commented] (TC-217) Self Service - CRUD Sub Tenant

[ https://issues.apache.org/jira/browse/TC-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15954994#comment-15954994 ] Nir Sopher commented on TC-217: --- Further thinking of the issue I would like to revise the earlier suggestion I

[jira] [Comment Edited] (TC-217) Self Service - CRUD Sub Tenant

[ https://issues.apache.org/jira/browse/TC-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972417#comment-15972417 ] Nir Sopher edited comment on TC-217 at 4/18/17 12:42 PM: - Hi, I believe we need to

[jira] [Commented] (TC-217) Self Service - CRUD Sub Tenant

[ https://issues.apache.org/jira/browse/TC-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15972417#comment-15972417 ] Nir Sopher commented on TC-217: --- Hi, I believe we need to distinguish between the 2 terminologies:

[jira] [Created] (TC-525) Cannot snapshot CrConfig when no mid server exists

Nir Sopher created TC-525: - Summary: Cannot snapshot CrConfig when no mid server exists Key: TC-525 URL: https://issues.apache.org/jira/browse/TC-525 Project: Traffic Control Issue Type: Improvement

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

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:

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

Nir Sopher created TC-527: - Summary: Traffic_Router Default Profile - Uses unsupported pattern (${toHostname}) Key: TC-527 URL: https://issues.apache.org/jira/browse/TC-527 Project: Traffic Control

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

[ 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

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

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

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

[ 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

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

[ 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

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

[ 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

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

[ 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.

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

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

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

Nir Sopher created TC-528: - Summary: 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

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

[ 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

[jira] [Commented] (TC-384) Profiles exported from TC1.7 cannot be imported to TC 2.1

[ https://issues.apache.org/jira/browse/TC-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16128655#comment-16128655 ] Nir Sopher commented on TC-384: --- Waiting for 2.2 will make it irrelevant. I think it can be dismissed. If

[jira] [Updated] (TC-384) Profiles exported from TC1.7 cannot be imported to TC 2.1

[ https://issues.apache.org/jira/browse/TC-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher updated TC-384: -- Issue Type: Improvement (was: Bug) > Profiles exported from TC1.7 cannot be imported to TC 2.1 >

[jira] [Updated] (TC-501) TPv2 installation - better defaults are required

[ https://issues.apache.org/jira/browse/TC-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher updated TC-501: -- Issue Type: Improvement (was: Bug) > TPv2 installation - better defaults are required >

[jira] [Created] (TC-508) Import Profile may create parameters duplications

Nir Sopher created TC-508: - Summary: Import Profile may create parameters duplications Key: TC-508 URL: https://issues.apache.org/jira/browse/TC-508 Project: Traffic Control Issue Type: Bug

[jira] [Closed] (TC-508) Import Profile may create parameters duplications

[ https://issues.apache.org/jira/browse/TC-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher closed TC-508. - Resolution: Invalid Jeremy is correct. I was probably confused due to the appearance of the same variable twice in

[jira] [Created] (TC-428) Tenancy based access control - Delivery Service API

Nir Sopher created TC-428: - Summary: Tenancy based access control - Delivery Service API Key: TC-428 URL: https://issues.apache.org/jira/browse/TC-428 Project: Traffic Control Issue Type:

[jira] [Created] (TC-462) Delivery-service tenancy based access control - Regexes

Nir Sopher created TC-462: - Summary: Delivery-service tenancy based access control - Regexes Key: TC-462 URL: https://issues.apache.org/jira/browse/TC-462 Project: Traffic Control Issue Type:

[jira] [Updated] (TC-469) User tenancy based access control - log

[ https://issues.apache.org/jira/browse/TC-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher updated TC-469: -- Description: We have recently added "tenancy" to the project. With tenancy, every resource have a tenant, where

[jira] [Created] (TC-460) Delivery-service tenancy based access control - DS/Server Assignment

Nir Sopher created TC-460: - Summary: Delivery-service tenancy based access control - DS/Server Assignment Key: TC-460 URL: https://issues.apache.org/jira/browse/TC-460 Project: Traffic Control

[jira] [Created] (TC-463) Delivery-service tenancy based access control - DS/User Assignment

Nir Sopher created TC-463: - Summary: Delivery-service tenancy based access control - DS/User Assignment Key: TC-463 URL: https://issues.apache.org/jira/browse/TC-463 Project: Traffic Control Issue

[jira] [Created] (TC-469) User tenancy based access control - log

Nir Sopher created TC-469: - Summary: User tenancy based access control - log Key: TC-469 URL: https://issues.apache.org/jira/browse/TC-469 Project: Traffic Control Issue Type: Improvement

[jira] [Updated] (TC-466) Delivery-service tenancy based access control - statidnsentry

[ https://issues.apache.org/jira/browse/TC-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher updated TC-466: -- Description: We have recently added "tenancy" to the project. With tenancy, every resource have a tenant, where

[jira] [Updated] (TC-464) Delivery-service tenancy based access control - Federation

[ https://issues.apache.org/jira/browse/TC-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher updated TC-464: -- Description: We have recently added "tenancy" to the project. With tenancy, every resource have a tenant, where

[jira] [Created] (TC-466) Delivery-service tenancy based access control - statidnsentry

Nir Sopher created TC-466: - Summary: Delivery-service tenancy based access control - statidnsentry Key: TC-466 URL: https://issues.apache.org/jira/browse/TC-466 Project: Traffic Control Issue Type:

[jira] [Created] (TC-464) Delivery-service tenancy based access control - Federation

Nir Sopher created TC-464: - Summary: Delivery-service tenancy based access control - Federation Key: TC-464 URL: https://issues.apache.org/jira/browse/TC-464 Project: Traffic Control Issue Type:

[jira] [Updated] (TC-467) Delivery-service tenancy based access control - DNSSEC and SSL Keys

[ https://issues.apache.org/jira/browse/TC-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher updated TC-467: -- Description: We have recently added "tenancy" to the project. With tenancy, every resource have a tenant, where

[jira] [Updated] (TC-465) Delivery-service tenancy based access control - JOBs

[ https://issues.apache.org/jira/browse/TC-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher updated TC-465: -- Description: We have recently added "tenancy" to the project. With tenancy, every resource have a tenant, where

[jira] [Created] (TC-478) Parameter value cannot be set to "0" using the parameters crud API

Nir Sopher created TC-478: - Summary: Parameter value cannot be set to "0" using the parameters crud API Key: TC-478 URL: https://issues.apache.org/jira/browse/TC-478 Project: Traffic Control Issue

[jira] [Created] (TC-427) Tenancy Based Access Control - User Resource

Nir Sopher created TC-427: - Summary: Tenancy Based Access Control - User Resource Key: TC-427 URL: https://issues.apache.org/jira/browse/TC-427 Project: Traffic Control Issue Type: Improvement

[jira] [Commented] (TC-412) Currently when a delivery service encounters an error we currently don’t know how to find the owner to notify them of the outage or contact them to find cause of issue.

[ https://issues.apache.org/jira/browse/TC-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16076233#comment-16076233 ] Nir Sopher commented on TC-412: --- Hi William, Regarding the addition of owner to each DS. Are you going to use

[jira] [Created] (TC-485) Steering Target API - Redundent parameters

Nir Sopher created TC-485: - Summary: Steering Target API - Redundent parameters Key: TC-485 URL: https://issues.apache.org/jira/browse/TC-485 Project: Traffic Control Issue Type: Bug

[jira] [Created] (TC-501) TPv2 installation - better defaults are required

Nir Sopher created TC-501: - Summary: TPv2 installation - better defaults are required Key: TC-501 URL: https://issues.apache.org/jira/browse/TC-501 Project: Traffic Control Issue Type: Bug

[jira] [Resolved] (TC-427) Tenancy Based Access Control - User Resource

[ https://issues.apache.org/jira/browse/TC-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-427. --- Resolution: Fixed Fix Version/s: 2.1.0 > Tenancy Based Access Control - User Resource >

[jira] [Resolved] (TC-398) Create User API - Broken due to merge issue

[ https://issues.apache.org/jira/browse/TC-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-398. --- Resolution: Fixed > Create User API - Broken due to merge issue > --- > >

[jira] [Resolved] (TC-463) Delivery-service tenancy based access control - DS/User Assignment

[ https://issues.apache.org/jira/browse/TC-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-463. --- Resolution: Fixed Fix Version/s: 2.1.0 > Delivery-service tenancy based access control - DS/User

[jira] [Resolved] (TC-462) Delivery-service tenancy based access control - Regexes

[ https://issues.apache.org/jira/browse/TC-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-462. --- Resolution: Fixed Fix Version/s: 2.1.0 > Delivery-service tenancy based access control - Regexes >

[jira] [Resolved] (TC-461) Delivery-service tenancy based access control - Steering Target

[ https://issues.apache.org/jira/browse/TC-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-461. --- Resolution: Fixed Fix Version/s: 2.1.0 > Delivery-service tenancy based access control - Steering Target >

[jira] [Resolved] (TC-459) User default tenancy should be "none"

[ https://issues.apache.org/jira/browse/TC-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-459. --- Resolution: Fixed Fix Version/s: 2.1.0 > User default tenancy should be "none" >

[jira] [Resolved] (TC-428) Tenancy based access control - Delivery Service API

[ https://issues.apache.org/jira/browse/TC-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-428. --- Resolution: Fixed Fix Version/s: 2.1.0 > Tenancy based access control - Delivery Service API >

[jira] [Resolved] (TC-460) Delivery-service tenancy based access control - DS/Server Assignment

[ https://issues.apache.org/jira/browse/TC-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-460. --- Resolution: Fixed Fix Version/s: 2.1.0 > Delivery-service tenancy based access control - DS/Server

[jira] [Assigned] (TC-461) Delivery-service tenancy based access control - Steering Target

[ https://issues.apache.org/jira/browse/TC-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher reassigned TC-461: - Assignee: Nir Sopher > Delivery-service tenancy based access control - Steering Target >

[jira] [Assigned] (TC-462) Delivery-service tenancy based access control - Regexes

[ https://issues.apache.org/jira/browse/TC-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher reassigned TC-462: - Assignee: Nir Sopher > Delivery-service tenancy based access control - Regexes >

[jira] [Assigned] (TC-463) Delivery-service tenancy based access control - DS/User Assignment

[ https://issues.apache.org/jira/browse/TC-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher reassigned TC-463: - Assignee: Nir Sopher > Delivery-service tenancy based access control - DS/User Assignment >

[jira] [Assigned] (TC-471) Delivery-service tenancy based access control - ignore-tenancy parameter change

[ https://issues.apache.org/jira/browse/TC-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher reassigned TC-471: - Assignee: Nir Sopher > Delivery-service tenancy based access control - ignore-tenancy parameter > change >

[jira] [Resolved] (TC-471) Delivery-service tenancy based access control - ignore-tenancy parameter change

[ https://issues.apache.org/jira/browse/TC-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-471. --- Resolution: Fixed Fix Version/s: 2.1.0 > Delivery-service tenancy based access control - ignore-tenancy

[jira] [Resolved] (TC-485) Steering Target API - Redundent parameters

[ https://issues.apache.org/jira/browse/TC-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-485. --- Resolution: Fixed Fix Version/s: 2.1.0 > Steering Target API - Redundent parameters >

[jira] [Resolved] (TC-478) Parameter value cannot be set to "0" using the parameters crud API

[ https://issues.apache.org/jira/browse/TC-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-478. --- Resolution: Fixed Fix Version/s: 2.1.0 > Parameter value cannot be set to "0" using the parameters crud

[jira] [Created] (TC-317) ORT syncds bug

Nir Sopher created TC-317: - Summary: ORT syncds bug Key: TC-317 URL: https://issues.apache.org/jira/browse/TC-317 Project: Traffic Control Issue Type: Bug Reporter: Nir Sopher Based

[jira] [Created] (TC-304) Ping each Riak server

Nir Sopher created TC-304: - Summary: Ping each Riak server Key: TC-304 URL: https://issues.apache.org/jira/browse/TC-304 Project: Traffic Control Issue Type: Improvement Components:

[jira] [Created] (TC-299) TO Change Log. Expand status to human readable string

Nir Sopher created TC-299: - Summary: TO Change Log. Expand status to human readable string Key: TC-299 URL: https://issues.apache.org/jira/browse/TC-299 Project: Traffic Control Issue Type:

[jira] [Created] (TC-332) Heatlh tab never loads if there are no traffic monitors

Nir Sopher created TC-332: - Summary: Heatlh tab never loads if there are no traffic monitors Key: TC-332 URL: https://issues.apache.org/jira/browse/TC-332 Project: Traffic Control Issue Type: Bug

[jira] [Updated] (TC-384) Profiles exported from TC1.7 cannot be imported to TC 2.1

[ https://issues.apache.org/jira/browse/TC-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher updated TC-384: -- Description: Due to a missing "profile-type" in the 1.7 json, the profiles cannot be imported. was: Do to a

[jira] [Created] (TC-398) Create User API - Broken due to merge issue

Nir Sopher created TC-398: - Summary: Create User API - Broken due to merge issue Key: TC-398 URL: https://issues.apache.org/jira/browse/TC-398 Project: Traffic Control Issue Type: Bug

[jira] [Commented] (TC-550) TO API - fetch deliveryservices for a user should have tenancy hooked in

[ https://issues.apache.org/jira/browse/TC-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139010#comment-16139010 ] Nir Sopher commented on TC-550: --- What is the purpose of this endpoint? When writing the code I considered it as

[jira] [Resolved] (TC-535) DS URL sig key apis needs to have tenancy check in place

[ https://issues.apache.org/jira/browse/TC-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nir Sopher resolved TC-535. --- Resolution: Fixed > DS URL sig key apis needs to have tenancy check in place >

[jira] [Comment Edited] (TC-384) Profiles exported from TC1.7 cannot be imported to TC 2.1

[ https://issues.apache.org/jira/browse/TC-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130943#comment-16130943 ] Nir Sopher edited comment on TC-384 at 8/17/17 6:16 PM: The "type" should added to the

[jira] [Commented] (TC-384) Profiles exported from TC1.7 cannot be imported to TC 2.1

[ https://issues.apache.org/jira/browse/TC-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130943#comment-16130943 ] Nir Sopher commented on TC-384: --- The "type" should added to the "profile" dictionary in the profile json. For