add easyblock for installing Allinea tools#279
Conversation
There was a problem hiding this comment.
is it better to copy a file or, to rather symlink towards $HOME/licenses/allinea* ?
just asking the question to hear the argumentation...
There was a problem hiding this comment.
btw. the intention of the comment above is to obtain the same functionality like with Intel tools:
I can change the license server in one place without having to hack around directories;
how to implement that is left as an exercise (I would do the symlink approach most likely)
There was a problem hiding this comment.
Symlinking is not a good option imho. You're not always installing the software with a user that has his home dir wide open to everyone who will be using the software.
For Intel tools, it's usually a different story.
There was a problem hiding this comment.
the ability to centrally control the licensing on per vendor basis, has proven to be ultra-useful;
if there is some way to continue having that feature -seen with intel cases- with DDT, it could be worthy.
(think of this case: after 12 buildsets with 3 DDT versions each, you change the license server location, that serves perhaps N clusters)
maybe you say that a license manager proxy is the solution to that kind of need...
There was a problem hiding this comment.
I'm just saying this is not EasyBuild's problem...
For Intel tools, they listen to environment variable like $INTEL_LICENSE_FILE, so you can move license files or start using new ones whenever you want. I'm not aware of something like that for Allinea, but I might be wrong.
|
Sorry, I am a bit confused about this |
|
Jenkins: test this please |
1 similar comment
|
Jenkins: test this please |
|
@besserox: I think you're right, maybe I'm taking this step too far... I'll get rid of that part, which also removes the requirement of having X forwarding enabled. |
|
Reworked on top of |
add easyblock for installing Allinea tools
This currently requires X forwarding to be enabled, and thus this is not ready to be merged in yet (although it works fine)...
We need to figure out a way around the X forwarding mess.
The
ddttool doesn't require X forwarding when a~/.allinea/system.configfile is present already, but does require it to (re)generate one. Maybe putting a dummy file there would work?