Thank you Dan, Indeed, moving to postgres would be the right choice, as I want to test the changes on the branch I submit to. I already tested today my dev env with TC 1.8, and I now have some confidence in my its bringup protocol so I can move to a less stable branch.
I used the command you sent. Additionally I had to add a database with the same name, and adjust "pg_hba.conf". My traffic-ops is now up :) I assume (and tried it out), that: 1. In order to run "prove t" I need to run "./db/admin.pl --env=test setup" 2. In order to run "prove t_integration" I need to run "./db/admin.pl --env=integration setup" 3. In order to launch traffic-ops I need to run "./db/admin.pl --env=development setup" Am I correct? It looks like these admin.pl injected data can live together in the same DB without a conflict. Is it true, or should I drop the DB / replace setup when moving from one env to another? Thanks again. Nir On Tue, Jan 24, 2017 at 5:56 PM, Dan Kirkwood <[email protected]> wrote: > sorry -- prematurely sent.. > > Hi Nir, > > It probably is best to continue with postgres rather than starting with > mysql.. > > You need to be running as a user that has superuser privilege on the > postgres db to run the `admin.pl setup`. Try this: > > sudo su - postgres createuser -s -r -d -E <your username> > > and then try the `db/admin.pl ... setup` command again.. > > If you still have problems, please send the command and output you're > seeing and we'll try to help move you along further.. > > -dan > > On Tue, Jan 24, 2017 at 8:50 AM, Dan Kirkwood <[email protected]> wrote: > > Hi Nir, > > > > It probably is best to continue with postgres rather than starting with > mysql.. > > > > You need to be running as a user that has superuser privilege on the > > postgres db to run the `admin.pl setup`. Try this: > > > > sudo su postgres createuser -s > > > > On Tue, Jan 24, 2017 at 8:27 AM, David Neuman <[email protected]> > wrote: > >> First of all, it looks like your documentation is to our old site, you > will > >> want to use http://trafficcontrol.apache.org/docs/latest/index.html in > the > >> future. > >> If you don't have docker and docker-compose on your VM (it would need > to be > >> centos 7.x or above), we should be able to get it working with a > "normal" > >> postgres install; I would start by taking a look at the scripts that > are in > >> `/traffic_control/traffic_ops/app/db/pg-migration`. Maybe @dangogh is > >> familiar enough with the process that he can provide a quick how-to? > >> > >> On Mon, Jan 23, 2017 at 5:14 PM, Nir Sopher <[email protected]> wrote: > >> > >>> Thank you Dave&Dan, > >>> > >>> The pg-migration document assumes I am working in a Docker environment. > >>> Currently I am working on a VM on which I manually installed the > software > >>> requirement list > >>> <http://traffic-control-cdn.net/docs/latest/development/ > >>> traffic_ops.html?#software-requirements> > >>> . > >>> Is there a specification that will allow me to bring up such a Docker? > Am I > >>> practically required t have one in order to work on traffic-ops? > >>> > >>> I tried to configure the postgres myself, but with no success so far. > >>> Anyway, as I'm practically utilizing my dev environment for the first > time, > >>> it may be counter productive to work on an unstable branch. > >>> > >>> 10x, > >>> Nir > >>> > >>> > >>> > >>> > >>> Nir > >>> > >>> On Tue, Jan 24, 2017 at 12:56 AM, Dan Kirkwood <[email protected]> > wrote: > >>> > >>> > The postgresql version is still quite experimental right now. If > you > >>> > are feeling adventurous, we appreciate the help in testing it, but > >>> > you may want to use 1.7.x or 1.8.x with mysql until we have the > >>> > postgresql branch (master) more stable. The master branch will not > >>> > work with mysql at all. > >>> > > >>> > -Dan > >>> > > >>> > On Mon, Jan 23, 2017 at 2:50 PM, Dave Neuman <[email protected]> > wrote: > >>> > > I am certainly not the expert here, but I would start by taking a > look > >>> at > >>> > > the README.md file in traffic_control/traffic_ops/ > app/db/pg-migration. > >>> > You > >>> > > can use that to migrate from mysql to postgres using > docker-compose. > >>> > > > >>> > > —Dave > >>> > > > >>> > > > >>> > > On Mon, Jan 23, 2017 at 2:44 PM, Nir Sopher <[email protected]> > wrote: > >>> > > > >>> > >> Hi, > >>> > >> > >>> > >> I am trying to create a new Traffic-Ops dev environment setup, > >>> following > >>> > >> the instructions in the developer guide. > >>> > >> I encountered however several failures on the way, related to the > >>> > movement > >>> > >> toward postgresql. I therefore installed the relevant postgresql > RPMs. > >>> > >> > >>> > >> I got to the point I have to initilize the values in the > postgresql > >>> > server > >>> > >> in order for the "./db/admin.pl --env=development setup" command > to > >>> > run. > >>> > >> > >>> > >> Should I follow the instructions in "experimental/server/README. > md"? > >>> > >> Is there a way to deactivate the postgresql server and continue to > >>> work > >>> > >> with mysql until postgresql moves out from "experimental" phase? > >>> > >> > >>> > >> 10x, > >>> > >> Nir > >>> > >> > >>> > > >>> >
