SaltStack configured MyTardis installation

[Grischa]

As some of you may have experienced already, the Chef recipe for MyTardis hasn't received much attention lately.

I am finally ready to release its actively maintained replacement for future versions of MyTardis incl. the current develop branch.

This one is based on SaltStack instead of Chef. Find the code and a quick-start three-liner here:

https://github.com/mytardis/mytardis-salt

Currently, the quick-start script runs fine on Ubuntu 13.10 and 12.04. Please send your error or success reports so we can make it more robust on more platforms.

Any other suggestions and pull requests are most welcome.

Caveats:

  - this relies on a bugfix added to the salt develop branch last week. The develop branch might break something at any moment. Of course, eventually I will base this on a stable release of salt,

  - the quick-start script does not result in a secure production installation of MyTardis. For that you still need to change the configuration (pillar directory) for your specific use case,

  - there is no documentation yet.

Cheers

Grischa

[Stephen Crawley]

On the topic of the Chef recipe for MyTardis, I have created a "Berkshelf-ised" version of the Cookbook and included it in the NeCTAR Cookbooks collection at https://github.com/orgs/nectar-cookbooks.

The cookbook is still "pre-release", but it already includes a number of improvements over the "official" MyTardis version, including:

    - a "production" mode that enables protection against potential damage caused by unexpected South migrations,
    - support for simple backups,
    - support for log watching, and log rotation, and
    - removal of the use of the 'iptables' recipe to mess with the system / virtual's firewall configs.  (This is a "separation of responsibility" issue.  The MyTardis recipe should not preempt this, since it may cause conflicts with other services that the recipe doesn't / can't know about ...)

There are other things on the radar including ClamAV scanning and improvements to the handling of MyTardis settings and plugins.

The Berkshelf-isation means that I / we no longer provide a "chef repo" containing snapshots of all of the dependent cookbooks.  This has many benefits.

If you want a quick-start on using Chef-solo and Berkshelf on NeCTAR virtuals, take a look here:

   https://espaces.edu.au/vwrangler/deployment-tools

Dr Stephen Crawley, eResearch Specialist
Research Computing Centre, University of Queensland
Mobile: 0427 027 304

---

From: tardis...@googlegroups.com [tardis...@googlegroups.com] on behalf of Grischa [gri...@gmail.com]
Sent: 30 January 2014 22:11
To: tardis...@googlegroups.com
Subject: SaltStack configured MyTardis installation

--
You received this message because you are subscribed to the Google Groups "tardis-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tardis-devel...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Steve Androulakis]

Stephen: I will make sure I give your enhanced chef cookbook a run when you're ready.

I just wanted to mention there's a small blog post on http//mytardis.org about the Saltstack setup. Indeed, if anyone wants to put any MyTardis related stuff up there, feel free to contact me for an account. It's getting a fair few hits so far, including from the US, UK, Germany.