[GitHub] incubator-trafficcontrol pull request #595: add missing Apache licenses

[dangogh]

GitHub user dangogh opened a pull request:

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

add missing Apache licenses



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

$ git pull https://github.com/dangogh/incubator-trafficcontrol fix/license

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

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


commit 882fc986b76ee90c3a201d5a325c19eca33dc210
Author: Dan Kirkwood 
Date:   2017-05-19T22:54:39Z

license fixes to be backported to 2.0.x

commit f7619d8ed4750e729bcc17628c34e09cbf2e6e7a
Author: Dan Kirkwood 
Date:   2017-05-19T23:33:26Z

add missing license statements

commit 0df9bb8e2cbfa935c816907bc98389aa19e9d564
Author: Dan Kirkwood 
Date:   2017-05-20T01:07:58Z

add license to Dockerfiles

commit 0a21bb6d160aee98292be318a237261258a9c4d1
Author: Dan Kirkwood 
Date:   2017-05-20T03:42:59Z

add license to sql file




---
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 #594: [Backport TC-345] source tarball...

[dangogh]

GitHub user dangogh opened a pull request:

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

[Backport TC-345] source tarball has invalid link

(cherry picked from commit ebfae5038a66a3124a329c9f11c51c705b083dd0)

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

$ git pull https://github.com/dangogh/incubator-trafficcontrol 
fix/2.0-tarball

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

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


commit 83c3fbb7aff62b15eb356b06db0843c0a32c0807
Author: Dan Kirkwood 
Date:   2017-05-19T19:54:33Z

redo --transform on tar to fix symlink issue

(cherry picked from commit ebfae5038a66a3124a329c9f11c51c705b083dd0)




---
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-344) TO API - ds of type ANY_MAP, STEERING or CLIENT_STEERING does not require an orgServerFqdn

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> TO API - ds of type ANY_MAP, STEERING or CLIENT_STEERING does not require an 
> orgServerFqdn
> --
>
> Key: TC-344
> URL: https://issues.apache.org/jira/browse/TC-344
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> In the TO API, the create delivery service endpoint does the following 
> validations:
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/API/Deliveryservice.pm#L1024
> orgServerFqdn is not required if type = ANY_MAP, STEERING OR CLIENT_STEERING



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (TC-345) source tarball has invalid link

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> source tarball has invalid link
> ---
>
> Key: TC-345
> URL: https://issues.apache.org/jira/browse/TC-345
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Release
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
>Priority: Blocker
>  Labels: easyfix
> Fix For: 2.0.0, 2.1.0
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> There's a symlink in the repo: 
> traffic_stats/vendor/github.com/apache/incubator-trafficcontrol/traffic_ops/client
>  -> ../../../../../../traffic_ops/client
> When the tarball is created,  it uses tar's `--transform` option which breaks 
> that symlink.   Fix is trivial,  but needs to be backported to 2.0.x because 
> it will break anyone trying to build traffic_stats from the tarball.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #593: [TC-345] fix tarball constructio...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-345) source tarball has invalid link

[ASF GitHub Bot (JIRA)]

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

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

GitHub user dangogh opened a pull request:

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

[TC-345] fix tarball construction issue with symlinks



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

$ git pull https://github.com/dangogh/incubator-trafficcontrol 
fix/tarball-link

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

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


commit 2a8f3b2d7b9074c3fdad2c020ed62c4ceb7e8f74
Author: Dan Kirkwood 
Date:   2017-05-19T19:54:33Z

redo --transform on tar to fix symlink issue




> source tarball has invalid link
> ---
>
> Key: TC-345
> URL: https://issues.apache.org/jira/browse/TC-345
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Release
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
>Priority: Blocker
>  Labels: easyfix
> Fix For: 2.0.0, 2.1.0
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> There's a symlink in the repo: 
> traffic_stats/vendor/github.com/apache/incubator-trafficcontrol/traffic_ops/client
>  -> ../../../../../../traffic_ops/client
> When the tarball is created,  it uses tar's `--transform` option which breaks 
> that symlink.   Fix is trivial,  but needs to be backported to 2.0.x because 
> it will break anyone trying to build traffic_stats from the tarball.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #593: [TC-345] fix tarball constructio...

[dangogh]

GitHub user dangogh opened a pull request:

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

[TC-345] fix tarball construction issue with symlinks



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

