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 the field Facility to the Location model #8683

New Issue
Closed
opened 2025-12-29 20:39:52 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:39:52 +01:00
Owner
Copy Link

Originally created by @jsenecal on GitHub (Sep 27, 2023).

Originally assigned to: @DanSheps on GitHub.

NetBox version

v3.6.3

Feature type

Data model extension

Proposed functionality

Add the field facility to the Location model the same way it's done on the Site model

Use case

Most of the time the Facility is not a whole building but rather a Suite (Location) in a building (Site). You may also have more than one Facility inside the same Site or have a single facility in a suite in the building but also other tenants in their own Locations which are not part of that Facility.

For example:
151 Front St., Toronto, ON Canada; Canada's largest Carrier Hotel.
Equinix TR1: Suite 706
Neutral Data Toronto: Suite 800
BELL Canada: Suite 605
Coloware YTZ1: Suite 504
Cologix TOR1: Suite 602
eStruxture TOR-1: Suite 341
Aptum: Suite 402
... and many others

Being able to document this Facility name/ID in a consistent manner across NetBox seems only reasonable.

Database changes

A new CharField, facility needs to be added to the Location model.

We can use the Site model for reference.

External dependencies

None

Originally created by @jsenecal on GitHub (Sep 27, 2023). Originally assigned to: @DanSheps on GitHub. ### NetBox version v3.6.3 ### Feature type Data model extension ### Proposed functionality Add the field `facility` to the `Location` model the same way it's done on [the `Site` model](https://github.com/netbox-community/netbox/blob/v3.6.3/netbox/dcim/models/sites.py#L180-L185) ### Use case Most of the time the _Facility_ is not a whole building but rather a Suite (Location) in a building (Site). You may also have more than one Facility inside the same Site or have a single facility in a suite in the building but also other tenants in their own Locations which are not part of that Facility. For example: **151 Front St., Toronto, ON Canada; Canada's largest Carrier Hotel.** Equinix TR1: Suite 706 Neutral Data Toronto: Suite 800 BELL Canada: Suite 605 Coloware YTZ1: Suite 504 Cologix TOR1: Suite 602 eStruxture TOR-1: Suite 341 Aptum: Suite 402 ... and many others Being able to document this Facility name/ID in a consistent manner across NetBox seems only reasonable. ### Database changes A new CharField, `facility` needs to be added to the `Location` model. We can use [the `Site` model](https://github.com/netbox-community/netbox/blob/v3.6.3/netbox/dcim/models/sites.py#L180-L185) for reference. ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 20:39:53 +01:00
adam closed this issue 2025-12-29 20:39:53 +01:00
adam commented 2025-12-29 20:39:53 +01:00
Author
Owner
Copy Link

@kmorin18 commented on GitHub (Sep 27, 2023):

Agreed, we have POPs in many locations where the location is a suite that acts as a Provider's facility

@kmorin18 commented on GitHub (Sep 27, 2023): Agreed, we have POPs in many locations where the location is a suite that acts as a Provider's facility
adam commented 2025-12-29 20:39:54 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Sep 27, 2023):

FWIW I can submit a PR for this, if accepted.

@jsenecal commented on GitHub (Sep 27, 2023): FWIW I can submit a PR for this, if accepted.
adam commented 2025-12-29 20:39:54 +01:00
Author
Owner
Copy Link

@yash-pal1 commented on GitHub (Sep 28, 2023):

@abhi1693 Can you please assign me this task i can able to do that

@yash-pal1 commented on GitHub (Sep 28, 2023): @abhi1693 Can you please assign me this task i can able to do that
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 status: accepted 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#8683
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?