
Oved, totally agree about externalizing the configuration. Also I like Roy Golan's recommendation of a wiki design page, because I can probably offer more in the design phase than the actual coding phase. I know the OpenLDAP schema interface rather well, and I have my own OID so I can define globally useful oVirt schema for you if you'd like to go that route. You guys are always very helpful and encouraging, which is why this project moves so fast. --Charlie On Wed, Nov 14, 2012 at 11:41 AM, Oved Ourfalli <ovedo@redhat.com> wrote:
----- Original Message -----
From: "Oved Ourfalli" <ovedo@redhat.com> To: "Jiri Belka" <jbelka@redhat.com>, medievalist@gmail.com Cc: users@ovirt.org Sent: Wednesday, November 14, 2012 3:50:45 PM Subject: Re: [Users] Ovirt 3.1 and Samba4 AD
----- Original Message -----
From: "Jiri Belka" <jbelka@redhat.com> To: users@ovirt.org Sent: Wednesday, November 14, 2012 9:30:39 AM Subject: Re: [Users] Ovirt 3.1 and Samba4 AD
On 11/13/2012 09:40 PM, Charlie wrote:
I would like to help oVirt gain compatibility with standards-based services like OpenLDAP, but the code's in a language I haven't used and a version control system I haven't used and the wiki has no LDAP interaction design documents (other than the sources themselves) and I've got very limited free time, all of which makes it hard to contribute.
+1
We do have some wiki pages that can be useful to set up a development environment, like: http://wiki.ovirt.org/wiki/Working_with_oVirt_Gerrit http://wiki.ovirt.org/wiki/Building_oVirt_engine
Architecture page: http://wiki.ovirt.org/wiki/Architecture
And specifically, there is a wiki page on the LDAP infrastructure, that can give a clue on what entities we have there, and how to work with them: http://wiki.ovirt.org/wiki/DomainInfrastructure
When looking at OpenLDAP before I remember the issue was that we didn't have any standard schema to work with, that had all the different attributes we need. Currently, we require to authenticate to a Kerberos server. Also, the configuration of the different provider queries is done inside the source code, and not configured externally. So, IMO the best way to add a new OpenLDAP provider is first to externalize this configuration, so that anyone can tweak it out according to his schema.
I hope the wiki pages above can give a clue on the infrastructure, but we would be more than happy to help guiding you about that. The relevant people are Yair Zaslavsky (yzaslavs@redhat.com), and Roy Golan (rgolan@redhat.com), and myself, which did the latest work on this infrastructure, so we would be more than happy to help on IRC, E-mails, phone calls, and etc.
Another relevant mailing list is engine-devel@ovirt.org, where most engine developers are, so that's the best place to get guidance regarding git, gerrit, java, and every development matter.
Oved
--
Jiri Belka jbelka@redhat.com _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users