Le Thu, 18 Nov 2010 20:46:33 +0100 Walid Nouh <walid.n...@gmail.com> a écrit:
>Hello, > >Today I've faced a problem when I tried to setup rules and automatic >links between computers in OCS & GLPI. > >1 - Computers that are in stock are manually encoded and stored in a >specific entity. When the computers is delivered by the supplier, we >have no idea where it's going to be dispatched. > >2 - The computer is the put in service and the OCS Inventory or >FusionInventory agent is installed and send his inventory in the OCS >Server. > >3 - The GLPI synchronization process detects a new computer in OCS : >it goes through the rules engine and a target entity is assigned. Then >GLPI try to find a computer with, in my case, the same serial number. >Of course it won't find anything, and will create a new computer => so >we get doubles into GLPI :( > >My idea will be to extend the link process and be able to specific in >the OCSNG Mode configuration an entity in which GLPI will try, >alternatively, to look for the computer : > >1 - GLPI synchronization process detects a new computer : it goes >through the rules engine and a target entity is assigned >2 - GLPI try to find a computer with the same serial number >3 - not computer found : run the same search but on the alternate >entity configured in OCSNG mode >4 - computer found in this entity : transfer the GLPI computer first >in the target entity and the link the 2 computers > It seems good but do you make same thing when you have : Rule 1 => serial Rule 2 => uuid Rule 3 => macaddress Rule4 .... do we search on each entity for each rule or when all don't match we retry all in all entities? David _______________________________________________ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
