The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "EGI-InSPIRE:Jra1 2013-05-07"
| Line 21: | Line 21: | ||
Until now, according to the users requirements received, TJRA1.4 concentrated its effort on: | Until now, according to the users requirements received, TJRA1.4 concentrated its effort on: | ||
- Accounting of Cloud resources | - Accounting of Cloud resources | ||
- Accounting of Storage resources | - Accounting of Storage resources | ||
| Line 27: | Line 29: | ||
According to the DoW (see page 88) other two activities should be performed by TJRA1.4 by the end of the project: | According to the DoW (see page 88) other two activities should be performed by TJRA1.4 by the end of the project: | ||
- Billing: integrate a billing function onto the accounting repository enabling different resource usage to be accounted for and a bill generated. | - Billing: integrate a billing function onto the accounting repository enabling different resource usage to be accounted for and a bill generated. | ||
- Accounting of data usage: account the number of access for pricing or auding reasons. | - Accounting of data usage: account the number of access for pricing or auding reasons. | ||
About these activities we would like to know the AMB opinion on the following points: | About these activities we would like to know the AMB opinion on the following points: | ||
- If both the activities are still considered important requirements to be satisfied. | - If both the activities are still considered important requirements to be satisfied. | ||
- For the billing: we need as input the definition of the billing function. Moreover we should identify who is in charge of to define this function (PMB? AMB? Policies Group?) | - For the billing: we need as input the definition of the billing function. Moreover we should identify who is in charge of to define this function (PMB? AMB? Policies Group?) | ||
- For the accounting of data usage: we need a clear requirement coming from the communities interested. We can have this discussion at the OTAG but, probably, user communities potentially interested are not adeguately represented within the advisory group. | - For the accounting of data usage: we need a clear requirement coming from the communities interested. We can have this discussion at the OTAG but, probably, user communities potentially interested are not adeguately represented within the advisory group. | ||
Revision as of 12:51, 6 March 2013
<< JRA1 weekly reports main page
1. Progress on Milestones Deliverables
MS710 - Operational Tools Roadmap
An updated version of the document satisfying reviewers’ comments has been uploaded in the document server: https://documents.egi.eu/secure/ShowDocument?docid=1501
D7.3 - Annual Report on Operational Tool maintenance and development activity
TOC available on the document server: https://documents.egi.eu/secure/ShowDocument?docid=1562.
The first draft will be available by this week.
2. Critical Issues
1) TJRA1.4: the task is still under-reporting after QR11: 54% Worked PM/Committed PM (49% in QR10).
Until now, according to the users requirements received, TJRA1.4 concentrated its effort on:
- Accounting of Cloud resources
- Accounting of Storage resources
Moreover a first prototype for the Accounting of application usage has been developed.
According to the DoW (see page 88) other two activities should be performed by TJRA1.4 by the end of the project:
- Billing: integrate a billing function onto the accounting repository enabling different resource usage to be accounted for and a bill generated.
- Accounting of data usage: account the number of access for pricing or auding reasons.
About these activities we would like to know the AMB opinion on the following points:
- If both the activities are still considered important requirements to be satisfied.
- For the billing: we need as input the definition of the billing function. Moreover we should identify who is in charge of to define this function (PMB? AMB? Policies Group?)
- For the accounting of data usage: we need a clear requirement coming from the communities interested. We can have this discussion at the OTAG but, probably, user communities potentially interested are not adeguately represented within the advisory group.
2) A developer left the Ops Portal team the 1st of December. This could create the following problems:
- A final under-reporting on the TJRA1.5 (this task ends at the end of PY3);
- The complete release in production of the new portal could be delayed. The release will be probably done step by step - initiated with the new dashboard. The progress on this part will be also dependent from the integration of a new developer.