[
https://issues.apache.org/jira/browse/AIRAVATA-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140819#comment-17140819
]
ASF subversion and git services commented on AIRAVATA-3344:
-----------------------------------------------------------
Commit aec5cdfab5d185be4af3c66c8722f91079e0ddea in airavata-django-portal's
branch refs/heads/develop from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=aec5cdf ]
Merge branch 'AIRAVATA-3344-add-total-physical-memory-to-queue-settings' into
develop
> Add Total Physical Memory to queue settings
> -------------------------------------------
>
> Key: AIRAVATA-3344
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3344
> Project: Airavata
> Issue Type: Bug
> Components: Django Portal
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
>
> From chat with [~spamidig]:
> {quote}
> @Marcus For LM queues in bridges the memory need to be set in the interface,
> could you please enable memory for this for all gateways.
> Sure @spamidig. Which interface is this that memory needs to be set?
> In deployment currently we are only letting users set nodes and processors…
> for LM queue we should also let teh memory be set. We used to have this in
> PGA perhaps when we went to Django we simplified it by removing memory as a
> node reserved will also get the memory associated..for LM it is not the case
> in a shared memory system..
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
