[GitHub] incubator-trafficcontrol pull request #232: goTM logging cleanup
Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/232 --- 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] [Assigned] (TC-114) Fail to restart Tomcat when TM start before config pulled
[ https://issues.apache.org/jira/browse/TC-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Mitchell reassigned TC-114: -- Assignee: Zhilin Huang > Fail to restart Tomcat when TM start before config pulled > - > > Key: TC-114 > URL: https://issues.apache.org/jira/browse/TC-114 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Monitor >Affects Versions: 1.7.0 >Reporter: Zhilin Huang >Assignee: Zhilin Huang > > Here are the steps to reproduce it: > 1) Clean install traffic monitor > 2) Start tomcat and check the tomcat process ID > 3) Add traffic monitor to traffic ops > 4) Run traffic monitor config init perl script > 5) Restart traffic monitor and check the tomcat process ID > Check the process id, you will find the traffic monitor is not restarted at > all. And the traffic monitor will be always in error status except kill it by > "kill -9". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TC-114) Fail to restart Tomcat when TM start before config pulled
[ https://issues.apache.org/jira/browse/TC-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840345#comment-15840345 ] Jeremy Mitchell commented on TC-114: ok, you were not a "contributor". you are now so I assigned it to you. thanks! > Fail to restart Tomcat when TM start before config pulled > - > > Key: TC-114 > URL: https://issues.apache.org/jira/browse/TC-114 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Monitor >Affects Versions: 1.7.0 >Reporter: Zhilin Huang >Assignee: Zhilin Huang > > Here are the steps to reproduce it: > 1) Clean install traffic monitor > 2) Start tomcat and check the tomcat process ID > 3) Add traffic monitor to traffic ops > 4) Run traffic monitor config init perl script > 5) Restart traffic monitor and check the tomcat process ID > Check the process id, you will find the traffic monitor is not restarted at > all. And the traffic monitor will be always in error status except kill it by > "kill -9". -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (TC-122) TO DBdump no longer works with Postgres
Jeremy Mitchell created TC-122:
--
Summary: TO DBdump no longer works with Postgres
Key: TC-122
URL: https://issues.apache.org/jira/browse/TC-122
Project: Traffic Control
Issue Type: Bug
Components: Traffic Ops
Affects Versions: 2.0.0
Reporter: Jeremy Mitchell
Fix For: 2.0.0
The following route produces an empty file:
$r->get('/dbdump')->over( authenticated => 1 )->to( 'GenDbDump#dbdump',
namespace => $namespace );
I think pg_dump requires a password or something. maybe ~/.pgpass is the answer?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-trafficcontrol pull request #233: refactored functionality to the ...
GitHub user dewrich opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/233 refactored functionality to the migrate.sh for automation You can merge this pull request into a Git repository by running: $ git pull https://github.com/dewrich/incubator-trafficcontrol dewrich/enhancement/pg-migration Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/233.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 #233 commit 911a81d0b0c36a08876625d1e3e9ad01c2b7d251 Author: Dewayne Richardson Date: 2017-01-26T21:43:47Z refactored functionality to the migrate.sh for automation --- 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 #234: Move TM2 to trafficcontrol/traff...
GitHub user rob05c opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/234 Move TM2 to trafficcontrol/traffic_monitor_golang, add Docker build You can merge this pull request into a Git repository by running: $ git pull https://github.com/rob05c/incubator-trafficcontrol tm2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/234.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 #234 commit 87699e2decbdef0ff7775857367976b42f118878 Author: Robert Butts Date: 2017-01-26T21:31:39Z Move TM2 to trafficcontrol/traffic_monitor_golang commit 9512bf2a17e652fef036a7ad8feb2d082a63169e Author: Robert Butts Date: 2017-01-26T21:34:40Z Add TM2 docker build --- 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 #233: refactored functionality to the ...
Github user dangogh commented on a diff in the pull request: https://github.com/apache/incubator-trafficcontrol/pull/233#discussion_r98099812 --- Diff: traffic_ops/app/db/pg-migration/README.md --- @@ -1,17 +1,10 @@ -# Converting existing mysql `traffic_ops` database to postgres +# Converts existing mysql `traffic_ops` database to postgres * Requires a recent ( 1.12 ) version of `docker-engine` and `docker-compose`. -* Modify the mysql.env for your existing Mysql Database - -* Modify the postgres.env for your new Postgres Database - (NOTE: do not set the POSTGRES_HOST to 'localhost' it needs to be the IP address or DNS available hostname so that the container can reach out to Postgres) - +* Modify the mysql-to-postgres.env file for the parameters in your Migration * Ensure that your new Postgres service is running (local or remote) * Run the Mysql to Postgres Migration Docker flow - * `$ docker-compose -f pgmigration.yml down -v && docker-compose -f pgmigration.yml build && TO_SERVER=https://traffic_ops.kabletown.com TO_USER=me TO_PASSWORD='my!passwd' docker-compose -f pgmigration.yml up` - -* Run the Postgres datatype conversion - * `$ docker-compose -f convert.yml up` + * `sh migrate.sh --- End diff -- minor -- missing closing backquote --- 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 #233: refactored functionality to the ...
Github user dangogh commented on a diff in the pull request:
https://github.com/apache/incubator-trafficcontrol/pull/233#discussion_r98100084
--- Diff: traffic_ops/app/db/pg-migration/migrate.sh ---
@@ -0,0 +1,90 @@
+#!/bin/bash
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+#
+
+: ${TO_SERVER?"Please the TO_SERVER environment variable: ie:
https://kabletown.net"}
+: ${TO_USER?"Please the TO_USER environment variable: ie: "}
+: ${TO_PASSWORD?"Please the TO_PASSWORD environment variable: ie: "}
+
--- End diff --
minor -- missing a word: Please ->set<- the ...
---
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 #233: refactored functionality to the ...
Github user dangogh commented on a diff in the pull request: https://github.com/apache/incubator-trafficcontrol/pull/233#discussion_r98100403 --- Diff: traffic_ops/app/db/pg-migration/mysql-to-postgres.env --- @@ -0,0 +1,43 @@ +#!/bin/bash +# +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the License. +# You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +# + +#Traffic Ops Settings +# The following configs should be configured to point to the +# Traffic Ops instances that is connected to the MySQL that +# you want to convert +TO_SERVER=to_url +TO_USER=(your_user) +TO_PASSWORD=(your_password) + +# Staging Mysql +# These variables are for the "staging" Docker MySQL instance that is used +# to load the Traffic Ops "dbdump" into. ONLY change the MYSQL_HOST variable +# Leave the other variables. +MYSQL_HOST=( the_ip_address_running_this_migration ) +MYSQL_PORT=3306 +MYSQL_DATABASE=traffic_ops_db +MYSQL_USER=to_user +MYSQL_PASSWORD=twelve +MYSQL_RANDOM_ROOT_PASSWORD=yes + +# The following +# New Producion Postgres Settings, these variables should be changed for the Postgres --- End diff -- sp --- 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] [Resolved] (TC-103) GET /update/:host_name should return boolean values
[
https://issues.apache.org/jira/browse/TC-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Mitchell resolved TC-103.
Resolution: Fixed
> GET /update/:host_name should return boolean values
> ---
>
> Key: TC-103
> URL: https://issues.apache.org/jira/browse/TC-103
> Project: Traffic Control
> Issue Type: Improvement
> Components: Traffic Ops, Traffic Ops API, Traffic Ops ORT
>Affects Versions: 2.0.0
>Reporter: Jeremy Mitchell
>Assignee: Jeremy Mitchell
>Priority: Minor
> Labels: postgres
> Fix For: 2.0.0
>
>
> GET /update/:host_name returns
> [ { "upd_pending": 0, "parent_pending": "0", "status": "REPORTED",
> "host_id": 22, "host_name": "foo-bar" } ]
> it should return
> [ { "upd_pending": true|false, "parent_pending": true|false, "status":
> "REPORTED", "host_id": 22, "host_name": "foo-bar" } ]
> since TO ORT relies heavily on this endpoint, ensure that ORT can handle
> booleans as opposed to int/string 0|1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-trafficcontrol pull request #233: refactored functionality to the ...
Github user asfgit closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/233 --- 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. ---