$ git pull https://github.com/dangogh/incubator-trafficcontrol 
fix/tarball-link

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

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


commit 2a8f3b2d7b9074c3fdad2c020ed62c4ceb7e8f74
Author: Dan Kirkwood 
Date:   2017-05-19T19:54:33Z

redo --transform on tar to fix symlink issue




---
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 #592: updated documentation for traffi...

[dneuman64]

GitHub user dneuman64 opened a pull request:

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

updated documentation for traffic_stats



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

$ git pull https://github.com/dneuman64/incubator-trafficcontrol 
update-ts-docs-21

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

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


commit 2f5445ce0d717544a4d0f38dbe00dd265311cf0e
Author: David Neuman 
Date:   2017-05-19T19:44:35Z

updated documentation for traffic_stats




---
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 #530: [Backport TC-150] 2.0 document c...

[dangogh]

Github user dangogh closed the pull request at:

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


---
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 #531: [Backport] remove KEYS -- stored...

[dangogh]

Github user dangogh closed the pull request at:

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


---
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-150) generateCert script not echoing prompts from openssl

[ASF GitHub Bot (JIRA)]

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

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

Github user dangogh closed the pull request at:

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


> generateCert script not echoing prompts from openssl
> 
>
> Key: TC-150
> URL: https://issues.apache.org/jira/browse/TC-150
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0, 2.1.0
> Environment: New install on Centos 7
>Reporter: Dan Kirkwood
>Priority: Minor
> Fix For: 2.0.0, 2.1.0
>
>
> using the script to generate certs,  the initial prompts are shown,  but when 
> it gets to asking for city, state, organization, etc,  the prompt isn't shown 
> and appears to hang.  Hit  9 times, and it shows the next prompt 
> after that portion..
> This should be trivial to fix...Script is 
> traffic_ops/install/bin/generateCert



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #532: [Backport TC-167] 2.0.x fix cach...

[dangogh]

Github user dangogh closed the pull request at:

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


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

Jenkins build is back to normal : incubator-trafficcontrol-master-build #13

[Apache Jenkins Server]

See 

[jira] [Commented] (TC-64) TO experimental SPA application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TC-64:
--

Github user asfgit closed the pull request at:

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


> TO 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
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> 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.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #589: [TC-64] - To experimental - allo...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-345) source tarball has invalid link

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

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


> source tarball has invalid link
> ---
>
> Key: TC-345
> URL: https://issues.apache.org/jira/browse/TC-345
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Release
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
>Priority: Blocker
>  Labels: easyfix
> Fix For: 2.0.0, 2.1.0
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> There's a symlink in the repo: 
> traffic_stats/vendor/github.com/apache/incubator-trafficcontrol/traffic_ops/client
>  -> ../../../../../../traffic_ops/client
> When the tarball is created,  it uses tar's `--transform` option which breaks 
> that symlink.   Fix is trivial,  but needs to be backported to 2.0.x because 
> it will break anyone trying to build traffic_stats from the tarball.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #591: [TC-345] when creating tarball, ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #591: [TC-345] when creating tarball, do not ...

[dangogh]

Github user dangogh commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/591
  
to test,  build the tarball:
```
   $ docker-compose -f infrastructure/docker/build/docker-compose.yml run 
source
```
and extract the contents.  There is one symbolic link -- this is prior to 
the fix:
```
   $ tar xf dist/trafficcontrol-2.1.tar.gz -C /tmp
   $ find /tmp/trafficcontrol-incubating-2.1.0 -type l -ls
... 
/tmp/trafficcontrol-incubating-2.1.0/traffic_stats/vendor/github.com/apache/incubator-trafficcontrol/traffic_ops/client
 -> trafficcontrol-incubating-2.1.0/../../../../../../traffic_ops/client
```
After applying the fix,   build the tarball again and extract contents 
again.   The link content 
(`trafficcontrol-incubating-2.1.0/../../../../../../traffic_ops/client`) should 
not have that leading directory name (should be 
`../../../../../../traffic_ops/client`)



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

Build failed in Jenkins: incubator-trafficcontrol-master-build #12

[Apache Jenkins Server]

See 


Changes:

[dangogh] adds different views for each ds type

