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

New model: business system #5762

New Issue
Closed
opened 2025-12-29 19:32:21 +01:00 by adam · 7 comments
adam commented 2025-12-29 19:32:21 +01:00
Owner
Copy Link

Originally created by @xth0331 on GitHub (Dec 11, 2021).

NetBox version

v3.1.0

Feature type

New functionality

Proposed functionality

Is it possible to add a new model, which is used to describe business systems, such as OA or websites, which include virtual machines, servers, etc.

Not sure if it makes sense

Use case

This can integrate and classify multiple physical resources and virtual machine resources

Database changes

No response

External dependencies

No response

Originally created by @xth0331 on GitHub (Dec 11, 2021). ### NetBox version v3.1.0 ### Feature type New functionality ### Proposed functionality Is it possible to add a new model, which is used to describe business systems, such as OA or websites, which include virtual machines, servers, etc. Not sure if it makes sense ### Use case This can integrate and classify multiple physical resources and virtual machine resources ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:32:21 +01:00
adam closed this issue 2025-12-29 19:32:21 +01:00
adam commented 2025-12-29 19:32:22 +01:00
Author
Owner
Copy Link

@apellini commented on GitHub (Dec 11, 2021):

It could be useful to explain application stack present in your organization

@apellini commented on GitHub (Dec 11, 2021): It could be useful to explain application stack present in your organization
adam commented 2025-12-29 19:32:22 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 13, 2021):

I'm not sure what you mean by "business system." Can you elaborate on your proposed implementation please? It would help to provide an example or two.

@jeremystretch commented on GitHub (Dec 13, 2021): I'm not sure what you mean by "business system." Can you elaborate on your proposed implementation please? It would help to provide an example or two.
adam commented 2025-12-29 19:32:22 +01:00
Author
Owner
Copy Link

@xth0331 commented on GitHub (Dec 15, 2021):

Sorry, my English is poor, For example, a search service,It contains multiple virtual machines.

@xth0331 commented on GitHub (Dec 15, 2021): Sorry, my English is poor, For example, a search service,It contains multiple virtual machines.
adam commented 2025-12-29 19:32:22 +01:00
Author
Owner
Copy Link

@zombah commented on GitHub (Dec 16, 2021):

Sorry, my English is poor, For example, a search service,It contains multiple virtual machines.

I use tags for such things.
For example create tag busines_system_search_service and apply this tag
to all involved elements: vm's, int's, ip's and etc.

@zombah commented on GitHub (Dec 16, 2021): > Sorry, my English is poor, For example, a search service,It contains multiple virtual machines. I use tags for such things. For example create tag busines_system_search_service and apply this tag to all involved elements: vm's, int's, ip's and etc.
adam commented 2025-12-29 19:32:23 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 21, 2021):

I'm afraid this isn't an actionable feature request without much more detail around the proposed implementation and its use case. Perhaps consider starting a discussion to work out exactly what it is you'd like to see added to NetBox. Once you've sorted out these details and fleshed out a complete proposal we can revisit the feature request.

@jeremystretch commented on GitHub (Dec 21, 2021): I'm afraid this isn't an actionable feature request without much more detail around the proposed implementation and its use case. Perhaps consider starting a [discussion](https://github.com/netbox-community/netbox/discussions/new) to work out exactly what it is you'd like to see added to NetBox. Once you've sorted out these details and fleshed out a complete proposal we can revisit the feature request.
adam commented 2025-12-29 19:32:23 +01:00
Author
Owner
Copy Link

@apellini commented on GitHub (Dec 21, 2021):

Sorry for late response. This feature could be useful because we could create a relationship model based on Application that are running on our DC and relate them network resource to build standards to construct your Application Stack and giving modeling that could be used on CI/CD pipelines.

Below an example. Development team A develops applications based on LAMP Application stack and SysAdmin deploy three server for each application, one dedicted to Apache with mod_proxy module, one for PHP backend and one MySQL/MariaDB for DB, this one is totally managed by DBA.

Each of this services has their management application on common environment that hosts Ansible, GIT Repo and Backup services.

Network Admins for having control of network opening needs to dedicate a network for each layer in a non-SDN environment.

Using this model we could correlate application layer to network in order to map and mantain this correlation and permits to automation to build correctly all application.

Also if you correlate network opening to this model you could create an automation that could clone openings in case of network expansion or implement network micro segmentation between layers.

@apellini commented on GitHub (Dec 21, 2021): Sorry for late response. This feature could be useful because we could create a relationship model based on Application that are running on our DC and relate them network resource to build standards to construct your Application Stack and giving modeling that could be used on CI/CD pipelines. Below an example. Development team A develops applications based on LAMP Application stack and SysAdmin deploy three server for each application, one dedicted to Apache with mod_proxy module, one for PHP backend and one MySQL/MariaDB for DB, this one is totally managed by DBA. Each of this services has their management application on common environment that hosts Ansible, GIT Repo and Backup services. Network Admins for having control of network opening needs to dedicate a network for each layer in a non-SDN environment. Using this model we could correlate application layer to network in order to map and mantain this correlation and permits to automation to build correctly all application. Also if you correlate network opening to this model you could create an automation that could clone openings in case of network expansion or implement network micro segmentation between layers.
adam commented 2025-12-29 19:32:23 +01:00
Author
Owner
Copy Link

@bluikko commented on GitHub (Dec 24, 2021):

I too currently use tags for this sort of thing. But it will be not manageable in the long run as more "business systems" are documented in NetBox - there would be dozens of tags.

I too would find something like this useful. Much, much more implementation details would be needed...

Sounds like there would be a new model, say "Application", that could refer to other models. What models would it refer to? What attributes would such a model have?

@bluikko commented on GitHub (Dec 24, 2021): I too currently use tags for this sort of thing. But it will be not manageable in the long run as more "business systems" are documented in NetBox - there would be dozens of tags. I too would find something like this useful. Much, much more implementation details would be needed... Sounds like there would be a new model, say "Application", that could refer to other models. What models would it refer to? What attributes would such a model have?
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: revisions needed 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#5762
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?