peeringdb update · • questions to [email protected] • challenges during the launch •...

PeeringDBUpdateAaronHughes

[email protected]

11-14April,2016 GPF11– Hollywood,CA 1

Agenda

• PeeringDB2.0• Membership/Governance• Committees• April2016Elections• Sponsorship• ContactInformation


WhatisPeeringDB?

• PeeringDB isthedatabaseofpeeringinformationontheInternet• Containspeeringlocationandcontactinformationfor

• Networks• Exchanges• Facilities

• APeeringDB recordmakesiteasyforpeopletofindyou,andhelpsyoutoestablishpeering• Ifyouaren’tregisteredinPeeringDB,youcanregisterathttps://www.peeringdb.com/register• Weusebasicverificationfornewaccountsandrequirecurrentwhoisinformation• Pleaseupdateyourwhoisinformation• Pleaseregisterfromacompanyemailaddress


PeeringDB2.0

• PeeringDB 2.0launched15March,2016• Backenddatabase(1.0)discontinuedsimultaneously• LastlegacySQLdumpforpublicconsumption:https://peeringdb.com/v1/dbexport/peeringdb.sql• Investigating404sforoldSQLtocontactusers• [email protected]

• Challengesduringthelaunch• Veryminorbugfixesrequired,butoverallasuccess!• Lotsofsupporttickets• 2.0.7currentrelease• 20C(developercontractor)veryresponsivetocommunity- thanks!

GPF11– Hollywood,CA 411-14April,2016

KeyNewInfrastructureFeatures

• CompleterewriteinPython• Fastandclean,widelyusedandsupported• Supportforamultideveloper environment

• Redesignedschemawithdatavalidation• Alldataispermissioned andeditable• Inputvalidationonfields:IPaddresses,emailaddresses,etc.• ValidationinPeeringDB record:dropdownboxtoselectASNatexchange

• Dataversioning• Revisionhistoryforeverydatachange• Easytorestoreandrollback• HistoricaldataimportfromCAIDAgoingbackto2010(notavailableyet)

• RESTful API• Stateless• Incrementaldatabasesyncs• Withdocumentationandtools,ohmy!


KeyNewUserFeatures

• Facilitiesandexchangescannowupdatetheirowninfo• Networksarestill requiredtoassociatetheirrecordatafacilityorexchange

• Multiplerecordsofanytypecanbeassociatedwithanorganization• Simplerorganizationmanagementwithasingleaccountfornetwork,facility,exchangerecords

• Oneaccountcanmanagemultipleorganization• Manageallofthethingswithasingleaccount

• Userscanmanagetheiraccounts• Adminaccountforanorganizationcandelegatefine-grainedpermissions

• Contactinfohaspermissions• Private/users/publicpermissions• Allusersmustregister,nomoreguestaccount• Publicviewcanseeallinfoexceptcontactinfo(nologinneeded)

• APIsandlocaldatabasesync• SyncPeeringDBtoalocaldatabase inanyengineformat


MultipleRecordsUnderaSingleOrganization


FacilitiesareShownHereAMS-IXhasnoFacilities

NetworksareShownHereAMS-IXhas3NetworkRecords

ExchangesareShownHereAMS-IXhas6ExchangeRecords

OneAccountManagingMultipleOrganizations


Account“job”isAffiliatedwith4Organizations

RequestOwnershipofanExistingOrganization• NetworkrecordsshouldalreadyhaveanorganizationadmincopiedfromPeeringDB1.0• Facilityandexchangerecordswillneedtohaveanorganizationadminassignedtothem


Click“RequestOwnership”GeneratesaSupportTicketforValidationandApproval

RequestAffiliationtoanOrganization


1.GotoYourProfile

2.ConfirmEmailAddress(ClickHereifnotConfirmed)

3.EnterASNorOrganizationHereAutocomplete onExistingASNsandOrganizationsinPeeringDB

4.Click“Affiliate”Existing:OrganizationAdmin

NeedstoApproveNew:GeneratesaSupportTicketforValidationand

Approval

OrganizationUserManagement


ApproveorDenyPendingRequests

DelegatePermissionsforMembersAdminsHaveAccesstoEverything

ChangeUserAccessLevelsAdmin– Administrator

Member– DelegatePermissions

RemoveUsersFromtheOrganizationDoesnotRemovetheUserAccountFromPeeringDB

AdministrativePermissionDelegation


User“rho”canManagethe“Equinix Connect”NetworkRecord,andAnyExchangeorFacility

User“equinix-uk”canManageSeveralNetworkRecords,butno ExchangesorFacilities

Create– NewEntriesinRecordUpdate– ChangeExistingEntriesinRecordDelete– DeleteEntriesinRecord

NetworkRecordContactInformationPermissions


SeparateVisibilityPreferencesforEachRolePrivate– OrganizationOnly(Default)

Users– RegisteredUsersOnlyPublic– Anyone(noLoginRequired)

RESTfulAPIDesignedforAutomation

• Alloperationsaresupportedandaredesignedtobeautomated• Read• Create• Update• Delete

• Eachobjecttypehasanassociatedtag• org• net• ix• fac

• Listofobjects:https://peeringdb.com/apidocs/• APIdocumentation:http://docs.peeringdb.com/api_specs/


QuickExamplesReturnOutputinJSON

• Listallnetworks:curl -X GET https://<username>:<password>@www.peeringdb.com/api/net

• Showaspecificnetwork: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, " ... }

LocalDatabaseSync

• DatabasesyncgivesyoualocalcopyofPeeringDBforcustomizationorinternaluse• Syncasoftenasyoulike• Incrementalsyncissupported

• ImprovesperformanceandreducesloadonPeeringDB servers• Buildcustomindexesandinterfaces• Addcustomfields• Choiceofdatabaseengines

