| | 1 | = Federating With DETER = |
| | 2 | |
| | 3 | This discusses how to connect a [http://deterproject.org DETER] or [http://www.emulab.net Emulab]-based testbed to [https://www.isi.deterlab.net DETERLab] using [WikiStart fedd], [http://abac.deterlab.net ABAC] and their tools. |
| | 4 | |
| | 5 | == Introduction == |
| | 6 | |
| | 7 | This page takes a user through the process of adding federation components to an existing DETER and assigning user credentials that will allow users to access that DETER through the fedd interfaces, and then to use those same interfaces to access federated resources. We will also talk about how to allow federated users to use the local resources. |
| | 8 | |
| | 9 | This document will discuss the relevant fedd components, what they do, and what they need in order to do those jobs. We also discuss the tools an experimenter uses to create and monitor federated experiments. Then we briefly discuss how to get the ABAC credentials necessary to access the federated environment. |
| | 10 | |
| | 11 | === Federation Components === |
| | 12 | |
| | 13 | Fedd really is two entities, an '''Access Controler''' that mediates access to federated resources and provides standard interfaces for allocating them, and an '''Experiment Controller''' that acts as a credential store and coordinates requests across multiple access controllers. The [FeddAbout discussion of the DeterFederation Architecture] has more to say about these entities, but this is enough to get started. |
| | 14 | |
