GOsa and opsi

[pav5088]

I see that GOsa has the capability of integrating with opsi. Has anyone tried this? I'm unsure of how GOsa and opsi should interact with eachothers data in LDAP. It seems to be very new, and all undocumented at the moment unfortunately.

[pav5088]

I should also mention that the LDAP configuration section of the manual seems to be out of date for opsi v1.3.1 (and of course v1.4). I tried to get opsi+LDAP working anyway by guessing some configuration values, but still no luck.

I must say that I'm very excited by this product. I wrote my own solution years ago based on Unattended, and some scripts and C (for querying hardware/software config via the win32 api)... but it was command line, unfriendly and messy, and it died after I left the university position where I maintained it. It did get me interested in this kind of thing though... it's fun! I couldn't understand why people here were more interested in web development etc.. etc...

[d.oertel]

Hi,

the integration of opsi and gosa is new and maintained by Gonicus.
So try the gosa forum:
https://oss.gonicus.de/labs/gosa/discussion

If get no answers there - so please come back to this place.

regards

detlef oertel

[pav5088]

I posted on the GOsa mailing list on Thursday night (was Friday morning for me in Australia). I could give it a few more days.

I'm trying opsi+LDAP and am having problems. I'm getting :
Opsi service error: [BackendIOError]{'info': 'no structural object class provided', 'desc': 'Object class violation'}
Opsi service error: [BackendMissingDataError] Host 'amd64.strategicit.homelinux.net' does not exist: No results for search in baseDN

I change 30_vars.conf to :

self.defaultBackend = BACKEND_LDAP
self.clientManagingBackend = BACKEND_LDAP
self.pxebootconfBackend = BACKEND_OPSIPXECONFD
self.passwordBackend = BACKEND_FILE31
self.pckeyBackend = BACKEND_FILE31
self.swinventBackend = BACKEND_FILE31
self.hwinventBackend = BACKEND_FILE31
self.licenseBackend = BACKEND_MYSQL
self.loggingBackend = BACKEND_FILE31

I change the following config in /etc/opsi/backendmanager.d/11_ldap.conf
self.backends[BACKEND_LDAP] = {
'load': True
}

and also I had to change the bindDN line to :
"bindDn": "cn=admin,dc=my,dc=domain,dc=com",
...where my.domain.com was my domain. (What does the original bindDN line do anyway? I didn't understand it. It didn't seem to work for me. I guess this is probably pointing to an issue?)

Also, this was my post to the GOsa forums :

-----
How does GOsa and opsi fit together? I've discovered the instructions
for giving opsi an LDAP backend, but I'm wondering what part GOsa +
server infrastructure plays. Is there any additional configuration
required? (I think Jan hinted that GOsa could eg. run queries on an
opsi server - presumably with a MySQL backend for caching configuration
data etc...).
----

[pav5088]

For anyone who's interested Cajus's reply (the main developer of GOsa) is here : https://oss.gonicus.de/pipermail/gosa/2 ... 03974.html

Basically GOsa doesn't rely on opsi's LDAP support for integration - apparently opsi's schema doesn't mesh well with GOsa. I guess this means I don't have to use the LDAP backend for opsi, so that particular problem goes away.