--
[...truncated 35.14 KB...]
---> Package nodejs.x86_64 1:6.10.2-1.el7 will be installed
--> Processing Dependency: libuv >= 1:1.9.1 for package: 
1:nodejs-6.10.2-1.el7.x86_64
--> Processing Dependency: libuv.so.1()(64bit) for package: 
1:nodejs-6.10.2-1.el7.x86_64
--> Processing Dependency: libicuuc.so.50()(64bit) for package: 
1:nodejs-6.10.2-1.el7.x86_64
--> Processing Dependency: libicui18n.so.50()(64bit) for package: 
1:nodejs-6.10.2-1.el7.x86_64
--> Processing Dependency: libicudata.so.50()(64bit) for package: 
1:nodejs-6.10.2-1.el7.x86_64
---> Package npm.x86_64 1:3.10.10-1.6.10.2.1.el7 will be installed
---> Package ruby-devel.x86_64 0:2.0.0.648-29.el7 will be installed
--> Processing Dependency: ruby(x86-64) = 2.0.0.648-29.el7 for package: 
ruby-devel-2.0.0.648-29.el7.x86_64
--> Processing Dependency: libruby.so.2.0()(64bit) for package: 
ruby-devel-2.0.0.648-29.el7.x86_64
---> Package rubygems.noarch 0:2.0.14.1-29.el7 will be installed
--> Processing Dependency: rubygem(rdoc) >= 4.0.0 for package: 
rubygems-2.0.14.1-29.el7.noarch
--> Processing Dependency: rubygem(psych) >= 2.0.0 for package: 
rubygems-2.0.14.1-29.el7.noarch
--> Processing Dependency: rubygem(io-console) >= 0.4.2 for package: 
rubygems-2.0.14.1-29.el7.noarch
--> Running transaction check
---> Package cpp.x86_64 0:4.8.5-11.el7 will be installed
---> Package glibc-devel.x86_64 0:2.17-157.el7_3.1 will be installed
--> Processing Dependency: glibc-headers = 2.17-157.el7_3.1 for package: 
glibc-devel-2.17-157.el7_3.1.x86_64
--> Processing Dependency: glibc-headers for package: 
glibc-devel-2.17-157.el7_3.1.x86_64
---> Package libgomp.x86_64 0:4.8.5-11.el7 will be installed
---> Package libicu.x86_64 0:50.1.2-15.el7 will be installed
---> Package libmpc.x86_64 0:1.0.1-3.el7 will be installed
---> Package libuv.x86_64 1:1.10.2-1.el7 will be installed
---> Package mpfr.x86_64 0:3.1.1-4.el7 will be installed
---> Package ruby.x86_64 0:2.0.0.648-29.el7 will be installed
--> Processing Dependency: rubygem(bigdecimal) >= 1.2.0 for package: 
ruby-2.0.0.648-29.el7.x86_64
---> Package ruby-libs.x86_64 0:2.0.0.648-29.el7 will be installed
---> Package rubygem-io-console.x86_64 0:0.4.2-29.el7 will be installed
---> Package rubygem-psych.x86_64 0:2.0.0-29.el7 will be installed
--> Processing Dependency: libyaml-0.so.2()(64bit) for package: 
rubygem-psych-2.0.0-29.el7.x86_64
---> Package rubygem-rdoc.noarch 0:4.0.0-29.el7 will be installed
--> Processing Dependency: ruby(irb) = 2.0.0.648 for package: 
rubygem-rdoc-4.0.0-29.el7.noarch
--> Processing Dependency: rubygem(json) >= 1.7.7 for package: 
rubygem-rdoc-4.0.0-29.el7.noarch
--> Running transaction check
---> Package glibc-headers.x86_64 0:2.17-157.el7_3.1 will be installed
--> Processing Dependency: kernel-headers >= 2.2.1 for package: 
glibc-headers-2.17-157.el7_3.1.x86_64
--> Processing Dependency: kernel-headers for package: 
glibc-headers-2.17-157.el7_3.1.x86_64
---> Package libyaml.x86_64 0:0.1.4-11.el7_0 will be installed
---> Package ruby-irb.noarch 0:2.0.0.648-29.el7 will be installed
---> Package rubygem-bigdecimal.x86_64 0:1.2.0-29.el7 will be installed
---> Package rubygem-json.x86_64 0:1.7.7-29.el7 will be installed
--> Running transaction check
---> Package kernel-headers.x86_64 0:3.10.0-514.16.1.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved


 Package   Arch  Version   Repository  Size

