Difference between revisions of "User:Ekacnet"

From SambaWiki
Line 29: Line 29:
 
The idea is to use instead GUID at least in indexes.
 
The idea is to use instead GUID at least in indexes.
   
Currently an indexed search is done like this:
+
Currently an indexed search on attribute samAccountName for the value ''mat'' is done like this:
  +
  +
# search for DN: @INDEX:SAMACCOUNTNAME:MAT
  +
# get the different DNs in the @IDX attributes
  +
# fetch each objects for which the DN was return in step 2
  +
# do the filtering
   
**
 
 
ltdb_index_filter
 
ltdb_index_filter

Revision as of 19:09, 10 June 2011

Hello this is my page ! I'm Matthieu Patou, you can reach me on #samba-technical with the nick ekacnet.

I'm now a Samba team member (yeah !) since May 2010.

I try to keep the fantasy page up to date with what I'll try to do in the short term.


What I've done / For what you can blame me !

  • Upgradeprovsion, a script to update your running provision to adapt to the perpetual changes we do in the Samba Domain controller code (aka Samba4 so far).
  • DFS referral resolution, so that multi DC setup can work correctly with newer client when accessing sysvol and netlogon share
  • Protected storage, a protocol to decrypt selected user secrets with DCs private key, used mainly for certificates
  • Dirsync, an LDAP control used for polling changes
  • Pseudobacklinks, a technical artifact so that all attributes with DN syntax are updated when the targeted DN change its name, allow moving DC between sites

Short term jobs

  • None

Medium term jobs

  • File Replication Service
  • Change indexing

About indexing

For the moment LDB use DN as entries of a index, as DN can be quite long we use a lot of space and memory for this. The idea is to use instead GUID at least in indexes.

Currently an indexed search on attribute samAccountName for the value mat is done like this:

  1. search for DN: @INDEX:SAMACCOUNTNAME:MAT
  2. get the different DNs in the @IDX attributes
  3. fetch each objects for which the DN was return in step 2
  4. do the filtering

ltdb_index_filter