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

Clouds in topology drawings #1148

New Issue
Closed
opened 2025-12-29 16:29:26 +01:00 by adam · 9 comments
adam commented 2025-12-29 16:29:26 +01:00
Owner
Copy Link

Originally created by @kopacko on GitHub (Aug 6, 2017).

Issue type: Feature Request

I have been working with the topology maps and currently, I am using a "site" as my WAN and a "site" as the Internet that I can then assign my WAN and INET ISP provider devices interfaces as connected to these sites. Then with my equipment attached to the ISP equipment a topology map gives a visual representation from a user access switch, through the distribution block, through the WAN aggregation block, across my Internet WAN and out the other side down to the user access switch. This little map isn't really for me, it's more for the desktop folks within my organization so that they can follow the path while troubleshooting end points.

It would be really nice to have some sort of the WAN/Internet option or cloud option to complete the connectivity of multiple sites without having to create "sites" that are not real.

Originally created by @kopacko on GitHub (Aug 6, 2017). <!-- Please note: GitHub issues are to be used only for feature requests and bug reports. For installation assistance or general discussion, please join us on the mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please indicate "bug report" or "feature request" below. Be sure to search the existing set of issues (both open and closed) to see if a similar issue has already been raised. --> ### Issue type: Feature Request I have been working with the topology maps and currently, I am using a "site" as my WAN and a "site" as the Internet that I can then assign my WAN and INET ISP provider devices interfaces as connected to these sites. Then with my equipment attached to the ISP equipment a topology map gives a visual representation from a user access switch, through the distribution block, through the WAN aggregation block, across my Internet WAN and out the other side down to the user access switch. This little map isn't really for me, it's more for the desktop folks within my organization so that they can follow the path while troubleshooting end points. It would be really nice to have some sort of the WAN/Internet option or cloud option to complete the connectivity of multiple sites without having to create "sites" that are not real.
adam closed this issue 2025-12-29 16:29:26 +01:00
adam commented 2025-12-29 16:29:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 7, 2017):

The topology map feature in NetBox is intended only to provide a convenient mechanism for illustrating a specific set of links. It is not a suitable replacement for curated documentation. You're going to be much better off drawing real maps with labels applicable to the context.

@jeremystretch commented on GitHub (Aug 7, 2017): The topology map feature in NetBox is intended only to provide a convenient mechanism for illustrating a specific set of links. It is not a suitable replacement for curated documentation. You're going to be much better off drawing real maps with labels applicable to the context.
adam commented 2025-12-29 16:29:27 +01:00
Author
Owner
Copy Link

@kopacko commented on GitHub (Aug 7, 2017):

I have Visios. But this is more of a centralized way of displaying said data. It's also for the rest of the team to view without having to deal with Visio. I've attached the beginnings of what I am building to show how each site is topologically connected via the WAN. The bottom half of the map will have the other WAN connections, Internet connections, etc.

Uploading NetBox Cloud.png…

@kopacko commented on GitHub (Aug 7, 2017): I have Visios. But this is more of a centralized way of displaying said data. It's also for the rest of the team to view without having to deal with Visio. I've attached the beginnings of what I am building to show how each site is topologically connected via the WAN. The bottom half of the map will have the other WAN connections, Internet connections, etc. ![Uploading NetBox Cloud.png…]()
adam commented 2025-12-29 16:29:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 8, 2017):

Do you want to extend the topology map rendering to include a "cloud" representing the provider of a circuit with only one termination? I think that would be reasonable.

I have Visios.

You can export them as PNGs and upload them as image attachments to individual sites.

@jeremystretch commented on GitHub (Aug 8, 2017): Do you want to extend the topology map rendering to include a "cloud" representing the provider of a circuit with only one termination? I think that would be reasonable. > I have Visios. You can export them as PNGs and upload them as image attachments to individual sites.
adam commented 2025-12-29 16:29:28 +01:00
Author
Owner
Copy Link

@kopacko commented on GitHub (Aug 8, 2017):

Yeap that's exactly what I am trying to accomplish is a central "object" to represent public or private central points. Like a WAN object that I can add "interfaces" to in order to join all my sites together.

Yes I know I can export the Visios but with a simple regex, my WAN topology could be dynamically represented by that awesomeness that is NetBox.

@kopacko commented on GitHub (Aug 8, 2017): Yeap that's exactly what I am trying to accomplish is a central "object" to represent public or private central points. Like a WAN object that I can add "interfaces" to in order to join all my sites together. Yes I know I can export the Visios but with a simple regex, my WAN topology could be dynamically represented by that awesomeness that is NetBox.
adam commented 2025-12-29 16:29:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 8, 2017):

Like a WAN object that I can add "interfaces" to in order to join all my sites together.

This would not be something we'd support in NetBox. NetBox is intentionally limited to defining real, concrete connections; it does not support abstraction.

@jeremystretch commented on GitHub (Aug 8, 2017): > Like a WAN object that I can add "interfaces" to in order to join all my sites together. This would not be something we'd support in NetBox. NetBox is intentionally limited to defining real, concrete connections; it does not support abstraction.
adam commented 2025-12-29 16:29:28 +01:00
Author
Owner
Copy Link

@kopacko commented on GitHub (Aug 8, 2017):

These are real, physical connections. These would be the Z side of Internet and WAN circuits collated into one object.

@kopacko commented on GitHub (Aug 8, 2017): These are real, physical connections. These would be the Z side of Internet and WAN circuits collated into one object.
adam commented 2025-12-29 16:29:28 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 8, 2017):

"The WAN" isn't a discrete physical object, so it doesn't get modeled in NetBox. The topology mapping functionality in NetBox is an ancillary feature provided as a convenience. Extending the data model solely for the sake of more complex drawings is out of scope for NetBox.

@jeremystretch commented on GitHub (Aug 8, 2017): "The WAN" isn't a discrete physical object, so it doesn't get modeled in NetBox. The topology mapping functionality in NetBox is an ancillary feature provided as a convenience. Extending the data model solely for the sake of more complex drawings is out of scope for NetBox.
adam commented 2025-12-29 16:29:29 +01:00
Author
Owner
Copy Link

@kopacko commented on GitHub (Aug 8, 2017):

Well that is incredibly disappointing. Thanks.

@kopacko commented on GitHub (Aug 8, 2017): Well that is incredibly disappointing. Thanks.
adam commented 2025-12-29 16:29:29 +01:00
Author
Owner
Copy Link

@KempWatson commented on GitHub (Jun 23, 2018):

I'd agree this is very disappointing.. generally awesome package, with this glaring omission I found in 5 minutes of using the product. Connecting to clouds is about 100% common nowadays, and kopacko is bang on that these are real, physical connections that can't be properly modelled in NetBox. Real shame.

@KempWatson commented on GitHub (Jun 23, 2018): I'd agree this is very disappointing.. generally awesome package, with this glaring omission I found in 5 minutes of using the product. Connecting to clouds is about 100% common nowadays, and kopacko is bang on that these are real, physical connections that can't be properly modelled in NetBox. Real shame.
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#1148
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?