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

2017-06-27 Thread ASF GitHub Bot (JIRA) 

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

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

Github user asfgit closed the pull request at:

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


> 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
>  Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Nir Sopher
> Fix For: 2.1.0
>
>
> "Create" user API was recently added to TO. 
> Additionally, TO password hashing was changed to scrypt.
> The merge between the 2 changes left the "create" command with the old "sha1" 
> calls.



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

[GitHub] incubator-trafficcontrol pull request #691: [TC-398] "create user" API - mov...

2017-06-27 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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-64) Experimental SPA application

2017-06-27 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on TC-64:
--

Github user asfgit closed the pull request at:

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


> 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)

[GitHub] incubator-trafficcontrol pull request #703: [TC-64] - new TO UI is to be nam...

2017-06-27 Thread asfgit 
Github user asfgit closed the pull request at:

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


---
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-64) Experimental SPA application

2017-06-27 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on TC-64:
--

Github user mitchell852 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/703
  
Per this email thread - 
https://lists.apache.org/thread.html/b24a6a6807a50c52d6c9e82e4a3e00f78a56179e57cfadf21fc1711a@%3Cusers.trafficcontrol.apache.org%3E


> 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)

[GitHub] incubator-trafficcontrol issue #703: [TC-64] - new TO UI is to be named traf...

2017-06-27 Thread mitchell852 
Github user mitchell852 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/703
  
Per this email thread - 
https://lists.apache.org/thread.html/b24a6a6807a50c52d6c9e82e4a3e00f78a56179e57cfadf21fc1711a@%3Cusers.trafficcontrol.apache.org%3E


---
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-64) Experimental SPA application

2017-06-27 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on TC-64:
--

GitHub user mitchell852 opened a pull request:

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

[TC-64] - new TO UI is to be named traffic portal



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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
rename-to-tp

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

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


commit 2be369d80b6473920afc6a1a1102e6c5f3ddb687
Author: Jeremy Mitchell 
Date:   2017-06-27T20:38:24Z

new TO UI is to be named traffic portal




> 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] [Assigned] (TC-393) Traffic Ops API Gateway

2017-06-27 Thread Ryan Durfey (JIRA) 

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

Ryan Durfey reassigned TC-393:
--

Assignee: Nir Sopher

> Traffic Ops API Gateway
> ---
>
> Key: TC-393
> URL: https://issues.apache.org/jira/browse/TC-393
> Project: Traffic Control
>  Issue Type: New Feature
>  Components: Traffic Ops API
>Affects Versions: 2.1.0
>Reporter: Ryan Durfey
>Assignee: Nir Sopher
>Priority: Critical
>
> Build API gateway for Traffic Ops
> See: https://cwiki.apache.org/confluence/display/TC/API+Gateway
> See: 
> https://lists.apache.org/thread.html/e7aa72c73177a25a6a834ebca268c9ac973f547ce77d5331e7f84ee0@%3Cdev.trafficcontrol.apache.org%3E
> See https://github.com/apache/incubator-trafficcontrol/pull/567



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

[jira] [Closed] (TC-401) Traffic Router Serves OFFLINE Caches

2017-06-27 Thread Jeff Elsloo (JIRA) 

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

Jeff Elsloo closed TC-401.
--
Assignee: Jeff Elsloo

