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.

Difference between revisions of "EGI-InSPIRE:Jra1 2013-05-07"

From EGIWiki
Jump to navigation Jump to search
 
(40 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{Template:EGI-Inspire menubar}}
[[Category:EGI-InSPIRE]]
[[Inspire_JRA1_weekly_reports| << JRA1 weekly reports main page]]  
[[Inspire_JRA1_weekly_reports| << JRA1 weekly reports main page]]  


Line 4: Line 6:


== 1. Progress on Milestones Deliverables  ==
== 1. Progress on Milestones Deliverables  ==
* Periodic Report


MS710 - Operational Tools Roadmap
PTs input collected. JRA1 contribution completed by this week.


An updated version of the document satisfying reviewers’ comments has been uploaded in the document server: https://documents.egi.eu/secure/ShowDocument?docid=1501
* MS710 - Operational Tools Roadmap


Final version available at: https://documents.egi.eu/document/1501


D7.3 - Annual Report on Operational Tool maintenance and development activity
* 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.
Final version available at: https://documents.egi.eu/secure/ShowDocument?docid=1562
 
The first draft will be available by this week.


== 2. Critical Issues  ==
== 2. Critical Issues  ==
 
* GOCDB issue: John Casson left the GOCDB team. This will delay the release of GOCDB v5. The delay should be in order of 2 months (v5 was expected for May/early June).
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. Major work done during the past week by task  ==


=== 3.1 TJRA1.1  ===
=== 3.1 TJRA1.1  ===
 
* Periodic Report
- MS710 External Review
* Metrics computation
 
* JRA1 monthly meeting preparation
- D7.3
* JRA1 action review
 
- 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 TJRA1.2 TJRA1.3 TJRA1.5  ===


==== 3.2.1 SAM  ====
==== 3.2.1 SAM  ====
 
* Final version of EGI QR12
SAM U20: WLCG experiments completed the validation last week. Therefore we are going to update our central installation.
* Next SAM Update ongoing
 
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.2 GOCDB  ====
* Hardware installation for new gocdb-failover at Daresbury labs.
* Initial review of JC's v5 code.
* Mentoring our new GOCDB mini-project developer.


==== 3.2.3 GGUS  ====
==== 3.2.3 GGUS  ====
* Ticket monitoring
* Preparation of the next GGUS release
* Cleaning up support units after end of EMI project
* Defining new structure of PTs


==== 3.2.4 Ops Portal  ====
==== 3.2.4 Ops Portal  ====
* Refactoring of the VO ID cards (bootstrap + Jquery)


==== 3.2.5 Accounting Portal  ====
==== 3.2.5 Accounting Portal  ====
* Continuing refactor of the code
* Changes for new accounting.


==== 3.2.6 Metrics Portal  ====
==== 3.2.6 Metrics Portal  ====
* Work for QR12


=== 3.3 TJRA1.4 (Accounting for new resource types)  ===
=== 3.3 TJRA1.4 (Accounting for new resource types)  ===
==== Accounting Repo ====
* EMI 3 APEL client update released, first site now publishing in production
* Regional APEL Server documentation/links to code sent to additional site (Taiwan) for testing.
==== Accounting Portal ====
* Cloud accounting fixes


== 4. Next Meetings  ==
== 4. Next Meetings  ==
 
* Next JRA1 meeting: 13 May 2013
[[Category:JRA1_weekly_report]]

Latest revision as of 10:18, 6 January 2015

EGI Inspire Main page

<< JRA1 weekly reports main page


1. Progress on Milestones Deliverables

  • Periodic Report

PTs input collected. JRA1 contribution completed by this week.

  • MS710 - Operational Tools Roadmap

Final version available at: https://documents.egi.eu/document/1501

  • D7.3 - Annual Report on Operational Tool maintenance and development activity

Final version available at: https://documents.egi.eu/secure/ShowDocument?docid=1562

2. Critical Issues

  • GOCDB issue: John Casson left the GOCDB team. This will delay the release of GOCDB v5. The delay should be in order of 2 months (v5 was expected for May/early June).

3. Major work done during the past week by task

3.1 TJRA1.1

  • Periodic Report
  • Metrics computation
  • JRA1 monthly meeting preparation
  • JRA1 action review

3.2 TJRA1.2 TJRA1.3 TJRA1.5

3.2.1 SAM

  • Final version of EGI QR12
  • Next SAM Update ongoing

3.2.2 GOCDB

  • Hardware installation for new gocdb-failover at Daresbury labs.
  • Initial review of JC's v5 code.
  • Mentoring our new GOCDB mini-project developer.

3.2.3 GGUS

  • Ticket monitoring
  • Preparation of the next GGUS release
  • Cleaning up support units after end of EMI project
  • Defining new structure of PTs

3.2.4 Ops Portal

  • Refactoring of the VO ID cards (bootstrap + Jquery)

3.2.5 Accounting Portal

  • Continuing refactor of the code
  • Changes for new accounting.

3.2.6 Metrics Portal

  • Work for QR12

3.3 TJRA1.4 (Accounting for new resource types)

Accounting Repo

  • EMI 3 APEL client update released, first site now publishing in production
  • Regional APEL Server documentation/links to code sent to additional site (Taiwan) for testing.

Accounting Portal

  • Cloud accounting fixes

4. Next Meetings

  • Next JRA1 meeting: 13 May 2013