Menu
▾
▴
#66 free text in jdl
Hi,
In job configuration window, it is currently possible to specify some JDL parameters, but the list of possibilities is very limited. In some workflow components, it is very important for us to be able to specify some JDL attributes which are not currently included in WS-PGrade. As one specific example, I would like to be able to specify "WholeNodes = true;" for some workflows that require more resources.
It is necessary to be able to specify these things as free text, in much the same way, as it is currently possible to specify default JDL settings in DCI-Bridge configuration.
Thanks
Mahdi (AMC)
The WS-PGRADE administrator can define new parameters for each middleware type in "Settings / Message & Label Editor" menu in the following way:
For each parameter must be defined 2 key-value pair. One for the help text and one for the parameter key.
For eg.: add the key "CPUNumber" fog gLite:
select the radio button "add"
Key:glite.textCPUNumber
Desc:--
Value:The CPUNumber attribute is an integer greater than 1....
save the value.
select the radio button "add"
Key:glite.keyCPUNumber
Desc:--
Value:CPUNumber
save the value.
The keys are stored in the database.
If the previous values are disappeared, then restart WS-PGRADE.
Dear Imi,
Thanks for your reply. I am forwarding the message to the user forum.
I have tried your recommendation, and it partially works, meaning:
The field is successfully added to guse database and is shown in job
configuration, and it is added to the JDL, but in the wrong format, i.e.,
as a string instead of an integer. More specifically, it is added like
CPUNumber = "1";
while it should be like
CPUNumber = 1;
As a result, the WMS complains: wrong type caught for attribute
Best regards
Mahdi
On Wed, Feb 12, 2014 at 4:37 PM, imi i-mi@users.sf.net wrote:
Related
Feature Requests: #66
Which version do you use? From 3.6.0 the glite plugin should handle every integer type attribute (ShallowRetryCount, RetryCount, SMPGranularity, HostNumber, CPUNumber, max_running_nodes, ExpiryTime, PerusalTimeInterval)
By the way, CPUNumber will be added to the jdl if you define "MPI Node Number" in job configuration UI. In this case you do not need the jdl editor.
The description of the parameter definition is already in the Admin Manual (in the section Additional Enhancement).
Dear Tibor and Imi,
Thanks for your replies.
1- I am doing this on 3.6.1 where the newly added JDL attribute is treated
as String (I mean if I add the attribute as you explained using the Label
Editor portlet.
2- I will keep in mind that I can use the MPI workaround to trick guse to
put the CPUNumber tag in JDL (I am not using MPI clearly, but I understand
it could fix the problem).
3- The admin manual indeed explains that you can "change displayed texts"
in WS-PGrade, but you don't expect people to guess that this feature can
be used for adding JDL tags, do you?
On the other hand, I won't get to this page if I for example search for JDL
in this document. You do understand that this is the only way this document
may be used (I mean trust me, no one is going to read and memorize the
document like you do for your course exams!) :-)
Conclusion:
These are all nice features in WS-PGrade, but they are hidden! I would
suggest to make them more visible in the documentation. Probably there are
hundreds of such improvements possible, but maybe you can go on case by
case.
Regards
Mahdi
On Thu, Feb 13, 2014 at 3:39 PM, Tibor Gottdank gottdank@users.sf.netwrote:
Related
Feature Requests: #66