Difference between revisions of "Roadmap"

From SambaWiki
(Created page with "== Introduction == This page describes the bigger next steps in the development of Samba. It is not named roadmap since it does presently not provide a timeline. The purpose is …")
 
 
(121 intermediate revisions by 12 users not shown)
Line 1: Line 1:
== Introduction ==
+
= Introduction =
   
This page describes the bigger next steps in the development of Samba.
+
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.
It is not named roadmap since it does presently not provide a timeline.
 
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.
== Active Directory Server ==
 
   
  +
Involvement is highly welcome and can come in various guises: manpower for coding, testing, documentation, ...
* sysvol replication (file system replication)
 
  +
* subdomains
 
  +
'''Contact the Samba Team go get involved!'''
* forest trusts
 
  +
  +
= Features =
   
 
== File Server (smbd) ==
 
== File Server (smbd) ==
   
=== SMB2 ===
+
=== Infrastructure ===
  +
  +
* s4u2self (Correct authorization in complex AD topologies on Linux AD member for non-SMB acccess)
  +
* Split out RPC server from smbd to reduce memory footprint ('''FUNDED''')
  +
* ksmbd integration
  +
  +
=== [[Samba3/SMB2|SMB2/SMB3]] ===
  +
  +
* Witness service - Prototype
  +
* Clustering (Continuous availability, Scale-out)
  +
* Persistent file handles - Prototype ([[User:slowfranklin|slow]])
  +
* RDMA (SMB direct) - Prototype ([[User:Metze|Metze]])
  +
* Directory leases - Prototype ([[User:slowfranklin|slow]])
  +
* SMB2 UNIX Extensions
  +
  +
=== Clustering - CTDB ===
  +
  +
* Split up locking.tdb for better scaling of per-file concurrent access
  +
  +
=== File Systems ===
  +
  +
Support for special features of various file systems, especially cluster file systems, typically through VFS modules.
  +
  +
* gpfs ('''FUNDED''')
  +
* GlusterFS ('''FUNDED''')
  +
* CephFS
  +
  +
=== Performance ===
  +
  +
Performance tuning and optimization is an important reoccurring topic. It is difficult
  +
to really track the current issues...
  +
  +
* Use iouring with splice() - Prototype ('''FUNDED''')
  +
* Performance in clusters, TDB/CTDB
  +
* Parallel, small I/O (HyperV) workload
  +
  +
== Print Server (smbd|spoolssd) ==
  +
  +
* 'MS-PAR'
  +
* [[Spoolss|SPOOLSS]]
  +
** Improve Spoolss Server performance
  +
** Improve Spoolss Testsuite
  +
* [[Winreg|Improve Winreg performance]]
  +
  +
== Active Directory Server ==
  +
  +
* S4U2Self, S4U2Proxy, PKINIT ... You can find more details at: [[Roadmap_MIT_KDC]]
  +
* Two-way forest trusts (Metze)
  +
* [[The_Samba_AD_DNS_Back_Ends]]
  +
* [[Samba4/DRS_TODO_List|Directory Replication Service (DRS)]]
  +
* sysvol Replication (FRS/DFSR)
  +
* Read-only Domain Controller (RODC)
  +
* Subdomain support
  +
* One way trusts
  +
* Support all LSA and Netlogon server functions
  +
  +
== [[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 client implementations (Metze)
  +
* Make RPC client implementation fully asynchronuous (Metze)
  +
* Merge [[Endpoint_Mapper|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)
  +
  +
== Testing ==
  +
  +
* Multi-trust environments setup to test trusts
  +
* Rewrite and improve the Selftest Suite
  +
  +
= Completed tasks =
  +
  +
=== File Server ===
  +
  +
* SMB 2.0 durable file handles
  +
* SMB 2.1 Leases
  +
* SMB 2.1 Multi-Credit
  +
* SMB 3.0 protocol support (including encryption)
  +
* Multichannel
  +
* 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
* SMB2 leases
 
  +
* use smbd as file server
  +
* use winbindd for id-mapping
  +
* Correct non-mesh inter-site and intra-site replication via Knowledge Consistency Checker (KCC) (Andrew Bartlett, Garming Sam, Douglas Bagnall)
   
=== SMB3 ===
+
=== DCERPC Infrastructure ===
   
* multi-channel
+
* common secure channel implementation
  +
* Merge source3 and source4 server implementations
* persistent file handles
 
  +
* Make RPC server implementation fully asynchronuous
* witness notification protocol
 
** asynchronous RPC server
 
* RDMA (SMB direct)
 
* directory leases
 
* clustering
 
** continuously available shares, scale-out shares
 
   
== CTDB ==
+
=== Testing ===
   
  +
* Implement preloadable wrappers for better testing - [https://cwrap.org The cwrap project]
* integrate CTDB master into samba master
 

Latest revision as of 13:20, 25 November 2021

Introduction

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!

Features

File Server (smbd)

Infrastructure

  • s4u2self (Correct authorization in complex AD topologies on Linux AD member for non-SMB acccess)
  • Split out RPC server from smbd to reduce memory footprint (FUNDED)
  • ksmbd integration

SMB2/SMB3

  • Witness service - Prototype
  • Clustering (Continuous availability, Scale-out)
  • Persistent file handles - Prototype (slow)
  • RDMA (SMB direct) - Prototype (Metze)
  • Directory leases - Prototype (slow)
  • SMB2 UNIX Extensions

Clustering - CTDB

  • Split up locking.tdb for better scaling of per-file concurrent access

File Systems

Support for special features of various file systems, especially cluster file systems, typically through VFS modules.

  • gpfs (FUNDED)
  • GlusterFS (FUNDED)
  • CephFS

Performance

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

  • Use iouring with splice() - Prototype (FUNDED)
  • 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 client implementations (Metze)
  • Make RPC 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)

Testing

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

Completed tasks

File Server

  • SMB 2.0 durable file handles
  • SMB 2.1 Leases
  • SMB 2.1 Multi-Credit
  • SMB 3.0 protocol support (including encryption)
  • Multichannel
  • 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
  • Correct non-mesh inter-site and intra-site replication via Knowledge Consistency Checker (KCC) (Andrew Bartlett, Garming Sam, Douglas Bagnall)

DCERPC Infrastructure

  • common secure channel implementation
  • Merge source3 and source4 server implementations
  • Make RPC server implementation fully asynchronuous

Testing