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 Provider to Site #7962

New Issue
Closed
opened 2025-12-29 20:30:31 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:30:31 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (Apr 29, 2023).

NetBox version

v3.4.10

Feature type

Data model extension

Proposed functionality

For each site, be able to associate it with a provider, i.e. supplier of facilities services: e.g. "Openreach", "Equinix" etc

Use case

Be able to group and list sites by provider, and have somewhere to store account and contact information for the facilities supplier.

My current workaround: have a custom object field on Site which links to Circuits > Provider. This seemed to be the nearest existing object to my requirements - more accurate than e.g. Manufacturer - and avoids having to build a full plugin.

Other options would be Site Groups (if you're not using them for anything else), or Tags. Neither can store account/contact info though.

Database changes

On the assumption that the role of Circuits > Provider could be expanded to include facilities provider, it's just one extra column with FK link to that table.

It seems to me that "service providers" can reasonably provide both circuits and facilities space. If you wanted, there could be flags added for "Circuit provider" and "Facilities provider", similar to how Device Roles have "VM Capable".

Otherwise, a separate DCIM > Provider could be added, but (a) I don't think it's necessary, and (b) there are potential problems with two models with the same name, even if they are in different sub-applications. To avoid the naming conflict it could be called something else, e.g. DCIM > Landlord or DCIM > Supplier.

External dependencies

None

Originally created by @candlerb on GitHub (Apr 29, 2023). ### NetBox version v3.4.10 ### Feature type Data model extension ### Proposed functionality For each site, be able to associate it with a provider, i.e. supplier of facilities services: e.g. "Openreach", "Equinix" etc ### Use case Be able to group and list sites by provider, and have somewhere to store account and contact information for the facilities supplier. My current workaround: have a custom object field on Site which links to Circuits > Provider. This seemed to be the nearest existing object to my requirements - more accurate than e.g. Manufacturer - and avoids having to build a full plugin. Other options would be Site Groups (if you're not using them for anything else), or Tags. Neither can store account/contact info though. ### Database changes On the assumption that the role of Circuits > Provider could be expanded to include facilities provider, it's just one extra column with FK link to that table. It seems to me that "service providers" can reasonably provide both circuits and facilities space. If you wanted, there could be flags added for "Circuit provider" and "Facilities provider", similar to how Device Roles have "VM Capable". Otherwise, a separate DCIM > Provider could be added, but (a) I don't think it's necessary, and (b) there are potential problems with two models with the same name, even if they are in different sub-applications. To avoid the naming conflict it could be called something else, e.g. DCIM > Landlord or DCIM > Supplier. ### External dependencies None
adam added the type: feature label 2025-12-29 20:30:31 +01:00
adam closed this issue 2025-12-29 20:30:31 +01:00
adam commented 2025-12-29 20:30:32 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Apr 29, 2023):

Actually, don't worry - Site Group is good enough. I can add CFs on that if required for account info, and Contacts can be assigned to Site Group already.

@candlerb commented on GitHub (Apr 29, 2023): Actually, don't worry - Site Group is good enough. I can add CFs on that if required for account info, and Contacts can be assigned to Site Group already.
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 type: feature
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#7962
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?