I have now done some initial testing of the basic CMDB-part if Cmdbuild. For the moment, we are not interested in the workflow-part. I have a few questions.
- Are you supposed to never remove objects from the database? It seems like a nice idea to be able to follow the lifecycle of servers, but it has certain challenges. It is always tricky to handle the cases where
- A host changes to new hardware
- The old hardware passes to another host
- Hosts are removed, and the hardware becomes another host
- I'm guessing that it is a good idea to model the two classes "host" and "server_hardware", and have them connected with a Domain. Is this a known approach? Is it easy to remove a domain from one hostcard and connect it to another hostcard?
- We have various sources for the information, and some of them are databases that we can adapt the external connectors for. For some other information we probably have to use the CSV import. How do these two (external connector and CSV import) handle deletions? If a card/host/whatever disappears from one datasource, will it then be deleted/disactivated in Cmdbuild?
Finally, some wishes
- It would be practical to save searches.
- In the LDAP-auth-part, it would be very practical and timesaving to be able to say:
We have hundreds of potential users of Cmdbuild, and they are already categorized by group memberships in LDAP. We want to say something like this in ldap,conf:
- Allow all users to try to authenticate
- If the password is correct, then
- check if the user is a member of a few certain LDAP groups, then
- map these groups to groups in Cmdbuild
and so on.
- "unix-admins" in LDAP -> "admins" in Cmdbuild
- "windows-admins" in LDAP -> "admins" in Cmdbuild
- "operators" in LDAP -> "readonly" in Cmdbuild
--
Ståle