starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add integration with PeeringDB for facilities #1748

New Issue
Closed
opened 2025-12-29 16:34:58 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:34:58 +01:00
Owner
Copy Link

Originally created by @zorun on GitHub (May 25, 2018).

Issue type

[X] Feature request
[ ] Bug report
[ ] Documentation

Description

Currently, the "Facility" field of a site is a free-form text. It would be nice to have integration with PeeringDB. Some examples of functionalities I have in mind:

  • provide auto-completion of facility name using PeeringDB data
  • automatically fill in the physical address of the facility from PeeringDB (and possibly GPS coordinates, see #2118)
  • add a field containing the facility ID from PeeringDB, so that it's easier to combine data from the Netbox API and the PeeringDB API (100% accurate matching of Netbox sites with PeeringDB facilities)

Here is a facility in PeeringDB for example: https://peeringdb.com/fac/53

Originally created by @zorun on GitHub (May 25, 2018). ### Issue type [X] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> <!-- BUG REPORTS must include: * A list of the steps needed for someone else to reproduce the bug * A description of the expected and observed behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description Currently, the "Facility" field of a site is a free-form text. It would be nice to have integration with PeeringDB. Some examples of functionalities I have in mind: - provide auto-completion of facility name using PeeringDB data - automatically fill in the physical address of the facility from PeeringDB (and possibly GPS coordinates, see #2118) - add a field containing the facility ID from PeeringDB, so that it's easier to combine data from the Netbox API and the PeeringDB API (100% accurate matching of Netbox sites with PeeringDB facilities) Here is a facility in PeeringDB for example: https://peeringdb.com/fac/53
adam closed this issue 2025-12-29 16:34:58 +01:00
adam commented 2025-12-29 16:34:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 18, 2018):

The facility is a general purpose field which means different things to different users. For example, we use it to record data center names; a college might use it to annotate building number. I'd venture a guess that most NetBox users aren't using it in relation to PeeringDB facilities.

I'm also not clear on the workflow being proposed here. Could you elaborate?

@jeremystretch commented on GitHub (Jul 18, 2018): The facility is a general purpose field which means different things to different users. For example, we use it to record data center names; a college might use it to annotate building number. I'd venture a guess that most NetBox users aren't using it in relation to PeeringDB facilities. I'm also not clear on the workflow being proposed here. Could you elaborate?
adam commented 2025-12-29 16:34:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 31, 2018):

Closing due to lack of activity.

@jeremystretch commented on GitHub (Jul 31, 2018): Closing due to lack of activity.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1748
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?