search

Kitware / flow

Full data science workflows on the web
http://resonant-flow.readthedocs.org
Apache License 2.0
20 stars 15 forks source link

Switch to ansible galaxy #207

Closed danlamanna closed 8 years ago

danlamanna commented 8 years ago

This PR removes the complex remnants of GoBig that still remained.

This still needs some testing, particularly on CyVerse.

Note: This removes the requirement of an old ansible version.

curtislisle commented 8 years ago

Should I do anything special besides git pull, check out this branch, and "vagrant up"? ansible-galaxy fails on a development machine with missing dependencies of one of the roles.

danlamanna commented 8 years ago

@curtislisle Could you paste the error output here?

I just ran this and had no issues. It also might help to make sure you're on a recent-ish version of ansible, so something like pip install --upgrade ansible.

curtislisle commented 8 years ago

I’ll update ansible & node and try again. I am sure updated devops software will work. I am out of the office today, so will try again tonight. Thanks!

On Oct 3, 2016, at 11:24 AM, Dan LaManna notifications@github.com wrote:

@curtislisle https://github.com/curtislisle Could you paste the error output here?

I just ran this and had no issues. It also might help to make sure you're on a recent-ish version of ansible, so something like pip install --upgrade ansible.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Kitware/flow/pull/207#issuecomment-251136835, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDZ9hHytt5vyvbDh0D6yKObuFAE0qGKks5qwR4jgaJpZM4J_PG2.

danlamanna commented 8 years ago

To be clear, you don't have to update anything on your machine. Just destroy the vagrant box and re-run vagrant up with this branch checked out.

On Mon, Oct 3, 2016 at 12:36 PM, Curtis Lisle notifications@github.com wrote:

I’ll update ansible & node and try again. I am sure updated devops software will work. I am out of the office today, so will try again tonight. Thanks!

On Oct 3, 2016, at 11:24 AM, Dan LaManna notifications@github.com wrote:

@curtislisle https://github.com/curtislisle Could you paste the error output here?

I just ran this and had no issues. It also might help to make sure you're on a recent-ish version of ansible, so something like pip install --upgrade ansible.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/Kitware/flow/pull/207#issuecomment-251136835>, or mute the thread https://github.com/notifications/unsubscribe-auth/ ACDZ9hHytt5vyvbDh0D6yKObuFAE0qGKks5qwR4jgaJpZM4J_PG2.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Kitware/flow/pull/207#issuecomment-251156363, or mute the thread https://github.com/notifications/unsubscribe-auth/AAlH5fcSil_y9Uo5W6guGVRoywZIdhtDks5qwS7_gaJpZM4J_PG2 .

Dan LaManna Kitware, Inc.

curtislisle commented 8 years ago

Thank you, understood!

On Oct 3, 2016, at 1:00 PM, Dan LaManna notifications@github.com wrote:

To be clear, you don't have to update anything on your machine. Just destroy the vagrant box and re-run vagrant up with this branch checked out.

On Mon, Oct 3, 2016 at 12:36 PM, Curtis Lisle notifications@github.com wrote:

I’ll update ansible & node and try again. I am sure updated devops software will work. I am out of the office today, so will try again tonight. Thanks!

On Oct 3, 2016, at 11:24 AM, Dan LaManna notifications@github.com wrote:

@curtislisle https://github.com/curtislisle Could you paste the error output here?

I just ran this and had no issues. It also might help to make sure you're on a recent-ish version of ansible, so something like pip install --upgrade ansible.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/Kitware/flow/pull/207#issuecomment-251136835>, or mute the thread https://github.com/notifications/unsubscribe-auth/ ACDZ9hHytt5vyvbDh0D6yKObuFAE0qGKks5qwR4jgaJpZM4J_PG2.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Kitware/flow/pull/207#issuecomment-251156363, or mute the thread https://github.com/notifications/unsubscribe-auth/AAlH5fcSil_y9Uo5W6guGVRoywZIdhtDks5qwS7_gaJpZM4J_PG2 .

Dan LaManna Kitware, Inc. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

danlamanna commented 8 years ago

I'm merging this since it works for me and a few mac wielding colleagues, and the existing ansible on master doesn't due to node issues.

I'll be releasing a new Arbor base image shortly (probably won't be officially curated until tomorrow) which uses this. If there are any issues let me know.

curtislisle commented 8 years ago

Thanks, Dan. I'll try it tomorrow.

On Oct 4, 2016, at 4:43 PM, Dan LaManna notifications@github.com wrote:

I'm merging this since it works for me and a few mac wielding colleagues, and the existing ansible on master doesn't due to node issues.

I'll be releasing a new Arbor base image shortly (probably won't be officially curated until tomorrow) which uses this. If there are any issues let me know.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

curtislisle commented 8 years ago

provisioning works on Mac and Linux Mint 18! Thanks!

The Branding default is TangeloHub, but this is OK. I changed it in the girder init.py and repeated provisioning successfully to change to Arbor. Automatic load of analyses (load-analyses.py) works fine. Everything up to adding the easy mode apps works. The devops/easymode-setup.py fails due to wrong port number (9000) then insufficient girder permissions, though. We are almost there! Once I can get the easy mode apps loaded again, I'll test and update them. Please help with the easy mode-setup script. Thanks!

curtislisle commented 8 years ago

I can't run the devops/load-analyses.py script to pre-load collections. The girder_client is not defined in the system python anymore. I looked for /opt/.girderenv but this directory doesn't exist. I tried to use "find" to find any girderenv or girder_env directories in the system unsuccessfully. I then created my own virtualenv and in it tried to run 'pip install girder' in order to get a python with girder defined, but this failed, too. Help! Thanks. This flow is commit #cf970ac (10/14)

danlamanna commented 8 years ago

~/.virtualenvs/girder should have it. If not, pip installing girder-client should fix it (you only need the client to communicate with the running Girder instance).

curtislisle commented 8 years ago

Thanks. this resolved my issue. I had to change the API call in the script from load_or_create_folder to loadOrCreateFolder to keep up with girder API changes, but then this worked. I did have to install girder_client. This issue can be closed now.

On Oct 20, 2016, at 1:05 AM, Dan LaManna notifications@github.com wrote:

~/.virtualenvs/girder should have it. If not, pip installing girder-client should fix it (you only need the client to communicate with the running Girder instance).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Kitware/flow/pull/207#issuecomment-255010082, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDZ9iMMC41ZYbNKh1R1yLsLvraGRJ4Kks5q1vacgaJpZM4J_PG2.