Re: [easybuild] Module File for Intel clck

2017-02-20 Thread Kenneth Hoste



On 20/02/2017 14:53, Siddiqui, Shahzeb wrote:

Do you want me to update the PR with the name IntelClusterChecker.


I think that makes sense, yes.


PATH variable needs to be set to use CLCK.


OK, but let's follow this up in your pull request 
https://github.com/hpcugent/easybuild-easyconfigs/pull/4156/ ?



regards,

Kenneth



-Original Message-
From: easybuild-requ...@lists.ugent.be 
[mailto:easybuild-requ...@lists.ugent.be] On Behalf Of Kenneth Hoste
Sent: Monday, February 20, 2017 5:05 AM
To: easybuild@lists.ugent.be
Subject: Re: [easybuild] Module File for Intel clck



On 20/02/2017 03:11, Fotis Georgatos wrote:

On Feb 17, 2017, at 7:53 PM, Kenneth Hoste  wrote:

It's unclear to me what you consider to be wrong in this module file exactly?
Is something missing, or are some environment variables set incorrectly?

I believe you would expect some *PATH* variables to be defined there, no?!

See also
https://github.com/hpcugent/easybuild-easyconfigs/pull/4156/files, where $PATH 
& co are being specified (although perhaps incorrectly?).

Since we’re still on this topic: clck is not a spectacular name in
terms of user friendliness; perhaps adding and intel- or even i prefix may make 
it more palatable to first time cluster testers...

+1, maybe should be IntelClusterChecker?


K.




RE: [easybuild] Module File for Intel clck

2017-02-20 Thread Siddiqui, Shahzeb
Do you want me to update the PR with the name IntelClusterChecker. 

PATH variable needs to be set to use CLCK.


-Original Message-
From: easybuild-requ...@lists.ugent.be 
[mailto:easybuild-requ...@lists.ugent.be] On Behalf Of Kenneth Hoste
Sent: Monday, February 20, 2017 5:05 AM
To: easybuild@lists.ugent.be
Subject: Re: [easybuild] Module File for Intel clck



On 20/02/2017 03:11, Fotis Georgatos wrote:
> On Feb 17, 2017, at 7:53 PM, Kenneth Hoste  wrote:
>> It's unclear to me what you consider to be wrong in this module file exactly?
>> Is something missing, or are some environment variables set incorrectly?
> I believe you would expect some *PATH* variables to be defined there, no?!

See also
https://github.com/hpcugent/easybuild-easyconfigs/pull/4156/files, where $PATH 
& co are being specified (although perhaps incorrectly?).
>
> Since we’re still on this topic: clck is not a spectacular name in 
> terms of user friendliness; perhaps adding and intel- or even i prefix may 
> make it more palatable to first time cluster testers...

+1, maybe should be IntelClusterChecker?


K.


Re: [easybuild] Module File for Intel clck

2017-02-20 Thread Kenneth Hoste



On 20/02/2017 03:11, Fotis Georgatos wrote:

On Feb 17, 2017, at 7:53 PM, Kenneth Hoste  wrote:

It's unclear to me what you consider to be wrong in this module file exactly?
Is something missing, or are some environment variables set incorrectly?

I believe you would expect some *PATH* variables to be defined there, no?!


See also 
https://github.com/hpcugent/easybuild-easyconfigs/pull/4156/files, where 
$PATH & co are being specified (although perhaps incorrectly?).


Since we’re still on this topic: clck is not a spectacular name in terms of 
user friendliness;
perhaps adding and intel- or even i prefix may make it more palatable to first 
time cluster testers...


+1, maybe should be IntelClusterChecker?


K.


Re: [easybuild] Module File for Intel clck

2017-02-19 Thread Fotis Georgatos

On Feb 17, 2017, at 7:53 PM, Kenneth Hoste  wrote:
> It's unclear to me what you consider to be wrong in this module file exactly?
> Is something missing, or are some environment variables set incorrectly?

I believe you would expect some *PATH* variables to be defined there, no?!

Since we’re still on this topic: clck is not a spectacular name in terms of 
user friendliness;
perhaps adding and intel- or even i prefix may make it more palatable to first 
time cluster testers...

Fotis


-- 
echo "sysadmin know better bash than english" | sed s/min/mins/ \
  | sed 's/better bash/bash better/' # signal detected in a CERN forum









Re: [easybuild] Module File for Intel clck

2017-02-17 Thread Kenneth Hoste

Hi Shahzeb,

On 17/02/2017 17:45, Siddiqui, Shahzeb wrote:


I am having trouble figuring out why IntelBase easyblock is generating 
this module file. Do I need to create a separate easyblock for this? 
The build works fine with the IntelBase easyblock when I added my 
sanity check path.




It's unclear to me what you consider to be wrong in this module file 
exactly?


Is something missing, or are some environment variables set incorrectly?


regards,

Kenneth



hpcswadm@hpcv18$ml show clck



/nfs/grid/software/testing/RHEL7/easybuild/modules/all/clck/2017.1.016:



whatis("Description: Verifies cluster components work together ― for   
- better uptime and productivity and lower


total  - cost of ownership (TCO)   - Homepage: 
https://software.intel.com/en-us/intel-cluster-checker ")


conflict("clck")

setenv("EBROOTCLCK","/nfs/grid/software/testing/RHEL7/easybuild/software/clck/2017.1.016")

setenv("EBVERSIONCLCK","2017.1.016")

setenv("EBDEVELCLCK","/nfs/grid/software/testing/RHEL7/easybuild/software/clck/2017.1.016/easybuild/clck-2017.1.

016-easybuild-devel")

prepend_path("INTEL_LICENSE_FILE","/opt/intel/licenses/license.lic")

prepend_path("NLSPATH","/nfs/grid/software/testing/RHEL7/easybuild/software/clck/2017.1.016/idb/intel64/locale/%

l_%t/%N")

help([[ Verifies cluster components work together ― for

 - better uptime and productivity and lower total

- cost of ownership (TCO)

  - Homepage: https://software.intel.com/en-us/intel-cluster-checker

]])

Shahzeb Siddiqui

HPC Linux Engineer

B2220-447.2

Groton, CT