https://wiki.egi.eu/w/api.php?action=feedcontributions&user=Pkoro&feedformat=atomEGIWiki - User contributions [en]2024-03-28T11:03:29ZUser contributionsMediaWiki 1.37.1https://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=88277Resource Centres OLA and Resource infrastructure Provider OLA reports2016-06-15T07:31:07Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| [https://documents.egi.eu/document/2590 08/15]<br />
| [https://documents.egi.eu/document/2607 09/15]<br />
| [https://documents.egi.eu/document/2642 10/15]<br />
| [https://documents.egi.eu/document/2712 11/15]<br />
| [https://documents.egi.eu/document/2735 12/15]<br />
|-<br />
! 2016 <br />
| [https://documents.egi.eu/document/2755 01/16]<br />
| [https://documents.egi.eu/document/2781 02/16]<br />
| [https://documents.egi.eu/document/2797 03/16]<br />
| [https://documents.egi.eu/document/2830 04/16]<br />
| [https://documents.egi.eu/document/2844 05/16]<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=88126Resource Centres OLA and Resource infrastructure Provider OLA reports2016-06-09T10:00:07Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| [https://documents.egi.eu/document/2590 08/15]<br />
| [https://documents.egi.eu/document/2607 09/15]<br />
| [https://documents.egi.eu/document/2642 10/15]<br />
| [https://documents.egi.eu/document/2712 11/15]<br />
| [https://documents.egi.eu/document/2735 12/15]<br />
|-<br />
! 2016 <br />
| [https://documents.egi.eu/document/2755 01/16]<br />
| [https://documents.egi.eu/document/2781 02/16]<br />
| [https://documents.egi.eu/document/2797 03/16]<br />
| [https://documents.egi.eu/document/2830 04/16]<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=87174Resource Centres OLA and Resource infrastructure Provider OLA reports2016-04-21T07:25:26Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| [https://documents.egi.eu/document/2590 08/15]<br />
| [https://documents.egi.eu/document/2607 09/15]<br />
| [https://documents.egi.eu/document/2642 10/15]<br />
| [https://documents.egi.eu/document/2712 11/15]<br />
| [https://documents.egi.eu/document/2735 12/15]<br />
|-<br />
! 2016 <br />
| [https://documents.egi.eu/document/2755 01/16]<br />
| [https://documents.egi.eu/document/2781 02/16]<br />
| [https://documents.egi.eu/document/2797 03/16]<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=86697Resource Centres OLA and Resource infrastructure Provider OLA reports2016-03-24T11:16:49Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| [https://documents.egi.eu/document/2590 08/15]<br />
| [https://documents.egi.eu/document/2607 09/15]<br />
| [https://documents.egi.eu/document/2642 10/15]<br />
| [https://documents.egi.eu/document/2712 11/15]<br />
| [https://documents.egi.eu/document/2735 12/15]<br />
|-<br />
! 2016 <br />
| [https://documents.egi.eu/document/2755 01/16]<br />
| [https://documents.egi.eu/document/2781 02/16]<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=85938Resource Centres OLA and Resource infrastructure Provider OLA reports2016-02-22T13:32:32Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| [https://documents.egi.eu/document/2590 08/15]<br />
| [https://documents.egi.eu/document/2607 09/15]<br />
| [https://documents.egi.eu/document/2642 10/15]<br />
| [https://documents.egi.eu/document/2712 11/15]<br />
| [https://documents.egi.eu/document/2735 12/15]<br />
|-<br />
! 2016 <br />
| [https://documents.egi.eu/document/2755 01/16]<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=85937Resource Centres OLA and Resource infrastructure Provider OLA reports2016-02-22T13:32:14Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| [https://documents.egi.eu/document/2590 08/15]<br />
| [https://documents.egi.eu/document/2607 09/15]<br />
| [https://documents.egi.eu/document/2642 10/15]<br />
| [https://documents.egi.eu/document/2712 11/15]<br />
| [https://documents.egi.eu/document/2735 12/15]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2755 01/16]<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=85422Resource Centres OLA and Resource infrastructure Provider OLA reports2016-01-14T10:19:03Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| [https://documents.egi.eu/document/2590 08/15]<br />
| [https://documents.egi.eu/document/2607 09/15]<br />
| [https://documents.egi.eu/document/2642 10/15]<br />
| [https://documents.egi.eu/document/2712 11/15]<br />
| [https://documents.egi.eu/document/2735 12/15]<br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=85210Resource Centres OLA and Resource infrastructure Provider OLA reports2015-12-15T07:35:32Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| [https://documents.egi.eu/document/2590 08/15]<br />
| [https://documents.egi.eu/document/2607 09/15]<br />
| [https://documents.egi.eu/document/2642 10/15]<br />
| [https://documents.egi.eu/document/2712 11/15]<br />
| <br><br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Service_Level_Target_-_Availability_Reliability&diff=85054Service Level Target - Availability Reliability2015-12-02T07:36:32Z<p>Pkoro: /* Reports */</p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
<br> <br />
<br />
= Description =<br />
<br />
The ARGO service collects status results and computes daily and monthly availability (A) and reliability (R) metrics of distributed services. Both status results and A/R metrics are delivered through the ARGO Web UI, with the ability for a user to drill-down from the availability of a site to individual test results that contributed to the computed figure. <br />
<br />
== Components ==<br />
<br />
ARGO is comprised of the following building blocks: <br />
<br />
*'''The consumer.''' This service collects the metric results from the Message Broker Network (MBN) and delivers them to the compute engine in avro encoded format <br />
*'''The connectors.''' This is a collection of python modules that periodically connect to sources of truth (such as GOCDB for topology or downtimes, or POEM services for low level metric profiles etc) and deliver the information to the compute engine in avro encoded format. The period is set to daily. <br />
*'''The prefilter.''' This component is used by the ARGO compute engine in order to filter out results that may not be official (for example a non-authorative monitoring instance publishing results via the MBN) <br />
*'''The compute engine.''' Using the filtered data collected the compute engine is responsible for flattening out the metric results and for computing the services availability and reliability metrics. See next section for a more detailed description on how the computations are being performed. Results (status and A/R) are passed onto a fast, reliable and distributed datastore. <br />
*'''The REST API.''' This component serves all computed status and A/R results via a programmatic interface. <br />
*'''The Web UI.''' This component is based on the Lavoisier software. It is used in order to present the status and A/R results graphically and gives the ability to any given user to drill down from the availability of a given resource down to the actual metric results that were recorded and contributed to the computed figures.<br />
<br />
== Definitions ==<br />
<br />
=== Groupings of resources ===<br />
<br />
The definitions of entities (resources) are the following: <br />
<br />
*'''Service Endpoint:''' A service endpoint is defined as a hostname and service pair, so for example foo.example.com is a hostname, mysql is a service and a mysql database running on foo.example.com (i.e. foo.example.com:mysql) is a service endpoint. <br />
*'''Service Flavour''': A collection of same services (service endpoints). For example, multiple CREAM CEs in a site together make up the CREAM CE service flavour for the site. <br />
*'''Site:''' A collection of Service Flavours. A site can be made up of one or more service flavours. <br />
*'''NGI:''' A collection of Sites.<br />
<br />
=== Metrics and Statuses ===<br />
<br />
The following define the Metric and the Status, core building blocks of the algorithm used for A/R computations <br />
<br />
*'''Metric:''' A Metric is a functional test for a given service flavour. Within a given context (i.e. ROC_CRITICAL) each service flavour has a set of service metrics that verify its functionality and performance. This correlation between service flavour functionality and Metrics is given by the POEM service. Metric results are generated when monitoring (i.e. Nagios) tests are run on a particular service endpoint. <br />
*'''Status''': Status of a metric result, service, service endpoint, service flavour or a site is the status of that entity at a given point in time. (Note here that to go from metric result onto a site hierarchy some logic is being used in the background. This is discussed more in detail below.) Possible status values are <br />
**OK <br />
**WARNING <br />
**CRITICAL <br />
**UNKNOWN <br />
**MISSING <br />
**DOWNTIME<br />
<br />
These status values are mutually exclusive. The status of a resource can have only one value at a given point in time. <br />
<br />
=== Profiles ===<br />
<br />
There are three (3) types of profiles used within each A/R computation: <br />
<br />
*'''Metric profile:''' A profile defines which metrics are to be considered to compute the status of a service of a particular flavour. <br />
*'''Operations profile''': An operations profile defines how to aggregate status results from the metric level onto service endpoint and service flavour status results. In principal these define how ANDing and ORing operations are performed between status values. For example: <br />
**OK '''AND''' CRITICAL =&gt; CRITICAL <br />
**OK '''OR''' CRITICAL =&gt; OK <br />
*'''Aggregation profile:''' An aggregation profile defines how to aggregate service flavour statuses into site status results. As an example in the default Site A/R aggregation profiles service endpoints of the same type are ANDed to form the service flavor status (for example multiple CREAM-CE flavours are ANDed into one service flavour) while similar service flavours are ORed (for example CREAM-CE OR ARC-CE in the default profile)<br />
<br />
*'''Report''': Any given combination of one metric, one operations and one aggregation profile creates an ARGO report (see section reports below).<br />
<br />
<br> <br />
<br />
=== Time slices ===<br />
<br />
For computations of A/R results the ARGO compute engine uses 288 discrete samples on the daily timeline. The quantization of 288 values has been selected because it corresponds to a sampling frequency of 5mins. (24h * 60 = 1440 mins / 288 = 5mins). <br />
<br />
The compute engine performs computations on a daily base timeframe (even though the computations run per hour, actually ARGO performs the same daily computation with updated metric data). <br />
<br />
<br> <br />
<br />
== A/R Computation Algorithm ==<br />
<br />
The A/R results are produced by integrating status results according to metric, operations and aggregation profiles. So the compute engine needs to handle status results from metric data in an efficient way in order to algorithmically combine and integrate upon them. When the engine creates a daily timeline for a specific service endpoint and a specific metric it initiates a 288 item array reserved for the service endpoint and metric couple. <br />
<br />
[[Image:Empty sliced timeline.png|400px|Empty sliced timeline.png]] <br />
<br />
When metric data is collected for a specific metric (for a specific service endpoint) it is roughly in the following form: <br />
<br />
{ time_stamp | metric | service_flavour | hostname | status | vo | vofqan | profile | dates }<br />
<br />
The engine then gathers all relevant daily data for the specific service endpoint and metric. For example imagine that for a given day 5 distinct metric data for the hostname <tt>foo.example.com</tt>, the service <tt>mysql.service</tt> and the metric <tt>mysql.some.metric</tt>. The data rows for that day will be of the following form: <br />
<br />
{ time_stamp #1 | mysql.some.metric | mysql.service | foo.example.com | UNKOWN | vo | vofqan | profile | dates }<br />
{ time_stamp #2 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #3 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #4 | mysql.some.metric | mysql.service | foo.example.com | CRITICAL | vo | vofqan | profile | dates }<br />
{ time_stamp #5 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
The compute engine will also grab the last metric from the previous day timeline <br />
<br />
{ time_stamp #0 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
Based on the timestamp and status fields the compute engine will map these data points to the correct indexes of the metric array: <br />
<br />
[[Image:Init sliced timeline.png|400px|Init sliced timeline.png]] <br />
<br />
Afterwards the compute engine will fill in the gaps appropriately, like so: <br />
<br />
[[Image:Filled sliced timeline.png|400px|Filled sliced timeline.png]] <br />
<br />
When the engine needs to combine several different timelines in order to produce an aggregated timeline result (for example for a specific service flavor), it does the following: <br />
<br />
#Reserves a new array for the aggregation timeline <br />
#Aligns the relevant timeline arrays <br />
#Begins from index 0 and combines all array_items[0] to produce the aggregation_item[0] <br />
#Moves to next index<br />
<br />
The end result is an aggregated timeline: <br />
<br />
[[Image:Aggregated sliced timeline.png|400px|Aggregated sliced timeline.png]] <br />
<br />
*Aggregation of metric timelines into service endpoint timelines is based on the given metric profile used.. <br />
*Aggregation of service endpoint timelines into service flavour timelines is based on the given aggregation profile used. <br />
*Aggregation of service flavor timelines into group of endpoints (sites) is based also on the given aggregation profile used.<br />
<br />
In all cases AND and OR operations are based on the Operations profile used. <br />
<br />
It is important to note that the discrete handling of the status results as samples gives an easy and graceful way to implement aggregations. <br />
<br />
== Status Aggregation Algorithm ==<br />
<br />
Regarding status timelines and since there are no pre-established points in time shared by all timelines (like in sampling and A/R computations described above) the compute engine operates differently. <br />
<br />
If for example the compute engine is given 3 continuous status timelines that need to be aggregated a new timeline for the aggregation is reserved. <br />
<br />
[[Image:Empty status timeline.png|400px|Empty status timeline.png]] <br />
<br />
Then the points of interest (timestamps were status changes occur) are collected <br />
<br />
[[Image:Pois status timeline.png|400px|Pois status timeline.png]] <br />
<br />
and the compute engine slices the timeline accordingly <br />
<br />
[[Image:Sliced status timeline.png|400px|Sliced status timeline.png]] <br />
<br />
The compute engine then creates a number of chunks based on the points of interest found <br />
<br />
[[Image:Chunked status timeline.png|400px|Chunked status timeline.png]] <br />
<br />
And iteratively fills up the gaps progressively based on the profiles used in the given computation. <br />
<br />
[[Image:Aggr1 status timeline.png|400px|Aggr1 status timeline.png]] <br />
<br />
<br> [[Image:Aggr2 status timeline.png|400px|Aggr2 status timeline.png]] <br />
<br />
Once the filling up is completed the compute engine stitches back the complete aggregated timeline, like in the picture below: <br />
<br />
[[Image:Filled status timeline.png|400px|Filled status timeline.png]] <br />
<br />
= Reports =<br />
<br />
In the following subsections the metric and aggregation profiles used for each EGI report are given. <br />
<br />
The operations profile used in all of the subsequent EGI reports are given in the tabulars here:<br />
<br />
{| class="wikitable"<br />
|-<br />
| '''AND'''<br />
| '''OK'''<br />
| '''WARNING'''<br />
| '''UNKNOWN'''<br />
| '''MISSING'''<br />
| '''CRITICAL'''<br />
| '''DOWNTIME'''<br />
|-<br />
| '''OK'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''WARNING'''<br />
| WARNING<br />
| WARNING<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''UNKNOWN'''<br />
| UNKNOWN<br />
| UNKNOWN<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''MISSING'''<br />
| MISSING<br />
| MISSING<br />
| MISSING<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''CRITICAL'''<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
|-<br />
| '''DOWNTIME'''<br />
| DOWNTIME<br />
| DOWNTIME<br />
| DOWNTIME<br />
| DOWNTIME<br />
| CRITICAL<br />
| DOWNTIME<br />
|}<br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
| '''OR'''<br />
| '''OK'''<br />
| '''WARNING'''<br />
| '''UNKNOWN'''<br />
| '''MISSING'''<br />
| '''CRITICAL'''<br />
| '''DOWNTIME'''<br />
|-<br />
| '''OK'''<br />
| OK<br />
| OK<br />
| OK<br />
| OK<br />
| OK<br />
| OK<br />
|-<br />
| '''WARNING'''<br />
| OK<br />
| WARNING<br />
| WARNING<br />
| WARNING<br />
| WARNING<br />
| WARNING<br />
|-<br />
| '''UNKNOWN'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| UNKNOWN<br />
| CRITICAL<br />
| UNKNOWN<br />
|-<br />
| '''MISSING'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''CRITICAL'''<br />
| OK<br />
| WARNING<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
|-<br />
| '''DOWNTIME'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| DOWNTIME<br />
| CRITICAL<br />
| DOWNTIME<br />
|}<br />
<br />
<br />
<br />
<br />
<br />
== Sites A/R ==<br />
<br />
In the Sites A/R report the following metric profile is used: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| org.nordugrid.ARC-CE-ARIS <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-IGTF <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-result <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-srm <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-sw-csh <br />
| ARC-CE<br />
|-<br />
| emi.cream.CREAMCE-JobSubmit <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-Bi <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-Csh <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-SoftVer <br />
| CREAM-CE<br />
|-<br />
| hr.srce.CADist-Check <br />
| CREAM-CE<br />
|-<br />
| hr.srce.CREAMCE-CertLifetime <br />
| CREAM-CE<br />
|-<br />
| hr.srce.GRAM-Auth <br />
| GRAM5<br />
|-<br />
| hr.srce.GRAM-CertLifetime <br />
| GRAM5<br />
|-<br />
| hr.srce.GRAM-Command <br />
| GRAM5<br />
|-<br />
| hr.srce.QCG-Computing-CertLifetime <br />
| QCG.Computing<br />
|-<br />
| pl.plgrid.QCG-Computing <br />
| QCG.Computing<br />
|-<br />
| hr.srce.SRM2-CertLifetime <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Del <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Get <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-GetSURLs <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-GetTURLs <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Ls <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-LsDir <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Put <br />
| SRMv2<br />
|-<br />
| org.bdii.Entries <br />
| Site-BDII<br />
|-<br />
| org.bdii.Freshness <br />
| Site-BDII<br />
|-<br />
| emi.unicore.TargetSystemFactory <br />
| unicore6.TargetSystemFactory<br />
|-<br />
| emi.unicore.UNICORE-Job <br />
| unicore6.TargetSystemFactory<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Sites Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="8" | '''AND''' <br />
| rowspan="5" | Compute <br />
| rowspan="5" | '''OR''' <br />
| CREAM-CE<br />
|-<br />
| ARC-CE<br />
|-<br />
| GRAM5<br />
|-<br />
| unicore6.TargetSystemFactory<br />
|-<br />
| QCG.Computing<br />
|-<br />
| rowspan="2" | Storage <br />
| rowspan="2" | '''OR''' <br />
| SRMv2<br />
|-<br />
| SRM<br />
|-<br />
| Information <br />
| '''OR''' <br />
| Site-BDII<br />
|}<br />
<br />
<br> <br />
<br />
== NGI sites A/R ==<br />
<br />
For the NGI level aggregation all A/R results for sites belonging to the NGI are collected and aggregated dynamically weighted based on the HEPSPEC factor for each site. Hence larger sites contribute more to the overall NGI A/R and smaller sites less. <br />
<br />
=== Monthly League Tables ===<br />
<br />
Monthly EGI League Tables are accessible via the ARGO Web UI (Lavoisier) under the following link: '''<nowiki>http://argo.egi.eu/lavoisier/ngi_reports?month=YYYY-MM</nowiki>''' <br />
<br />
To get results for a specific month one should replace YYYY and MM with the calendar year and month respectively, hence to obtain results for August 2015 the link should be formatted as follows: http://argo.egi.eu/lavoisier/ngi_reports?month=2015-08 . <br />
<br />
Monthly Reports are also available at '''[[Resource Centres OLA and Resource infrastructure Provider OLA reports|'''Resource Centres OLA and Resource infrastructure Provider OLA reports wiki page''']] ''' <br />
<br />
== Core services A/R ==<br />
<br />
The Core service A/R report utilizes the following metric profile: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| org.activemq.OpenWireSSL <br />
| egi.APELRepository<br />
|-<br />
| org.nagiosexchange.AccountingPortal-WebCheck <br />
| egi.AccountingPortal<br />
|-<br />
| org.nagiosexchange.AppDB-WebCheck <br />
| egi.AppDB<br />
|-<br />
| org.nagiosexchange.GGUS-WebCheck <br />
| egi.GGUS<br />
|-<br />
| org.nagios.GOCDB-PortCheck <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GOCDB-PI <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GOCDB-WebCheck <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GSTAT-WebCheck <br />
| egi.GSTAT<br />
|-<br />
| org.activemq.Network-Topic <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.Network-VirtualDestination <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.OpenWire <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.OpenWireSSL <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.STOMP <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.STOMPSSL <br />
| egi.MSGBroker<br />
|-<br />
| org.nagiosexchange.MetricsPortal-WebCheck <br />
| egi.MetricsPortal<br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck <br />
| egi.OpsPortal<br />
|-<br />
| eu.egi.cloud.Perun-Check <br />
| egi.Perun<br />
|-<br />
| org.nagiosexchange.Portal-WebCheck <br />
| egi.Portal<br />
|-<br />
| ch.cern.sam.SAMCentralWebAPI <br />
| egi.SAM<br />
|-<br />
| org.nagiosexchange.TMP-WebCheck <br />
| egi.TMP<br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck <br />
| ngi.OpsPortal<br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosHostSummary <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosProcess <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosWebInterface <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosHostSummary <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosProcess <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosWebInterface <br />
| vo.SAM<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Core Services Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="15" | '''AND''' <br />
| gstat <br />
| '''OR''' <br />
| egi.GSTAT<br />
|-<br />
| vosam <br />
| '''OR''' <br />
| vo.SAM<br />
|-<br />
| ngisam <br />
| '''OR''' <br />
| ngi.SAM<br />
|-<br />
| egisam <br />
| '''OR''' <br />
| egi.SAM<br />
|-<br />
| brokering <br />
| '''OR''' <br />
| egi.MSGBroker<br />
|-<br />
| egiportal <br />
| '''OR''' <br />
| egi.Portal<br />
|-<br />
| egiopsportal <br />
| '''OR''' <br />
| egi.OpsPortal<br />
|-<br />
| egimetricsportal <br />
| '''OR''' <br />
| egi.MetricsPortal<br />
|-<br />
| registry <br />
| '''OR''' <br />
| egi.GOCDB<br />
|-<br />
| helpdesk <br />
| '''OR''' <br />
| egi.GGUS<br />
|-<br />
| applications <br />
| '''OR''' <br />
| egi.AppDB<br />
|-<br />
| authentication <br />
| '''OR''' <br />
| egi.Perun<br />
|-<br />
| tpm <br />
| '''OR''' <br />
| egi.TPM<br />
|-<br />
| apelrepository <br />
| '''OR''' <br />
| egi.APELRepository<br />
|-<br />
| accountingportal <br />
| '''OR''' <br />
| egi.AccountingPortal<br />
|}<br />
<br />
<br> <br />
<br />
== Cloud Sites A/R ==<br />
<br />
The Core service A/R report utilizes the following metric profile: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| eu.egi.cloud.APEL-Pub <br />
| eu.egi.cloud.accounting<br />
|-<br />
| org.nagios.CDMI-TCP <br />
| eu.egi.cloud.storage-management.cdmi<br />
|-<br />
| eu.egi.cloud.OCCI-Context <br />
| eu.egi.cloud.vm-management.occi<br />
|-<br />
| eu.egi.cloud.OCCI-VM <br />
| eu.egi.cloud.vm-management.occi<br />
|-<br />
| org.nagios.OCCI-TCP <br />
| eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Cloud Sites Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="4" | '''AND''' <br />
| accounting <br />
| '''OR''' <br />
| eu.egi.cloud.accounting<br />
|-<br />
| information <br />
| '''OR''' <br />
| eu.egi.cloud.information.bdii<br />
|-<br />
| storage-management <br />
| '''OR''' <br />
| eu.egi.cloud.storage-management.cdmi<br />
|-<br />
| vm-management <br />
| '''OR''' <br />
| eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
<br><br />
<br />
= Recomputation procedure =<br />
<br />
Please refer to [[PROC10]]. <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Service_Level_Target_-_Availability_Reliability&diff=85053Service Level Target - Availability Reliability2015-12-02T07:36:04Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
<br> <br />
<br />
= Description =<br />
<br />
The ARGO service collects status results and computes daily and monthly availability (A) and reliability (R) metrics of distributed services. Both status results and A/R metrics are delivered through the ARGO Web UI, with the ability for a user to drill-down from the availability of a site to individual test results that contributed to the computed figure. <br />
<br />
== Components ==<br />
<br />
ARGO is comprised of the following building blocks: <br />
<br />
*'''The consumer.''' This service collects the metric results from the Message Broker Network (MBN) and delivers them to the compute engine in avro encoded format <br />
*'''The connectors.''' This is a collection of python modules that periodically connect to sources of truth (such as GOCDB for topology or downtimes, or POEM services for low level metric profiles etc) and deliver the information to the compute engine in avro encoded format. The period is set to daily. <br />
*'''The prefilter.''' This component is used by the ARGO compute engine in order to filter out results that may not be official (for example a non-authorative monitoring instance publishing results via the MBN) <br />
*'''The compute engine.''' Using the filtered data collected the compute engine is responsible for flattening out the metric results and for computing the services availability and reliability metrics. See next section for a more detailed description on how the computations are being performed. Results (status and A/R) are passed onto a fast, reliable and distributed datastore. <br />
*'''The REST API.''' This component serves all computed status and A/R results via a programmatic interface. <br />
*'''The Web UI.''' This component is based on the Lavoisier software. It is used in order to present the status and A/R results graphically and gives the ability to any given user to drill down from the availability of a given resource down to the actual metric results that were recorded and contributed to the computed figures.<br />
<br />
== Definitions ==<br />
<br />
=== Groupings of resources ===<br />
<br />
The definitions of entities (resources) are the following: <br />
<br />
*'''Service Endpoint:''' A service endpoint is defined as a hostname and service pair, so for example foo.example.com is a hostname, mysql is a service and a mysql database running on foo.example.com (i.e. foo.example.com:mysql) is a service endpoint. <br />
*'''Service Flavour''': A collection of same services (service endpoints). For example, multiple CREAM CEs in a site together make up the CREAM CE service flavour for the site. <br />
*'''Site:''' A collection of Service Flavours. A site can be made up of one or more service flavours. <br />
*'''NGI:''' A collection of Sites.<br />
<br />
=== Metrics and Statuses ===<br />
<br />
The following define the Metric and the Status, core building blocks of the algorithm used for A/R computations <br />
<br />
*'''Metric:''' A Metric is a functional test for a given service flavour. Within a given context (i.e. ROC_CRITICAL) each service flavour has a set of service metrics that verify its functionality and performance. This correlation between service flavour functionality and Metrics is given by the POEM service. Metric results are generated when monitoring (i.e. Nagios) tests are run on a particular service endpoint. <br />
*'''Status''': Status of a metric result, service, service endpoint, service flavour or a site is the status of that entity at a given point in time. (Note here that to go from metric result onto a site hierarchy some logic is being used in the background. This is discussed more in detail below.) Possible status values are <br />
**OK <br />
**WARNING <br />
**CRITICAL <br />
**UNKNOWN <br />
**MISSING <br />
**DOWNTIME<br />
<br />
These status values are mutually exclusive. The status of a resource can have only one value at a given point in time. <br />
<br />
=== Profiles ===<br />
<br />
There are three (3) types of profiles used within each A/R computation: <br />
<br />
*'''Metric profile:''' A profile defines which metrics are to be considered to compute the status of a service of a particular flavour. <br />
*'''Operations profile''': An operations profile defines how to aggregate status results from the metric level onto service endpoint and service flavour status results. In principal these define how ANDing and ORing operations are performed between status values. For example: <br />
**OK '''AND''' CRITICAL =&gt; CRITICAL <br />
**OK '''OR''' CRITICAL =&gt; OK <br />
*'''Aggregation profile:''' An aggregation profile defines how to aggregate service flavour statuses into site status results. As an example in the default Site A/R aggregation profiles service endpoints of the same type are ANDed to form the service flavor status (for example multiple CREAM-CE flavours are ANDed into one service flavour) while similar service flavours are ORed (for example CREAM-CE OR ARC-CE in the default profile)<br />
<br />
*'''Report''': Any given combination of one metric, one operations and one aggregation profile creates an ARGO report (see section reports below).<br />
<br />
<br> <br />
<br />
=== Time slices ===<br />
<br />
For computations of A/R results the ARGO compute engine uses 288 discrete samples on the daily timeline. The quantization of 288 values has been selected because it corresponds to a sampling frequency of 5mins. (24h * 60 = 1440 mins / 288 = 5mins). <br />
<br />
The compute engine performs computations on a daily base timeframe (even though the computations run per hour, actually ARGO performs the same daily computation with updated metric data). <br />
<br />
<br> <br />
<br />
== A/R Computation Algorithm ==<br />
<br />
The A/R results are produced by integrating status results according to metric, operations and aggregation profiles. So the compute engine needs to handle status results from metric data in an efficient way in order to algorithmically combine and integrate upon them. When the engine creates a daily timeline for a specific service endpoint and a specific metric it initiates a 288 item array reserved for the service endpoint and metric couple. <br />
<br />
[[Image:Empty sliced timeline.png|400px|Empty sliced timeline.png]] <br />
<br />
When metric data is collected for a specific metric (for a specific service endpoint) it is roughly in the following form: <br />
<br />
{ time_stamp | metric | service_flavour | hostname | status | vo | vofqan | profile | dates }<br />
<br />
The engine then gathers all relevant daily data for the specific service endpoint and metric. For example imagine that for a given day 5 distinct metric data for the hostname <tt>foo.example.com</tt>, the service <tt>mysql.service</tt> and the metric <tt>mysql.some.metric</tt>. The data rows for that day will be of the following form: <br />
<br />
{ time_stamp #1 | mysql.some.metric | mysql.service | foo.example.com | UNKOWN | vo | vofqan | profile | dates }<br />
{ time_stamp #2 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #3 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #4 | mysql.some.metric | mysql.service | foo.example.com | CRITICAL | vo | vofqan | profile | dates }<br />
{ time_stamp #5 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
The compute engine will also grab the last metric from the previous day timeline <br />
<br />
{ time_stamp #0 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
Based on the timestamp and status fields the compute engine will map these data points to the correct indexes of the metric array: <br />
<br />
[[Image:Init sliced timeline.png|400px|Init sliced timeline.png]] <br />
<br />
Afterwards the compute engine will fill in the gaps appropriately, like so: <br />
<br />
[[Image:Filled sliced timeline.png|400px|Filled sliced timeline.png]] <br />
<br />
When the engine needs to combine several different timelines in order to produce an aggregated timeline result (for example for a specific service flavor), it does the following: <br />
<br />
#Reserves a new array for the aggregation timeline <br />
#Aligns the relevant timeline arrays <br />
#Begins from index 0 and combines all array_items[0] to produce the aggregation_item[0] <br />
#Moves to next index<br />
<br />
The end result is an aggregated timeline: <br />
<br />
[[Image:Aggregated sliced timeline.png|400px|Aggregated sliced timeline.png]] <br />
<br />
*Aggregation of metric timelines into service endpoint timelines is based on the given metric profile used.. <br />
*Aggregation of service endpoint timelines into service flavour timelines is based on the given aggregation profile used. <br />
*Aggregation of service flavor timelines into group of endpoints (sites) is based also on the given aggregation profile used.<br />
<br />
In all cases AND and OR operations are based on the Operations profile used. <br />
<br />
It is important to note that the discrete handling of the status results as samples gives an easy and graceful way to implement aggregations. <br />
<br />
== Status Aggregation Algorithm ==<br />
<br />
Regarding status timelines and since there are no pre-established points in time shared by all timelines (like in sampling and A/R computations described above) the compute engine operates differently. <br />
<br />
If for example the compute engine is given 3 continuous status timelines that need to be aggregated a new timeline for the aggregation is reserved. <br />
<br />
[[Image:Empty status timeline.png|400px|Empty status timeline.png]] <br />
<br />
Then the points of interest (timestamps were status changes occur) are collected <br />
<br />
[[Image:Pois status timeline.png|400px|Pois status timeline.png]] <br />
<br />
and the compute engine slices the timeline accordingly <br />
<br />
[[Image:Sliced status timeline.png|400px|Sliced status timeline.png]] <br />
<br />
The compute engine then creates a number of chunks based on the points of interest found <br />
<br />
[[Image:Chunked status timeline.png|400px|Chunked status timeline.png]] <br />
<br />
And iteratively fills up the gaps progressively based on the profiles used in the given computation. <br />
<br />
[[Image:Aggr1 status timeline.png|400px|Aggr1 status timeline.png]] <br />
<br />
<br> [[Image:Aggr2 status timeline.png|400px|Aggr2 status timeline.png]] <br />
<br />
Once the filling up is completed the compute engine stitches back the complete aggregated timeline, like in the picture below: <br />
<br />
[[Image:Filled status timeline.png|400px|Filled status timeline.png]] <br />
<br />
= Reports =<br />
<br />
In the following subsections the metric and aggregation profiles used for each EGI report are given. <br />
<br />
The operations profile used in all of the subsequent EGI reports are given in the tabulars here:<br />
<br />
{| class="wikitable"<br />
|-<br />
| '''AND'''<br />
| '''OK'''<br />
| '''WARNING'''<br />
| '''UNKNOWN'''<br />
| '''MISSING'''<br />
| '''CRITICAL'''<br />
| '''DOWNTIME'''<br />
|-<br />
| '''OK'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''WARNING'''<br />
| WARNING<br />
| WARNING<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''UNKNOWN'''<br />
| UNKNOWN<br />
| UNKNOWN<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''MISSING'''<br />
| MISSING<br />
| MISSING<br />
| MISSING<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''CRITICAL'''<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
|-<br />
| '''DOWNTIME'''<br />
| DOWNTIME<br />
| DOWNTIME<br />
| DOWNTIME<br />
| DOWNTIME<br />
| CRITICAL<br />
| DOWNTIME<br />
|}<br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
| '''OR'''<br />
| '''OK'''<br />
| '''WARNING'''<br />
| '''UNKNOWN'''<br />
| '''MISSING'''<br />
| '''CRITICAL'''<br />
| '''DOWNTIME'''<br />
|-<br />
| '''OK'''<br />
| OK<br />
| OK<br />
| OK<br />
| OK<br />
| OK<br />
| OK<br />
|-<br />
| '''WARNING'''<br />
| OK<br />
| WARNING<br />
| WARNING<br />
| WARNING<br />
| WARNING<br />
| WARNING<br />
|-<br />
| '''UNKNOWN'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| UNKNOWN<br />
| CRITICAL<br />
| UNKNOWN<br />
|-<br />
| '''MISSING'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''CRITICAL'''<br />
| OK<br />
| WARNING<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
|-<br />
| '''DOWNTIME'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| DOWNTIME<br />
| CRITICAL<br />
| DOWNTIME<br />
|}<br />
<br />
<br />
<br />
<br />
<br />
== Sites A/R ==<br />
<br />
In the Sites A/R report the following metric profile is used: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| org.nordugrid.ARC-CE-ARIS <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-IGTF <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-result <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-srm <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-sw-csh <br />
| ARC-CE<br />
|-<br />
| emi.cream.CREAMCE-JobSubmit <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-Bi <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-Csh <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-SoftVer <br />
| CREAM-CE<br />
|-<br />
| hr.srce.CADist-Check <br />
| CREAM-CE<br />
|-<br />
| hr.srce.CREAMCE-CertLifetime <br />
| CREAM-CE<br />
|-<br />
| hr.srce.GRAM-Auth <br />
| GRAM5<br />
|-<br />
| hr.srce.GRAM-CertLifetime <br />
| GRAM5<br />
|-<br />
| hr.srce.GRAM-Command <br />
| GRAM5<br />
|-<br />
| hr.srce.QCG-Computing-CertLifetime <br />
| QCG.Computing<br />
|-<br />
| pl.plgrid.QCG-Computing <br />
| QCG.Computing<br />
|-<br />
| hr.srce.SRM2-CertLifetime <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Del <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Get <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-GetSURLs <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-GetTURLs <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Ls <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-LsDir <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Put <br />
| SRMv2<br />
|-<br />
| org.bdii.Entries <br />
| Site-BDII<br />
|-<br />
| org.bdii.Freshness <br />
| Site-BDII<br />
|-<br />
| emi.unicore.TargetSystemFactory <br />
| unicore6.TargetSystemFactory<br />
|-<br />
| emi.unicore.UNICORE-Job <br />
| unicore6.TargetSystemFactory<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Sites Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="8" | '''AND''' <br />
| rowspan="5" | Compute <br />
| rowspan="5" | '''OR''' <br />
| CREAM-CE<br />
|-<br />
| ARC-CE<br />
|-<br />
| GRAM5<br />
|-<br />
| unicore6.TargetSystemFactory<br />
|-<br />
| QCG.Computing<br />
|-<br />
| rowspan="2" | Storage <br />
| rowspan="2" | '''OR''' <br />
| SRMv2<br />
|-<br />
| SRM<br />
|-<br />
| Information <br />
| '''OR''' <br />
| Site-BDII<br />
|}<br />
<br />
<br> <br />
<br />
== NGI sites A/R ==<br />
<br />
For the NGI level aggregation all A/R results for sites belonging to the NGI are collected and aggregated dynamically weighted based on the HEPSPEC factor for each site. Hence larger sites contribute more to the overall NGI A/R and smaller sites less. <br />
<br />
=== Monthly League Tables ===<br />
<br />
Monthly EGI League Tables are accessible via the ARGO Web UI (Lavoisier) under the following link: '''<nowiki>http://argo.egi.eu/lavoisier/ngi_reports?month=YYYY-MM</nowiki>''' <br />
<br />
To get results for a specific month one should replace YYYY and MM with the calendar year and month respectively, hence to obtain results for August 2015 the link should be formatted as follows: http://argo.egi.eu/lavoisier/ngi_reports?month=2015-08 . <br />
<br />
Monthly Reports are also available at '''[[Resource Centres OLA and Resource infrastructure Provider OLA reports|'''Resource Centres OLA and Resource infrastructure Provider OLA reports wiki page''']] ''' <br />
<br />
== Core services A/R ==<br />
<br />
The Core service A/R report utilizes the following metric profile: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| org.activemq.OpenWireSSL <br />
| egi.APELRepository<br />
|-<br />
| org.nagiosexchange.AccountingPortal-WebCheck <br />
| egi.AccountingPortal<br />
|-<br />
| org.nagiosexchange.AppDB-WebCheck <br />
| egi.AppDB<br />
|-<br />
| org.nagiosexchange.GGUS-WebCheck <br />
| egi.GGUS<br />
|-<br />
| org.nagios.GOCDB-PortCheck <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GOCDB-PI <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GOCDB-WebCheck <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GSTAT-WebCheck <br />
| egi.GSTAT<br />
|-<br />
| org.activemq.Network-Topic <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.Network-VirtualDestination <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.OpenWire <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.OpenWireSSL <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.STOMP <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.STOMPSSL <br />
| egi.MSGBroker<br />
|-<br />
| org.nagiosexchange.MetricsPortal-WebCheck <br />
| egi.MetricsPortal<br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck <br />
| egi.OpsPortal<br />
|-<br />
| eu.egi.cloud.Perun-Check <br />
| egi.Perun<br />
|-<br />
| org.nagiosexchange.Portal-WebCheck <br />
| egi.Portal<br />
|-<br />
| ch.cern.sam.SAMCentralWebAPI <br />
| egi.SAM<br />
|-<br />
| org.nagiosexchange.TMP-WebCheck <br />
| egi.TMP<br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck <br />
| ngi.OpsPortal<br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosHostSummary <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosProcess <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosWebInterface <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosHostSummary <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosProcess <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosWebInterface <br />
| vo.SAM<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Core Services Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="15" | '''AND''' <br />
| gstat <br />
| '''OR''' <br />
| egi.GSTAT<br />
|-<br />
| vosam <br />
| '''OR''' <br />
| vo.SAM<br />
|-<br />
| ngisam <br />
| '''OR''' <br />
| ngi.SAM<br />
|-<br />
| egisam <br />
| '''OR''' <br />
| egi.SAM<br />
|-<br />
| brokering <br />
| '''OR''' <br />
| egi.MSGBroker<br />
|-<br />
| egiportal <br />
| '''OR''' <br />
| egi.Portal<br />
|-<br />
| egiopsportal <br />
| '''OR''' <br />
| egi.OpsPortal<br />
|-<br />
| egimetricsportal <br />
| '''OR''' <br />
| egi.MetricsPortal<br />
|-<br />
| registry <br />
| '''OR''' <br />
| egi.GOCDB<br />
|-<br />
| helpdesk <br />
| '''OR''' <br />
| egi.GGUS<br />
|-<br />
| applications <br />
| '''OR''' <br />
| egi.AppDB<br />
|-<br />
| authentication <br />
| '''OR''' <br />
| egi.Perun<br />
|-<br />
| tpm <br />
| '''OR''' <br />
| egi.TPM<br />
|-<br />
| apelrepository <br />
| '''OR''' <br />
| egi.APELRepository<br />
|-<br />
| accountingportal <br />
| '''OR''' <br />
| egi.AccountingPortal<br />
|}<br />
<br />
<br> <br />
<br />
== Cloud Sites A/R ==<br />
<br />
The Core service A/R report utilizes the following metric profile: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| eu.egi.cloud.APEL-Pub <br />
| eu.egi.cloud.accounting<br />
|-<br />
| org.nagios.CDMI-TCP <br />
| eu.egi.cloud.storage-management.cdmi<br />
|-<br />
| eu.egi.cloud.OCCI-Context <br />
| eu.egi.cloud.vm-management.occi<br />
|-<br />
| eu.egi.cloud.OCCI-VM <br />
| eu.egi.cloud.vm-management.occi<br />
|-<br />
| org.nagios.OCCI-TCP <br />
| eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Cloud Sites Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="4" | '''AND''' <br />
| accounting <br />
| '''OR''' <br />
| eu.egi.cloud.accounting<br />
|-<br />
| information <br />
| '''OR''' <br />
| eu.egi.cloud.information.bdii<br />
|-<br />
| storage-management <br />
| '''OR''' <br />
| eu.egi.cloud.storage-management.cdmi<br />
|-<br />
| vm-management <br />
| '''OR''' <br />
| eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
<br> <br />
<br />
= Recomputation procedure =<br />
<br />
Please refer to [[PROC10]]. <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Service_Level_Target_-_Availability_Reliability&diff=85052Service Level Target - Availability Reliability2015-12-02T07:29:05Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
<br> <br />
<br />
= Description =<br />
<br />
The ARGO service collects status results and computes daily and monthly availability (A) and reliability (R) metrics of distributed services. Both status results and A/R metrics are delivered through the ARGO Web UI, with the ability for a user to drill-down from the availability of a site to individual test results that contributed to the computed figure. <br />
<br />
== Components ==<br />
<br />
ARGO is comprised of the following building blocks: <br />
<br />
*'''The consumer.''' This service collects the metric results from the Message Broker Network (MBN) and delivers them to the compute engine in avro encoded format <br />
*'''The connectors.''' This is a collection of python modules that periodically connect to sources of truth (such as GOCDB for topology or downtimes, or POEM services for low level metric profiles etc) and deliver the information to the compute engine in avro encoded format. The period is set to daily. <br />
*'''The prefilter.''' This component is used by the ARGO compute engine in order to filter out results that may not be official (for example a non-authorative monitoring instance publishing results via the MBN) <br />
*'''The compute engine.''' Using the filtered data collected the compute engine is responsible for flattening out the metric results and for computing the services availability and reliability metrics. See next section for a more detailed description on how the computations are being performed. Results (status and A/R) are passed onto a fast, reliable and distributed datastore. <br />
*'''The REST API.''' This component serves all computed status and A/R results via a programmatic interface. <br />
*'''The Web UI.''' This component is based on the Lavoisier software. It is used in order to present the status and A/R results graphically and gives the ability to any given user to drill down from the availability of a given resource down to the actual metric results that were recorded and contributed to the computed figures.<br />
<br />
== Definitions ==<br />
<br />
=== Groupings of resources ===<br />
<br />
The definitions of entities (resources) are the following: <br />
<br />
*'''Service Endpoint:''' A service endpoint is defined as a hostname and service pair, so for example foo.example.com is a hostname, mysql is a service and a mysql database running on foo.example.com (i.e. foo.example.com:mysql) is a service endpoint. <br />
*'''Service Flavour''': A collection of same services (service endpoints). For example, multiple CREAM CEs in a site together make up the CREAM CE service flavour for the site. <br />
*'''Site:''' A collection of Service Flavours. A site can be made up of one or more service flavours. <br />
*'''NGI:''' A collection of Sites.<br />
<br />
=== Metrics and Statuses ===<br />
<br />
The following define the Metric and the Status, core building blocks of the algorithm used for A/R computations <br />
<br />
*'''Metric:''' A Metric is a functional test for a given service flavour. Within a given context (i.e. ROC_CRITICAL) each service flavour has a set of service metrics that verify its functionality and performance. This correlation between service flavour functionality and Metrics is given by the POEM service. Metric results are generated when monitoring (i.e. Nagios) tests are run on a particular service endpoint. <br />
*'''Status''': Status of a metric result, service, service endpoint, service flavour or a site is the status of that entity at a given point in time. (Note here that to go from metric result onto a site hierarchy some logic is being used in the background. This is discussed more in detail below.) Possible status values are <br />
**OK <br />
**WARNING <br />
**CRITICAL <br />
**UNKNOWN <br />
**MISSING <br />
**DOWNTIME<br />
<br />
These status values are mutually exclusive. The status of a resource can have only one value at a given point in time. <br />
<br />
=== Profiles ===<br />
<br />
There are three (3) types of profiles used within each A/R computation: <br />
<br />
*'''Metric profile:''' A profile defines which metrics are to be considered to compute the status of a service of a particular flavour. <br />
*'''Operations profile''': An operations profile defines how to aggregate status results from the metric level onto service endpoint and service flavour status results. In principal these define how ANDing and ORing operations are performed between status values. For example: <br />
**OK '''AND''' CRITICAL =&gt; CRITICAL <br />
**OK '''OR''' CRITICAL =&gt; OK <br />
*'''Aggregation profile:''' An aggregation profile defines how to aggregate service flavour statuses into site status results. As an example in the default Site A/R aggregation profiles service endpoints of the same type are ANDed to form the service flavor status (for example multiple CREAM-CE flavours are ANDed into one service flavour) while similar service flavours are ORed (for example CREAM-CE OR ARC-CE in the default profile)<br />
<br />
*'''Report''': Any given combination of one metric, one operations and one aggregation profile creates an ARGO report (see section reports below).<br />
<br />
<br> <br />
<br />
=== Time slices ===<br />
<br />
For computations of A/R results the ARGO compute engine uses 288 discrete samples on the daily timeline. The quantization of 288 values has been selected because it corresponds to a sampling frequency of 5mins. (24h * 60 = 1440 mins / 288 = 5mins). <br />
<br />
The compute engine performs computations on a daily base timeframe (even though the computations run per hour, actually ARGO performs the same daily computation with updated metric data). <br />
<br />
<br> <br />
<br />
== A/R Computation Algorithm ==<br />
<br />
The A/R results are produced by integrating status results according to metric, operations and aggregation profiles. So the compute engine needs to handle status results from metric data in an efficient way in order to algorithmically combine and integrate upon them. When the engine creates a daily timeline for a specific service endpoint and a specific metric it initiates a 288 item array reserved for the service endpoint and metric couple. <br />
<br />
[[Image:Empty sliced timeline.png|400px|Empty sliced timeline.png]] <br />
<br />
When metric data is collected for a specific metric (for a specific service endpoint) it is roughly in the following form: <br />
<br />
{ time_stamp | metric | service_flavour | hostname | status | vo | vofqan | profile | dates }<br />
<br />
The engine then gathers all relevant daily data for the specific service endpoint and metric. For example imagine that for a given day 5 distinct metric data for the hostname <tt>foo.example.com</tt>, the service <tt>mysql.service</tt> and the metric <tt>mysql.some.metric</tt>. The data rows for that day will be of the following form: <br />
<br />
{ time_stamp #1 | mysql.some.metric | mysql.service | foo.example.com | UNKOWN | vo | vofqan | profile | dates }<br />
{ time_stamp #2 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #3 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #4 | mysql.some.metric | mysql.service | foo.example.com | CRITICAL | vo | vofqan | profile | dates }<br />
{ time_stamp #5 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
The compute engine will also grab the last metric from the previous day timeline <br />
<br />
{ time_stamp #0 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
Based on the timestamp and status fields the compute engine will map these data points to the correct indexes of the metric array: <br />
<br />
[[Image:Init sliced timeline.png|400px|Init sliced timeline.png]] <br />
<br />
Afterwards the compute engine will fill in the gaps appropriately, like so: <br />
<br />
[[Image:Filled sliced timeline.png|400px|Filled sliced timeline.png]] <br />
<br />
When the engine needs to combine several different timelines in order to produce an aggregated timeline result (for example for a specific service flavor), it does the following: <br />
<br />
#Reserves a new array for the aggregation timeline <br />
#Aligns the relevant timeline arrays <br />
#Begins from index 0 and combines all array_items[0] to produce the aggregation_item[0] <br />
#Moves to next index<br />
<br />
The end result is an aggregated timeline: <br />
<br />
[[Image:Aggregated sliced timeline.png|400px|Aggregated sliced timeline.png]] <br />
<br />
*Aggregation of metric timelines into service endpoint timelines is based on the given metric profile used.. <br />
*Aggregation of service endpoint timelines into service flavour timelines is based on the given aggregation profile used. <br />
*Aggregation of service flavor timelines into group of endpoints (sites) is based also on the given aggregation profile used.<br />
<br />
In all cases AND and OR operations are based on the Operations profile used. <br />
<br />
It is important to note that the discrete handling of the status results as samples gives an easy and graceful way to implement aggregations. <br />
<br />
== Status Aggregation Algorithm ==<br />
<br />
Regarding status timelines and since there are no pre-established points in time shared by all timelines (like in sampling and A/R computations described above) the compute engine operates differently. <br />
<br />
If for example the compute engine is given 3 continuous status timelines that need to be aggregated a new timeline for the aggregation is reserved. <br />
<br />
[[Image:Empty status timeline.png|400px|Empty status timeline.png]] <br />
<br />
Then the points of interest (timestamps were status changes occur) are collected <br />
<br />
[[Image:Pois status timeline.png|400px|Pois status timeline.png]] <br />
<br />
and the compute engine slices the timeline accordingly <br />
<br />
[[Image:Sliced status timeline.png|400px|Sliced status timeline.png]] <br />
<br />
The compute engine then creates a number of chunks based on the points of interest found <br />
<br />
[[Image:Chunked status timeline.png|400px|Chunked status timeline.png]] <br />
<br />
And iteratively fills up the gaps progressively based on the profiles used in the given computation. <br />
<br />
[[Image:Aggr1 status timeline.png|400px|Aggr1 status timeline.png]] <br />
<br />
<br> [[Image:Aggr2 status timeline.png|400px|Aggr2 status timeline.png]] <br />
<br />
Once the filling up is completed the compute engine stitches back the complete aggregated timeline, like in the picture below: <br />
<br />
[[Image:Filled status timeline.png|400px|Filled status timeline.png]] <br />
<br />
= Reports =<br />
<br />
In the following subsections the metric and aggregation profiles used for each EGI report are given. <br />
<br />
The operations profile used in all of the subsequent EGI reports is shown in the tabulars here:<br />
<br />
{| class="wikitable"<br />
|-<br />
| '''AND'''<br />
| '''OK'''<br />
| '''WARNING'''<br />
| '''UNKNOWN'''<br />
| '''MISSING'''<br />
| '''CRITICAL'''<br />
| '''DOWNTIME'''<br />
|-<br />
| '''OK'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''WARNING'''<br />
| WARNING<br />
| WARNING<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''UNKNOWN'''<br />
| UNKNOWN<br />
| UNKNOWN<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''MISSING'''<br />
| MISSING<br />
| MISSING<br />
| MISSING<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''CRITICAL'''<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
|-<br />
| '''DOWNTIME'''<br />
| DOWNTIME<br />
| DOWNTIME<br />
| DOWNTIME<br />
| DOWNTIME<br />
| CRITICAL<br />
| DOWNTIME<br />
|}<br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
| '''OR'''<br />
| '''OK'''<br />
| '''WARNING'''<br />
| '''UNKNOWN'''<br />
| '''MISSING'''<br />
| '''CRITICAL'''<br />
| '''DOWNTIME'''<br />
|-<br />
| '''OK'''<br />
| OK<br />
| OK<br />
| OK<br />
| OK<br />
| OK<br />
| OK<br />
|-<br />
| '''WARNING'''<br />
| OK<br />
| WARNING<br />
| WARNING<br />
| WARNING<br />
| WARNING<br />
| WARNING<br />
|-<br />
| '''UNKNOWN'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| UNKNOWN<br />
| CRITICAL<br />
| UNKNOWN<br />
|-<br />
| '''MISSING'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| MISSING<br />
| CRITICAL<br />
| DOWNTIME<br />
|-<br />
| '''CRITICAL'''<br />
| OK<br />
| WARNING<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
| CRITICAL<br />
|-<br />
| '''DOWNTIME'''<br />
| OK<br />
| WARNING<br />
| UNKNOWN<br />
| DOWNTIME<br />
| CRITICAL<br />
| DOWNTIME<br />
|}<br />
<br />
<br />
<br />
<br />
<br />
== Sites A/R ==<br />
<br />
In the Sites A/R report the following metric profile is used: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| org.nordugrid.ARC-CE-ARIS <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-IGTF <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-result <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-srm <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-sw-csh <br />
| ARC-CE<br />
|-<br />
| emi.cream.CREAMCE-JobSubmit <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-Bi <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-Csh <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-SoftVer <br />
| CREAM-CE<br />
|-<br />
| hr.srce.CADist-Check <br />
| CREAM-CE<br />
|-<br />
| hr.srce.CREAMCE-CertLifetime <br />
| CREAM-CE<br />
|-<br />
| hr.srce.GRAM-Auth <br />
| GRAM5<br />
|-<br />
| hr.srce.GRAM-CertLifetime <br />
| GRAM5<br />
|-<br />
| hr.srce.GRAM-Command <br />
| GRAM5<br />
|-<br />
| hr.srce.QCG-Computing-CertLifetime <br />
| QCG.Computing<br />
|-<br />
| pl.plgrid.QCG-Computing <br />
| QCG.Computing<br />
|-<br />
| hr.srce.SRM2-CertLifetime <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Del <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Get <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-GetSURLs <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-GetTURLs <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Ls <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-LsDir <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Put <br />
| SRMv2<br />
|-<br />
| org.bdii.Entries <br />
| Site-BDII<br />
|-<br />
| org.bdii.Freshness <br />
| Site-BDII<br />
|-<br />
| emi.unicore.TargetSystemFactory <br />
| unicore6.TargetSystemFactory<br />
|-<br />
| emi.unicore.UNICORE-Job <br />
| unicore6.TargetSystemFactory<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Sites Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="8" | '''AND''' <br />
| rowspan="5" | Compute <br />
| rowspan="5" | '''OR''' <br />
| CREAM-CE<br />
|-<br />
| ARC-CE<br />
|-<br />
| GRAM5<br />
|-<br />
| unicore6.TargetSystemFactory<br />
|-<br />
| QCG.Computing<br />
|-<br />
| rowspan="2" | Storage <br />
| rowspan="2" | '''OR''' <br />
| SRMv2<br />
|-<br />
| SRM<br />
|-<br />
| Information <br />
| '''OR''' <br />
| Site-BDII<br />
|}<br />
<br />
<br> <br />
<br />
== NGI sites A/R ==<br />
<br />
For the NGI level aggregation all A/R results for sites belonging to the NGI are collected and aggregated dynamically weighted based on the HEPSPEC factor for each site. Hence larger sites contribute more to the overall NGI A/R and smaller sites less. <br />
<br />
=== Monthly League Tables ===<br />
<br />
Monthly EGI League Tables are accessible via the ARGO Web UI (Lavoisier) under the following link: '''<nowiki>http://argo.egi.eu/lavoisier/ngi_reports?month=YYYY-MM</nowiki>''' <br />
<br />
To get results for a specific month one should replace YYYY and MM with the calendar year and month respectively, hence to obtain results for August 2015 the link should be formatted as follows: http://argo.egi.eu/lavoisier/ngi_reports?month=2015-08 . <br />
<br />
Monthly Reports are also available at '''[[Resource Centres OLA and Resource infrastructure Provider OLA reports|'''Resource Centres OLA and Resource infrastructure Provider OLA reports wiki page''']] ''' <br />
<br />
== Core services A/R ==<br />
<br />
The Core service A/R report utilizes the following metric profile: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| org.activemq.OpenWireSSL <br />
| egi.APELRepository<br />
|-<br />
| org.nagiosexchange.AccountingPortal-WebCheck <br />
| egi.AccountingPortal<br />
|-<br />
| org.nagiosexchange.AppDB-WebCheck <br />
| egi.AppDB<br />
|-<br />
| org.nagiosexchange.GGUS-WebCheck <br />
| egi.GGUS<br />
|-<br />
| org.nagios.GOCDB-PortCheck <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GOCDB-PI <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GOCDB-WebCheck <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GSTAT-WebCheck <br />
| egi.GSTAT<br />
|-<br />
| org.activemq.Network-Topic <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.Network-VirtualDestination <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.OpenWire <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.OpenWireSSL <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.STOMP <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.STOMPSSL <br />
| egi.MSGBroker<br />
|-<br />
| org.nagiosexchange.MetricsPortal-WebCheck <br />
| egi.MetricsPortal<br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck <br />
| egi.OpsPortal<br />
|-<br />
| eu.egi.cloud.Perun-Check <br />
| egi.Perun<br />
|-<br />
| org.nagiosexchange.Portal-WebCheck <br />
| egi.Portal<br />
|-<br />
| ch.cern.sam.SAMCentralWebAPI <br />
| egi.SAM<br />
|-<br />
| org.nagiosexchange.TMP-WebCheck <br />
| egi.TMP<br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck <br />
| ngi.OpsPortal<br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosHostSummary <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosProcess <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosWebInterface <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosHostSummary <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosProcess <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosWebInterface <br />
| vo.SAM<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Core Services Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="15" | '''AND''' <br />
| gstat <br />
| '''OR''' <br />
| egi.GSTAT<br />
|-<br />
| vosam <br />
| '''OR''' <br />
| vo.SAM<br />
|-<br />
| ngisam <br />
| '''OR''' <br />
| ngi.SAM<br />
|-<br />
| egisam <br />
| '''OR''' <br />
| egi.SAM<br />
|-<br />
| brokering <br />
| '''OR''' <br />
| egi.MSGBroker<br />
|-<br />
| egiportal <br />
| '''OR''' <br />
| egi.Portal<br />
|-<br />
| egiopsportal <br />
| '''OR''' <br />
| egi.OpsPortal<br />
|-<br />
| egimetricsportal <br />
| '''OR''' <br />
| egi.MetricsPortal<br />
|-<br />
| registry <br />
| '''OR''' <br />
| egi.GOCDB<br />
|-<br />
| helpdesk <br />
| '''OR''' <br />
| egi.GGUS<br />
|-<br />
| applications <br />
| '''OR''' <br />
| egi.AppDB<br />
|-<br />
| authentication <br />
| '''OR''' <br />
| egi.Perun<br />
|-<br />
| tpm <br />
| '''OR''' <br />
| egi.TPM<br />
|-<br />
| apelrepository <br />
| '''OR''' <br />
| egi.APELRepository<br />
|-<br />
| accountingportal <br />
| '''OR''' <br />
| egi.AccountingPortal<br />
|}<br />
<br />
<br> <br />
<br />
== Cloud Sites A/R ==<br />
<br />
The Core service A/R report utilizes the following metric profile: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| eu.egi.cloud.APEL-Pub <br />
| eu.egi.cloud.accounting<br />
|-<br />
| org.nagios.CDMI-TCP <br />
| eu.egi.cloud.storage-management.cdmi<br />
|-<br />
| eu.egi.cloud.OCCI-Context <br />
| eu.egi.cloud.vm-management.occi<br />
|-<br />
| eu.egi.cloud.OCCI-VM <br />
| eu.egi.cloud.vm-management.occi<br />
|-<br />
| org.nagios.OCCI-TCP <br />
| eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Cloud Sites Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="4" | '''AND''' <br />
| accounting <br />
| '''OR''' <br />
| eu.egi.cloud.accounting<br />
|-<br />
| information <br />
| '''OR''' <br />
| eu.egi.cloud.information.bdii<br />
|-<br />
| storage-management <br />
| '''OR''' <br />
| eu.egi.cloud.storage-management.cdmi<br />
|-<br />
| vm-management <br />
| '''OR''' <br />
| eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
<br> <br />
<br />
= Recomputation procedure =<br />
<br />
Please refer to [[PROC10]]. <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Service_Level_Target_-_Availability_Reliability&diff=85010Service Level Target - Availability Reliability2015-11-27T11:10:42Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
<br> <br />
<br />
= Description =<br />
<br />
The ARGO service collects status results and computes daily and monthly availability (A) and reliability (R) metrics of distributed services. Both status results and A/R metrics are delivered through the ARGO Web UI, with the ability for a user to drill-down from the availability of a site to individual test results that contributed to the computed figure. <br />
<br />
== Components ==<br />
<br />
ARGO is comprised of the following building blocks: <br />
<br />
*'''The consumer.''' This service collects the metric results from the MBN and delivers them to the compute engine in avro encoded format <br />
*'''The connectors.''' This is a collection of python modules that periodically connect to sources of truth (such as GOCDB for topology or downtimes, or POEM services for low level metric profiles etc) and deliver the information to the compute engine in avro encoded format. The period is set to daily. <br />
*'''The prefilter.''' This component is used by the ARGO compute engine in order to filter out results that may not be official (for example a non-authorative monitoring instance publishing results via the MBN) <br />
*'''The compute engine.''' Using the filtered data collected the compute engine is responsible for flattening out the metric results and for computing the services availability and reliability metrics. See next section for a more detailed description on how the computations are being performed. Results (status and A/R) are passed onto a fast, reliable and distributed datastore. <br />
*'''The REST API.''' This component serves all computed status and A/R results via a programmatic interface. <br />
*'''The Web UI.''' This component is based on the Lavoisier software. It is used in order to present the status and A/R results graphically and gives the ability to any given user to drill down from the availability of a given resource down to the actual metric results that were recorded and contributed to the computed figures.<br />
<br />
== Definitions ==<br />
<br />
=== Groupings of resources ===<br />
<br />
The definitions of entities (resources) are the following: <br />
<br />
*'''Service Endpoint:''' A service endpoint is defined as a hostname and service pair, so for example foo.example.com is a hostname, mysql is a service and a mysql database running on foo.example.com (i.e. foo.example.com:mysql) is a service endpoint. <br />
*'''Service Flavour''': A collection of same services (service endpoints). For example, multiple CREAM CEs in a site together make up the CREAM CE service flavour for the site. <br />
*'''Site:''' A collection of Service Flavours. A site can be made up of one or more service flavours. <br />
*'''NGI:''' A collection of Sites.<br />
<br />
=== Metrics and Statuses ===<br />
<br />
The following define the Metric and the Status, core building blocks of the algorithm used for A/R computations <br />
<br />
*'''Metric:''' A Metric is a functional test for a given service flavour. Within a given context (i.e. ROC_CRITICAL) each service flavour has a set of service metrics that verify its functionality and performance. This correlation between service flavour functionality and Metrics is given by the POEM service. Metric results are generated when moniroting (i.e. Nagios) tests are run on a particular service endpoint. <br />
*'''Status''': Status of a metric result, service, service endpoint, service flavour or a site is the status of that entity at a given point in time. (Note here that to go from metric result onto a site hierarchy some logic is being used in the background. This is discussed more in detail below.) Possible status values are <br />
**OK <br />
**WARNING <br />
**CRITICAL <br />
**UNKNOWN <br />
**MISSING <br />
**DOWNTIME<br />
<br />
These status values are mutually exclusive. The status of a resource can have only one value at a given point in time. <br />
<br />
=== Profiles ===<br />
<br />
There are three (3) types of profiles used within each A/R computation: <br />
<br />
*'''Metric profile:''' A profile defines which metrics are to be considered to compute the status of a service of a particular flavour. <br />
*'''Operations profile''': An operations profile defines how to aggregate status results from the metric level onto service endpoint and service flavour status results. In principal these define how ANDing and ORing operations are performed between status values. For example: <br />
**OK '''AND''' CRITICAL =&gt; CRITICAL <br />
**OK '''OR''' CRITICAL =&gt; OK <br />
*'''Aggregation profile:''' An aggregation profile defines how to aggregate service flavour statuses into site status results. As an example in the default Site A/R aggregation profiles service endpoints of the same type are ANDed to form the service flavor status (for example multiple CREAM-CE flavours are ANDed into one service flavour) while similar service flavours are ORed (for example CREAM-CE OR ARC-CE in the default profile)<br />
<br />
*'''Report''': Any given combination of one metric, one operations and one aggregation profile creates an ARGO report (see section reports below).<br />
<br />
<br> <br />
<br />
=== Time slices ===<br />
<br />
For computations of A/R results the ARGO compute engine uses 288 discrete samples on the daily timeline. The quantization of 288 values has been selected because it corresponds to a sampling frequency of 5mins. (24h * 60 = 1440 mins / 288 = 5mins). <br />
<br />
The compute engine performs computations on a daily base timeframe (even though the computations run per hour, actually ARGO performs the same daily computation with updated metric data). <br />
<br />
<br> <br />
<br />
== A/R Computation Algorithm ==<br />
<br />
The A/R results are produced by integrating status results according to metric, operations and aggregation profiles. So the compute engine needs to handle status results from metric data in an efficient way in order to algorithmically combine and integrate upon them. When the engine creates a daily timeline for a specific service endpoint and a specific metric it initiates a 288 item array reserved for the service endpoint and metric couple. <br />
<br />
[[Image:Empty sliced timeline.png|400px|Empty sliced timeline.png]] <br />
<br />
When metric data is collected for a specific metric (for a specific service endpoint) it is roughly in the following form: <br />
<br />
{ time_stamp | metric | service_flavour | hostname | status | vo | vofqan | profile | dates }<br />
<br />
The engine then gathers all relevant daily data for the specific service endpoint and metric. For example imagine that for a given day 5 distinct metric data for the hostname <tt>foo.example.com</tt>, the service <tt>mysql.service</tt> and the metric <tt>mysql.some.metric</tt>. The data rows for that day will be of the following form: <br />
<br />
{ time_stamp #1 | mysql.some.metric | mysql.service | foo.example.com | UNKOWN | vo | vofqan | profile | dates }<br />
{ time_stamp #2 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #3 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #4 | mysql.some.metric | mysql.service | foo.example.com | CRITICAL | vo | vofqan | profile | dates }<br />
{ time_stamp #5 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
The compute engine will also grab the last metric from the previous day timeline <br />
<br />
{ time_stamp #0 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
Based on the timestamp and status fields the compute engine will map these data points to the correct indexes of the metric array: <br />
<br />
[[Image:Init sliced timeline.png|400px|Init sliced timeline.png]] <br />
<br />
Afterwards the compute engine will fill in the gaps appropriately, like so: <br />
<br />
[[Image:Filled sliced timeline.png|400px|Filled sliced timeline.png]] <br />
<br />
When the engine needs to combine several different timelines in order to produce an aggregated timeline result (for example for a specific service flavor), it does the following: <br />
<br />
#Reserves a new array for the aggregation timeline <br />
#Aligns the relevant timeline arrays <br />
#Begins from index 0 and combines all array_items[0] to produce the aggregation_item[0] <br />
#Moves to next index<br />
<br />
The end result is an aggregated timeline: <br />
<br />
[[Image:Aggregated sliced timeline.png|400px|Aggregated sliced timeline.png]] <br />
<br />
*Aggregation of metric timelines into service endpoint timelines is based on the given metric profile used.. <br />
*Aggregation of service endpoint timelines into service flavour timelines is based on the given aggregation profile used. <br />
*Aggregation of service flavor timelines into group of endpoints (sites) is based also on the given aggregation profile used.<br />
<br />
In all cases AND and OR operations are based on the Operations profile used. <br />
<br />
It is important to note that the discrete handling of the status results as samples gives an easy and graceful way to implement aggregations. <br />
<br />
== Status Aggregation Algorithm ==<br />
<br />
Regarding status timelines and since there are no pre-established points in time shared by all timelines (like in sampling and A/R computations described above) the compute engine operates differently. <br />
<br />
If for example the compute engine is given 3 continuous status timelines that need to be aggregated a new timeline for the aggregation is reserved. <br />
<br />
[[Image:Empty status timeline.png|400px|Empty status timeline.png]] <br />
<br />
Then the points of interest (timestamps were status changes occur) are collected <br />
<br />
[[Image:Pois status timeline.png|400px|Pois status timeline.png]] <br />
<br />
and the compute engine slices the timeline accordingly <br />
<br />
[[Image:Sliced status timeline.png|400px|Sliced status timeline.png]] <br />
<br />
The compute engine then creates a number of chunks based on the points of interest found <br />
<br />
[[Image:Chunked status timeline.png|400px|Chunked status timeline.png]] <br />
<br />
And iteratively fills up the gaps progressively based on the profiles used in the given computation. <br />
<br />
[[Image:Aggr1 status timeline.png|400px|Aggr1 status timeline.png]] <br />
<br />
<br> [[Image:Aggr2 status timeline.png|400px|Aggr2 status timeline.png]] <br />
<br />
Once the filling up is completed the compute engine stitches back the complete aggregated timeline, like in the picture below: <br />
<br />
[[Image:Filled status timeline.png|400px|Filled status timeline.png]] <br />
<br />
= Reports =<br />
<br />
In the following subsections the metric and aggregation profiles used for each EGI report are given. <br />
<br />
== Sites A/R ==<br />
<br />
In the Sites A/R report the following metric profile is used: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| org.nordugrid.ARC-CE-ARIS <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-IGTF <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-result <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-srm <br />
| ARC-CE<br />
|-<br />
| org.nordugrid.ARC-CE-sw-csh <br />
| ARC-CE<br />
|-<br />
| emi.cream.CREAMCE-JobSubmit <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-Bi <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-Csh <br />
| CREAM-CE<br />
|-<br />
| emi.wn.WN-SoftVer <br />
| CREAM-CE<br />
|-<br />
| hr.srce.CADist-Check <br />
| CREAM-CE<br />
|-<br />
| hr.srce.CREAMCE-CertLifetime <br />
| CREAM-CE<br />
|-<br />
| hr.srce.GRAM-Auth <br />
| GRAM5<br />
|-<br />
| hr.srce.GRAM-CertLifetime <br />
| GRAM5<br />
|-<br />
| hr.srce.GRAM-Command <br />
| GRAM5<br />
|-<br />
| hr.srce.QCG-Computing-CertLifetime <br />
| QCG.Computing<br />
|-<br />
| pl.plgrid.QCG-Computing <br />
| QCG.Computing<br />
|-<br />
| hr.srce.SRM2-CertLifetime <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Del <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Get <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-GetSURLs <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-GetTURLs <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Ls <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-LsDir <br />
| SRMv2<br />
|-<br />
| org.sam.SRM-Put <br />
| SRMv2<br />
|-<br />
| org.bdii.Entries <br />
| Site-BDII<br />
|-<br />
| org.bdii.Freshness <br />
| Site-BDII<br />
|-<br />
| emi.unicore.TargetSystemFactory <br />
| unicore6.TargetSystemFactory<br />
|-<br />
| emi.unicore.UNICORE-Job <br />
| unicore6.TargetSystemFactory<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Sites Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="8" | '''AND''' <br />
| rowspan="5" | Compute <br />
| rowspan="5" | '''OR''' <br />
| CREAM-CE<br />
|-<br />
| ARC-CE<br />
|-<br />
| GRAM5<br />
|-<br />
| unicore6.TargetSystemFactory<br />
|-<br />
| QCG.Computing<br />
|-<br />
| rowspan="2" | Storage <br />
| rowspan="2" | '''OR''' <br />
| SRMv2<br />
|-<br />
| SRM<br />
|-<br />
| Information <br />
| '''OR''' <br />
| Site-BDII<br />
|}<br />
<br />
<br> <br />
<br />
== NGI sites A/R ==<br />
<br />
For the NGI level aggregation all A/R results for sites belonging to the NGI are collected and aggregated dynamically weighted based on the HEPSPEC factor for each site. Hence larger sites contribute more to the overall NGI A/R and smaller sites less. <br />
<br />
=== Monthly League Tables ===<br />
<br />
Monthly EGI League Tables are accessible via the ARGO Web UI (Lavoisier) under the following link: '''<nowiki>http://argo.egi.eu/lavoisier/ngi_reports?month=YYYY-MM</nowiki>''' <br />
<br />
To get results for a specific month one should replace YYYY and MM with the calendar year and month respectively, hence to obtain results for August 2015 the link should be formatted as follows: http://argo.egi.eu/lavoisier/ngi_reports?month=2015-08 . <br />
<br />
Monthly Reports are also available at '''[[Resource Centres OLA and Resource infrastructure Provider OLA reports|'''Resource Centres OLA and Resource infrastructure Provider OLA reports wiki page''']] ''' <br />
<br />
== Core services A/R ==<br />
<br />
The Core service A/R report utilizes the following metric profile: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| org.activemq.OpenWireSSL <br />
| egi.APELRepository<br />
|-<br />
| org.nagiosexchange.AccountingPortal-WebCheck <br />
| egi.AccountingPortal<br />
|-<br />
| org.nagiosexchange.AppDB-WebCheck <br />
| egi.AppDB<br />
|-<br />
| org.nagiosexchange.GGUS-WebCheck <br />
| egi.GGUS<br />
|-<br />
| org.nagios.GOCDB-PortCheck <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GOCDB-PI <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GOCDB-WebCheck <br />
| egi.GOCDB<br />
|-<br />
| org.nagiosexchange.GSTAT-WebCheck <br />
| egi.GSTAT<br />
|-<br />
| org.activemq.Network-Topic <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.Network-VirtualDestination <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.OpenWire <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.OpenWireSSL <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.STOMP <br />
| egi.MSGBroker<br />
|-<br />
| org.activemq.STOMPSSL <br />
| egi.MSGBroker<br />
|-<br />
| org.nagiosexchange.MetricsPortal-WebCheck <br />
| egi.MetricsPortal<br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck <br />
| egi.OpsPortal<br />
|-<br />
| eu.egi.cloud.Perun-Check <br />
| egi.Perun<br />
|-<br />
| org.nagiosexchange.Portal-WebCheck <br />
| egi.Portal<br />
|-<br />
| ch.cern.sam.SAMCentralWebAPI <br />
| egi.SAM<br />
|-<br />
| org.nagiosexchange.TMP-WebCheck <br />
| egi.TMP<br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck <br />
| ngi.OpsPortal<br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosHostSummary <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosProcess <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.NagiosWebInterface <br />
| ngi.SAM<br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosHostSummary <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosProcess <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary <br />
| vo.SAM<br />
|-<br />
| org.nagiosexchange.NagiosWebInterface <br />
| vo.SAM<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Core Services Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="15" | '''AND''' <br />
| gstat <br />
| '''OR''' <br />
| egi.GSTAT<br />
|-<br />
| vosam <br />
| '''OR''' <br />
| vo.SAM<br />
|-<br />
| ngisam <br />
| '''OR''' <br />
| ngi.SAM<br />
|-<br />
| egisam <br />
| '''OR''' <br />
| egi.SAM<br />
|-<br />
| brokering <br />
| '''OR''' <br />
| egi.MSGBroker<br />
|-<br />
| egiportal <br />
| '''OR''' <br />
| egi.Portal<br />
|-<br />
| egiopsportal <br />
| '''OR''' <br />
| egi.OpsPortal<br />
|-<br />
| egimetricsportal <br />
| '''OR''' <br />
| egi.MetricsPortal<br />
|-<br />
| registry <br />
| '''OR''' <br />
| egi.GOCDB<br />
|-<br />
| helpdesk <br />
| '''OR''' <br />
| egi.GGUS<br />
|-<br />
| applications <br />
| '''OR''' <br />
| egi.AppDB<br />
|-<br />
| authentication <br />
| '''OR''' <br />
| egi.Perun<br />
|-<br />
| tpm <br />
| '''OR''' <br />
| egi.TPM<br />
|-<br />
| apelrepository <br />
| '''OR''' <br />
| egi.APELRepository<br />
|-<br />
| accountingportal <br />
| '''OR''' <br />
| egi.AccountingPortal<br />
|}<br />
<br />
<br> <br />
<br />
== Cloud Sites A/R ==<br />
<br />
The Core service A/R report utilizes the following metric profile: <br />
<br />
{| class="wikitable"<br />
|-<br />
| Metric <br />
| Service Type<br />
|-<br />
| eu.egi.cloud.APEL-Pub <br />
| eu.egi.cloud.accounting<br />
|-<br />
| org.nagios.CDMI-TCP <br />
| eu.egi.cloud.storage-management.cdmi<br />
|-<br />
| eu.egi.cloud.OCCI-Context <br />
| eu.egi.cloud.vm-management.occi<br />
|-<br />
| eu.egi.cloud.OCCI-VM <br />
| eu.egi.cloud.vm-management.occi<br />
|-<br />
| org.nagios.OCCI-TCP <br />
| eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
The Aggregation profile used is the following one: <br />
<br />
{| class="wikitable"<br />
|-<br />
! colspan="4" | Cloud Sites Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability''' <br />
| Operation <br />
| '''Service Flavor'''<br />
|-<br />
| rowspan="4" | '''AND''' <br />
| accounting <br />
| '''OR''' <br />
| eu.egi.cloud.accounting<br />
|-<br />
| information <br />
| '''OR''' <br />
| eu.egi.cloud.information.bdii<br />
|-<br />
| storage-management <br />
| '''OR''' <br />
| eu.egi.cloud.storage-management.cdmi<br />
|-<br />
| vm-management <br />
| '''OR''' <br />
| eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
<br> <br />
<br />
= Recomputation procedure =<br />
<br />
Please refer to [[PROC10]]. <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Service_Level_Target_-_Availability_Reliability&diff=85005Service Level Target - Availability Reliability2015-11-26T22:07:40Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
<br />
= Description =<br />
<br />
The ARGO service collects status results and computes daily and monthly availability (A) and reliability (R) metrics of distributed services. Both status results and A/R metrics are delivered through the ARGO Web UI, with the ability for a user to drill-down from the availability of a site to individual test results that contributed to the computed figure. <br />
<br />
== Components ==<br />
<br />
ARGO is comprised of the following building blocks:<br />
* The consumer. This service collects the metric results from the MBN and delivers them to the compute engine in avro encoded format<br />
* The connectors. This is a collection of python modules that periodically connect to sources of truth (such as GOCDB for topology or downtimes, or POEM services for low level metric profiles etc) and deliver the information to the compute engine in avro encoded format. The period is set to daily. <br />
* The prefilter. This component is used by the ARGO compute engine in order to filter out results that may not be official (for example a non-authorative monitoring instance publishing results via the MBN)<br />
* The compute engine. Using the filtered data collected the compute engine is responsible for flattening out the metric results and for computing the services availability and reliability metrics. See next section for a more detailed description on how the computations are being performed. Results (status and A/R) are passed onto a fast, reliable and distributed datastore.<br />
* The REST API. This component serves all computed status and A/R results via a programmatic interface. <br />
* The Web UI. This component is based on the Lavoisier software. It is used in order to present the status and A/R results graphically and gives the ability to any given user to drill down from the availability of a given resource down to the actual metric results that were recorded and contributed to the computed figures. <br />
<br />
== Definitions ==<br />
<br />
=== Groupings of resources ===<br />
<br />
The definitions of entities (resources) are the following:<br />
<br />
* Service Endpoint: A service endpoint is defined as a hostname and service pair, so for example foo.example.com is a hostname, mysql is a service and a mysql database running on foo.example.com (i.e. foo.example.com:mysql) is a service endpoint. <br />
* Service Flavour: A collection of same services (service endpoints). For example, multiple CREAM CEs in a site together make up the CREAM CE service flavour for the site.<br />
* Site: A collection of Service Flavours. A site can be made up of one or more service flavours.<br />
* NGI: A collection of Sites. <br />
<br />
=== Metrics and Statuses ===<br />
<br />
The following define the Metric and the Status, core building blocks of the algorithm used for A/R computations<br />
<br />
* Metric: A Metric is a functional test for a given service flavour. Within a given context (i.e. ROC_CRITICAL) each service flavour has a set of service metrics that verify its functionality and performance. This correlation between service flavour functionality and Metrics is given by the POEM service. Metric results are generated when moniroting (i.e. Nagios) tests are run on a particular service endpoint. <br />
* Status: Status of a metric result, service, service endpoint, service flavour or a site is the status of that entity at a given point in time. (Note here that to go from metric result onto a site hierarchy some logic is being used in the background. This is discussed more in detail below.) Possible status values are<br />
** OK<br />
** WARNING<br />
** CRITICAL<br />
** UNKNOWN<br />
** MISSING<br />
** DOWNTIME<br />
These status values are mutually exclusive. The status of a resource can have only one value at a given point in time.<br />
<br />
=== Profiles ===<br />
<br />
There are three (3) types of profiles used within each A/R computation:<br />
<br />
* Metric profile: A profile defines which metrics are to be considered to compute the status of a service of a particular flavour. <br />
* Operations profile: An operations profile defines how to aggregate status results from the metric level onto service endpoint and service flavour status results. In principal these define how ANDing and ORing operations are performed between status values. For example:<br />
** OK '''AND''' CRITICAL => CRITICAL<br />
** OK '''OR''' CRITICAL => OK<br />
* Aggregation profile: An aggregation profile defines how to aggregate service flavour statuses into site status results. As an example in the default Site A/R aggregation profiles service endpoints of the same type are ANDed to form the service flavor status (for example multiple CREAM-CE flavours are ANDed into one service flavour) while similar service flavours are ORed (for example CREAM-CE OR ARC-CE in the default profile)<br />
<br />
* Report: Any given combination of one metric, one operations and one aggregation profile creates an ARGO report (see section reports below). <br />
<br />
<br />
=== Time slices ===<br />
<br />
For computations of A/R results the ARGO compute engine uses 288 discrete samples on the daily timeline. The quantization of 288 values has been selected because it corresponds to a sampling frequency of 5mins. (24h * 60 = 1440 mins / 288 = 5mins). <br />
<br />
The compute engine performs computations on a daily base timeframe (even though the computations run per hour, actually ARGO performs the same daily computation with updated metric data). <br />
<br />
<br />
== A/R Computation Algorithm ==<br />
<br />
The A/R results are produced by integrating status results according to metric, operations and aggregation profiles. So the compute engine needs to handle status results from metric data in an efficient way in order to algorithmically combine and integrate upon them. When the engine creates a daily timeline for a specific service endpoint and a specific metric it initiates a 288 item array reserved for the service endpoint and metric couple. <br />
<br />
[[File:Empty sliced timeline.png|400px]]<br />
<br />
When metric data is collected for a specific metric (for a specific service endpoint) it is roughly in the following form:<br />
<br />
{ time_stamp | metric | service_flavour | hostname | status | vo | vofqan | profile | dates }<br />
<br />
The engine then gathers all relevant daily data for the specific service endpoint and metric. For example imagine that for a given day 5 distinct metric data for the hostname <tt>foo.example.com</tt>, the service <tt>mysql.service</tt> and the metric <tt>mysql.some.metric</tt>. The data rows for that day will be of the following form:<br />
<br />
{ time_stamp #1 | mysql.some.metric | mysql.service | foo.example.com | UNKOWN | vo | vofqan | profile | dates }<br />
{ time_stamp #2 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #3 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #4 | mysql.some.metric | mysql.service | foo.example.com | CRITICAL | vo | vofqan | profile | dates }<br />
{ time_stamp #5 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
The compute engine will also grab the last metric from the previous day timeline<br />
<br />
{ time_stamp #0 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
Based on the timestamp and status fields the compute engine will map these data points to the correct indexes of the metric array:<br />
<br />
[[File:Init sliced timeline.png|400px]]<br />
<br />
Afterwards the compute engine will fill in the gaps appropriately, like so:<br />
<br />
[[File:Filled sliced timeline.png|400px]]<br />
<br />
When the engine needs to combine several different timelines in order to produce an aggregated timeline result (for example for a specific service flavor), it does the following:<br />
<br />
# Reserves a new array for the aggregation timeline<br />
# Aligns the relevant timeline arrays<br />
# Begins from index 0 and combines all array_items[0] to produce the aggregation_item[0] <br />
# Moves to next index<br />
<br />
The end result is an aggregated timeline:<br />
<br />
[[File:Aggregated sliced timeline.png|400px]]<br />
<br />
* Aggregation of metric timelines into service endpoint timelines is based on the given metric profile used.. <br />
* Aggregation of service endpoint timelines into service flavour timelines is based on the given aggregation profile used. <br />
* Aggregation of service flavor timelines into group of endpoints (sites) is based also on the given aggregation profile used.<br />
<br />
In all cases AND and OR operations are based on the Operations profile used. <br />
<br />
It is important to note that the discrete handling of the status results as samples gives an easy and graceful way to implement aggregations.<br />
<br />
== Status Aggregation Algorithm ==<br />
<br />
<br />
Regarding status timelines and since there are no pre-established points in time shared by all timelines (like in sampling and A/R computations described above) the compute engine operates differently. <br />
<br />
If for example the compute engine is given 3 continuous status timelines that need to be aggregated a new timeline for the aggregation is reserved. <br />
<br />
[[File:Empty status timeline.png|400px]]<br />
<br />
Then the points of interest (timestamps were status changes occur) are collected<br />
<br />
[[File:Pois status timeline.png|400px]]<br />
<br />
and the compute engine slices the timeline accordingly<br />
<br />
[[File:Sliced status timeline.png|400px]]<br />
<br />
The compute engine then creates a number of chunks based on the points of interest found<br />
<br />
[[File:Chunked status timeline.png|400px]]<br />
<br />
And iteratively fills up the gaps progressively based on the profiles used in the given computation.<br />
<br />
[[File:Aggr1 status timeline.png|400px]]<br />
<br />
<br />
[[File:Aggr2 status timeline.png|400px]]<br />
<br />
Once the filling up is completed the compute engine stitches back the complete aggregated timeline, like in the picture below:<br />
<br />
[[File:Filled status timeline.png|400px]]<br />
<br />
= Reports =<br />
<br />
In the following subsections the metric and aggregation profiles used for each EGI report are given. <br />
<br />
== Sites A/R ==<br />
<br />
In the Sites A/R report the following metric profile is used:<br />
<br />
{| class="wikitable"<br />
| Metric || Service Type<br />
|-<br />
| org.nordugrid.ARC-CE-ARIS || ARC-CE <br />
|-<br />
| org.nordugrid.ARC-CE-IGTF || ARC-CE <br />
|-<br />
| org.nordugrid.ARC-CE-result || ARC-CE <br />
|-<br />
| org.nordugrid.ARC-CE-srm || ARC-CE <br />
|-<br />
| org.nordugrid.ARC-CE-sw-csh || ARC-CE <br />
|-<br />
| emi.cream.CREAMCE-JobSubmit || CREAM-CE <br />
|-<br />
| emi.wn.WN-Bi || CREAM-CE <br />
|-<br />
| emi.wn.WN-Csh || CREAM-CE <br />
|-<br />
| emi.wn.WN-SoftVer || CREAM-CE <br />
|-<br />
| hr.srce.CADist-Check || CREAM-CE <br />
|-<br />
| hr.srce.CREAMCE-CertLifetime || CREAM-CE <br />
|-<br />
| hr.srce.GRAM-Auth || GRAM5 <br />
|-<br />
| hr.srce.GRAM-CertLifetime || GRAM5 <br />
|-<br />
| hr.srce.GRAM-Command || GRAM5 <br />
|-<br />
| hr.srce.QCG-Computing-CertLifetime || QCG.Computing <br />
|-<br />
| pl.plgrid.QCG-Computing || QCG.Computing <br />
|-<br />
| hr.srce.SRM2-CertLifetime || SRMv2 <br />
|-<br />
| org.sam.SRM-Del || SRMv2 <br />
|-<br />
| org.sam.SRM-Get || SRMv2 <br />
|-<br />
| org.sam.SRM-GetSURLs || SRMv2 <br />
|-<br />
| org.sam.SRM-GetTURLs || SRMv2 <br />
|-<br />
| org.sam.SRM-Ls || SRMv2 <br />
|-<br />
| org.sam.SRM-LsDir || SRMv2 <br />
|-<br />
| org.sam.SRM-Put || SRMv2 <br />
|-<br />
| org.bdii.Entries || Site-BDII <br />
|-<br />
| org.bdii.Freshness || Site-BDII <br />
|-<br />
| emi.unicore.TargetSystemFactory || unicore6.TargetSystemFactory <br />
|-<br />
| emi.unicore.UNICORE-Job || unicore6.TargetSystemFactory <br />
|}<br />
<br />
The Aggregation profile used is the following one:<br />
<br />
{| class="wikitable"<br />
!colspan="4"| Sites Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability'''<br />
| Operation<br />
| '''Service Flavor'''<br />
|-<br />
|rowspan="8"| '''AND'''<br />
|rowspan="5"| Compute<br />
|rowspan="5"| '''OR'''<br />
| CREAM-CE<br />
|-<br />
| ARC-CE<br />
|-<br />
| GRAM5<br />
|-<br />
| unicore6.TargetSystemFactory<br />
|-<br />
| QCG.Computing<br />
|-<br />
|rowspan="2"| Storage <br />
|rowspan="2"|'''OR'''<br />
| SRMv2<br />
|-<br />
| SRM<br />
|-<br />
| Information <br />
| '''OR'''<br />
| Site-BDII<br />
|}<br />
<br />
<br />
== NGI sites A/R ==<br />
<br />
For the NGI level aggregation all A/R results for sites belonging to the NGI are collected and aggregated dynamically weighted based on the HEPSPEC factor for each site. Hence larger sites contribute more to the overall NGI A/R and smaller sites less. <br />
<br />
=== Monthly League Tables ===<br />
<br />
Monthly EGI League Tables are accessible via the ARGO Web UI (Lavoisier) under the following link: '''<nowiki>http://argo.egi.eu/lavoisier/ngi_reports?month=YYYY-MM</nowiki>'''<br />
<br />
To get results for a specific month one should replace YYYY and MM with the calendar year and month respectively, hence to obtain results for August 2015 the link should be formatted as follows: http://argo.egi.eu/lavoisier/ngi_reports?month=2015-08 . <br />
<br />
Monthly Reports are also available at '''[[Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports|'''Resource Centres OLA and Resource infrastructure Provider OLA reports wiki page''']] <br />
<br />
== Core services A/R ==<br />
<br />
The Core service A/R report utilizes the following metric profile:<br />
<br />
{| class="wikitable"<br />
| Metric || Service Type<br />
|-<br />
| org.activemq.OpenWireSSL || egi.APELRepository <br />
|-<br />
| org.nagiosexchange.AccountingPortal-WebCheck || egi.AccountingPortal <br />
|-<br />
| org.nagiosexchange.AppDB-WebCheck || egi.AppDB <br />
|-<br />
| org.nagiosexchange.GGUS-WebCheck || egi.GGUS <br />
|-<br />
| org.nagios.GOCDB-PortCheck || egi.GOCDB <br />
|-<br />
| org.nagiosexchange.GOCDB-PI || egi.GOCDB <br />
|-<br />
| org.nagiosexchange.GOCDB-WebCheck || egi.GOCDB <br />
|-<br />
| org.nagiosexchange.GSTAT-WebCheck || egi.GSTAT <br />
|-<br />
| org.activemq.Network-Topic || egi.MSGBroker <br />
|-<br />
| org.activemq.Network-VirtualDestination || egi.MSGBroker <br />
|-<br />
| org.activemq.OpenWire || egi.MSGBroker <br />
|-<br />
| org.activemq.OpenWireSSL || egi.MSGBroker <br />
|-<br />
| org.activemq.STOMP || egi.MSGBroker <br />
|-<br />
| org.activemq.STOMPSSL || egi.MSGBroker <br />
|-<br />
| org.nagiosexchange.MetricsPortal-WebCheck || egi.MetricsPortal <br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck || egi.OpsPortal <br />
|-<br />
| eu.egi.cloud.Perun-Check || egi.Perun <br />
|-<br />
| org.nagiosexchange.Portal-WebCheck || egi.Portal <br />
|-<br />
| ch.cern.sam.SAMCentralWebAPI || egi.SAM <br />
|-<br />
| org.nagiosexchange.TMP-WebCheck || egi.TMP <br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck || ngi.OpsPortal <br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface || ngi.SAM <br />
|-<br />
| org.nagiosexchange.NagiosHostSummary || ngi.SAM <br />
|-<br />
| org.nagiosexchange.NagiosProcess || ngi.SAM <br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary || ngi.SAM <br />
|-<br />
| org.nagiosexchange.NagiosWebInterface || ngi.SAM <br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface || vo.SAM <br />
|-<br />
| org.nagiosexchange.NagiosHostSummary || vo.SAM <br />
|-<br />
| org.nagiosexchange.NagiosProcess || vo.SAM <br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary || vo.SAM <br />
|-<br />
| org.nagiosexchange.NagiosWebInterface || vo.SAM <br />
|}<br />
<br />
The Aggregation profile used is the following one:<br />
<br />
{| class="wikitable"<br />
!colspan="4"| Core Services Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability'''<br />
| Operation<br />
| '''Service Flavor'''<br />
|-<br />
|rowspan="15"| '''AND'''<br />
| gstat<br />
| '''OR'''<br />
| egi.GSTAT<br />
|-<br />
| vosam<br />
| '''OR'''<br />
| vo.SAM<br />
|-<br />
| ngisam<br />
| '''OR'''<br />
| ngi.SAM<br />
|-<br />
| egisam<br />
| '''OR'''<br />
| egi.SAM<br />
|-<br />
| brokering<br />
| '''OR'''<br />
| egi.MSGBroker<br />
|-<br />
| egiportal<br />
| '''OR'''<br />
| egi.Portal<br />
|-<br />
| egiopsportal<br />
| '''OR'''<br />
| egi.OpsPortal<br />
|-<br />
| egimetricsportal<br />
| '''OR'''<br />
| egi.MetricsPortal<br />
|-<br />
| registry<br />
| '''OR'''<br />
| egi.GOCDB<br />
|-<br />
| helpdesk<br />
| '''OR'''<br />
| egi.GGUS<br />
|-<br />
| applications<br />
| '''OR'''<br />
| egi.AppDB<br />
|-<br />
| authentication<br />
| '''OR'''<br />
| egi.Perun<br />
|-<br />
| tpm<br />
| '''OR'''<br />
| egi.TPM<br />
|-<br />
| apelrepository<br />
| '''OR'''<br />
| egi.APELRepository<br />
|-<br />
| accountingportal<br />
| '''OR'''<br />
| egi.AccountingPortal<br />
|}<br />
<br />
<br />
== Cloud Sites A/R ==<br />
<br />
<br />
The Core service A/R report utilizes the following metric profile:<br />
<br />
{| class="wikitable"<br />
| Metric || Service Type<br />
|-<br />
| eu.egi.cloud.APEL-Pub || eu.egi.cloud.accounting <br />
|-<br />
| org.nagios.CDMI-TCP || eu.egi.cloud.storage-management.cdmi <br />
|-<br />
| eu.egi.cloud.OCCI-Context || eu.egi.cloud.vm-management.occi <br />
|-<br />
| eu.egi.cloud.OCCI-VM || eu.egi.cloud.vm-management.occi <br />
|-<br />
| org.nagios.OCCI-TCP || eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
The Aggregation profile used is the following one:<br />
<br />
{| class="wikitable"<br />
!colspan="4"| Core Services Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability'''<br />
| Operation<br />
| '''Service Flavor'''<br />
|-<br />
|rowspan="4"| '''AND'''<br />
| accounting<br />
| '''OR'''<br />
| eu.egi.cloud.accounting<br />
|-<br />
| information<br />
| '''OR'''<br />
| eu.egi.cloud.information.bdii<br />
|-<br />
| storage-management<br />
| '''OR'''<br />
| eu.egi.cloud.storage-management.cdmi<br />
|-<br />
| vm-management<br />
| '''OR'''<br />
| eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
<br />
= Recomputation procedure =<br />
<br />
Please refer to [[PROC10]]. <br />
<br />
<br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Service_Level_Target_-_Availability_Reliability&diff=84998Service Level Target - Availability Reliability2015-11-26T15:06:49Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
<br />
= Description =<br />
<br />
The ARGO service collects status results and computes daily and monthly availability (A) and reliability (R) metrics of distributed services. Both status results and A/R metrics are delivered through the ARGO Web UI, with the ability for a user to drill-down from the availability of a site to individual test results that contributed to the computed figure. <br />
<br />
== Components ==<br />
<br />
ARGO is comprised of the following building blocks:<br />
* The consumer. This service collects the metric results from the MBN and delivers them to the compute engine in avro encoded format<br />
* The connectors. This is a collection of python modules that periodically connect to sources of truth (such as GOCDB for topology or downtimes, or POEM services for low level metric profiles etc) and deliver the information to the compute engine in avro encoded format. The period is set to daily. <br />
* The prefilter. This component is used by the ARGO compute engine in order to filter out results that may not be official (for example a non-authorative monitoring instance publishing results via the MBN)<br />
* The compute engine. Using the filtered data collected the compute engine is responsible for flattening out the metric results and for computing the services availability and reliability metrics. See next section for a more detailed description on how the computations are being performed. Results (status and A/R) are passed onto a fast, reliable and distributed datastore.<br />
* The REST API. This component serves all computed status and A/R results via a programmatic interface. <br />
* The Web UI. This component is based on the Lavoisier software. It is used in order to present the status and A/R results graphically and gives the ability to any given user to drill down from the availability of a given resource down to the actual metric results that were recorded and contributed to the computed figures. <br />
<br />
== Definitions ==<br />
<br />
=== Groupings of resources ===<br />
<br />
The definitions of entities (resources) are the following:<br />
<br />
* Service Endpoint: A service endpoint is defined as a hostname and service pair, so for example foo.example.com is a hostname, mysql is a service and a mysql database running on foo.example.com (i.e. foo.example.com:mysql) is a service endpoint. <br />
* Service Flavour: A collection of same services (service endpoints). For example, multiple CREAM CEs in a site together make up the CREAM CE service flavour for the site.<br />
* Site: A collection of Service Flavours. A site can be made up of one or more service flavours.<br />
* NGI: A collection of Sites. <br />
<br />
=== Metrics and Statuses ===<br />
<br />
The following define the Metric and the Status, core building blocks of the algorithm used for A/R computations<br />
<br />
* Metric: A Metric is a functional test for a given service flavour. Within a given context (i.e. ROC_CRITICAL) each service flavour has a set of service metrics that verify its functionality and performance. This correlation between service flavour functionality and Metrics is given by the POEM service. Metric results are generated when moniroting (i.e. Nagios) tests are run on a particular service endpoint. <br />
* Status: Status of a metric result, service, service endpoint, service flavour or a site is the status of that entity at a given point in time. (Note here that to go from metric result onto a site hierarchy some logic is being used in the background. This is discussed more in detail below.) Possible status values are<br />
** OK<br />
** WARNING<br />
** CRITICAL<br />
** UNKNOWN<br />
** MISSING<br />
** DOWNTIME<br />
These status values are mutually exclusive. The status of a resource can have only one value at a given point in time.<br />
<br />
=== Profiles ===<br />
<br />
There are three (3) types of profiles used within each A/R computation:<br />
<br />
* Metric profile: A profile defines which metrics are to be considered to compute the status of a service of a particular flavour. <br />
* Operations profile: An operations profile defines how to aggregate status results from the metric level onto service endpoint and service flavour status results. In principal these define how ANDing and ORing operations are performed between status values. For example:<br />
** OK '''AND''' CRITICAL => CRITICAL<br />
** OK '''OR''' CRITICAL => OK<br />
* Aggregation profile: An aggregation profile defines how to aggregate service flavour statuses into site status results. As an example in the default Site A/R aggregation profiles service endpoints of the same type are ANDed to form the service flavor status (for example multiple CREAM-CE flavours are ANDed into one service flavour) while similar service flavours are ORed (for example CREAM-CE OR ARC-CE in the default profile)<br />
<br />
* Report: Any given combination of one metric, one operations and one aggregation profile creates an ARGO report (see section reports below). <br />
<br />
<br />
=== Time slices ===<br />
<br />
For computations of A/R results the ARGO compute engine uses 288 discrete samples on the daily timeline. The quantization of 288 values has been selected because it corresponds to a sampling frequency of 5mins. (24h * 60 = 1440 mins / 288 = 5mins). <br />
<br />
The compute engine performs computations on a daily base timeframe (even though the computations run per hour, actually ARGO performs the same daily computation with updated metric data). <br />
<br />
<br />
== A/R Computation Algorithm ==<br />
<br />
The A/R results are produced by integrating status results according to metric, operations and aggregation profiles. So the compute engine needs to handle status results from metric data in an efficient way in order to algorithmically combine and integrate upon them. When the engine creates a daily timeline for a specific service endpoint and a specific metric it initiates a 288 item array reserved for the service endpoint and metric couple. <br />
<br />
[[File:Empty sliced timeline.png|400px]]<br />
<br />
When metric data is collected for a specific metric (for a specific service endpoint) it is roughly in the following form:<br />
<br />
{ time_stamp | metric | service_flavour | hostname | status | vo | vofqan | profile | dates }<br />
<br />
The engine then gathers all relevant daily data for the specific service endpoint and metric. For example imagine that for a given day 5 distinct metric data for the hostname <tt>foo.example.com</tt>, the service <tt>mysql.service</tt> and the metric <tt>mysql.some.metric</tt>. The data rows for that day will be of the following form:<br />
<br />
{ time_stamp #1 | mysql.some.metric | mysql.service | foo.example.com | UNKOWN | vo | vofqan | profile | dates }<br />
{ time_stamp #2 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #3 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
{ time_stamp #4 | mysql.some.metric | mysql.service | foo.example.com | CRITICAL | vo | vofqan | profile | dates }<br />
{ time_stamp #5 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
The compute engine will also grab the last metric from the previous day timeline<br />
<br />
{ time_stamp #0 | mysql.some.metric | mysql.service | foo.example.com | OK | vo | vofqan | profile | dates }<br />
<br />
Based on the timestamp and status fields the compute engine will map these data points to the correct indexes of the metric array:<br />
<br />
[[File:Init sliced timeline.png|400px]]<br />
<br />
Afterwards the compute engine will fill in the gaps appropriately, like so:<br />
<br />
[[File:Filled sliced timeline.png|400px]]<br />
<br />
When the engine needs to combine several different timelines in order to produce an aggregated timeline result (for example for a specific service flavor), it does the following:<br />
<br />
# Reserves a new array for the aggregation timeline<br />
# Aligns the relevant timeline arrays<br />
# Begins from index 0 and combines all array_items[0] to produce the aggregation_item[0] <br />
# Moves to next index<br />
<br />
The end result is an aggregated timeline:<br />
<br />
[[File:Aggregated sliced timeline.png|400px]]<br />
<br />
* Aggregation of metric timelines into service endpoint timelines is based on the given metric profile used.. <br />
* Aggregation of service endpoint timelines into service flavour timelines is based on the given aggregation profile used. <br />
* Aggregation of service flavor timelines into group of endpoints (sites) is based also on the given aggregation profile used.<br />
<br />
In all cases AND and OR operations are based on the Operations profile used. <br />
<br />
It is important to note that the discrete handling of the status results as samples gives an easy and graceful way to implement aggregations.<br />
<br />
== Status Aggregation Algorithm ==<br />
<br />
<br />
Regarding status timelines and since there are no pre-established points in time shared by all timelines (like in sampling and A/R computations described above) the compute engine operates differently. <br />
<br />
If for example the compute engine is given 3 continuous status timelines that need to be aggregated a new timeline for the aggregation is reserved. <br />
<br />
[[File:Empty status timeline.png|400px]]<br />
<br />
Then the points of interest (timestamps were status changes occur) are collected<br />
<br />
[[File:Pois status timeline.png|400px]]<br />
<br />
and the compute engine slices the timeline accordingly<br />
<br />
[[File:Sliced status timeline.png|400px]]<br />
<br />
The compute engine then creates a number of chunks based on the points of interest found<br />
<br />
[[File:Chunked status timeline.png|400px]]<br />
<br />
And iteratively fills up the gaps progressively based on the profiles used in the given computation.<br />
<br />
[[File:Aggr1 status timeline.png|400px]]<br />
<br />
<br />
[[File:Aggr2 status timeline.png|400px]]<br />
<br />
Once the filling up is completed the compute engine stitches back the complete aggregated timeline, like in the picture below:<br />
<br />
[[File:Filled status timeline.png|400px]]<br />
<br />
= Reports =<br />
<br />
In the following subsections the metric and aggregation profiles used for each EGI report are given. <br />
<br />
== Sites A/R ==<br />
<br />
In the Sites A/R report the following metric profile is used:<br />
<br />
{| class="wikitable"<br />
| Metric || Service Type<br />
|-<br />
| org.nordugrid.ARC-CE-ARIS || ARC-CE <br />
|-<br />
| org.nordugrid.ARC-CE-IGTF || ARC-CE <br />
|-<br />
| org.nordugrid.ARC-CE-result || ARC-CE <br />
|-<br />
| org.nordugrid.ARC-CE-srm || ARC-CE <br />
|-<br />
| org.nordugrid.ARC-CE-sw-csh || ARC-CE <br />
|-<br />
| emi.cream.CREAMCE-JobSubmit || CREAM-CE <br />
|-<br />
| emi.wn.WN-Bi || CREAM-CE <br />
|-<br />
| emi.wn.WN-Csh || CREAM-CE <br />
|-<br />
| emi.wn.WN-SoftVer || CREAM-CE <br />
|-<br />
| hr.srce.CADist-Check || CREAM-CE <br />
|-<br />
| hr.srce.CREAMCE-CertLifetime || CREAM-CE <br />
|-<br />
| hr.srce.GRAM-Auth || GRAM5 <br />
|-<br />
| hr.srce.GRAM-CertLifetime || GRAM5 <br />
|-<br />
| hr.srce.GRAM-Command || GRAM5 <br />
|-<br />
| hr.srce.QCG-Computing-CertLifetime || QCG.Computing <br />
|-<br />
| pl.plgrid.QCG-Computing || QCG.Computing <br />
|-<br />
| hr.srce.SRM2-CertLifetime || SRMv2 <br />
|-<br />
| org.sam.SRM-Del || SRMv2 <br />
|-<br />
| org.sam.SRM-Get || SRMv2 <br />
|-<br />
| org.sam.SRM-GetSURLs || SRMv2 <br />
|-<br />
| org.sam.SRM-GetTURLs || SRMv2 <br />
|-<br />
| org.sam.SRM-Ls || SRMv2 <br />
|-<br />
| org.sam.SRM-LsDir || SRMv2 <br />
|-<br />
| org.sam.SRM-Put || SRMv2 <br />
|-<br />
| org.bdii.Entries || Site-BDII <br />
|-<br />
| org.bdii.Freshness || Site-BDII <br />
|-<br />
| emi.unicore.TargetSystemFactory || unicore6.TargetSystemFactory <br />
|-<br />
| emi.unicore.UNICORE-Job || unicore6.TargetSystemFactory <br />
|}<br />
<br />
The Aggregation profile used is the following one:<br />
<br />
{| class="wikitable"<br />
!colspan="4"| Sites Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability'''<br />
| Operation<br />
| '''Service Flavor'''<br />
|-<br />
|rowspan="8"| '''AND'''<br />
|rowspan="5"| Compute<br />
|rowspan="5"| '''OR'''<br />
| CREAM-CE<br />
|-<br />
| ARC-CE<br />
|-<br />
| GRAM5<br />
|-<br />
| unicore6.TargetSystemFactory<br />
|-<br />
| QCG.Computing<br />
|-<br />
|rowspan="2"| Storage <br />
|rowspan="2"|'''OR'''<br />
| SRMv2<br />
|-<br />
| SRM<br />
|-<br />
| Information <br />
| '''OR'''<br />
| Site-BDII<br />
|}<br />
<br />
<br />
== NGI sites A/R ==<br />
<br />
For the NGI level aggregation all A/R results for sites belonging to the NGI are collected and aggregated dynamically weighted based on the HEPSPEC factor for each site. Hence larger sites contribute more to the overall NGI A/R and smaller sites less. <br />
<br />
== Core services A/R ==<br />
<br />
The Core service A/R report utilizes the following metric profile:<br />
<br />
{| class="wikitable"<br />
| Metric || Service Type<br />
|-<br />
| org.activemq.OpenWireSSL || egi.APELRepository <br />
|-<br />
| org.nagiosexchange.AccountingPortal-WebCheck || egi.AccountingPortal <br />
|-<br />
| org.nagiosexchange.AppDB-WebCheck || egi.AppDB <br />
|-<br />
| org.nagiosexchange.GGUS-WebCheck || egi.GGUS <br />
|-<br />
| org.nagios.GOCDB-PortCheck || egi.GOCDB <br />
|-<br />
| org.nagiosexchange.GOCDB-PI || egi.GOCDB <br />
|-<br />
| org.nagiosexchange.GOCDB-WebCheck || egi.GOCDB <br />
|-<br />
| org.nagiosexchange.GSTAT-WebCheck || egi.GSTAT <br />
|-<br />
| org.activemq.Network-Topic || egi.MSGBroker <br />
|-<br />
| org.activemq.Network-VirtualDestination || egi.MSGBroker <br />
|-<br />
| org.activemq.OpenWire || egi.MSGBroker <br />
|-<br />
| org.activemq.OpenWireSSL || egi.MSGBroker <br />
|-<br />
| org.activemq.STOMP || egi.MSGBroker <br />
|-<br />
| org.activemq.STOMPSSL || egi.MSGBroker <br />
|-<br />
| org.nagiosexchange.MetricsPortal-WebCheck || egi.MetricsPortal <br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck || egi.OpsPortal <br />
|-<br />
| eu.egi.cloud.Perun-Check || egi.Perun <br />
|-<br />
| org.nagiosexchange.Portal-WebCheck || egi.Portal <br />
|-<br />
| ch.cern.sam.SAMCentralWebAPI || egi.SAM <br />
|-<br />
| org.nagiosexchange.TMP-WebCheck || egi.TMP <br />
|-<br />
| org.nagiosexchange.OpsPortal-WebCheck || ngi.OpsPortal <br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface || ngi.SAM <br />
|-<br />
| org.nagiosexchange.NagiosHostSummary || ngi.SAM <br />
|-<br />
| org.nagiosexchange.NagiosProcess || ngi.SAM <br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary || ngi.SAM <br />
|-<br />
| org.nagiosexchange.NagiosWebInterface || ngi.SAM <br />
|-<br />
| org.nagiosexchange.MyEGIWebInterface || vo.SAM <br />
|-<br />
| org.nagiosexchange.NagiosHostSummary || vo.SAM <br />
|-<br />
| org.nagiosexchange.NagiosProcess || vo.SAM <br />
|-<br />
| org.nagiosexchange.NagiosServiceSummary || vo.SAM <br />
|-<br />
| org.nagiosexchange.NagiosWebInterface || vo.SAM <br />
|}<br />
<br />
The Aggregation profile used is the following one:<br />
<br />
{| class="wikitable"<br />
!colspan="4"| Core Services Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability'''<br />
| Operation<br />
| '''Service Flavor'''<br />
|-<br />
|rowspan="15"| '''AND'''<br />
| gstat<br />
| '''OR'''<br />
| egi.GSTAT<br />
|-<br />
| vosam<br />
| '''OR'''<br />
| vo.SAM<br />
|-<br />
| ngisam<br />
| '''OR'''<br />
| ngi.SAM<br />
|-<br />
| egisam<br />
| '''OR'''<br />
| egi.SAM<br />
|-<br />
| brokering<br />
| '''OR'''<br />
| egi.MSGBroker<br />
|-<br />
| egiportal<br />
| '''OR'''<br />
| egi.Portal<br />
|-<br />
| egiopsportal<br />
| '''OR'''<br />
| egi.OpsPortal<br />
|-<br />
| egimetricsportal<br />
| '''OR'''<br />
| egi.MetricsPortal<br />
|-<br />
| registry<br />
| '''OR'''<br />
| egi.GOCDB<br />
|-<br />
| helpdesk<br />
| '''OR'''<br />
| egi.GGUS<br />
|-<br />
| applications<br />
| '''OR'''<br />
| egi.AppDB<br />
|-<br />
| authentication<br />
| '''OR'''<br />
| egi.Perun<br />
|-<br />
| tpm<br />
| '''OR'''<br />
| egi.TPM<br />
|-<br />
| apelrepository<br />
| '''OR'''<br />
| egi.APELRepository<br />
|-<br />
| accountingportal<br />
| '''OR'''<br />
| egi.AccountingPortal<br />
|}<br />
<br />
<br />
== Cloud Sites A/R ==<br />
<br />
<br />
The Core service A/R report utilizes the following metric profile:<br />
<br />
{| class="wikitable"<br />
| Metric || Service Type<br />
|-<br />
| eu.egi.cloud.APEL-Pub || eu.egi.cloud.accounting <br />
|-<br />
| org.nagios.CDMI-TCP || eu.egi.cloud.storage-management.cdmi <br />
|-<br />
| eu.egi.cloud.OCCI-Context || eu.egi.cloud.vm-management.occi <br />
|-<br />
| eu.egi.cloud.OCCI-VM || eu.egi.cloud.vm-management.occi <br />
|-<br />
| org.nagios.OCCI-TCP || eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
The Aggregation profile used is the following one:<br />
<br />
{| class="wikitable"<br />
!colspan="4"| Core Services Aggregation Profile<br />
|-<br />
| Operation <br />
| '''Capability'''<br />
| Operation<br />
| '''Service Flavor'''<br />
|-<br />
|rowspan="4"| '''AND'''<br />
| accounting<br />
| '''OR'''<br />
| eu.egi.cloud.accounting<br />
|-<br />
| information<br />
| '''OR'''<br />
| eu.egi.cloud.information.bdii<br />
|-<br />
| storage-management<br />
| '''OR'''<br />
| eu.egi.cloud.storage-management.cdmi<br />
|-<br />
| vm-management<br />
| '''OR'''<br />
| eu.egi.cloud.vm-management.occi<br />
|}<br />
<br />
<br />
= Recomputation procedure =<br />
<br />
Please refer to [[PROC10]]. <br />
<br />
= Reports =<br />
<br />
Monthly EGI League Tables are accessible via the ARGO Web UI (Lavoisier) under the following link: '''<nowiki>http://argo.egi.eu/lavoisier/ngi_reports?month=YYYY-MM</nowiki>'''<br />
<br />
To get results for a specific month one should replace YYYY and MM with the calendar year and month respectively, hence to obtain results for August 2015 the link should be formatted as follows: http://argo.egi.eu/lavoisier/ngi_reports?month=2015-08 . <br />
<br />
Monthly Reports are also available at '''[[Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports|'''Resource Centres OLA and Resource infrastructure Provider OLA reports wiki page''']] <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=File:Chunked_status_timeline.png&diff=84993File:Chunked status timeline.png2015-11-26T13:49:31Z<p>Pkoro: Chunked status timeline</p>
<hr />
<div>Chunked status timeline</div>Pkorohttps://wiki.egi.eu/w/index.php?title=File:Filled_status_timeline.png&diff=84992File:Filled status timeline.png2015-11-26T13:46:16Z<p>Pkoro: Filled status timeline</p>
<hr />
<div>Filled status timeline</div>Pkorohttps://wiki.egi.eu/w/index.php?title=File:Aggr2_status_timeline.png&diff=84991File:Aggr2 status timeline.png2015-11-26T13:45:57Z<p>Pkoro: Aggr2 status timeline</p>
<hr />
<div>Aggr2 status timeline</div>Pkorohttps://wiki.egi.eu/w/index.php?title=File:Aggr1_status_timeline.png&diff=84990File:Aggr1 status timeline.png2015-11-26T13:45:37Z<p>Pkoro: Aggr1 status timeline</p>
<hr />
<div>Aggr1 status timeline</div>Pkorohttps://wiki.egi.eu/w/index.php?title=File:Sliced_status_timeline.png&diff=84989File:Sliced status timeline.png2015-11-26T13:45:17Z<p>Pkoro: Sliced status timeline</p>
<hr />
<div>Sliced status timeline</div>Pkorohttps://wiki.egi.eu/w/index.php?title=File:Pois_status_timeline.png&diff=84988File:Pois status timeline.png2015-11-26T13:44:57Z<p>Pkoro: pois status timeline</p>
<hr />
<div>pois status timeline</div>Pkorohttps://wiki.egi.eu/w/index.php?title=File:Empty_status_timeline.png&diff=84987File:Empty status timeline.png2015-11-26T13:44:22Z<p>Pkoro: Empty status timeline</p>
<hr />
<div>Empty status timeline</div>Pkorohttps://wiki.egi.eu/w/index.php?title=File:Aggregated_sliced_timeline.png&diff=84984File:Aggregated sliced timeline.png2015-11-26T13:04:36Z<p>Pkoro: Aggregated sliced timeline</p>
<hr />
<div>Aggregated sliced timeline</div>Pkorohttps://wiki.egi.eu/w/index.php?title=File:Filled_sliced_timeline.png&diff=84983File:Filled sliced timeline.png2015-11-26T13:03:36Z<p>Pkoro: Filled sliced timeline</p>
<hr />
<div>Filled sliced timeline</div>Pkorohttps://wiki.egi.eu/w/index.php?title=File:Init_sliced_timeline.png&diff=84982File:Init sliced timeline.png2015-11-26T13:02:45Z<p>Pkoro: Init sliced timeline</p>
<hr />
<div>Init sliced timeline</div>Pkorohttps://wiki.egi.eu/w/index.php?title=File:Empty_sliced_timeline.png&diff=84981File:Empty sliced timeline.png2015-11-26T12:57:33Z<p>Pkoro: Empty sliced timeline</p>
<hr />
<div>Empty sliced timeline</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Service_Level_Target_-_Availability_Reliability&diff=84910Service Level Target - Availability Reliability2015-11-23T15:34:44Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
<br />
= Definition =<br />
<br />
<br />
<br />
= Threshold =<br />
<br />
<br />
<br />
= Recomputation procedure =<br />
<br />
Please refer to [[PROC10]]. <br />
<br />
= Reports =<br />
<br />
Monthly EGI League Tables are accessible via the ARGO Web UI (Lavoisier) under the following link: '''<nowiki>http://argo.egi.eu/lavoisier/ngi_reports?month=YYYY-MM</nowiki>'''<br />
<br />
To get results for a specific month one should replace YYYY and MM with the calendar year and month respectively, hence to obtain results for August 2015 the link should be formatted as follows: http://argo.egi.eu/lavoisier/ngi_reports?month=2015-08 . <br />
<br />
Monthly Reports are also available at '''[[Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports|'''Resource Centres OLA and Resource infrastructure Provider OLA reports wiki page''']] <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=84592Resource Centres OLA and Resource infrastructure Provider OLA reports2015-11-06T08:14:44Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| [https://documents.egi.eu/document/2590 08/15]<br />
| [https://documents.egi.eu/document/2607 09/15]<br />
| [https://documents.egi.eu/document/2642 10/15]<br />
| <br><br />
| <br><br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=84041Resource Centres OLA and Resource infrastructure Provider OLA reports2015-10-08T06:41:57Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| [https://documents.egi.eu/document/2590 08/15]<br />
| [https://documents.egi.eu/document/2607 09/15]<br />
| <br><br />
| <br><br />
| <br><br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=83651Resource Centres OLA and Resource infrastructure Provider OLA reports2015-09-14T14:07:54Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| [https://documents.egi.eu/document/2590 08/15]<br />
| <br><br />
| <br><br />
| <br><br />
| <br><br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Resource_Centres_OLA_and_Resource_infrastructure_Provider_OLA_reports&diff=82475Resource Centres OLA and Resource infrastructure Provider OLA reports2015-08-06T09:12:44Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}} __NOTOC__ <br />
<br />
<br> <br />
<br />
[[Performance|&lt;&lt; Performance main page]] <br />
<br />
Container for reports supporting Resource Centre Operational Level Agreement [https://documents.egi.eu/document/31] and Resource infrastructure Provider Operational Level Agreement [https://documents.egi.eu/document/463] (for NGIs and EIROs. <br />
<br />
<br> <br> <br />
<br />
'''Availability and Reliability reports are oversight according to procedure [[PROC04|''PROC04 Quality verification of monthly availability and reliability statistics'']]''' <br />
<br />
<br> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|-<br />
! Availability/Reliability <br />
! Jan <br />
! Feb <br />
! Mar <br />
! Apr <br />
! May <br />
! Jun <br />
! Jul <br />
! Aug <br />
! Sep <br />
! Oct <br />
! Nov <br />
! Dec<br />
|-<br />
! 2010 <br />
| - <br />
| - <br />
| - <br />
| - <br />
| [https://documents.egi.eu/document/42 05/10] <br />
| [https://documents.egi.eu/document/96 06/10] <br />
| [https://documents.egi.eu/document/130 07/10] <br />
| [https://documents.egi.eu/document/157 08/10] <br />
| [https://documents.egi.eu/document/219 09/10] <br />
| [https://documents.egi.eu/document/238 10/10] <br />
| [https://documents.egi.eu/document/266 11/10] <br />
| [https://documents.egi.eu/document/299 12/10]<br />
|-<br />
! 2011 <br />
| [https://documents.egi.eu/document/332 01/11] <br />
| [https://documents.egi.eu/document/402 02/11] <br />
| [https://documents.egi.eu/document/465 03/11] <br />
| [https://documents.egi.eu/document/508 04/11] <br />
| [https://documents.egi.eu/document/593 05/11] <br />
| [https://documents.egi.eu/document/648 06/11] <br />
| [https://documents.egi.eu/document/716 07/11] <br />
| [https://documents.egi.eu/document/783 08/11] <br />
| [https://documents.egi.eu/document/820 09/11] <br />
| [https://documents.egi.eu/document/879 10/11] <br />
| [https://documents.egi.eu/document/905 11/11] <br />
| [https://documents.egi.eu/document/959 12/11]<br />
|-<br />
! 2012 <br />
| [https://documents.egi.eu/document/1000 01/12] <br />
| [https://documents.egi.eu/document/1033 02/12] <br />
| [https://documents.egi.eu/document/1091 03/12] <br />
| [https://documents.egi.eu/document/1117 04/12] <br />
| [https://documents.egi.eu/document/1174 05/12] <br />
| [https://documents.egi.eu/document/1251 06/12] <br />
| [https://documents.egi.eu/document/1307 07/12] <br />
| [https://documents.egi.eu/document/1332 08/12] <br />
| [https://documents.egi.eu/document/1370 09/12] <br />
| [https://documents.egi.eu/document/1429 10/12] <br />
| [https://documents.egi.eu/document/1487 11/12] <br />
| [https://documents.egi.eu/document/1516 12/12]<br />
|-<br />
! 2013 <br />
| [https://documents.egi.eu/document/1567 01/13] <br />
| [https://documents.egi.eu/document/1615 02/13] <br />
| [https://documents.egi.eu/document/1683 03/13] <br />
| [https://documents.egi.eu/document/1734 04/13] <br />
| [https://documents.egi.eu/document/1788 05/13] <br />
| [https://documents.egi.eu/document/1857 06/13] <br />
| [https://documents.egi.eu/document/1880 07/13] <br />
| [https://documents.egi.eu/document/1934 08/13] <br />
| [https://documents.egi.eu/document/1980 09/13] <br />
| [https://documents.egi.eu/document/2017 10/13] <br />
| [https://documents.egi.eu/document/2056 11/13] <br />
| [https://documents.egi.eu/document/2068 12/13]<br />
|-<br />
! 2014 <br />
| [https://documents.egi.eu/document/2105 01/14] <br />
| [https://documents.egi.eu/document/2142 02/14] <br />
| [https://documents.egi.eu/document/2172 03/14] <br />
| [https://documents.egi.eu/document/2203 04/14] <br />
| [https://documents.egi.eu/document/2252 05/14] <br />
| [https://documents.egi.eu/document/2264 06/14] <br />
| [https://documents.egi.eu/document/2290 07/14] <br />
| [https://documents.egi.eu/document/2292 08/14] <br />
| [https://documents.egi.eu/document/2305 09/14] <br />
| [https://documents.egi.eu/document/2352 10/14] <br />
| [https://documents.egi.eu/document/2368 11/14] <br />
| [https://documents.egi.eu/document/2386 12/14]<br />
|-<br />
! 2015 <br />
| [https://documents.egi.eu/document/2423 01/15]<br />
| [https://documents.egi.eu/document/2440 02/15]<br />
| [https://documents.egi.eu/document/2464 03/15]<br />
| [https://documents.egi.eu/document/2474 04/15]<br />
| [https://documents.egi.eu/document/2519 05/15]<br />
| [https://documents.egi.eu/document/2543 06/15]<br />
| [https://documents.egi.eu/document/2566 07/15]<br />
| <br><br />
| <br><br />
| <br><br />
| <br><br />
| <br><br />
|}<br />
<br />
<br> <br />
<br />
Entries includes following reports<br> <br />
<br />
*EGI Cloud RC A/R <br />
*EGI RP/RC A/R/U <br />
*EGI RP Quality of Support <br />
*EGI RP ROD performance index <br />
*EGI RP SAM A/R&nbsp; <br />
*EGI RP Top-BDII A/R <br><br />
<br />
<br> <br />
<br />
*List of [[Underperforming sites and suspensions|underperforming/suspended Resource Centres ]]<br> <br />
*ROD performance index before 10.2014 cen be found [[ROD performance index#Performance_reports|here]] <br />
*EGEE&nbsp;project Reports:&nbsp; [https://documents.egi.eu/document/1622 January 2008 - April 2010]<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Catch_All_Grid_Core_Services&diff=78490Catch All Grid Core Services2015-04-14T13:44:12Z<p>Pkoro: /* CA Services */</p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
<br> <br />
<br />
The Core Software Services are those required by a VO in order to operate, i.e., where there is a single instance in the infrastructure or in a region. <br />
<br />
Catch-all instances are provided by EGI.eu to support small user communities. <br />
<br />
'''Contact:''' EGI Catch-all services in [http://ggus.eu/ GGUS] <br />
<br />
= Site Certification Services =<br />
<br />
NGIs that do not have their own Core Grid Services to perform certification for new sites, can use the Catch All Certification Services provided by AUTH/GRNET as part of the EGI-InSPIRE SA1.8 activity. The existing Catch All Site Certification infrastructure consists of: <br />
<br />
*'''Top Level BDII''' (cert-bdii.hellasgrid.gr) <br />
*'''WMS/LB''' (cert-wms.hellasgrid.gr)<br />
<br />
NGI Managers can add sites to the '''EGI Catch All Top Level certification BDII''' through [https://site-certification.egi.eu/ the site certification portal] <br />
<br />
= CA Services =<br />
<br />
A Catch All CA needs to be available to any user community within the EGI. Right now most of the countries participating in the EGI have or are in the process of creating their own Certification Authorities. Yet, there are still a number of countries that are late to this process and their user communities depend on the existence of a catch all CA to issue them certificates. <br />
<br />
'''SEE-GRID CA provides CA services for EGI and collaborating countries that have not established their own PKI.''' <br> <br />
<br />
SEE-GRID CA is a member of the International Grid Trust Federation (IGTF) and it is accredited by the European Grid Policy Management Authority (EUGridPMA). <br />
<br />
[http://see-grid-ca.hellasgrid.gr/about.html More information] about SEE-GRID CA along with the current list of SEE-GRID CA Registration Authorities.<br><br />
<br />
= DTEAM VO for Site Administrators =<br />
<br />
The DTEAM VO is an infrastructure VO that MUST be enabled by all EGI Resource Centers that support the VO concept for user authentication, as stated in the Resource Centre Operational Level Agreement. It is meant for testing and troubleshooting of grid capabilities across EGI Resource Centers. Usage of the DTEAM VO is subject to the EGI Security Policies. <br />
<br />
[[Dteam vo|More information]] about the DTEAM VO and how site administrators can join the VO.<br> <br />
<br />
= Services for small user communities =<br />
<br />
As part of the EGI-InSPIRE SA1.8 Activity AUTH/GRNET operates Grid Core Service for small user communities that can not operate their own Grid Core Infrastructures. <br />
<br />
{| class="wikitable"<br />
|-<br />
! Service <br />
! Description<br />
|-<br />
| '''VOMS''' <br />
| <br />
Two EGI Catch All VOMS servers: <br />
<br />
*'''voms.hellasgrid.gr ''' <br />
*'''voms2.hellasgrid.gr'''<br />
<br />
Small user communities that can not operate their own VOMS infrastructure, can use the EGI Catch All VOMS servers. <br />
<br />
'''Interested VOs can open a ticket to the ''''''"EGI Catch-all services" Unit through [http://ggus.eu/ GGUS] .''' <br />
<br />
|-<br />
| '''MyProxy ''' <br />
| <br />
EGI Catch All MyProxy server''':''' <br />
<br />
*'''myproxy.hellasgrid.gr'''<br />
<br />
Can be used by any small user community that does not operate its own MyProxy Service. <br />
<br />
|-<br />
| '''LFC ''' <br />
| <br />
EGI Catch All LFC server ''':''' <br />
<br />
*'''lfc.hellasgrid.gr'''<br />
<br />
Can be used by any small user community that does not operate its own LFC Service. <br />
<br />
|-<br />
| '''WMS/LB''' <br />
| <br />
EGI Catch All WMS/LB server: <br />
<br />
*'''wms.hellasgrid.gr'''<br />
<br />
Can be used by any small user community that does not operate its own WMS/LB Service. <br />
<br />
|-<br />
| '''TOP-BDII ''' <br />
| <br />
EGI Catch All TOP-BDII server: <br />
<br />
*'''bdii.hellasgrid.gr'''<br />
<br />
Can be used by any small user community that does not operate its own TOP-BDII Service. <br />
<br />
|}<br />
<br />
[[Category:Catch_All_Grid_Core_Services|*]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Message_brokers&diff=72083Message brokers2014-12-04T12:02:54Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
[[Category:SAM]]<br />
<br />
The production EGI Operations Message Broker Network (PROD MSG) is used in order to facilitate the message exchange between the operational tools of EGI. This broker network consists of 2 geographically separated brokers which are operated by 2 institutes: AUTH and SRCE.<br />
<br />
= Find the list of brokers =<br />
The list of the brokers that are connected to the PROD MSG Network is always available through the BDII information system. It is strongly advised that all producers and consumers that use the PROD MSG Network use the BDII in order to find the brokers that are part of the PROD MSG Network at any time. <br />
<br />
In order not to inquire the BDII every time that a consumer or producer wants to use the PROD MSG Network, information can be cached. The cache must refresh its information at least every day.<br />
<br />
= Usage policy = <br />
The PROD MSG Network is used in order to facilitate the message exchange between the operational tools of EGI. If the operators of an operational tool, that is not part of the existing set of approved operational tools for the the PROD MSG Network (a table of approved tools follows), want to use the PROD MSG Network, then they have to apply by sending a request via GGUS. Please indicate in the ticket that it must be handed to the "Messaging SU".<br />
<br />
In their request they have to provide the following information: <br />
<br />
*name: a unique short name to identify the operational tool <br />
*contact information: contact information for notifications related to the messaging infrastructure (i.e. maintenance, upgrades)<br />
*description: a multi-line description of what the operational tool does, including pointers (URLs) for more information <br />
*expected activity (if possible: average '''and''' peak numbers): <br />
**number of connections (= new sessions) per second <br />
**number of messages per second (received by the broker) <br />
**amplification factor (= number of messages sent by the broker divided by the number of messages received) <br />
**message sizes <br />
**number of clients connected at the same time<br />
<br />
*protocol(s) used as stomp|openwire x plain|ssl <br />
*exhaustive list of all destinations used, with wildcards if needed (e.g. /topic/grid.accounting.apel.{ngi} and /queue/Consumer.{role}.grid.accounting.apel.{ngi}) <br />
*whether the operational tool is local (i.e. only using one node, messages should not be propagated) or global (network of broker wise); if local, we need the broker(s) that it is allowed to run on <br />
*credentials: a list of accounts/DNs used or a credential source (i.e. Nagios NGI instances from GOCDB) <br />
*security requirements in terms of ACLs: which accounts are allowed to do what on which destinations<br />
<br />
= Usage of PROD MSG by other applications =<br />
The PROD MSG Network is a critical component for the operational requirements of the Infrastructure. Taking in mind that its capacity are not infinite, it is not advised that the PROD MSG Network is used for applications and tools outside of the operational tools of EGI. We envision that in the future, that the broker service will be yet another component of the UMD and that it will be possible to install it at the site, national and VO level opening the possibility for the creation of a number of service specific networks. Until then, application developers/operators can request for access to the PROD MSG Network and they will have to provide the same information as it is described [[Message_brokers#Usage_policy|above]]. Apart from this, we require the contact information of the operator of the application. <br />
<br />
=Operational tools using PROD MSG=<br />
<br />
<br> <br />
<center><br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|-<br />
! Tool <br />
! Description or URL<br />
! Queues and Topics<br />
|-<br />
| SAM <br />
| [[SAM]]<br />
| <br />
|-<br />
| APEL<br />
| [[APEL]]<br />
| <br />
|}<br />
</center><br />
<br />
<br />
= Maintenance windows =<br />
<br />
The following maintenance windows are used for applying regular OS upgrades. All necessary precautions (switching off bdii services etc) are taken care of beforehand by the operations teams. <br />
<br />
<br> <br />
<center><br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|-<br />
! Hostname (network endpoint) <br />
! Window<br />
|-<br />
| mq.cro-ngi.hr<br />
| first Wednesday of each month (10:00 - 12:00 CET)<br />
|-<br />
| mq.afroditi.hellasgrid.gr.<br />
| first Thursday of each month (10:00 - 12:00 CET)<br />
|}<br />
</center><br />
= External links =<br />
* [https://tomtools.cern.ch/confluence/display/MIG/Messaging.html Messaging Documentation]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Message_brokers&diff=71170Message brokers2014-11-04T09:41:30Z<p>Pkoro: /* Operational tools using PROD MSG */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
[[Category:SAM]]<br />
<br />
The production EGI Operations Message Broker Network (PROD MSG) is used in order to facilitate the message exchange between the operational tools of EGI. This broker network consists of 2 geographically separated brokers which are operated by 2 institutes: AUTH and SRCE.<br />
<br />
= Find the list of brokers =<br />
The list of the brokers that are connected to the PROD MSG Network is always available through the BDII information system. It is strongly advised that all producers and consumers that use the PROD MSG Network use the BDII in order to find the brokers that are part of the PROD MSG Network at any time. <br />
<br />
In order not to inquire the BDII every time that a consumer or producer wants to use the PROD MSG Network, information can be cached. The cache must refresh its information at least every day.<br />
<br />
= Usage policy = <br />
The PROD MSG Network is used in order to facilitate the message exchange between the operational tools of EGI. If the operators of an operational tool, that is not part of the existing set of approved operational tools for the the PROD MSG Network (a table of approved tools follows), want to use the PROD MSG Network, then they have to apply by sending a request via GGUS. Please indicate in the ticket that it must be handed to the "Messaging SU".<br />
<br />
In their request they have to provide the following information: <br />
<br />
*name: a unique short name to identify the operational tool <br />
*contact information: contact information for notifications related to the messaging infrastructure (i.e. maintenance, upgrades)<br />
*description: a multi-line description of what the operational tool does, including pointers (URLs) for more information <br />
*expected activity (if possible: average '''and''' peak numbers): <br />
**number of connections (= new sessions) per second <br />
**number of messages per second (received by the broker) <br />
**amplification factor (= number of messages sent by the broker divided by the number of messages received) <br />
**message sizes <br />
**number of clients connected at the same time<br />
<br />
*protocol(s) used as stomp|openwire x plain|ssl <br />
*exhaustive list of all destinations used, with wildcards if needed (e.g. /topic/grid.accounting.apel.{ngi} and /queue/Consumer.{role}.grid.accounting.apel.{ngi}) <br />
*whether the operational tool is local (i.e. only using one node, messages should not be propagated) or global (network of broker wise); if local, we need the broker(s) that it is allowed to run on <br />
*credentials: a list of accounts/DNs used or a credential source (i.e. Nagios NGI instances from GOCDB) <br />
*security requirements in terms of ACLs: which accounts are allowed to do what on which destinations<br />
<br />
= Usage of PROD MSG by other applications =<br />
The PROD MSG Network is a critical component for the operational requirements of the Infrastructure. Taking in mind that its capacity are not infinite, it is not advised that the PROD MSG Network is used for applications and tools outside of the operational tools of EGI. We envision that in the future, that the broker service will be yet another component of the UMD and that it will be possible to install it at the site, national and VO level opening the possibility for the creation of a number of service specific networks. Until then, application developers/operators can request for access to the PROD MSG Network and they will have to provide the same information as it is described [[Message_brokers#Usage_policy|above]]. Apart from this, we require the contact information of the operator of the application. <br />
<br />
=Operational tools using PROD MSG=<br />
<br />
<br> <br />
<center><br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|-<br />
! Tool <br />
! Description or URL<br />
! Queues and Topics<br />
|-<br />
| SAM <br />
| [[SAM]]<br />
| <br />
|-<br />
| APEL<br />
| [[APEL]]<br />
| <br />
|}<br />
</center><br />
<br />
= External links =<br />
* [https://tomtools.cern.ch/confluence/display/MIG/Messaging.html Messaging Documentation]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Message_brokers&diff=71169Message brokers2014-11-04T09:41:02Z<p>Pkoro: /* Operational tools using PROD MSG */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
[[Category:SAM]]<br />
<br />
The production EGI Operations Message Broker Network (PROD MSG) is used in order to facilitate the message exchange between the operational tools of EGI. This broker network consists of 2 geographically separated brokers which are operated by 2 institutes: AUTH and SRCE.<br />
<br />
= Find the list of brokers =<br />
The list of the brokers that are connected to the PROD MSG Network is always available through the BDII information system. It is strongly advised that all producers and consumers that use the PROD MSG Network use the BDII in order to find the brokers that are part of the PROD MSG Network at any time. <br />
<br />
In order not to inquire the BDII every time that a consumer or producer wants to use the PROD MSG Network, information can be cached. The cache must refresh its information at least every day.<br />
<br />
= Usage policy = <br />
The PROD MSG Network is used in order to facilitate the message exchange between the operational tools of EGI. If the operators of an operational tool, that is not part of the existing set of approved operational tools for the the PROD MSG Network (a table of approved tools follows), want to use the PROD MSG Network, then they have to apply by sending a request via GGUS. Please indicate in the ticket that it must be handed to the "Messaging SU".<br />
<br />
In their request they have to provide the following information: <br />
<br />
*name: a unique short name to identify the operational tool <br />
*contact information: contact information for notifications related to the messaging infrastructure (i.e. maintenance, upgrades)<br />
*description: a multi-line description of what the operational tool does, including pointers (URLs) for more information <br />
*expected activity (if possible: average '''and''' peak numbers): <br />
**number of connections (= new sessions) per second <br />
**number of messages per second (received by the broker) <br />
**amplification factor (= number of messages sent by the broker divided by the number of messages received) <br />
**message sizes <br />
**number of clients connected at the same time<br />
<br />
*protocol(s) used as stomp|openwire x plain|ssl <br />
*exhaustive list of all destinations used, with wildcards if needed (e.g. /topic/grid.accounting.apel.{ngi} and /queue/Consumer.{role}.grid.accounting.apel.{ngi}) <br />
*whether the operational tool is local (i.e. only using one node, messages should not be propagated) or global (network of broker wise); if local, we need the broker(s) that it is allowed to run on <br />
*credentials: a list of accounts/DNs used or a credential source (i.e. Nagios NGI instances from GOCDB) <br />
*security requirements in terms of ACLs: which accounts are allowed to do what on which destinations<br />
<br />
= Usage of PROD MSG by other applications =<br />
The PROD MSG Network is a critical component for the operational requirements of the Infrastructure. Taking in mind that its capacity are not infinite, it is not advised that the PROD MSG Network is used for applications and tools outside of the operational tools of EGI. We envision that in the future, that the broker service will be yet another component of the UMD and that it will be possible to install it at the site, national and VO level opening the possibility for the creation of a number of service specific networks. Until then, application developers/operators can request for access to the PROD MSG Network and they will have to provide the same information as it is described [[Message_brokers#Usage_policy|above]]. Apart from this, we require the contact information of the operator of the application. <br />
<br />
=Operational tools using PROD MSG=<br />
<br />
<br> <br />
<center><br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|-<br />
! Tool <br />
! Description or URL<br />
! Queues and Topics<br />
|-<br />
| SAM <br />
| [[SAM]]<br />
| <br />
|-<br />
| APEL<br />
| <br />
| <br />
|}<br />
</center><br />
<br />
= External links =<br />
* [https://tomtools.cern.ch/confluence/display/MIG/Messaging.html Messaging Documentation]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Message_brokers&diff=71168Message brokers2014-11-04T09:38:02Z<p>Pkoro: /* External links */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
[[Category:SAM]]<br />
<br />
The production EGI Operations Message Broker Network (PROD MSG) is used in order to facilitate the message exchange between the operational tools of EGI. This broker network consists of 2 geographically separated brokers which are operated by 2 institutes: AUTH and SRCE.<br />
<br />
= Find the list of brokers =<br />
The list of the brokers that are connected to the PROD MSG Network is always available through the BDII information system. It is strongly advised that all producers and consumers that use the PROD MSG Network use the BDII in order to find the brokers that are part of the PROD MSG Network at any time. <br />
<br />
In order not to inquire the BDII every time that a consumer or producer wants to use the PROD MSG Network, information can be cached. The cache must refresh its information at least every day.<br />
<br />
= Usage policy = <br />
The PROD MSG Network is used in order to facilitate the message exchange between the operational tools of EGI. If the operators of an operational tool, that is not part of the existing set of approved operational tools for the the PROD MSG Network (a table of approved tools follows), want to use the PROD MSG Network, then they have to apply by sending a request via GGUS. Please indicate in the ticket that it must be handed to the "Messaging SU".<br />
<br />
In their request they have to provide the following information: <br />
<br />
*name: a unique short name to identify the operational tool <br />
*contact information: contact information for notifications related to the messaging infrastructure (i.e. maintenance, upgrades)<br />
*description: a multi-line description of what the operational tool does, including pointers (URLs) for more information <br />
*expected activity (if possible: average '''and''' peak numbers): <br />
**number of connections (= new sessions) per second <br />
**number of messages per second (received by the broker) <br />
**amplification factor (= number of messages sent by the broker divided by the number of messages received) <br />
**message sizes <br />
**number of clients connected at the same time<br />
<br />
*protocol(s) used as stomp|openwire x plain|ssl <br />
*exhaustive list of all destinations used, with wildcards if needed (e.g. /topic/grid.accounting.apel.{ngi} and /queue/Consumer.{role}.grid.accounting.apel.{ngi}) <br />
*whether the operational tool is local (i.e. only using one node, messages should not be propagated) or global (network of broker wise); if local, we need the broker(s) that it is allowed to run on <br />
*credentials: a list of accounts/DNs used or a credential source (i.e. Nagios NGI instances from GOCDB) <br />
*security requirements in terms of ACLs: which accounts are allowed to do what on which destinations<br />
<br />
= Usage of PROD MSG by other applications =<br />
The PROD MSG Network is a critical component for the operational requirements of the Infrastructure. Taking in mind that its capacity are not infinite, it is not advised that the PROD MSG Network is used for applications and tools outside of the operational tools of EGI. We envision that in the future, that the broker service will be yet another component of the UMD and that it will be possible to install it at the site, national and VO level opening the possibility for the creation of a number of service specific networks. Until then, application developers/operators can request for access to the PROD MSG Network and they will have to provide the same information as it is described [[Message_brokers#Usage_policy|above]]. Apart from this, we require the contact information of the operator of the application. <br />
<br />
=Operational tools using PROD MSG=<br />
<br />
<br> <br />
<center><br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|-<br />
! Tool <br />
! Description or URL<br />
|-<br />
| SAM <br />
| [[SAM]]<br />
|}<br />
</center><br />
<br />
= External links =<br />
* [https://tomtools.cern.ch/confluence/display/MIG/Messaging.html Messaging Documentation]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Message_brokers&diff=71167Message brokers2014-11-04T09:37:45Z<p>Pkoro: /* External links */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
[[Category:SAM]]<br />
<br />
The production EGI Operations Message Broker Network (PROD MSG) is used in order to facilitate the message exchange between the operational tools of EGI. This broker network consists of 2 geographically separated brokers which are operated by 2 institutes: AUTH and SRCE.<br />
<br />
= Find the list of brokers =<br />
The list of the brokers that are connected to the PROD MSG Network is always available through the BDII information system. It is strongly advised that all producers and consumers that use the PROD MSG Network use the BDII in order to find the brokers that are part of the PROD MSG Network at any time. <br />
<br />
In order not to inquire the BDII every time that a consumer or producer wants to use the PROD MSG Network, information can be cached. The cache must refresh its information at least every day.<br />
<br />
= Usage policy = <br />
The PROD MSG Network is used in order to facilitate the message exchange between the operational tools of EGI. If the operators of an operational tool, that is not part of the existing set of approved operational tools for the the PROD MSG Network (a table of approved tools follows), want to use the PROD MSG Network, then they have to apply by sending a request via GGUS. Please indicate in the ticket that it must be handed to the "Messaging SU".<br />
<br />
In their request they have to provide the following information: <br />
<br />
*name: a unique short name to identify the operational tool <br />
*contact information: contact information for notifications related to the messaging infrastructure (i.e. maintenance, upgrades)<br />
*description: a multi-line description of what the operational tool does, including pointers (URLs) for more information <br />
*expected activity (if possible: average '''and''' peak numbers): <br />
**number of connections (= new sessions) per second <br />
**number of messages per second (received by the broker) <br />
**amplification factor (= number of messages sent by the broker divided by the number of messages received) <br />
**message sizes <br />
**number of clients connected at the same time<br />
<br />
*protocol(s) used as stomp|openwire x plain|ssl <br />
*exhaustive list of all destinations used, with wildcards if needed (e.g. /topic/grid.accounting.apel.{ngi} and /queue/Consumer.{role}.grid.accounting.apel.{ngi}) <br />
*whether the operational tool is local (i.e. only using one node, messages should not be propagated) or global (network of broker wise); if local, we need the broker(s) that it is allowed to run on <br />
*credentials: a list of accounts/DNs used or a credential source (i.e. Nagios NGI instances from GOCDB) <br />
*security requirements in terms of ACLs: which accounts are allowed to do what on which destinations<br />
<br />
= Usage of PROD MSG by other applications =<br />
The PROD MSG Network is a critical component for the operational requirements of the Infrastructure. Taking in mind that its capacity are not infinite, it is not advised that the PROD MSG Network is used for applications and tools outside of the operational tools of EGI. We envision that in the future, that the broker service will be yet another component of the UMD and that it will be possible to install it at the site, national and VO level opening the possibility for the creation of a number of service specific networks. Until then, application developers/operators can request for access to the PROD MSG Network and they will have to provide the same information as it is described [[Message_brokers#Usage_policy|above]]. Apart from this, we require the contact information of the operator of the application. <br />
<br />
=Operational tools using PROD MSG=<br />
<br />
<br> <br />
<center><br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|-<br />
! Tool <br />
! Description or URL<br />
|-<br />
| SAM <br />
| [[SAM]]<br />
|}<br />
</center><br />
<br />
= External links =<br />
* [https://tomtools.cern.ch/confluence/display/MIG/Messaging.html]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=Message_brokers&diff=71166Message brokers2014-11-04T09:37:09Z<p>Pkoro: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Tools menubar}}<br />
{{TOC_right}}<br />
[[Category:SAM]]<br />
<br />
The production EGI Operations Message Broker Network (PROD MSG) is used in order to facilitate the message exchange between the operational tools of EGI. This broker network consists of 2 geographically separated brokers which are operated by 2 institutes: AUTH and SRCE.<br />
<br />
= Find the list of brokers =<br />
The list of the brokers that are connected to the PROD MSG Network is always available through the BDII information system. It is strongly advised that all producers and consumers that use the PROD MSG Network use the BDII in order to find the brokers that are part of the PROD MSG Network at any time. <br />
<br />
In order not to inquire the BDII every time that a consumer or producer wants to use the PROD MSG Network, information can be cached. The cache must refresh its information at least every day.<br />
<br />
= Usage policy = <br />
The PROD MSG Network is used in order to facilitate the message exchange between the operational tools of EGI. If the operators of an operational tool, that is not part of the existing set of approved operational tools for the the PROD MSG Network (a table of approved tools follows), want to use the PROD MSG Network, then they have to apply by sending a request via GGUS. Please indicate in the ticket that it must be handed to the "Messaging SU".<br />
<br />
In their request they have to provide the following information: <br />
<br />
*name: a unique short name to identify the operational tool <br />
*contact information: contact information for notifications related to the messaging infrastructure (i.e. maintenance, upgrades)<br />
*description: a multi-line description of what the operational tool does, including pointers (URLs) for more information <br />
*expected activity (if possible: average '''and''' peak numbers): <br />
**number of connections (= new sessions) per second <br />
**number of messages per second (received by the broker) <br />
**amplification factor (= number of messages sent by the broker divided by the number of messages received) <br />
**message sizes <br />
**number of clients connected at the same time<br />
<br />
*protocol(s) used as stomp|openwire x plain|ssl <br />
*exhaustive list of all destinations used, with wildcards if needed (e.g. /topic/grid.accounting.apel.{ngi} and /queue/Consumer.{role}.grid.accounting.apel.{ngi}) <br />
*whether the operational tool is local (i.e. only using one node, messages should not be propagated) or global (network of broker wise); if local, we need the broker(s) that it is allowed to run on <br />
*credentials: a list of accounts/DNs used or a credential source (i.e. Nagios NGI instances from GOCDB) <br />
*security requirements in terms of ACLs: which accounts are allowed to do what on which destinations<br />
<br />
= Usage of PROD MSG by other applications =<br />
The PROD MSG Network is a critical component for the operational requirements of the Infrastructure. Taking in mind that its capacity are not infinite, it is not advised that the PROD MSG Network is used for applications and tools outside of the operational tools of EGI. We envision that in the future, that the broker service will be yet another component of the UMD and that it will be possible to install it at the site, national and VO level opening the possibility for the creation of a number of service specific networks. Until then, application developers/operators can request for access to the PROD MSG Network and they will have to provide the same information as it is described [[Message_brokers#Usage_policy|above]]. Apart from this, we require the contact information of the operator of the application. <br />
<br />
=Operational tools using PROD MSG=<br />
<br />
<br> <br />
<center><br />
{| border="1" cellspacing="0" cellpadding="5"<br />
|-<br />
! Tool <br />
! Description or URL<br />
|-<br />
| SAM <br />
| [[SAM]]<br />
|}<br />
</center><br />
<br />
= External links =<br />
* [https://tomtools.cern.ch/confluence/display/MIG/Messaging EMI Messaging]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:SA1.8-QR16&diff=67564EGI-InSPIRE:SA1.8-QR162014-05-23T07:33:43Z<p>Pkoro: /* 4. Plans for the next period */</p>
<hr />
<div>{{Template:Op menubar}} {{Template:Inspire_reports_menubar}} {{TOC_right}} <br />
= 1. Task Meetings = <!--<br />
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. <br />
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.<br />
--> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center"<br />
|-<br />
! style="width: 10%" | Date (dd/mm/yyyy) <br />
! style="width: 20%" | Url Indico Agenda <br />
! style="width: 20%" | Title <br />
! style="width: 50%" | Outcome<br />
|-<br />
| ... <br />
| .... <br />
| ... <br />
| ...<br />
|}<br />
<br />
= 2. Main Achievements = <!--<br />
Note. This is a detailed account of progress over the previous quarter of activities within the task. <br />
PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (AVOID BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN AN OVERALL REPORT)<br />
--><br />
<br />
<br />
<br />
== Availability reporting ==<br />
<br />
Within quarter 16 availability reporting was performed as usual on a monthly basis. Publication of results and re-computation requests regarding A/R results were handled by the SLM unit via GGUS.<br />
<br />
<br />
== Catch all services and core grid services ==<br />
<br />
=== VO services ===<br />
<br />
Few bugs regarding the notifications mechanism on EMI-3 VOMS have been identified. The VOMS development team was notified, bugs have been accepted and rollout of bug fixes provided have been applied on central dteam VO instances. <br />
<br />
<br />
=== EGI Catch all CA ===<br />
<br />
The EGI catch-all CA has switched over. All new end entity certificates are signed using the new CA. Old CA will continue operations (only CRL issuance).<br />
<br />
New RA have been contacted within QR16 but not yet established.<br />
<br />
=== Core services for site certification ===<br />
<br />
Code and service maintainance for site-certification.egi.eu has been taking place within QR16. <br />
<br />
=== Operational Tools ===<br />
<br />
During quarter 16 maintenance operations on the midmon dedicated SAM instance (used for monitoring of running middleware versions on sites) have been applied. Transition of SAM central services has urged some configuration changes on the instance. Also several new probes have been added that enable and assist the campaign for unsupported middleware service instances. Similar configuration changes have been applied on security monitoring central instance as well. <br />
<br />
<br />
<br />
<br><br />
<br />
= 3. Issues and Mitigation = <!-- fill the table below<br />
PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (AVOID BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN AN OVERALL REPORT)--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|-<br />
| <br />
| <br />
|-<br />
| <br />
| <br />
|}<br />
<br />
= 4. Plans for the next period = <!-- provide your text below. PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (NO BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN A REPORT) --> <br />
<br />
[[Category:SA1_Task_QR_Reports]]<br />
<br />
== Availability reporting ==<br />
<br />
Investigation of whether operational tools advancements can simplify the procedure of providing A/R reports. <br />
<br />
== Catch all services and core grid services ==<br />
<br />
=== VO Services ===<br />
<br />
Removal of dteam VO legacy groups and re-organization of Group managers per group (champaign is on-going).<br />
<br />
=== EGI Catch All CA ===<br />
<br />
Expand the network of RAs as needed. <br />
<br />
=== Core Services for Site Certification ===<br />
<br />
Maintenance and regular updates. <br />
<br />
=== Operational tools ===<br />
<br />
Maintenance and updates from middleware monitoring and security nagios instances.</div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:SA1.8-QR16&diff=67562EGI-InSPIRE:SA1.8-QR162014-05-23T07:32:36Z<p>Pkoro: /* 2. Main Achievements */</p>
<hr />
<div>{{Template:Op menubar}} {{Template:Inspire_reports_menubar}} {{TOC_right}} <br />
= 1. Task Meetings = <!--<br />
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. <br />
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.<br />
--> <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center"<br />
|-<br />
! style="width: 10%" | Date (dd/mm/yyyy) <br />
! style="width: 20%" | Url Indico Agenda <br />
! style="width: 20%" | Title <br />
! style="width: 50%" | Outcome<br />
|-<br />
| ... <br />
| .... <br />
| ... <br />
| ...<br />
|}<br />
<br />
= 2. Main Achievements = <!--<br />
Note. This is a detailed account of progress over the previous quarter of activities within the task. <br />
PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (AVOID BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN AN OVERALL REPORT)<br />
--><br />
<br />
<br />
<br />
== Availability reporting ==<br />
<br />
Within quarter 16 availability reporting was performed as usual on a monthly basis. Publication of results and re-computation requests regarding A/R results were handled by the SLM unit via GGUS.<br />
<br />
<br />
== Catch all services and core grid services ==<br />
<br />
=== VO services ===<br />
<br />
Few bugs regarding the notifications mechanism on EMI-3 VOMS have been identified. The VOMS development team was notified, bugs have been accepted and rollout of bug fixes provided have been applied on central dteam VO instances. <br />
<br />
<br />
=== EGI Catch all CA ===<br />
<br />
The EGI catch-all CA has switched over. All new end entity certificates are signed using the new CA. Old CA will continue operations (only CRL issuance).<br />
<br />
New RA have been contacted within QR16 but not yet established.<br />
<br />
=== Core services for site certification ===<br />
<br />
Code and service maintainance for site-certification.egi.eu has been taking place within QR16. <br />
<br />
=== Operational Tools ===<br />
<br />
During quarter 16 maintenance operations on the midmon dedicated SAM instance (used for monitoring of running middleware versions on sites) have been applied. Transition of SAM central services has urged some configuration changes on the instance. Also several new probes have been added that enable and assist the campaign for unsupported middleware service instances. Similar configuration changes have been applied on security monitoring central instance as well. <br />
<br />
<br />
<br />
<br><br />
<br />
= 3. Issues and Mitigation = <!-- fill the table below<br />
PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (AVOID BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN AN OVERALL REPORT)--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|-<br />
| <br />
| <br />
|-<br />
| <br />
| <br />
|}<br />
<br />
= 4. Plans for the next period = <!-- provide your text below. PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (NO BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN A REPORT) --> <br />
<br />
[[Category:SA1_Task_QR_Reports]]</div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Sa1_2014-04-29&diff=66977EGI-InSPIRE:Sa1 2014-04-292014-04-30T06:43:28Z<p>Pkoro: /* SA1.8 Availability and core services */</p>
<hr />
<div>{{Template:Op menubar}} <br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}} <br />
[[Category:SA1 weekly report]]<br />
=Progress of SA1 issues= <br />
<!-- M. Krakowian--><br />
Nothing new to report.<br />
<br />
=Milestones/Deliverables=<br />
<!-- M. Krakowian --><br />
<br />
<br />
=SA1.1 Activity Management= <br />
<!-- M. Krakowian, P. Solagna --><br />
<br />
MEETINGS<br />
<br />
ACTIVITIES<br />
<br />
=SA1.2 Security= <br />
<!-- D. Kelsey --><br />
<br />
= SA1.3 Staged rollout =<br />
<!-- J. Pina --><br />
<br />
=SA1.3 Integration=<br />
<!-- M. Krakowian --><br />
<br />
=SA1.4 Central tools= <br />
<!--E. Imamagic --><br />
<br />
=SA1.5 Accounting= <br />
'''<!--S. Pullinger--> Repository '''<br />
<br />
'''<!--S. Pullinger--> Portal'''<br />
<br />
=SA1.6 Helpdesk= <br />
<!-- G. Grein --><br />
* Preparing next GGUS release<br />
* Maintenance and development work<br />
* Ticket monitoring<br />
<br />
=SA1.7 Support=<br />
<!-- R. Trompert --><br />
<br />
== Software Support ==<br />
<!-- A Krenek --><br />
<br />
<br />
=SA1.8 Availability and core services=<br />
<!--P. Korosoglou--><br />
<br />
* Contact with ROC_Africa to setup catch-all RA (ongoing process)<br />
* Issue regarding dteam voms received and fixed<br />
<br />
== Documentation ==<br />
<!-- M. Krakowian --><br />
<br />
= Meetings=<br />
<!--all--></div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Sa1_2014-04-22&diff=66825EGI-InSPIRE:Sa1 2014-04-222014-04-23T08:50:30Z<p>Pkoro: /* SA1.8 Availability and core services */</p>
<hr />
<div>{{Template:Op menubar}} <br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}} <br />
[[Category:SA1 weekly report]]<br />
=Progress of SA1 issues= <br />
<!-- M. Krakowian--><br />
Nothing new to report.<br />
<br />
=Milestones/Deliverables=<br />
<!-- M. Krakowian --><br />
<br />
<br />
=SA1.1 Activity Management= <br />
<!-- M. Krakowian, P. Solagna --><br />
<br />
MEETINGS<br />
<br />
ACTIVITIES<br />
<br />
=SA1.2 Security= <br />
<!-- D. Kelsey --><br />
* loads of work chasing and handling the OpenSSL Heartbleed vulnerability (CVE-2014-0160)<br />
* EGI CSIRT F2F meeting in Abingdon (15-17 April)<br />
* Easter holiday<br />
<br />
= SA1.3 Staged rollout =<br />
<!-- J. Pina --><br />
<br />
=SA1.3 Integration=<br />
<!-- M. Krakowian --><br />
<br />
=SA1.4 Central tools= <br />
<!--E. Imamagic --><br />
<br />
=SA1.5 Accounting= <br />
'''<!--S. Pullinger--> Repository '''<br />
<br />
'''<!--S. Pullinger--> Portal'''<br />
<br />
=SA1.6 Helpdesk= <br />
<!-- G. Grein --><br />
<br />
=SA1.7 Support=<br />
<!-- R. Trompert --><br />
<br />
== Software Support ==<br />
<!-- A Krenek --><br />
<br />
<br />
=SA1.8 Availability and core services=<br />
<!--P. Korosoglou--><br />
<br />
* Published final A/R reports for March 2014<br />
** Still waiting for Top-BDII reports to be included on document db<br />
<br />
<br />
<br />
== Documentation ==<br />
<!-- M. Krakowian --><br />
<br />
= Meetings=<br />
<!--all--></div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Sa1_2014-03-25&diff=65731EGI-InSPIRE:Sa1 2014-03-252014-03-24T16:53:01Z<p>Pkoro: /* SA1.8 Availability and core services */</p>
<hr />
<div>{{Template:Op menubar}} <br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}} <br />
[[Category:SA1 weekly report]]<br />
=Progress of SA1 issues= <br />
<!-- M. Krakowian--><br />
Nothing new to report.<br />
<br />
=Milestones/Deliverables=<br />
<!-- M. Krakowian --><br />
<br />
<br />
=SA1.1 Activity Management= <br />
<!-- M. Krakowian, P. Solagna --><br />
<br />
MEETINGS<br />
<br />
ACTIVITIES<br />
<br />
=SA1.2 Security= <br />
<!-- D. Kelsey --><br />
<br />
= SA1.3 Staged rollout =<br />
<!-- J. Pina --><br />
<br />
=SA1.3 Integration=<br />
<!-- M. Krakowian --><br />
<br />
=SA1.4 Central tools= <br />
<!--E. Imamagic --><br />
<br />
* fedcloud<br />
* SAM Update-22 campaign <br />
** current status is 93% done:<br />
*** Update-22: 43<br />
*** Update-19: 2<br />
*** Unavailable: 1<br />
* Meetings<br />
** weekly fedcloud meeting - presented the status of monitoring activities<br />
** SAM migration meeting (https://indico.egi.eu/indico/conferenceDisplay.py?confId=2092)<br />
<br />
=SA1.5 Accounting= <br />
'''<!--S. Pullinger--> Repository '''<br />
<br />
'''<!--S. Pullinger--> Portal'''<br />
<br />
=SA1.6 Helpdesk= <br />
<!-- G. Grein --><br />
* Implementation and testing of CMS integration into GGUS<br />
* Preparing next GGUS release<br />
* Testing new release on test instance<br />
* Preparing next AB<br />
* Ticket monitoring<br />
<br />
=SA1.7 Support=<br />
<!-- R. Trompert --><br />
<br />
== Software Support ==<br />
<!-- A Krenek --><br />
<br />
{| class="wikitable"<br />
|-<br />
! DMSU tickets flow Mar 16 -- 22<br />
|-<br />
| assigned <br />
| 7<br />
|-<br />
| back to tpm <br />
| 0<br />
|-<br />
| reassigned to 3rd level <br />
| 6<br />
|-<br />
| solved <br />
| 1<br />
|}<br />
<br />
{| class="wikitable"<br />
|-<br />
! open DMSU tickets status<br />
|-<br />
| assigned <br />
| 0<br />
|-<br />
| in progress <br />
| 2<br />
|-<br />
| waiting for reply <br />
| 2<br />
|-<br />
| on hold <br />
| 2<br />
|}<br />
<br />
=SA1.8 Availability and core services=<br />
<!--P. Korosoglou--><br />
<br />
* Final A/R reports for Feb 2014 published<br />
* Problem in VOMS-Admin interface resolved<br />
<br />
== Documentation ==<br />
<!-- M. Krakowian --><br />
<br />
= Meetings=<br />
<!--all--></div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Sa1_2014-03-18&diff=65619EGI-InSPIRE:Sa1 2014-03-182014-03-18T16:43:34Z<p>Pkoro: /* SA1.8 Availability and core services */</p>
<hr />
<div>{{Template:Op menubar}} <br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}} <br />
[[Category:SA1 weekly report]]<br />
=Progress of SA1 issues= <br />
<!-- M. Krakowian--><br />
Nothing new to report.<br />
<br />
=Milestones/Deliverables=<br />
<!-- M. Krakowian --><br />
<br />
<br />
=SA1.1 Activity Management= <br />
<!-- M. Krakowian, P. Solagna --><br />
<br />
MEETINGS<br />
<br />
ACTIVITIES<br />
<br />
=SA1.2 Security= <br />
<!-- D. Kelsey --><br />
* usual ongoing operational tasks - tracking incidents and vulnerabilities<br />
* preparing for security workshop and talks at next weeks ISGC2014 conference<br />
<br />
= SA1.3 Staged rollout =<br />
<!-- J. Pina --><br />
* WN tarball (UMD-3) was put to SR.<br />
* glexec v. 1.2.2<br />
* dpm-yaim v. 1.8.7<br />
<br />
=SA1.3 Integration=<br />
<!-- M. Krakowian --><br />
<br />
=SA1.4 Central tools= <br />
<!--E. Imamagic --><br />
<br />
* ActiveMQ brokers migration <br />
** added missing apel-reports user on new brokers (GGUS #101980)<br />
* fedcloud<br />
** three tests added to Operations tests, Operations portal configured to support alarms from cloudmon.egi.eu (GGUS #101714)<br />
** deployed new version of OCCI CLI (4.2.2)<br />
** added tests for Brokers (eu.egi.cloud.broker.compss, u.egi.cloud.broker.vmdirac )<br />
* midmon<br />
** fixed the issue with alarms not being sent to dashboard<br />
** modified the eu.egi.sec.ARC-EMI-2 test<br />
** modified the eu.egi.sec.dCache-SHA-2 test to ignore everything >= 2.6.0<br />
** EMI-2 tests and GLUE2-Validate test added to Operations tests<br />
* SAM Update-22 campaign <br />
** current status is 91% done:<br />
*** Update-22: 42<br />
*** Update-19: 3<br />
*** Unavailable: 1<br />
* Meetings<br />
** weekly fedcloud meeting - presented the status of monitoring activities<br />
** SAM migration meeting (https://indico.egi.eu/indico/conferenceDisplay.py?confId=2092)<br />
<br />
=SA1.5 Accounting= <br />
'''<!--S. Pullinger--> Repository '''<br />
<br />
'''<!--S. Pullinger--> Portal'''<br />
<br />
=SA1.6 Helpdesk= <br />
<!-- G. Grein --><br />
* Implementation and testing of CMS integration into GGUS<br />
* Preparing next GGUS release<br />
* Ticket monitoring<br />
<br />
=SA1.7 Support=<br />
<!-- R. Trompert --><br />
<br />
== Software Support ==<br />
<!-- A Krenek --><br />
<br />
<br />
=SA1.8 Availability and core services=<br />
<!--P. Korosoglou--><br />
<br />
* Handling of recomputation requests for Feb 2014<br />
* Problem in January reports noticed and followed up. <br />
<br />
== Documentation ==<br />
<!-- M. Krakowian --><br />
<br />
= Meetings=<br />
<!--all--></div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Sa1_2014-03-18&diff=65618EGI-InSPIRE:Sa1 2014-03-182014-03-18T16:43:05Z<p>Pkoro: /* SA1.8 Availability and core services */</p>
<hr />
<div>{{Template:Op menubar}} <br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}} <br />
[[Category:SA1 weekly report]]<br />
=Progress of SA1 issues= <br />
<!-- M. Krakowian--><br />
Nothing new to report.<br />
<br />
=Milestones/Deliverables=<br />
<!-- M. Krakowian --><br />
<br />
<br />
=SA1.1 Activity Management= <br />
<!-- M. Krakowian, P. Solagna --><br />
<br />
MEETINGS<br />
<br />
ACTIVITIES<br />
<br />
=SA1.2 Security= <br />
<!-- D. Kelsey --><br />
* usual ongoing operational tasks - tracking incidents and vulnerabilities<br />
* preparing for security workshop and talks at next weeks ISGC2014 conference<br />
<br />
= SA1.3 Staged rollout =<br />
<!-- J. Pina --><br />
* WN tarball (UMD-3) was put to SR.<br />
* glexec v. 1.2.2<br />
* dpm-yaim v. 1.8.7<br />
<br />
=SA1.3 Integration=<br />
<!-- M. Krakowian --><br />
<br />
=SA1.4 Central tools= <br />
<!--E. Imamagic --><br />
<br />
* ActiveMQ brokers migration <br />
** added missing apel-reports user on new brokers (GGUS #101980)<br />
* fedcloud<br />
** three tests added to Operations tests, Operations portal configured to support alarms from cloudmon.egi.eu (GGUS #101714)<br />
** deployed new version of OCCI CLI (4.2.2)<br />
** added tests for Brokers (eu.egi.cloud.broker.compss, u.egi.cloud.broker.vmdirac )<br />
* midmon<br />
** fixed the issue with alarms not being sent to dashboard<br />
** modified the eu.egi.sec.ARC-EMI-2 test<br />
** modified the eu.egi.sec.dCache-SHA-2 test to ignore everything >= 2.6.0<br />
** EMI-2 tests and GLUE2-Validate test added to Operations tests<br />
* SAM Update-22 campaign <br />
** current status is 91% done:<br />
*** Update-22: 42<br />
*** Update-19: 3<br />
*** Unavailable: 1<br />
* Meetings<br />
** weekly fedcloud meeting - presented the status of monitoring activities<br />
** SAM migration meeting (https://indico.egi.eu/indico/conferenceDisplay.py?confId=2092)<br />
<br />
=SA1.5 Accounting= <br />
'''<!--S. Pullinger--> Repository '''<br />
<br />
'''<!--S. Pullinger--> Portal'''<br />
<br />
=SA1.6 Helpdesk= <br />
<!-- G. Grein --><br />
* Implementation and testing of CMS integration into GGUS<br />
* Preparing next GGUS release<br />
* Ticket monitoring<br />
<br />
=SA1.7 Support=<br />
<!-- R. Trompert --><br />
<br />
== Software Support ==<br />
<!-- A Krenek --><br />
<br />
<br />
=SA1.8 Availability and core services=<br />
<!--P. Korosoglou--><br />
<br />
* Handling of recomputation requests for Feb 2014<br />
<br />
<br />
== Documentation ==<br />
<!-- M. Krakowian --><br />
<br />
= Meetings=<br />
<!--all--></div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Sa1_2014-03-11&diff=65481EGI-InSPIRE:Sa1 2014-03-112014-03-11T14:27:10Z<p>Pkoro: /* SA1.8 Availability and core services */</p>
<hr />
<div>{{Template:Op menubar}} <br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}} <br />
[[Category:SA1 weekly report]]<br />
=Progress of SA1 issues= <br />
<!-- M. Krakowian--><br />
Nothing new to report.<br />
<br />
=Milestones/Deliverables=<br />
<!-- M. Krakowian --><br />
<br />
<br />
=SA1.1 Activity Management= <br />
<!-- M. Krakowian, P. Solagna --><br />
<br />
MEETINGS<br />
<br />
ACTIVITIES<br />
<br />
=SA1.2 Security= <br />
<!-- D. Kelsey --><br />
<br />
= SA1.3 Staged rollout =<br />
<!-- J. Pina --><br />
<br />
* Making last EMI-3 update [http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-14-03-03-2014-v-3-7-2-1#WMS_server_v_3_6_3_and_WMS_clien 14] available into UMD repository<br />
* WMS 3.6.3 in staged rollout<br />
<br />
=SA1.3 Integration=<br />
<!-- M. Krakowian --><br />
<br />
=SA1.4 Central tools= <br />
<!--E. Imamagic --><br />
<br />
* ActiveMQ brokers migration <br />
** new brokers added to GOCDB and opsmon<br />
** resolving issues with broker network on Monday March 10th<br />
* fedcloud<br />
** integrated new OCCI probe provided by Boris Parak<br />
** added documentation for all fedcloud probes on cloudmon.egi.eu: [[Cloud SAM tests]]<br />
* GOCDB<br />
** outage on Tuesday - Wednesday, March 4th - 5th: the DB server failed and next day intermittent site networking issues occurred. <br />
* midmon<br />
** added EMI-2 tests for DPM and StoRM: [[MW_SAM_tests#EMI-2_tests]]<br />
* ops-monitor<br />
** added new alias opsmon.egi.eu -> ops-monitor.cern.ch, alias will be used for smooth migration of opsmon to Croatia<br />
** tracking issues with ngi.SAM instances in GOCDB continued: [[SAM_Instances#Analysis_of_SAM_instances_in_GOCDB|SAM in GOCDB]]<br />
* SAM Update-22 campaign <br />
** current status is 87% done:<br />
*** Update-22: 40<br />
*** Update-19: 4<br />
*** Unavailable: 2<br />
* Meetings<br />
** weekly fedcloud meeting - presented the status of monitoring activities<br />
<br />
=SA1.5 Accounting= <br />
'''<!--S. Pullinger--> Repository '''<br />
<br />
'''<!--S. Pullinger--> Portal'''<br />
<br />
=SA1.6 Helpdesk= <br />
<!-- G. Grein --><br />
* Implementation and testing of CMS integration into GGUS<br />
* Preparing next GGUS release<br />
* Finishing post-release tasks<br />
* Ticket monitoring<br />
<br />
=SA1.7 Support=<br />
<!-- R. Trompert --><br />
<br />
== Software Support ==<br />
<!-- A Krenek --><br />
<br />
<br />
=SA1.8 Availability and core services=<br />
<!--P. Korosoglou--><br />
<br />
* Received A/R and Top-BDII reports for February 2014 (initial publication made)<br />
** Problem with Top-BDII reports identified. Waiting for updated version<br />
* Follow up on GGUS ticket on registering robot certificate with Dteam VO [[https://ggus.eu/index.php?mode=ticket_info&ticket_id=100994]]<br />
* Created new Dteam Group AfricaArabia [[https://ggus.eu/index.php?mode=ticket_info&ticket_id=101661]]<br />
* GlueValidator package updated on midmon.egi.eu instance. <br />
<br />
== Documentation ==<br />
<!-- M. Krakowian --><br />
<br />
= Meetings=<br />
<!--all--></div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Sa1_2014-03-11&diff=65480EGI-InSPIRE:Sa1 2014-03-112014-03-11T14:23:35Z<p>Pkoro: /* SA1.8 Availability and core services */</p>
<hr />
<div>{{Template:Op menubar}} <br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}} <br />
[[Category:SA1 weekly report]]<br />
=Progress of SA1 issues= <br />
<!-- M. Krakowian--><br />
Nothing new to report.<br />
<br />
=Milestones/Deliverables=<br />
<!-- M. Krakowian --><br />
<br />
<br />
=SA1.1 Activity Management= <br />
<!-- M. Krakowian, P. Solagna --><br />
<br />
MEETINGS<br />
<br />
ACTIVITIES<br />
<br />
=SA1.2 Security= <br />
<!-- D. Kelsey --><br />
<br />
= SA1.3 Staged rollout =<br />
<!-- J. Pina --><br />
<br />
* Making last EMI-3 update [http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-14-03-03-2014-v-3-7-2-1#WMS_server_v_3_6_3_and_WMS_clien 14] available into UMD repository<br />
* WMS 3.6.3 in staged rollout<br />
<br />
=SA1.3 Integration=<br />
<!-- M. Krakowian --><br />
<br />
=SA1.4 Central tools= <br />
<!--E. Imamagic --><br />
<br />
* ActiveMQ brokers migration <br />
** new brokers added to GOCDB and opsmon<br />
** resolving issues with broker network on Monday March 10th<br />
* fedcloud<br />
** integrated new OCCI probe provided by Boris Parak<br />
** added documentation for all fedcloud probes on cloudmon.egi.eu: [[Cloud SAM tests]]<br />
* GOCDB<br />
** outage on Tuesday - Wednesday, March 4th - 5th: the DB server failed and next day intermittent site networking issues occurred. <br />
* midmon<br />
** added EMI-2 tests for DPM and StoRM: [[MW_SAM_tests#EMI-2_tests]]<br />
* ops-monitor<br />
** added new alias opsmon.egi.eu -> ops-monitor.cern.ch, alias will be used for smooth migration of opsmon to Croatia<br />
** tracking issues with ngi.SAM instances in GOCDB continued: [[SAM_Instances#Analysis_of_SAM_instances_in_GOCDB|SAM in GOCDB]]<br />
* SAM Update-22 campaign <br />
** current status is 87% done:<br />
*** Update-22: 40<br />
*** Update-19: 4<br />
*** Unavailable: 2<br />
* Meetings<br />
** weekly fedcloud meeting - presented the status of monitoring activities<br />
<br />
=SA1.5 Accounting= <br />
'''<!--S. Pullinger--> Repository '''<br />
<br />
'''<!--S. Pullinger--> Portal'''<br />
<br />
=SA1.6 Helpdesk= <br />
<!-- G. Grein --><br />
* Implementation and testing of CMS integration into GGUS<br />
* Preparing next GGUS release<br />
* Finishing post-release tasks<br />
* Ticket monitoring<br />
<br />
=SA1.7 Support=<br />
<!-- R. Trompert --><br />
<br />
== Software Support ==<br />
<!-- A Krenek --><br />
<br />
<br />
=SA1.8 Availability and core services=<br />
<!--P. Korosoglou--><br />
<br />
* Received A/R and Top-BDII reports for February 2014 (initial publication made)<br />
** Problem with Top-BDII reports identified. Waiting for updated version<br />
* Follow up on GGUS ticket on registering robot certificate with Dteam VO [[https://ggus.eu/index.php?mode=ticket_info&ticket_id=100994]]<br />
* Created new Dteam Group AfricaArabia [[https://ggus.eu/index.php?mode=ticket_info&ticket_id=101661]]<br />
<br />
== Documentation ==<br />
<!-- M. Krakowian --><br />
<br />
= Meetings=<br />
<!--all--></div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Sa1_2014-03-11&diff=65479EGI-InSPIRE:Sa1 2014-03-112014-03-11T14:22:10Z<p>Pkoro: /* SA1.8 Availability and core services */</p>
<hr />
<div>{{Template:Op menubar}} <br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}} <br />
[[Category:SA1 weekly report]]<br />
=Progress of SA1 issues= <br />
<!-- M. Krakowian--><br />
Nothing new to report.<br />
<br />
=Milestones/Deliverables=<br />
<!-- M. Krakowian --><br />
<br />
<br />
=SA1.1 Activity Management= <br />
<!-- M. Krakowian, P. Solagna --><br />
<br />
MEETINGS<br />
<br />
ACTIVITIES<br />
<br />
=SA1.2 Security= <br />
<!-- D. Kelsey --><br />
<br />
= SA1.3 Staged rollout =<br />
<!-- J. Pina --><br />
<br />
* Making last EMI-3 update [http://www.eu-emi.eu/releases/emi-3-monte-bianco/updates/-/asset_publisher/5Na8/content/update-14-03-03-2014-v-3-7-2-1#WMS_server_v_3_6_3_and_WMS_clien 14] available into UMD repository<br />
* WMS 3.6.3 in staged rollout<br />
<br />
=SA1.3 Integration=<br />
<!-- M. Krakowian --><br />
<br />
=SA1.4 Central tools= <br />
<!--E. Imamagic --><br />
<br />
* ActiveMQ brokers migration <br />
** new brokers added to GOCDB and opsmon<br />
** resolving issues with broker network on Monday March 10th<br />
* fedcloud<br />
** integrated new OCCI probe provided by Boris Parak<br />
** added documentation for all fedcloud probes on cloudmon.egi.eu: [[Cloud SAM tests]]<br />
* GOCDB<br />
** outage on Tuesday - Wednesday, March 4th - 5th: the DB server failed and next day intermittent site networking issues occurred. <br />
* midmon<br />
** added EMI-2 tests for DPM and StoRM: [[MW_SAM_tests#EMI-2_tests]]<br />
* ops-monitor<br />
** added new alias opsmon.egi.eu -> ops-monitor.cern.ch, alias will be used for smooth migration of opsmon to Croatia<br />
** tracking issues with ngi.SAM instances in GOCDB continued: [[SAM_Instances#Analysis_of_SAM_instances_in_GOCDB|SAM in GOCDB]]<br />
* SAM Update-22 campaign <br />
** current status is 87% done:<br />
*** Update-22: 40<br />
*** Update-19: 4<br />
*** Unavailable: 2<br />
* Meetings<br />
** weekly fedcloud meeting - presented the status of monitoring activities<br />
<br />
=SA1.5 Accounting= <br />
'''<!--S. Pullinger--> Repository '''<br />
<br />
'''<!--S. Pullinger--> Portal'''<br />
<br />
=SA1.6 Helpdesk= <br />
<!-- G. Grein --><br />
* Implementation and testing of CMS integration into GGUS<br />
* Preparing next GGUS release<br />
* Finishing post-release tasks<br />
* Ticket monitoring<br />
<br />
=SA1.7 Support=<br />
<!-- R. Trompert --><br />
<br />
== Software Support ==<br />
<!-- A Krenek --><br />
<br />
<br />
=SA1.8 Availability and core services=<br />
<!--P. Korosoglou--><br />
<br />
* Received A/R and Top-BDII reports for February 2014 (initial publication made)<br />
* Follow up on GGUS ticket [[https://ggus.eu/index.php?mode=ticket_info&ticket_id=100994]]<br />
* Created new Dteam Group AfricaArabia [[https://ggus.eu/index.php?mode=ticket_info&ticket_id=101661]]<br />
<br />
== Documentation ==<br />
<!-- M. Krakowian --><br />
<br />
= Meetings=<br />
<!--all--></div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Sa1_2014-03-04&diff=65380EGI-InSPIRE:Sa1 2014-03-042014-03-05T16:20:48Z<p>Pkoro: /* SA1.8 Availability and core services */</p>
<hr />
<div>{{Template:Op menubar}} <br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}} <br />
[[Category:SA1 weekly report]]<br />
=Progress of SA1 issues= <br />
<!-- M. Krakowian--><br />
Nothing new to report.<br />
<br />
=Milestones/Deliverables=<br />
<!-- M. Krakowian --><br />
* MS129 Quarterly Report - PM46<br />
* D4.10 Annual Report on the EGI Production Infrastructure. - PM47<br />
<br />
=SA1.1 Activity Management= <br />
<!-- M. Krakowian, P. Solagna --><br />
MEETINGS<br />
* JAR1 meeting<br />
* Fed cloud call<br />
* GGUS AB <br />
* OMB<br />
* Biovel EGI call<br />
<br />
ACTIVITIES<br />
* Follow up with the DIRAC pilot requirements<br />
* handling of GGUS tickets<br />
* VO validation/decommissioning activities <br />
* GGUS SU QoS declaration campaign<br />
* preparing EMI2 decommission campaign<br />
* coordinating task handover after PY4<br />
* Review of MoU with China ROC<br />
<br />
=SA1.2 Security= <br />
<!-- D. Kelsey --><br />
* usual ongoing operational duties tracking incidents and vulnerabilities<br />
* production of and presentation of Cloud provider questionnaires at OMB<br />
* planning security events at ISGC2014 and EGI CF<br />
* ongoing work on monitoring and emergency suspension<br />
<br />
= SA1.3 Staged rollout =<br />
<!-- J. Pina --><br />
<br />
=SA1.3 Integration=<br />
<!-- M. Krakowian --><br />
* QCG, ARC, UNICORE, Globus accounting campaign<br />
* discussing with XSEDE next integrations steps<br />
<br />
=SA1.4 Central tools= <br />
<!--E. Imamagic --><br />
<br />
* ActiveMQ brokers migration <br />
** broker network reconfigured to include two new instance on Thursday February 27th<br />
* GOCDB<br />
** GOCDBv5.2 was released on February 26th. This version adds an extensibility mechanism which allows Services, ServiceGroups and Sites to be extended using custom key-value pairs (following the GLUE2 extensibility mechanism).<br />
* ops-monitor<br />
** analyzing issue with broken org.nagiosexchange.GGUS-WebCheck test: https://ggus.eu/?mode=ticket_info&ticket_id=101651<br />
* SAM Update-22 campaign <br />
** tracking issues with ngi.SAM instances in GOCDB continued: [[SAM_Instances#Analysis_of_SAM_instances_in_GOCDB|SAM in GOCDB]]<br />
** current status is 80% done:<br />
*** Update-22: 38<br />
*** Update-19: 5<br />
*** Unavailable: 4<br />
* Meetings<br />
** OMB on Thursday February 27th - presented the status of ActiveMQ brokers & SAM migration<br />
** BioVel meeting - participation in discussion about SAM monitoring system<br />
<br />
=SA1.5 Accounting= <br />
'''<!--S. Pullinger--> Repository '''<br />
<br />
'''<!--S. Pullinger--> Portal'''<br />
<br />
<br />
''' ARC, QCG, Unicore, Globus campaign'''<br />
<br />
QCG: There are 9 QCG services registered at 7 sites, 6 in Poland and 1 in Byelorusse. Of these, 3 are publishing to APEL. Of the 6 others, 3 are at PNSC which I would expect to be active. <br />
<br />
Globus: We still haven't fully tested the Globus solution. I have contacted Helmut asking him to kickstart the work again. I have yet to push for better documentation.<br />
<br />
Unicore: I approached Juelich to be the first Unicore test site.<br />
<br />
=SA1.6 Helpdesk= <br />
<!-- G. Grein --><br />
* Implementation and testing of CMS integration into GGUS<br />
* GGUS release<br />
* GGUS-AB<br />
* Ticket monitoring<br />
<br />
=SA1.7 Support=<br />
<!-- R. Trompert --><br />
* The usual dashboard work and ticket handling.<br />
<br />
== Software Support ==<br />
<!-- A Krenek --><br />
<br />
=SA1.8 Availability and core services=<br />
<!--P. Korosoglou--><br />
<br />
* A/R recalculations handled and publication of results for Feb 2014 (ongoing)<br />
* Communications with RA in Albania regarding EGI catch all CA<br />
<br />
<br />
== Documentation ==<br />
<!-- M. Krakowian --><br />
nothing to report<br />
<br />
= Meetings=<br />
<!--all--></div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Sa1_2014-02-25&diff=64991EGI-InSPIRE:Sa1 2014-02-252014-02-25T15:25:53Z<p>Pkoro: /* SA1.8 Availability and core services */</p>
<hr />
<div>{{Template:Op menubar}} <br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}} <br />
[[Category:SA1 weekly report]]<br />
=Progress of SA1 issues= <br />
<!-- M. Krakowian--><br />
Nothing new to report.<br />
<br />
=Milestones/Deliverables=<br />
<!-- M. Krakowian --><br />
<br />
<br />
=SA1.1 Activity Management= <br />
<!-- M. Krakowian, P. Solagna --><br />
<br />
MEETINGS<br />
<br />
ACTIVITIES<br />
<br />
=SA1.2 Security= <br />
<!-- D. Kelsey --><br />
* usual list of ongoing operational tasks<br />
* Prepare for EGI CF and ISGC 2014<br />
* Revise MS246 milestone document after reviewers comments<br />
<br />
= SA1.3 Staged rollout =<br />
<!-- J. Pina --><br />
<br />
* Release of the fifth update of UMD [http://repository.egi.eu/2014/02/20/release-umd-3-5-0/ 3.5.0]<br />
<br />
=SA1.3 Integration=<br />
<!-- M. Krakowian --><br />
<br />
=SA1.4 Central tools= <br />
<!--E. Imamagic --><br />
<br />
* Operations Portal<br />
** Candidate Release 3.0 was released on February 20th<br />
* ActiveMQ brokers migration<br />
** two new instances deployed in Croatia and Greece<br />
** connection to production instances is scheduled for Thursday, 27th of February<br />
* SAM migration<br />
** CNRS instance is working fine<br />
** comparison of results between CERN and CNRS will be performed at beginning of March<br />
* EMI-2 campaign<br />
** added two new tests: [[MW_Nagios_tests#EMI-2_tests|EMI-2 tests]]<br />
* SAM Update-22 campaign<br />
** tracking issues with ngi.SAM instances in GOCDB continued: [[SAM_Instances#Analysis_of_SAM_instances_in_GOCDB|SAM in GOCDB]]<br />
** current status is 74% done:<br />
*** Update-22: 35<br />
*** Update-19: 7<br />
*** Unavailable: 5<br />
<br />
=SA1.5 Accounting= <br />
'''<!--S. Pullinger--> Repository '''<br />
<br />
'''<!--S. Pullinger--> Portal'''<br />
<br />
=SA1.6 Helpdesk= <br />
<!-- G. Grein --><br />
* Implementation and testing of CMS integration into GGUS<br />
* Testing merge of GGUS and xGUS structures<br />
* Preparing next release<br />
* Ticket monitoring<br />
<br />
=SA1.7 Support=<br />
<!-- R. Trompert --><br />
<br />
== Software Support ==<br />
<!-- A Krenek --><br />
<br />
<br />
=SA1.8 Availability and core services=<br />
<!--P. Korosoglou--><br />
<br />
* EGI Catch-all operations<br />
* Handling of recomputations for A/R tables for January 2014 (waiting to receive final tables)<br />
<br />
== Documentation ==<br />
<!-- M. Krakowian --><br />
<br />
= Meetings=<br />
<!--all--></div>Pkorohttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Sa1_2014-02-18&diff=64843EGI-InSPIRE:Sa1 2014-02-182014-02-19T06:50:53Z<p>Pkoro: /* SA1.8 Availability and core services */</p>
<hr />
<div>{{Template:Op menubar}} <br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}} <br />
[[Category:SA1 weekly report]]<br />
=Progress of SA1 issues= <br />
<!-- M. Krakowian--><br />
Nothing new to report.<br />
<br />
=Milestones/Deliverables=<br />
<!-- M. Krakowian --><br />
* MS129 Quarterly Report - PM46<br />
* D4.10 Annual Report on the EGI Production Infrastructure. - PM47<br />
<br />
=SA1.1 Activity Management= <br />
<!-- M. Krakowian, P. Solagna --><br />
<br />
MEETINGS<br />
* Dirac4EGI<br />
* CVMFS call<br />
<br />
ACTIVITIES<br />
* Follow up with the DIRAC pilot requirements<br />
* Preparing QR15 <br />
* handling of GGUS tickets<br />
* VO validation/decommissioning activities <br />
* GGUS SU QoS declaration campaign<br />
* Investigation of new ava/rel threshold implementation <br />
<br />
=SA1.2 Security= <br />
<!-- D. Kelsey --><br />
* usual ongoing security operational duties<br />
* attend TF-CSIRT meeting in Zurich<br />
* plan for training at ISGC 2014<br />
* plan for security sessions at EGI CF<br />
<br />
= SA1.3 Staged rollout =<br />
<!-- J. Pina --><br />
<br />
* Release UMD-2 [http://repository.egi.eu/2014/02/11/release-umd-2-8-0/ 2.8.0] with a total of 3 products.<br />
* Preparation of the next UMD-3 release [https://wiki.egi.eu/w/index.php?title=UMD-3:UMD-3.5.0 3.5.0] with a total of 11 products.<br />
<br />
=SA1.3 Integration=<br />
<!-- M. Krakowian --><br />
* FedCloud resources certification campaign <br />
<br />
=SA1.4 Central tools= <br />
<!--E. Imamagic --><br />
<br />
* SAM Update-22 upgrade campaign<br />
** Analysis of SAM instances in GOCDB: https://wiki.egi.eu/wiki/SAM_Instances#Analysis_of_SAM_instances_in_GOCDB<br />
** Requested adding ch.cern.sam.SamCheckUpdate to Operations tests (https://ggus.eu/ws/ticket_info.php?ticket=101306)<br />
* GOCDB ugpraded to 5.2<br />
* Tracking down issues with alarms in dashboard raised by ops-monitor.cern.ch<br />
<br />
=SA1.5 Accounting= <br />
'''<!--S. Pullinger--> Repository '''<br />
<br />
'''<!--S. Pullinger--> Portal'''<br />
<br />
=SA1.6 Helpdesk= <br />
<!-- G. Grein --><br />
* Implementation and testing of CMS integration into GGUS<br />
* Testing merge of GGUS and xGUS structures<br />
* Preparing next release<br />
* Ticket monitoring<br />
<br />
=SA1.7 Support=<br />
<!-- R. Trompert --><br />
<br />
== Software Support ==<br />
<!-- A Krenek --><br />
<br />
<br />
=SA1.8 Availability and core services=<br />
<!--P. Korosoglou--><br />
<br />
* Support regarding x509 certificate requests for EGI catch all CA<br />
* A/R recalculations for Jan & Feb 2014<br />
<br />
<br />
== Documentation ==<br />
<!-- M. Krakowian --><br />
* EGI.eu SLA covering global tasks preparation<br />
<br />
= Meetings=<br />
<!--all--></div>Pkoro