Well we used ansible-galaxy-extras for provisioning a VM server so - I guess that's just right. I'll have to look into how to script updates - we're trying to move away from "precious" servers to entirely scripted ones. Hopefully put together some PRs to harmonise things.
This stuff would make a good topic for Galaxy-Admins in the future. Peter On 20 January 2016 at 16:17, John Chilton <jmchil...@gmail.com> wrote: > Peter - thanks for sharing this. > > ansible-galaxy-extras and ansible-galaxy were just created by > different people at different times and I don't think a lot of thought > went into rationalizing variable names across projects. Indeed even > within ansible-galaxy-extras the variable names aren't very > consistent. I have opened a PR to switch ansible-galaxy-extras over to > using galaxy_server_dir - because ansible-galaxy is clearly the more > reasonable thought out role and has been published to the ... > unfortunately named... Anisble Galaxy (https://galaxy.ansible.com/). > > https://github.com/galaxyproject/ansible-galaxy-extras/pull/48 > > Some other people have brought up this problem as well, I'm happy to > make changes needed to ansible-galaxy-extras to bring it in line with > the rest of Galaxy ansible ecosystem. As everyone encounters these > problems, I'd just encourage opening PRs to adjust them or seeking > advice on the issue tracker of any of the projects or here. It would > be really nice to have a coherent set of ansible modules. > > There is some more discussion on this topic on the following Github issue: > > https://github.com/bgruening/docker-galaxy-stable/issues/135 > > Finally, just a note of warning about ansible-galaxy-extras - it was > explicitly created with the intention of one-time provisioning of VMs > and Docker images - I didn't put a lot of thought into long running > production servers. I don't know of any problems you will encounter - > but I did want to give you the buyer beware warning. Since ansible > doesn't provide any ability to write tests, I'm pretty sure I'd > universally encourage people not to use it as a long running > configuration management technology - but obviously I don't speak for > the project on that topic since it is used extensively to power Galaxy > infrastructure. > > Hope this helps and thanks a ton for the contributions, they look awesome! > > -John > > On Wed, Jan 20, 2016 at 12:37 PM, Peter van Heusden <p...@sanbi.ac.za> > wrote: > > Hi there > > > > We've just finished provisioning a new Galaxy server here using the > > ansible-galaxy and ansible-galaxy-extras roles, with some extra roles > from > > Nate and our own creation. In the ansible-galaxy role Galaxy's install > > location is set using the galaxy_server_dir variable, but in > > ansible-galaxy-extras the variables galaxy_home_dir and galaxy_root > > (presumably for distinct locations for the galaxy user's home directory > and > > the root of the Galaxy installation) are used. > > > > Is this difference deliberate? Attached is our Ansible playbook - we just > > configured the variables to all point to the same location (and set the > > galaxy_venv_dir to be .venv not venv). I thought the two roles were > meant to > > work together, so this difference is somewhat confusing. > > > > Thanks, > > Peter > > > > ___________________________________________________________ > > Please keep all replies on the list by using "reply all" > > in your mail client. To manage your subscriptions to this > > and other Galaxy lists, please use the interface at: > > https://lists.galaxyproject.org/ > > > > To search Galaxy mailing lists use the unified search at: > > http://galaxyproject.org/search/mailinglists/ >
___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: https://lists.galaxyproject.org/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
