Changes between Version 4 and Version 5 of FeddDatabases


Ignore:
Timestamp:
Nov 5, 2009 7:28:06 PM (15 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FeddDatabases

    v4 v5  
    5050
    5151This is the most complex of the accessDBs.  Its purpose is to configure how an access control component maps a [FeddAbout#GlobalIdentifiers:Three-levelNames three level name] to a local testbed user and project, as well as the rights the project must possess (the node types it can access).  It also includes information about which kinds of nodes are restricted and allows a testbed owner to supply additional attributes used in accessing the testbed.
     52
     53==== Emulab Mappings ====
    5254
    5355The file is a text file.  Each line containing a -> represents a rule for mapping from one or more three-level names to local testbed entities.  The format for a three-level name to project info mapping has the format:
     
    107109indicates that the use of `node_type` is not open to all users.  If a requester asks for access to a restricted node type and is mapped to a project that does not include access to that type, the `fedd` will deny the request.  To specify multiple such types, include multiple such lines.
    108110
    109 For exmaple if `node_type` is restricted and `(fedid:ce90957dd5b7d20f9c3890c4599313b7f1cf31ea,emulab-ops, faber)` makes an access request, that user will succeed if he or she matches:
     111For example if `node_type` is restricted and `(fedid:ce90957dd5b7d20f9c3890c4599313b7f1cf31ea,emulab-ops, faber)` makes an access request, that user will succeed if he or she matches:
    110112
    111113{{{
     
    119121}}}
    120122
     123==== DRAGON Mappings ====
     124
     125A dragon controller maps the [FeddAbout#GlobalIdentifiers:Three-levelNames three level name] to a directory holding the X.509 certificates to use for the allocation.  In OSCARS command-line terms, it maps the requester to the '''repo''' parameter.  This line;
     126
     127{{{
     128(fedid:ce90957dd5b7d20f9c3890c4599313b7f1cf31ea,emulab-ops, faber) -> (/usr/local/OSCARS/local_repo)
     129}}}
     130
     131Maps the given three-level name to the keys stored in /usr/local/OSCARS/local_repo.  That directory should be protected appropriately.
     132
     133=== Attributes ====
     134
    121135A line of the form:
    122136
     
    127141specifies an attribute to be passed back to the requester.  In this case the attribute specifies that nodes used to connect this testbed to another federant should use local Emulab image FBSD7-TVF.  Attribute values start with the first non-whitespace character after '''value:''' and continue until the end of the line.
    128142
    129 Currently `fedd`'s experiment control system understands the following attributes:
     143Currently `fedd`'s experiment system understands the following attributes:
    130144
    131145 '''!ConnectorImage'''::
     
    143157 '''SMBShare'''::
    144158  The name of the machine that the SMB file system is exported from.  Defaults to USERS which is usually correct.  If not, swap in a windows experiment and see where your testbed exports from.
     159 '''dragon'''::
     160  The endpoint designator of this testbed to DRAGON.  This indicates that the testbed is DRAGON-connected.
     161 '''vlans'''::
     162  The acceptable vlan numbers to allocate from DRAGON, if any.  Ranges and comma separated lists (and lists of ranges) are acceptable.
    145163
    146164Generally the '''!StartCmd''' attributes do not need to be modified.