Installing:
 gcc   x86_644.8.5-11.el7  base16 M
 libffi-devel  x86_643.0.13-18.el7 base23 k
 make  x86_641:3.82-23.el7 base   420 k
 nodejsx86_641:6.10.2-1.el7epel   4.6 M
 npm   x86_641:3.10.10-1.6.10.2.1.el7  epel   2.5 M
 ruby-develx86_642.0.0.648-29.el7  base   128 k
 rubygems  noarch2.0.14.1-29.el7   base   216 k
Installing for dependencies:
 cpp   x86_644.8.5-11.el7  base   5.9 M
 glibc-devel   x86_642.17-157.el7_3.1  updates1.1 M
 glibc-headers x86_642.17-157.el7_3.1  updates668 k
 kernel-headersx86_643.10.0-514.16.1.el7   updates4.8 M
 libgomp   x86_644.8.5-11.el7  base   152 k
 libicux86_6450.1.2-15.el7 base   6.9 M
 libmpcx86_641.0.1-3.el7   base51 k
 libuv 

[jira] [Commented] (TC-64) TO experimental SPA application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TC-64:
--

Github user asfgit closed the pull request at:

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


> TO 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
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> 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.3.15#6346)

[GitHub] incubator-trafficcontrol pull request #586: [TC-64] - TO experimental - adds...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #550: adds timezone to last_seen_log b...

[mitchell852]

Github user mitchell852 closed the pull request at:

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


---
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-345) source tarball has invalid link

[ASF GitHub Bot (JIRA)]

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

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

GitHub user dangogh opened a pull request:

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

[TC-345] when creating tarball, do not transform symlinks



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

$ git pull https://github.com/dangogh/incubator-trafficcontrol 
fix/tarball-link

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

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


commit 99f5e005861dc85f05b04dba11e3398e4bf115ed
Author: Dan Kirkwood 
Date:   2017-05-19T18:20:41Z

when creating tarball, do not transform symlinks




> source tarball has invalid link
> ---
>
> Key: TC-345
> URL: https://issues.apache.org/jira/browse/TC-345
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Release
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Dan Kirkwood
>Assignee: Dan Kirkwood
>Priority: Blocker
>  Labels: easyfix
> Fix For: 2.0.0, 2.1.0
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> There's a symlink in the repo: 
> traffic_stats/vendor/github.com/apache/incubator-trafficcontrol/traffic_ops/client
>  -> ../../../../../../traffic_ops/client
> When the tarball is created,  it uses tar's `--transform` option which breaks 
> that symlink.   Fix is trivial,  but needs to be backported to 2.0.x because 
> it will break anyone trying to build traffic_stats from the tarball.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (TC-345) source tarball has invalid link

[Dan Kirkwood (JIRA)]

Dan Kirkwood created TC-345:
---

 Summary: source tarball has invalid link
 Key: TC-345
 URL: https://issues.apache.org/jira/browse/TC-345
 Project: Traffic Control
  Issue Type: Bug
  Components: Release
Affects Versions: 2.0.0, 2.1.0
Reporter: Dan Kirkwood
Assignee: Dan Kirkwood
Priority: Blocker
 Fix For: 2.0.0, 2.1.0


There's a symlink in the repo: 
traffic_stats/vendor/github.com/apache/incubator-trafficcontrol/traffic_ops/client
 -> ../../../../../../traffic_ops/client

When the tarball is created,  it uses tar's `--transform` option which breaks 
that symlink.   Fix is trivial,  but needs to be backported to 2.0.x because it 
will break anyone trying to build traffic_stats from the tarball.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TC-82:
--

Github user mitchell852 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/486
  
Here are the APIs being removed in this PR:

remove GET /api/$version/deliveryservices/list in favor of GET 
/api/$version/deliveryservices
remove GET /api/$version/deliveryservices/:id/get in favor of GET 
/api/$version/deliveryservices/:id
remove POST /api/$version/deliveryservices/create in favor of POST 
/api/$version/deliveryservices
remove PUT /api/$version/deliveryservices/:id/update in favor of PUT 
/api/$version/deliveryservices/:id
remove GET /api/$version/cachegroups/list in favor of GET 
/api/$version/cachegroups
remove POST /api/$version/cachegroups/create in favor of POST 
/api/$version/cachegroups
remove PUT /api/$version/cachegroups/:id/update in favor of PUT 
/api/$version/cachegroups/:id
remove DELETE /api/$version/cachegroups/:id/delete in favor of DELETE 
/api/$version/cachegroups/:id
remove POST /api/$version/servers/create in favor of POST 
/api/$version/servers
remove PUT /api/$version/servers/:id/update in favor of PUT 
/api/$version/servers/:id

