One of my customers, who uses GLPI very extensively for asset management, recently brought me a new request wanting a central overview of their host and IP registration. These host names and IPs are currently being maintained across various applications and tools, although GLPI is used as the central administrative application.
As is so often the case, this situation has grown organically over time. There are also various departments that are allowed to put devices into operation in their own defined network area. So often what happens is that host names or IP addresses were incorrectly assigned twice. In addition, it has become difficult for employees in IT operations to keep track of all devices and maintain a complete inventory.
After some deliberation, we decided to expand their existing GLPI installation with a plug-in that can meet this requirement, which we named IPTool. In a more detailed joint analysis, we defined the following three main implementation steps:
Since several thousand devices may be loaded when these requirements are put into practice, every interface must of course be carefully tested. We are currently in the implementation phase of the first step and the data from five different applications are now already displayed in IPTool.
This use case shows once again how sometimes complex requirements can be processed via GLPI.
Due to the relatively simple creation of additional plug-ins, the functional scope of GLPI can be expanded in an interesting way.
The development of this IP tool is being carried out by my colleague Mirko Morandini.