Fed4Fire with Omni

From Grid5000
Revision as of 14:34, 13 November 2019 by Lbertot (talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Although omni is explicitly stated as a compatible tool for working with Fed4Fire, finding documentation on how to do so can be complicated.

This page presents a working configuration file for using Fed4fire with omni completed with any useful considerations.

Omni configuration

default_cf = fedblock
users = userblock


urn = urn:publicid:IDN+wall.ilabt.iminds.be+user+<username>
keys = ~/.ssh/id_rsa.pub


Fields details

  • [omni]
    • Fields within this block represents your default settings, they mostly point to other blocks in the configuration file.
  • [fedblock]
    • type
    Must be chapi (not sfa) to communicate with the member and slice authority set up by Fed4Fire.
    (thanks to Brecht Vermeulen for this indication)
    • cert
    Path to the certificate provided by the Fed4Fire user authority, usually the same as the key.
    • key
    Path to the key provided by the Fed4Fire user authority, usually the same as the cert cert.
    • ch (Clearing House)
    Made useless by providing ma and sa but still mandatory, must at least contain a valid protocol.
    • ma (Member authority)
    Address of Fed4Fire Member Authority API.
    (as seen in jFed-probe)
    • sa (Slice authority)
    Address of Fed4Fire Slice Authority API.
    (as seen in jFed-probe)
  • [userblock]
    • urn
    URN attributed by federation authority, can be found in the certificate under Subject Alternative Name.
    Usually "urn:publicid:IDN+wall.ilabt.iminds.be+user+<username>".
    • keys
    Path to ssh keys
  • [aggregate_nicknames]
    • List of aliases for Aggregate Managers (AM) written as :
the URN is optional, do not forget the coma