This page describes the bigger next steps in the development of Samba. The purpose is to point out the broader direction into which Samba is heading.
If a feature listed below is flagged as FUNDED, this means that someone is currently being paid to work on it. Hence there are realistic chances that this feature might be completed in a reasonably short time frame. For all other features, further involvement is needed: Otherwise it could even take years to complete even if a feature is flagged as work in progress (WIP), since these are usually being worked on in someone's spare time.
Involvement is highly welcome and can come in various guises: Manpower for coding, testing, documentation, ...
Contact the Samba Team go get involved!
File Server (smbd)
- FUNDED: Implment Multi-channel (Michael, Metze)
- FUNDED: Add support for Witness service (Günther, Metze)
- Prerequisite: A asynchronous RPC server. See DCERPC
- Clustering (continuous availability, scale-out) - Planning (Michael)
- Persistent file handles - Planning (Ira, Michael, ...)
- RDMA (SMB direct) - Planning (Metze, Richard, Michael)
- Directory leases
Clustering - CTDB
- integrate the clustered file server into selftest/autobuild - WIP (Michael)
- Performance on small-CPU platforms (like ARM)
- reduce CPU usage
- performance in clusters, TDB/CTDB
- Parallel, small I/O (HyperV) workload
Print Server (smbd|spoolssd)
Active Directory Server
- FUNDED: MIT Kerberos support (Andreas)
- FUNDED: Two-way forest trusts (Metze)
- FUNDED: Use the OpenLDAP Database engine and LDAP protocol handlers in AD server
- FUNDED: Knowledge Consistency Checker (KCC)
- Directory Replication Service (DRS)
- Sysvolume Replication
- Subdomain support
- One way trusts
- Support all LSA and Netlogon server functions
The RPC server infrastructure component is of crucial importance for both the file server and the active directory server. A few tasks in for the RPC server are prerequisites for higher level features in the file server and the active directory server. See DCERPC for details.
- Merge source3 and source4 server and client implementations (Metze)
- Make RPC server (and client) implementation fully asynchronuous (Metze)
- Merge endpoint mapper implementations
- Implement Association groups
- Multi-trust environments setup to test trusts
- Rewrite and improve the Selftest Suite
- sysvol replication (file system replication)
- FRS / DFSR
- See DCERPC
- use source3/winbindd in AD server
- forest trusts
- FRS / DFSR
- MIT Kerberos support in AD server (IN_PROGRESS, HELP NEEDED, TESTING NEEDED! Talk to Günther and Andreas to help with resources)
- Create preloadable wrappers (DONE)
- Re-test existing MIT KDC glue around the hdb backend (this has been completely rewritten)
A lot of DCE/RPC work needs to be done before we can really finish this task.
- async schannel (NETLOGON) client (Metze)
- merged crypto handling for samlogon cred validation (Günther/Metze)
- merged libnetjoin interfaces (Günther/Metze)
- DCE/RPC client API changes (Günther/Metze)
- tevent based async infrastructure (new services: witness, replication, snapshot, PAR)
- client context (get rid of lp_ usage and globals for client details)
- association group implementation
- DCE/RPC server API merge and cleanup
- See DCERPC
Abstract data model
We might want to implement the abstract data model as outlined in MS-ADPS and other specs. This would allow to abstract the existing interfaces (dsdb/passdb) which both are not the best match for trust handling. Once we have that, and we have the common DCE/RPC infrastructure, we can easily plug implementations for trusts (e.g. from s3) into s4 (and vice-versa).
- We need to find a way to setup multi-trust environments during make test to test more compelx scenarios (e.g. the forst trust test from Sumit Bose).
- We need to test trust calls on MEMBER and DC configurations.
- SMB 2.0 durable file handles* SMB 2.1 Leases
- SMB 2.1 Leases
- SMB 2.1 Multi-Credit
- SMB 3.0 protocol support (including encryption)
- Transparent file compression
- Serverside copy using COPYCHUNK
Clustering - CTDB
- integrate CTDB master into samba master:
- integrate the code under ctdb/ - DONE
- integrate the build into the top level waf build - DONE