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

Request for the option to move a physical to a VM once a device is P2V'd #4399

New Issue
Closed
opened 2025-12-29 18:35:37 +01:00 by adam · 5 comments
adam commented 2025-12-29 18:35:37 +01:00
Owner
Copy Link

Originally created by @waynster on GitHub (Dec 23, 2020).

Environment

  • Python version: 3.6
  • NetBox version: 2124f31f2d87 (v2.9.7)

Proposed Functionality

Can it be considered to have a function to transfer (p2v) a physical to a VM entry? We are busy retiring lots of legacy hardare to VMs and currently deleting and creating new entries is cumbersome

We virtualize a physical system to a VM
Firstly we go into netbox device entry for the old physical
Click edit then have a field or button to virtualize host
Clicking this presents dropdowns/fields for renaming, resizing, new cluster, cluster group region, comments, local configuration context data etc.
Once submitted, new VM is created, also old physical is marked as offline

Use Case

For virtualizing servers as stated

Database Changes

Not known/N/A

External Dependencies

Not known/N/A

Originally created by @waynster on GitHub (Dec 23, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6 * NetBox version: 2124f31f2d87 (v2.9.7) <!-- --> ### Proposed Functionality Can it be considered to have a function to transfer (p2v) a physical to a VM entry? We are busy retiring lots of legacy hardare to VMs and currently deleting and creating new entries is cumbersome <!-- ---> We virtualize a physical system to a VM Firstly we go into netbox device entry for the old physical Click edit then have a field or button to virtualize host Clicking this presents dropdowns/fields for renaming, resizing, new cluster, cluster group region, comments, local configuration context data etc. Once submitted, new VM is created, also old physical is marked as offline ### Use Case For virtualizing servers as stated <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Not known/N/A <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies Not known/N/A
adam added the plugin candidatepending closure labels 2025-12-29 18:35:37 +01:00
adam closed this issue 2025-12-29 18:35:37 +01:00
adam commented 2025-12-29 18:35:38 +01:00
Author
Owner
Copy Link

@rodvand commented on GitHub (Jan 1, 2021):

This sounds like a perfect use case for a custom script.

@rodvand commented on GitHub (Jan 1, 2021): This sounds like a perfect use case for a custom script.
adam commented 2025-12-29 18:35:38 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 5, 2021):

As @rodvand mentioned, this would be best handled with a custom script or plugin that creates a VM, creates new data, then deleted the old device.

We are not going to be adding this to the base functionality and this will be pending closure.

@DanSheps commented on GitHub (Jan 5, 2021): As @rodvand mentioned, this would be best handled with a custom script or plugin that creates a VM, creates new data, then deleted the old device. We are not going to be adding this to the base functionality and this will be pending closure.
adam commented 2025-12-29 18:35:38 +01:00
Author
Owner
Copy Link

@sdktr commented on GitHub (Jan 8, 2021):

@Mathijsvanwilligen tagging for future reference re: migration script

@sdktr commented on GitHub (Jan 8, 2021): @Mathijsvanwilligen tagging for future reference re: migration script
adam commented 2025-12-29 18:35:38 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 5, 2021):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@stale[bot] commented on GitHub (Mar 5, 2021): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:35:39 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 21, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@stale[bot] commented on GitHub (Mar 21, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure plugin candidate
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#4399
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?