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

Add "front-to-front" option for airflow. #6173

New Issue
Closed
opened 2025-12-29 19:37:41 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:37:41 +01:00
Owner
Copy Link

Originally created by @jcollie on GitHub (Mar 6, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.1.8

Feature type

Data model extension

Proposed functionality

Add "front to front" option for airflow.

Use case

The Cisco ISR4321 has its air exhaust and intake on the front, as seen in this diagram taken from a Cisco manual.

Screenshot from 2022-03-06 07-54-27

Database changes

None.

External dependencies

None.

Originally created by @jcollie on GitHub (Mar 6, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.1.8 ### Feature type Data model extension ### Proposed functionality Add "front to front" option for airflow. ### Use case The Cisco ISR4321 has its air exhaust and intake on the front, as seen in this diagram taken from a Cisco manual. ![Screenshot from 2022-03-06 07-54-27](https://user-images.githubusercontent.com/740022/156926435-b077958b-6a1e-4ed5-bff8-b1e859cd9f0b.png) ### Database changes None. ### External dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 19:37:41 +01:00
adam closed this issue 2025-12-29 19:37:41 +01:00
adam commented 2025-12-29 19:37:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 7, 2022):

Ignoring the absurdity of this design, if a device takes in and exhausts air from the same face, there's no need to track airflow direction.

@jeremystretch commented on GitHub (Mar 7, 2022): Ignoring the absurdity of this design, if a device takes in and exhausts air from the same face, there's no need to track airflow direction.
adam commented 2025-12-29 19:37:42 +01:00
Author
Owner
Copy Link

@jcollie commented on GitHub (Mar 9, 2022):

Yes, it's a silly design IMHO but it exists and was a relatively popular router in it's day. If we can't have "front-to-front" can we get "other" to indicate that it's not a passively cooled device and that the airflow is not unknown (which None would indicate to me).

@jcollie commented on GitHub (Mar 9, 2022): Yes, it's a silly design IMHO but it exists and was a relatively popular router in it's day. If we can't have "front-to-front" can we get "other" to indicate that it's not a passively cooled device and that the airflow is not unknown (which None would indicate to me).
adam commented 2025-12-29 19:37:42 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 9, 2022):

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.

@github-actions[bot] commented on GitHub (May 9, 2022): 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 19:37:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 12, 2022):

I'm going to add an option for "mixed," which IMO should cover all such odd corner cases.

@jeremystretch commented on GitHub (May 12, 2022): I'm going to add an option for "mixed," which IMO should cover all such odd corner cases.
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#6173
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?