= Status =
== Latest additions ==
 * automatic pseudo-striping if
  * file consists of no more than one object
  * network has high latency, i.e. an effective RTT of > 10ms
== Test cell in Hamburg ==
 * Hartmut has built enhanced ''openafs-osd-bpc'' on ''dirac'' machines
  * some of the most recent changes are not yet in the svn trunk
  * latest code is in ''/afs/osdtest/openafs'' (also take note of ''perftest'' there)
 * as of last week, the dcache interface machine was not yet available
 * dcache support requires some special handling of linktables (?)

= Policies =
== Database backend ==
 * creation of sensible data structures in ''osddb.xg''
 * saving in the same manner as all data in the OSDDB
  * typed entries are already supported, so this will require very little work

== Code structure ==
 * from fileserver perspective, there are at least two places from where policy evaluation might make sense
  * in '''SAFSS_Create``File''', almost all relevant information is known already, however
  * size estimations can be made no sooner than in '''common_Store``Data64'''
  * the latter has a disadvantage, as e.g. the filename needs to be looked up again
 * all functions that make direct use of the policy data structures should live in the ''osddb'' subtree, specifically in ''osddbuser.c''
 * functions that add behaviour to the fileserver should live in ''vol_osd.c''