Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Track VM hypervisor host #2553

Closed
ebusto opened this issue Nov 6, 2018 · 3 comments
Closed

Track VM hypervisor host #2553

ebusto opened this issue Nov 6, 2018 · 3 comments

Comments

@ebusto
Copy link

ebusto commented Nov 6, 2018

Environment

  • Python version: 3.5.4
  • NetBox version: 2.4.7

Proposed Functionality

It would be useful to track which physical device a VM resides on.

Use Case

In the case where a VM is not automatically migrated from one VM cluster member to another (such as with VMware vSphere's vMotion functionality), it would be quite useful to know which VMs would be impacted by a device failing or requiring maintenance.

Database Changes

One additional virtual machine field, which would be optional, along with a validation to ensure the device is a member of the cluster hosting the VM.

External Dependencies

None.

@ebusto
Copy link
Author

ebusto commented Nov 6, 2018

This also provides a mechanism to capture the relationship between bare-metal servers and their parent devices.

@jeremystretch
Copy link
Member

This was discussed at length in #142 during the original implementation. The current model was largely agreed upon and likely won't be substantially changed in the near future.

@ebusto
Copy link
Author

ebusto commented Nov 6, 2018

That's unfortunate, considering how trivial a change this is.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants