Re: [Glpi-dev] Multientity management & share stock between subentities
Bonjour, Cordialement, David DURIEUX Tel : +33 (0)4.74.04.81.34 Port : +33 (0)6.34.99.45.18 Mail : d.duri...@siprossii.com Site Web : http://www.siprossii.com/ SIPROSSII 847 route de Frans (Créacité) 69400 Villefranche sur Saône FRANCE Le Fri, 19 Nov 2010 08:15:56 +0100 Walid Nouh a écrit: >Le 18/11/2010 21:48, David DURIEUX a écrit : >> Le Thu, 18 Nov 2010 20:46:33 +0100 >> Walid Nouh 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? >> >> >This is not my initial question, and it's related to fusioninventory >right ? > >Walid. You say on actual rules or futur rules (with rules / rulecollection) class of OCS ? David ___ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
Re: [Glpi-dev] Multientity management & share stock between subentities
Le 18/11/2010 21:48, David DURIEUX a écrit : Le Thu, 18 Nov 2010 20:46:33 +0100 Walid Nouh 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? This is not my initial question, and it's related to fusioninventory right ? Walid. ___ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
Re: [Glpi-dev] Multientity management & share stock between subentities
Le Thu, 18 Nov 2010 20:46:33 +0100 Walid Nouh 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
[Glpi-dev] Multientity management & share stock between subentities
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 What do you think about it ? We may try to make it more configurable, to handle shared stocks for a set of entities (for a shared stock for a group of entities). Walid ___ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
[Glpi-dev] Une première documentation pour GLPI version 0.78 est enfin disponible !
Initiée lors des HackWeeks d'Amiens en 2010 http://hackweeks.epplug.org/fr-fr/genese-des-hackweeks, elle est le fruit du travail d'une dizaine de contributeurs. Au delà de la rédaction de la documentation, un travail important d'harmonisation et de simplification a été réalisé en parallèle ) afin de rendre l'application plus compréhensible par les utilisateurs. Une partie de ces travaux est déjà visible sur la version 0.78 de GLPI , le reste le sera pour la version 0.80 disponible d'ici quelques mois. Il reste encore beaucoup de relecture et d'écriture à faire afin arriver à une documentation complète tant la tâche est longue et chronophage : la prochaine étape est une documentation complète pour GLPI version 0.80 disponible en français ET en anglais. Le projet a donc fortement besoin de nouveaux contributeurs pour la documentation, de relecteurs, et traducteur. Le renforcement de l'équipe de documentation actuelle est une étape indispensable. Si vous utilisez GLPI et que vous cherchez une manière de contribuer, alors n'hésitez plus ! GLPI a besoin de vous ! Rejoignez nous : - La liste de diffusion de l'équipe de documentation : https://mail.gna.org/listinfo/glpi-doc - L'espace de conception de la documentation : https://forge.indepnet.net/projects/glpidoc La documentation est disponible dans l’espace de téléchargement du site du projet GLPI. L'équipe de documentation, ___ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
