Closed afgane closed 8 years ago
Amazing stuff! It'll take us a while to review, but that looks awesome!
No rush; @nturaga is working on some docs to help with any setup. Overall, following our discussion in #180, all of this should be quite isolated and quite easily (and by default) omitted from the playbook runs.
👍 I have extensively tested the PR over deployments in various environments, including aws. It's OK. Thanks ! I did not review the cloud setup role. @mvdbeek feel free to merge when ready.
TASK [galaxyprojectdotorg.trackster : Unarchive .len files] ********************
fatal: [localhost]: FAILED! => {"failed": true, "msg": "Could not find imported module support code for unarchive. Looked for either to_text or _text"}
urgh, smells like yet another ansible issue: https://github.com/ansible/ansible/issues/16638
I reran the container build locally and it completed fine. Did you just restart the tests? I was going to suggest to give it another try...
Did you just restart the tests? I was going to suggest to give it another try...
Yup. I was thinking this should have failed with the previous builds as well, if it really was the issue I linked.
Finally looks like this built properly!
Thanks everyone, this is fantastic!
Included is a fairly general role for setting up Galaxy severs primarily on cloud infrastructures, meant as a 'cloud' flavor and discussed in #180. The flavor has been tested on Jetstream and GCE clouds. One particularly neat feature is that it hooks into Galaxy project's reference data file system that is hosted over CVMFS, allowing the Galaxy server to have access to all those reference genomes without those needing to be explicitly setup.