Roadmap: Difference between revisions

From SambaWiki
(change how we express the OpenLDAP backend)
(reference DCERPC and Samba3/SMB2 pages)
Line 4: Line 4:
It is not named roadmap since it does presently not provide a timeline.
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.
The purpose is to point out the broader direction into which Samba is heading.

== DCERPC infrastructure ==

* See [[DCERPC]]


== Active Directory Server ==
== Active Directory Server ==
Line 9: Line 13:
* sysvol replication (file system replication)
* sysvol replication (file system replication)
** FRS / DFSR
** FRS / DFSR
*** See [[DCERPC]]
** use source3/winbindd in AD server
** use source3/winbindd in AD server
** subdomains
** subdomains
Line 29: Line 34:
** association group implementation
** association group implementation
* DCE/RPC server API merge and cleanup
* DCE/RPC server API merge and cleanup
* See [[DCERPC]]

Some of the existing work can be found already here:

https://gitweb.samba.org/?p=metze/samba/wip.git;a=shortlog;h=refs/heads/master4-dcerpc
https://gitweb.samba.org/?p=metze/samba/wip.git;a=shortlog;h=refs/heads/master4-schannel


==== Abstract data model ====
==== Abstract data model ====
Line 53: Line 54:


* SMB2 leases
* SMB2 leases
** See [[Samba3/SMB2#SMB_2.1]]


=== SMB3 ===
=== SMB3 ===


* See [[Samba3/SMB2#SMB_3.0]]
* multi-channel
* multi-channel
* persistent file handles
* persistent file handles
* witness notification protocol
* witness notification protocol
** asynchronous RPC server
** asynchronous RPC server. See [[DCERPC]]
* RDMA (SMB direct)
* RDMA (SMB direct)
* directory leases
* directory leases

Revision as of 11:09, 20 September 2013

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 to point out the broader direction into which Samba is heading.

DCERPC infrastructure

Active Directory Server

Trust support

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).

Testing

  • 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.

File Server (smbd)

SMB2

SMB3

  • See Samba3/SMB2#SMB_3.0
  • multi-channel
  • persistent file handles
  • witness notification protocol
    • asynchronous RPC server. See DCERPC
  • RDMA (SMB direct)
  • directory leases
  • clustering
    • continuously available shares, scale-out shares

CTDB

  • integrate CTDB master into samba master