Operations

[elisabettai]

Description: Continuous work is expected regarding:

• status monitoring and maintenance of the platform (includes as well monitoring of AWS, storage); improvement of the monitoring infrastructure
• platform testing, e.g., adding automatic tests for new services / functionality
• bug fixing of reported issues (internal and external) and issues arising from continuous development of the platform

Deliverable: Continuous operations activity (updates in each NIH SIM-Core Update meeting)

Deadline: Continuous task

wrike Y7–(Task) 9c: Operations

[elisabettai]

@mrnicegyu11, @YuryHrytsuk, is there something we could highlight next week at the NIH review?

[elisabettai]

Y7Q3 Status update (05/28/2024): Continuously Ongoing Implementation: Summary of key work performed during Q3, which was presented in parts to the NIH at the monthly update meeting on 03/27/2024 (see slides and minutes).

• Releases: during the reporting period, there were 15 releases to the staging deployment (osparc-stating.io) and 7 to production (osparc.io, including some “hot-fixes”)
• Speed up of testing and release pipelines for the operation microservices (CI/CD for devops); as a result the pipeline execution time was reduced from 28 to 6 minutes
• A first complete migration of a full o²S²PARC deployment has been completed for the Temporal Interference Planning Tool tip.swiss. It was moved from an in-house cluster to the ZMT AWS account. The developed infrastructure, including migration scripts, will serve as basis for migrating osparc.io to a new deployment after the STRIDES account runs out.
• Refactoring of Docker networks to increase platform stability (e.g. to avoid temporary timeouts between platform microservices)
• Finalization of migration to Terraform (i.e. transitioning to an “infrastructure as code” paradigm). This permits to create backups of the cloud architecture. Each platform component is documented as code.