March 2016 - Pdb-tech

[PDB-tech] adding new IX point to peeringDB record
by Mainer, Michael 30 Mar '16

30 Mar '16

All, I am trying to add a new peering IX point to my peeringDB record however it is not giving me the ability to manually key in my remote/anycasted ASN (AS26415). The drop down box only lists the primary one (AS7342). FYI, my peeringDB record is (http://as7342.peeringdb.com) Another issue is when I do click the “edit” button I notice all my existing peering IX points force the ASN to be that of my primary ASN, this is a big problem for someone like Verisign who has multiple ASNs. Is there another way to manually key in the ASN that is present at a IX or am I doing something wrong? I look a quick look at the archives and didn’t see this issue posted… If this is already being worked on sorry for the noise. Thanks, -Mike Mainer Interconnection Architect (703) 948-4362

3 2

[PDB-tech] new query / client features
by Matt Griswold 29 Mar '16

29 Mar '16

We're going back and trying to address a lot of the ease of use complaints now, starting with improved querying which will allow for easier retrieval of related entities. So far we have: * /fac?net_id=X - list facilities where network is present * /fac?ix_id=X - list facilities where exchange is present * /ix?net_id=X - list exchanges where network is present * /ix?fac_id=X - list exchanges at facility * /net?fac_id=X - list networks at facility * /net?ix_id=X - list networks at exchange * /net?ixlan_id=X - list networks at ixlan * /netixlan?ix_id=X - list netixlan objects for exchange * /ixpfx?ix=X - list all prefixes at exchange All of these queries support our query filters on related object fields, for example: * /ix?net__asn=XXX - list all exchanges where network with matching ASN is present * /net?ix__name__startswith=XXX - list all networks at exchanges where exchange name starts with XXX Anyone else have suggestions on which end points to add? The peeringdb-py client needs refactoring and a fair amount of work, in fact, I didn't mean to have it still in this state by release, so my apologies. Will be refactoring out the library to be fairly standalone, adding functions to include the above queries automatically. Also will be adding a whois feature to replace the old whois displays yet allow for auth so it can also display contacts. Changes will be showing up at https://github.com/peeringdb/peeringdb-py as soon as they're complete. Again, any other suggestions / improvements are welcome, now is the time to bring them up. Thanks!

1 0

[PDB-tech] peeringdb-py feedback
by Chris Caputo 22 Mar '16

22 Mar '16

I am happy to report the Seattle IX is now utilizing PeeringDB 2.0 to supplement its web site and route server configs. In case useful for other sites, my total development time to change from PDB 1.0's mysql tables to installing and using peeringdb-py with sqlite was under 3.5 hours. Some feedback to the creators of peeringdb-py: 1) The "updated" field in the local database, for each table, appears to be based on when the local database is updated, rather than based on the dates garnered by the sync. Can it be made to match the web site? (Same for "created".) 2) For peeringdb-py it may be useful to make it so diagnostic output is all to stdout, while errors are to stderr. That way folks using it in a crontab with "peeringdb sync > /dev/null" won't get an email unless there is an actual error logged to stderr. And in that case the email will be useful for chasing down the error. These lines are going to stderr, when they would best be going to stdout: Starting new HTTPS connection (1): www.peeringdb.com "GET /api/org?since=1458111034 HTTP/1.1" 200 None 3) For the crontab example at: http://peeringdb.github.io/peeringdb-py/cli/ it may be a good idea to avoid a thundering herd, from everyone following that example, by having a random duration sleep of between 0 and 10 minutes. For example: crontab -l | { cat; echo "0 0 * * * sleep \$[RANDOM\%600] ; `which peeringdb` sync > /dev/null 2>&1"; } | crontab - (Remove the '2>&1' if #2 suggestion is accepted.) Thanks, Chris

2 2

[PDB-tech] CLI client for access to PDB data?
by Job Snijders 20 Mar '16

20 Mar '16

Hi all, In the past, PeeringDB offered a textual interface to the PDB data through finger/whois. Multiple people (from as many companies) have approach me that they miss that approach and argued that the internet is more then a collection of websites. Most seem to depend having access to the contact information (which we do not expose without authentication) - but they also don't want to run a local mirror of the database: they want it lightweight and easy. My question: has anyone started work on a CLI based client which interacts with the hosted API on peeringdb.com/api, has no or very few dependencies, and authenticates itself? The only relevant lookup key is the AS number. Kind regards, Job

3 3

[PDB-tech] Going live
by Chris Phillips 15 Mar '16

15 Mar '16

What time is v2.0 going live tomorrow? Thanks. -- Chris Phillips Aptient Consulting Group Inc. +1 (917) 521-5290 - office +1 (250) 863-3519 - mobile

2 1

[PDB-tech] peeringdb python library - django error
by Jeroen Valcke 09 Mar '16

09 Mar '16

