[
https://issues.apache.org/jira/browse/AIRAVATA-3959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941699#comment-17941699
]
Ramya Vedi edited comment on AIRAVATA-3959 at 4/8/25 12:00 PM:
---------------------------------------------------------------
Hi Airavata team,
For my proposal(GSoC), I’ve containerized the Agent service with Docker and
MariaDB, running on ports 18880 (HTTP) and 9090 (gRPC). I used
`default-storage-id` for `airavata.storageResourceId` to resolve a config
error. My setup is below—can you advise on the correct value or source for this
property? Thanks!
Thanks,
Ramya Vedi[^docker-compose.yml]
was (Author: JIRAUSER308884):
Hi Airavata team,
For my proposal (due April 9th), I’ve containerized the Agent service with
Docker and MariaDB, running on ports 18880 (HTTP) and 9090 (gRPC). I used
`default-storage-id` for `airavata.storageResourceId` to resolve a config
error. My setup is below—can you advise on the correct value or source for this
property? Thanks!
Thanks,
Ramya Vedi[^docker-compose.yml]
> Containerized Deployment of Airavata Services
> ---------------------------------------------
>
> Key: AIRAVATA-3959
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3959
> Project: Airavata
> Issue Type: Wish
> Reporter: Yasith Jayawardana
> Priority: Major
> Labels: gsoc, gsoc2025, mentor
> Attachments: Dockerfile, docker-compose.yml
>
>
> Currently, all Airavata services are packaged and deployed as Java bundles.
> The goal is to containerize each service by wrapping it within a Dockerfile,
> allowing seamless deployment on container-enabled resources while also
> enabling local execution for development purposes.
> This enhancement has potential to improve deployment consistency, simplify
> dependency management, and provide greater flexibility in running Airavata
> services across different environments, for both testing and production use
> cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
