= Configuration Examples =

This page gives several `fedd` layouts and the configuration files that support them.  You can take them either as starting points from which to create your own configuration or as demonstrations of how the parameters in the [FeddConfig configuration files] and [FeddDatabases databases] work together.

== Static Access Only on Users ==

This is the simplest configuration of `fedd`, used to allow users of other testbeds to use resources from yours using pre-configured projects.  The layout assumes that for each [FeddAbout#GlobalIdentifiers:Three-levelName] three-level name] you are willing to allow to use your testbed, you have set up a project that already has proper keys installed.  Because no local projects or local users need to be modified, `fedd` does not need access to boss.

A commented fedd.conf (installed in `/usr/local/etc/fedd.conf`) on `users.isi.deterlab.net` might look like this:

{{{
[access]
# Keep access state (which experiments are live) in this file
# Be sure it is writeable by the fedd user
access_state: /var/db/fedd/deter_access.state

# Parameters for remote fedds to instantiate experiments
boss: boss
ops: users
domain: .isi.deterlab.net
fileserver: fs
eventserver: event-server

# This machine's URI to discriminate proxy requests
testbed: https://users.isi.deterlab.net:23235

# The database that maps requester to local acces projects
accessdb: /usr/local/etc/fedd/deter_access

[allocate]
allocation_level: none
allocate_state: /var/db/fedd/deter_allocate.state

[globals]
cert_file: /usr/local/etc/fedd/fedd.pem
services: 23235

}}}