Status of the accounting repository activities - Monday 10th of October 2016

Attendees:
- STFC/APEL: Adrian and John
- EGI Foundation: Peter, Alessandro and Diego

A) Cloud  Accounting:  Usage  Record V0.4.
- Production repository to be updated Oct 12-13
- Probes in the cloud sites need to be updated to the latest version
- Summary to the portal to be updated

1. Action on Adrian (deadline ASAP): Check if the APEL probes are aligned with the UR V0.4. Communicate the release number to EGI Operations that will coordinate the update if needed
2. Action on Adrian (deadline ASAP): Check with the EGI FedCloud Cloud Management Framework teams which values of the UR V0.4 are correctly filled in and which not
3. Action on Adrian (deadline ASAP): Update the summary report for the portal to allow Ivan to include the new values in the cloud views
4. Action on Peter (depends on action 1): organise the deployment of the new APEL client in the EGI FedCloud

B) Long Running VMs:
- Production repository to be updated Oct 12-13
- Transparent change for sites and portal
- Potential issues on the portal related to not cumulative metrics (e.g. Number of VMs running in a month): 1 VM could be counted more time

6. Action on John (deadline ASAP): discuss with Ivan of the potential issues and propose some solutions

C) ARC Parser:
- Low priority

D) Storage Accounting: Usage Record V2.0 and Production deployment
- Problems fixed. We could start to collect records again. We need to chase RPs to publish information.
- Documentation available at https://wiki.egi.eu/wiki/APEL/Storage
- Testing values available in the dev version of the old accounting portal: http://accounting-devel.egi.eu/storage.php

7. Action on Peter (deadline ASAP): identify new RPs willing to test this new feature

E) XML parser:
- Low priority

F) Data Accounting:
- New usage record to be defined according to the comments received.
- Add an "Orcid ID" field in the data accounting usage record for future aims. This field will contain the Orcid ID of the user that accessed, stored, updated the data.
- D3.8 First data accounting prototype to be sent to the EC by Oct 31

8. Action on Adrian (deadline ASAP): define the new usage record accordingly to the comments received. Include the Orcid ID field
9. Action on Diego (depends on action 8.): share the draft usage record with all the communities involved in requirements gathering
10. Action on Diego (depends on action 9.): contact the OneData team to check if all the attributes are available in the internal OneData tracking system
11. Action on Adrian (deadline Oct 27): deliverable ready to go into external review. The deliverable should be available some days before the deadline to run an internal review. External review will run during Adrian's holiday (2 weeks). Deliverable to be finalised in the second half of November.
12. Action on Diego (deadline ASAP): inform AMB about the delay on completing D3.8

G) Investigating Big Data tools to improve accounting repository according to the schedule defined in D3.6
(https://documents.egi.eu/public/ShowDocument?docid=2667) 
- currently no work has been done to test the different deployments. Big delay. According to the schedule in D3.6 all the deployments should be tested by end of 2016.

13. Action on Adrian (deadline ASAP): provide an update schedule for testing the different deployments.