[GitHub] incubator-trafficcontrol issue #768: Tenant parent - on delete cascade
Github user MattMills commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/768 In that case, why would this be an ON DELETE CASCADE, rather than an ON DELETE RESTRICT? --- 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 #344: TO Install instructions
Github user MattMills commented on a diff in the pull request: https://github.com/apache/incubator-trafficcontrol/pull/344#discussion_r106282322 --- Diff: traffic_ops/INSTALL.md --- @@ -88,14 +107,18 @@ We need to tell carton where it is so the `DBD::Pg` module is installed correctl - if logging data needed, change ERROR to DEBUG on first line ## Initialize the db + $ cd /opt/traffic_ops/app $ PERL5LIB=$(pwd)/lib:$(pwd)/local/lib/perl5 db/admin.pl --env=production setup ## Install any extensions needed + - install in /opt/traffic_ops_extensions ## Install `openssl` certs (or use this to generate them) + - `sudo /opt/traffic_ops/install/bin/generateCert` ## Install web dependencies + - `sudo /opt/traffic_ops/install/bin/download_web_deps` --- End diff -- What about the additional data in https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops/install/data/json that used to be loaded by (I think) postinstall, but now isn't loaded, which includes the default profiles and parameters? If we don't have a way to load them today, I think it's worth putting a warning in the install instructions that they won't quite be able to get to a fully functioning install yet. --- 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 #344: TO Install instructions
Github user MattMills commented on a diff in the pull request: https://github.com/apache/incubator-trafficcontrol/pull/344#discussion_r106281138 --- Diff: traffic_ops/INSTALL.md --- @@ -8,53 +8,71 @@ Instructions are here: https://yum.postgresql.org/ - grab the link for CentOS 7 and install: -$ sudo yum install https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-.noarch.rpm +$ sudo yum install https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-.noarch.rpm + + NOTE: get a valid link from https://yum.postgresql.org/ with the correct version number. + - install `postgresql96` (for psql commands) and `postgresql96-devel` (for includes/libraries needed to install `DBD::Pg` perl library) + $ sudo yum install postgresql96 postgresql96-devel ## Install Postgres 9.6 server (in a container or on the host) ### on the host: + $ sudo yum install postgresql96-server ### -or- in a container NOTE: you do *not* need postgresql96-server if running postgres within a `docker` container. Install `docker` and `docker-compose` using instructions here: + https://docs.docker.com/engine/installation/linux/centos/ + https://docs.docker.com/compose/install/ Add yourself to `docker` group + $ sudo usermod -G docker $USER Remember to logout and login again.. You should see `docker` in your list of groups: $ id uid=9876(myuser) gid=9876(myuser) groups=9876(myuser),990(docker) ... +Edit `mysql-to-postgres.env` to suit your needs. +* modify `POSTGRES_*` vars to apply to new postgres container that will house your database, e.g. + * POSTGRES_USER=postgres + * POSTGRES_PASSWORD=itSas3cre4 + +If migrating from an existing pre-2.0 traffic_ops server (mysql): +* `TO_*` vars for admin access to existing mysql-based `traffic_ops` (to get a db dump), e.g. + * TO_SERVER=https://trafficops.example.com + * TO_USER=dennisr + +* `MYSQL_*` vars to apply to temporary mysql container -- really no need to change.. + Start a docker container to run postgres + $ cd incubator-trafficcontrol/traffic_ops/app/db/pg-migration $ ./start_postgres.sh -Edit `mysql-to-postgres.yml` to suit your needs. -- modify `POSTGRES_*` vars to apply to new postgres container that will house - -If migrating from an existing pre-2.0 traffic_ops server (mysql): -- `TO_*` vars for admin access to existing mysql-based `traffic_ops` (to get a db dump) -- `MYSQL_*` vars to apply to temporary mysql container - Run migration from existing mysql-based `traffic_ops` + $ ./migrate.sh ## Install `traffic_ops` + $ sudo yum install traffic_ops --- End diff -- This won't work outside of Comcast --- 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 #344: TO Install instructions
Github user MattMills commented on a diff in the pull request: https://github.com/apache/incubator-trafficcontrol/pull/344#discussion_r106280949 --- Diff: traffic_ops/INSTALL.md --- @@ -8,53 +8,71 @@ Instructions are here: https://yum.postgresql.org/ - grab the link for CentOS 7 and install: -$ sudo yum install https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-.noarch.rpm +$ sudo yum install https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-.noarch.rpm + + NOTE: get a valid link from https://yum.postgresql.org/ with the correct version number. + --- End diff -- You'll also need a yum install epel-release, since postgres' repo depends on epel. --- 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 #345: [TC-182] Add additional statuses...
Github user MattMills closed the pull request at: https://github.com/apache/incubator-trafficcontrol/pull/345 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] incubator-trafficcontrol issue #345: [TC-182] Add additional statuses into t...
Github user MattMills commented on the issue: https://github.com/apache/incubator-trafficcontrol/pull/345 After looking at this more with Dave, there is a larger underlying problem here affecting more than just statuses. --- 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 #345: [TC-182] Add additional statuses...
GitHub user MattMills opened a pull request: https://github.com/apache/incubator-trafficcontrol/pull/345 [TC-182] Add additional statuses into traffic ops seeds.sql This pr adds additional required statuses into the traffic ops status table fixing TC-182. You can merge this pull request into a Git repository by running: $ git pull https://github.com/MattMills/incubator-trafficcontrol TC-182_fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-trafficcontrol/pull/345.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 #345 commit 536bfe21971c1a757bf3d6a03f3d1fe75acbc4f4 Author: Matt Mills <mmi...@2bn.net> Date: 2017-03-10T15:51:47Z Add additional statuses into traffic ops seeds.sql (TC-182) --- 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. ---
