[jira] [Commented] (AIRAVATA-2984) Webpack bundle fails to load during deploy
[
https://issues.apache.org/jira/browse/AIRAVATA-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798188#comment-16798188
]
Marcus Christie commented on AIRAVATA-2984:
---
I've implemented setting the DEBUG flag to False. This does turn on caching and
it helps the issue.
However, if the webpack-stats.json file had not been loaded once then it won't
be cached and you can still run into the problem during a deploy.
To really address this I think we need to load the webpack-stats.json file out
of the static/ directory instead of from the source checkout directory. This
way everything is consistent. And this would allow us to set DEBUG to True if
we needed to do so.
> Webpack bundle fails to load during deploy
> --
>
> Key: AIRAVATA-2984
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2984
> Project: Airavata
> Issue Type: Bug
> Components: Django Portal
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> {noformat}
> Loading failed for the
[jira] [Commented] (AIRAVATA-2984) Webpack bundle fails to load during deploy
[
https://issues.apache.org/jira/browse/AIRAVATA-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16798191#comment-16798191
]
ASF subversion and git services commented on AIRAVATA-2984:
---
Commit dcbb73f518a237121677bc1ae89031c34e20bb4c in airavata's branch
refs/heads/develop from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=dcbb73f ]
AIRAVATA-2984 default DEBUG to false for Django deploys
Also add alias for /media serving in Apache virtual host config.
> Webpack bundle fails to load during deploy
> --
>
> Key: AIRAVATA-2984
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2984
> Project: Airavata
> Issue Type: Bug
> Components: Django Portal
>Reporter: Marcus Christie
>Assignee: Marcus Christie
>Priority: Major
>
> {noformat}
> Loading failed for the
[jira] [Updated] (AIRAVATA-2984) Webpack bundle fails to load during deploy
[
https://issues.apache.org/jira/browse/AIRAVATA-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Christie updated AIRAVATA-2984:
--
Description:
{noformat}
Loading failed for the
[jira] [Created] (AIRAVATA-2999) [GSoC] Administration ashboard for Airavata Services
Dimuthu Upeksha created AIRAVATA-2999: - Summary: [GSoC] Administration ashboard for Airavata Services Key: AIRAVATA-2999 URL: https://issues.apache.org/jira/browse/AIRAVATA-2999 Project: Airavata Issue Type: New Feature Reporter: Dimuthu Upeksha Typical Apache Airavata deployment consists of multiple microservices (API Server, Participant, Controller, Pre Workflow Manager, Post Workflow Manager, Job Monitors and etc) and several other services (Database, Kafka, RabbitMQ, Keycloak, Zookeeper, Apache Helix). As it is a deployment with multiple components, when it comes to an issue, it is time consuming to find which component is having the problem. So we need an Administration Dashboard which can visualize the system health and provide some handle to Administrators to control those services like stopping or restarting each component through the dashboard. Additionally, this dashboard should be able to Authenticate users through Keycloak which is the identity provider for Airavata and only system administrators should be given access to those operations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRAVATA-2999) [GSoC] Administration Dashboard for Airavata Services
[ https://issues.apache.org/jira/browse/AIRAVATA-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha updated AIRAVATA-2999: -- Description: Typical Apache Airavata deployment consists of multiple microservices (API Server, Participant, Controller, Pre Workflow Manager, Post Workflow Manager, Job Monitors and etc) and several other services (Database, Kafka, RabbitMQ, Keycloak, Zookeeper, Apache Helix). As it is a deployment with multiple components, when it comes to an issue, it is time consuming to find which component is having the problem. So we need an Administration Dashboard which can visualize the system health and provide some handle to administrators to control those services like stopping or restarting each component through the dashboard. Additionally, this dashboard should be able to authenticate users through Keycloak which is the identity provider for Airavata and only system administrators should be given access to those operations. was: Typical Apache Airavata deployment consists of multiple microservices (API Server, Participant, Controller, Pre Workflow Manager, Post Workflow Manager, Job Monitors and etc) and several other services (Database, Kafka, RabbitMQ, Keycloak, Zookeeper, Apache Helix). As it is a deployment with multiple components, when it comes to an issue, it is time consuming to find which component is having the problem. So we need an Administration Dashboard which can visualize the system health and provide some handle to Administrators to control those services like stopping or restarting each component through the dashboard. Additionally, this dashboard should be able to Authenticate users through Keycloak which is the identity provider for Airavata and only system administrators should be given access to those operations. Summary: [GSoC] Administration Dashboard for Airavata Services (was: [GSoC] Administration ashboard for Airavata Services) > [GSoC] Administration Dashboard for Airavata Services > - > > Key: AIRAVATA-2999 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2999 > Project: Airavata > Issue Type: New Feature >Reporter: Dimuthu Upeksha >Priority: Major > > Typical Apache Airavata deployment consists of multiple microservices (API > Server, Participant, Controller, Pre Workflow Manager, Post Workflow Manager, > Job Monitors and etc) and several other services (Database, Kafka, RabbitMQ, > Keycloak, Zookeeper, Apache Helix). As it is a deployment with multiple > components, when it comes to an issue, it is time consuming to find which > component is having the problem. So we need an Administration Dashboard which > can visualize the system health and provide some handle to administrators to > control those services like stopping or restarting each component through the > dashboard. > Additionally, this dashboard should be able to authenticate users through > Keycloak which is the identity provider for Airavata and only system > administrators should be given access to those operations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRAVATA-3000) [GSoC] Refactor parser framework into a generic workflow framework
Dimuthu Upeksha created AIRAVATA-3000: - Summary: [GSoC] Refactor parser framework into a generic workflow framework Key: AIRAVATA-3000 URL: https://issues.apache.org/jira/browse/AIRAVATA-3000 Project: Airavata Issue Type: New Feature Reporter: Dimuthu Upeksha This an extension of the work we have done in GSoC 2018. Yasas has worked on developing a workflow framework for Airavata and his mail list discussions and medium post can be found from [1] [2]. Based on his research and the another GSoC project which was done in integrating a parser framework for Airavata, we have developed a new parser framework [3] [4] [5] [6] which utilized Apache Helix task framework [7] as the task execution engine. Even though this framework was specifically developed for parsers, we feel that this implementation shares a lot of common features of the workflow design which Yasas has worked on. So in this project we need to generalize parser framework into a generic workflow framework where we can create and launch workflows with any application registered in Airavata Student should be good at Java and distributed system concepts Key Expectations # Refactor/ improve parser data models into workflow data models # Refactor/ improve parser tables into workflow database tables # Implement new helix tasks to support workflow operations mentioned in [2] # Refactor/ improve parser API into a workflow level API [5] # Demonstrate that we can still preserve parser workflows in newly created generic workflow engine (This will be final demo). [1] [https://medium.com/@yasgun/gsoc-2018-with-apache-airavata-user-defined-airavata-workflows-39f0e79234ee] [2] [http://mail-archives.apache.org/mod_mbox/airavata-dev/201806.mbox/browser] [3] [https://github.com/apache/airavata/tree/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/task/parsing] [4] [https://github.com/apache/airavata/blob/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/workflow/ParserWorkflowManager.java] [5] [https://github.com/apache/airavata/blob/develop/thrift-interface-descriptions/airavata-apis/airavata_api.thrift#L3505] [6] https://github.com/apache/airavata/blob/develop/thrift-interface-descriptions/data-models/app-catalog-models/parser_model.thrift [7] [https://helix.apache.org/0.8.4-docs/tutorial_task_framework.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRAVATA-2999) [GSoC] Administration Dashboard for Airavata Services
[ https://issues.apache.org/jira/browse/AIRAVATA-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Marru updated AIRAVATA-2999: --- Labels: gsoc2019 (was: ) > [GSoC] Administration Dashboard for Airavata Services > - > > Key: AIRAVATA-2999 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2999 > Project: Airavata > Issue Type: New Feature >Reporter: Dimuthu Upeksha >Priority: Major > Labels: gsoc2019 > > Typical Apache Airavata deployment consists of multiple microservices (API > Server, Participant, Controller, Pre Workflow Manager, Post Workflow Manager, > Job Monitors and etc) and several other services (Database, Kafka, RabbitMQ, > Keycloak, Zookeeper, Apache Helix). As it is a deployment with multiple > components, when it comes to an issue, it is time consuming to find which > component is having the problem. So we need an Administration Dashboard which > can visualize the system health and provide some handle to administrators to > control those services like stopping or restarting each component through the > dashboard. > Additionally, this dashboard should be able to authenticate users through > Keycloak which is the identity provider for Airavata and only system > administrators should be given access to those operations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AIRAVATA-3000) [GSoC] Refactor parser framework into a generic workflow framework
[ https://issues.apache.org/jira/browse/AIRAVATA-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Marru updated AIRAVATA-3000: --- Labels: gsoc2019 (was: ) > [GSoC] Refactor parser framework into a generic workflow framework > -- > > Key: AIRAVATA-3000 > URL: https://issues.apache.org/jira/browse/AIRAVATA-3000 > Project: Airavata > Issue Type: New Feature >Reporter: Dimuthu Upeksha >Priority: Major > Labels: gsoc2019 > > This an extension of the work we have done in GSoC 2018. Yasas has worked on > developing a workflow framework for Airavata and his mail list discussions > and medium post can be found from [1] [2]. Based on his research and the > another GSoC project which was done in integrating a parser framework for > Airavata, we have developed a new parser framework [3] [4] [5] [6] which > utilized Apache Helix task framework [7] as the task execution engine. > Even though this framework was specifically developed for parsers, we feel > that this implementation shares a lot of common features of the workflow > design which Yasas has worked on. So in this project we need to generalize > parser framework into a generic workflow framework where we can create and > launch workflows with any application registered in Airavata > Student should be good at Java and distributed system concepts > Key Expectations > # Refactor/ improve parser data models into workflow data models > # Refactor/ improve parser tables into workflow database tables > # Implement new helix tasks to support workflow operations mentioned in [2] > # Refactor/ improve parser API into a workflow level API [5] > # Demonstrate that we can still preserve parser workflows in newly created > generic workflow engine (This will be final demo). > [1] > [https://medium.com/@yasgun/gsoc-2018-with-apache-airavata-user-defined-airavata-workflows-39f0e79234ee] > [2] > [http://mail-archives.apache.org/mod_mbox/airavata-dev/201806.mbox/browser] > [3] > [https://github.com/apache/airavata/tree/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/task/parsing] > [4] > [https://github.com/apache/airavata/blob/develop/modules/airavata-helix/helix-spectator/src/main/java/org/apache/airavata/helix/impl/workflow/ParserWorkflowManager.java] > [5] > [https://github.com/apache/airavata/blob/develop/thrift-interface-descriptions/airavata-apis/airavata_api.thrift#L3505] > [6] > https://github.com/apache/airavata/blob/develop/thrift-interface-descriptions/data-models/app-catalog-models/parser_model.thrift > [7] [https://helix.apache.org/0.8.4-docs/tutorial_task_framework.html] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
