|EGI Inspire Main page|
|Inspire reports menu:||Home •||SA1 weekly Reports •||SA1 Task QR Reports •||NGI QR Reports •||NGI QR User support Reports|
1. Task Meetings
|Date (dd/mm/yyyy)||Url Indico Agenda||Title||Outcome|
||Accounting Workshop at EGI TF||https://www.egi.eu/indico/materialDisplay.py?sessionId=71&materialId=minutes&confId=452|
|22/9/2011||https://www.egi.eu/indico/sessionDisplay.py?sessionId=89&confId=452#20110922||Workshop at EGI TF on New Types Of Accounting.||https://www.egi.eu/indico/getFile.py/access?contribId=361&sessionId=89&resId=0&materialId=minutes&confId=452|
2. Main Achievements
Repository: Ran the production repository with no internal problems this quarter. There was one unscheduled network break of seven hours at RAL and a few very small firewall scheduled outages which prevented the service receiving new data. This data would all have been received the next time the affected clients tried to publish.
Much support work has been with sites who have been publishing the wrong SPECInt value for part of all of their cluster. Others needed to change the java memory limits or required support in order to republish data after they had made configuration changes.
All the APEL team attended the EGI Technical Forum. Although our main interaction was in JRA1 workshops there was much useful networking on production issues.
There is now a test repository running all the time to receive tests from other sites developing their software against SSM the new STOMP and Python-based messaging layer which runs on the production EGI Messaging Infrastructure. The team engaged with developers from Unicore, ARC, and IGE in a series of phone calls and meetings to discuss how they will publish accounting data to the central repository. Progress was made in each of these. John Gordon and Will Rogers attended the EMI AHM to describe the EGI Accounting Infrastructure and propose that they publish accounting into it. Portal: Release of version Canopus (v4.0). The service ran smoothly.
The new version uses a new codebase and versioning system, with GGUS referenced commits.
URL simplification and rewriting support.
New pchart 2.0 graph engine.
New FQAN support on vo manager and site views.
Many bug fixes and minor enhancements.
3. Issues and Mitigation
|Issue Description||Mitigation Description|
4. Plans for the next period
Start a production service receiving summaries from other accounting services over SSM and joining them with the old summary system. Once all systems have migrated the old database will be migrated to a new one and the old clients piped into that. This second step is likely to be in Q8.