Support separate backend for system users

[jof]

I would like to get this cookbook into a state where it can be used to fully bootstrap a server and replication environment.
However, in its current form, it assumes some things about there being a single database and suffix.

For example, let's say I operate LDAP for example.com under dc=example,dc=com

If I want to bootstrap two nodes, replicating off of one another before loading in my data from a backup, replication can't exist, because the configuration is assuming that data is already loaded with a "syncrole" user.

Another approach I would like to have considered would be to setup a second back-ldif database and directory for system users, like for cn=syncrole, cn=config, etc.
It could be named "cn=system_users", for example, and into there we could create a user like "cn=syncrole,cn=system_users", independent of whatever BDB/HDB database content is being setup.

[acaiafa]

I am working on a branch right now that will allow some of these features. The first commit and merge will be library resources for group and user. Those will be up shortly as I am just away for a few days. Once that is up we can add the the ability to launch replicas easily. I have that cookbook locally and will push that up shortly as well.

[cheeseplus]

Now that we've gotten things back in a working state I'm going to be looking at making this a bit more flexible.