Difference between revisions of "Roadmap"

(Active Directory Server)
 
(72 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Introduction ==
+
= 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.
 
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.
  
'''We need resources to achieve that. Manpower for coding, testing and documentation!'''
+
Involvement is highly welcome and can come in various guises: '''Manpower for coding, testing, documentation, ...'''
  
  
Contact the Samba Team and help us!
+
'''Contact the Samba Team go get involved!'''
 +
 
 +
= Features =
  
 
== File Server (smbd) ==
 
== File Server (smbd) ==
  
=== [[Samba3/SMB2|SMB3]] ===
+
=== [[Samba3/SMB2|SMB2/SMB3]] ===
  
* See [[Samba3/SMB2#SMB_3.0]]
+
* '''FUNDED''': Implement multi-channel ([[User:Obnox|Michael]], [[User:Metze|Metze]])
* multi-channel - WIP ([[User:Metze|Metze]], [[User:Obnox|Michael]])
+
* '''FUNDED''': Implement the witness service (Günther, [[User:Metze|Metze]])
* persistent file handles
+
** Prerequisite: A asynchronous RPC server. See [[DCERPC]]
* witness notification protocol - WIP ([[User:Metze|Metze]])
+
* '''FUNDED for Gluster''': Clustering (continuous availability, scale-out) - Planning ([[User:Ira|Ira]], [[User:Obnox|Michael]], ...)
** prerequisite: asynchronous RPC server. See [[DCERPC]]
+
* '''FUNDED for Gluster''': Persistent file handles - Planning ([[User:Ira|Ira]], [[User:Obnox|Michael]], ...) (Do not expect this immediately - Ira)
* RDMA (SMB direct) - Planning ([[User:Metze|Metze]], [[User:Rsharpe|Richard]], [[User:Obnox|Michael]])
+
* RDMA (SMB direct) - Planning ([[User:Metze|Metze]], [[User:Rsharpe|Richard]], [[User:Obnox|Michael]], [[User:Ira|Ira]])
* directory leases
+
* Directory leases
* clustering - Planning/WIP ([[User:Obnox|Michael]])
 
** continuously available shares, scale-out shares
 
  
 
=== Clustering - CTDB ===
 
=== Clustering - CTDB ===
  
* integrate CTDB master into samba master:
+
* 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 ===
 +
 
 +
Support for special features of various file systems, especially cluster file systems, typically through VFS modules.
 +
 
 +
* '''FUNDED''': gpfs
 +
* '''FUNDED''': GlusterFS
 +
* CephFS
 +
* ...
  
 
=== Performance ===
 
=== Performance ===
  
* Performance on small-CPU platforms (like ARM)
+
Performance tuning and optimization is an important reoccurring topic. It is difficult
** reduce CPU usage
+
to really track the current issues...
* Database/TDB-Performance
+
 
 
* performance in clusters, TDB/CTDB
 
* performance in clusters, TDB/CTDB
 
* Parallel, small I/O (HyperV) workload
 
* Parallel, small I/O (HyperV) workload
  
 +
== Print Server (smbd|spoolssd) ==
  
 +
* '''FUNDED''': MS-PAR (Andreas, Günther)
 +
* [[Spoolss|SPOOLSS]]
 +
** Improve Spoolss Server performance
 +
** Improve Spoolss Testsuite
 +
* [[Winreg|Improve Winreg performance]]
  
 +
== Active Directory Server ==
  
== Active Directory Server ==
+
* '''HELP NEEDED:''' S4U2Self, S4U2Proxy, PKINIT ... You can find more details at: [[Roadmap_MIT_KDC]]
 +
* '''FUNDED:''' Two-way forest trusts (Metze)
 +
* '''FUNDED:''' [[Samba4/LDAP Backend|Use the OpenLDAP Database engine and LDAP protocol handlers in AD server]]
 +
* '''FUNDED:''' Correct non-mesh inter-site and intra-site replication via Knowledge Consistency Checker (KCC) (Andrew Bartlett, Garming Sam, Douglas
 +
Bagnall)
 +
 
 +
* [[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
  
* [[DNS]]
+
== [[DCERPC]] infrastructure ==
* [[Samba4/DRS_TODO_List]]
 
* sysvol replication (file system replication)
 
** FRS / DFSR
 
*** See [[DCERPC]]
 
** use source3/winbindd in AD server
 
** subdomains
 
** forest trusts
 
* 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)
 
  
* [[Samba4/LDAP Backend|Use the OpenLDAP Database engine and LDAP protocol handlers in AD server]]
+
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.
  
=== Trust support ===
+
* Merge source3 and source4 server and client implementations (Metze)
 +
* Make RPC server (and client) implementation fully asynchronuous (Metze)
 +
* Merge [[Endpoint_Mapper|endpoint mapper]] implementations
 +
* Implement Association groups
  
A lot of DCE/RPC work needs to be done before we can really finish this task.
 
  
 
* async schannel (NETLOGON) client (Metze)
 
* async schannel (NETLOGON) client (Metze)
 
* merged crypto handling for samlogon cred validation (Günther/Metze)
 
* merged crypto handling for samlogon cred validation (Günther/Metze)
 
* merged libnetjoin interfaces (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).
+
== Testing ==
  
==== Testing ====
+
* Multi-trust environments setup to test trusts
 +
* Rewrite and improve the Selftest Suite
  
* 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.
 
  
==== LSA/Netlogon ====
 
  
* Samba4 lacks support for some LSA and Netlogon calls related to trusts, some of them exist in s3 some are in my master-netlogon branch.
+
= Completed tasks =
  
== RPC Servers==
+
=== File Server ===
* [[Spoolss]]
 
* [[Winreg]]
 
 
 
== DCERPC infrastructure ==
 
  
The RPC server is an infrastructure component that 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.
+
* SMB 2.0 durable file handles
 +
* SMB 2.1 Leases
 +
* SMB 2.1 Multi-Credit
 +
* SMB 3.0 protocol support (including encryption)
  
* See [[DCERPC]] for details
 
* Reconcile source3 source4 server and client implementations ([[User:Metze|Metze]])
 
* Make RPC server (and client) implementation fully asynchronuous ([[User:Metze|Metze]])
 
* [[Endpoint_Mapper]]
 
  
 +
* Transparent file compression
 +
* Serverside copy using COPYCHUNK
  
== Complete ==
 
  
=== File Server ===
+
* Improved performance on small-CPUs
 +
* Improved TDB database performance (using robust mutex locking)
  
* SMB2 Leases
 
  
 
=== Clustering - CTDB ===
 
=== Clustering - CTDB ===
  
 
* integrate CTDB master into samba master:
 
* integrate CTDB master into samba master:
** integrate the code under ctdb/ - DONE
+
** integrate the code under ctdb/
** integrate the build into the top level waf build - DONE
+
** 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
 +
 
 +
=== Testing ===
 +
 
 +
* Implement preloadable wrappers for better testing - [https://cwrap.org The cwrap project]

Latest revision as of 08:16, 6 March 2019

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)

SMB2/SMB3

  • FUNDED: Implement multi-channel (Michael, Metze)
  • FUNDED: Implement the witness service (Günther, Metze)
    • Prerequisite: A asynchronous RPC server. See DCERPC
  • FUNDED for Gluster: Clustering (continuous availability, scale-out) - Planning (Ira, Michael, ...)
  • FUNDED for Gluster: Persistent file handles - Planning (Ira, Michael, ...) (Do not expect this immediately - Ira)
  • RDMA (SMB direct) - Planning (Metze, Richard, Michael, Ira)
  • Directory leases

Clustering - CTDB

  • integrate the clustered file server into selftest/autobuild - WIP (Michael)

File Systems

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

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

Performance

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

Bagnall)

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)


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)


  • 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

Testing