Changes between Version 12 and Version 13 of FeddGettingStarted


Ignore:
Timestamp:
Apr 9, 2012 3:10:15 PM (13 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FeddGettingStarted

    v12 v13  
    341341The output indicates that the experiment is swapping in.  You can get more information using the [FeddCommands#fedd_spewlog.py fedd_spewlog.py] command or [FeddCommands#fedd_multistatus.py fedd_multistatus.py] as well as watching the fedd log files and DETER web interface.  The [FeddCommands#fedd_terminate.py fedd_terminate.py] command will delete the experiment.  There are [FeddCommands#CommandLine many command line tools to try].
    342342
     343== Adding federation credentials to the experiment controller ==
     344
     345While each federation agreement is different, the procedure is generally to negotiate some access with DETER and then receive a credential from the DETER experiment controller that delegates some rights to the federated system.  This will be one or more X.509 attribute certificates that need to be installed in the policy of your local experiment controller.  (Actually, you could also put them into each user's ABAC credentials directory, but the experiment controller is easier.)
     346
     347To do this, use the [wiki:FeddABAC#import_abac_creds.py import_abac_creds.py] program to add these credentials to your policy.  If the experiment controller's ABAC is kept in {{{/usr/local/etc/fedd/abac}}} the command will be something like:
     348
     349{{{
     350$ import_abac_creds.py --dir /usr/local/etc/fedd/abac cred1.pem cred2.der cred3.pem cred4.der
     351}}}
     352