We can probably make use of the approach used in the Ansible-galaxy-tools role.

Regards.

Steve McMahon
Solution Architect and Senior System Administrator | Scientific Computing
Information Management and Technology
CSIRO

T +61 2 6214 2968 Alt +61 4 0077 9318
steve.mcmahon@csiro.au | www.csiro.au
1 Wilf Crane Crescent, Yarralumla ACT 2600

PLEASE NOTE
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.

Please consider the environment before printing this email.

From: Martin Čech [mailto:marten@bx.psu.edu]
Sent: Monday, 25 January 2016 12:38 PM
To: McMahon, Steve (IM&T, Yarralumla) <Steve.Mcmahon@csiro.au>; galaxy-dev@lists.galaxyproject.org
Cc: Hlinka, Ondrej (IM&T, St. Lucia) <Ondrej.Hlinka@csiro.au>; Ludbey, Joel (IM&T, Clayton) <Joel.Ludbey@csiro.au>
Subject: Re: [galaxy-dev] configuration management, tool shed and tool revisions

Hello Steve,

Galaxy project's efforts in automating tool installations are mostly represented by the following Ansible playbook (https://github.com/afgane/galaxy-tools-playbook) and a role (https://github.com/galaxyproject/ansible-galaxy-tools).

We plan on improving that tracked at: https://github.com/galaxyproject/galaxy/issues/1115

The install_tool_shed_repositories.py script should install the latest revision when no revision is specified (and owner and repo name is present). This feature was added on May 14, 2014 (https://github.com/galaxyproject/galaxy/commit/2d5c37a73f90931e03291d5c4ad6057a0e41a712).

Please let us know how it works for you.

Thank you for using Galaxy.

Martin Cech

On Sun, Jan 24, 2016 at 7:02 PM <Steve.Mcmahon@csiro.au> wrote:

Hi,

We are using Puppet to manage the configuration for VMs for our development and production Galaxy instances. We would like to be able to specify tool shed tools and their revisions and have Puppet ensure that they are installed. Our Puppet code makes use of the “install_tool_shed_repositories.py” script and a script based on that which checks to see whether a particular tool and revision is installed.

We are finding that if we don’t specify the latest revision of a tool that the “install_tool_shed_repositories.py” script fails. Is this what others experience?

I know other sites are doing configuration management with Ansible. What approach are these sites taking for ensuring tools are installed or are these sites doing the tool installations outside of configuration management?

Regards.

Steve McMahon
Solution Architect and Senior System Administrator | Scientific Computing
Information Management and Technology
CSIRO

T +61 2 6214 2968 Alt +61 4 0077 9318
steve.mcmahon@csiro.au | www.csiro.au
1 Wilf Crane Crescent, Yarralumla ACT 2600

PLEASE NOTE
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.

Please consider the environment before printing this email.

___________________________________________________________
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/