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

Bulk rename interfaces when create Virtual Chassis #3331

New Issue
Closed
opened 2025-12-29 18:27:48 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:27:48 +01:00
Owner
Copy Link

Originally created by @vsvetlov on GitHub (Feb 14, 2020).

Environment

  • Python version: 3.7.3
  • NetBox version: 2.7.4

Proposed Functionality

Optionally rename interfaces automatically when adding a device to a virtual chassis according to the predefined find/replace/regex variables.

Use Case

Usually name convention for interfaces in virtual chassis is slightly different than for standalone devices.
It depends on vendor implementation. For example, if for standalone switch interface name is GigabitEthernet10, then for virtual chassis it can be GigabitEthernet1/10 where 1 is prefix that points to device priority in the virtual chassis.

Actually bulk renaming already implemented. We need to call it when adding a device to virtual chassis. It would really help in the case of many virtual chassis.

Database Changes

None

External Dependencies

None

Originally created by @vsvetlov on GitHub (Feb 14, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. 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.7.3<!-- Example: 3.6.9 --> * NetBox version: 2.7.4<!-- Example: 2.7.3 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Optionally rename interfaces automatically when adding a device to a virtual chassis according to the predefined find/replace/regex variables. <!-- 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 Usually name convention for interfaces in virtual chassis is slightly different than for standalone devices. It depends on vendor implementation. For example, if for standalone switch interface name is GigabitEthernet10, then for virtual chassis it can be GigabitEthernet1/10 where 1 is prefix that points to device priority in the virtual chassis. Actually bulk renaming already implemented. We need to call it when adding a device to virtual chassis. It would really help in the case of many virtual chassis. <!-- 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 None <!-- 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 added the pending closure label 2025-12-29 18:27:48 +01:00
adam closed this issue 2025-12-29 18:27:49 +01:00
adam commented 2025-12-29 18:27:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 14, 2020):

Optionally rename interfaces automatically when adding a device to a virtual chassis according to the predefined find/replace/regex variables.

This needs far more detail to be actionable. What is the proposed workflow? What modifications to existing forms are necessary? How will validation be handled?

@jeremystretch commented on GitHub (Feb 14, 2020): > Optionally rename interfaces automatically when adding a device to a virtual chassis according to the predefined find/replace/regex variables. This needs far more detail to be actionable. What is the proposed workflow? What modifications to existing forms are necessary? How will validation be handled?
adam commented 2025-12-29 18:27:50 +01:00
Author
Owner
Copy Link

@vsvetlov commented on GitHub (Feb 21, 2020):

I agree it can be difficult to rename during the procedure of adding a device to VC.
Having an option to consider device position in bulk renaming for VC would be enough.
It can be done by using a special pattern to highlight a position in interface name where we want to put device number. For example, we have 4 switches in VC with interfaces GigiabitEthernet[1-24] which we want to rename to GigiabitEthernet[1-4]/[1-24]

Find: GigabitEthernet
Replace: GigabitEthernet{p}/

where {p} is pattern we should replace with number of device position before regex().
I think more intelligent regex also can be used.

@vsvetlov commented on GitHub (Feb 21, 2020): I agree it can be difficult to rename during the procedure of adding a device to VC. Having an option to consider device position in bulk renaming for VC would be enough. It can be done by using a special pattern to highlight a position in interface name where we want to put device number. For example, we have 4 switches in VC with interfaces GigiabitEthernet[1-24] which we want to rename to GigiabitEthernet[1-4]/[1-24] Find: GigabitEthernet Replace: GigabitEthernet{p}/ where {p} is pattern we should replace with number of device position before regex(). I think more intelligent regex also can be used.
adam commented 2025-12-29 18:27:50 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 6, 2020):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@stale[bot] commented on GitHub (Mar 6, 2020): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:27:51 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 13, 2020):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@stale[bot] commented on GitHub (Mar 13, 2020): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure
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#3331
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?