Changes between Version 19 and Version 20 of FeddGettingStarted


Ignore:
Timestamp:
Aug 15, 2012 9:31:34 AM (12 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FeddGettingStarted

    v19 v20  
    363363
    364364The standard fedkit also requires access to the global DNS in order to find peer portal nodes.
     365
     366== Connectivity Requirements ==
     367
     368If you are planning to put a federation instance up behind a firewall, here are the communication requirements:
     369
     370 * If you run an experiment controller, it needs to be reachable on the port(s) defined in the {{{services:}}} field of the experiment controller configuration.  It acts as an information exchange point for access controllers to tell one another parameters to interconnect.  Specifically, the experiment controller's service port must be accessible to any users who wish to contact it and any access controllers known to the experiment controller.
     371 * Access controllers need to be accessible on their {{{services:}}} ports as well, from any experiment controller that will make requests and must be able to access any experiment controller that will make requests.
     372 * Portal nodes need to be able to reach other portal nodes.  This may be through a network address translator, but if so the portals can only connect to globally addressible portals.  We are working to relax this.
     373 * Portals use DNS to rendez-vous by default, so it is very helpful if DNS is available to them.  Bare IP addresses can be used in a pinch.