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

Configuration profiles/templates for set of interfaces #2026

New Issue
Closed
opened 2025-12-29 17:21:34 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:21:34 +01:00
Owner
Copy Link

Originally created by @vsvetlov on GitHub (Sep 26, 2018).

Environment

  • Python version: 3.5.4
  • NetBox version: 2.4.4

Proposed Functionality

It could be already discussed somewhere, sorry if I missed that.
Cisco NXOS and IOS for switches have ability to configure predefined configuration that later can be applied to a bunch of the interfaces instead of configuring every interface independently in manual mode.

Use Case

When you have many switches and thousends of interfaces it is a very convenient feature to apply the same configuration to many ports. It also significantly decrease the amount of work when you need to modify interface configuration. For example, if you need to add vlan to 20 trunk interfaces it can be easily done by modifying port-profile in NXOS. If you have just 10 different configurations for 500 ports it would be really helpful to have ability to modify just 10 entities instead of 500. Also, it creates some level of abstraction which is good for automation purposes and decrease number of requests to NetBox.

Database Changes

Looking into NetBox data scheme it seems the best way to implement such feature is by using config context killer feature.
May be it is better to create separate UI view for config contexts associated with interfaces.
Coexistent with current interface settings in DB can be done in the folowing way. If interface has associated config context it should take data from it, such as 802.1q mode, assigned vlans etc. If not the settings assigned to that particular interface should be used.

External Dependencies

None

Originally created by @vsvetlov on GitHub (Sep 26, 2018). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.5.4 * NetBox version: 2.4.4 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality It could be already discussed somewhere, sorry if I missed that. Cisco NXOS and IOS for switches have ability to configure predefined configuration that later can be applied to a bunch of the interfaces instead of configuring every interface independently in manual mode. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case When you have many switches and thousends of interfaces it is a very convenient feature to apply the same configuration to many ports. It also significantly decrease the amount of work when you need to modify interface configuration. For example, if you need to add vlan to 20 trunk interfaces it can be easily done by modifying port-profile in NXOS. If you have just 10 different configurations for 500 ports it would be really helpful to have ability to modify just 10 entities instead of 500. Also, it creates some level of abstraction which is good for automation purposes and decrease number of requests to NetBox. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Looking into NetBox data scheme it seems the best way to implement such feature is by using config context killer feature. May be it is better to create separate UI view for config contexts associated with interfaces. Coexistent with current interface settings in DB can be done in the folowing way. If interface has associated config context it should take data from it, such as 802.1q mode, assigned vlans etc. If not the settings assigned to that particular interface should be used. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam closed this issue 2025-12-29 17:21:35 +01:00
adam commented 2025-12-29 17:21:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 27, 2018):

NetBox is not intended to fully replicate device configuration. This feature would be out of scope.

@jeremystretch commented on GitHub (Sep 27, 2018): NetBox is not intended to fully replicate device configuration. This feature would be out of scope.
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#2026
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?