I've just upgrade my two GLPI installation from 0.68.X to the latest
0.71.5 version.
Not sufficient, thanks to the multi-entity feature of 0.71, i've done a
manual merge of my two GLPI installation by the way of manual 'UPDATE
TABLE ...', dump and restore.
I think i've lost a great quantity of neurons today, but seems to work.
;)
I've found some drawbacks in entities handling, so i'm seeking
feedback. But first my situation.
I'm the sysadmin of an nonprofit catholic organization aimed toward
care and research on disabled children.
The IT staff are located on a region, and my ragion have 2 branch, each
having one branch also (and branch cosnsist of a Samba server with LDAP
backend).
On previous setup i've simply 'ignored' the 2 sub-branch and installed
two GLPI instances for the 2 branch.
Today, i've sayed, i've marged the two installation (and clearly
enabled the 2 sub-branch, but this is not the point).
I've found two major trouble:
1) in the two branch office there's people that are different but have
the same login: eg in office SANVITO there's tiziana, in office PASIAN
there's tiziana also but they are not the same person.
I've had to do:
alter table glpi_users drop KEY `name`;
alter table glpi_users add key name (name);
because the key 'name' was defined as 'UNIQUE KEY'.
And if i ask tiziana (both one) to login to the system, i can see on
log the succesful login, but user seems like have logon and logoff (the
logon page display, after some flickering).
I've found that a similar trouble happens for group: i cannot import
group from domain PASIAN if they are the same name of groups in domain
SANVITO in GLPI LDAP import page.
But i can insert with SQL, and seems they work flawlessy...
So (apart the 'UNIQUE KEY' on name, that seems to me a mistake) i
suppose that for some reason you have choose not to have multiple
users...
Consider that normally in such complex systems there's a 'domain'
information, and users have a domain attribute (eg, tiziana\SANVITO and
tiziana\PASIAN), so i consider not so smart to have this restriction.
[The domain information can be explicitly setup in login box, but also
taken from the logon phase, eg, the user belong to the domains that
accept their password! ;-) ]
2) i've see that for some items (enterprises, contracts for example)
there's an information of 'recursion'.
Eg, if i put a contract on 'root', or on 'Polo FVG' (that contain
PASIAN and SANVITO) and set it as 'recursive' i ca see it on Polo FVG
but also on Pasian and Sanvito. The right thing. ;)
Why this is not possible for other items? Apart general
consideration on computers, monitors, ... that clearly are tipically
binded to a branch/entity, i've found this frustrating particulary for
software and cartdriges.
For software now i've the same software duped for the two branch, and
if i need to fire up a ticket on it, i've to choose what, and probably
when i will need to look at past tickets, i miss the right one. ;)
I consider better solution to add the 'recursion' function also to
other iterms, or, for software, to move the entity information from
software to licence, that clearly can be tighted to a particular
entity.
Same things for cartdrige (move from cartdrige_type to cartdrige).
I'm seeking feedback, hoping this can be useful to GLPI!
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La Nostra Famiglia'' http://www.sv.lnf.it/
Polo FVG - Via della Bontà , 7 - 33078 - San Vito al Tagliamento (PN)
marco.gaiarin(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797
Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
http://www.lanostrafamiglia.it/chi_siamo/5xmille.php
(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)
_______________________________________________
Glpi-user mailing list
[email protected]
https://mail.gna.org/listinfo/glpi-user
