Recent changes to feature-requests

Add support for CREAM CE

Muhammad Farhan Sjaugi — Sat, 02 Jul 2016 23:48:32 -0000

Hi,

Will you support CREAM CE direct job submission in near future?

Regards

Add support for DIRAC

Muhammad Farhan Sjaugi — Mon, 18 May 2015 15:03:49 -0000

Hi,

Will DIRAC middleware will be supported soon? because our NGI (Academic Grid Malaysia) will put more effort in supporting DIRAC for efficiency, hence I would really appreciate if gUSE/WS-PGRADE can support DIRAC as well.

Regards

Add user-specific info to robot proxies

Zoltán Farkas — Wed, 03 Dec 2014 09:55:40 -0000

EGI.eu has created a recommendation on adding portal user-specific identification to proxies created out of robot certificates used for job submission. The slides describing the approach are available here: http://indico.egi.eu/indico/materialDisplay.py?contribId=0&materialId=slides&confId=2155

DCI Bridge should be extended with this robot proxy annotation method.

#75 Potential speed-up in ASMService

chahuistle — Thu, 18 Sep 2014 10:58:09 -0000

Yes, we can definitively call the ASMWorkflowConfiguration object directly, changes on our part are minor and there's not a lot of copy-pasting anyway... Although, it would've been nicer to have it done in ASMService, you know, developers tend to be lazy ;)

#75 Potential speed-up in ASMService

Akos Balasko — Tue, 16 Sep 2014 08:50:20 -0000

Dear Luis,

As far as I see it has already been implemented, you need to get the configuration using asmService.getWorkflowConfig(String userID, String workflowName) method that returns an ASMWorkflowConfiguration object, modify this object as you need (setting inputs path and so on) which step does not indicate any web-service invocations, and finally save the configuration using asmService.saveWorkflowConfig(String userID, String workflowName, ASMWorkflowConfiguration) configuration) method.

Hope this solution is acceptable for you,

cheers,
akos

#75 Potential speed-up in ASMService

Zoltán Farkas — Mon, 26 May 2014 12:59:35 -0000

assigned_to: Akos Balasko

Unicore IDB Tools listing should always be sorted

chahuistle — Fri, 09 May 2014 20:34:14 -0000

Navigatina through the tools from the IDB from UNICORE can result in a tedious task if they are not sorted.

Currently, configuration for new UNICORE jobs do not display tools in alphabetical order, making it hard for users to find the desired tool.

The attached patch can be applied (i.e., git am --signoff < sorted_idbtools.path) to test my proposed (and tested) solution.

issue with the job inputs port

gregoire gesmier — Thu, 08 May 2014 14:06:09 -0000

Hi all,

there's an issue for the configuration of the workflows, if the same job input port has been uploaded with a file and on the sql tab the login and password field are fill then we will have the following error message on this port:

"Nothing in the set relating the given input port has been defined"

then the workflow can't be submitted

Regards
Gregoire Gesmier

Potential speed-up in ASMService

chahuistle — Wed, 16 Apr 2014 12:41:14 -0000

The ASM API, in its version 3.4.9, introduces an important step towards optimization of workflow configuration via the provided API. However, there is still a low hanging fruit refactoring that would speed-up ASM-based portals.

Suppose that in your code you set remote input ports. You would need to use setRemoteInputPath in ASMService. Looking at the source code, you'll realize that this method invokes getWorkflowConfig(userID, workflowName) and this method, in turn, invokes a web service. You'll easily realize that for each port that you want to set, a web service invocation will be performed. Typically, you would implement this in a for loop, as follows:

for (final Job job : workflow.getJobs()) {
  for (final InputPort port : job.getInputPorts()) {
    if (mustSetPort(port)) {
      final String path = generatePath(job, port);
      // webservice invocation
      asmService.setRemoteInputPath(userID, wfName, job.getName(), port.getNumber(), path);
    }
  }
}

If, however, the ASM API offered a way to pass the workflow configuration as a parameter, unnecessary web service invocations would be avoided:

// webservice call
ASMWorkflowConfiguration wfConfig = asmService.getWorkflowConfig(userID, wfName);
for (final Job job : workflow.getJobs()) {
  for (final InputPort port : job.getInputPorts()) {
    if (mustSetPort(port)) {
      final String path = generatePath(job, port);
      // no webservice call!
      asmService.setRemoteInputPath(wfConfig, userID, wfName, job.getName(), port.getNumber(), path);
    }
  }
}
// webservice call
asmService.saveWorkflowConfig(userID, wfName, wfConfig);

The polymorphed method setRemoteInputPath takes an ASMWorkflowConfiguration and, internally, it is not needed to invoke a web service to obtain it. In other words, only two webservices will be executed, regardless of the number of modified jobs.

ASMService would declare then two methods, as follows:

public void setRemoteInputPath(String userID, String workflowName, String jobName, String portNumber, String newRemotePath) {
  // no wf configuration... get it from the webservice
  ASMWorkflowConfiguration wfConfig = getWorkflowConfig(userID, workflowName);
  // invoke the "real" method now
  setRemoteInputpath(wfConfig, userID, workflowName, jobName, portNumber, newRemotePath);
}

public void setRemoteInputPath(ASMWorkflowConfiguration wfConfig, String userID, String workflowName, String jobName, String portNumber, String newRemotePath) {
    // configuration is given... no need to invoke a web service
    // do whatever is needed to set remote input path, given the configuration
}

I believe this change is a piece of cake to implement and would speed up things a lot if you need to operate on individual jobs.

Potential speed-up in ASMService

chahuistle — Wed, 16 Apr 2014 12:41:14 -0000

Ticket 75 has been modified: Potential speed-up in ASMService
Edited By: Zoltán Farkas (zfarkas)
Owner updated: None => u'akosbalasko'