You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Lahiru Gunathilake (JIRA)" <ji...@apache.org> on 2012/11/20 18:09:00 UTC

[jira] [Commented] (AIRAVATA-635) Providing sample to configure workflow context header for each node

    [ https://issues.apache.org/jira/browse/AIRAVATA-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501304#comment-13501304 ] 

Lahiru Gunathilake commented on AIRAVATA-635:
---------------------------------------------

If you provide the context header like this it will pick appropriate configuration for each node during gfac invocation.

<wor:workflow-scheduling-context>
    <!--1 or more repetitions:-->
    <wor:application-scheduling-context wor:workflow-node-id="string" wor:service-id="THIS IS THE SERVICE NODE NAME IN YOUR WORKFLOW" wor:host-name="http://www.any.com/certo/quisquam" wor:wsgram-preferred="true" wor:gatekeeper-epr="http://www.sample.gov/ac/sed" wor:job-manager="string" wor:cpu-count="3" wor:node-count="3" wor:queue-name="string" wor:max-wall-time="3">string</wor:application-scheduling-context>

<wor:application-scheduling-context wor:workflow-node-id="string" wor:service-id="NODE1" wor:host-name="http://www.any.com/certo/quisquam" wor:wsgram-preferred="true" wor:gatekeeper-epr="http://www.sample.gov/ac/sed" wor:job-manager="string" wor:cpu-count="3" wor:node-count="3" wor:queue-name="string" wor:max-wall-time="3">string</wor:application-scheduling-context>

<wor:application-scheduling-context wor:workflow-node-id="string" wor:service-id="NODE2" wor:host-name="http://www.any.com/certo/quisquam" wor:wsgram-preferred="true" wor:gatekeeper-epr="http://www.sample.gov/ac/sed" wor:job-manager="string" wor:cpu-count="3" wor:node-count="3" wor:queue-name="string" wor:max-wall-time="3">string</wor:application-scheduling-context>


  </wor:workflow-scheduling-context>

So in your workflowContext header if you specify each application configuration element with service ID we use that.
                
> Providing sample to configure workflow context header for each node
> -------------------------------------------------------------------
>
>                 Key: AIRAVATA-635
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-635
>             Project: Airavata
>          Issue Type: Bug
>          Components: Workflow Tracking
>         Environment: mac
>            Reporter: Lahiru Gunathilake
>             Fix For: 0.7
>
>
> $subject

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira