...
Peering Setup - Local Installations:
Table of Contents | ||
---|---|---|
|
ProVision versions 7.x and newer
For ProVision versions 7.x and later, ProVision directly interfaces with PeeringDB's API to update exchange and peering data, caching the data for a default time of 12 hours.
This requires a PeeringDB account, and for the account credentials to be set in ProVision. The credentials may either be hard coded into globals.php, or set into the database via the Admin/Peering GUI. See Admin Settings and Peering v2 for detailed information.
Additional Peering constants may be added into globals.php to change the PeeringDB URL between the main and beta site (some users may find the beta site to have faster response times), and to adjust the PeeringDB cache TTL.
For real-time updates, TTL may be set to 0. However, some users may experience severe lag with a TTL = 0; we recommend using a 10 to 15 minute or greater TTL if this occurs.
ProVision versions 5.3.0 to 6.1.2 (Legacy)
For legacy set up (not recommended):
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
ProVision uses a locally-hosted mirror of the PeeringDB database in order to perform non-edit Peering functions. There are a few steps to take in order to set up your locally hosted instance to coordinate with PeeringDB information.
1) Create a new database to store the PeeringDB data. This must be on the same server as the database which is used by ProVision. 2) Download, install, and use the PeeringDB Python Client to populate the database. The PeeringDB documentation is available here: http://peeringdb.github.io/peeringdb-py/ 3) Once this has been done, edit the ProVision global configuration file located here:
It must be updated with the following variables to inform ProVision of the location of this new install. The username and password fields correspond to the username and password of the MySQL account which has access to the database (Not the username and password to your PeeringDB account).
4) Periodically sync with the PeeringDB server to get the latest updates. This can be done manually, or there are instructions in the PeeringDB documentation on how to automatically schedule syncs using cron (http://peeringdb.github.io/peeringdb-py/cli/#sync). |
ProVision versions 7.x and newer
For ProVision versions 7.x and later, ProVision directly interfaces with PeeringDB's API to update exchange and peering data, caching the data for a default time of 12 hours.
This requires a PeeringDB account, and for the account credentials to be set in ProVision. The credentials may either be hard coded into globals.php, or set into the database via the Admin/Peering GUI. See Admin Preferences and Peering v2 for detailed information.
...
) |
...
. |
...
Peering Constants
In globals.php, the following constants can be defined to tweak the Peering internals:
...
For additional information on working with Peering, see the following documentation sections: