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

Automatic creation of devices when populating bays #1201

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

Originally created by @wenners on GitHub (Aug 30, 2017).

Issue type

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

Environment

  • Python version: 3.4.5
  • NetBox version: 2.1.3

Description

A detailed description of the proposed functionality

I am struggling a bit with the concept that I need to pre-create a device for e.g. every line card I want to populate to a switch.
For more conveniance there could be some auto-generated device if I populate a device bay. In my idea this would add a drop-down for the device type and a "auto-genarate" button to the populate menu - in addition to "save" and "cancel". Anybody who wants to do assign an existing device could just use the menu as before.
This button would then create a device with the same properies as the parent, the selected type and device name could be "parent devicename"-"bay name", size 0.

A use case for the new feature

Populate new infrastructure more quickly

A rough description of any necessary changes to the database schema

None, just UI change and coding

Any relevant third-party libraries which would be needed

No

Originally created by @wenners on GitHub (Aug 30, 2017). ### Issue type [x] Feature request [ ] Bug report [ ] Documentation ### Environment * Python version: 3.4.5 * NetBox version: 2.1.3 ### Description #### A detailed description of the proposed functionality I am struggling a bit with the concept that I need to pre-create a device for e.g. every line card I want to populate to a switch. For more conveniance there could be some auto-generated device if I populate a device bay. In my idea this would add a drop-down for the device type and a "auto-genarate" button to the populate menu - in addition to "save" and "cancel". Anybody who wants to do assign an existing device could just use the menu as before. This button would then create a device with the same properies as the parent, the selected type and device name could be "parent devicename"-"bay name", size 0. #### A use case for the new feature Populate new infrastructure more quickly #### A rough description of any necessary changes to the database schema None, just UI change and coding #### Any relevant third-party libraries which would be needed No
adam closed this issue 2025-12-29 16:30:01 +01:00
adam commented 2025-12-29 16:30:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 21, 2018):

I am struggling a bit with the concept that I need to pre-create a device for e.g. every line card I want to populate to a switch.

NetBox does not currently support modeling line card within a device; see #824. If you're trying to use the device model to represent line cards, it's not going to work well.

For more conveniance there could be some auto-generated device if I populate a device bay.

You would still need to select a manufacturer, device type, and role, and likely set some other attributes as well. Trying to fit all this on the same page as creating a device bay would be convoluted. #1626 might have a better approach.

@jeremystretch commented on GitHub (Feb 21, 2018): > I am struggling a bit with the concept that I need to pre-create a device for e.g. every line card I want to populate to a switch. NetBox does not currently support modeling line card within a device; see #824. If you're trying to use the device model to represent line cards, it's not going to work well. > For more conveniance there could be some auto-generated device if I populate a device bay. You would still need to select a manufacturer, device type, and role, and likely set some other attributes as well. Trying to fit all this on the same page as creating a device bay would be convoluted. #1626 might have a better approach.
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#1201
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?