> Traffic Router Serves OFFLINE Caches
> 
>
> Key: TC-401
> URL: https://issues.apache.org/jira/browse/TC-401
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Router
>Affects Versions: 2.0.0
>Reporter: Jeff Elsloo
>Assignee: Jeff Elsloo
> Fix For: 2.1.0
>
>
> We identified an issue that causes Traffic Router to serve up an {{OFFLINE}} 
> cache indefinitely after a snapshot of the CRConfig. This bug will also do 
> the inverse, where a cache that was previously set to {{OFFLINE}} will never 
> have traffic routed to it when set back to {{ONLINE}} or {{REPORTED}} 
> (referenced only as {{ONLINE}} henceforth).
> The bug is caused by {{ConfigHandler.processConfig()}} clearing the cache 
> locations from the {{NetworkNode}} prior to swapping out the instance of 
> {{CacheRegister}}. When the cache locations have been cleared, but the prior 
> {{CacheRegister}} is still in place, a race condition can occur where the 
> {{CacheLocation}} for a given cache group from the prior config will be set 
> on the recently cleared {{NetworkNode}}. When this happens, the 
> {{List}} contains the prior config's list for that cache group, which 
> means that any host state change from/to {{ONLINE}} or {{OFFLINE}} will not 
> be reflected. This is because when transitioning to {{OFFLINE}} the {{Cache}} 
> drops from the CRConfig and it will reappear when set to {{ONLINE}}. Contrast 
> this with {{ONLINE}} to {{ADMIN_DOWN}}, the {{Cache}} remains in the 
> CRConfig, so we are simply using the status to determine whether the cache is 
> available and the software works as designed.
> This is due to the way we use lazy loading to associate network ranges within 
> the CZF with {{CacheLocations}} within a given {{NetworkNode}} representing 
> that section of the CZF. In {{TrafficRouter}}, during cache selection, if we 
> have a hit in the coverage zone file but the {{CacheLocation}} is 
> uninitialized, we obtain the {{CacheLocation}} from {{CacheRegister}} and set 
> it for that specific {{NetworkNode}}. If our {{NetworkNode}} is cleared but 
> our {{CacheRegister}} has yet to be swapped, we will set the {{NetworkNode}} 
> to the old {{CacheLocation}} and as mentioned, which will have a reference to 
> the prior {{List}}, denying anyone the opportunity to populate that 
> {{NetworkNode}} with the new {{CacheLocation}} and new {{List}}.



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

[jira] [Commented] (TC-401) Traffic Router Serves OFFLINE Caches

2017-06-27 Thread ASF GitHub Bot (JIRA) 

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

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

Github user asfgit closed the pull request at:

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


> Traffic Router Serves OFFLINE Caches
> 
>
> Key: TC-401
> URL: https://issues.apache.org/jira/browse/TC-401
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Router
>Affects Versions: 2.0.0
>Reporter: Jeff Elsloo
> Fix For: 2.1.0
>
>
> We identified an issue that causes Traffic Router to serve up an {{OFFLINE}} 
> cache indefinitely after a snapshot of the CRConfig. This bug will also do 
> the inverse, where a cache that was previously set to {{OFFLINE}} will never 
> have traffic routed to it when set back to {{ONLINE}} or {{REPORTED}} 
> (referenced only as {{ONLINE}} henceforth).
> The bug is caused by {{ConfigHandler.processConfig()}} clearing the cache 
> locations from the {{NetworkNode}} prior to swapping out the instance of 
> {{CacheRegister}}. When the cache locations have been cleared, but the prior 
> {{CacheRegister}} is still in place, a race condition can occur where the 
> {{CacheLocation}} for a given cache group from the prior config will be set 
> on the recently cleared {{NetworkNode}}. When this happens, the 
> {{List}} contains the prior config's list for that cache group, which 
> means that any host state change from/to {{ONLINE}} or {{OFFLINE}} will not 
> be reflected. This is because when transitioning to {{OFFLINE}} the {{Cache}} 
> drops from the CRConfig and it will reappear when set to {{ONLINE}}. Contrast 
> this with {{ONLINE}} to {{ADMIN_DOWN}}, the {{Cache}} remains in the 
> CRConfig, so we are simply using the status to determine whether the cache is 
> available and the software works as designed.
> This is due to the way we use lazy loading to associate network ranges within 
> the CZF with {{CacheLocations}} within a given {{NetworkNode}} representing 
> that section of the CZF. In {{TrafficRouter}}, during cache selection, if we 
> have a hit in the coverage zone file but the {{CacheLocation}} is 
> uninitialized, we obtain the {{CacheLocation}} from {{CacheRegister}} and set 
> it for that specific {{NetworkNode}}. If our {{NetworkNode}} is cleared but 
> our {{CacheRegister}} has yet to be swapped, we will set the {{NetworkNode}} 
> to the old {{CacheLocation}} and as mentioned, which will have a reference to 
> the prior {{List}}, denying anyone the opportunity to populate that 
> {{NetworkNode}} with the new {{CacheLocation}} and new {{List}}.



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

[GitHub] incubator-trafficcontrol pull request #702: [TC-401] Fixes a race condition ...

2017-06-27 Thread asfgit 
Github user asfgit closed the pull request at:

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


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