In the current deployment of Foreman we are thinking hard how can we
centralize the data source into single repository in order to have all the
information regarding hosts, domains, puppet classes etc. in one place. I
see there is LDAP support in Foreman, but as far as I know it is only for
the authentication purposes. Are there any attempts to extend the LDAP
support in Foreman?
I was thinking about substituting the model layer in Foreman code to
interface LDAP instead of the database, what do you think about such idea?
Does it make sense for you? Maybe anyone has already tried it?
Well Foreman's database is just using Rails' ActiveRecord ORM mapping and
can (in theory) support whatever ActiveRecord supports. At this point I
believe the only tested backends are sqllite, mysql, and postgresql.
Storing node information in LDAP isn't a trivial change, and probably
doesn't make sense for this project. (That said if someone where to write
something in a maintainable fashion, it might be doable.)
One option if you really need this info in LDAP, is you could write a sync
tool that interfaces with Foreman's API, to export the data into LDAP, but
I don't know your goals here, so don't know if that would make sense.
-Brian
···
On Thu, Dec 20, 2012 at 5:19 PM, stefan wrote:
I was thinking about substituting the model layer in Foreman code to
interface LDAP instead of the database, what do you think about such idea?
Does it make sense for you? Maybe anyone has already tried it?
