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

Status Update:

• V5 (Doctrine): Aiming to release a test version in next few weeks to test main PI methods (PI now nearly reproduced using Doctrine DB).

• New AAI layer for abstracting different authentication mechanisms integrated into v5 (e.g. x509, un/pw - loosely based on Spring Security3).

• Service type request in progress (‘ARC-CE’ to ‘org.nordugrid.arex’).

• GOCDB Mini-project: Scoping Enhancements + Management Interface.

• GLUE2 XML rendering opened for public comment at OGF 37 (12th March)

• Will be adopted by new GOCDB PI methods (planned)

• Existing PI methods largely unchanged except for the PK changes described at: https://wiki.egi.eu/wiki/Doctrine

• Additional failover to be hosted at Daresbury Labs (UK)

• Hardware found, in prep.


RT Requirements Analysis:

V5 Release (end ~May):

• Support for other RDBMS: https://rt.egi.eu/rt/Ticket/Display.html?id=4516

Number of smaller issues will be addressed in v5 release:

• Output of get_downtime method (https://rt.egi.eu/rt/Ticket/Display.html?id=1017)

• Add link to GOCDB roc object in XML results of 'get_roc_contacts’ (https://rt.egi.eu/rt/Ticket/Display.html?id=1423)

• Blank Roles due to deleted users: (https://rt.egi.eu/rt/Ticket/Display.html?id=4642)

• Use scope pull-down consistently across Site/SE views: https://rt.egi.eu/rt/Ticket/Display.html?id=4466

• Hide EGI Visibility (Scopes for EUDAT)

https://rt.egi.eu/rt/Ticket/Display.html?id=4595


Post v5 release:

• Add new REST (PI) method to programmatically insert downtimes, EUDAT+PRACE? (https://rt.egi.eu/rt/Ticket/Display.html?id=4935)

• GLUE2 XML Rendering (https://rt.egi.eu/rt/Ticket/Display.html?id=4517)

• Multiple Endpoints per Service: (https://rt.egi.eu/rt/Ticket/Display.html?id=3347)

• Mini-project: Scoping enhancements + Management interface.

3.2.3 GGUS

Status Update: GGUS release 2013-02-27

  • GGUS web interface
    • New "Did you know?" Title: Ticket relation in GGUS
    • Explaining status “waiting for reply”
    • Decommission of the software release dashboard
  • GGUS structure
    • Decommission VO «demo.vo.edges-grid.eu»
    • Decommission VO «ict.vo.ibergrid.eu»
  • Interfaces to other systems
    • Implement interface GGUS - IBERGRID RT
    • Renew certificate of NGI_PL interface
    • Renew certificate of NGI_IT interface
  • Mail issues
    • Migration of GGUS mail boxes to new infrastructure - Part 2
    • Moved ggus.org domain from old mail infrastructure to new infrastructure
  • Reporting
    • GGUS RG: RG deviation of figures from manual reports
    • GGUS RG: Implement SLA report "open tickets by priority

GGUS next release 2013-03-27 Items for next release are not yet defined, open items are recorded at:

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