[GitHub] incubator-trafficcontrol pull request #732: adds integration tests to docker...

GitHub user dangogh opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/732 adds integration tests to docker setup for traffic_ops You can merge this pull request into a Git repository by running: $ git pull

Build failed in Jenkins: incubator-trafficcontrol-traffic_ops-test #17

See Changes: [dewrich] removes duplicate cachegroup apis [dewrich] removes duplicate server apis [dewrich] removes duplicate deliveryservice apis [dewrich] fixes tests and fixes bad

Build failed in Jenkins: incubator-trafficcontrol-traffic_ops-test #16

See Changes: [mitchell852] Tenant col in DS - tenant name in API -- [...truncated 1.03 MB...] unit_1 | # got: '62' unit_1 | #

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

[ https://issues.apache.org/jira/browse/TC-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086396#comment-16086396 ] ASF GitHub Bot commented on TC-82: -- Github user asfgit closed the pull request at:

[GitHub] incubator-trafficcontrol pull request #486: [TC-82] - removes duplicate apis

Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/486 --- 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

[GitHub] incubator-trafficcontrol pull request #718: Tenant in DS table - tenant name...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/718 --- 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

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

[ https://issues.apache.org/jira/browse/TC-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086198#comment-16086198 ] ASF GitHub Bot commented on TC-192: --- GitHub user rguiliani opened a pull request:

[GitHub] incubator-trafficcontrol pull request #731: [TC-192] Differentiates between ...

GitHub user rguiliani opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/731 [TC-192] Differentiates between goTM and javaTM rpm builds Adds a version differentiator for building goTM and javaTM by including an environment variable in the build service

Build failed in Jenkins: incubator-trafficcontrol-traffic_ops-test #15

See Changes: [dewrich] updating current user uses a different api than updating any user -- [...truncated 1.06 MB...] unit_1 | # got:

[GitHub] incubator-trafficcontrol pull request #730: [TC-64] - updating current user ...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/730 --- 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

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

[ https://issues.apache.org/jira/browse/TC-64?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086130#comment-16086130 ] ASF GitHub Bot commented on TC-64: -- GitHub user mitchell852 opened a pull request:

[GitHub] incubator-trafficcontrol pull request #730: [TC-64] - updating current user ...

GitHub user mitchell852 opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/730 [TC-64] - updating current user uses a different api than updating any user You can merge this pull request into a Git repository by running: $ git pull

[GitHub] incubator-trafficcontrol issue #729: Traffic Ops Golang Incremental Rewrite ...

Github user rob05c commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/729 > upgrade to perform all the config changes necessary to maintain > allocate a new, high, port > Notify the user via a message during upgrade @alficles Agree, will

[GitHub] incubator-trafficcontrol issue #729: Traffic Ops Golang Incremental Rewrite ...

Github user alficles commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/729 From a user's perspective, this creates some extra (as-yet-poorly-documented) obligations for configuration. An RPM upgrade should take care of itself. There should be enough

[GitHub] incubator-trafficcontrol issue #729: Traffic Ops Golang Incremental Rewrite ...

Github user rob05c commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/729 Right, it _will_ cause build changes, don't merge this until we do get consensus from the community on the mailing list (I sent an email to `users` and forwarded to `dev`, "Traffic

[GitHub] incubator-trafficcontrol issue #729: Traffic Ops Golang Incremental Rewrite ...

Github user dewrich commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/729 Also, should `traffic_ops/traffic_ops_golang/auth.go` be in `traffic_ops/experimental/traffic_ops_golang`? We haven't gotten any buy in from the community to put that code into

[GitHub] incubator-trafficcontrol issue #729: Traffic Ops Golang Incremental Rewrite ...

Github user rob05c commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/729 It should be easy to retire. Once all endpoints are in Golang, simply delete the Perl from the RPM and Service files. --- If your project is set up for it, you can reply to this

[GitHub] incubator-trafficcontrol issue #729: Traffic Ops Golang Incremental Rewrite ...

Github user dewrich commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/729 I agree with simple, but I also don't want to "couple" the two. I don't find it egregious, to implement them as a "sidecar" rpm. We also might want to scale them differently

[GitHub] incubator-trafficcontrol issue #729: Traffic Ops Golang Incremental Rewrite ...

Github user rob05c commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/729 The reason is to make it as operationally simple as possible. That's the only reason. We can make more RPMs, microservices, etc after we've moved away from Perl. I have no objection

[GitHub] incubator-trafficcontrol issue #729: Traffic Ops Golang Incremental Rewrite ...

Github user dewrich commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/729 I'm not sure why you would couple the Golang Microservices with the Traffic Op Perl Monolith. If anything you should begin a new "rpm" that only contains the Microservices (which

[GitHub] incubator-trafficcontrol pull request #729: Traffic Ops Golang Incremental R...

GitHub user rob05c opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/729 Traffic Ops Golang Incremental Rewrite App This adds an app, which serves Traffic Ops endpoints as they're written (currently, just monitoring.json), and reverse-proxies everything