svn commit: samba-web r966 - in trunk/projects: .

[ab at samba.org]

Author: ab
Date: 2006-04-28 13:07:31 +0000 (Fri, 28 Apr 2006)
New Revision: 966

WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba-web&rev=966

Log:
Add workload generator idea for SoC2006
Modified:
   trunk/projects/summercode06.html


Changeset:
Modified: trunk/projects/summercode06.html
===================================================================
--- trunk/projects/summercode06.html	2006-04-24 10:59:52 UTC (rev 965)
+++ trunk/projects/summercode06.html	2006-04-28 13:07:31 UTC (rev 966)
@@ -17,7 +17,7 @@
 
   <h2>Project Ideas</h2>
 
-  <h4>SACL VFS Module (Samba 3)</h2>
+  <h4>SACL VFS Module (Samba 3)</h4>
   <p>Support for file systems SACLs (i.e. file system auditing) 
      on in Samba in a VFS module by utilizing Extended Attributes.  This 
      project should ensure that users are able to successfully view and 
@@ -25,7 +25,7 @@
      Explorer.  
   </p>
 
-  <h4>Consolidate internal LDAP SASL support (Samba 3)</h2>
+  <h4>Consolidate internal LDAP SASL support (Samba 3)</h4>
   <p>Samba has two separate copies of LDAP support routines.  One is
      used to access Active Directories servers when operating as 
      a member server and the other is used for implementing the 
@@ -33,13 +33,13 @@
      with LDAP directories services and SASL mechanisms such as GSS-SPNEGO.
   </p>
 
-  <h4>Backport EndPointMapper and support for ncacn_ip_tcp (Samba 3)</h2>
+  <h4>Backport EndPointMapper and support for ncacn_ip_tcp (Samba 3)</h4>
   <p>Current Samba 3.0 releases only support MS-RPC over SMB named pipes.
      The SAMBA_4_0 code base has support RPC directory over TCP which could
      be back ported in some degree to the SAMBA_3_0 tree.
   </p>
 
-  <h4>Alternative configuration backends (Samba 3)</h2>
+  <h4>Alternative configuration backends (Samba 3)</h4>
   <p>The current smb.conf does not allow the flexible set read and modify 
      individual key/value pairs from within smbd.  This project would explore
      using a registry like backend that would allow more flexibility 
@@ -50,25 +50,25 @@
      along with a simple command line interpreter/editor.
   </p>
 
-  <h4>Performance optimizations on NetBSD (Samba 3)</h2>
+  <h4>Performance optimizations on NetBSD (Samba 3)</h4>
   <p>This work is under the umbrella of the NetBSD project and is listed here
      for publicity and to help inform interested applicants.  Please refer 
      to <a href="http://www.netbsd.org/contrib/projects.html#smbtuneup">the 
      NetBSD project site</a> for a complete description.
   </p>
 
-  <h4>Full SAM implementation (Samba 3)</h2>
+  <h4>Full SAM implementation (Samba 3)</h4>
   <p>Provide a new database passdb backend that provides both the Unix 
      and Win32 attributes without the use of external commands such 
      as the &quot;add user script&quot;.
   </p>
 
-  <h4>SNMP support (Samba 3)</h2>
+  <h4>SNMP support (Samba 3)</h4>
   <p>Explore supporting the LANMAN SNMP MIB included with Windows 
      server operating systems in smbd, nmbd, and winbindd.
   </p>
 
-  <h4>Solve the overabundance of configuration parameters (Samba 3)</h2>
+  <h4>Solve the overabundance of configuration parameters (Samba 3)</h4>
   <p>Samba 3.0 includes many config options which are necessary only 
      in extreme circumstances.  Only a small percentage of the parameters
      are required in most installations.  The challenge is to remove
@@ -76,14 +76,14 @@
      providing access to them when absolutely necessary.
   </p>
 
-  <h4>Implement a Berkeley DB backend for LDB</h2>
+  <h4>Implement a Berkeley DB backend for LDB</h4>
   <p><a href="http://ldb.samba.org/">LDB</a> currently supports
      both TDB and LDAP backend storage mechanisms.  Another alternative
      backend possibility is the <a href="http://www.sleepcat.com">Berkeley DB 
      database</a>. 
   </p>
 
-  <h4>Develop an Administrative Logging System (Samba 3)</h2>
+  <h4>Develop an Administrative Logging System (Samba 3)</h4>
   <p>The log files in Samba are commonly of more use to developers
      than to administrators.  A new logging system (in parallel with the
      existing debug logs) similar to the Windows auditing facilities 
@@ -92,19 +92,19 @@
      configuration changes, etc...
   </p>
 
-  <h4>Implement missing functionality in DsGetNCChanges (Samba 4)</h2>
+  <h4>Implement missing functionality in DsGetNCChanges (Samba 4)</h4>
   <p>The primary goal is to review and implement the compression 
      algorithm used in directory services replication.
   </p>
 
-  <h4>Implement missing SWAT features (Samba 4)</h2>
+  <h4>Implement missing SWAT features (Samba 4)</h4>
   <p>SWAT research in the SAMBA_4_0 branch is very different from 
      the model of SWAT in the Samba 3 releases.  There are many 
      possibilities for new management features that have yet to be 
      explored.
   </p>
 
-  <h4>Componentization of Samba (Samba 3 &amp; 4)</h2>
+  <h4>Componentization of Samba (Samba 3 &amp; 4)</h4>
   <p>Samba has many APIs and subsystems, such as talloc, ldb &amp; tdb, etc...,  
      that would be of use to the Open Source community at large.  Much work 
      is needed to break these individual projects out of the current
@@ -112,5 +112,28 @@
      if which Samba is but one consumer.
   </p>
 
+  <h4>Dbench and Nbench workload generator based on Samba 4</h4>
+  <p>Samba 4 has two NTVFS backends (cifs and nbench) which allow to
+     create a CIFS proxy which:
+     <ol>
+      <li>intercepts CIFS traffic and forwards that to a remote server, and</li>
+      <li>write down a workload scenario file for Nbench and Dbench tools</li>
+     </ol>
+   </p>
+   <p>For every connection there is one log file is written. These logs can later
+      be replayed by nbench/dbench against any file system/server to reproduce the
+      same workload. Implementation of the following things will allow to create
+      a specialized workload generator to test various usage scenarious based on
+      real world applications:
+      <ol>
+       <li>Add a functionality to post-process generated logs to create a combined
+           dbench/nbench scenario representing multiple-client access pattern.</li>
+       <li>Add CIFS Posix Extensions support to both Nbench NTVFS backend and dbench/nbench
+           tools so that Linux applications running against Linux CIFS file system
+	   could be profiled.</li>
+       <li>Package resulting solution as simply-installable and configurable application
+           similar to <a href="http://www.enterprisesamba.org/">Samba4WINS package</a></li>
+      </ol>
+   </p>
 
 <!--#include virtual="/samba/footer.html" -->