starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Introduce a cloud model for representing unknown/abstract networks #4662

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

Originally created by @jeremystretch on GitHub (Mar 16, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v2.10.6

Feature type

Data model extension

Proposed functionality

Introduce a new model named Cloud within the circuits app. Circuit terminations will be able to bind to cloud instances to convey a connection to an unknown network. For example, you might define a provider's MPLS network as a cloud, with all related circuits terminating on a device interface at the A side and the cloud instance on the Z side (or vice versa).

Use case

Immediately, this model allows NetBox to better convey the concept of a network boundary, and to abstract external networks we don't necessarily and/or care about (such as in the example above).

Over a longer term, this model might be useful for extending cable tracing across circuits as discussed in #5879. It might also be useful for constraining the scope of virtual circuits or overlay networks once we undertake work on those features.

Database changes

  • Add the circuits_cloud table
  • Extend CircuitTermination to allow termination to Cloud instances

External dependencies

No response

Originally created by @jeremystretch on GitHub (Mar 16, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v2.10.6 ### Feature type Data model extension ### Proposed functionality Introduce a new model named Cloud within the circuits app. Circuit terminations will be able to bind to cloud instances to convey a connection to an unknown network. For example, you might define a provider's MPLS network as a cloud, with all related circuits terminating on a device interface at the A side and the cloud instance on the Z side (or vice versa). ### Use case Immediately, this model allows NetBox to better convey the concept of a network boundary, and to abstract external networks we don't necessarily and/or care about (such as in the example above). Over a longer term, this model might be useful for extending cable tracing across circuits as discussed in #5879. It might also be useful for constraining the scope of virtual circuits or overlay networks once we undertake work on those features. ### Database changes - Add the `circuits_cloud` table - Extend CircuitTermination to allow termination to Cloud instances ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:19:16 +01:00
adam closed this issue 2025-12-29 19:19:16 +01:00
adam commented 2025-12-29 19:19:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 1, 2021):

Note: Originally named "Cloud," this model has been renamed to "Provider Network" to be less ambiguous about its purpose.

@jeremystretch commented on GitHub (Apr 1, 2021): Note: Originally named "Cloud," this model has been renamed to "Provider Network" to be less ambiguous about its purpose.
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#4662
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?