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:SA1.5-QR9"

From EGIWiki
Jump to navigation Jump to 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...")
 
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
__NOTOC__
{{Template:EGI-Inspire menubar}}
= 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 task meetings participants are ALWAYS recorded either on indico from the registrants’ list, or in the minutes.
OMB meeting will be reported under task TSA1.1 only. Monday Operations meetings need to be reported under task TSA1.3 only. Training events will be recorded in the training event registry and need not be mentioned here.
-->
{|  border="1" cellspacing="0" cellpadding="5" align="center"
! style="width: 25%" | Date (dd/mm/yyyy)
! style="width: 25%" | Url Indico Agenda
! style="width: 10%" | Title
! style="width: 10%" | Outcome
|-
|dd/mm/yyyy
|
|
|
|-
|}


{{Template:Inspire_reports_menubar}}
{{TOC_right}}
<h1> 1. Task Meetings  </h1>
<table cellpadding="5" border="1" align="center" cellspacing="0">


= 2. Main Achievements =
<tr>
<!--
<th style="width: 25%;"> Date (dd/mm/yyyy)
Note. This is a detailed account of progress over the previous quarter of activities within the  task.
</th>
-->
<th style="width: 25%;"> Url Indico Agenda
</th>
<th style="width: 10%;"> Title
</th>
<th style="width: 10%;"> Outcome
</th></tr>
<tr>
<td> No formal meetings this quarter
</td>
<td>
</td>
<td>
</td>
<td>
</td></tr></table>
<p><br />
</p>
<h1> 2. Main Achievements </h1>
<h2> Repository:  </h2>
<p>Ran the production repository with no internal problems this quarter. There were 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.
</p><p>CERN and OSG moved their production accounting to the new SSM infrastructure. For CERN’s job records summaries are made which are then merged with the summaries from the old system for transfer to the CESGA Portal. OSG send summaries and these too are merged. The test repository continues to run 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 done some testing using SSM, now including SGAS and GridSafe. Tests also received from CC-IN2P3, and ARC-JURA. Planning with Grid-Safe and MAPPER. EDGI should start next quarter.
</p><p>Participated in Inter-NGI Report Virtual Team. MPI Virtual Team, and the Federated Cloud Task Force. For this latter we continue to run a test cloud accounting database. This quarter we have five Resource Providers who have successfully sent in cloud accounting records, this is from OpenNebula and Openstack cloud middleware, previously we had only OpenNebula accounting records. (Client cloud accounting scripts have been provided by CESGA for OpenNebula and IN2P3 for Openstack.)
</p>
<h2> Portal </h2>
<p>As main ahievements on PQ9 for the accounting portal, there was miscellaneous query improvement and index optimization, better HTML output, testing with several browsers, tweaks on the graph engine, and other minor changes.</font>
</p><p>There was also preliminary work prior to the implementation of new interNGI usage features.<br />&#160;
</p>
<h1> 3. Issues and Mitigation </h1>
<table cellpadding="2" border="1" cellspacing="0">


= 3. Issues and Mitigation =
<tr>
<!-- fill the table below -->
<th scope="col"> Issue Description
 
</th>
{| border="1" cellspacing="0" cellpadding="2"
<th scope="col"> Mitigation Description
|-
</th></tr>
!scope="col"| Issue Description
<tr>
!scope="col"| Mitigation Description
<td>There was a bigger problem with a change to the EGI broker network after which APEL could not discover any brokers in the BDII. We put a manual fix in place the same day but it took some time more before the resource discovery worked. &#160;We still do not understand why this happened or how to mitigate future occurrences.
|-
</td>
|Issue description || Issue mitigation
<td> We are working with them both and hope to achieve this in the coming quarter.
|-
</td></tr></table>
|}
<h1> 4. Plans for the next period </h1>
 
Migrate the SGAS and DGAS feeds to SSM then flip the database to the new schema and pipe the existing client feeds into that. Implement summary feeds for external services, with CESGA as the main one. The production infrastructure will now be ready to receive data from the EMI3 client.   
= 4. Plans for the next period =
There will be an accounting workshop in the Technical Forum.
<!-- provide your text below -->
The next version of the portal will be released and the portal will work on accepting data by messaging.

Latest revision as of 19:04, 6 January 2015

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
No formal meetings this quarter


2. Main Achievements

Repository:

Ran the production repository with no internal problems this quarter. There were 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.

CERN and OSG moved their production accounting to the new SSM infrastructure. For CERN’s job records summaries are made which are then merged with the summaries from the old system for transfer to the CESGA Portal. OSG send summaries and these too are merged. The test repository continues to run 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 done some testing using SSM, now including SGAS and GridSafe. Tests also received from CC-IN2P3, and ARC-JURA. Planning with Grid-Safe and MAPPER. EDGI should start next quarter.

Participated in Inter-NGI Report Virtual Team. MPI Virtual Team, and the Federated Cloud Task Force. For this latter we continue to run a test cloud accounting database. This quarter we have five Resource Providers who have successfully sent in cloud accounting records, this is from OpenNebula and Openstack cloud middleware, previously we had only OpenNebula accounting records. (Client cloud accounting scripts have been provided by CESGA for OpenNebula and IN2P3 for Openstack.)

Portal

As main ahievements on PQ9 for the accounting portal, there was miscellaneous query improvement and index optimization, better HTML output, testing with several browsers, tweaks on the graph engine, and other minor changes.

There was also preliminary work prior to the implementation of new interNGI usage features.
 

3. Issues and Mitigation

Issue Description Mitigation Description
There was a bigger problem with a change to the EGI broker network after which APEL could not discover any brokers in the BDII. We put a manual fix in place the same day but it took some time more before the resource discovery worked.  We still do not understand why this happened or how to mitigate future occurrences. We are working with them both and hope to achieve this in the coming quarter.

4. Plans for the next period

Migrate the SGAS and DGAS feeds to SSM then flip the database to the new schema and pipe the existing client feeds into that. Implement summary feeds for external services, with CESGA as the main one. The production infrastructure will now be ready to receive data from the EMI3 client. There will be an accounting workshop in the Technical Forum. The next version of the portal will be released and the portal will work on accepting data by messaging.