• Currentlysupported:MySQL,Postgres,SQLite• Redis:https://github.com/netflix/peeringdb-py

• SyncusingtheprovidedtoolsorbuildyourownusingtheAPI

11-14April,2016 16GPF11– Hollywood,CA

DjangoLibrary

• django-peeringdbisaDjangolibrarywithalocalPeeringDBdatabasesync• Definesthedatabaseschematocreatealocaldatabasecopy• Easytointegrateinacommonframeworkforlocalstoolsandcustominterfaces• Supportsmultipledatabaseengines(MySQL,Postgres,SQLite)• Availableathttp://peeringdb.github.io/django-peeringdb/


PythonClient

• peeringdb-pyisaPythonclientforPeeringDB• GetsobjectsandoutputinJSONorYAMLformat• Providesawhois-likedisplayofrecords• Integratedlocaldatbasesync• Pythonlibraryforintegratewithcustomtools• Availableathttp://peeringdb.github.io/peeringdb-py/• Examplesathttps://github.com/grizz/pdb-examples

11-14April,2016 18GPF11– Hollywood,CA

Agenda

• PeeringDB2.0• Membership/Governance• Committees• April2016Elections• Sponsorship• ContactInformation


Membership/Governance

• PeeringDBorganizationformallyformed16Dec,2015• PeeringDB501(c)(6)filed7Jan,2016(approved24Feb,2016)• 5Boardmeetingshavebeenheld• 86membersregisteredandvotedinthefirstelection• 288addressessubscribedtotheGovernancemailinglist(asof6Apr2016)• Acorporation,limitedliabilitycompany,partnershiporotherlegalbusinessentitymaybeaMemberoftheCorporation.MembershipisdeterminedbyhavingbothanactivePeeringDB.comaccountandanindividualrepresentativeorrolesubscriptiontothePeeringDBGovernancemailinglist:• http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov• Moreinformationavailableathttp://gov.peeringdb.com/


Committees

• AdminCommittee• Willwritecharter(inprogress)• WillseekindividualsfromthecommunitytoserveonAdminCommittee• Willdefineroles,responsibilitiesandassistwithscheduleforAdminCommitee• Seeking2communityvolunteers(1yearterm)• BoardmembersJobSnijders andPatrickGilmore(Snijders asChair)• [email protected]

• ProductDevelopmentCommittee• Willwritecharter• Willseekinputfromthecommunityondesiredfeatures• WillwriteSoW’s tosolicitbidstocompleterequestedfeatures• Willmanageprioritiesforselecteddevelopmentvendor(s)• Seeking4communityvolunteers(1yearterm)• BoardmembersAaronHughesandMattGriswold(HughesasChair)• [email protected]


GregHankins MattGriswold ArnoldNipper Florian Hibler JobSnijders (Chair)

PatrickGilmore(ViceChair) EduardoAscenço Reis EricLindsjö WaltWollny KateGerry

AdminCommittee

Bigthankstoourawesometeamofadmins!


Interestedinvolunteeringyour [email protected]

ProductDevelopmentCommittee

• AProductDevelopmentCommitteeisneeded• Directfeaturerequests• Maintaintheproductroadmap

• [email protected]• [email protected]


BecomeaPeeringDBSponsor!

• DiamondSponsorship- $25,000/year• Limitedto2sponsors• VerylargelogoontoplineofSponsorspage• DiamondSponsordisplayonrecords

• PlatinumSponsorship- $10,000/year• LargelogoonsecondlineofSponsorspage• PlatinumSponsordisplayonrecords

• GoldSponsorship- $5,000/year• MediumlogoonthirdlineofSponsorspage• GoldSponsorlogodisplayonrecords

• SilverSponsorship- $2,500/year• SmalllogoonfourthlineofSponsorspage• SilverSponsorlogodisplayonrecords

• [email protected]


PlatinumSponsor

SilverSponsors

Thankyoutoourinitialsponsors!


BoardElections(April2016)

• PeeringDBBoardelectioninApril2016(1and2yearterms)• 5seatsupforelection• Current(initial)BoardservesthroughApril2016• Interestedinmoreinformationaboutroles/responsibilitiesandtimecommitments?• [email protected]://gov.peeringdb.com/

• ThroughApril14th23:59:59UTC2016:vandidatesmaysubmittheircandidacyandmaximum300wordstatement,asdeterminedbyPOSIX"LANG=en_US.UTF-8wc -w"command,orrevisionstotheirstatement,[email protected]• April15th2016:ballots,withcandidatestatements,willbesubmittedtothePeeringDBGovernancemailinglist([email protected])• April15ththrough29th23:59:59UTC2016:voting


BoardElections(April2016)

• Boardcandidates(asof10April,2016)• PatrickW.Gilmore• MattGriswold• FlorianHibler• AaronHughes• ArnoldNipper• JobSnijders


MailingLists

• Announce:http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce• Governance:http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov• Technical:http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-tech• UserDiscuss:http://lists.peeringdb.com/cgi-bin/mailman/listinfo/user-discuss


Havequestions?

• PeeringDBOfficers&Board([email protected])• AaronHughes– President,Director• PatrickGilmore– VicePresident,Director• ChrisCaputo– Secretary&Treasurer(non-boardmember)• MattGriswold– Director• ArnoldNipper– Director• JobSnijders – Director

• PeeringDB Admins([email protected])


ThankstoRichardTurkbergen

ThePeeringDBBoardherebyexpressesitsenormousappreciationtoRichardA.Turkbergen (néeSteenbergen)forhiscreationanddonationofPeeringDBtotheorganization.


Questions?


peeringdb update · • questions to [email protected] • challenges during the launch •...

Documents