-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
personalizable resource limits #618
personalizable resource limits #618
Comments
To avoid overscheduling of nodes, services should be scheduled with minimal resource requirements. In order not to limit "power users", those requirements can be dynamically be overwritten by users via the osparc user interface. Possibility to override is tied to users/group permissions. |
Update on sprint MacaronsDone
Todo
|
Update on sprint CroissantDone
OngoingOpen
|
@mguidon, could something be done this sprint to prevent the case MS was hitting see this message in Mattermost? For the POs this is still very important and needed for s4l upcoming releases. |
Hi. Strictly speaking, personalized resources are not required for s4l:web:lite. Melanies problem is related to her using a very outdated legacy service (with strict resource limits of outrageous 96 GB RAM) and her needing more RAM than the default one for the newer version (16GB). |
Update on sprint MithrilDone |
Some notescurrent implementation
If the user need to dynamically change a service resources I see the following requirements:
|
Goal for sprint Jelly BeansWrite down in details how this will be surfaced to the users
Potential first use case: |
Update on sprint Jelly BeansTowards user-defined resources on services plan1. Running a service with dynamically changed resources
2. administrator access to a service default resources
3. sharing a study
Use-case:
after discussion with @mguidon the idea is to go with 1. first and wait with 2. until capabilities of dynamic clusters are better defined. 3. could be implemented once 1. is done. |
|
|
Update for sprint Pastel de NataOngoing |
To avoid overscheduling of nodes, services should be scheduled with minimal resource requirements. In order not to limit "power users", those requirements can be dynamically be overwritten by users via the osparc user interface. Possibility to override is tied to users/group permissions.
(computational backend for now, also keep in mind #576)
Tasks
Sundae
The text was updated successfully, but these errors were encountered: