Hello Ken, all, On 03 Mar, 2013, at 10:12, Kenneth Hoste wrote: >> We released on Friday our most popular cluster back in production, >> after a maintenance window, delivering >500 modules in production, >> all thanks to v1.2.0; that was very good job everybody!!! Solid stuff. > > Nice. Did you test the software behind all those modules too? ;-)
Let's play around this toy device: """ Let's soon release the mpi-enabled http://en.wikipedia.org/wiki/ELIZA at milestone v42, which passes the http://en.wikipedia.org/wiki/Turing_test for 1000 or more persons, to eliminate completely this family of questions :-P I am truly sorry: "make test" for ELIZA v42 cannot be non-interactive! """ > * group modules by field, to only show the ones groups of people are > interested in (that's hard, imho) By now, many of us need that urgently; can we come up with something/anything before v1.3? I think the extras we would like to have now are almost this list, some examples seen nearby to defend the need for the category: * cae # OpenFOAM, FLUENT * data # HDF5, bb*, GridFTP... * debugger # GDB, TV, DDT, Marmot... * devel # *devel*, git, cmake, Boost, ant, SWIG, *ASM * ide # Eclipse PTP, snavigator * math # Octave, MATLAB, R * mpi # *MPI* * numlib # goalf-{go}, MKL, *METIS, PETSc, Trilinos, Scotch, ACML * perf # PAPI, Intel TAC/Inspector/Amplifier/Advisor, Scalasca... * phys # ROOT, Geant * system # hwloc, torque-client, openssh-client, gnutls... * tools # EasyBuild, mc, Stow, parallel * vis # VTK, ParaView, Visit, OpenDX, gnuplot hm... not sure if we need a "lang" category for Chapel, Python etc. I can assist with the boring re-categorization; let's remind the existing discussion: https://github.com/hpcugent/easybuild-framework/issues/209 https://github.com/fgeorgatos/easybuild.experimental/wiki/Package-categories Plans there were sorted according to our past "beauty contest", feel free to modify as per your liking, just pick something that makes you comfortable, ASAP. > * set a decent default for all software packages, and only show those by > default with 'module av' This requires hacking existing module avail (or overriding it), no? > * set a default toolchain + version, and only show software built with that > toolchain by default That last idea seems also to be a quite good candidate about how to do it, since it may allow sites to promote/prefer eg. the last ictce toolchain. (ie. make other toolchains available, but with more loading steps). It also looks closer to the Lmod style of organizing modules, which has its own merit. Hackathon pending, we just need to recycle our past todo lists and get to it: https://github.com/fgeorgatos/easybuild.experimental/wiki/Wishlist cheers, Fotis
