Alert.png 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.

EGI-InSPIRE:Jra1 2013-05-07

From EGIWiki
Jump to navigation Jump to search

<< 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.

3. Major work done during the past week by task

3.1 TJRA1.1

- MS710 External Review

- D7.3

- JRA1 meeting: https://indico.egi.eu/indico/conferenceDisplay.py?confId=1344

- Analysis on JRA1 tasks effort used versus plan with data coming from QR11

- Analysis of the MiniProjects proposals VAPOR and GOCDB Scoping Extensions and Management Interface

3.2 TJRA1.2 TJRA1.3 TJRA1.5

3.2.1 SAM

SAM U20: WLCG experiments completed the validation last week. Therefore we are going to update our central installation.

SAM U21 ongoing: integration of the EMI probes

RT2791: It can be supported without any major modifications to SAM given that GOCDB provides a link that would list both locally and globally scoped services for a given region.

3.2.2 GOCDB

3.2.3 GGUS

3.2.4 Ops Portal

3.2.5 Accounting Portal

3.2.6 Metrics Portal

3.3 TJRA1.4 (Accounting for new resource types)

4. Next Meetings