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

Reserve/Book device ports #1794

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

Originally created by @Za66ax on GitHub (Jun 18, 2018).

Issue type

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

Environment

• NetBox version: 2.3.4

Description
It would be nice to be able to connect an interface to an object that’s not in the database (i.e a host), today you’re required to have a device registered to be able to make a connection. For network devices/virtual machines that’s awesome. But if you are required to register all hosts I fear that the database would become cluttered with non-essential data. The port could maybe just be marked as either connected or reserved.
This would work perfectly with feature request #1957.

Originally created by @Za66ax on GitHub (Jun 18, 2018). Issue type [ X ] Feature request [ ] Bug report [ ] Documentation Environment • NetBox version: 2.3.4 Description It would be nice to be able to connect an interface to an object that’s not in the database (i.e a host), today you’re required to have a device registered to be able to make a connection. For network devices/virtual machines that’s awesome. But if you are required to register all hosts I fear that the database would become cluttered with non-essential data. The port could maybe just be marked as either connected or reserved. This would work perfectly with feature request #1957.
adam closed this issue 2025-12-29 17:19:10 +01:00
adam commented 2025-12-29 17:19:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 18, 2018):

NetBox supports "planned" connections. This is the most succinct way of representing a future connection. It does require that you add both hosts to the database, but the future host can also be designated as "planned."

@jeremystretch commented on GitHub (Jun 18, 2018): NetBox supports "planned" connections. This is the most succinct way of representing a future connection. It does require that you add both hosts to the database, but the future host can also be designated as "planned."
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#1794
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?