Asset Feature Suggestions: Hypervisors & VM Linking

JoeV

Hi everyone,

I’ve got a few suggestions to level up the Assets section in ITFlow, especially for virtualized setups:

Add ‘Hypervisor/VM Host’ Type: We should have an asset type for hypervisors (e.g., VMware ESXi, Hyper-V, Proxmox) to track these critical hosts properly.
Link Virtual Machines to Hypervisors: If an asset’s type is ‘Virtual Machine,’ let us link it to a Hypervisor/VM Host asset. This would make visualizing VM relationships a breeze.

JoeV

I’ve got another quick tweak to suggest for ITFlow’s Assets:

Virtual Machine Icon: The current cloud icon for VMs feels off since they’re often local (e.g., on a hypervisor). Something like a server stack or VM symbol would fit better—any thoughts on a more appropriate icon?
Add a VPS Category: How about a ‘VPS’ (Virtual Private Server) type for hosted servers (e.g., AWS, DigitalOcean)? It’d help distinguish them from local VMs and physical boxes.
Custom Categories: Better yet, why not let us create custom asset types? It’d make ITFlow way more flexible—imagine adding ‘Firewall,’ ‘NAS,’ or whatever fits our setups—without waiting for official updates.

JoeV

While we are at it, why not add.
Virtual Switch Type: Add a ‘vSwitch’ asset type to represent virtual switches (e.g., VMware vSwitch, Hyper-V Virtual Switch). Tat type should be able to;

Link to Hypervisor: Let us tie each vSwitch to a Hypervisor/VM Host asset, since they’re part of that ecosystem.
Link VM Ports: Allow VMs to connect their ports to a vSwitch—like how we’d map NICs to virtual networks in real setups.

Jambery

I like this, We handle a lot of virtualized environments

litechforce

Jambery

As do I. I would also love to see this!

johnny

We plan to have asset linking with other assets, so this is where linking a VM to a hypervisor will come into play.

ontariokicker44

johnny Is there hope to have cross client linking of assests? We host a "cloud" so our clients may have VMs that are on another "clients" hypervisor