New features of the LSC provisioning project with a particular focus about multi vendor support of on-the-fly updates notification
This proposal is a 2009 J. Clarke's talk update about the LSC provisioning project with a particular focus about directory on-the-fly update notifications
After two years of active project development, LSC project has reached a new level, version 2.0, with major features, new connectors and administration web interface.
After adding asynchronous support through pull or event based triggers, LSC is now a daemon that is manageable by the interface and JMX remote commands. It allows tasks to be started, stop, monitored and launched again on a particular identifiers list (for example to force particular user propagation ...). These actions can be achieved also through the web interface which embeds a scheduler for planned executions.
- A connector API has been stabilized and some connectors have been added:
- A source NIS connector
- A source LDAPSync customer connector
- A source / destination native executable based connector
- A source / destination web service connector
LSC is also now fully embeddable in a regular application (standalone, server or web) or can be wrapped as a separate service in order to provide an application provisioning engine (either in a SaaS architecture or in a product oriented way).
The talk will include a short presentation of the next version features including:
- A switch from a stack threaded model to a message oriented middleware in order to support natively distributed and highly available deployments.
- A built-in database to maintain a synchronization status from run to run in order to provide a stateful engine and conflict resolution
Then it will present the way the LSC has embedded a syncrepl consumer in order to support live update event notification. But directory server agents from various vendors implement their own synchronization protocol and sometimes a change log or an audit log and RFC 4533 is not widely supported. The talk will try and present various approaches in order to get some feedback about the way such applications must support this synchronization capability in a most vendor neutral way.