[jira] [Commented] (AIRAVATA-2907) UI for setting a gateway's StoragePreference
[
https://issues.apache.org/jira/browse/AIRAVATA-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690053#comment-16690053
]
ASF subversion and git services commented on AIRAVATA-2907:
---
Commit d30077beb635aaa5d004f8bd7f2c6702f35b9837 in airavata-django-portal's
branch refs/heads/master from [~marcuschristie]
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=d30077b ]
AIRAVATA-2907 Delete storage prefs
> UI for setting a gateway's StoragePreference
>
>
> Key: AIRAVATA-2907
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2907
> Project: Airavata
> Issue Type: Improvement
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Need a GatewayResourceProfile editor. Immediate need is to add storage
> preferences.
> h5. TODO
> * [x] load list of storage resources for picking to create a new storage
> preference
> * [x] only allow members of the Admins group to edit GatewayResourceProfile
> * [ ] delete storage preference
> * [ ] change backend to look for default key in GatewayResourceProfile (for
> storage preferences only)
> h5. Workaround
> Here's what I told Eroma for the workaround I did for SimCCS:
> {noformat}
> [4:56 PM] Marcus Christie: @eroma if you need to deploy more django gateways,
> you'll need to manually setup the STORAGE_PREFERENCE for each one.
> [4:56 PM] Marcus Christie: log into airav...@dbdev.scigap.org
> [4:56 PM] Marcus Christie: mysql app_catalog
> [4:56 PM] Marcus Christie: What I ran for SimCCS:
> [4:56 PM] Marcus Christie: insert into STORAGE_PREFERENCE values ('simccs',
> 'pgadev.scigap.org_7ddf28fd-d503-4ff8-bbc5-3279a7c3b99e', NULL,
> '/var/www/portals/gateway-user-data/django-simccs', 'pga');
> [4:57 PM] Marcus Christie: This assumes also that 1) you set a default
> credential for the Group Resource Profile and 2) you copy that SSH public key
> into pga's .ssh/authorized_keys file
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2907) UI for setting a gateway's StoragePreference
[
https://issues.apache.org/jira/browse/AIRAVATA-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690051#comment-16690051
]
ASF subversion and git services commented on AIRAVATA-2907:
---
Commit dd63cc19d120771a172f5ae8a88ea41cb10c9aec in airavata-django-portal's
branch refs/heads/master from [~marcuschristie]
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=dd63cc1 ]
AIRAVATA-2907 Better default ssh key description; filter storage options
> UI for setting a gateway's StoragePreference
>
>
> Key: AIRAVATA-2907
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2907
> Project: Airavata
> Issue Type: Improvement
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Need a GatewayResourceProfile editor. Immediate need is to add storage
> preferences.
> h5. TODO
> * [x] load list of storage resources for picking to create a new storage
> preference
> * [x] only allow members of the Admins group to edit GatewayResourceProfile
> * [ ] delete storage preference
> * [ ] change backend to look for default key in GatewayResourceProfile (for
> storage preferences only)
> h5. Workaround
> Here's what I told Eroma for the workaround I did for SimCCS:
> {noformat}
> [4:56 PM] Marcus Christie: @eroma if you need to deploy more django gateways,
> you'll need to manually setup the STORAGE_PREFERENCE for each one.
> [4:56 PM] Marcus Christie: log into airav...@dbdev.scigap.org
> [4:56 PM] Marcus Christie: mysql app_catalog
> [4:56 PM] Marcus Christie: What I ran for SimCCS:
> [4:56 PM] Marcus Christie: insert into STORAGE_PREFERENCE values ('simccs',
> 'pgadev.scigap.org_7ddf28fd-d503-4ff8-bbc5-3279a7c3b99e', NULL,
> '/var/www/portals/gateway-user-data/django-simccs', 'pga');
> [4:57 PM] Marcus Christie: This assumes also that 1) you set a default
> credential for the Group Resource Profile and 2) you copy that SSH public key
> into pga's .ssh/authorized_keys file
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2907) UI for setting a gateway's StoragePreference
[
https://issues.apache.org/jira/browse/AIRAVATA-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690049#comment-16690049
]
ASF subversion and git services commented on AIRAVATA-2907:
---
Commit da40a7ba995556c05fd657bcd65e3fb9de461134 in airavata-django-portal's
branch refs/heads/master from [~marcuschristie]
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=da40a7b ]
AIRAVATA-2907 Only allow Admins to edit GatewayResourceProfile
> UI for setting a gateway's StoragePreference
>
>
> Key: AIRAVATA-2907
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2907
> Project: Airavata
> Issue Type: Improvement
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Need a GatewayResourceProfile editor. Immediate need is to add storage
> preferences.
> h5. TODO
> * [x] load list of storage resources for picking to create a new storage
> preference
> * [x] only allow members of the Admins group to edit GatewayResourceProfile
> * [ ] delete storage preference
> * [ ] change backend to look for default key in GatewayResourceProfile (for
> storage preferences only)
> h5. Workaround
> Here's what I told Eroma for the workaround I did for SimCCS:
> {noformat}
> [4:56 PM] Marcus Christie: @eroma if you need to deploy more django gateways,
> you'll need to manually setup the STORAGE_PREFERENCE for each one.
> [4:56 PM] Marcus Christie: log into airav...@dbdev.scigap.org
> [4:56 PM] Marcus Christie: mysql app_catalog
> [4:56 PM] Marcus Christie: What I ran for SimCCS:
> [4:56 PM] Marcus Christie: insert into STORAGE_PREFERENCE values ('simccs',
> 'pgadev.scigap.org_7ddf28fd-d503-4ff8-bbc5-3279a7c3b99e', NULL,
> '/var/www/portals/gateway-user-data/django-simccs', 'pga');
> [4:57 PM] Marcus Christie: This assumes also that 1) you set a default
> credential for the Group Resource Profile and 2) you copy that SSH public key
> into pga's .ssh/authorized_keys file
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2907) UI for setting a gateway's StoragePreference
[
https://issues.apache.org/jira/browse/AIRAVATA-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690052#comment-16690052
]
ASF subversion and git services commented on AIRAVATA-2907:
---
Commit fd358e4781ff804e1c3e4a2602d1ea3b6a7b75c3 in airavata-django-portal's
branch refs/heads/master from [~marcuschristie]
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=fd358e4 ]
AIRAVATA-2907 Formatting storage pref listing
> UI for setting a gateway's StoragePreference
>
>
> Key: AIRAVATA-2907
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2907
> Project: Airavata
> Issue Type: Improvement
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Need a GatewayResourceProfile editor. Immediate need is to add storage
> preferences.
> h5. TODO
> * [x] load list of storage resources for picking to create a new storage
> preference
> * [x] only allow members of the Admins group to edit GatewayResourceProfile
> * [ ] delete storage preference
> * [ ] change backend to look for default key in GatewayResourceProfile (for
> storage preferences only)
> h5. Workaround
> Here's what I told Eroma for the workaround I did for SimCCS:
> {noformat}
> [4:56 PM] Marcus Christie: @eroma if you need to deploy more django gateways,
> you'll need to manually setup the STORAGE_PREFERENCE for each one.
> [4:56 PM] Marcus Christie: log into airav...@dbdev.scigap.org
> [4:56 PM] Marcus Christie: mysql app_catalog
> [4:56 PM] Marcus Christie: What I ran for SimCCS:
> [4:56 PM] Marcus Christie: insert into STORAGE_PREFERENCE values ('simccs',
> 'pgadev.scigap.org_7ddf28fd-d503-4ff8-bbc5-3279a7c3b99e', NULL,
> '/var/www/portals/gateway-user-data/django-simccs', 'pga');
> [4:57 PM] Marcus Christie: This assumes also that 1) you set a default
> credential for the Group Resource Profile and 2) you copy that SSH public key
> into pga's .ssh/authorized_keys file
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRAVATA-2950) Failed output file transfer task hangs in the system until task timeout and fails the rest of the workflow
[ https://issues.apache.org/jira/browse/AIRAVATA-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-2950: Description: # File transfer scp session transfers part of the file and then the scp session hangs. # The file transfer task will be alive since the scp session is alive and open # The helix tasks has its own timeouts, and when the timeout took place the task cancelled. # When the task cancels the rest of the workflow fails. Is there a way to figure out the file transfer hangs, or that it stopped in middle. If this task fails is the experiment tagged as FAILED? A fix to this issue need to [consider|https://staging.ultrascan.scigap.org/] large file transfers and slow file transfers as well. US3-ADEV_226a4446-49a4-4125-ba2c-020d7f0afa8e was: # File transfer scp session transfers part of the file and then the scp session hangs. # The file transfer task will be alive since the scp session is alive and open # The helix tasks has its own timeouts, and when the timeout took place the task cancelled. # When the task cancels the rest of the workflow fails. Is there a way to figure out the file transfer hangs, or that it stopped in middle. If this task fails is the experiment tagged as FAILED? A fix to this issue need to [consider|https://staging.ultrascan.scigap.org/] large file transfers and slow file transfers as well. > Failed output file transfer task hangs in the system until task timeout and > fails the rest of the workflow > -- > > Key: AIRAVATA-2950 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2950 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 > Environment: https://staging.ultrascan.scigap.org >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > # File transfer scp session transfers part of the file and then the scp > session hangs. > # The file transfer task will be alive since the scp session is alive and > open > # The helix tasks has its own timeouts, and when the timeout took place the > task cancelled. > # When the task cancels the rest of the workflow fails. > Is there a way to figure out the file transfer hangs, or that it stopped in > middle. If this task fails is the experiment tagged as FAILED? > A fix to this issue need to [consider|https://staging.ultrascan.scigap.org/] > large file transfers and slow file transfers as well. > US3-ADEV_226a4446-49a4-4125-ba2c-020d7f0afa8e -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRAVATA-2950) Failed output file transfer task hangs in the system until task timeout and fails the rest of the workflow
Eroma created AIRAVATA-2950: --- Summary: Failed output file transfer task hangs in the system until task timeout and fails the rest of the workflow Key: AIRAVATA-2950 URL: https://issues.apache.org/jira/browse/AIRAVATA-2950 Project: Airavata Issue Type: Bug Components: helix implementation Affects Versions: 0.18 Environment: https://staging.ultrascan.scigap.org Reporter: Eroma Assignee: Dimuthu Upeksha Fix For: 0.18 # File transfer scp session transfers part of the file and then the scp session hangs. # The file transfer task will be alive since the scp session is alive and open # The helix tasks has its own timeouts, and when the timeout took place the task cancelled. # When the task cancels the rest of the workflow fails. Is there a way to figure out the file transfer hangs, or that it stopped in middle. If this task fails is the experiment tagged as FAILED? A fix to this issue need to [consider|https://staging.ultrascan.scigap.org/] large file transfers and slow file transfers as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRAVATA-2949) Cannot add users to admin and gateway_user groups for admin gateway user
Eroma created AIRAVATA-2949: --- Summary: Cannot add users to admin and gateway_user groups for admin gateway user Key: AIRAVATA-2949 URL: https://issues.apache.org/jira/browse/AIRAVATA-2949 Project: Airavata Issue Type: Bug Components: Django Portal Affects Versions: 0.18 Environment: https://django.seagrid.org Reporter: Eroma Assignee: Marcus Christie Fix For: 0.18 # Logged in to [https://django.seagrid.org|https://django.seagrid.org/] as admin user # Can edit gateway_user, admin read only and admin groups. # No users are listed for admin and gateway_user groups # Cannot search and add new users to those two groups, searching doesn't retrieve any users. # Admin read only group seem to be working, users can be searched and existing users are listed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRAVATA-2907) UI for setting a gateway's StoragePreference
[
https://issues.apache.org/jira/browse/AIRAVATA-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-2907:
--
Description:
Need a GatewayResourceProfile editor. Immediate need is to add storage
preferences.
h5. TODO
* [x] load list of storage resources for picking to create a new storage
preference
* [x] only allow members of the Admins group to edit GatewayResourceProfile
* [ ] delete storage preference
* [ ] change backend to look for default key in GatewayResourceProfile (for
storage preferences only)
h5. Workaround
Here's what I told Eroma for the workaround I did for SimCCS:
{noformat}
[4:56 PM] Marcus Christie: @eroma if you need to deploy more django gateways,
you'll need to manually setup the STORAGE_PREFERENCE for each one.
[4:56 PM] Marcus Christie: log into airav...@dbdev.scigap.org
[4:56 PM] Marcus Christie: mysql app_catalog
[4:56 PM] Marcus Christie: What I ran for SimCCS:
[4:56 PM] Marcus Christie: insert into STORAGE_PREFERENCE values ('simccs',
'pgadev.scigap.org_7ddf28fd-d503-4ff8-bbc5-3279a7c3b99e', NULL,
'/var/www/portals/gateway-user-data/django-simccs', 'pga');
[4:57 PM] Marcus Christie: This assumes also that 1) you set a default
credential for the Group Resource Profile and 2) you copy that SSH public key
into pga's .ssh/authorized_keys file
{noformat}
was:
Need a GatewayResourceProfile editor. Immediate need is to add storage
preferences.
h5. TODO
* [x] load list of storage resources for picking to create a new storage
preference
* [x] only allow members of the Admins group to edit GatewayResourceProfile
* [ ] delete storage preference
h5. Workaround
Here's what I told Eroma for the workaround I did for SimCCS:
{noformat}
[4:56 PM] Marcus Christie: @eroma if you need to deploy more django gateways,
you'll need to manually setup the STORAGE_PREFERENCE for each one.
[4:56 PM] Marcus Christie: log into airav...@dbdev.scigap.org
[4:56 PM] Marcus Christie: mysql app_catalog
[4:56 PM] Marcus Christie: What I ran for SimCCS:
[4:56 PM] Marcus Christie: insert into STORAGE_PREFERENCE values ('simccs',
'pgadev.scigap.org_7ddf28fd-d503-4ff8-bbc5-3279a7c3b99e', NULL,
'/var/www/portals/gateway-user-data/django-simccs', 'pga');
[4:57 PM] Marcus Christie: This assumes also that 1) you set a default
credential for the Group Resource Profile and 2) you copy that SSH public key
into pga's .ssh/authorized_keys file
{noformat}
> UI for setting a gateway's StoragePreference
>
>
> Key: AIRAVATA-2907
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2907
> Project: Airavata
> Issue Type: Improvement
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Need a GatewayResourceProfile editor. Immediate need is to add storage
> preferences.
> h5. TODO
> * [x] load list of storage resources for picking to create a new storage
> preference
> * [x] only allow members of the Admins group to edit GatewayResourceProfile
> * [ ] delete storage preference
> * [ ] change backend to look for default key in GatewayResourceProfile (for
> storage preferences only)
> h5. Workaround
> Here's what I told Eroma for the workaround I did for SimCCS:
> {noformat}
> [4:56 PM] Marcus Christie: @eroma if you need to deploy more django gateways,
> you'll need to manually setup the STORAGE_PREFERENCE for each one.
> [4:56 PM] Marcus Christie: log into airav...@dbdev.scigap.org
> [4:56 PM] Marcus Christie: mysql app_catalog
> [4:56 PM] Marcus Christie: What I ran for SimCCS:
> [4:56 PM] Marcus Christie: insert into STORAGE_PREFERENCE values ('simccs',
> 'pgadev.scigap.org_7ddf28fd-d503-4ff8-bbc5-3279a7c3b99e', NULL,
> '/var/www/portals/gateway-user-data/django-simccs', 'pga');
> [4:57 PM] Marcus Christie: This assumes also that 1) you set a default
> credential for the Group Resource Profile and 2) you copy that SSH public key
> into pga's .ssh/authorized_keys file
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (AIRAVATA-2907) UI for setting a gateway's StoragePreference
[
https://issues.apache.org/jira/browse/AIRAVATA-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-2907:
--
Description:
Need a GatewayResourceProfile editor. Immediate need is to add storage
preferences.
h5. TODO
* [x] load list of storage resources for picking to create a new storage
preference
* [x] only allow members of the Admins group to edit GatewayResourceProfile
* [ ] delete storage preference
h5. Workaround
Here's what I told Eroma for the workaround I did for SimCCS:
{noformat}
[4:56 PM] Marcus Christie: @eroma if you need to deploy more django gateways,
you'll need to manually setup the STORAGE_PREFERENCE for each one.
[4:56 PM] Marcus Christie: log into airav...@dbdev.scigap.org
[4:56 PM] Marcus Christie: mysql app_catalog
[4:56 PM] Marcus Christie: What I ran for SimCCS:
[4:56 PM] Marcus Christie: insert into STORAGE_PREFERENCE values ('simccs',
'pgadev.scigap.org_7ddf28fd-d503-4ff8-bbc5-3279a7c3b99e', NULL,
'/var/www/portals/gateway-user-data/django-simccs', 'pga');
[4:57 PM] Marcus Christie: This assumes also that 1) you set a default
credential for the Group Resource Profile and 2) you copy that SSH public key
into pga's .ssh/authorized_keys file
{noformat}
was:
Need a GatewayResourceProfile editor. Immediate need is to add storage
preferences.
h5. TODO
* [ ] load list of storage resources for picking to create a new storage
preference
* [ ] only allow members of the Admins group to edit GatewayResourceProfile
* [ ] delete storage preference
h5. Workaround
Here's what I told Eroma for the workaround I did for SimCCS:
{noformat}
[4:56 PM] Marcus Christie: @eroma if you need to deploy more django gateways,
you'll need to manually setup the STORAGE_PREFERENCE for each one.
[4:56 PM] Marcus Christie: log into airav...@dbdev.scigap.org
[4:56 PM] Marcus Christie: mysql app_catalog
[4:56 PM] Marcus Christie: What I ran for SimCCS:
[4:56 PM] Marcus Christie: insert into STORAGE_PREFERENCE values ('simccs',
'pgadev.scigap.org_7ddf28fd-d503-4ff8-bbc5-3279a7c3b99e', NULL,
'/var/www/portals/gateway-user-data/django-simccs', 'pga');
[4:57 PM] Marcus Christie: This assumes also that 1) you set a default
credential for the Group Resource Profile and 2) you copy that SSH public key
into pga's .ssh/authorized_keys file
{noformat}
> UI for setting a gateway's StoragePreference
>
>
> Key: AIRAVATA-2907
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2907
> Project: Airavata
> Issue Type: Improvement
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> Need a GatewayResourceProfile editor. Immediate need is to add storage
> preferences.
> h5. TODO
> * [x] load list of storage resources for picking to create a new storage
> preference
> * [x] only allow members of the Admins group to edit GatewayResourceProfile
> * [ ] delete storage preference
> h5. Workaround
> Here's what I told Eroma for the workaround I did for SimCCS:
> {noformat}
> [4:56 PM] Marcus Christie: @eroma if you need to deploy more django gateways,
> you'll need to manually setup the STORAGE_PREFERENCE for each one.
> [4:56 PM] Marcus Christie: log into airav...@dbdev.scigap.org
> [4:56 PM] Marcus Christie: mysql app_catalog
> [4:56 PM] Marcus Christie: What I ran for SimCCS:
> [4:56 PM] Marcus Christie: insert into STORAGE_PREFERENCE values ('simccs',
> 'pgadev.scigap.org_7ddf28fd-d503-4ff8-bbc5-3279a7c3b99e', NULL,
> '/var/www/portals/gateway-user-data/django-simccs', 'pga');
> [4:57 PM] Marcus Christie: This assumes also that 1) you set a default
> credential for the Group Resource Profile and 2) you copy that SSH public key
> into pga's .ssh/authorized_keys file
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (AIRAVATA-2948) Implement user friendly actionable and informative messages in Airavata
Eroma created AIRAVATA-2948: --- Summary: Implement user friendly actionable and informative messages in Airavata Key: AIRAVATA-2948 URL: https://issues.apache.org/jira/browse/AIRAVATA-2948 Project: Airavata Issue Type: Task Components: Airavata API, helix implementation Affects Versions: 0.18 Environment: https://staging.ultrascan.scigap.org Reporter: Eroma Assignee: Dimuthu Upeksha Fix For: 0.18 Currently the direct ERROR logs are presented to the user and they may not be clear or directly actionable. Going forward apart fro the ERROR message more actionable message will be presented. The change will be for internal components of airavata and also the the gateway bridge code. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRAVATA-2947) Random experiments in CREATED without moving forward. Need more insight in to the situation
Eroma created AIRAVATA-2947: --- Summary: Random experiments in CREATED without moving forward. Need more insight in to the situation Key: AIRAVATA-2947 URL: https://issues.apache.org/jira/browse/AIRAVATA-2947 Project: Airavata Issue Type: Task Components: Airavata API Affects Versions: 0.18 Reporter: Eroma Assignee: Dimuthu Upeksha Fix For: 0.18 Random experiments in CREATED. The current logs in API need to be improved to contain more messages to locate the issue. The Gateway bridge code should be also studied to analyze the situation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRAVATA-2947) Random experiments in CREATED without moving forward. Need more insight in to the situation
[ https://issues.apache.org/jira/browse/AIRAVATA-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-2947: Description: Random experiments in CREATED. The current logs in API need to be improved to contain more messages to locate the issue. Current log files in API server does not provide any messages for these CREATED experiments. The Gateway bridge code should be also studied to analyze the situation. was: Random experiments in CREATED. The current logs in API need to be improved to contain more messages to locate the issue. The Gateway bridge code should be also studied to analyze the situation. > Random experiments in CREATED without moving forward. Need more insight in to > the situation > --- > > Key: AIRAVATA-2947 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2947 > Project: Airavata > Issue Type: Task > Components: Airavata API >Affects Versions: 0.18 >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > Random experiments in CREATED. The current logs in API need to be improved to > contain more messages to locate the issue. > Current log files in API server does not provide any messages for these > CREATED experiments. > The Gateway bridge code should be also studied to analyze the situation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRAVATA-2946) Monitoring and notification mechanism for Apache Helix components in Airavata
Eroma created AIRAVATA-2946: --- Summary: Monitoring and notification mechanism for Apache Helix components in Airavata Key: AIRAVATA-2946 URL: https://issues.apache.org/jira/browse/AIRAVATA-2946 Project: Airavata Issue Type: Task Components: helix implementation Affects Versions: 0.18 Environment: https://staging.ultrascan.scigap.org Reporter: Eroma Assignee: Dimuthu Upeksha Fix For: 0.18 Currently the Helix server component level issues such as unresponsiveness goes undetected unless a gateway or a user reports experiment issues. Once reported the Airavata development team can act on the issue and experiments move forward. In order to be proactive a mechanism to monitor and notify Helix server components should be implemented. Any server getting into a 'hanged' state will be notified. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (AIRAVATA-2942) Experiment cancelation request was not processed in Helix
[ https://issues.apache.org/jira/browse/AIRAVATA-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2942. --- Resolution: Fixed > Experiment cancelation request was not processed in Helix > -- > > Key: AIRAVATA-2942 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2942 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 > Environment: https://staging.ultrascan.scigap.org - exp ID: > US3-ADEV_4e8bdbb7-20f9-4dcf-82be-e2c581b651b6 >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > Experiment was launched and the job was submitted to Slurm cluster. After > nearly 4 hours the user sends a cancel request as the job was queued for a > long time. The cancel request has come on the same day but it didnt process > it. Hence the experiment was left as CANCELING without processing and > cancelling it. > This issue was seeing occurring in multiple HPC clusters with the gateway. > NOTE: the email shows that this was queued for nearly a day but no indication > of job completing email in the mailbox. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2942) Experiment cancelation request was not processed in Helix
[ https://issues.apache.org/jira/browse/AIRAVATA-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689597#comment-16689597 ] Dimuthu Upeksha commented on AIRAVATA-2942: --- Fixed in [https://github.com/apache/airavata/commit/3e879e4325fba582186acd8133552ea6f8542cb6] [https://github.com/apache/airavata/commit/e642e7f1e42072bbe63dbd3e357acc8af2a8fa74] [https://github.com/apache/airavata/commit/bb7d3ca0770a1a0301d975e30e7eb37f9834b7c4] [https://github.com/apache/airavata/commit/23631de8140ef0d74c95cfaf5eeb4228e800a037] https://github.com/apache/airavata/commit/3f68a88febe5c7997d2c2627fd720fbdda278494 > Experiment cancelation request was not processed in Helix > -- > > Key: AIRAVATA-2942 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2942 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 > Environment: https://staging.ultrascan.scigap.org - exp ID: > US3-ADEV_4e8bdbb7-20f9-4dcf-82be-e2c581b651b6 >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > Experiment was launched and the job was submitted to Slurm cluster. After > nearly 4 hours the user sends a cancel request as the job was queued for a > long time. The cancel request has come on the same day but it didnt process > it. Hence the experiment was left as CANCELING without processing and > cancelling it. > This issue was seeing occurring in multiple HPC clusters with the gateway. > NOTE: the email shows that this was queued for nearly a day but no indication > of job completing email in the mailbox. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
