An update from FusionInventory for GLPI development branch …
The future release will be named 2.3.0, and come with major improvements. This release target GLPI 0.78 as the supported platform. The task management module has been greatly improved.
See also translations of this screencast in portuguses.
Quick overview of the improvements :
-
Communication mode : both pull and push communication are supported.
- Pull: The agent takes the initiative to contact the server. The server answer with the list of all tasks assigned to the agent. This is very useful in an environment where the presence of the agents is not predictable. The server is waiting for agents requests and can’t force the precise schedule of a task.
- Push : The server takes the initiative to contact the agent. The agent, running as a service, is waiting for the order from the server. When waking up, the agent contacts the server. The server answer with the list of all tasks assigned to the agent.
</li>* Schedule : The task’s execution can be scheduled. For tasks using push communication, the starting time is the effective startup time of the action. For tasks using pull communication, the starting time defines the time where the server will begin to distribute the task to the agents.
- Agent selection: You can choose which agents have to perform a task, or let FusionInventory for GLPI dynamically manage a dynamic pool of agents.
-
Tasks and Actions : A task can contain an unlimited number of actions. For example a first action will wake up a computer (Wake On LAN) and a second one will perform an inventory.
-
Target definition : Action’s target, for example an IP range, a list of devices, a dynamic group of devices, etc…
- Display current running actions: All task in a running state are displayed.
- History : Task execution logs are available as history. Each task actions may have different states : prepared, started, running, ok, error, unknown.
- Dynamic pool of agents: When using the Push mode, the server looks for all agents running and allowed to run a specific module (inventory, netdiscovery, snmpinventory, wakeonlan). The server then balance the load of the process within the agents. For example if you use an IP range with 10 agents, each agent will have to do 1/10 of the whole job.