This was also discussed in this email thread - 
https://lists.apache.org/thread.html/3ae4898e183fa4183a049eb3805836d236b32a2e7b068a8002317164@%3Cdev.trafficcontrol.apache.org%3E


> 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
>
> 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.3.15#6346)

[jira] [Commented] (TC-344) TO API - ds of type ANY_MAP, STEERING or CLIENT_STEERING does not require an orgServerFqdn

[ASF GitHub Bot (JIRA)]

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

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

GitHub user mitchell852 opened a pull request:

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

[TC-344] - orgserverfqdn is not required when ds type is ANY_MAP, STEERING 
OR CL…

…IENT_STEERING

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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-344-org-server-fqdn

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

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


commit 386b4bfd772083109902db4a2bd5325c1d62239b
Author: Jeremy Mitchell 
Date:   2017-05-19T17:30:26Z

orgserverfqdn is not required when ds type is ANY_MAP, STEERING OR 
CLIENT_STEERING




> TO API - ds of type ANY_MAP, STEERING or CLIENT_STEERING does not require an 
> orgServerFqdn
> --
>
> Key: TC-344
> URL: https://issues.apache.org/jira/browse/TC-344
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> In the TO API, the create delivery service endpoint does the following 
> validations:
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/API/Deliveryservice.pm#L1024
> orgServerFqdn is not required if type = ANY_MAP, STEERING OR CLIENT_STEERING



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (TC-344) TO API - ds of type ANY_MAP, STEERING or CLIENT_STEERING does not require an orgServerFqdn

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell updated TC-344:
---
Description: 
In the TO API, the create delivery service endpoint does the following 
validations:

https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/API/Deliveryservice.pm#L1024

orgServerFqdn is not required if type = ANY_MAP, STEERING OR CLIENT_STEERING

  was:
In the TO API, the create delivery service endpoint does the following 
validations:

https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/API/Deliveryservice.pm#L1024

orgServerFqdn is not required if type = ANY_MAP


> TO API - ds of type ANY_MAP, STEERING or CLIENT_STEERING does not require an 
> orgServerFqdn
> --
>
> Key: TC-344
> URL: https://issues.apache.org/jira/browse/TC-344
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> In the TO API, the create delivery service endpoint does the following 
> validations:
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/API/Deliveryservice.pm#L1024
> orgServerFqdn is not required if type = ANY_MAP, STEERING OR CLIENT_STEERING



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (TC-344) TO API - ds of type ANY_MAP, STEERING or CLIENT_STEERING does not require an orgServerFqdn

[Jeremy Mitchell (JIRA)]

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

Jeremy Mitchell updated TC-344:
---
Summary: TO API - ds of type ANY_MAP, STEERING or CLIENT_STEERING does not 
require an orgServerFqdn  (was: TO API - ds of type ANY_MAP does not require an 
orgServerFqdn)

> TO API - ds of type ANY_MAP, STEERING or CLIENT_STEERING does not require an 
> orgServerFqdn
> --
>
> Key: TC-344
> URL: https://issues.apache.org/jira/browse/TC-344
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> In the TO API, the create delivery service endpoint does the following 
> validations:
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/API/Deliveryservice.pm#L1024
> orgServerFqdn is not required if type = ANY_MAP



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[dneuman64]

Github user dneuman64 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/108
  
Hey @jifyang, the PR has conflicts, can you please rebase?



---
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 #30: Add --skip-ssl option to post install to...

[dneuman64]

Github user dneuman64 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/30
  
@limited I think this can be closed per @dangogh's comment above


---
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 #28: [WIP] Travis ci

[dneuman64]

Github user dneuman64 commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/28
  
I think this can be closed now that we have jenkins on apache infra?


---
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 #589: [TC-64] - To experimental - allo...

[mitchell852]

GitHub user mitchell852 opened a pull request:

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

[TC-64] - To experimental - allows user to assign/unassign params from 
profile or cachegroup



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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-64-link-param-to-profile

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

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


