Where should I import my virtual servers to have good relations with my physical servers ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi everyone,
I need to add the servers of one of my company's entities. I have added them to my assets, class servers.
So I have my Asset and my CI. Respectively in alm_hardware and cmdb_ci_server.
I checked the "Is virtual" box for virtual servers.
I need your help to create a relation between my physical and virtual servers.
I have several options available to me.
I have seen several places where people said to add virtual servers to both the cmdb_ci_server AND cmdb_ci_vm_instance tables.
What do you suggest I do ? The idea is to do it properly so that everything is in order when we actually integrate the CMDB.
And based on that, what would be the right relationship to use (Hosted on, virtualised by, etc.)?
Should we use a "Physical server" hosted on, and virtualise it itself in the cmdb_ci_vm_instance?
Thank you in advance for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
hi @NicolasMothes ,
How to store your servers
Physical servers: These go into the cmdb_ci_server table.
Virtual servers: Best practice is to put them in both:
cmdb_ci_server (so they’re treated like any other server in reports and integrations).
cmdb_ci_vm_instance (so you capture virtualization-specific details like VM ID, hypervisor, etc.).
That way, you don’t lose consistency, and you still get the extra VM attributes.
How to link them
A physical server is the host.
A virtual server (VM) is the guest.
So the relationship should be:
VM → Virtualized by → Physical server
This makes it clear that the VM depends on the physical host.
Other relationships like “Hosted on” are more for applications running on servers, not for VM-to-host links.
