Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New hierarchy for ordinary companies #2241

Closed
andershagman opened this issue Jul 15, 2018 · 1 comment
Closed

New hierarchy for ordinary companies #2241

andershagman opened this issue Jul 15, 2018 · 1 comment
Labels
status: duplicate This issue has already been raised

Comments

@andershagman
Copy link

Issue type

[X ] Feature request
[ ] Bug report
[ ] Documentation
[ ] Housekeeping

Environment

  • Python version: 3.6.5
  • NetBox version: 2.3.5

Description

Netbox is great and is a software I have bin locking for for a long time. But, as we say, it uses a hierarchy like "world -> country -> town and last site and the devices. This is probably the right way for service providers but does not fit ordinary company's or organisations like ours that is healthcare. I know that you kan use regions in what way you want but regions are only placeholder and all the information is inside the site object.
As an example we have only one region, and the name is really "Region Kalmar". Next level is typically the site with all the info regarding contact, address and what kind of type of healthcare we have. Next we have buildings, floors, rooms, racks and last devices.
In my attempt to fit our organisation in Netbox I have user rack groups as rooms and ignored buildings and floors using naming like Buildingxx-Flooryy-Roomzz. It works but is not ideal. Also a rack group is not searchable by text and with around 500 rooms it is a long list.
It would be nice with a model like Company -> site -> building -> floor -> room as we have in Cisco Prime.

@jeremystretch
Copy link
Member

Hierarchical rack groups are addressed in #1754

@jeremystretch jeremystretch added the status: duplicate This issue has already been raised label Jul 16, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jan 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue has already been raised
Projects
None yet
Development

No branches or pull requests

2 participants