Changes between Version 22 and Version 23 of bestPractices

Show
Ignore:
Timestamp:
06/30/10 14:52:23 (9 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • bestPractices

    v22 v23  
    7272}}} 
    7373'''CAVEAT:''' this method obviously accumulates certificates of all actors across containers. This is '''OK''' for some definition of OK. The important thing is that the container has a version of the keystore that contains the certificates for actors in that container. Any extra certificates will not harm but present a potential security loophole. A more involved method would create separate runtime/ directories for each container. 
    74 === Deploying actors === 
    7574 
    76   1. Create the [https://geni-orca.renci.org/orca-doc/current/guides/container-configuration/xml.html actor configuration] for the container by editing $HOME/hostX/actor_configs/config.xml for each host. At the bottom of this page is a working example of a configuration file. 
     75=== Deploying  === 
     76 
     77  1. Create the [https://geni-orca.renci.org/orca-doc/current/guides/container-configuration/xml.html actor configuration] for the container by editing $HOME/hostX/actor_configs/config.xml for each host. You will need the GUIDs you have issued to the actors. At the bottom of this page is a working example of a configuration file. 
    7778  1. To lookup certificates for actors in other containers (if they are already running), consult ORCA [http://geni.renci.org/actors.php actor registry]. You can extract them from your own keystores as described [https://geni-orca.renci.org/orca-doc/current/guides/getting-started/index.html#How_to_generate_an_actor_certificate here] 
    7879  1. Edit the $HOME/hostX/ant/build.properties to point to the URL of the container on hostX