Address user issues with XRootD standalone documentation

Description

I sat down with Pascal and watched him make his way through the XRootD standalone installation document. Here are some issues that we found as a result of the exercise:

Install document changes

  • He copied the set rootdir = /data directly into the config file. Let's change the code block from an example to a generic with <REPLACE ME> style text

  • The resourcename example doesn't look like a Topology resource name. Also dCache? That doesn't make much sense

  • We should add a registration section like this one https://opensciencegrid.org/docs/data/frontier-squid/#registering-frontier-squid

  • AuthZ configuration doc needs to reference the LCMAPS VOMS doc, i.e. the voms and grid mapfiles result in the users specified in the XRootD authfile

  • Validation section should note that if they set up authZ, they'll need to add themselves to the authfile/gridmap appropriately and have a proxy

  • Seems like we should just do HTTP validation with curl or wget instead of gfal2 (if that's possible with authZ)

Document in both the install doc and the config files

  • He wasn't clear about the relative directory export and he asked why he would want to limit directories within /data. An example would be helpful here

  • We should state that if you don't want to limit what XRootD shares in rootdir, do nothing

Freshdesk Tickets

None

Assignee

Brian Lin

Reporter

Brian Lin

Priority

Critical

Labels

None

Components

Fix versions

None

Epic Link

None

Sprint

Configure