Tool data paths of newly installed DMs are in /cvmfs

[natefoo]

Currently, DMs are installed via the Test Installer and then data is built into Corral. When the DM is installed, paths are:

• Tool Data (data table conf and loc files): /cvmfs/test.galaxyproject.org/tool_data/... (CVMFS)
• DM-built data: /galaxy-repl/manageddata/data (Corral)

However, /cvmfs/test.galaxyproject.org/ is not writable when DMs are running, as they are not run in a CVMFS transaction. To fix this, after installing a new DM, the following steps are necessary:

1. In a transaction on test.galaxyproject.org, locate the /cvmfs/test.galaxyproject.org/config/shed_tool_data_table_conf.xml entry corresponding to the newly installed DM (e.g. the one at/near the bottom w/ a repo name in the <file path="..."> attribute matching the DM you just installed)
2. Replace /cvmfs/test.galaxyproject.org in the path with /galaxy-repl/test
3. Copy the DM-created tool data contents to /galaxy-repl with rsync -avP /cvmfs/test.galaxyproject.org/tool_data/toolshed.g2.bx.psu.edu/repos/<owner>/<repo_name>/<changeset_id> /galaxy-repl/test/tool_data/toolshed.g2.bx.psu.edu/repos/<owner>/<repo_name>. You may have to create the parent directories on /galaxy-repl.
4. Adjust the paths in /galaxy-repl/test/tool_data/toolshed.g2.bx.psu.edu/repos/<owner>/<repo_name>/<changeset_id>/tool_data_table_conf.xml to point to /galaxy-repl
5. Publish the transaction and reload Test

The process above is a temporary workaround, a proper fix for this issue should come with #30