commit efa7708d87e12b06580a06851f1921e816f8e4b1
Author: Jeremy Mitchell 
Date:   2017-05-19T02:34:23Z

allows user to assign/unassign params from profile or cachegroup




---
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) TO experimental SPA application

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on TC-64:
--

GitHub user mitchell852 opened a pull request:

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

[TC-64] - To experimental - allows user to assign/unassign params from 
profile or cachegroup



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

$ git pull https://github.com/mitchell852/incubator-trafficcontrol 
tc-64-link-param-to-profile

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

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


commit efa7708d87e12b06580a06851f1921e816f8e4b1
Author: Jeremy Mitchell 
Date:   2017-05-19T02:34:23Z

allows user to assign/unassign params from profile or cachegroup




> TO 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
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
>
> 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.3.15#6346)

[GitHub] incubator-trafficcontrol issue #587: Adds external file download functionali...

[dg4prez]

Github user dg4prez commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/587
  
I'm not really sure how it's dangerous, as in order to use it you have to 
be an operator or higher.


---
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 #587: Adds external file download functionali...

[dg4prez]

Github user dg4prez commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/587
  
That was my initial design, actually, and it's easier to implement.  I 
suppose my main concern was not pointing a thundering herd at some poor 
defenseless host that isn't traffic ops.  If you guys think that a straight 
shot from the cache to the hosted file is better I can certainly go that way.


---
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 #587: Adds external file download functionali...

[elsloo]

Github user elsloo commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/587
  
@dg4prez this seems a little dangerous? Not sure why we'd need this 
functionality when caches by definition can usually go upstream via HTTP to 
arbitrary endpoints?


---
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-340) remove unneeded vendored dependencies

[ASF GitHub Bot (JIRA)]

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

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

Github user limited commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/583
  
merged, please close


> remove unneeded vendored dependencies
> -
>
> Key: TC-340
> URL: https://issues.apache.org/jira/browse/TC-340
> Project: Traffic Control
>  Issue Type: Task
>  Components: Traffic Stats
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Dan Kirkwood
> Fix For: 2.0.0, 2.1.0
>
>
> traffic_stats/vendor/gopkg.in/errgo.v1
> traffic_stats/vendor/gopkg.in/retry.v1
> These are no longer needed because of removal of the juju/persistentcookie 
> dependency.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol issue #583: [Backport TC-340] Remove TS unnecessary...

[limited]

Github user limited commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/583
  
merged, please close


---
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-167) api/1.1/cachegroupparameter.t test fails

[ASF GitHub Bot (JIRA)]

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

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

Github user limited commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/532
  
merged, please close


> api/1.1/cachegroupparameter.t test fails 
> -
>
> Key: TC-167
> URL: https://issues.apache.org/jira/browse/TC-167
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0
>Reporter: Jan van Doorn
>Assignee: Jan van Doorn
>Priority: Minor
> Fix For: 2.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol issue #532: [Backport TC-167] 2.0.x fix cachegroupp...

[limited]

Github user limited commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/532
  
merged, please close


---
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 #531: [Backport] remove KEYS -- stored in dis...

[limited]

Github user limited commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/531
  
merged, please close


---
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-150) generateCert script not echoing prompts from openssl

[ASF GitHub Bot (JIRA)]

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

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

Github user limited commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/530
  
merged to 2.0.x, please close


> generateCert script not echoing prompts from openssl
> 
>
> Key: TC-150
> URL: https://issues.apache.org/jira/browse/TC-150
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Ops
>Affects Versions: 2.0.0, 2.1.0
> Environment: New install on Centos 7
>Reporter: Dan Kirkwood
>Priority: Minor
> Fix For: 2.0.0, 2.1.0
>
>
> using the script to generate certs,  the initial prompts are shown,  but when 
> it gets to asking for city, state, organization, etc,  the prompt isn't shown 
> and appears to hang.  Hit  9 times, and it shows the next prompt 
> after that portion..
> This should be trivial to fix...Script is 
> traffic_ops/install/bin/generateCert



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] incubator-trafficcontrol issue #530: [Backport TC-150] 2.0 document cert gen...

[limited]

Github user limited commented on the issue:

https://github.com/apache/incubator-trafficcontrol/pull/530
  
merged to 2.0.x, please close


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