Site Landlord #134

New Issue

adam · 2025-12-29T15:34:46+01:00

adam commented

2025-12-29 15:34:46 +01:00

Originally created by @ryanmerolle on GitHub (Jul 1, 2016).

I would have suggested a vendor type and used it to specify device manufacturers, circuit carriers, and site landlords. Given you used individual entities for those types, I would recommend a Landlord type to consolidate contact details, show contracts & number of sites managed, etc. It would then allow for the Facility field just reference the Landlord's site code/reference instead.

Originally created by @ryanmerolle on GitHub (Jul 1, 2016). I would have suggested a vendor type and used it to specify device manufacturers, circuit carriers, and site landlords. Given you used individual entities for those types, I would recommend a Landlord type to consolidate contact details, show contracts & number of sites managed, etc. It would then allow for the Facility field just reference the Landlord's site code/reference instead.

adam closed this issue

2025-12-29 15:34:46 +01:00

adam commented

2025-12-29 15:34:47 +01:00

@rekeds commented on GitHub (Jul 6, 2016):

yeah, this would be great outside the DC, like building landlords :>
contact info, etc.

@rekeds commented on GitHub (Jul 6, 2016): yeah, this would be great outside the DC, like building landlords :> contact info, etc.

adam commented

2025-12-29 15:34:47 +01:00

@peelman commented on GitHub (Jul 7, 2016):

Another one of those times where abstraction should be considered.

Company is the desirable entity, with Manufacturers, Carriers, Landlords, Vendors/Resellers, etc. all being subsets of that. Each Company can have multiple Points of Contact, which can be account execs, support contacts, technical contacts, facilities contacts (in terms of landlords that are data centers).

Abstract in the beginning, or duplicate effort later.

@peelman commented on GitHub (Jul 7, 2016): Another one of those times where abstraction should be considered. `Company` is the desirable entity, with Manufacturers, Carriers, Landlords, Vendors/Resellers, etc. all being subsets of that. Each `Company` can have multiple `Points of Contact`, which can be account execs, support contacts, technical contacts, facilities contacts (in terms of landlords that are data centers). Abstract in the beginning, or duplicate effort later.

adam commented

2025-12-29 15:34:47 +01:00

@jeremystretch commented on GitHub (Dec 29, 2016):

#756 added simple contact details (name, phone, and email) to the Site model. I think that's a good place to set the perimeter of NetBox as it concerns administrative contacts.

In the case a user needs to track multiple sites belonging to a common landlord, it might be appropriate to define a custom field to track the assignment, and store the desired landlord data (which will vary a lot among use cases) elsewhere.

@jeremystretch commented on GitHub (Dec 29, 2016): #756 added simple contact details (name, phone, and email) to the Site model. I think that's a good place to set the perimeter of NetBox as it concerns administrative contacts. In the case a user needs to track multiple sites belonging to a common landlord, it might be appropriate to define a custom field to track the assignment, and store the desired landlord data (which will vary a lot among use cases) elsewhere.

adam referenced this issue

2025-12-29 20:25:55 +01:00

Multi-termination jumper deletion creates front port inconsistency #7601

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#134