Contacts autocomplete/suggest from PeeringDB when creating/editing a new AS

[mngan]

Environment

• Python version:
• Peering Manager version:

Proposed Functionality

When entering the contacts for a new AS, it would be helpful to suggest possible completions from the PeeringDB contact list.

Use Case

When creating new AS having some assistance filling in the contact details would be good, otherwise you have to fill it in afterwards by flipping back and forth between two tabs.

I have gotten around this by writing a tool using the REST API to pull the PDB contact into the Peering Manager contact.

External Dependencies

None.

[netravnen]

2x key technical requirements, (amongst others):

(1) A PeringDB account with at least 'member' affiliation status to at least one network,

(2) Storing username and password in clear-text (somewhere) (PeeringDB does not, yet, support any form of Oauth-style login using a token/API-key), (2.1) Password rotation policy needs to be considered,

[mngan]

All the data is already in the peeringdb_contact table if you have synced the PeeringDB database with an authorized account. If the data is missing from this table, then that should not affect the autocomplete. The only thing missing is the connection from the form to the peeringdb_contact table.

[gmazoyer]

Maybe it is time to make contacts a first class citizen inside Peering Manager as well. Instead of having the possibility to register only one contact or use the one from PeeringDB, we could create a new Contact class and create a one-to-many relationship between an AS and a contact.

[netravnen]

we could create a new Contact class and create a one-to-many relationship between an AS and a contact.

Will makes sense to deduplicate data when possible. (The primary reason, from my perspective, is for the organizations in PeeringDB, which manages several networks (also known as ASN's) and can often have identical contact information)

[jaakub]

Maybe it is time to make contacts a first class citizen inside Peering Manager as well. Instead of having the possibility to register only one contact or use the one from PeeringDB, we could create a new Contact class and create a one-to-many relationship between an AS and a contact.

We'd also like to see the ability to create multiple contacts for a single ASN - both manually but also via auto-complete (although not so important to us since we'd only create a manual ASN entry if the 3rd party does not have a valid PeeringDB record).