May DevOps Infrastructure and Automation (3/3)

[elisabettai]

Description:
Develop DevOps infrastructure empowering users to perform more monitoring and troubleshooting tasks themselves, thus facilitating debugging and reducing the required SIM-Core manpower in the longer run.
Foreseen functionality includes:

• Provide increased automation for the following routine DevOps tasks:

  • Better organization of docker images in registry (validation of metadata, deletion of faulty images)
  • Simplification of interaction with database to have command line tools for:
    • bulk add/remove/upgrade access rights to services for a user/group
    • bulk remove/add/upgrade services from projects
    • automate resource limits assignment for users based on service and user/group-id (also relates to API extensions & computational backend refactoring discussed above)
  • Information on which users have currently which studies open
  • Development of tools to collect resource usage (compute & storage) information for potential billing (part of sustainability plans) based on
    • services
    • user groups
  • Housekeeping: Detecting stale (old/unused) user accounts and proactively find corrupt projects/services and unused data for clean-up by DevOps

• Web-Application Monitoring: Automatic collection of metrics upon any unexpected failures and nascent bugs, which will be used to assess the user-experience during our development cycles. This will help to assess if user experience degrades or improves and how much time for maintenance is required flexibly. There is no need to rely only on traditional, mostly slow feedback cycles (such as dissatisfied users’ email feedback)

Deliverable:
Extended DevOps infrastructure: housekeeping, simplification of interaction with database, web-application monitoring

Acceptance criteria:
Infrastructure is in place that provides increased DevOps automation and web-application monitoring

Out of scope: –

Deadline:
Q1

wrike Y7-MS 7.1.3: DevOps Infrastructure and Automation (3/3)

[SCA-ZMT]

Prepare for review.

[elisabettai]

I am writing this up for the NIH reporting.

I am sure there's a lot we're done for "housekeeping, simplification of interaction with database, web-application monitoring"

We can for sure mention the new dashboards on Graphana to monitor running machines, right @YuryHrytsuk @sanderegg? Do you have more details that we can share?

Something about interaction with the DB? Maybe we can mention scripts or other tools that we used to migrate TIP to AWS? @matusdrobuliak66

Anything else for housekeeping @mrnicegyu11?