Closed elisabettai closed 1 year ago
From NIH June meeting: deadline is now Q4
As discussed, we can close this once we're able to track resources from director-v2. This will enable tracking all services (and not only jupyter-smash).
@matusdrobuliak66, @mrnicegyu11 please correct if this is wrong. I am following up progress for this in https://github.com/ITISFoundation/osparc-issues/issues/922, but I will need to figure out which tasks from there will close this one.
As discussed, we can close this once we're able to track resources from director-v2. This will enable tracking all services (and not only jupyter-smash).
@matusdrobuliak66, @mrnicegyu11 please correct if this is wrong. I am following up progress for this in #922, but I will need to figure out which tasks from there will close this one.
You are correct, basically, most of the tasks that are currently in the Sundae task list (all that are connected with RabbitMQ, publishing messages from director-v2, and receiving/storing messages somewhere in resource-usage-tracker) are needed to track the usage.
The question I have here is, what is the outcome/goal of this milestone? The outcome of the second one is to track the user credits based on which you are able to bill. What is the goal here, is it the same?
Done:
In progress:
Todo:
Done:
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. Usage tracking and attribution functionality shall be developed that permits to attribute storage and computational resource costs to and preparation for cost attribution to paying users.
Deliverable: Functionality to track and attribute o²S²PARC resource usage Deadline: Month 8
Wrike M7.1.2