[
https://issues.apache.org/jira/browse/AIRAVATA-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475792#comment-17475792
]
ASF subversion and git services commented on AIRAVATA-3543:
-----------------------------------------------------------
Commit 510cbe42e22c5b444b2887820d94d1c8be3904a5 in airavata-django-portal's
branch refs/heads/staging from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=510cbe4 ]
AIRAVATA-3543 Auto update nodeCount/totalCPUCount based on cpuPerNode
> When CPU per node is configured the Nodes are not calculated upon entering
> CPUs
> --------------------------------------------------------------------------------
>
> Key: AIRAVATA-3543
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3543
> Project: Airavata
> Issue Type: Bug
> Components: Django
> Reporter: Eroma
> Assignee: Marcus Christie
> Priority: Major
>
> When Computational clusters are configured, per partition we can define CPUs
> per node.
> When this is configured, at the time of creating a new experiment or updating
> aa cloned one user can enter CPUs and the nodes will be auto calculated.
> Similarly, when nodes are entered CPUs will be calculated.
> This feature is not currently existing in Django Portal. Need to enable this
> feature again for Django portals.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)