Roadmap: Difference between revisions

From SambaWiki
No edit summary
Line 25: Line 25:

* integrate the clustered file server into selftest/autobuild - WIP ([[User:Obnox|Michael]])
* integrate the clustered file server into selftest/autobuild - WIP ([[User:Obnox|Michael]])

=== File Systems ===

* '''FUNDED''' gpfs
* '''FUNDED''' GlusterFS
* CephFS
* ...

=== Performance ===
=== Performance ===

Revision as of 08:51, 21 April 2015


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)

File Systems

  • FUNDED gpfs
  • FUNDED GlusterFS
  • CephFS
  • ...


Performance tuning and optimization is an important reoccurring topic. It is difficult to really track the current issues...

  • performance in clusters, TDB/CTDB
  • Parallel, small I/O (HyperV) workload

Print Server (smbd|spoolssd)

Active Directory Server

DCERPC infrastructure

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

  • async schannel (NETLOGON) client (Metze)
  • merged crypto handling for samlogon cred validation (Günther/Metze)
  • merged libnetjoin interfaces (Günther/Metze)


  • Multi-trust environments setup to test trusts
  • Rewrite and improve the Selftest Suite


File Server

  • SMB 2.0 durable file handles
  • SMB 2.1 Leases
  • SMB 2.1 Multi-Credit
  • SMB 3.0 protocol support (including encryption)

  • Transparent file compression
  • Serverside copy using COPYCHUNK

  • Improved performance on small-CPUs
  • Improved TDB database performance (using robust mutex locking)

Clustering - CTDB

  • integrate CTDB master into samba master:
    • integrate the code under ctdb/
    • integrate the build into the top level waf build

Active Directory Server

  • internal dns server
  • use smbd as file server
  • use winbindd for id-mapping

DCERPC Infrastructure

  • common secure channel implementation