Difference between revisions of "EGI-InSPIRE:SA1.5-QR7"

From EGIWiki
Jump to: navigation, search
(Created page with '__NOTOC__ = 1. Task Meetings = <!-- Notes. Report here all task-specific meetings held. This includes (a) face-to-face meetings and (b) phone meetings. Make sure that for all tas…')
 
(2. Main Achievements: initial input)
Line 27: Line 27:
 
Note. This is a detailed account of progress over the previous quarter of activities within  the  task.  
 
Note. This is a detailed account of progress over the previous quarter of activities within  the  task.  
 
-->
 
-->
 +
Repository: Ran the production repository with no internal problems this quarter. There was one scheduled firewall outage of 45 minutes at RAL and a few very small network breaks which prevented the service receiving new data. This data would all have been received the next time the affected clients tried to publish. Total availability 99.97%.
 +
 +
Heavier support load than usual. Mainly due to rollout of CREAM CE and configuration errors during setup. It would be good to have second line support for APEL as for the other middleware. The APEL Team should only be providing third line support.
 +
 +
The planned production release of the new infrastructure slipped beyond the end of this quarter.
 +
 +
There is 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. All of the other existing and new accounting services have tested using SSM except SGAS where the developer has moved on and has not yet been replaced.
  
 
= 3. Issues and Mitigation =
 
= 3. Issues and Mitigation =

Revision as of 18:11, 20 February 2012

1. Task Meetings

Date (dd/mm/yyyy) Url Indico Agenda Title Outcome

2. Main Achievements

Repository: Ran the production repository with no internal problems this quarter. There was one scheduled firewall outage of 45 minutes at RAL and a few very small network breaks which prevented the service receiving new data. This data would all have been received the next time the affected clients tried to publish. Total availability 99.97%.

Heavier support load than usual. Mainly due to rollout of CREAM CE and configuration errors during setup. It would be good to have second line support for APEL as for the other middleware. The APEL Team should only be providing third line support.

The planned production release of the new infrastructure slipped beyond the end of this quarter.

There is 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. All of the other existing and new accounting services have tested using SSM except SGAS where the developer has moved on and has not yet been replaced.

3. Issues and Mitigation

Issue Description Mitigation Description

4. Plans for the next period