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

Customizable default roles (ip address) #1787

New Issue
Closed
opened 2025-12-29 17:19:05 +01:00 by adam · 3 comments
adam commented 2025-12-29 17:19:05 +01:00
Owner
Copy Link

Originally created by @luqasz on GitHub (Jun 14, 2018).

Issue type

[x ] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version:
  • NetBox version:

Description

I'd like to be able to customize roles for ip addresses. Some roles are not applicable for my organization.
Use cases:

  • Select HAPROXY role for ips, so that we know that this ip is used for haproxy.
  • Select GATEWAY role to mark ip as a gateway.
Originally created by @luqasz on GitHub (Jun 14, 2018). ### Issue type [x ] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) If you are submitting a bug report and have made any changes to the code base, please first validate that your bug can be recreated while running an official release. --> ### Environment * Python version: <!-- Example: 3.5.4 --> * NetBox version: <!-- Example: 2.1.3 --> <!-- 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 I'd like to be able to customize roles for ip addresses. Some roles are not applicable for my organization. Use cases: * Select `HAPROXY` role for ips, so that we know that this ip is used for haproxy. * Select `GATEWAY` role to mark ip as a gateway.
adam closed this issue 2025-12-29 17:19:05 +01:00
adam commented 2025-12-29 17:19:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 14, 2018):

IP address roles are not customizable. They are methods in which an IP address can be configured to operate: VIP, secondary, anycast, VRRP, etc. This has nothing to with designation for a particular application or function.

@jeremystretch commented on GitHub (Jun 14, 2018): IP address roles are not customizable. They are methods in which an IP address can be configured to operate: VIP, secondary, anycast, VRRP, etc. This has nothing to with designation for a particular application or function.
adam commented 2025-12-29 17:19:08 +01:00
Author
Owner
Copy Link

@luqasz commented on GitHub (Jun 14, 2018):

IP address roles are not customizable. They are methods in which an IP address can be configured to operate: VIP, secondary, anycast, VRRP, etc. This has nothing to with designation for a particular application or function.

Prefixes and many other resources have a customizable role. Why this is different ?

@luqasz commented on GitHub (Jun 14, 2018): > IP address roles are not customizable. They are methods in which an IP address can be configured to operate: VIP, secondary, anycast, VRRP, etc. This has nothing to with designation for a particular application or function. Prefixes and many other resources have a customizable role. Why this is different ?
adam commented 2025-12-29 17:19:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 14, 2018):

It's an entirely different concept. Prefix roles are functional and arbitrary. IP address roles relate to their manner of operation. For example, you list "gateway" as a desired role. But a gateway can be any of several available roles, such as VRRP or secondary.

@jeremystretch commented on GitHub (Jun 14, 2018): It's an entirely different concept. Prefix roles are functional and arbitrary. IP address roles relate to their manner of operation. For example, you list "gateway" as a desired role. But a gateway can be any of several available roles, such as VRRP or secondary.
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#1787
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?