Changes between Version 18 and Version 19 of HPC_deploy

Timestamp:

2015-11-18T18:32:13+01:00 (8 years ago)

Author:

Pieter Neerincx

Comment:

--

HPC_deploy

@@ -13 +13 @@
 The depad group uses [https://hpcugent.github.io/easybuild/ EasyBuild], which uses !EasyConfigs as recipes to enforce consistent, reproducible installations.
 In a nutshell an EasyConfig deployment recipe can handle the following steps:
-* (Bootstrap an installation and satisfy dependencies)
-* Download the (source) code
-* Verify checksums of the downloads
-* Unpack the downloads
-* Configure the build
-* Compile the code
-* Run sanity checks to verify the build was Ok
-* Install the (compiled) code together with it's !EasyBuild log
-* Generate a module file for use with a module system to configure the environment at runtime.
+1. (Bootstrap an installation and satisfy dependencies)
+1. Download the (source) code
+1. Verify checksums of the downloads
+1. Unpack the downloads
+1. Configure the build
+1. Compile the code
+1. Run sanity checks to verify the build was Ok
+1. Install the (compiled) code together with it's !EasyBuild log
+1. Generate a module file for use with a module system to configure the environment at runtime.
 
 The locations where we store source code, deployed apps, their accompanying module files, etc. are documented in the [wiki:HPC_storage#Software Storage SOP].
-For many apps !EasyBuild !EasyConfigs are already available; These files are stored
-* On [https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs]
+!EasyBuild comes with !EasyConfigs for many our apps of interest ''out of the box''; These files are stored
+* On [https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs https://github.com/hpcugent/easybuild-easyconfigs/tree/master/easybuild/easyconfigs] - Latest and greatest from the source.
+* On our machines in a sub sub sub directory of where !EasyBuild was installed - Latest stable release we deployed.
+  The easiest way to find the latter is to load !EasyBuild and search for an app like this:
+{{{
+$> module load EasyBuild
+$> module list
+
+Currently Loaded Modules:
+  1) EasyBuild/2.2.0
+
+$> eb -S GATK
+== temporary log file in case of crash /tmp/eb-JHpvCj/easybuild-tR8MKl.log
+== Searching (case-insensitive) for 'GATK' in /apps/software/EasyBuild/2.2.0/lib/python2.6/site-packages/easybuild_easyconfigs-2.2.0-py2.6.egg/easybuild/easyconfigs 
+CFGS1=/apps/software/EasyBuild/2.2.0/lib/python2.6/site-packages/easybuild_easyconfigs-2.2.0-py2.6.egg/easybuild/easyconfigs/g/GATK
+ * $CFGS1/GATK-1.0.5083.eb
+ * $CFGS1/GATK-2.5-2-Java-1.7.0_10.eb
+ * $CFGS1/GATK-2.6-5-Java-1.7.0_10.eb
+ * $CFGS1/GATK-2.7-4-Java-1.7.0_10.eb
+ * $CFGS1/GATK-2.7-4.eb
+ * $CFGS1/GATK-2.8-1-Java-1.7.0_10.eb
+ * $CFGS1/GATK-3.0-0-Java-1.7.0_10.eb
+ * $CFGS1/GATK-3.3-0-Java-1.7.0_21.eb
+== temporary log file(s) /tmp/eb-JHpvCj/easybuild-tR8MKl.log* have been removed.
+== temporary directory /tmp/eb-JHpvCj has been removed.
+}}}
+* On our machines in {{{/apps/sources/EasyBuild/custom/}}} - Bleeding edge home made !EasyConfigs that were not yet committed to and pull-merged into the !GitHub repos. 
 
 If there is not an easybuild file (.eb) on github and there is no eb file on the cluster (/apps/sources/EasyBuild/custom), we have to create one ourselves.