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

Front/Back racks mirroring (option) #2520

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

Originally created by @deku-m on GitHub (Apr 15, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5.8

Proposed Functionality

When you stand in front of racks it depends on how you number the racks, if for example you start numbering your racks from 1,2,3,4,5 (front) with left hand 1 and on your right hand 5.

FRONT:
| 1 | 2 | 3 | 4 | 5 |

When you change position in reality, it would be.

BACK:
| 5 | 4 | 3 | 2 | 1 |

Summary:
On the left it is 1 and right is 5. If you change your position to the back of the rack. It is normally reversed. On the right you start with 1 and on the left is 5.
So if you now choose your rack groups and you have like 2 or more racks in it and switch between front/back its not as the view in reality when you are standing in front of it.

A option/button could be to mirror/reflect it.
So it will rearrange numbering backwards depends on what the start rack view is.

Other option is to use to fields above and state in there what left or right is. and reverse this on changing from fron to back or other way around. All depends on the devices positions.

This may sound stupid indead. Hope it makes some sense.

Use Case

As told above you dont make mistakes when you stand in front of the racks (back/front) because it matches the reality. Some people in netbox look at a site select this and then select a rackgroup which is in our environment a MER or SER with racks in it. If they change there position and look at the racks it doesn't match the overview with numbering when you think of it.

Database Changes

Dont know this exactly.

External Dependencies

N/A

Originally created by @deku-m on GitHub (Apr 15, 2019). <!-- 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.2<!-- Example: 3.5.4 --> * NetBox version: 2.5.8<!-- Example: 2.3.6 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality When you stand in front of racks it depends on how you number the racks, if for example you start numbering your racks from 1,2,3,4,5 (front) with left hand 1 and on your right hand 5. **FRONT:** | 1 | 2 | 3 | 4 | 5 | When you change position in reality, it would be. **BACK:** | 5 | 4 | 3 | 2 | 1 | **Summary:** On the left it is 1 and right is 5. If you change your position to the back of the rack. It is normally reversed. On the right you start with 1 and on the left is 5. So if you now choose your rack groups and you have like 2 or more racks in it and switch between front/back its not as the view in reality when you are standing in front of it. A option/button could be to mirror/reflect it. So it will rearrange numbering backwards depends on what the start rack view is. Other option is to use to fields above and state in there what left or right is. and reverse this on changing from fron to back or other way around. All depends on the devices positions. This may sound stupid indead. Hope it makes some sense. <!-- 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 As told above you dont make mistakes when you stand in front of the racks (back/front) because it matches the reality. Some people in netbox look at a site select this and then select a rackgroup which is in our environment a MER or SER with racks in it. If they change there position and look at the racks it doesn't match the overview with numbering when you think of it. <!-- 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 Dont know this exactly. <!-- 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 N/A
adam closed this issue 2025-12-29 18:19:36 +01:00
adam commented 2025-12-29 18:19:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 15, 2019):

NetBox does not know how racks are physically ordered on a floor, thus it is not possible to provide this. (We can't assume that they are physically in order by facility ID or name.)

@jeremystretch commented on GitHub (Apr 15, 2019): NetBox does not know how racks are physically ordered on a floor, thus it is not possible to provide this. (We can't assume that they are physically in order by facility ID or name.)
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#2520
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?