[jira] [Resolved] (TC-513) Traffic Ops Golang must send Whole-Content-SHA512
[ https://issues.apache.org/jira/browse/TC-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson resolved TC-513. --- Resolution: Fixed > Traffic Ops Golang must send Whole-Content-SHA512 > - > > Key: TC-513 > URL: https://issues.apache.org/jira/browse/TC-513 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops >Affects Versions: 2.1.0, 2.2.0 >Reporter: Robert Butts >Assignee: Robert Butts > Fix For: 2.1.0, 2.2.0 > > > Once https://github.com/apache/incubator-trafficcontrol/pull/786 is merged > fixing TC-503, TO Golang must send a Whole-Content-SHA512 header, or ORT will > fail. (In fact, TO Golang fails without it, with the current MIC.) > This is necessary for a Message Integrity Check. Previously Content-Length > was used, which must not be sent under certain circumstances with HTTP/1.1. > See pull/786 and TC-503 for more details. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (TC-503) Traffic Ops ORT Fails with Chunked Encoding
[ https://issues.apache.org/jira/browse/TC-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson resolved TC-503. --- Resolution: Fixed > Traffic Ops ORT Fails with Chunked Encoding > --- > > Key: TC-503 > URL: https://issues.apache.org/jira/browse/TC-503 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops ORT >Affects Versions: 2.1.0, 2.2.0 >Reporter: Robert Butts >Assignee: Dewayne Richardson > Fix For: 2.1.0, 2.2.0 > > Original Estimate: 24h > Remaining Estimate: 24h > > ORT fails if no 'Content-Length' header exists. > Content-Length MAY be omitted per HTTP/1.1 RFC 7230, and in fact MUST NOT be > included with a 'Transfer-Encoding: Chunked' header, which MUST be accepted > by clients. > So far, we've just been lucky Perl/Mojolicious Traffic Ops doesn't happen to > send Chunked encodings to ORT. But the spec requires clients accept it, ORT > is in violation of HTTP/1.1. > Further, the upcoming Golang Traffic Ops sends Chunked encoding, and there's > no reasonable way in Go to prevent it. There's no HTTP-compliant way to > instruct the server not to send Chunked encoding either, since clients are > required to accept it. The right solution here is to fix ORT to accept > Chunked encoding, without Content-Length. > It appears ORT only refuses it as a safety check, and doesn't actually need > it for anything. Should be a simple fix. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (TC-542) TO init.d script needs to be converted to LSB Init for Golang Proxy
[ https://issues.apache.org/jira/browse/TC-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson reassigned TC-542: - Assignee: Dan Kirkwood > TO init.d script needs to be converted to LSB Init for Golang Proxy > --- > > Key: TC-542 > URL: https://issues.apache.org/jira/browse/TC-542 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dan Kirkwood > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-542) TO init.d script needs to be converted to LSB Init for Golang Proxy
Dewayne Richardson created TC-542: - Summary: TO init.d script needs to be converted to LSB Init for Golang Proxy Key: TC-542 URL: https://issues.apache.org/jira/browse/TC-542 Project: Traffic Control Issue Type: Improvement Components: Traffic Ops Affects Versions: 2.1.0 Reporter: Dewayne Richardson -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TC-291) GenIso can't handle concurrent requests
[
https://issues.apache.org/jira/browse/TC-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dewayne Richardson updated TC-291:
--
Issue Type: Improvement (was: Bug)
> GenIso can't handle concurrent requests
>
>
> Key: TC-291
> URL: https://issues.apache.org/jira/browse/TC-291
> Project: Traffic Control
> Issue Type: Improvement
> Components: Traffic Ops
>Affects Versions: 2.1.0, 2.0.0, 2.2.0
>Reporter: Dewayne Richardson
> Labels: genlso
> Fix For: 2.1.0, 2.2.0
>
>
> Because GenIso always changes the same files (no temporary directories
> created), it can't handle concurrent requests. We sometimes send commands to
> create 10 Edge Caches at the same time and we found out that the wrong IP
> address shows up on servers.
> I've got the code to fix it up (but need to sign our paperwork). But our
> GenIso.pm now deviates from what's in Traffic Ops because we wanted to keep
> the 1.0.0 functionality (don't use the install_cfg directory, keep using the
> simple network line).
> Suggestion: We should have a parameter to call different ISO generator
> scripts. Seems like this is implementation specific and not really a core
> function of Traffic Ops.
> Basic changes :
> use File::Temp;
> use File::Copy::Recursive;
> my $tmpdir = File::Temp::tempdir(CLEANUP => 1);
> ...
> GenIso.pm:my $tmp = File::Copy::Recursive::dircopy($dir,$tmpdir);
> GenIso.pm: my $cfg_dir = "$tmpdir/$install_cfg";
> GenIso.pm: print STUF "Dir== $tmpdir\n";
> GenIso.pm: my $cmd = "mkisofs -joliet-long -input-charset utf-8 -b
> isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4
> -boot-info-table -R -J -v -T $tmpdir";
> GenIso.pm: open(IN, "<$tmpdir/ks.src") || die("$tmpdir/ks.src:$!");
> GenIso.pm: open (OUT, ">$tmpdir/ks.cfg") || die("$tmpdir/ks.cfg:$!");
> GenIso.pm:File::Path::rmtree $tmpdir;
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (TC-503) Traffic Ops ORT Fails with Chunked Encoding
[ https://issues.apache.org/jira/browse/TC-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson reassigned TC-503: - Assignee: Dewayne Richardson (was: Robert Butts) > Traffic Ops ORT Fails with Chunked Encoding > --- > > Key: TC-503 > URL: https://issues.apache.org/jira/browse/TC-503 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops ORT >Affects Versions: 2.1.0 >Reporter: Robert Butts >Assignee: Dewayne Richardson > Original Estimate: 24h > Remaining Estimate: 24h > > ORT fails if no 'Content-Length' header exists. > Content-Length MAY be omitted per HTTP/1.1 RFC 7230, and in fact MUST NOT be > included with a 'Transfer-Encoding: Chunked' header, which MUST be accepted > by clients. > So far, we've just been lucky Perl/Mojolicious Traffic Ops doesn't happen to > send Chunked encodings to ORT. But the spec requires clients accept it, ORT > is in violation of HTTP/1.1. > Further, the upcoming Golang Traffic Ops sends Chunked encoding, and there's > no reasonable way in Go to prevent it. There's no HTTP-compliant way to > instruct the server not to send Chunked encoding either, since clients are > required to accept it. The right solution here is to fix ORT to accept > Chunked encoding, without Content-Length. > It appears ORT only refuses it as a safety check, and doesn't actually need > it for anything. Should be a simple fix. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TC-445) Traffic Ops API Rewrite: Implement /api/1.2/servers
[ https://issues.apache.org/jira/browse/TC-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson updated TC-445: -- Description: Implement the second TO Golang endpoint (was: Implement the first TO Golang endpoint using the MojoCookies+Capabilities) > Traffic Ops API Rewrite: Implement /api/1.2/servers > --- > > Key: TC-445 > URL: https://issues.apache.org/jira/browse/TC-445 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > > Implement the second TO Golang endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TC-445) Traffic Ops API Rewrite: Implement /api/1.2/servers
[ https://issues.apache.org/jira/browse/TC-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson updated TC-445: -- Summary: Traffic Ops API Rewrite: Implement /api/1.2/servers (was: Traffic Ops API Rewrite: Implement /api/1.2/users with MojoCookie+Capabilities) > Traffic Ops API Rewrite: Implement /api/1.2/servers > --- > > Key: TC-445 > URL: https://issues.apache.org/jira/browse/TC-445 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > > Implement the first TO Golang endpoint using the MojoCookies+Capabilities -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-452) Traffic Ops API Rewrite: Document the Golang API using Swagger Annotations
[ https://issues.apache.org/jira/browse/TC-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-452. - Resolution: Fixed Fix Version/s: 2.2.0 Fixed in PR https://github.com/apache/incubator-trafficcontrol/pull/729 > Traffic Ops API Rewrite: Document the Golang API using Swagger Annotations > -- > > Key: TC-452 > URL: https://issues.apache.org/jira/browse/TC-452 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > Fix For: 2.2.0 > > > Documenting the API with Swagger annotations will automate the Traffic Ops > API Documentation as well as generate an API tool for testing purposes. > See: > https://github.com/swagger-api/swagger-core/wiki/Annotations-1.5.X > https://engineroom.teamwork.com/generate-api-from-annotations-in-go -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-450) Traffic Ops API Rewrite: Unit Testing approach
[ https://issues.apache.org/jira/browse/TC-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-450. - Resolution: Fixed Changed Fixed in Version > Traffic Ops API Rewrite: Unit Testing approach > -- > > Key: TC-450 > URL: https://issues.apache.org/jira/browse/TC-450 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > Fix For: 2.2.0 > > > Work through how to build a Unit Tests against the Golang modules, Database > Code in a consistent fashion -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TC-450) Traffic Ops API Rewrite: Unit Testing approach
[ https://issues.apache.org/jira/browse/TC-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson updated TC-450: -- Fix Version/s: (was: 2.1.0) > Traffic Ops API Rewrite: Unit Testing approach > -- > > Key: TC-450 > URL: https://issues.apache.org/jira/browse/TC-450 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > > Work through how to build a Unit Tests against the Golang modules, Database > Code in a consistent fashion -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (TC-450) Traffic Ops API Rewrite: Unit Testing approach
[ https://issues.apache.org/jira/browse/TC-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson reopened TC-450: --- > Traffic Ops API Rewrite: Unit Testing approach > -- > > Key: TC-450 > URL: https://issues.apache.org/jira/browse/TC-450 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > Fix For: 2.1.0 > > > Work through how to build a Unit Tests against the Golang modules, Database > Code in a consistent fashion -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-450) Traffic Ops API Rewrite: Unit Testing approach
[ https://issues.apache.org/jira/browse/TC-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-450. - Resolution: Fixed Fix Version/s: 2.1.0 Completed with https://github.com/apache/incubator-trafficcontrol/pull/729 > Traffic Ops API Rewrite: Unit Testing approach > -- > > Key: TC-450 > URL: https://issues.apache.org/jira/browse/TC-450 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > Fix For: 2.1.0 > > > Work through how to build a Unit Tests against the Golang modules, Database > Code in a consistent fashion -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-451) Traffic Ops API Rewrite: Developer's Guide - Documentation
[ https://issues.apache.org/jira/browse/TC-451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-451. - Resolution: Fixed Completed with https://github.com/apache/incubator-trafficcontrol/pull/729 > Traffic Ops API Rewrite: Developer's Guide - Documentation > -- > > Key: TC-451 > URL: https://issues.apache.org/jira/browse/TC-451 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > > Documentation (Developer's Guide) on how to build a new Golang endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-449) Traffic Ops API Rewrite: Implement logging wrapper
[ https://issues.apache.org/jira/browse/TC-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-449. - Resolution: Fixed Completed with https://github.com/apache/incubator-trafficcontrol/pull/729 > Traffic Ops API Rewrite: Implement logging wrapper > -- > > Key: TC-449 > URL: https://issues.apache.org/jira/browse/TC-449 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > > Build a consistent wrapper for the access.log and the traffic_ops.log -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TC-283) traffic ops api (PUT api/.../server/...) doc inconsistent with code
[
https://issues.apache.org/jira/browse/TC-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dewayne Richardson updated TC-283:
--
Issue Type: Improvement (was: Bug)
> traffic ops api (PUT api/.../server/...) doc inconsistent with code
> ---
>
> Key: TC-283
> URL: https://issues.apache.org/jira/browse/TC-283
> Project: Traffic Control
> Issue Type: Improvement
> Components: Traffic Ops API
>Affects Versions: 2.1.0
>Reporter: Dan Kirkwood
> Labels: api_server
>
> The Traffic Ops API documentation for "PUT /api/1.2/servers/{:id}" shows that
> "type" is a required field. It's actually "type_id". I think that's true
> for all the fields representing foreign keys.
> Documentation is here:
> http://trafficcontrol.incubator.apache.org/docs/latest/development/traffic_ops_api/v12/server.html
> Code is here:
> https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/lib/API/Server.pm#L201
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (TC-445) Traffic Ops API Rewrite: Implement /api/1.2/users with MojoCookie+Capabilities
[ https://issues.apache.org/jira/browse/TC-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson updated TC-445: -- Issue Type: New Feature (was: Improvement) > Traffic Ops API Rewrite: Implement /api/1.2/users with MojoCookie+Capabilities > -- > > Key: TC-445 > URL: https://issues.apache.org/jira/browse/TC-445 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > > Implement the first TO Golang endpoint using the MojoCookies+Capabilities -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-347) Docker Build for Portal fails with SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://rubygems.org/latest_specs.4.8.gz
[ https://issues.apache.org/jira/browse/TC-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-347. - Resolution: Cannot Reproduce Assignee: Dewayne Richardson > Docker Build for Portal fails with SSL_connect returned=1 errno=0 state=SSLv3 > read server certificate B: certificate verify failed > (https://rubygems.org/latest_specs.4.8.gz > > > Key: TC-347 > URL: https://issues.apache.org/jira/browse/TC-347 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Portal >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > Labels: build, docker > > Attempting to build the rpms and the build fails at the Portal phase. > --- > Step 6/10 : RUN gem install compass > ---> Running in 5f883ef539c1 > ERROR: Could not find a valid gem 'compass' (>= 0), here is why: > Unable to download data from https://rubygems.org/ - SSL_connect > returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify > failed (https://rubygems.org/latest_specs.4.8.gz) > ERROR: Service 'traffic_portal_build' failed to build: The command '/bin/sh > -c gem install compass' returned a non-zero code: 2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-375) yum upgrade traffic_ops... can't find goose
[ https://issues.apache.org/jira/browse/TC-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-375. - Resolution: Fixed Assignee: Dewayne Richardson This was fixed when we introduced /etc/profile.d/traffic_ops.sh to the rpm to set the global PATH accordingly > yum upgrade traffic_ops... can't find goose > --- > > Key: TC-375 > URL: https://issues.apache.org/jira/browse/TC-375 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops >Affects Versions: 2.1.0 >Reporter: Dan Kirkwood >Assignee: Dewayne Richardson > Labels: goose, postinstall, yum > Fix For: 2.1.0 > > > Traffic Ops postinstall puts goose in /opt/traffic_ops/go/bin. The rpm > upgrade path executes `db/admin.pl upgrade` which tries to run goose, but > can't find it because it's not in the root PATH. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TC-445) Traffic Ops API Rewrite: Implement /api/1.2/users with MojoCookie+Capabilities
[ https://issues.apache.org/jira/browse/TC-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson updated TC-445: -- Issue Type: Improvement (was: Bug) > Traffic Ops API Rewrite: Implement /api/1.2/users with MojoCookie+Capabilities > -- > > Key: TC-445 > URL: https://issues.apache.org/jira/browse/TC-445 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops API >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > > Implement the first TO Golang endpoint using the MojoCookies+Capabilities -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-446) Traffic Ops API Rewrite: Testing PR #729 to use as the basis for TO rewrite
[ https://issues.apache.org/jira/browse/TC-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-446. - Resolution: Fixed Assignee: Dewayne Richardson Complete: https://github.com/apache/incubator-trafficcontrol/pull/729 > Traffic Ops API Rewrite: Testing PR #729 to use as the basis for TO rewrite > --- > > Key: TC-446 > URL: https://issues.apache.org/jira/browse/TC-446 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops API >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-447) Traffic Ops API Rewrite: Testing PR #729 to use as the basis for TO rewrite
[ https://issues.apache.org/jira/browse/TC-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-447. - Resolution: Fixed Fix Version/s: 2.1.0 Is complete, will be merging soon: https://github.com/apache/incubator-trafficcontrol/pull/729 > Traffic Ops API Rewrite: Testing PR #729 to use as the basis for TO rewrite > --- > > Key: TC-447 > URL: https://issues.apache.org/jira/browse/TC-447 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > Fix For: 2.1.0 > > > PR https://github.com/apache/incubator-trafficcontrol/pull/729 is being > evaluated to determine how to move forward with the TO rewrite. It has a > Mojolicious Cookie feature that will allow for services to be built that can > be authenticated against Mojolicious. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TC-493) API documentation is not accurate for API Server Create and Update end-points
[ https://issues.apache.org/jira/browse/TC-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson updated TC-493: -- Priority: Minor (was: Major) > API documentation is not accurate for API Server Create and Update end-points > - > > Key: TC-493 > URL: https://issues.apache.org/jira/browse/TC-493 > Project: Traffic Control > Issue Type: Bug > Components: Documentation, Traffic Ops API >Affects Versions: 2.1.0 >Reporter: Robert Scrimo >Priority: Minor > > API documentation is not accurate to functionality and lite on details for > API Server Create and Update end-points. > Also, it may be a good idea to check over the entire Server API documentation > for accuracy while this work is being done. > NOTE: Other versions of Traffic Ops may be affected. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-448) Traffic Ops API Rewrite: Config file organization
[ https://issues.apache.org/jira/browse/TC-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-448. - Resolution: Fixed Fix Version/s: 2.1.0 See: https://github.com/apache/incubator-trafficcontrol/pull/729 > Traffic Ops API Rewrite: Config file organization > - > > Key: TC-448 > URL: https://issues.apache.org/jira/browse/TC-448 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > Fix For: 2.1.0 > > > Write Golang logic to reuse the existing > /opt/traffic_ops/app/conf//*.conf files. As well as build a new > config file to support features the existing config files do not support. > Which might entail building reading the existing cdn.conf which is in a Perl > hash format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TC-452) Traffic Ops API Rewrite: Document the Golang API using Swagger Annotations
[ https://issues.apache.org/jira/browse/TC-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson updated TC-452: -- Summary: Traffic Ops API Rewrite: Document the Golang API using Swagger Annotations (was: Traffic Ops API Rewrite: Document the Golang API using Swagger Annotation) > Traffic Ops API Rewrite: Document the Golang API using Swagger Annotations > -- > > Key: TC-452 > URL: https://issues.apache.org/jira/browse/TC-452 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > > Documenting the API with Swagger annotations will automate the Traffic Ops > API Documentation as well as generate an API tool for testing purposes. > See: > https://github.com/swagger-api/swagger-core/wiki/Annotations-1.5.X > https://engineroom.teamwork.com/generate-api-from-annotations-in-go -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TC-452) Traffic Ops API Rewrite: Document the Golang API using Swagger Annotation
[ https://issues.apache.org/jira/browse/TC-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson updated TC-452: -- Summary: Traffic Ops API Rewrite: Document the Golang API using Swagger Annotation (was: Traffic Ops API Rewrite: Document the Golang API using Swagger using Swagger Annotation) > Traffic Ops API Rewrite: Document the Golang API using Swagger Annotation > - > > Key: TC-452 > URL: https://issues.apache.org/jira/browse/TC-452 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > > Documenting the API with Swagger annotations will automate the Traffic Ops > API Documentation as well as generate an API tool for testing purposes. > See: > https://github.com/swagger-api/swagger-core/wiki/Annotations-1.5.X > https://engineroom.teamwork.com/generate-api-from-annotations-in-go -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-452) Traffic Ops API Rewrite: Document the Golang API using Swagger using Swagger Annotation
Dewayne Richardson created TC-452: - Summary: Traffic Ops API Rewrite: Document the Golang API using Swagger using Swagger Annotation Key: TC-452 URL: https://issues.apache.org/jira/browse/TC-452 Project: Traffic Control Issue Type: New Feature Components: Traffic Ops API Reporter: Dewayne Richardson Assignee: Dewayne Richardson Documenting the API with Swagger annotations will automate the Traffic Ops API Documentation as well as generate an API tool for testing purposes. See: https://github.com/swagger-api/swagger-core/wiki/Annotations-1.5.X https://engineroom.teamwork.com/generate-api-from-annotations-in-go -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-451) Traffic Ops API Rewrite: Developer's Guide - Documentation
Dewayne Richardson created TC-451: - Summary: Traffic Ops API Rewrite: Developer's Guide - Documentation Key: TC-451 URL: https://issues.apache.org/jira/browse/TC-451 Project: Traffic Control Issue Type: New Feature Components: Traffic Ops API Reporter: Dewayne Richardson Assignee: Dewayne Richardson Documentation (Developer's Guide) on how to build a new Golang endpoint -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-450) Traffic Ops API Rewrite: Unit Testing approach
Dewayne Richardson created TC-450: - Summary: Traffic Ops API Rewrite: Unit Testing approach Key: TC-450 URL: https://issues.apache.org/jira/browse/TC-450 Project: Traffic Control Issue Type: New Feature Components: Traffic Ops API Reporter: Dewayne Richardson Assignee: Dewayne Richardson Work through how to build a Unit Tests against the Golang modules, Database Code in a consistent fashion -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (TC-448) Traffic Ops API Rewrite: Config file organization
[ https://issues.apache.org/jira/browse/TC-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson updated TC-448: -- Description: Write Golang logic to reuse the existing /opt/traffic_ops/app/conf//*.conf files. As well as build a new config file to support features the existing config files do not support. Which might entail building reading the existing cdn.conf which is in a Perl hash format. (was: Write Golang logic to reuse the existing /opt/traffic_ops/app/conf//*.conf files. As well as build a new config file to support features the existing config files do not support.) > Traffic Ops API Rewrite: Config file organization > - > > Key: TC-448 > URL: https://issues.apache.org/jira/browse/TC-448 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Ops API >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson > > Write Golang logic to reuse the existing > /opt/traffic_ops/app/conf//*.conf files. As well as build a new > config file to support features the existing config files do not support. > Which might entail building reading the existing cdn.conf which is in a Perl > hash format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-449) Traffic Ops API Rewrite: Implement logging wrapper
Dewayne Richardson created TC-449: - Summary: Traffic Ops API Rewrite: Implement logging wrapper Key: TC-449 URL: https://issues.apache.org/jira/browse/TC-449 Project: Traffic Control Issue Type: New Feature Components: Traffic Ops API Reporter: Dewayne Richardson Assignee: Dewayne Richardson Build a consistent wrapper for the access.log and the traffic_ops.log -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-448) Traffic Ops API Rewrite: Config file organization
Dewayne Richardson created TC-448: - Summary: Traffic Ops API Rewrite: Config file organization Key: TC-448 URL: https://issues.apache.org/jira/browse/TC-448 Project: Traffic Control Issue Type: New Feature Components: Traffic Ops API Affects Versions: 2.1.0 Reporter: Dewayne Richardson Assignee: Dewayne Richardson Write Golang logic to reuse the existing /opt/traffic_ops/app/conf//*.conf files. As well as build a new config file to support features the existing config files do not support. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-447) Traffic Ops API Rewrite: Testing PR #729 to use as the basis for TO rewrite
Dewayne Richardson created TC-447: - Summary: Traffic Ops API Rewrite: Testing PR #729 to use as the basis for TO rewrite Key: TC-447 URL: https://issues.apache.org/jira/browse/TC-447 Project: Traffic Control Issue Type: New Feature Components: Traffic Ops API Affects Versions: 2.1.0 Reporter: Dewayne Richardson Assignee: Dewayne Richardson PR https://github.com/apache/incubator-trafficcontrol/pull/729 is being evaluated to determine how to move forward with the TO rewrite. It has a Mojolicious Cookie feature that will allow for services to be built that can be authenticated against Mojolicious. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-350) Traffic Ops Environment needs to be consistent PERL5LIB, GOPATH, and PATH
[ https://issues.apache.org/jira/browse/TC-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-350. - Resolution: Fixed the RPM sets up an /etc/profile.d/traffic_ops.sh and Postinstall now helps with the pathing > Traffic Ops Environment needs to be consistent PERL5LIB, GOPATH, and PATH > - > > Key: TC-350 > URL: https://issues.apache.org/jira/browse/TC-350 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson >Priority: Minor > Labels: gopath, library, path > Fix For: 2.1.0 > > > PERL5LIB: > /opt/traffic_ops_extensions/private/lib:/opt/traffic_ops/app/lib:/opt/traffic_ops/app/local/lib/perl5 > GOPATH: > /opt/traffic_ops/go > PATH: > $PATH:/opt/traffic_ops/go/bin:/usr/local/go/bin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-346) 2.1 (master) Traffic Ops Installation issues.
[
https://issues.apache.org/jira/browse/TC-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dewayne Richardson closed TC-346.
-
Resolution: Fixed
> 2.1 (master) Traffic Ops Installation issues.
> -
>
> Key: TC-346
> URL: https://issues.apache.org/jira/browse/TC-346
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Jan van Doorn
>Assignee: Dewayne Richardson
> Labels: installation
>
> Trying to install TO from scratch. Some notes:
> 1) had to install postgres stuff even though postgres is remote:
> [jvando001@ipcdn-cache-28 tmp]$ sudo yum install postgresql
> [root@ipcdn-cache-28 ~]# yum install postgresql-devel
> 2) Some errors on the seeds, not sure if they matter:
> {code}
> === Setting up parameters
> Use of uninitialized value in concatenation (.) or string at
> /opt/traffic_ops/install/bin/_postinstall line 638.
> Use of uninitialized value in concatenation (.) or string at
> /opt/traffic_ops/install/bin/_postinstall line 638.
> -- global parameters
> insert into parameter (name, config_file, value)
> values ('tm.url', 'global', 'https://localhost')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('tm.instance_name', 'global', '')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('tm.toolname', 'global', '')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('tm.infourl', 'global', 'https://localhost/doc')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> -- CRConfig.json parameters
> insert into parameter (name, config_file, value)
> values ('geolocation.polling.url', 'CRConfig.json',
> 'https://localhost/routing/GeoLite2-City.mmdb.gz')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('geolocation6.polling.url', 'CRConfig.json',
> 'https://localhost/routing/GeoLiteCityv6.dat.gz')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> === Setting up profilesUse of uninitialized value in concatenation
> (.) or string at /opt/traffic_ops/install/bin/_postinstall line 676.
> Use of uninitialized value in concatenation (.) or string at
> /opt/traffic_ops/install/bin/_postinstall line 676.
> -- global parameters
> insert into profile (name, description, type)
> values ('GLOBAL', 'Global Traffic Ops profile, DO NOT
> DELETE', 'UNK_PROFILE')
> ON CONFLICT (name) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'tm.url' and config_file = 'global'
> and value = 'https://localhost') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'tm.instance_name' and config_file =
> 'global' and value = '') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'tm.toolname' and config_file =
> 'global' and value = '') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'tm.infourl' and config_file =
> 'global' and value = 'https://localhost/doc') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'geolocation.polling.url' and
> config_file = 'CRConfig.json' and value =
> 'https://cdn1.denver-isp.org/routing/GeoLite2-City.mmdb.gz') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'geolocation6.polling.url' and
> config_file = 'CRConfig.json' and value =
> 'https://cdn1.denver-isp.org/routing/GeoLiteCityv6.dat.gz') )
> ON CONFLICT (profil
[jira] [Assigned] (TC-220) Logging System Creation
[ https://issues.apache.org/jira/browse/TC-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson reassigned TC-220: - Assignee: Matt Mills (was: Dewayne Richardson) > Logging System Creation > --- > > Key: TC-220 > URL: https://issues.apache.org/jira/browse/TC-220 > Project: Traffic Control > Issue Type: New Feature > Components: Traffic Analytics >Affects Versions: 2.1.0 >Reporter: Ryan Durfey >Assignee: Matt Mills > Labels: logs > > Create an open source system to gather ATS request / response logs. > 1. Must be built from all open source components. > 2. Must be able to ingest 1MM records a second on a reasonable amount of > hardware and be horizontally scalable to add additional capacity. > 3. Must allow storage of raw logs for configurable period of time between > 30-90 days. > 4. Must be able to process raw logs from ATS and split based service by > assessing configuration of service. > 5. Must be able to split logs into files of no more than 2 hours or 500k logs > whichever occurs first. These should be starter configs and should be > configurable on a per service basis. > 6. Log files must be compressed to conserve space. > 7. Log files should be accessible via a web server interface. > 8. Log files should be accessible via an API request. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (TC-380) Integration test data for kabletown has bad regex types
[ https://issues.apache.org/jira/browse/TC-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-380. - Resolution: Fixed > Integration test data for kabletown has bad regex types > --- > > Key: TC-380 > URL: https://issues.apache.org/jira/browse/TC-380 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops >Affects Versions: 2.1.0 >Reporter: Dewayne Richardson >Assignee: Dewayne Richardson >Priority: Critical > Labels: integration-test > Fix For: 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-446) Traffic Ops API Rewrite: Testing PR #729 to use as the basis for TO rewrite
Dewayne Richardson created TC-446: - Summary: Traffic Ops API Rewrite: Testing PR #729 to use as the basis for TO rewrite Key: TC-446 URL: https://issues.apache.org/jira/browse/TC-446 Project: Traffic Control Issue Type: Bug Components: Traffic Ops API Affects Versions: 2.1.0 Reporter: Dewayne Richardson -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-445) Traffic Ops API Rewrite: Implement /api/1.2/users with MojoCookie+Capabilities
Dewayne Richardson created TC-445: - Summary: Traffic Ops API Rewrite: Implement /api/1.2/users with MojoCookie+Capabilities Key: TC-445 URL: https://issues.apache.org/jira/browse/TC-445 Project: Traffic Control Issue Type: Bug Components: Traffic Ops API Affects Versions: 2.1.0 Reporter: Dewayne Richardson Assignee: Dewayne Richardson Implement the first TO Golang endpoint using the MojoCookies+Capabilities -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-426) Postinstall -- answering "no" to certificate generation does not skip
Dewayne Richardson created TC-426: - Summary: Postinstall -- answering "no" to certificate generation does not skip Key: TC-426 URL: https://issues.apache.org/jira/browse/TC-426 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Affects Versions: 2.1.0 Reporter: Dewayne Richardson Priority: Minor Answering 'no' to 'Do you want to generate a certificate?:' forces certificate generation. That section should have been skipped. ===/opt/traffic_ops/install/data/json/openssl_configuration.json=== Do you want to generate a certificate?: no Country Name (2 letter code): US -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-402) xml_id should not be changed after initial Delivery Service Creation
Dewayne Richardson created TC-402: - Summary: xml_id should not be changed after initial Delivery Service Creation Key: TC-402 URL: https://issues.apache.org/jira/browse/TC-402 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Reporter: Dewayne Richardson Traffic Ops cannot handle changing the xml_id because the parameters for the ATS config files use the xml_id by naming convention. Easy fix, just disable the 'xml_id' field for "Edit/Updates" -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-380) Integration test data for kabletown has bad regex types
Dewayne Richardson created TC-380: - Summary: Integration test data for kabletown has bad regex types Key: TC-380 URL: https://issues.apache.org/jira/browse/TC-380 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Affects Versions: 2.1.0 Reporter: Dewayne Richardson Assignee: Dewayne Richardson Priority: Critical Fix For: 2.1.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (TC-350) Traffic Ops Environment needs to be consistent PERL5LIB, GOPATH, and PATH
Dewayne Richardson created TC-350: - Summary: Traffic Ops Environment needs to be consistent PERL5LIB, GOPATH, and PATH Key: TC-350 URL: https://issues.apache.org/jira/browse/TC-350 Project: Traffic Control Issue Type: Improvement Components: Traffic Ops Affects Versions: 2.1.0 Reporter: Dewayne Richardson Assignee: Dewayne Richardson Priority: Minor Fix For: 2.1.0 PERL5LIB: /opt/traffic_ops_extensions/private/lib:/opt/traffic_ops/app/lib:/opt/traffic_ops/app/local/lib/perl5 GOPATH: /opt/traffic_ops/go PATH: $PATH:/opt/traffic_ops/go/bin:/usr/local/go/bin -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TC-346) 2.1 (master) Traffic Ops Installation issues.
[
https://issues.apache.org/jira/browse/TC-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dewayne Richardson reassigned TC-346:
-
Assignee: Dewayne Richardson (was: Dan Kirkwood)
> 2.1 (master) Traffic Ops Installation issues.
> -
>
> Key: TC-346
> URL: https://issues.apache.org/jira/browse/TC-346
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
>Affects Versions: 2.1.0
>Reporter: Jan van Doorn
>Assignee: Dewayne Richardson
>
> Trying to install TO from scratch. Some notes:
> 1) had to install postgres stuff even though postgres is remote:
> [jvando001@ipcdn-cache-28 tmp]$ sudo yum install postgresql
> [root@ipcdn-cache-28 ~]# yum install postgresql-devel
> 2) Some errors on the seeds, not sure if they matter:
> {code}
> === Setting up parameters
> Use of uninitialized value in concatenation (.) or string at
> /opt/traffic_ops/install/bin/_postinstall line 638.
> Use of uninitialized value in concatenation (.) or string at
> /opt/traffic_ops/install/bin/_postinstall line 638.
> -- global parameters
> insert into parameter (name, config_file, value)
> values ('tm.url', 'global', 'https://localhost')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('tm.instance_name', 'global', '')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('tm.toolname', 'global', '')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('tm.infourl', 'global', 'https://localhost/doc')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> -- CRConfig.json parameters
> insert into parameter (name, config_file, value)
> values ('geolocation.polling.url', 'CRConfig.json',
> 'https://localhost/routing/GeoLite2-City.mmdb.gz')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> insert into parameter (name, config_file, value)
> values ('geolocation6.polling.url', 'CRConfig.json',
> 'https://localhost/routing/GeoLiteCityv6.dat.gz')
> ON CONFLICT (name, config_file, value) DO NOTHING;
> === Setting up profilesUse of uninitialized value in concatenation
> (.) or string at /opt/traffic_ops/install/bin/_postinstall line 676.
> Use of uninitialized value in concatenation (.) or string at
> /opt/traffic_ops/install/bin/_postinstall line 676.
> -- global parameters
> insert into profile (name, description, type)
> values ('GLOBAL', 'Global Traffic Ops profile, DO NOT
> DELETE', 'UNK_PROFILE')
> ON CONFLICT (name) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'tm.url' and config_file = 'global'
> and value = 'https://localhost') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'tm.instance_name' and config_file =
> 'global' and value = '') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'tm.toolname' and config_file =
> 'global' and value = '') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'tm.infourl' and config_file =
> 'global' and value = 'https://localhost/doc') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'geolocation.polling.url' and
> config_file = 'CRConfig.json' and value =
> 'https://cdn1.denver-isp.org/routing/GeoLite2-City.mmdb.gz') )
> ON CONFLICT (profile, parameter) DO NOTHING;
> insert into profile_parameter (profile, parameter)
> values ( (select id from profile where name = 'GLOBAL'),
> (select id from parameter where name = 'geolocation6.polling.url' and
> config_file = 'CRConfig.json' and value =
> 'https://cdn1.denver-isp.org/routing/GeoLiteCityv6.dat.gz') )
> ON CONFLICT (p
[jira] [Created] (TC-347) Docker Build for Portal fails with SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://rubygems.org/latest_specs.4.8.gz
Dewayne Richardson created TC-347: - Summary: Docker Build for Portal fails with SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://rubygems.org/latest_specs.4.8.gz Key: TC-347 URL: https://issues.apache.org/jira/browse/TC-347 Project: Traffic Control Issue Type: Bug Components: Traffic Portal Affects Versions: 2.1.0 Reporter: Dewayne Richardson Attempting to build the rpms and the build fails at the Portal phase. --- Step 6/10 : RUN gem install compass ---> Running in 5f883ef539c1 ERROR: Could not find a valid gem 'compass' (>= 0), here is why: Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (https://rubygems.org/latest_specs.4.8.gz) ERROR: Service 'traffic_portal_build' failed to build: The command '/bin/sh -c gem install compass' returned a non-zero code: 2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-336) Add ability to copy url_sig keys from one DS to another GH #1540
Dewayne Richardson created TC-336: - Summary: 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 Reporter: Dewayne Richardson Priority: Minor 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.3.15#6346)
[jira] [Created] (TC-335) Traffic Router should not bring unresponsive Traffic Monitor decisions back right away GH #1661
Dewayne Richardson created TC-335: - Summary: Traffic Router should not bring unresponsive Traffic Monitor decisions back right away GH #1661 Key: TC-335 URL: https://issues.apache.org/jira/browse/TC-335 Project: Traffic Control Issue Type: Bug Components: Traffic Router Reporter: Dewayne Richardson Traffic Monitor split-brain scenario can have a violent recovery path -- potentially taking marking all caches unhealthy. mtorluemke opened this issue on Jul 29, 2016 · 1 comment -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-328) server Network IP expect to be different management GH #1618
Dewayne Richardson created TC-328: - Summary: server Network IP expect to be different management GH #1618 Key: TC-328 URL: https://issues.apache.org/jira/browse/TC-328 Project: Traffic Control Issue Type: Bug Reporter: Dewayne Richardson when you add or edit server at the GUI of traffic_ops,server Network IP can be same as management IP Address . pengyuewu opened this issue on Jul 21, 2016 · 0 comments -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-327) ConfigFiles.pm detects blank as not null and tries to gen files GH #1090
Dewayne Richardson created TC-327: - Summary: ConfigFiles.pm detects blank as not null and tries to gen files GH #1090 Key: TC-327 URL: https://issues.apache.org/jira/browse/TC-327 Project: Traffic Control Issue Type: Bug Reporter: Dewayne Richardson Assignee: Derek Gelinas ConfigFiles.pm will read a blank in the database as a file that needs creation or action upon. Some defensive code should detect this issue and either treat it as a null or pitch an error with some troubleshooting steps to fix the issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-321) Consider Adding Traffic Router Config for Certificate Check Interval GH #1780
Dewayne Richardson created TC-321: - Summary: Consider Adding Traffic Router Config for Certificate Check Interval GH #1780 Key: TC-321 URL: https://issues.apache.org/jira/browse/TC-321 Project: Traffic Control Issue Type: Improvement Components: Traffic Router Reporter: Dewayne Richardson Currently, when Traffic Router doesn't have certificates for delivery services, it sleeps for a hard-coded 1 second and tries again, infinitely. See b89c9c8#diff-895918d726d34df684cb81881e1b72f9R137 We should consider making the time interval a config, to allow dynamically changing the time between checks. We may decide this is too small to be worth another config param. But we should think about it and make a decision. If it is a config, it should probably be a static value, not exponential backoff, because there's no network activity. This checks a data object which is fetched by another thread, so the cost is only a tiny amount of CPU. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-315) Traffic Ops DS Create API does not validate Origin Server Base URL begins with http(s):// GH #1513
Dewayne Richardson created TC-315: - Summary: Traffic Ops DS Create API does not validate Origin Server Base URL begins with http(s):// GH #1513 Key: TC-315 URL: https://issues.apache.org/jira/browse/TC-315 Project: Traffic Control Issue Type: Bug Reporter: Dewayne Richardson If http(s):// is missing from the beginning of the URL, the map line in remap.config will be incorrect and the delivery service GET request will not be remapped on the edge cache. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (TC-182) Traffic Ops seeds.sql missing data from the status table
[
https://issues.apache.org/jira/browse/TC-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dewayne Richardson closed TC-182.
-
Resolution: Fixed
> Traffic Ops seeds.sql missing data from the status table
>
>
> Key: TC-182
> URL: https://issues.apache.org/jira/browse/TC-182
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
>Reporter: Matt Mills
>Priority: Minor
>
> Currently seeds.sql contains the following for the status table:
> {code:sql}
> -- statuses
> insert into status (name, description) values ('PRE_PROD', 'Pre Production.
> Not active in any configuration.') ON CONFLICT DO NOTHING;
> {code}
> After startup, trying to add a server without the OFFLINE status in the table
> throws a SQL error. This can be resolved by adding the additional statuses:
> {code}
> OFFLINE| Edge: Puts server in CCR config file in this state, but CCR will
> never route traffic to it. Mid: Server will not be included in parent.config
> files for its edge caches
> ONLINE | Edge: Puts server in CCR config file in this state, and CCR will
> always route traffic to it. Mid: Server will be included in parent.config
> files for its edges
> REPORTED | Edge: Puts server in CCR config file in this state, and CCR will
> adhere to the health protocol. Mid: N/A for now
> ADMIN_DOWN | Temporary down. Edge: XMPP client will send status OFFLINE to
> CCR, otherwise similar to REPORTED. Mid: Server will not be included in
> parent.config files for its edge caches
> CCR_IGNORE | Edge: 12M will not include caches in this state in CCR config
> files. Mid: N/A for now
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (TC-302) TO: Edit Profile Details and Close, change log entry created GH #1341
Dewayne Richardson created TC-302: - Summary: TO: Edit Profile Details and Close, change log entry created GH #1341 Key: TC-302 URL: https://issues.apache.org/jira/browse/TC-302 Project: Traffic Control Issue Type: Bug Reporter: Dewayne Richardson I was seeing some Change Log entries which made me question my team mates. Update profile with name: EDGE_R730XD_532-733 They haven't changed anything, but here's the steps to reproduce. Parameters -> Select Profile Select Profile Details Select Edit Select Close (So no change are done, they simply wanted to copy&paste) At this point, a change log entry is produced for something that wasn't updated. https://github.com/Comcast/traffic_control/blob/master/traffic_ops/app/lib/UI/Profile.pm#L190-L212 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-301) creating https delivery service and not setting to active still looks for cert. Github Issue #1086
Dewayne Richardson created TC-301: - Summary: creating https delivery service and not setting to active still looks for cert. Github Issue #1086 Key: TC-301 URL: https://issues.apache.org/jira/browse/TC-301 Project: Traffic Control Issue Type: Bug Reporter: Dewayne Richardson Que'ed and snapshotted - delivery service was not set to active. On syncds it err's looking for DS cert. ERROR Received error code 400 for https://trafficops/api/1.1/deliveryservices/hostname/deliveryservicename/sslkeys.json from Traffic Ops! FATAL SSL URL: https://trafficops/api/1.1/deliveryservices/hostname/deliveryservicename/sslkeys.json returned 400. Exiting. Just generating a ssl key and error goes away. Copying /tmp/ort/123/trafficserver/config_trops deliveryservicename .cer to /opt/trafficserver/etc/trafficserver/ssl//deliveryservicename_cert.cer ERROR Copying /tmp/ort/123/trafficserver/config_trops/deliveryservicename.key to /opt/trafficserver/etc/trafficserver/ssl//deliveryservicename.key -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-298) Health params.json updated with certain Profile names Github Issue #896
Dewayne Richardson created TC-298: - Summary: Health params.json updated with certain Profile names Github Issue #896 Key: TC-298 URL: https://issues.apache.org/jira/browse/TC-298 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Affects Versions: 2.0.0 Reporter: Dewayne Richardson Create Profile names in the Traffic_OPs with names such as Edge and Mid for Edge and Mid cache profiles, these don't get updated in the heath_params.json on the Traffic monitor. In the current implementation of traffic ops, there is no "type" for a profile. When generating the health-params.json for traffic monitor, ops do not know which profile is for edge or middle or router, etc. So in traffic ops code, it use the convention that: profile starting with "RASCAL" is a traffic monitor profile profile starting with "CCR" is a traffic router profile profile starting with "EDGE" is an edge server profile profile starting with "MID" is a middle server profile It is better to add a type for each profile, or make a restriction for the profile name. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-295) Invalid DS regex causes nasty exception and unexpected results Github Issue #514
Dewayne Richardson created TC-295: - Summary: Invalid DS regex causes nasty exception and unexpected results Github Issue #514 Key: TC-295 URL: https://issues.apache.org/jira/browse/TC-295 Project: Traffic Control Issue Type: Bug Reporter: Dewayne Richardson Fix For: 2.0.0 If a host regex (probably others) is specified as a plain string, rather than a real regex (e.g.: test vs ..mydeliveryservice..), the following exception occurs in Traffic Router, and the user would have to be watching the logs to see that something went wrong. Additionally, it is not clear why the failure occurred. Improve TO in general such that the regex is clearly defined (documented?) and potentially checked so that it doesn't get added to the CRConfig until it is what we expect to see. Additionally, discuss whether we want to support specific strings (e.g.: test) instead of a full regex. Doing so seems to be counter to the intent of the regex in the first place, so I do not think that this is a viable option at this time. WARN 2015-09-01T14:25:07.237 [New I/O worker #1] com.comcast.cdn.traffic_control.traffic_router.core.util.PeriodicResourceUpdater - 1 java.lang.ArrayIndexOutOfBoundsException: 1 at com.comcast.cdn.traffic_control.traffic_router.core.dns.ZoneManager.populateZoneMap(ZoneManager.java:311) at com.comcast.cdn.traffic_control.traffic_router.core.dns.ZoneManager.generateZones(ZoneManager.java:132) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-291) GenIso can't handle concurrent requests
Dewayne Richardson created TC-291:
-
Summary: GenIso can't handle concurrent requests
Key: TC-291
URL: https://issues.apache.org/jira/browse/TC-291
Project: Traffic Control
Issue Type: Bug
Components: Traffic Ops
Affects Versions: 2.0.0
Reporter: Dewayne Richardson
Because GenIso always changes the same files (no temporary directories
created), it can't handle concurrent requests. We sometimes send commands to
create 10 Edge Caches at the same time and we found out that the wrong IP
address shows up on servers.
I've got the code to fix it up (but need to sign our paperwork). But our
GenIso.pm now deviates from what's in Traffic Ops because we wanted to keep the
1.0.0 functionality (don't use the install_cfg directory, keep using the simple
network line).
Suggestion: We should have a parameter to call different ISO generator scripts.
Seems like this is implementation specific and not really a core function of
Traffic Ops.
Basic changes :
use File::Temp;
use File::Copy::Recursive;
my $tmpdir = File::Temp::tempdir(CLEANUP => 1);
...
GenIso.pm:my $tmp = File::Copy::Recursive::dircopy($dir,$tmpdir);
GenIso.pm: my $cfg_dir = "$tmpdir/$install_cfg";
GenIso.pm: print STUF "Dir== $tmpdir\n";
GenIso.pm: my $cmd = "mkisofs -joliet-long -input-charset utf-8 -b
isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4
-boot-info-table -R -J -v -T $tmpdir";
GenIso.pm: open(IN, "<$tmpdir/ks.src") || die("$tmpdir/ks.src:$!");
GenIso.pm: open (OUT, ">$tmpdir/ks.cfg") || die("$tmpdir/ks.cfg:$!");
GenIso.pm:File::Path::rmtree $tmpdir;
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (TC-281) yum upgrade on traffic_ops-2.1.0-6170.0ecd2765.el7.x86_64
Dewayne Richardson created TC-281: - Summary: yum upgrade on traffic_ops-2.1.0-6170.0ecd2765.el7.x86_64 Key: TC-281 URL: https://issues.apache.org/jira/browse/TC-281 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Affects Versions: 2.0.0, 2.1.0 Reporter: Dewayne Richardson Assignee: Dan Kirkwood rpm .spec for 'upgrade' is still referencing the Snapshots directory Executed: $ yum upgrade traffic_ops Error below: --- Backing up config files. tar: app/public/*Snapshots: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors Stopping traffic_ops (via systemctl): [ OK ] Updating : traffic_ops-2.1.0-6170.0ecd2765.el7.x86_64 1/2 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-279) Postinstall Sample Profiles out of date
Dewayne Richardson created TC-279: - Summary: Postinstall Sample Profiles out of date Key: TC-279 URL: https://issues.apache.org/jira/browse/TC-279 Project: Traffic Control Issue Type: Improvement Components: Traffic Ops Affects Versions: 2.1.0 Reporter: Dewayne Richardson Priority: Minor Fix For: 2.1.0 The existing sample profiles need to be update and the process documented -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (TC-264) Traffic Monitor Proxy should not be part of default parameter
[ https://issues.apache.org/jira/browse/TC-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson resolved TC-264. --- Resolution: Fixed Fix Version/s: 2.1.0 Removed the tm.traffic_mon_fwd_proxy from a fresh install in post install > Traffic Monitor Proxy should not be part of default parameter > -- > > Key: TC-264 > URL: https://issues.apache.org/jira/browse/TC-264 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops >Affects Versions: 1.8.0 >Reporter: Steve Malenfant >Assignee: Dewayne Richardson >Priority: Minor > Labels: documentation, newbie > Fix For: 2.1.0 > > > During Traffic Portal integration, the API could not reach Traffic Ops. Found > out during debugging session that the `tm.traffic_mon_fwd_proxy` parameter > was defined as orphaned variable and was actually being used. > Few things : > 1 - This parameter is set at install as an orphan. > 2 - This parameter is used even if not assigned to the GLOBAL profile > 3 - The code is silent about the proxy not being reachable > 4 - The documentation doesn't mention that parameter and which component uses > it. > I would suggest the following : > 1 - Removed from default parameter install AND/OR 2) > 2 - Add in the code that the profile "GLOBAL" needs assigned. Variable not > assigned to a profile should not be used. > 3 - Add logging to Traffic Ops (DEBUG at least) showing a proxy is being used > and show the failed proxy requests > 4 - Mention that profile parameter in the documentation > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (TC-264) Traffic Monitor Proxy should not be part of default parameter
[ https://issues.apache.org/jira/browse/TC-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson reassigned TC-264: - Assignee: Dewayne Richardson > Traffic Monitor Proxy should not be part of default parameter > -- > > Key: TC-264 > URL: https://issues.apache.org/jira/browse/TC-264 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops >Affects Versions: 1.8.0 >Reporter: Steve Malenfant >Assignee: Dewayne Richardson >Priority: Minor > Labels: documentation, newbie > > During Traffic Portal integration, the API could not reach Traffic Ops. Found > out during debugging session that the `tm.traffic_mon_fwd_proxy` parameter > was defined as orphaned variable and was actually being used. > Few things : > 1 - This parameter is set at install as an orphan. > 2 - This parameter is used even if not assigned to the GLOBAL profile > 3 - The code is silent about the proxy not being reachable > 4 - The documentation doesn't mention that parameter and which component uses > it. > I would suggest the following : > 1 - Removed from default parameter install AND/OR 2) > 2 - Add in the code that the profile "GLOBAL" needs assigned. Variable not > assigned to a profile should not be used. > 3 - Add logging to Traffic Ops (DEBUG at least) showing a proxy is being used > and show the failed proxy requests > 4 - Mention that profile parameter in the documentation > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (TC-264) Traffic Monitor Proxy should not be part of default parameter
[ https://issues.apache.org/jira/browse/TC-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15991299#comment-15991299 ] Dewayne Richardson commented on TC-264: --- This is fixed in master, so will be in 2.1 > Traffic Monitor Proxy should not be part of default parameter > -- > > Key: TC-264 > URL: https://issues.apache.org/jira/browse/TC-264 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops >Affects Versions: 1.8.0 >Reporter: Steve Malenfant >Priority: Minor > Labels: documentation, newbie > > During Traffic Portal integration, the API could not reach Traffic Ops. Found > out during debugging session that the `tm.traffic_mon_fwd_proxy` parameter > was defined as orphaned variable and was actually being used. > Few things : > 1 - This parameter is set at install as an orphan. > 2 - This parameter is used even if not assigned to the GLOBAL profile > 3 - The code is silent about the proxy not being reachable > 4 - The documentation doesn't mention that parameter and which component uses > it. > I would suggest the following : > 1 - Removed from default parameter install AND/OR 2) > 2 - Add in the code that the profile "GLOBAL" needs assigned. Variable not > assigned to a profile should not be used. > 3 - Add logging to Traffic Ops (DEBUG at least) showing a proxy is being used > and show the failed proxy requests > 4 - Mention that profile parameter in the documentation > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-233) db/admin.pl needs updating to manage the postgres superuser
Dewayne Richardson created TC-233: - Summary: db/admin.pl needs updating to manage the postgres superuser Key: TC-233 URL: https://issues.apache.org/jira/browse/TC-233 Project: Traffic Control Issue Type: Improvement Components: Traffic Ops Reporter: Dewayne Richardson Fix For: 2.0.0 The admin.pl with Postgres needed to be updated to support the 'postgres' user and 'traffic_ops' users according to privileges. This is needed to support the 'postinstall' script so that the TrafficOps rpm can be installed properly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (TC-40) Traffic Ops UI Tools.DB Dump doesn't work
[ https://issues.apache.org/jira/browse/TC-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson reopened TC-40: -- According to Dan Kirkwood there are still issues > Traffic Ops UI Tools.DB Dump doesn't work > - > > Key: TC-40 > URL: https://issues.apache.org/jira/browse/TC-40 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops >Affects Versions: 2.0.0 > Environment: "psql" branch >Reporter: Dewayne Richardson >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (TC-154) Adding cronjob to automatically clean iso generation
[ https://issues.apache.org/jira/browse/TC-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson resolved TC-154. --- Resolution: Fixed Resolved with PR 292 > Adding cronjob to automatically clean iso generation > > > Key: TC-154 > URL: https://issues.apache.org/jira/browse/TC-154 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops >Affects Versions: 2.0.0 >Reporter: Dewayne Richardson >Priority: Minor > Fix For: 2.0.0 > > > Need a cronjob to be added to automatically clean ISOs older than 7 days -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (TC-154) Adding cronjob to automatically clean iso generation
Dewayne Richardson created TC-154: - Summary: Adding cronjob to automatically clean iso generation Key: TC-154 URL: https://issues.apache.org/jira/browse/TC-154 Project: Traffic Control Issue Type: Improvement Components: Traffic Ops Affects Versions: 2.0.0 Reporter: Dewayne Richardson Priority: Minor Fix For: 2.0.0 Need a cronjob to be added to automatically clean ISOs older than 7 days -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (TC-40) Traffic Ops UI Tools.DB Dump doesn't work
[ https://issues.apache.org/jira/browse/TC-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-40. resolved as fixed > Traffic Ops UI Tools.DB Dump doesn't work > - > > Key: TC-40 > URL: https://issues.apache.org/jira/browse/TC-40 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops >Affects Versions: 2.0.0 > Environment: "psql" branch >Reporter: Dewayne Richardson >Priority: Minor > Fix For: 2.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-55) Multi Delivery Services With Same Domain Name and Different Path Prefixes
[ https://issues.apache.org/jira/browse/TC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705828#comment-15705828 ] Dewayne Richardson commented on TC-55: -- This feature seems to be in high demand, but we need to facilitate some discussion regarding the problem and the proposed solution. Once we have consensus about the design, typically the implementation is then started, which will result in a pull request. Once the PR has been reviewed and changed (if needed), then we will accept the PR. Please send future requirement requests and your design documents to the d...@trafficcontrol.incubator.apache.org mailing list so the discussion can begin. Thanks, -Dewayne > Multi Delivery Services With Same Domain Name and Different Path Prefixes > - > > Key: TC-55 > URL: https://issues.apache.org/jira/browse/TC-55 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops, Traffic Ops API >Affects Versions: 1.7.0 >Reporter: Jifeng Yang > > Enhance TC to support: > Multi Delivery Services With Same Domain Name and Different Path Prefixes > Details please ref the link: > https://docs.google.com/document/d/19-TZ6ODla_vdiYqZajbpRiOpLvpbJxil1SvIm44zb-0/edit?usp=sharing -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TC-49) Riak based test cases are broken in psql-rebase
[ https://issues.apache.org/jira/browse/TC-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-49. Resolution: Resolved Fix Version/s: 2.0.0 > Riak based test cases are broken in psql-rebase > --- > > Key: TC-49 > URL: https://issues.apache.org/jira/browse/TC-49 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops >Affects Versions: 2.0.0 >Reporter: Dewayne Richardson >Priority: Minor > Fix For: 2.0.0 > > > Test cases that failed: > traffic_ops/app/t/api/1.1/deliveryservice/keys_url_sig.t > traffic_ops/app/t/api/1.1/deliveryservice/ssl_keys.t -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-49) Riak based test cases are broken in psql-rebase
Dewayne Richardson created TC-49: Summary: Riak based test cases are broken in psql-rebase Key: TC-49 URL: https://issues.apache.org/jira/browse/TC-49 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Affects Versions: 2.0.0 Reporter: Dewayne Richardson Priority: Minor Test cases that failed: traffic_ops/app/t/api/1.1/deliveryservice/keys_url_sig.t traffic_ops/app/t/api/1.1/deliveryservice/ssl_keys.t -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-48) Steering Delivery Test Cases
Dewayne Richardson created TC-48: Summary: Steering Delivery Test Cases Key: TC-48 URL: https://issues.apache.org/jira/browse/TC-48 Project: Traffic Control Issue Type: Bug Components: Traffic Ops, Traffic Ops API Affects Versions: 2.0.0 Reporter: Dewayne Richardson Priority: Minor Temporarily removed the "t/api/1.2/steering_internal.t" so this will have to be revisited and pulled from 1.8.x after 'psql-rebase' has been merged into 'master' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-47) Test Cases for Traffic Ops in the psql-rebase branch are broken
Dewayne Richardson created TC-47: Summary: Test Cases for Traffic Ops in the psql-rebase branch are broken Key: TC-47 URL: https://issues.apache.org/jira/browse/TC-47 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Affects Versions: 2.0.0 Reporter: Dewayne Richardson Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TC-41) Traffic Ops route returns 500 Internal Error
[
https://issues.apache.org/jira/browse/TC-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dewayne Richardson closed TC-41.
Resolution: Fixed
Fixed
> Traffic Ops route returns 500 Internal Error
>
>
> Key: TC-41
> URL: https://issues.apache.org/jira/browse/TC-41
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
>Affects Versions: 1.8.0, 2.0.0
>Reporter: Dewayne Richardson
>Priority: Minor
> Fix For: 1.8.0, 2.0.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> GET /aadata/ProfileParameter/cachegroup/all fails with 500 Internal Error
> Fails with Traffic Ops Error:
> Traffic Ops fatal error occurred while processing your request.
> Error at line 242 ( while ( my $row = $rs->next ) {)
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st
> execute failed: Unknown column 'cachegroup' in 'where clause' [for Statement
> "SELECT me.id, me.name, me.config_file, me.value, me.last_updated, me.secure,
> profile.name FROM parameter me LEFT JOIN profile_parameter
> profile_parameters_2 ON profile_parameters_2.parameter = me.id LEFT JOIN
> profile profile ON profile.id = profile_parameters_2.profile WHERE (
> cachegroup IS NULL ) GROUP BY me.id, me.name, me.config_file, me.value,
> me.last_updated, me.secure, profile.name"] at
> /opt/traffic_ops/app/lib/UI/Cdn.pm line 242
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TC-41) Traffic Ops route returns 500 Internal Error
[
https://issues.apache.org/jira/browse/TC-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dewayne Richardson updated TC-41:
-
Description:
GET /aadata/ProfileParameter/cachegroup/all fails with 500 Internal Error
Fails with Traffic Ops Error:
Traffic Ops fatal error occurred while processing your request.
Error at line 242 ( while ( my $row = $rs->next ) {)
DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st
execute failed: Unknown column 'cachegroup' in 'where clause' [for Statement
"SELECT me.id, me.name, me.config_file, me.value, me.last_updated, me.secure,
profile.name FROM parameter me LEFT JOIN profile_parameter profile_parameters_2
ON profile_parameters_2.parameter = me.id LEFT JOIN profile profile ON
profile.id = profile_parameters_2.profile WHERE ( cachegroup IS NULL ) GROUP BY
me.id, me.name, me.config_file, me.value, me.last_updated, me.secure,
profile.name"] at /opt/traffic_ops/app/lib/UI/Cdn.pm line 242
was:GET /aadata/ProfileParameter/cachegroup/all fails with 500 Internal Error
> Traffic Ops route returns 500 Internal Error
>
>
> Key: TC-41
> URL: https://issues.apache.org/jira/browse/TC-41
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
>Affects Versions: 1.8.0, 2.0.0
>Reporter: Dewayne Richardson
>Priority: Minor
> Fix For: 1.8.0, 2.0.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> GET /aadata/ProfileParameter/cachegroup/all fails with 500 Internal Error
> Fails with Traffic Ops Error:
> Traffic Ops fatal error occurred while processing your request.
> Error at line 242 ( while ( my $row = $rs->next ) {)
> DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st
> execute failed: Unknown column 'cachegroup' in 'where clause' [for Statement
> "SELECT me.id, me.name, me.config_file, me.value, me.last_updated, me.secure,
> profile.name FROM parameter me LEFT JOIN profile_parameter
> profile_parameters_2 ON profile_parameters_2.parameter = me.id LEFT JOIN
> profile profile ON profile.id = profile_parameters_2.profile WHERE (
> cachegroup IS NULL ) GROUP BY me.id, me.name, me.config_file, me.value,
> me.last_updated, me.secure, profile.name"] at
> /opt/traffic_ops/app/lib/UI/Cdn.pm line 242
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (TC-41) Traffic Ops route returns 500 Internal Error
Dewayne Richardson created TC-41: Summary: Traffic Ops route returns 500 Internal Error Key: TC-41 URL: https://issues.apache.org/jira/browse/TC-41 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Affects Versions: 1.8.0, 2.0.0 Reporter: Dewayne Richardson Priority: Minor Fix For: 1.8.0, 2.0.0 GET /aadata/ProfileParameter/cachegroup/all fails with 500 Internal Error -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-40) Traffic Ops UI Tools.DB Dump doesn't work
Dewayne Richardson created TC-40: Summary: Traffic Ops UI Tools.DB Dump doesn't work Key: TC-40 URL: https://issues.apache.org/jira/browse/TC-40 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Affects Versions: 2.0.0 Environment: "psql" branch Reporter: Dewayne Richardson Priority: Minor Fix For: 2.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-32) Improve efficiency of ATS config generation
[ https://issues.apache.org/jira/browse/TC-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654741#comment-15654741 ] Dewayne Richardson commented on TC-32: -- Can you also show the example contexts for each of those routes to get an idea? For example: /api/ > Improve efficiency of ATS config generation > --- > > Key: TC-32 > URL: https://issues.apache.org/jira/browse/TC-32 > Project: Traffic Control > Issue Type: Improvement > Components: Traffic Ops API >Reporter: Derek Gelinas >Assignee: Derek Gelinas > Fix For: 1.9.0 > > > Currently when generating ATS configuration files, each server calls for its > individual files from traffic ops. This is a very database-intensive process > that is not scalable enough. I propose the following changes: > 1) Generate the configuration files only as many times as needed - many files > are the same (or can be) for the entire CDN or server profile. > 2) Once generated, the files can be cached locally. Requests for the files > by ORT will result in pulling down these cached files rather than many > hundreds of DB queries each time. > 3) Migrate the routes for these files to the API. Each call will have > multiple options - a request made with no options would return the cached > file, another option would return the current DB data, and a third option > would update the cached file with the current information in the DB. > 4) When an update is queued, generate and cache the configuration files, then > activate the update flag for the relevant servers once the cached file > generation is completed. > In this way, triggering updates for the caches will result in an initial > increase in activity as traffic ops generates the files needed, followed by > the much lower impact of the files themselves being requested by the caches. > I believe we can cut down the number of server-specific configuration files > to only 5 intially, and potentially fewer by having ORT fill in certain > fields on files like records.config with local data during processing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TC-33) GET /api/1.2/deliveryservices.json?orderby=name returns HTTP 500
[ https://issues.apache.org/jira/browse/TC-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-33. Resolution: Fixed Closed by Pull Request: https://github.com/apache/incubator-trafficcontrol/pull/57 > GET /api/1.2/deliveryservices.json?orderby=name returns HTTP 500 > > > Key: TC-33 > URL: https://issues.apache.org/jira/browse/TC-33 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops API >Affects Versions: 2.0.0 >Reporter: Dewayne Richardson >Priority: Minor > > when hitting that route the error is 500 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-33) GET /api/1.2/deliveryservices.json?orderby=name returns HTTP 500
[ https://issues.apache.org/jira/browse/TC-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647902#comment-15647902 ] Dewayne Richardson commented on TC-33: -- Closed by Pull Request: https://github.com/apache/incubator-trafficcontrol/pull/57 > GET /api/1.2/deliveryservices.json?orderby=name returns HTTP 500 > > > Key: TC-33 > URL: https://issues.apache.org/jira/browse/TC-33 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops API >Affects Versions: 2.0.0 >Reporter: Dewayne Richardson >Priority: Minor > > when hitting that route the error is 500 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-33) GET /api/1.2/deliveryservices.json?orderby=name returns HTTP 500
Dewayne Richardson created TC-33: Summary: GET /api/1.2/deliveryservices.json?orderby=name returns HTTP 500 Key: TC-33 URL: https://issues.apache.org/jira/browse/TC-33 Project: Traffic Control Issue Type: Bug Components: Traffic Ops API Affects Versions: 2.0.0 Reporter: Dewayne Richardson Priority: Minor when hitting that route the error is 500 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (TC-31) /CRConfig-Snapshots/kabletown/CRConfig.json is 404
[ https://issues.apache.org/jira/browse/TC-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dewayne Richardson closed TC-31. Resolution: Invalid That route only exists on the local file system that has been snapshotted > /CRConfig-Snapshots/kabletown/CRConfig.json is 404 > -- > > Key: TC-31 > URL: https://issues.apache.org/jira/browse/TC-31 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Ops >Affects Versions: 2.0.0 >Reporter: Dewayne Richardson > > /CRConfig-Snapshots/over-the-top/CRConfig.json is now a 404, need to update > the app/lib/TrafficOps.pm to use $r->get versus $->route -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-31) /CRConfig-Snapshots/over-the-top/CRConfig.json is 404
Dewayne Richardson created TC-31: Summary: /CRConfig-Snapshots/over-the-top/CRConfig.json is 404 Key: TC-31 URL: https://issues.apache.org/jira/browse/TC-31 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Affects Versions: 2.0.0 Reporter: Dewayne Richardson /CRConfig-Snapshots/over-the-top/CRConfig.json is now a 404, need to update the app/lib/TrafficOps.pm to use $r->get versus $->route -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-30) traffic_ops/app/db/create_tables.sql still has the 'to_user' owner assignment
Dewayne Richardson created TC-30: Summary: traffic_ops/app/db/create_tables.sql still has the 'to_user' owner assignment Key: TC-30 URL: https://issues.apache.org/jira/browse/TC-30 Project: Traffic Control Issue Type: Bug Components: Traffic Ops Affects Versions: 2.0.0 Reporter: Dewayne Richardson For postgres the database "role" should match the database "name", therefore the current role of "to_user" does not conform to that in the create_tables.sql. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
