Migrate projects where override service specifications are necessary

[sanderegg]

When new personalized resource limits feature reaches production, the projects needing overriden service resources shall be migrated. (PR #4449)

Specific users have specific service specifications. They currently start every single services using these specifications which is a huge waste of resources. These overrides shall be disabled and the specific users shall adapt their projects to have resources defined per service in the project directly.

This will be impacting TN, MS, Fariba and Anto.

Tasks

Preview Give feedback

1. list all overrides
2. allow supersusers to override resources
3. evaluate TVB devs needs
4. remove unnecessary overrides

[sanderegg]

current state

dalco-prod

• none

dalco-staging

• cassara: s4l-core-dy:2.0.16
• msteiner: jupyter-smash:3.0.3

AWS-staging

• cosimo: jupyter-smash:3.0.1

AWS-prod

• s4lliteusers: s4l-core-lite:2.0.84
• s4lliteusers: sim4life-lite:2.0.84
• s4lliteusers: s4l-core-stream:2.0.97
• s4lliteusers: sym-server-dy:2.0.84
• everyone: jupyter-smash-voila:2.5.5
• tvb devs: osparc-python-runner:1.2.0

[sanderegg]

Update Sundae

Done:

Fariba: can change limits on dalco-prod/AWS-prod
@newton1985 : can change limits on dalco-prod/dalco-staging/AWS-staging/AWS-prod
MS: can change limits on dalco-prod/dalco-staging/AWS-prod

Open:

• check with AC for his usage in dalco-staging
• check with CF/MaG for his usage in aws-staging
• TVB devs: evaluate needs
• remove all fixed overrides

[sanderegg]

dalco-staging: all entries removed. not a production deployment.
AWS-staging: all entries with overrides are gone.
AWS-production: kept entries, to be discussed.

[sanderegg]

this is now supposedly ok.