Reducing overhead costs by merging of o²S²PARC and Sim4Life deployment: After Y8, it will be desirable to merge the currently distinct o²S²PARC and Sim4Life deployments, to avoid duplication of infrastructure overhead (orchestration, storage, service catalog, authentication, monitoring, metrics scraping, dashboard, logging Services; web server, databases, testing infrastructure) and DevOps.
Successful migration requires: merging users, groups and organizations; merging S3 data, merging projects. These data and metadata "live" in different places (e.g., postgres, storage db, S3) and are strongly correlated. Carefully crafted scripts and APIs must be created to automate the process in a robust and reliable manner.
Deliverable
Revised platform deployment
Acceptance criteria:
o²S²PARC and Sim4Life share a common deployment
mrnicegyu11
commented
1 day ago
Description
Reducing overhead costs by merging of o²S²PARC and Sim4Life deployment: After Y8, it will be desirable to merge the currently distinct o²S²PARC and Sim4Life deployments, to avoid duplication of infrastructure overhead (orchestration, storage, service catalog, authentication, monitoring, metrics scraping, dashboard, logging Services; web server, databases, testing infrastructure) and DevOps. Successful migration requires: merging users, groups and organizations; merging S3 data, merging projects. These data and metadata "live" in different places (e.g., postgres, storage db, S3) and are strongly correlated. Carefully crafted scripts and APIs must be created to automate the process in a robust and reliable manner.
Deliverable
Revised platform deployment
Acceptance criteria: o²S²PARC and Sim4Life share a common deployment
Deadline
Y8Q4 (Aug.)
Wrike link (account/access required)