VM to Server

jonash

Am I overlooking the option to assign a VM to a server? So that you can see at a glance that VM1 belongs to HyperV1, etc.?

If this feature does not yet exist, please consider it a feature request.

magixnetworks

Can see a use for this when it's a standalone server. But in a cluster with HA where VMs are moving between hosts this can get out of date very fast

jonash

magixnetworks Yes, I agree. However, I often find myself in a situation where I have several HyperV hosts at a customer's site that are not running as an HA cluster.

And even with an HA cluster, a VM has a primary server, which is why I find this function to be very useful.

Michal

jonash

Hello Im using "services" module. Just add Hyper-V and VM as assets.

jonash

Michal Hello Im using "services" module. Just add Hyper-V and VM as assets.

That would be a temporary solution.

But it's not really a proper solution...

I can't document any access data there, let alone an IP address.

Documentation of hardware (RAM, CPU, etc.) would also be cool, of course.

wrongecho

I usually put the hypervisor name under make or model.

jonash

wrongecho

That would certainly be one option. However, I still think it makes sense to introduce this as a function.

If I've learned one thing, it's that IT people are “lazy.”

As an end user of ITFlow, I don't want to have to remember the name of the customer server every time so that I can enter it again or copy and paste it into the next screen when editing the VM.

Why take these “detours” when there is an easier way?

An example from an expensive German system for system houses

I can see immediately that HV01 has assigned several VMs. At a glance, without reading.

johnny

I think a many to many asset relation would work well here

For Example you can relate one asset to another hench a VM in a HyperV or Proxmox Hyepervisor