Hi, I'm installing the peeringdb python library on another system, and ran into a django issue. Any ideas on how to fix this? # peeringdb sync Traceback (most recent call last): File "/usr/local/bin/peeringdb", line 9, in <module> load_entry_point('peeringdb==0.4.2', 'console_scripts', 'peeringdb')() File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 716, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 696, in main rv = self.invoke(ctx) File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 1060, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 889, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python2.7/dist-packages/click/core.py", line 534, in invoke return callback(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/peeringdb/cli.py", line 124, in sync db = LocalDB(cfg) File "/usr/local/lib/python2.7/dist-packages/peeringdb/localdb.py", line 90, in __init__ django.setup() File "/usr/local/lib/python2.7/dist-packages/django/__init__.py", line 15, in setup from django.utils.log import configure_logging File "/usr/local/lib/python2.7/dist-packages/django/utils/log.py", line 16, in <module> from django.views.debug import ExceptionReporter, get_exception_reporter_filter File "/usr/local/lib/python2.7/dist-packages/django/views/debug.py", line 9, in <module> from django.core.urlresolvers import Resolver404, resolve File "/usr/local/lib/python2.7/dist-packages/django/core/urlresolvers.py", line 17, in <module> from django.http import Http404 File "/usr/local/lib/python2.7/dist-packages/django/http/__init__.py", line 4, in <module> from django.http.response import ( File "/usr/local/lib/python2.7/dist-packages/django/http/response.py", line 13, in <module> from django.core.serializers.json import DjangoJSONEncoder File "/usr/local/lib/python2.7/dist-packages/django/core/serializers/__init__.py", line 24, in <module> from django.core.serializers.base import SerializerDoesNotExist File "/usr/local/lib/python2.7/dist-packages/django/core/serializers/base.py", line 6, in <module> from django.db import models File "/usr/local/lib/python2.7/dist-packages/django/db/models/__init__.py", line 6, in <module> from django.db.models.query import Q, QuerySet, Prefetch # NOQA File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py", line 16, in <module> from django.db.models import sql File "/usr/local/lib/python2.7/dist-packages/django/db/models/sql/__init__.py", line 2, in <module> from django.db.models.sql.subqueries import * # NOQA File "/usr/local/lib/python2.7/dist-packages/django/db/models/sql/subqueries.py", line 9, in <module> from django.db.models.sql.query import Query File "/usr/local/lib/python2.7/dist-packages/django/db/models/sql/query.py", line 17, in <module> from django.db.models.aggregates import Count File "/usr/local/lib/python2.7/dist-packages/django/db/models/aggregates.py", line 5, in <module> from django.db.models.expressions import Func, Star File "/usr/local/lib/python2.7/dist-packages/django/db/models/expressions.py", line 7, in <module> from django.db.models import fields File "/usr/local/lib/python2.7/dist-packages/django/db/models/fields/__init__.py", line 19, in <module> from django import forms File "/usr/local/lib/python2.7/dist-packages/django/forms/__init__.py", line 6, in <module> from django.forms.fields import * # NOQA File "/usr/local/lib/python2.7/dist-packages/django/forms/fields.py", line 57, in <module> class Field(six.with_metaclass(RenameFieldMethods, object)): File "/usr/local/lib/python2.7/dist-packages/django/utils/six.py", line 778, in __new__ return meta(name, bases, d) File "/usr/local/lib/python2.7/dist-packages/django/utils/deprecation.py", line 53, in __new__ for base in inspect.getmro(new_class): AttributeError: 'module' object has no attribute 'getmro'

1 1

[PDB-tech] PeeringDB REST API - POC question
by Aaron Foss (aafoss) 07 Mar '16

07 Mar '16

Hello PDB API Experts, I'm trying to retrieve poc json data using beta.peeringdb.com. I notice that with the other API calls you can query all the members without needing a specific ID. Example (all AS#): https://beta.peeringdb.com/api/asn It doesn't appear this is possible with the point of contacts call: https://beta.peeringdb.com/api/poc The response I observe is the following: { "meta": { "generated": 1456793085.174871 }, "data": [] } I notice that when you query a specific ASN, such as 13445 the POC information is empty. Example snippet: https://beta.peeringdb.com/api/asn/13445 "poc_set": [], Questions: How do you identify the POC ID for tracking down a member's noc email or phone #? https://beta.peeringdb.com/api/poc/{pk}<https://beta.peeringdb.com/api/poc/%7bpk%7d> For example, how do I determine the POC ID for Cisco WebEx AS# 13445? Thank you very much for your time! Thanks, Aaron Aaron Foss Network Architect Cloud Collaboration Technology Group aafoss(a)cisco.com<mailto:aafoss@cisco.com> Phone: +1 585 249 1874

2 1

[PDB-tech] PeeringDB REST API - POC question
by Aaron Foss (aafoss) 01 Mar '16

01 Mar '16

Hello PDB API Experts, I'm trying to retrieve poc json data using beta.peeringdb.com. I notice that with the other API calls you can query all the members without needing a specific ID. Example (all AS#): https://beta.peeringdb.com/api/asn It doesn't appear this is possible with the point of contacts call: https://beta.peeringdb.com/api/poc The response I observe is the following: { "meta": { "generated": 1456793085.174871 }, "data": [] } I notice that when you query a specific ASN, such as 13445 the POC information is empty. Example snippet: https://beta.peeringdb.com/api/asn/13445 "poc_set": [], Questions: How do you identify the POC ID for tracking down a member's noc email or phone #? https://beta.peeringdb.com/api/poc/{pk} For example, how do I determine the POC ID for Cisco WebEx AS# 13445? Thank you very much for your time! Thanks, Aaron Foss Network Architect Cloud Collaboration Technology Group aafoss(a)cisco.com<mailto:aafoss@cisco.com> Phone: +1 585 249 1874

2 1