The configuration file

Every server and client uses their own configuration file that determines how operations are carried out. Configuration files are structured in a way that lets you share the same ones across servers and clients to simplify agreed upon deployment. This is not always necessary, though. For example, each server owner may customize which privacy policies are applied on their data.

Configuration is written in yaml. In general, there are two top-level blocks: privacy to declare privacy policies used by servers to declare a list of privacy policies sequentially applied on map operation outcomes, and methods to declare map-reduce operations supported by servers and clients. A simple configuration file that is shared between a server and client looks like this:

privacy:
  - policy: fedmed.privacy.Anonymity
    params:
      k: 2
  - policy: fedmed.privacy.CacheLimit
    params:
      limit: 30
  - policy: fedmed.privacy.ComplexityCap
    params:
      cap: 3

methods:
  __mul__: fedmed.ops.binary.mul
  __pow__: fedmed.ops.binary.pow
  __add__: fedmed.ops.binary.add
  sum:
    map: fedmed.ops.private.sum
    reduce: fedmed.ops.public.sum
  len:
    map: fedmed.ops.private.num
    reduce: fedmed.ops.public.sum

Tip

A configuration file with common options to adjust can be found in the library’s examples here .