peeringdb
play

PeeringDB Arnold Nipper arnold@peeringdb.com 2017-02-28 Apricot - PowerPoint PPT Presentation

PeeringDB Arnold Nipper arnold@peeringdb.com 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 1 Agenda PeeringDB 2.0 Membership and Governance Committees Sponsorship Information and Resources 2017-02-28 Apricot 2017,


  1. PeeringDB Arnold Nipper arnold@peeringdb.com 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 1

  2. Agenda • PeeringDB 2.0 • Membership and Governance • Committees • Sponsorship • Information and Resources 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 2

  3. What is PeeringDB? • PeeringDB is the database of peering information on the Internet • Contains peering location and contact information for • Networks • Exchanges • Facilities • A PeeringDB record makes it easy for people to find you, and helps you to establish peering • If you aren’t registered in PeeringDB, you can register at https://www.peeringdb.com/register • We use basic verification for new accounts and require current whois information • Please update your whois information • Please register from a company email address 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 3

  4. PeeringDB 2.0 is Here! • PeeringDB 2.0 launched 15 March, 2016 • Backend database (1.0) discontinued simultaneously • Last legacy SQL dump for public consumption: https://peeringdb.com/v1/dbexport/peeringdb.sql • Investigating 404s for old SQL to contact users • Questions to support@peeringdb.com • Challenges during the launch • Very minor bug fixes required, but overall a success! • Lots of support tickets • 20C (developer contractor) very responsive to community - thanks! • Current release: 2.0.14 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 4

  5. 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 5

  6. Key New Infrastructure Features • Complete rewrite in Python • Python: fast and clean, widely used and supported • HTML5: adaptive design for desktop and mobile • Support for a multideveloper environment • Redesigned schema with data validation • All data is permissioned and editable • Input validation on fields: IP addresses, email addresses, etc. • Validation in PeeringDB record: dropdown box to select ASN at exchange • Data versioning • Revision history for every data change • Easy to restore and roll back • Historical data import from CAIDA going back to 2010 (not available yet) • RESTful API • Stateless • Incremental database syncs • With documentation and tools, oh my! 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 6

  7. Key New User Features • Facilities and exchanges can now update their own info • Networks are still required to associate their record at a facility or exchange • Multiple records of any type can be associated with an organization • Simpler organization management with a single account for network, facility, exchange records • One account can manage multiple organizations • Manage all of the things with a single account • Users can manage their accounts • Admin account for an organization can delegate fine-grained permissions • Contact info has permissions • Private/users/public permissions • All users must register, no more guest account • Public view can see all info except contact info (no login needed) • APIs and local database sync • Sync PeeringDB to a local database in any engine format 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 7

  8. RESTful API Designed for Automation • All operations are supported and are designed to be automated • Read • Create • Update • Delete • Each object type has an associated tag • org • net • ix • fac • List of objects: https://peeringdb.com/apidocs/ • API documentation: http://docs.peeringdb.com/api_specs/ 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 8

  9. Quick Examples Return Output in JSON • List all networks: curl -X GET https://<username>:<password>@www.peeringdb.com/api/net • Show a specific network: curl -X GET https://<username>:<password>@www.peeringdb.com/api/net/20 {"meta": {}, "data": [{"id": 20, "org_id": 10356, "org": {"id": 10356, "name": "20C", "website": "http://20c.com", "notes": "", "net_set": [20], "fac_set": [], "ix_set": [], "address1": "", "address2": "", "city": "Chicago", "country": "US", "state": "IL", "zipcode": "", "created": "2014-11-17T14:59:34Z", "updated": "2016-03-23T20:39:18Z", "status": "ok"}, "name": "20C", "aka": "", "website": "http://20c.com", "asn": 63311, " ... } 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 9

  10. Local Database Sync • Database sync gives you a local copy of PeeringDB for customization or internal use • Sync as often as you like • Incremental sync is supported • Improves performance and reduces load on PeeringDB servers • Build custom indexes and interfaces • Add custom fields • Choice of database engines • Currently supported: MySQL, Postgres, SQLite • Sync using the provided tools or build your own using the API 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 10

  11. Django Library • django-peeringdb is a Django library with a local PeeringDB database sync • Defines the database schema to create a local database copy • Easy to integrate in a common framework for locals tools and custom interfaces • Supports multiple database engines (MySQL, Postgres, SQLite) • Available at http://peeringdb.github.io/django-peeringdb/ 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 11

  12. Python Client • peeringdb-py is a Python client for PeeringDB • Gets objects and outputs in JSON or YAML format • Provides a whois-like display of records • Integrated local database sync • Python library for integration with custom tools • Available at http://peeringdb.github.io/peeringdb-py/ • Examples at https://github.com/grizz/pdb-examples 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 12

  13. Status Page http://status.peeringdb.com/ 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 13

  14. Beta Development and Reporting Issues • Beta server • Available at https://beta.peeringdb.com/ • Runs the latest beta software version • Full access over HTTP and the API • Database is local to the beta server only, changes are not reflected on the production servers • Latest changes • Available at https://beta.peeringdb.com/changes • Redirects to the list of issues on GitHub • Documents all of the changes in the current beta version • Log bugs and feature requests at https://github.com/peeringdb/peeringdb/issues on GitHub 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 14

  15. Agenda • PeeringDB 2.0 • Membership and Governance • Committees • Sponsorship • Information and Resources 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 15

  16. Membership and Governance • PeeringDB organization formally formed 16 Dec, 2015 • PeeringDB 501(c)(6) filed 7 Jan, 2016 (approved 24 Feb, 2016) • 2 nd election held April 2016: 94 organizations registered, 80 voted • 3 rd election scheduled for April 2017 • 299 addresses subscribed to the Governance mailing list (as of 17 Oct 2016) • A corporation, limited liability company, partnership or other legal business entity may be a Member of the Corporation. Membership is determined by having both an active PeeringDB.com account and an individual representative or role subscription to the PeeringDB Governance mailing list: • http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov • More information available at http://gov.peeringdb.com/ 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 16

  17. Board of Directors and Officers Chris Caputo – Secretary & Treasurer Patrick Gilmore – Director Matt Griswold – Director (Non-Board Member) (Term Expires 2017) (Term Expires 2017) Aaron Hughes – President Arnold Nipper – Director Job Snijders – Vice President (Term Expires 2018) (Term Expires 2017) (Term Expires 2018) 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 17

  18. Committees Admin Committee Product Committee • Manage administration of user accounts and • Ask for input from the community on desired PeeringDB records features • Answer support tickets • Manage roadmap and development priorities • Board members Job Snijders (Chair) and • Write SoWs to solicit bids to complete Arnold Nipper (Vice Chair) requested features • Seeking 2 community volunteers (1 year term) • Board members Aaron Hughes (Chair) and Matt Griswold (Vice Chair) • Contact: support@peeringdb.com • Seeking 0 community volunteers (1 year term) • Contact: productcom@lists.peeringdb.com 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 18

  19. Admin Committee Samer Hendrik Kate Peter Florian Abdel-Hafez Braasch Gerry Helmenstine Hibler Eric Arnold Nipper – Eduardo Job Snijders – Michael Lindsjö Vice Chair Ascenço Reis Chair Still 2017-02-28 Apricot 2017, Ho Chi Minh City, Viet Nam 19

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend