[jira] [Commented] (AIRAVATA-3570) Adapt components for reuse separately in custom experiment editing situations

["Marcus Christie (Jira)" <ji...@apache.org>]

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

Marcus Christie commented on AIRAVATA-3570:
-------------------------------------------

There are three components that can be used together apart from the adpf-experiment-editor component. This should be useful for embedding in custom experiment creation/editing forms that want to reuse these components and their logic.

h3.  adpf-group-resource-profile-selector

{code}
<adpf-group-resource-profile-selector value="some-grp-id">
</adpf-group-resource-profile-selector>
{code}

Attributes:
- value: (optional) group resource profile id

Events:
- input: updated group resource profile id will be the first element in the {{event.detail}} array

h3.  adpf-experiment-compute-resource-selector

{code}
<adpf-experiment-compute-resource-selector value="some-compute-resource-id" application-module-id="some-application-module-id">
</adpf-experiment-compute-resource-selector>
{code}

Attributes:
- value: (optional) compute resource id
- application-module-id: (*required*) application module id, this is used to load available application deployments

Events:
- input: updated compute resource id will be the first element in the {{event.detail}} array

h3.  adpf-experiment-compute-resource-selector

{code}
<adpf-queue-settings-editor queue-name="shared" node-count="1" total-cpu-count="48" wall-time-limit="30">
</adpf-queue-settings-editor>
{code}

Attributes:
- queue-name: (optional) name of queue on compute resource
- node-count: (optional) number of nodes
- total-cpu-count: (optional) number of cpus
- wall-time-limit: (optional) number of minutes walltime
- total-physical-memory: (optional) number of MB of memory

Events:
- input: updated queue settings object will be the first element in the {{event.detail}} array. Example value:
{code}
{
  "queueName": "shared",
  "totalCPUCount": 24,
  "nodeCount": 2,
  "wallTimeLimit": 30,
  "totalPhysicalMemory": 0
}
{code}


> Adapt components for reuse separately in custom experiment editing situations
> -----------------------------------------------------------------------------
>
>                 Key: AIRAVATA-3570
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3570
>             Project: Airavata
>          Issue Type: New Feature
>          Components: Django Portal
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> The web components assume that they are used together in concert with the adpf-experiment-editor component. Sometimes a gateway will want a custom user interface for specifying experiments but it would be very useful to reuse the:
>  * group resource profile selector
>  * computation resource selector
>  * batch queue settings editor
> These components rely on a few different API to get available options and to apply maximum allowed values, so re-implementing this logic over again would be time consuming.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)