[openhpc-users] Need advice on how to work with developers to contribute to OpenHPC

David Brayford

I apologies for cross posting, but the post below is relevant to the current TSC discussions.

Would it be worth considering having a second repository of components that haven't been accepted (not rejected due for being unsuitable), define it as a development, alpha, beta version. That could be used as a staging post to the official OpenHPC (release) repository and allow the application to be evaluated before it is included in the official version.

This could be a method for allowing research/new software to be disseminated to the larger HPC community.


-------- Forwarded Message --------
Subject: [openhpc-users] Need advice on how to work with developers to contribute to OpenHPC
Date: Tue, 16 Aug 2016 23:33:53 +0000
From: Rashawn L. Knapp <rashawn.l.knapp@...>
Reply-To: OpenHPC-users@groups.io
To: OpenHPC-users@groups.io



This is primarily a long question for the maintainers of OpenHPC.


I have quite a few questions regarding how open-source HPC performance tool developers contribute to OpenHPC.  As background, I attended, in WW32, the Scalable Tools 2016 workshop, a workshop attended by largely open-source performance tool developers and  with focus  on scaling for today’s petaflop systems and preparing for the exa-scale successor generation.  I inquired with the tool developers about willingness to contribute to OpenHPC by mirroring their current repositories to ohpc/components/perf-tools. Most of the developers raised concerns about doing this. I have one developer from Barcelona Super Computing Center who will add one of their performance tools,  but I am not sure how to get the developer started.  I list out the concerns and questions below:



        Basic concerns are with optional components  and the RPM structure, for example Dyninst and PAPI are often optional components that one can integrate into a tool - how are optional components handled? TAU is a very good example of this which has many build optional configuration build settings.

        How are package dependencies handled? For example, packaging up for both OS types: CentOS 7.2 and SLES12

        Are source RPMs possible? I ask because most of these developers release source code and not RPMs

        How are specific recipes included in the package?

        The case here comes from one of the national laboratories who wants to ensure tools are installed and used as specified

        What are the guidelines and BKMs for developers to begin contributing?

        How are updates to OpenHPC validated?

        Do developers push their updates or is there another mechanism?


I will greatly appreciate all advice and pointers on this topic.




Rashawn Knapp