ClearFoundation

DRAFT: Replicate Initiative

In the past versions of ClarkConnect (now ClearOS) we have been working on laying a foundation for some exciting initiatives, namely getting multiple servers working together in the same security context. Now that ClearOS 5.1 has been released and we look to the future we are still overwhelmed at the lack of solid options and solutions in the Small Business and Distributed Enterprise market for truly integrated Linux and multi-platform solutions.

The Foundation has been laid and here we will start to create the changes that will make ClearOS interoperate in other ClearOS boxes seemlessly and also initiatives for interoperability to other directory services infrastructures such as Active Directory.

All of the information in this section and these sub-sections is subject to change and represents open development feedback should be posted in the appropriate discussion threads which should be linked from this and other documents.

Tentative initiative volunteers and staff

John Terpstra - Architecture/Oversight/Testing
Darryl Sokoloski - ClearOS integration/Development/UI/Testing
Peter Baldwin - Development/Oversight/Integration/Testing
Dave Loper - Specification/Architecture/External OS integration/Testing

Background

John has worked with Samba and LDAP integration for years and has created scalable/integrated LDAP solutions with PDC/BDC functionality (in fact he's written a book on it.) Dave has worked with Directory server and identity integration on multiple platforms including OpenLDAP, AD, eDir and others. Peter is a linux coder and brilliant integrator and has more ClarkConnect/ClearOS knowledge than nearly anyone. Darryl is a brilliant developer who silently produces some of the best solutions available on ClearOS.

Code

The following are code exchanges and correspondance relating to this development that has taken place thus far. Remember, this is only for testing purposes and is not meant for production:

Scope

Multi-server interoperability creates complexity with design. Servers must be aware of each other, share tasks, update each other when necessary, and provide active/active, failover, and ad hoc services under the same distributed services model. The following is a list of services and the scope of each including design, testing, and implementation.