Wiki for NediImport plugin¶
- Wiki for NediImport plugin
Why NediImport is not accessing directly the Mysql database?¶
NediImport is accessing the Nedi Web Server and run the requests with CURL.
- it can be slower than direct requests to the MySQL database (this is something we try to minimize in our code)
- Usually the web interface changes much more than the MySQL database between NeDi versions, then maintenance is bigger for us developpers
- security/rights relies on NeDi itself
- if you already have access to NeDi, then it works without giving rights/access to MySQL
- it works for us because we don't have any rights to access the NeDi database
NediImport and FusionInventory¶
NediImport tries to get useful information already available in NeDi and shows it in GLPI. So if you like NeDi or if you have an already running NeDi instance it can be quite interesting as you won't need for example SNMP access to the network devices.
NeDi is already running for years on sites with several thousands of nodes.
The best is to compare both projects NeDi and FusionInventory from their websites and see what best fit your needs.
I don't think it's a good idea to run both at the same time though! :)
What is a virtual switch in NediImport?¶
When a managed switch sees more than one MAC address attached to one of its port, it means usually that a dumb switch (non managed) is connected to that port and that several nodes are connected. It can also be the case when you run virtual machines.
In such a case, to be able to show this information in GLPI we create a fake switch, which we call "virtual switch" and we connect all theses nodes to this virtual switch. This virtual switch gets its name from the parent switch and the port number on which it is connected.