You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
In the future, it will be necessary for sustainability purposes to attribute (and charge) resource usage costs to commercial users, users exceeding the limits of the free usage tier, or whatever the adopted sustainability model foresees. This potentially includes compute time, simulation hours and S3 storage per user, as well as egress costs for download of files through the API. A cost explorer with detailed information about spent simulation hours (see DevOps infrastructure & automation regarding the collection of such information) and remaining credits will be established. This functionality can in the future be linked to a website to purchase additional simulation hours.
Deliverable:
Usage tracking and charging Infrastructure
Acceptance criteria:
User resource usage can be tracked and presented to the user, and infrastructure is in place to permit charging users for their resource costs (likely in the form of prepayment, i.e., buying credit)
elisabettai
changed the title
Sep Pay Per Use – Usage Tracking and Charging Infrastructure
Nov Pay Per Use – Usage Tracking and Charging Infrastructure
Sep 11, 2023
@pcrespov, this is related to the milestone for NIH.
Reading the "Acceptance criteria", I'd say that we have resource usage well tracked and presented to the user, and we're able to attribute/charge users (as we're doing since the internal launch).
Do you still see any important detail missing to consider this completed?
I checked the related WP10, and this seems the only detail missing: ITISFoundation/osparc-simcore#5057. Is this very critical for the overall functionality?
Do you still see any important detail missing to consider this completed? I checked the related WP10, and this seems the only detail missing: ITISFoundation/osparc-simcore#5057. Is this very critical for the overall functionality?
@elisabettai Yes, I agree. This is completed. The issue you point is a last enhancement and will in addition be closed in the coming days.
Description:
In the future, it will be necessary for sustainability purposes to attribute (and charge) resource usage costs to commercial users, users exceeding the limits of the free usage tier, or whatever the adopted sustainability model foresees. This potentially includes compute time, simulation hours and S3 storage per user, as well as egress costs for download of files through the API. A cost explorer with detailed information about spent simulation hours (see DevOps infrastructure & automation regarding the collection of such information) and remaining credits will be established. This functionality can in the future be linked to a website to purchase additional simulation hours.
Deliverable:
Usage tracking and charging Infrastructure
Acceptance criteria:
User resource usage can be tracked and presented to the user, and infrastructure is in place to permit charging users for their resource costs (likely in the form of prepayment, i.e., buying credit)
Out of scope:
Webpage for purchasing resources
Deadline:
Q1
wrike Y7-MS 7.2: Pay Per Use – Usage Tracking and Charging Infrastructure
The text was updated successfully, but these errors were encountered: