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

Dedicated model for redundancy protocol instances #4801

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

Originally created by @WilliamDEdwards on GitHub (Apr 21, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.11.1

Feature type

New functionality

Proposed functionality

Dedicated model for e.g. VRRP and HSRP instances.

A typical instance configuration only needs an interface, VRID and VIPs. Keeping track of VRIDs in IP Address objects (as proposed in https://github.com/netbox-community/netbox/issues/2456) would allow us to store these basic attributes in NetBox. Information like tenant and interface could be derived from objects linked to the the IP Address object.

However, some properties are instance-specific, like priority. To use NetBox as Source of Truth for e.g. Keepalived configurations, we have to keep track of these properties, but they cannot be saved in another object.

Use case

Keeping track of instance information would allow for:

Database changes

The proposal requires adding a new model.

Many redundancy protocols share basic properties, like priority. Redundancy protocol specific fields (e.g. HSRP use-bia) should be added by users themselves to prevent overcomplicating the model.

External dependencies

Unsure.

Originally created by @WilliamDEdwards on GitHub (Apr 21, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.11.1 ### Feature type New functionality ### Proposed functionality Dedicated model for e.g. VRRP and HSRP instances. A typical instance configuration only needs an interface, VRID and VIPs. Keeping track of VRIDs in IP Address objects (as proposed in https://github.com/netbox-community/netbox/issues/2456) would allow us to store these basic attributes in NetBox. Information like tenant and interface could be derived from objects linked to the the IP Address object. However, some properties are instance-specific, like priority. To use NetBox as Source of Truth for e.g. Keepalived configurations, we have to keep track of these properties, but they cannot be saved in another object. ### Use case Keeping track of instance information would allow for: * Using NetBox as Source of Truth for e.g. Keepalived configurations * Getting the next available VRID (like https://github.com/netbox-community/netbox/issues/1246) ### Database changes The proposal requires adding a new model. Many redundancy protocols share basic properties, like priority. Redundancy protocol specific fields (e.g. HSRP `use-bia`) should be added by users themselves to prevent overcomplicating the model. ### External dependencies Unsure.
adam added the status: acceptedtype: feature labels 2025-12-29 19:20:46 +01:00
adam closed this issue 2025-12-29 19:20:46 +01:00
adam commented 2025-12-29 19:20:47 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 22, 2021):

This is probably a better encapsulation of the intent behind #2456. I'm going to close that one out in favor of this FR.

@jeremystretch commented on GitHub (Apr 22, 2021): This is probably a better encapsulation of the intent behind #2456. I'm going to close that one out in favor of this FR.
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#4801
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?