Traffic Ops - Installing¶
The user must have the following for a successful minimal install:
- CentOS 7+
- Two machines - physical or virtual -, each with at least two (v)CPUs, 4GB of RAM, and 20 GB of disk space.
- Access to CentOS Base and EPEL repositories
- Access to The Comprehensive Perl Archive Network (CPAN)
Install PostgreSQL Database. For a production install it is best to install PostgreSQL on its own server/VM.
For more information on installing PostgreSQL, see their documentation.
yum update -y yum install -y https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-3.noarch.rpm yum install -y postgresql96-server su - postgres -c '/usr/pgsql-9.6/bin/initdb -A md5 -W' #-W forces the user to provide a superuser (postgres) password
/var/lib/pgsql/9.6/data/pg_hba.confto allow the Traffic Ops instance to access the PostgreSQL server. For example, if the IP address of the machine to be used as the Traffic Ops host is
192.0.2.1add the line
host all all 192.0.2.1/32 md5to the appropriate section of this file.
/var/lib/pgsql/9.6/data/postgresql.conffile to add the appropriate listen_addresses or
listen_addresses = '*', set
timezone = 'UTC', and start the database
systemctl enable postgresql-9.6 systemctl start postgresql-9.6 systemctl status postgresql-9.6 # Prints the status of the PostgreSQL service, to prove it's running
traffic_ops-version string.rpmfile using the instructions under the Building Traffic Control page.
Install a PostgreSQL client on the Traffic Ops host
yum install -y https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-3.noarch.rpm
Install the Traffic Ops RPM. The Traffic Ops RPM file should have been built in an earlier step.
yum install -y ./dist/traffic_ops-3.0.0-xxxx.yyyyyyy.el7.x86_64.rpm
This will install the PostgreSQL client,
psqlas a dependency.
Login to the Database from the Traffic Ops machine. At this point you should be able to login from the Traffic Ops (hostname
toin the example) host to the PostgreSQL (hostname
pgin the example) host
to-# psql -h pg -U postgres Password for user postgres: psql (9.6.3) Type "help" for help. postgres=#
Create the user and database. By default, Traffic Ops will expect to connect as the
traffic_opsuser to the
to-# psql -U postgres -h pg -c "CREATE USER traffic_ops WITH ENCRYPTED PASSWORD 'tcr0cks';" Password for user postgres: CREATE ROLE to-# createdb traffic_ops --owner traffic_ops -U postgres -h pg Password: to-#
Now, run the following command as the root user (or with
postinstallscript will first get all required Perl packages from CPAN. This may take a while, expect up to 30 minutes on the first install. If there are any prompts in this phase, please just answer with the defaults (some CPAN installs can prompt for install questions). When this phase is complete, you will see
Complete! Modules were installed into /opt/traffic_ops/app/local. Some additional files will be installed, and then it will proceed with the next phase of the install, where it will ask you about the local environment for your CDN. Please make sure you remember all your answers and verify that the database answers match the information previously used to create the database.
to-# /opt/traffic_ops/install/bin/postinstall ... ===========/opt/traffic_ops/app/conf/production/database.conf=========== Database type [Pg]: Database type: Pg Database name [traffic_ops]: Database name: traffic_ops Database server hostname IP or FQDN [localhost]: pg Database server hostname IP or FQDN: pg Database port number : Database port number: 5432 Traffic Ops database user [traffic_ops]: Traffic Ops database user: traffic_ops Password for Traffic Ops database user: Re-Enter Password for Traffic Ops database user: Writing json to /opt/traffic_ops/app/conf/production/database.conf Database configuration has been saved ===========/opt/traffic_ops/app/db/dbconf.yml=========== Database server root (admin) user [postgres]: Database server root (admin) user: postgres Password for database server admin: Re-Enter Password for database server admin: Download Maxmind Database? [yes]: Download Maxmind Database?: yes ===========/opt/traffic_ops/app/conf/cdn.conf=========== Generate a new secret? [yes]: Generate a new secret?: yes Number of secrets to keep? : Number of secrets to keep?: 10 Not setting up ldap ===========/opt/traffic_ops/install/data/json/users.json=========== Administration username for Traffic Ops [admin]: Administration username for Traffic Ops: admin Password for the admin user: Re-Enter Password for the admin user: Writing json to /opt/traffic_ops/install/data/json/users.json ===========/opt/traffic_ops/install/data/json/openssl_configuration.json=========== Do you want to generate a certificate? [yes]: Country Name (2 letter code): US State or Province Name (full name): CO Locality Name (eg, city): Denver Organization Name (eg, company): Super CDN, Inc Organizational Unit Name (eg, section): Common Name (eg, your name or your server's hostname): RSA Passphrase: Re-Enter RSA Passphrase: ===========/opt/traffic_ops/install/data/json/profiles.json=========== Traffic Ops url [https://localhost]: Traffic Ops url: https://localhost Human-readable CDN Name. (No whitespace, please) [kabletown_cdn]: blue_cdn Human-readable CDN Name. (No whitespace, please): blue_cdn DNS sub-domain for which your CDN is authoritative [cdn1.kabletown.net]: blue-cdn.supercdn.net DNS sub-domain for which your CDN is authoritative: blue-cdn.supercdn.net Writing json to /opt/traffic_ops/install/data/json/profiles.json Downloading Maxmind data --2017-06-11 15:32:41-- http://geolite.maxmind.com/download/geoip/database/GeoLite2-City.mmdb.gz Resolving geolite.maxmind.com (geolite.maxmind.com)... 2400:cb00:2048:1::6810:262f, 2400:cb00:2048:1::6810:252f, 220.127.116.11, ... Connecting to geolite.maxmind.com (geolite.maxmind.com)|2400:cb00:2048:1::6810:262f|:80... connected. ... much SQL output skipped Starting Traffic Ops Restarting traffic_ops (via systemctl): [ OK ] Waiting for Traffic Ops to restart Success! Postinstall complete.
¶ Field Description Database type This requests the type of database to be used. Answer with the default - ‘Pg’ to indicate a PostgreSQL database. Database name The name of the database Traffic Ops uses to store the configuration information. Database server hostname IP or FQDN The hostname of the database server (
pgin the example).
Database port number The database port number. The default value, 5432, should be correct unless you changed it during the setup. Traffic Ops database user The username Traffic Ops will use to read/write from the database. Password for Traffic Ops The password for the database user that Traffic Ops uses. Database server root (admin) user name Privileged database user that has permission to create the database and user for Traffic Ops. Database server root (admin) user password The password for the privileged database user. Traffic Ops URL The URL to connect to this instance of Traffic Ops, usually https://<Traffic Ops host>/ Human-readable CDN Name The name of the first CDN which Traffic Ops will be manage. DNS sub-domain for which your CDN is authoritative The DNS domain that will be delegated to this Traffic Control CDN. Administration username for Traffic Ops The Administration (highest privilege) Traffic Ops user to create. Use this user to login for the first time and create other users. Password for the admin user The password for the administrative Traffic Ops user.
Traffic Ops is now installed!
Default Profiles for initial configuration of the Traffic Ops instance.
Upgrading Traffic Ops¶
To upgrade from older Traffic Ops versions, stop the service, use yum(8) to upgrade to the latest available Traffic Ops package, and use the
admin tool to perform the database upgrade.
In order to upgrade to the latest version of Traffic Ops, please be sure that you have first upgraded to the latest available minor or patch version of your current release. For example, if your current Traffic Ops version is 3.0.0 and version 3.1.0 is available, you must first upgrade to 3.1.0 before proceeding to upgrade to 4.0.0. (Specifically, this means running all migrations,
traffic_ops/app/db/patches.sql for the latest of your current major version - which should be handled by the app/db/admin tool). The latest migration available before the release of 4.0.0 (pending at the time of this writing) was
traffic_ops/app/db/migrations/20180814000625_remove_capabilities_for_reseed.sql, so be sure that migrations up to this point have been run before attempting to upgrade Traffic Ops.
app/db/admin for more details about admin.
systemctl stop traffic_ops yum upgrade traffic_ops pushd /opt/traffic_ops/app/ ./db/admin --env production upgrade popd
After this completes, see Installation for instructions on running the
postinstall script. Once the
postinstall script, has finished, run the following command as the root user (or with
systemctl start traffic_ops to start the service.