| | 8 | |
| | 9 | == Fedd Roles: Experiment Control and Access Control == |
| | 10 | |
| | 11 | Fedd can act in two ways: |
| | 12 | |
| | 13 | '''Experiment controller''':: |
| | 14 | The central coordinator for creating and managing a federated experiment |
| | 15 | '''Access Controller''': |
| | 16 | Responsible for negotiating access to local testbed resources. It both maps the user into the local access control and manipulates local resources. |
| | 17 | |
| | 18 | Which role a fedd will act in depends on the configuration of the fedd. A single testbed is likely to run both an access controller to make its resources availabel to others and an experiment controller to create experiments for its local users. However, there is no requirement that experiment controllers run on testbed infrastructure. A trusted experiment controller may run on a desktop or elsewhere, as long as there are access controllers are willing to grant resources to [FeddAbout#GlobalIdentifiers:Three-levelNames three-level names] that are anchored to its [FeddAbout#GlobalIdentifiers:Fedids fedid]. |
