search

fusioninventory / fusioninventory-for-glpi

FusionInventory plugin for GLPI
http://www.FusionInventory.org/
GNU Affero General Public License v3.0
362 stars 150 forks source link

Default location of virtual computers. #1424

Open ddurieux opened 9 years ago

ddurieux commented 9 years ago

Author Name: Tomás Abad (Tomás Abad) Original Redmine Issue: 2540, http://forge.fusioninventory.org/issues/2540 Original Date: 2014-06-11

By default, set up the location of a virtual computer equal to location of its host (physical) machine. With this approach, you can see easily the location of a virtual machine that changes of host following some kind of policy of its virtual environment.

ddurieux commented 9 years ago

Original Redmine Comment Author Name: David Durieux (@ddurieux) Original Date: 2014-06-12T00:15:57Z

So you want do change the location when change host?

The main problem is VM and host are not really linked in DB, the relation is calculated only when you display VM on host and Host in the VM

ddurieux commented 9 years ago

Original Redmine Comment Author Name: Tomás Abad (Tomás Abad) Original Date: 2014-06-12T12:47:58Z

As you know, in a virtual environment (VMware vShere, for example) a virtual machine doesn't have why to run in the same host it was created or started (VMware DRS, VMware vMotion, etc. technologies).

In virtual environments like VMware vSphere doesn't have sense to set up a location to virtual computers because that location changes automatically. Linking or setting up the location of a virtual machine (in that cases which the location is not locked previously) with the location of host it runs could be a great feature. How to do that is other question. ;)

Perhaps, the relation you talk about (those registries in the DB) is not needed. Perhaps it's possible realice that set up in import time (when information from FusionInventory Agents is received) or in 'Virtual host remote inventory' task time (when information from virtual host inventory is received).

ddurieux commented 9 years ago

Original Redmine Comment Author Name: Stoat Wblr (@Stoatwblr) Original Date: 2014-07-14T15:47:04Z

Tomás Abad wrote:

By default, set up the location of a virtual computer equal to location of its host (physical) machine. With this approach, you can see easily the location of a virtual machine that changes of host following some kind of policy of its virtual environment.

I'd like to take this further.

My opinion: Ideally the location of a host should be picked up from the location of the network outlet associated with the switch port it has been detected as being connected to during switch inventory.

This would save significant administrative overhead, especially in an academic environment like ours where people are moving offices regularly and moving laptops around several times per day. The initial recorded location of a machine is only accurate for a few months in most cases and users don't usually bother telling us when they move offices.

(If there isn't a network outlet associated with a switch port, then the location should be left as-is)

There are a lot of "disconnects" in glpi/fusion which need tying together. Automation is usually better than relying on a human to make changes... :)

ddurieux commented 9 years ago

Original Redmine Comment Author Name: David Durieux (@ddurieux) Original Date: 2014-08-27T06:59:46Z

But there is no location on ports in GLPI and too in the port of switch. So it's a little complex :p