https://wiki.egi.eu/w/api.php?action=feedcontributions&user=Mkrakowi&feedformat=atomEGIWiki - User contributions [en]2024-03-28T12:30:02ZUser contributionsMediaWiki 1.37.1https://wiki.egi.eu/w/index.php?title=PROC09_Resource_Centre_Registration_and_Certification&diff=40237PROC09 Resource Centre Registration and Certification2012-09-07T14:59:06Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}}&nbsp; {{TOC_right}} <br />
<br />
{| border="1"<br />
|-<br />
| '''Title''' <br />
| ''Resource Centre Registration and Certification Procedure''<br />
|-<br />
| '''Document link''' <br />
| https://wiki.egi.eu/wiki/PROC09<br />
|-<br />
| '''Version - last modified''' <br />
| 1.0 - 17 May 2011<br><br />
|-<br />
| '''Policy Group Acronym''' <br />
| ''OMB''<br />
|-<br />
| '''Policy Group Name''' <br />
| ''Operations Management Board''<br />
|-<br />
| '''Contact Person''' <br />
| operational-documentation@mailman.egi.eu<br />
|-<br />
| '''Document Status''' <br />
| ''APPROVED''<br />
|-<br />
| '''Approved Date''' <br />
| 17 May 2011<br><br />
|-<br />
| '''Procedure Statement''' <br />
| ''A procedure for the steps involved to both register and certify new Resource Centres (sites) in the EGI infrastructure. The certification step can also be used to re-certify suspended Resource Centres (sites).''<br />
|}<br />
<br />
= Resource Centre Registration and Certification Procedure =<br />
<br />
Certification is a prerequisite for a [[#Definitions|Resource Centre]] (aka site) to become part of a Resource Infrastructure such as a National Grid Initiative (NGI), an EIRO, or a multi-country Resource Infrastructure. <br />
<br />
This document describes the steps required <br />
<br />
#to register and certify a new Resource Centre, <br />
#to re-certify a Resource Centre which has been suspended.<br />
<br />
Note: A separate document provides the [[PROC11|process for decommissioning a Resource Centre]]. <br />
<br />
Through its parent Resource Infrastructure, a certified Resource Centre becomes a member of the EGI Resource Infrastructure to make resources available to international user communities. <br />
<br />
The main difference between a certified Resource Centre and an uncertified or test Resource Centre is that a certified Resource Centre provides and guarantees a minimum quality of service of the resources (currently expressed in terms of monthly availability and reliability): the certified Resource Centre must ensure problems are handled in a timely fashion and the certified Resource Centre must understand and adhere to a common set of policies and procedures. All the requirements can be found in the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
<br />
= Definitions =<br />
<br />
*'''Resource Centre''' refers to the definition in the "[https://documents.egi.eu/document/31 Resource Centre OLA]".<br />
<br />
:''In this document, the term "'''site'''" is '''deprecated''', and '''Resource Centre''' has been used in its place.''<br />
<br />
*Other entities involved in this procedure are defined in the [[Glossary|EGI Glossary]].<br />
<br />
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. <br />
<br />
= Entities involved in the procedure =<br />
<br />
<!-- There are minimally two sets of players involved in this procedure --> <br />
<br />
*'''Resource Centre Operations Manager''': person who is responsible for initiating the certification process by applying for membership to a Resource Infrastructure. <br />
*'''Resource Infrastructure Operations Manager''': person who is responsible for approving the integration of a new Resource Centre into the respective Infrastructure. <br />
*'''Operations Centre''': entity which is technically responsible for carrying out the Resource Centre certification part of the procedure, once the membership is approved.<br />
<br />
The Resource Infrastructure Operations Manager can determine with the Resource Centre Operations Manager the level of involvement of other actors. <br />
<br />
= Contact information =<br />
<br />
*EGI Operations: operations (at) mailman.egi.eu <br />
*EGI Resource infrastructure Providers are listed on the EGI [https://www.egi.eu/infrastructure/Resource-providers/index.html web site] <br />
*A list of EGI Operations Centres with their respective contact information is available from the [http://go.egi.eu/operations-centres GOCDB] <br />
*EGI CSIRT: egi-csirt-team (at) mailman.egi.eu<br />
<br />
= Actions and responsibilities =<br />
<br />
== Resource Centre Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is responsible for all Resource Centres within its respective jurisdiction (for example, an NGI is responsible for all Resource Centres in its country). For this reason, the Resource Centre Operations Manager of a new Resource Centre is REQUIRED <br />
#*to contact the respective NGI if the Resource Centre is located in Europe, <br />
#*to contact the respective Resource infrastructure Provider active in a relevant geographical area if the Resource Centre is outside Europe, about the intention of the Resource Centre to join the EGI infrastructure. If needed, EGI Operations can assist the Resource Centre Operations Manager to get in contact with the relevant partners (see the Contact information section).<br> <br />
#The Resource Centre Operations Manager is REQUIRED to provide the necessary Resource Centre information needed to complete the registration process, and he/she is responsible for its accuracy and maintenance.<br> <br />
#In order to be certified, the Resource Centre Operations Manager is responsible for reading, understanding and accepting the [https://documents.egi.eu/document/31 Resource Centre Operational Level Agreement], which defines the obligations of a Resource Centre and the commitment to deliver a minimum quality of service to its future users. Endorsement of the OLA implies - among other things - the acceptance of: <br />
#*the [https://documents.egi.eu/document/86 Grid Security Policy] <br />
#*the [https://documents.egi.eu/document/75 Grid Resource Centre Operations Policy] <br />
#*the [https://documents.egi.eu/document/76 Resource Centre Registration Security Policy] <br />
#*all other policies for all EGI participants from the [https://wiki.egi.eu/wiki/SPG:Documents Security Policy Group]<br />
<br />
== Resource Infrastructure Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is REQUIRED to be responsible for all Resource Centres within its respective jurisdiction. For example, an NGI is responsible for all Resource Centres in its respective country. <br />
#The Resource Infrastructure Operations Managers MUST attend Resource Centre certification applications and MUST provide feedback to the requesting partners in a timely manner to accept or reject the requests received. <br />
#If the Resource Centre needs to be certified, s/he MUST provide information to the Resource Centre Operations Manager about the Resource Centre OLA, and is responsible for keeping records of the Resource Centre Operations Manager agreement, as deemed suitable by the Resource infrastructure Provider (for example, through a signed e-mail agreement, a collection of signatories on a paper copy of the OLA, or other means). <br />
#For the case where a request is accepted, the Resource Infrastructure Operations Manager MUST contact the relevant Operations Centre to start the Resource Centre registration as a candidate for the certification procedure. Registration is only needed for the case of new Resource Centres.<br />
<br />
== Operations Centre ==<br />
<br />
#The Operations Centre is responsible for registering (if applicable) and for certifying the Resource Centre. <br />
#The Operations Centre is responsible for registering an accepted Resource Centre in the EGI configuration repository [[GOCDB|GOCDB]]. <br />
#The Operations Centre MUST collect the mandatory information specified by the Resource Centre registration procedure, and MUST accurately input the data supplied into the GOCDB. <br />
#The Operations Centre MUST integrate Resource Centre information in all operations tools as needed, such as the local NAGIOS server for monitoring of certified Resource Centres, the local helpdesk (if available) for the registration of the Resource Centre support staff, etc. <br />
#In the case of an existing Resource Centre that is resuming certification after suspension for security reasons, the Operations Centre MUST contact the EGI CSIRT to verify that all requested repair operations have been successfully applied to fix the issue. <br />
#*For other suspension cases, the Operations Center MUST ensure that the issue that caused the suspension has been resolved. <br />
#The Operations Centre is responsible for verifying that all tests during the 3 calendar day certification process are successfully passed. The Operations Centre SHOULD only proceed with changing the Resource Centre status in the GOCDB to ''certified'' if this condition is met.<br />
<br />
= Workflow =<br />
<br />
The various steps required by both the Resource Infrastructure Operations Manager and the Resource Centre Operations Manager are explained in the tables below. The first part for a '''new''' Resource Centre is the registration process. The actual certification process, in the second table, is applicable to both new and suspended Resource Centres. <br />
<br />
The general status flow that a Resource Centre is allowed to follow is illustrated by the following diagram. Information on Resource Centre status and on how to manipulate it is available from [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Changing_Site_Certification_Status GOCDB Documentation]. <br />
<br />
[[Image:SiteStatusFlow.png|300px|SiteStatusFlow.png]] <br />
<br />
<br> <br />
<br />
A Resource Centre '''cannot '''be in <br />
<br />
*'''Candidate '''state for '''more than two months''' <br />
*'''Suspended''' state for '''more than four months'''<br />
<br />
After this period the Resource Centre SHOULD be closed. <br />
<br />
== Resource Centre registration ==<br />
<br />
=== Requirements ===<br />
<br />
#A Resource Centre MUST be part of a Resource Infrastructure and gets operational services offered by a Operations Centre. If a provider is not yet available for your country, then an alternative existing Operations Centre can be contacted. A procedure exists for this, and it is documented in the [[PROC02|Operations Centre creation]] procedure. <!-- text extracted from the Resource Centre registration procedure, which will likely disappear in the future--> <br />
#To satisfy Grid security requirements during the registration procedure the following information must be collected. The comprehensive list of required information is available ([[Operations/HOWTO01|here]]). <br />
#*The full name of the Resource Centre. <br />
#*An abbreviated name for the Resource Centre, which must be unique within the Grid, and preferably globally unique. <br />
#*The name, email address and telephone number of the Resource Centre Operations Manager and Resource Centre Security Contact in accordance with the requirements of the [https://documents.egi.eu/document/75 Resource Centre Operations Policy]. <br />
#*The email address of a managed list for contact with Resource Centre Administrators at the Resource Centre. <!-- Resource Administrators replaced by Site Administrators--> <br />
#*The email address of a managed list for contact with the Resource Centre security incident response team. <!--# A signed copy of the Site (Resource Centre) Operations Policy (https://documents.egi.eu/document/75).--><br />
<br />
Notes: <br />
<br />
#If a Resource Centre wishes to leave the Grid or the Grid decides to remove the Resource Centre, the registration information MUST be kept by [[GOCDB|GOCDB]] for at least the same period defined for logging in the [https://documents.egi.eu/document/81 Traceability and Logging Policy]. Personal registration information of the Resource Centre Operations Manager and Security Contact of the Resource Centre leaving the Grid MUST NOT be retained for longer than one year. <!--"Review and acceptance procedures and any operational requirements should be documented in a Grid specific<br />
document describing the implementation of the Resource Centre Registration Procedure." Comment: a maintenance procedure is currently missing. To check: what are the operational requirements? --> <br />
#It is RECOMMENDED that email contacts for the Resource Centre Administrators and Security Officer(s) are mailing lists, and not individuals.The contacts information SHOULD be available at the moment of the Resource Centre registration in GOCDB.<br />
<br />
<br> <br />
<br />
=== Steps ===<br />
<br />
The following steps are only applicable if '''the Resource Centre is not already registered in GOCDB'''. They describe the steps for a Resource Centre Operations Manager that is requesting the respective Resource Centre to join the EGI infrastructure. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RC <br />
| <br />
#Contact your Resource Infrastructure Operations Manager (contact information is available at [http://www.egi.eu/community/resource-providers/ http://www.egi.eu/community/resource-providers/]). <br />
#Provide your Resource Infrastructure Operations Manager the required information according to the template available in the [[Operations/HOWTO01|Required information]] page.<br />
<br />
|- valign="top"<br />
| 1 <br />
| RP <br />
| <br />
#Parse the Resource Centre registration request, decide to accept or reject it, and communicate this result back to applicant. <br />
#If the Resource Centre is accepted, notify the relevant Operations Centre, handle the Resource Centre information received, and put the Operations Centre in contact with the Resource Centre Operations Manager.<br />
<br />
|- valign="top"<br />
| 2 <br />
| OC <br />
| <br />
#The following actions can be done in parallel: <br />
#*Forward all [[Operations/HOWTO02|necessary and required documentation]] to install and configure the Resource Centre services to the Resource Centre Operations Manager. <br />
#*Communicate with the Operations Manager to clarify any doubts or questions. Include the Operations Centre ROD, CSIRT,&nbsp; or help-desk teams in the step if necessary.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#Add the Resource Centre to the [https://goc.egi.eu/ GOCDB ]and flag it as "Candidate". Note that all users with a GOCDB role at regional level can add a Resource Centre in scope (this includes Operations Manager, deputy and regional staff). Currently, GOCDB applies the same permissions to all of the "regional level roles". <br />
#Notify the Resource Centre Operations Manager that he/she should request for [http://www.eugridpma.org/ grid certificate], register in [https://voms.hellasgrid.gr:8443/vo/dteam/vomrs Dteam VO], register in the [https://goc.egi.eu/ GOCDB ]and request the&nbsp;<br />
'Resource Centre Operations Manager' role. Approve it when done.<br />
<br />
#Notify the Resource Centre Operations Manager that person responsible for security should request for [http://www.eugridpma.org/ grid certificate], register in [https://voms.hellasgrid.gr:8443/vo/dteam/vomrs Dteam VO], register in the [https://goc.egi.eu/ GOCDB ]and request the&nbsp; <br />
'Resource Centre Security Officer' role. Approve it when done.<br />
<br />
|- valign="top"<br />
| 4 <br />
| RC <br />
| <br />
#Complete any missing information for the Resource Centre's entry in the GOCDB, including services that are to be integrated into the infrastructure. <br />
#Request in the GOCDB (or ask the relevant Resource Centre security staff to request) the mandatory Resource Centre Security Officer role. A security expert is the most appropriate actor for this role. See the [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Understanding_and_manipulating_roles GOCDB Input System User Documentation] for more information on roles. <br />
#Accept or deny all the requested roles under the Resource Centre scope. Note: If the Resource Centre Operations Manager can not approve roles, they should request the Operations Centre to do so. This is a current flaw in GOCDB. <br />
#Notify the Operations Centre that the Resource Centre information update is concluded.<br />
<br />
|- valign="top"<br />
| 5 <br />
| RC or OC <br />
| <br />
#Check whether the Resource Centre appears in the "Notified Site" field in [https://ggus.eu/ws/ticket_search.php https://ggus.eu/ws/ticket_search.php] <br />
#Note that this step should happen automatically when the Resource Centre is correctly entered into the GOCDB. If this is still not visible 2 days after the GOCDB entries have been created, the Operations Centre should be informed and should then contact GGUS administrators through [https://ggus.eu/pages/ticket.php GGUS]. <br />
#A new Resource Centre Administrator should register in GGUS ([https://ggus.eu/admin/get_account.php?accounttype=support https://ggus.eu/admin/get_account.php?accounttype=support]) but not specify any role, unless directed to by the Operations Centre.<br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the Resource Centre's information is correct (Resource Centre (site) roles and any other additional information.) <br />
#Check that contacts receive email (if they are mailing lists, check that outside EGI members are allowed to post there). Site administrator MUST reply to the test email.<br> <br />
#Check that the required services for a Resource Centre are properly registered. Note that for Resource Centre adopting APEL, by registering a new glite-APEL node in GOCDB as gLite-APEL service including the correct DN, the APEL broker Access Control List gets automatically updated and Resource Centres can start publishing usage records in about two hours (for more information see the [https://twiki.cern.ch/twiki/bin/view/EMI/Glite-APELInstallation gLite-APEL documentation]). <br />
#Check domain names and forward and reverse DNS.<br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#Any other Operations Centre-specific requirements (e.g. join a certain VO and/or mailing list, etc.)<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#If all previous actions have been completed with success, notify the Resource Centre Operations Manager that the Registration is completed, and contact the Resource Infrastructure Operations Manager to notify that a new candidate Resource Centre exists and is ready to be certified.<br />
<br />
|}<br />
<br />
After the successful completion of all these steps, the registration phase is completed and the Resource Centre is ready for the start of the <span class="il">certification</span> phase. <br />
<br />
== Resource Centre certification ==<br />
<br />
=== Requirements ===<br />
<br />
#The Resource Centre Certification procedure is only applicable for '''both Resource Centres in "Candidate" or "Suspended"''' status state.<br> <br />
#The following procedure is only applicable if '''the Resource Centre is already registered in GOCDB'''. <br />
#In order to enter certification the Resource Centre Operations Managers SHALL accept the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
#A Resource Centre can successfully pass certification only if the conditions required by the [https://documents.egi.eu/document/31 Resource Centre OLA] are met.<br />
<br />
=== Steps ===<br />
<br />
The following is a detailed description of the steps required for the transition from the "Uncertified" to the "Certified" state of the Resource Centre. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Resource Centre Operations Manager to request the subscription of the [https://documents.egi.eu/public/ShowDocument?docid=31 Resource Centre OLA].<br />
<br />
|- valign="top"<br />
| 1 <br />
| RC <br />
| <br />
#The Resource Centre Operations Manager notifies the Resource Infrastructure Operations Manager that the Resource Centre OLA is accepted (if the Resource Centre is has not already endorsed it before for example in case of a suspended Resource Centre), and the Resource Centre is ready to start certification.<br />
<br />
|- valign="top"<br />
| 2 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Operations Centre asking to start the certification process.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#If the Resource Centre is in the "Candidate" or "Suspended" state, then flag the Resource Centre as "Uncertified". If it was in the "Suspended" state then check that the reason for suspension has been cleared. If the suspension cause is a security issue, then the EGI CSIRT needs to be contacted to verify that all requested repair operations were successully applied by the Resource Centre Administrators to fix the issue that caused suspension. See [[SAM#Monitoring_uncertified_sites|instructions]] on how to monitor uncertified RCs.<br />
<br />
|- valign="top"<br />
| 4 <br />
| OC <br />
| <br />
#Add Resource Centre contact information to any regional mailing list and provide access to regional tools as required<br />
<br />
|- valign="top"<br />
| 5 <br />
| OC <br />
| <br />
#Check that the GIIS (gLite: BDII) is working, and publishing coherent values (There are detailed examples for how to do this in [[Operations/HOWTO03|GIIS/BDII check]]. ), namely: <br />
#*the correct NGI is being published in GlueSiteOtherInfo (see manual MAN01 [[MAN1 How to publish Site Information|How to Publish Site Information]]). <br />
#all services are registered in GOCDB according to the requirements of the [https://documents.egi.eu/document/31 Resource Centre OLA], these are published and ALSO that services published in the GOCDB are valid. <br />
#Glite, ARC:&nbsp;the [[OPS vo|OPS VO]] (monitoring) and the [[Dteam vo|DTEAM VO]] (troubleshooting) are configured and supported by the Resource Centre. UNICORE: infrastructure it is possible to configure monitoring using users and authorization methods deployed by the Operations Center to which this Resource Center belongs. <br />
#regional VOs are configured and supported as needed by the Operations Centre. <br />
#the Resource Centre is integrated in any regional tool as needed (for example, the regional accounting infrastructure if present).<br><br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the registered services are fully functional by performing manual tests. e.g. from the UI or the Operations Centre monitoring infrastructure for uncertified Resource Centres. Note that monitoring of uncertified Resource Centres through the NGI Nagios production service is possible ([[SAM#Monitoring_uncertified_sites|instructions]]). Contact the Resource Centre admins if there are problems, and ensure that they fix them. Include the ROD, CSIRT and help-desk teams if necessary. Iterate this step with the Resource Centre admins until tests pass successfully. The prime tests to check are: <br />
#*network connectivity. <br />
#*CE job submission. <br />
#*SE data transfer<br />
<br />
Details for submitting manual tests can be found at [[Operations/HOWTO04|Grid manual tests]]. <br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#If all preliminary tests are passed for 3 consecutive calendar days, declare an initial maintenance downtime and switch the Resource Centre status to Certified. This ensures that Resource Centre will appear in NAGIOS and GSTAT.<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#The downtime should not be closed until the Resource Centre appears in all operational tools '''and''' accounting data is properly published. The major tools that are relevant are: <br />
#*Regional NAGIOS (NAGIOS) <br />
#**And all Nagios tests are passed <br />
#*Operations [https://operations-portal.egi.eu/dashboard Dashboard] (Dashboard-Siteview) <br />
#*[http://gstat.egi.eu/ GSTAT] <br />
#**GSTAT is not in an error state. Note: There may be some problems with this tool and ARC Resource Centres. <br />
#*[https://grid-monitoring.cern.ch/myegi/ MyEGI]<br />
<br />
If there are problems with a specific tool, open GGUS tickets to the relevant Support Units. Wait at least two days after the switch to the ''Certified'' status to open the ticket, the propagation of the new status to the operational tools or the publication of accounting data may take one or two days.<br> <br />
<br />
|- valign="top"<br />
| 9 <br />
| OC <br />
| <br />
#Notify the Resource Centre Operations Manager that the Resource Centre is certified<br><br />
<br />
|- valign="top"<br />
| 10 <br />
| OC <br />
| <br />
#The NGI can broadcast that a new Resource Centre is now part of the EGI infrastructure. This step is OPTIONAL.<br />
<br />
|}<br />
<br />
After the successful completion of these steps, the Resource Centre is considered as "Certified". <!--<br />
= Revision history =<br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center"<br />
|-<br />
! Version <br />
! Authors <br />
! Date <br />
! Comments<br />
|-<br />
| 1.11 <br />
| Peter Solagna <br />
| 2011-05-17 <br />
| According to OMB comments: Modified the maximum duration of different site statuses. Removed the two days suggested period of downtime. The definition of Resource Centre will point to the Site OLA.&nbsp;<br />
|-<br />
| 1.1 <br />
| Peter Soalgna <br />
| 2011-05-1 <br />
| Updated cert step 6: downtime period lasts at least two days. Moved Cert step #10 to #4. Changed ''"If there is no suitable provider for your country, it maybe that the an Operations Centre MUST first be created."'' with ''"If a'' <br />
provider is not yet available for your country, then an alternative existing Operations Centre can be contacted."''. Now site responsiveness through its mail contacts is requested from the being of the certification process.'' <br />
<br />
|-<br />
| 0.8 <br />
| Tiziana Ferrari <br />
| 2011-03-11 <br />
| Updated introduction, adopted MUST SHALL etc. terminology, proposed some changes to terminology, added a section with a list of responsibilities, added a few comments into the text to request clarifications.<br />
|-<br />
| 0.7 <br />
| Vera Hansper <br />
| 2011-02-02 <br />
| Updated introduction to include roles, etc. and added required documentation link for policies<br />
|}<br />
--> <br> <br />
<br />
= Revision History =<br />
<br />
*7/09/2012: (editorial, M.&nbsp;Krakowian) typos and adding links where necessary, Gridview link removed from #8 'Site Certification'<br> <br />
*25/10/2011: (editorial, T. Ferrari) Replacement of RIP with "RP" standing for Resource infrastructure Provider<br />
<br />
{{Template:Creative_commons}} <br />
<br />
[[Category:Procedures]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=PROC09_Resource_Centre_Registration_and_Certification&diff=40236PROC09 Resource Centre Registration and Certification2012-09-07T14:25:05Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}}&nbsp; {{TOC_right}} <br />
<br />
{| border="1"<br />
|-<br />
| '''Title''' <br />
| ''Resource Centre Registration and Certification Procedure''<br />
|-<br />
| '''Document link''' <br />
| https://wiki.egi.eu/wiki/PROC09<br />
|-<br />
| '''Version - last modified''' <br />
| 1.0 - 17 May 2011<br><br />
|-<br />
| '''Policy Group Acronym''' <br />
| ''OMB''<br />
|-<br />
| '''Policy Group Name''' <br />
| ''Operations Management Board''<br />
|-<br />
| '''Contact Person''' <br />
| operational-documentation@mailman.egi.eu<br />
|-<br />
| '''Document Status''' <br />
| ''APPROVED''<br />
|-<br />
| '''Approved Date''' <br />
| 17 May 2011<br><br />
|-<br />
| '''Procedure Statement''' <br />
| ''A procedure for the steps involved to both register and certify new Resource Centres (sites) in the EGI infrastructure. The certification step can also be used to re-certify suspended Resource Centres (sites).''<br />
|}<br />
<br />
= Resource Centre Registration and Certification Procedure =<br />
<br />
Certification is a prerequisite for a [[#Definitions|Resource Centre]] (aka site) to become part of a Resource Infrastructure such as a National Grid Initiative (NGI), an EIRO, or a multi-country Resource Infrastructure. <br />
<br />
This document describes the steps required <br />
<br />
#to register and certify a new Resource Centre, <br />
#to re-certify a Resource Centre which has been suspended.<br />
<br />
Note: A separate document provides the [[PROC11|process for decommissioning a Resource Centre]]. <br />
<br />
Through its parent Resource Infrastructure, a certified Resource Centre becomes a member of the EGI Resource Infrastructure to make resources available to international user communities. <br />
<br />
The main difference between a certified Resource Centre and an uncertified or test Resource Centre is that a certified Resource Centre provides and guarantees a minimum quality of service of the resources (currently expressed in terms of monthly availability and reliability): the certified Resource Centre must ensure problems are handled in a timely fashion and the certified Resource Centre must understand and adhere to a common set of policies and procedures. All the requirements can be found in the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
<br />
= Definitions =<br />
<br />
*'''Resource Centre''' refers to the definition in the "[https://documents.egi.eu/document/31 Resource Centre OLA]".<br />
<br />
:''In this document, the term "'''site'''" is '''deprecated''', and '''Resource Centre''' has been used in its place.''<br />
<br />
*Other entities involved in this procedure are defined in the [[Glossary|EGI Glossary]].<br />
<br />
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. <br />
<br />
= Entities involved in the procedure =<br />
<br />
<!-- There are minimally two sets of players involved in this procedure --> <br />
<br />
*'''Resource Centre Operations Manager''': person who is responsible for initiating the certification process by applying for membership to a Resource Infrastructure. <br />
*'''Resource Infrastructure Operations Manager''': person who is responsible for approving the integration of a new Resource Centre into the respective Infrastructure. <br />
*'''Operations Centre''': entity which is technically responsible for carrying out the Resource Centre certification part of the procedure, once the membership is approved.<br />
<br />
The Resource Infrastructure Operations Manager can determine with the Resource Centre Operations Manager the level of involvement of other actors. <br />
<br />
= Contact information =<br />
<br />
*EGI Operations: operations (at) mailman.egi.eu <br />
*EGI Resource infrastructure Providers are listed on the EGI [https://www.egi.eu/infrastructure/Resource-providers/index.html web site] <br />
*A list of EGI Operations Centres with their respective contact information is available from the [http://go.egi.eu/operations-centres GOCDB] <br />
*EGI CSIRT: egi-csirt-team (at) mailman.egi.eu<br />
<br />
= Actions and responsibilities =<br />
<br />
== Resource Centre Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is responsible for all Resource Centres within its respective jurisdiction (for example, an NGI is responsible for all Resource Centres in its country). For this reason, the Resource Centre Operations Manager of a new Resource Centre is REQUIRED <br />
#*to contact the respective NGI if the Resource Centre is located in Europe, <br />
#*to contact the respective Resource infrastructure Provider active in a relevant geographical area if the Resource Centre is outside Europe, about the intention of the Resource Centre to join the EGI infrastructure. If needed, EGI Operations can assist the Resource Centre Operations Manager to get in contact with the relevant partners (see the Contact information section).<br> <br />
#The Resource Centre Operations Manager is REQUIRED to provide the necessary Resource Centre information needed to complete the registration process, and he/she is responsible for its accuracy and maintenance.<br> <br />
#In order to be certified, the Resource Centre Operations Manager is responsible for reading, understanding and accepting the [https://documents.egi.eu/document/31 Resource Centre Operational Level Agreement], which defines the obligations of a Resource Centre and the commitment to deliver a minimum quality of service to its future users. Endorsement of the OLA implies - among other things - the acceptance of: <br />
#*the [https://documents.egi.eu/document/86 Grid Security Policy] <br />
#*the [https://documents.egi.eu/document/75 Grid Resource Centre Operations Policy] <br />
#*the [https://documents.egi.eu/document/76 Resource Centre Registration Security Policy] <br />
#*all other policies for all EGI participants from the [https://wiki.egi.eu/wiki/SPG:Documents Security Policy Group]<br />
<br />
== Resource Infrastructure Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is REQUIRED to be responsible for all Resource Centres within its respective jurisdiction. For example, an NGI is responsible for all Resource Centres in its respective country. <br />
#The Resource Infrastructure Operations Managers MUST attend Resource Centre certification applications and MUST provide feedback to the requesting partners in a timely manner to accept or reject the requests received. <br />
#If the Resource Centre needs to be certified, s/he MUST provide information to the Resource Centre Operations Manager about the Resource Centre OLA, and is responsible for keeping records of the Resource Centre Operations Manager agreement, as deemed suitable by the Resource infrastructure Provider (for example, through a signed e-mail agreement, a collection of signatories on a paper copy of the OLA, or other means). <br />
#For the case where a request is accepted, the Resource Infrastructure Operations Manager MUST contact the relevant Operations Centre to start the Resource Centre registration as a candidate for the certification procedure. Registration is only needed for the case of new Resource Centres.<br />
<br />
== Operations Centre ==<br />
<br />
#The Operations Centre is responsible for registering (if applicable) and for certifying the Resource Centre. <br />
#The Operations Centre is responsible for registering an accepted Resource Centre in the EGI configuration repository [[GOCDB|GOCDB]]. <br />
#The Operations Centre MUST collect the mandatory information specified by the Resource Centre registration procedure, and MUST accurately input the data supplied into the GOCDB. <br />
#The Operations Centre MUST integrate Resource Centre information in all operations tools as needed, such as the local NAGIOS server for monitoring of certified Resource Centres, the local helpdesk (if available) for the registration of the Resource Centre support staff, etc. <br />
#In the case of an existing Resource Centre that is resuming certification after suspension for security reasons, the Operations Centre MUST contact the EGI CSIRT to verify that all requested repair operations have been successfully applied to fix the issue. <br />
#*For other suspension cases, the Operations Center MUST ensure that the issue that caused the suspension has been resolved. <br />
#The Operations Centre is responsible for verifying that all tests during the 3 calendar day certification process are successfully passed. The Operations Centre SHOULD only proceed with changing the Resource Centre status in the GOCDB to ''certified'' if this condition is met.<br />
<br />
= Workflow =<br />
<br />
The various steps required by both the Resource Infrastructure Operations Manager and the Resource Centre Operations Manager are explained in the tables below. The first part for a '''new''' Resource Centre is the registration process. The actual certification process, in the second table, is applicable to both new and suspended Resource Centres. <br />
<br />
The general status flow that a Resource Centre is allowed to follow is illustrated by the following diagram. Information on Resource Centre status and on how to manipulate it is available from [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Changing_Site_Certification_Status GOCDB Documentation]. <br />
<br />
[[Image:SiteStatusFlow.png|300px|SiteStatusFlow.png]] <br />
<br />
<br> <br />
<br />
A Resource Centre '''cannot '''be in <br />
<br />
*'''Candidate '''state for '''more than two months''' <br />
*'''Suspended''' state for '''more than four months'''<br />
<br />
After this period the Resource Centre SHOULD be closed. <br />
<br />
== Resource Centre registration ==<br />
<br />
=== Requirements ===<br />
<br />
#A Resource Centre MUST be part of a Resource Infrastructure and gets operational services offered by a Operations Centre. If a provider is not yet available for your country, then an alternative existing Operations Centre can be contacted. A procedure exists for this, and it is documented in the [[PROC02|Operations Centre creation]] procedure. <!-- text extracted from the Resource Centre registration procedure, which will likely disappear in the future--> <br />
#To satisfy Grid security requirements during the registration procedure the following information must be collected. The comprehensive list of required information is available ([[Operations/HOWTO01|here]]). <br />
#*The full name of the Resource Centre. <br />
#*An abbreviated name for the Resource Centre, which must be unique within the Grid, and preferably globally unique. <br />
#*The name, email address and telephone number of the Resource Centre Operations Manager and Resource Centre Security Contact in accordance with the requirements of the [https://documents.egi.eu/document/75 Resource Centre Operations Policy]. <br />
#*The email address of a managed list for contact with Resource Centre Administrators at the Resource Centre. <!-- Resource Administrators replaced by Site Administrators--> <br />
#*The email address of a managed list for contact with the Resource Centre security incident response team. <!--# A signed copy of the Site (Resource Centre) Operations Policy (https://documents.egi.eu/document/75).--><br />
<br />
Notes: <br />
<br />
#If a Resource Centre wishes to leave the Grid or the Grid decides to remove the Resource Centre, the registration information MUST be kept by [[GOCDB|GOCDB]] for at least the same period defined for logging in the [https://documents.egi.eu/document/81 Traceability and Logging Policy]. Personal registration information of the Resource Centre Operations Manager and Security Contact of the Resource Centre leaving the Grid MUST NOT be retained for longer than one year. <!--"Review and acceptance procedures and any operational requirements should be documented in a Grid specific<br />
document describing the implementation of the Resource Centre Registration Procedure." Comment: a maintenance procedure is currently missing. To check: what are the operational requirements? --> <br />
#It is RECOMMENDED that email contacts for the Resource Centre Administrators and Security Officer(s) are mailing lists, and not individuals.The contacts information SHOULD be available at the moment of the Resource Centre registration in GOCDB.<br />
<br />
<br> <br />
<br />
=== Steps ===<br />
<br />
The following steps are only applicable if '''the Resource Centre is not already registered in GOCDB'''. They describe the steps for a Resource Centre Operations Manager that is requesting the respective Resource Centre to join the EGI infrastructure. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RC <br />
| <br />
#Contact your Resource Infrastructure Operations Manager (contact information is available at [http://www.egi.eu/community/resource-providers/ http://www.egi.eu/community/resource-providers/]). <br />
#Provide your Resource Infrastructure Operations Manager the required information according to the template available in the [[Operations/HOWTO01|Required information]] page.<br />
<br />
|- valign="top"<br />
| 1 <br />
| RP <br />
| <br />
#Parse the Resource Centre registration request, decide to accept or reject it, and communicate this result back to applicant. <br />
#If the Resource Centre is accepted, notify the relevant Operations Centre, handle the Resource Centre information received, and put the Operations Centre in contact with the Resource Centre Operations Manager.<br />
<br />
|- valign="top"<br />
| 2 <br />
| OC <br />
| <br />
#The following actions can be done in parallel: <br />
#*Forward all [[Operations/HOWTO02|necessary and required documentation]] to install and configure the Resource Centre services to the Resource Centre Operations Manager. <br />
#*Communicate with the Operations Manager to clarify any doubts or questions. Include the Operations Centre ROD, CSIRT,&nbsp; or help-desk teams in the step if necessary.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#Add the Resource Centre to the [https://goc.egi.eu/ GOCDB ]and flag it as "Candidate". Note that all users with a GOCDB role at regional level can add a Resource Centre in scope (this includes Operations Manager, deputy and regional staff). Currently, GOCDB applies the same permissions to all of the "regional level roles". <br />
#Notify the Resource Centre Operations Manager that they should request for [http://www.eugridpma.org/ grid certificate], register in [https://voms.hellasgrid.gr:8443/vo/dteam/vomrs Dteam VO], register themself in the [https://goc.egi.eu/ GOCDB ]and request the Resource Centre Administrator role. Approve it when done.<br />
<br />
|- valign="top"<br />
| 4 <br />
| RC <br />
| <br />
#Complete any missing information for the Resource Centre's entry in the GOCDB, including services that are to be integrated into the infrastructure. <br />
#Request in the GOCDB (or ask the relevant Resource Centre security staff to request) the mandatory Resource Centre Security Officer role. A security expert is the most appropriate actor for this role. See the [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Understanding_and_manipulating_roles GOCDB Input System User Documentation] for more information on roles. <br />
#Accept or deny all the requested roles under the Resource Centre scope. Note: If the Resource Centre Operations Manager can not approve roles, they should request the Operations Centre to do so. This is a current flaw in GOCDB. <br />
#Notify the Operations Centre that the Resource Centre information update is concluded.<br />
<br />
|- valign="top"<br />
| 5 <br />
| RC or OC <br />
| <br />
#Check whether the Resource Centre appears in the "Notified Site" field in [https://ggus.eu/ws/ticket_search.php https://ggus.eu/ws/ticket_search.php] <br />
#Note that this step should happen automatically when the Resource Centre is correctly entered into the GOCDB. If this is still not visible 2 days after the GOCDB entries have been created, the Operations Centre should be informed and should then contact GGUS administrators through [https://ggus.eu/pages/ticket.php GGUS]. <br />
#A new Resource Centre Administrator should register in GGUS ([https://ggus.eu/admin/get_account.php?accounttype=support https://ggus.eu/admin/get_account.php?accounttype=support]) but not specify any role, unless directed to by the Operations Centre.<br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the Resource Centre's information is correct (Resource Centre (site) roles and any other additional information.) <br />
#Check that contacts receive email (if they are mailing lists, check that outside EGI members are allowed to post there). Site administrator MUST reply to the test email.<br> <br />
#Check that the required services for a Resource Centre are properly registered. Note that for Resource Centre adopting APEL, by registering a new glite-APEL node in GOCDB as gLite-APEL service including the correct DN, the APEL broker Access Control List gets automatically updated and Resource Centres can start publishing usage records in about two hours (for more information see the [https://twiki.cern.ch/twiki/bin/view/EMI/Glite-APELInstallation gLite-APEL documentation]). <br />
#Check domain names and forward and reverse DNS.<br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#Any other Operations Centre-specific requirements (e.g. join a certain VO and/or mailing list, etc.)<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#If all previous actions have been completed with success, notify the Resource Centre Operations Manager that the Registration is completed, and contact the Resource Infrastructure Operations Manager to notify that a new candidate Resource Centre exists and is ready to be certified.<br />
<br />
|}<br />
<br />
After the successful completion of all these steps, the registration phase is completed and the Resource Centre is ready for the start of the <span class="il">certification</span> phase. <br />
<br />
== Resource Centre certification ==<br />
<br />
=== Requirements ===<br />
<br />
#The Resource Centre Certification procedure is only applicable for '''both Resource Centres in "Candidate" or "Suspended"''' status state.<br> <br />
#The following procedure is only applicable if '''the Resource Centre is already registered in GOCDB'''. <br />
#In order to enter certification the Resource Centre Operations Managers SHALL accept the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
#A Resource Centre can successfully pass certification only if the conditions required by the [https://documents.egi.eu/document/31 Resource Centre OLA] are met.<br />
<br />
=== Steps ===<br />
<br />
The following is a detailed description of the steps required for the transition from the "Uncertified" to the "Certified" state of the Resource Centre. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Resource Centre Operations Manager to request the subscription of the [https://documents.egi.eu/public/ShowDocument?docid=31 Resource Centre OLA].<br />
<br />
|- valign="top"<br />
| 1 <br />
| RC <br />
| <br />
#The Resource Centre Operations Manager notifies the Resource Infrastructure Operations Manager that the Resource Centre OLA is accepted (if the Resource Centre is has not already endorsed it before for example in case of a suspended Resource Centre), and the Resource Centre is ready to start certification.<br />
<br />
|- valign="top"<br />
| 2 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Operations Centre asking to start the certification process.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#If the Resource Centre is in the "Candidate" or "Suspended" state, then flag the Resource Centre as "Uncertified". If it was in the "Suspended" state then check that the reason for suspension has been cleared. If the suspension cause is a security issue, then the EGI CSIRT needs to be contacted to verify that all requested repair operations were successully applied by the Resource Centre Administrators to fix the issue that caused suspension. See [[SAM#Monitoring_uncertified_sites|instructions]] on how to monitor uncertified RCs.<br />
<br />
|- valign="top"<br />
| 4 <br />
| OC <br />
| <br />
#Add Resource Centre contact information to any regional mailing list and provide access to regional tools as required<br />
<br />
|- valign="top"<br />
| 5 <br />
| OC <br />
| <br />
#Check that the GIIS (gLite: BDII) is working, and publishing coherent values (There are detailed examples for how to do this in [[Operations/HOWTO03|GIIS/BDII check]]. ), namely: <br />
#*the correct NGI is being published in GlueSiteOtherInfo (see manual MAN01 [[MAN1 How to publish Site Information|How to Publish Site Information]]). <br />
#all services are registered in GOCDB according to the requirements of the [https://documents.egi.eu/document/31 Resource Centre OLA], these are published and ALSO that services published in the GOCDB are valid. <br />
#Glite, ARC:&nbsp;the [[OPS vo|OPS VO]] (monitoring) and the [[Dteam vo|DTEAM VO]] (troubleshooting) are configured and supported by the Resource Centre. UNICORE: infrastructure it is possible to configure monitoring using users and authorization methods deployed by the Operations Center to which this Resource Center belongs. <br />
#regional VOs are configured and supported as needed by the Operations Centre. <br />
#the Resource Centre is integrated in any regional tool as needed (for example, the regional accounting infrastructure if present).<br><br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the registered services are fully functional by performing manual tests. e.g. from the UI or the Operations Centre monitoring infrastructure for uncertified Resource Centres. Note that monitoring of uncertified Resource Centres through the NGI Nagios production service is possible ([[SAM#Monitoring_uncertified_sites|instructions]]). Contact the Resource Centre admins if there are problems, and ensure that they fix them. Include the ROD, CSIRT and help-desk teams if necessary. Iterate this step with the Resource Centre admins until tests pass successfully. The prime tests to check are: <br />
#*network connectivity. <br />
#*CE job submission. <br />
#*SE data transfer<br />
<br />
Details for submitting manual tests can be found at [[Operations/HOWTO04|Grid manual tests]]. <br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#If all preliminary tests are passed for 3 consecutive calendar days, declare an initial maintenance downtime and switch the Resource Centre status to Certified. This ensures that Resource Centre will appear in NAGIOS and GSTAT.<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#The downtime should not be closed until the Resource Centre appears in all operational tools '''and''' accounting data is properly published. The major tools that are relevant are: <br />
#*Regional NAGIOS (NAGIOS) <br />
#**And all Nagios tests are passed <br />
#*Operations [https://operations-portal.egi.eu/dashboard Dashboard] (Dashboard-Siteview)<br />
#*[http://gstat.egi.eu/ GSTAT] <br />
#**GSTAT is not in an error state. Note: There may be some problems with this tool and ARC Resource Centres. <br />
#*[https://grid-monitoring.cern.ch/myegi/ MyEGI]<br />
<br />
If there are problems with a specific tool, open GGUS tickets to the relevant Support Units. Wait at least two days after the switch to the ''Certified'' status to open the ticket, the propagation of the new status to the operational tools or the publication of accounting data may take one or two days.<br> <br />
<br />
|- valign="top"<br />
| 9 <br />
| OC <br />
| <br />
#Notify the Resource Centre Operations Manager that the Resource Centre is certified<br><br />
<br />
|- valign="top"<br />
| 10 <br />
| OC <br />
| <br />
#The NGI can broadcast that a new Resource Centre is now part of the EGI infrastructure. This step is OPTIONAL.<br />
<br />
|}<br />
<br />
After the successful completion of these steps, the Resource Centre is considered as "Certified". <!--<br />
= Revision history =<br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center"<br />
|-<br />
! Version <br />
! Authors <br />
! Date <br />
! Comments<br />
|-<br />
| 1.11 <br />
| Peter Solagna <br />
| 2011-05-17 <br />
| According to OMB comments: Modified the maximum duration of different site statuses. Removed the two days suggested period of downtime. The definition of Resource Centre will point to the Site OLA.&nbsp;<br />
|-<br />
| 1.1 <br />
| Peter Soalgna <br />
| 2011-05-1 <br />
| Updated cert step 6: downtime period lasts at least two days. Moved Cert step #10 to #4. Changed ''"If there is no suitable provider for your country, it maybe that the an Operations Centre MUST first be created."'' with ''"If a'' <br />
provider is not yet available for your country, then an alternative existing Operations Centre can be contacted."''. Now site responsiveness through its mail contacts is requested from the being of the certification process.'' <br />
<br />
|-<br />
| 0.8 <br />
| Tiziana Ferrari <br />
| 2011-03-11 <br />
| Updated introduction, adopted MUST SHALL etc. terminology, proposed some changes to terminology, added a section with a list of responsibilities, added a few comments into the text to request clarifications.<br />
|-<br />
| 0.7 <br />
| Vera Hansper <br />
| 2011-02-02 <br />
| Updated introduction to include roles, etc. and added required documentation link for policies<br />
|}<br />
--> <br> <br />
<br />
= Revision History =<br />
<br />
*7/09/2012: (editorial, M.&nbsp;Krakowian) typos and adding links where necessary, Gridview link removed from #8 'Site Certification'<br> <br />
*25/10/2011: (editorial, T. Ferrari) Replacement of RIP with "RP" standing for Resource infrastructure Provider<br />
<br />
{{Template:Creative_commons}} <br />
<br />
[[Category:Procedures]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=PROC09_Resource_Centre_Registration_and_Certification&diff=40235PROC09 Resource Centre Registration and Certification2012-09-07T13:46:35Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}}&nbsp; {{TOC_right}} <br />
<br />
{| border="1"<br />
|-<br />
| '''Title''' <br />
| ''Resource Centre Registration and Certification Procedure''<br />
|-<br />
| '''Document link''' <br />
| https://wiki.egi.eu/wiki/PROC09<br />
|-<br />
| '''Version - last modified''' <br />
| 1.0 - 17 May 2011<br><br />
|-<br />
| '''Policy Group Acronym''' <br />
| ''OMB''<br />
|-<br />
| '''Policy Group Name''' <br />
| ''Operations Management Board''<br />
|-<br />
| '''Contact Person''' <br />
| operational-documentation@mailman.egi.eu<br />
|-<br />
| '''Document Status''' <br />
| ''APPROVED''<br />
|-<br />
| '''Approved Date''' <br />
| 17 May 2011<br><br />
|-<br />
| '''Procedure Statement''' <br />
| ''A procedure for the steps involved to both register and certify new Resource Centres (sites) in the EGI infrastructure. The certification step can also be used to re-certify suspended Resource Centres (sites).''<br />
|}<br />
<br />
= Resource Centre Registration and Certification Procedure =<br />
<br />
Certification is a prerequisite for a [[#Definitions|Resource Centre]] (aka site) to become part of a Resource Infrastructure such as a National Grid Initiative (NGI), an EIRO, or a multi-country Resource Infrastructure. <br />
<br />
This document describes the steps required <br />
<br />
#to register and certify a new Resource Centre, <br />
#to re-certify a Resource Centre which has been suspended.<br />
<br />
Note: A separate document provides the [[PROC11|process for decommissioning a Resource Centre]]. <br />
<br />
Through its parent Resource Infrastructure, a certified Resource Centre becomes a member of the EGI Resource Infrastructure to make resources available to international user communities. <br />
<br />
The main difference between a certified Resource Centre and an uncertified or test Resource Centre is that a certified Resource Centre provides and guarantees a minimum quality of service of the resources (currently expressed in terms of monthly availability and reliability): the certified Resource Centre must ensure problems are handled in a timely fashion and the certified Resource Centre must understand and adhere to a common set of policies and procedures. All the requirements can be found in the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
<br />
= Definitions =<br />
<br />
*'''Resource Centre''' refers to the definition in the "[https://documents.egi.eu/document/31 Resource Centre OLA]".<br />
<br />
:''In this document, the term "'''site'''" is '''deprecated''', and '''Resource Centre''' has been used in its place.''<br />
<br />
*Other entities involved in this procedure are defined in the [[Glossary|EGI Glossary]].<br />
<br />
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. <br />
<br />
= Entities involved in the procedure =<br />
<br />
<!-- There are minimally two sets of players involved in this procedure --> <br />
<br />
*'''Resource Centre Operations Manager''': person who is responsible for initiating the certification process by applying for membership to a Resource Infrastructure. <br />
*'''Resource Infrastructure Operations Manager''': person who is responsible for approving the integration of a new Resource Centre into the respective Infrastructure. <br />
*'''Operations Centre''': entity which is technically responsible for carrying out the Resource Centre certification part of the procedure, once the membership is approved.<br />
<br />
The Resource Infrastructure Operations Manager can determine with the Resource Centre Operations Manager the level of involvement of other actors. <br />
<br />
= Contact information =<br />
<br />
*EGI Operations: operations (at) mailman.egi.eu <br />
*EGI Resource infrastructure Providers are listed on the EGI [https://www.egi.eu/infrastructure/Resource-providers/index.html web site] <br />
*A list of EGI Operations Centres with their respective contact information is available from the [http://go.egi.eu/operations-centres GOCDB] <br />
*EGI CSIRT: egi-csirt-team (at) mailman.egi.eu<br />
<br />
= Actions and responsibilities =<br />
<br />
== Resource Centre Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is responsible for all Resource Centres within its respective jurisdiction (for example, an NGI is responsible for all Resource Centres in its country). For this reason, the Resource Centre Operations Manager of a new Resource Centre is REQUIRED <br />
#*to contact the respective NGI if the Resource Centre is located in Europe, <br />
#*to contact the respective Resource infrastructure Provider active in a relevant geographical area if the Resource Centre is outside Europe, about the intention of the Resource Centre to join the EGI infrastructure. If needed, EGI Operations can assist the Resource Centre Operations Manager to get in contact with the relevant partners (see the Contact information section).<br> <br />
#The Resource Centre Operations Manager is REQUIRED to provide the necessary Resource Centre information needed to complete the registration process, and he/she is responsible for its accuracy and maintenance.<br> <br />
#In order to be certified, the Resource Centre Operations Manager is responsible for reading, understanding and accepting the [https://documents.egi.eu/document/31 Resource Centre Operational Level Agreement], which defines the obligations of a Resource Centre and the commitment to deliver a minimum quality of service to its future users. Endorsement of the OLA implies - among other things - the acceptance of: <br />
#*the [https://documents.egi.eu/document/86 Grid Security Policy] <br />
#*the [https://documents.egi.eu/document/75 Grid Resource Centre Operations Policy] <br />
#*the [https://documents.egi.eu/document/76 Resource Centre Registration Security Policy] <br />
#*all other policies for all EGI participants from the [https://wiki.egi.eu/wiki/SPG:Documents Security Policy Group]<br />
<br />
== Resource Infrastructure Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is REQUIRED to be responsible for all Resource Centres within its respective jurisdiction. For example, an NGI is responsible for all Resource Centres in its respective country. <br />
#The Resource Infrastructure Operations Managers MUST attend Resource Centre certification applications and MUST provide feedback to the requesting partners in a timely manner to accept or reject the requests received. <br />
#If the Resource Centre needs to be certified, s/he MUST provide information to the Resource Centre Operations Manager about the Resource Centre OLA, and is responsible for keeping records of the Resource Centre Operations Manager agreement, as deemed suitable by the Resource infrastructure Provider (for example, through a signed e-mail agreement, a collection of signatories on a paper copy of the OLA, or other means). <br />
#For the case where a request is accepted, the Resource Infrastructure Operations Manager MUST contact the relevant Operations Centre to start the Resource Centre registration as a candidate for the certification procedure. Registration is only needed for the case of new Resource Centres.<br />
<br />
== Operations Centre ==<br />
<br />
#The Operations Centre is responsible for registering (if applicable) and for certifying the Resource Centre. <br />
#The Operations Centre is responsible for registering an accepted Resource Centre in the EGI configuration repository [[GOCDB|GOCDB]]. <br />
#The Operations Centre MUST collect the mandatory information specified by the Resource Centre registration procedure, and MUST accurately input the data supplied into the GOCDB. <br />
#The Operations Centre MUST integrate Resource Centre information in all operations tools as needed, such as the local NAGIOS server for monitoring of certified Resource Centres, the local helpdesk (if available) for the registration of the Resource Centre support staff, etc. <br />
#In the case of an existing Resource Centre that is resuming certification after suspension for security reasons, the Operations Centre MUST contact the EGI CSIRT to verify that all requested repair operations have been successfully applied to fix the issue. <br />
#*For other suspension cases, the Operations Center MUST ensure that the issue that caused the suspension has been resolved. <br />
#The Operations Centre is responsible for verifying that all tests during the 3 calendar day certification process are successfully passed. The Operations Centre SHOULD only proceed with changing the Resource Centre status in the GOCDB to ''certified'' if this condition is met.<br />
<br />
= Workflow =<br />
<br />
The various steps required by both the Resource Infrastructure Operations Manager and the Resource Centre Operations Manager are explained in the tables below. The first part for a '''new''' Resource Centre is the registration process. The actual certification process, in the second table, is applicable to both new and suspended Resource Centres. <br />
<br />
The general status flow that a Resource Centre is allowed to follow is illustrated by the following diagram. Information on Resource Centre status and on how to manipulate it is available from [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Changing_Site_Certification_Status GOCDB Documentation]. <br />
<br />
[[Image:SiteStatusFlow.png|300px|SiteStatusFlow.png]] <br />
<br />
<br> <br />
<br />
A Resource Centre '''cannot '''be in <br />
<br />
*'''Candidate '''state for '''more than two months''' <br />
*'''Suspended''' state for '''more than four months'''<br />
<br />
After this period the Resource Centre SHOULD be closed. <br />
<br />
== Resource Centre registration ==<br />
<br />
=== Requirements ===<br />
<br />
#A Resource Centre MUST be part of a Resource Infrastructure and gets operational services offered by a Operations Centre. If a provider is not yet available for your country, then an alternative existing Operations Centre can be contacted. A procedure exists for this, and it is documented in the [[PROC02|Operations Centre creation]] procedure. <!-- text extracted from the Resource Centre registration procedure, which will likely disappear in the future--> <br />
#To satisfy Grid security requirements during the registration procedure the following information must be collected. The comprehensive list of required information is available ([[Operations/HOWTO01|here]]). <br />
#*The full name of the Resource Centre. <br />
#*An abbreviated name for the Resource Centre, which must be unique within the Grid, and preferably globally unique. <br />
#*The name, email address and telephone number of the Resource Centre Operations Manager and Resource Centre Security Contact in accordance with the requirements of the [https://documents.egi.eu/document/75 Resource Centre Operations Policy]. <br />
#*The email address of a managed list for contact with Resource Centre Administrators at the Resource Centre. <!-- Resource Administrators replaced by Site Administrators--> <br />
#*The email address of a managed list for contact with the Resource Centre security incident response team. <!--# A signed copy of the Site (Resource Centre) Operations Policy (https://documents.egi.eu/document/75).--><br />
<br />
Notes: <br />
<br />
#If a Resource Centre wishes to leave the Grid or the Grid decides to remove the Resource Centre, the registration information MUST be kept by [[GOCDB|GOCDB]] for at least the same period defined for logging in the [https://documents.egi.eu/document/81 Traceability and Logging Policy]. Personal registration information of the Resource Centre Operations Manager and Security Contact of the Resource Centre leaving the Grid MUST NOT be retained for longer than one year. <!--"Review and acceptance procedures and any operational requirements should be documented in a Grid specific<br />
document describing the implementation of the Resource Centre Registration Procedure." Comment: a maintenance procedure is currently missing. To check: what are the operational requirements? --> <br />
#It is RECOMMENDED that email contacts for the Resource Centre Administrators and Security Officer(s) are mailing lists, and not individuals.The contacts information SHOULD be available at the moment of the Resource Centre registration in GOCDB.<br />
<br />
<br> <br />
<br />
=== Steps ===<br />
<br />
The following steps are only applicable if '''the Resource Centre is not already registered in GOCDB'''. They describe the steps for a Resource Centre Operations Manager that is requesting the respective Resource Centre to join the EGI infrastructure. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RC <br />
| <br />
#Contact your Resource Infrastructure Operations Manager (contact information is available at [http://www.egi.eu/community/resource-providers/ http://www.egi.eu/community/resource-providers/]). <br />
#Provide your Resource Infrastructure Operations Manager the required information according to the template available in the [[Operations/HOWTO01|Required information]] page.<br />
<br />
|- valign="top"<br />
| 1 <br />
| RP <br />
| <br />
#Parse the Resource Centre registration request, decide to accept or reject it, and communicate this result back to applicant. <br />
#If the Resource Centre is accepted, notify the relevant Operations Centre, handle the Resource Centre information received, and put the Operations Centre in contact with the Resource Centre Operations Manager.<br />
<br />
|- valign="top"<br />
| 2 <br />
| OC <br />
| <br />
#The following actions can be done in parallel: <br />
#*Forward all [[Operations/HOWTO02|necessary and required documentation]] to install and configure the Resource Centre services to the Resource Centre Operations Manager. <br />
#*Communicate with the Operations Manager to clarify any doubts or questions. Include the Operations Centre ROD, CSIRT,&nbsp; or help-desk teams in the step if necessary.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#Add the Resource Centre to the [https://goc.egi.eu/ GOCDB ]and flag it as "Candidate". Note that all users with a GOCDB role at regional level can add a Resource Centre in scope (this includes Operations Manager, deputy and regional staff). Currently, GOCDB applies the same permissions to all of the "regional level roles". <br />
#Notify the Resource Centre Operations Manager that they should request for [http://www.eugridpma.org/ grid certificate], register in [https://voms.hellasgrid.gr:8443/vo/dteam/vomrs Dteam VO], register themself in the [https://goc.egi.eu/ GOCDB ]and request the Resource Centre Administrator role. Approve it when done.<br />
<br />
|- valign="top"<br />
| 4 <br />
| RC <br />
| <br />
#Complete any missing information for the Resource Centre's entry in the GOCDB, including services that are to be integrated into the infrastructure. <br />
#Request in the GOCDB (or ask the relevant Resource Centre security staff to request) the mandatory Resource Centre Security Officer role. A security expert is the most appropriate actor for this role. See the [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Understanding_and_manipulating_roles GOCDB Input System User Documentation] for more information on roles. <br />
#Accept or deny all the requested roles under the Resource Centre scope. Note: If the Resource Centre Operations Manager can not approve roles, they should request the Operations Centre to do so. This is a current flaw in GOCDB. <br />
#Notify the Operations Centre that the Resource Centre information update is concluded.<br />
<br />
|- valign="top"<br />
| 5 <br />
| RC or OC <br />
| <br />
#Check whether the Resource Centre appears in the "Notified Site" field in [https://ggus.eu/ws/ticket_search.php https://ggus.eu/ws/ticket_search.php] <br />
#Note that this step should happen automatically when the Resource Centre is correctly entered into the GOCDB. If this is still not visible 2 days after the GOCDB entries have been created, the Operations Centre should be informed and should then contact GGUS administrators through [https://ggus.eu/pages/ticket.php GGUS]. <br />
#A new Resource Centre Administrator should register in GGUS ([https://ggus.eu/admin/get_account.php?accounttype=support https://ggus.eu/admin/get_account.php?accounttype=support]) but not specify any role, unless directed to by the Operations Centre.<br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the Resource Centre's information is correct (Resource Centre (site) roles and any other additional information.) <br />
#Check that contacts receive email (if they are mailing lists, check that outside EGI members are allowed to post there). Site administrator MUST reply to the test email.<br> <br />
#Check that the required services for a Resource Centre are properly registered. Note that for Resource Centre adopting APEL, by registering a new glite-APEL node in GOCDB as gLite-APEL service including the correct DN, the APEL broker Access Control List gets automatically updated and Resource Centres can start publishing usage records in about two hours (for more information see the [https://twiki.cern.ch/twiki/bin/view/EMI/Glite-APELInstallation gLite-APEL documentation]). <br />
#Check domain names and forward and reverse DNS.<br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#Any other Operations Centre-specific requirements (e.g. join a certain VO and/or mailing list, etc.)<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#If all previous actions have been completed with success, notify the Resource Centre Operations Manager that the Registration is completed, and contact the Resource Infrastructure Operations Manager to notify that a new candidate Resource Centre exists and is ready to be certified.<br />
<br />
|}<br />
<br />
After the successful completion of all these steps, the registration phase is completed and the Resource Centre is ready for the start of the <span class="il">certification</span> phase. <br />
<br />
== Resource Centre certification ==<br />
<br />
=== Requirements ===<br />
<br />
#The Resource Centre Certification procedure is only applicable for '''both Resource Centres in "Candidate" or "Suspended"''' status state.<br> <br />
#The following procedure is only applicable if '''the Resource Centre is already registered in GOCDB'''. <br />
#In order to enter certification the Resource Centre Operations Managers SHALL accept the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
#A Resource Centre can successfully pass certification only if the conditions required by the [https://documents.egi.eu/document/31 Resource Centre OLA] are met.<br />
<br />
=== Steps ===<br />
<br />
The following is a detailed description of the steps required for the transition from the "Uncertified" to the "Certified" state of the Resource Centre. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Resource Centre Operations Manager to request the subscription of the [https://documents.egi.eu/public/ShowDocument?docid=31 Resource Centre OLA].<br />
<br />
|- valign="top"<br />
| 1 <br />
| RC <br />
| <br />
#The Resource Centre Operations Manager notifies the Resource Infrastructure Operations Manager that the Resource Centre OLA is accepted (if the Resource Centre is has not already endorsed it before for example in case of a suspended Resource Centre), and the Resource Centre is ready to start certification.<br />
<br />
|- valign="top"<br />
| 2 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Operations Centre asking to start the certification process.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#If the Resource Centre is in the "Candidate" or "Suspended" state, then flag the Resource Centre as "Uncertified". If it was in the "Suspended" state then check that the reason for suspension has been cleared. If the suspension cause is a security issue, then the EGI CSIRT needs to be contacted to verify that all requested repair operations were successully applied by the Resource Centre Administrators to fix the issue that caused suspension. See [[SAM#Monitoring_uncertified_sites|instructions]] on how to monitor uncertified RCs.<br />
<br />
|- valign="top"<br />
| 4 <br />
| OC <br />
| <br />
#Add Resource Centre contact information to any regional mailing list and provide access to regional tools as required<br />
<br />
|- valign="top"<br />
| 5 <br />
| OC <br />
| <br />
#Check that the GIIS (gLite: BDII) is working, and publishing coherent values, namely: <br />
#*the correct NGI is being published in GlueSiteOtherInfo (see manual MAN01 [[MAN1 How to publish Site Information|How to Publish Site Information]]). <br />
#all services are registered in GOCDB according to the requirements of the [https://documents.egi.eu/document/31 Resource Centre OLA], these are published and ALSO that services published in the GOCDB are valid. <br />
#the [[OPS vo|OPS VO]] (monitoring) and the [[Dteam vo|DTEAM VO]] (troubleshooting) are configured and supported by the Resource Centre. <br />
#regional VOs are configured and supported as needed by the Operations Centre. <br />
#the Resource Centre is integrated in any regional tool as needed (for example, the regional accounting infrastructure if present).<br />
<br />
There are detailed examples for how to do this in [[Operations/HOWTO03|GIIS/BDII check]]. <br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the registered services are fully functional by performing manual tests. e.g. from the UI or the Operations Centre monitoring infrastructure for uncertified Resource Centres. Note that monitoring of uncertified Resource Centres through the NGI Nagios production service is possible ([[SAM#Monitoring_uncertified_sites|instructions]]). Contact the Resource Centre admins if there are problems, and ensure that they fix them. Include the ROD, CSIRT and help-desk teams if necessary. Iterate this step with the Resource Centre admins until tests pass successfully. The prime tests to check are: <br />
#*network connectivity. <br />
#*CE job submission. <br />
#*SE data transfer<br />
<br />
Details for submitting manual tests can be found at [[Operations/HOWTO04|Grid manual tests]]. <br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#If all preliminary tests are passed for 3 consecutive calendar days, declare an initial maintenance downtime and switch the Resource Centre status to Certified. This ensures that Resource Centre will appear in NAGIOS and GSTAT.<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#The downtime should not be closed until the Resource Centre appears in all operational tools '''and''' accounting data is properly published. The major tools that are relevant are: <br />
#*Regional NAGIOS (NAGIOS) <br />
#**And all Nagios tests are passed <br />
#*Operations [https://operations-portal.egi.eu/dashboard Dashboard] (Dashboard-Siteview) <br />
#*[http://gridview.cern.ch/GRIDVIEW/same_index.php GridView] <br />
#*[http://gstat.egi.eu/ GSTAT] <br />
#**GSTAT is not in an error state. Note: There may be some problems with this tool and ARC Resource Centres. <br />
#*[https://grid-monitoring.cern.ch/myegi/ MyEGI]<br />
<br />
If there are problems with a specific tool, open GGUS tickets to the relevant Support Units. Wait at least two days after the switch to the ''Certified'' status to open the ticket, the propagation of the new status to the operational tools or the publication of accounting data may take one or two days.<br> <br />
<br />
|- valign="top"<br />
| 9 <br />
| OC <br />
| <br />
#Notify the Resource Centre Operations Manager that the Resource Centre is certified<br><br />
<br />
|- valign="top"<br />
| 10 <br />
| OC <br />
| <br />
#The NGI can broadcast that a new Resource Centre is now part of the EGI infrastructure. This step is OPTIONAL.<br />
<br />
|}<br />
<br />
After the successful completion of these steps, the Resource Centre is considered as "Certified". <!--<br />
= Revision history =<br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center"<br />
|-<br />
! Version <br />
! Authors <br />
! Date <br />
! Comments<br />
|-<br />
| 1.11 <br />
| Peter Solagna <br />
| 2011-05-17 <br />
| According to OMB comments: Modified the maximum duration of different site statuses. Removed the two days suggested period of downtime. The definition of Resource Centre will point to the Site OLA.&nbsp;<br />
|-<br />
| 1.1 <br />
| Peter Soalgna <br />
| 2011-05-1 <br />
| Updated cert step 6: downtime period lasts at least two days. Moved Cert step #10 to #4. Changed ''"If there is no suitable provider for your country, it maybe that the an Operations Centre MUST first be created."'' with ''"If a'' <br />
provider is not yet available for your country, then an alternative existing Operations Centre can be contacted."''. Now site responsiveness through its mail contacts is requested from the being of the certification process.'' <br />
<br />
|-<br />
| 0.8 <br />
| Tiziana Ferrari <br />
| 2011-03-11 <br />
| Updated introduction, adopted MUST SHALL etc. terminology, proposed some changes to terminology, added a section with a list of responsibilities, added a few comments into the text to request clarifications.<br />
|-<br />
| 0.7 <br />
| Vera Hansper <br />
| 2011-02-02 <br />
| Updated introduction to include roles, etc. and added required documentation link for policies<br />
|}<br />
--> <br> <br />
<br />
= Revision History =<br />
<br />
*7/09/2012: (editorial, M.&nbsp;Krakowian) typos and adding links where necessary<br> <br />
*25/10/2011: (editorial, T. Ferrari) Replacement of RIP with "RP" standing for Resource infrastructure Provider<br />
<br />
{{Template:Creative_commons}} <br />
<br />
[[Category:Procedures]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=PROC09_Resource_Centre_Registration_and_Certification&diff=40233PROC09 Resource Centre Registration and Certification2012-09-07T13:09:12Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}}&nbsp; {{TOC_right}} <br />
<br />
{| border="1"<br />
|-<br />
| '''Title''' <br />
| ''Resource Centre Registration and Certification Procedure''<br />
|-<br />
| '''Document link''' <br />
| https://wiki.egi.eu/wiki/PROC09<br />
|-<br />
| '''Version - last modified''' <br />
| 1.0 - 17 May 2011<br><br />
|-<br />
| '''Policy Group Acronym''' <br />
| ''OMB''<br />
|-<br />
| '''Policy Group Name''' <br />
| ''Operations Management Board''<br />
|-<br />
| '''Contact Person''' <br />
| operational-documentation@mailman.egi.eu<br />
|-<br />
| '''Document Status''' <br />
| ''APPROVED''<br />
|-<br />
| '''Approved Date''' <br />
| 17 May 2011<br><br />
|-<br />
| '''Procedure Statement''' <br />
| ''A procedure for the steps involved to both register and certify new Resource Centres (sites) in the EGI infrastructure. The certification step can also be used to re-certify suspended Resource Centres (sites).''<br />
|}<br />
<br />
= Resource Centre Registration and Certification Procedure =<br />
<br />
Certification is a prerequisite for a [[#Definitions|Resource Centre]] (aka site) to become part of a Resource Infrastructure such as a National Grid Initiative (NGI), an EIRO, or a multi-country Resource Infrastructure. <br />
<br />
This document describes the steps required <br />
<br />
#to register and certify a new Resource Centre, <br />
#to re-certify a Resource Centre which has been suspended.<br />
<br />
Note: A separate document provides the [[PROC11|process for decommissioning a Resource Centre]]. <br />
<br />
Through its parent Resource Infrastructure, a certified Resource Centre becomes a member of the EGI Resource Infrastructure to make resources available to international user communities. <br />
<br />
The main difference between a certified Resource Centre and an uncertified or test Resource Centre is that a certified Resource Centre provides and guarantees a minimum quality of service of the resources (currently expressed in terms of monthly availability and reliability): the certified Resource Centre must ensure problems are handled in a timely fashion and the certified Resource Centre must understand and adhere to a common set of policies and procedures. All the requirements can be found in the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
<br />
= Definitions =<br />
<br />
*'''Resource Centre''' refers to the definition in the "[https://documents.egi.eu/document/31 Resource Centre OLA]".<br />
<br />
:''In this document, the term "'''site'''" is '''deprecated''', and '''Resource Centre''' has been used in its place.''<br />
<br />
*Other entities involved in this procedure are defined in the [[Glossary|EGI Glossary]].<br />
<br />
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. <br />
<br />
= Entities involved in the procedure =<br />
<br />
<!-- There are minimally two sets of players involved in this procedure --> <br />
<br />
*'''Resource Centre Operations Manager''': person who is responsible for initiating the certification process by applying for membership to a Resource Infrastructure. <br />
*'''Resource Infrastructure Operations Manager''': person who is responsible for approving the integration of a new Resource Centre into the respective Infrastructure. <br />
*'''Operations Centre''': entity which is technically responsible for carrying out the Resource Centre certification part of the procedure, once the membership is approved.<br />
<br />
The Resource Infrastructure Operations Manager can determine with the Resource Centre Operations Manager the level of involvement of other actors. <br />
<br />
= Contact information =<br />
<br />
*EGI Operations: operations (at) mailman.egi.eu <br />
*EGI Resource infrastructure Providers are listed on the EGI [https://www.egi.eu/infrastructure/Resource-providers/index.html web site] <br />
*A list of EGI Operations Centres with their respective contact information is available from the [http://go.egi.eu/operations-centres GOCDB] <br />
*EGI CSIRT: egi-csirt-team (at) mailman.egi.eu<br />
<br />
= Actions and responsibilities =<br />
<br />
== Resource Centre Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is responsible for all Resource Centres within its respective jurisdiction (for example, an NGI is responsible for all Resource Centres in its country). For this reason, the Resource Centre Operations Manager of a new Resource Centre is REQUIRED <br />
#*to contact the respective NGI if the Resource Centre is located in Europe, <br />
#*to contact the respective Resource infrastructure Provider active in a relevant geographical area if the Resource Centre is outside Europe, about the intention of the Resource Centre to join the EGI infrastructure. If needed, EGI Operations can assist the Resource Centre Operations Manager to get in contact with the relevant partners (see the Contact information section).<br> <br />
#The Resource Centre Operations Manager is REQUIRED to provide the necessary Resource Centre information needed to complete the registration process, and he/she is responsible for its accuracy and maintenance.<br> <br />
#In order to be certified, the Resource Centre Operations Manager is responsible for reading, understanding and accepting the [https://documents.egi.eu/document/31 Resource Centre Operational Level Agreement], which defines the obligations of a Resource Centre and the commitment to deliver a minimum quality of service to its future users. Endorsement of the OLA implies - among other things - the acceptance of: <br />
#*the [https://documents.egi.eu/document/86 Grid Security Policy] <br />
#*the [https://documents.egi.eu/document/75 Grid Resource Centre Operations Policy] <br />
#*the [https://documents.egi.eu/document/76 Resource Centre Registration Security Policy] <br />
#*all other policies for all EGI participants from the [https://wiki.egi.eu/wiki/SPG:Documents Security Policy Group]<br />
<br />
== Resource Infrastructure Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is REQUIRED to be responsible for all Resource Centres within its respective jurisdiction. For example, an NGI is responsible for all Resource Centres in its respective country. <br />
#The Resource Infrastructure Operations Managers MUST attend Resource Centre certification applications and MUST provide feedback to the requesting partners in a timely manner to accept or reject the requests received. <br />
#If the Resource Centre needs to be certified, s/he MUST provide information to the Resource Centre Operations Manager about the Resource Centre OLA, and is responsible for keeping records of the Resource Centre Operations Manager agreement, as deemed suitable by the Resource infrastructure Provider (for example, through a signed e-mail agreement, a collection of signatories on a paper copy of the OLA, or other means). <br />
#For the case where a request is accepted, the Resource Infrastructure Operations Manager MUST contact the relevant Operations Centre to start the Resource Centre registration as a candidate for the certification procedure. Registration is only needed for the case of new Resource Centres.<br />
<br />
== Operations Centre ==<br />
<br />
#The Operations Centre is responsible for registering (if applicable) and for certifying the Resource Centre. <br />
#The Operations Centre is responsible for registering an accepted Resource Centre in the EGI configuration repository [[GOCDB|GOCDB]]. <br />
#The Operations Centre MUST collect the mandatory information specified by the Resource Centre registration procedure, and MUST accurately input the data supplied into the GOCDB. <br />
#The Operations Centre MUST integrate Resource Centre information in all operations tools as needed, such as the local NAGIOS server for monitoring of certified Resource Centres, the local helpdesk (if available) for the registration of the Resource Centre support staff, etc. <br />
#In the case of an existing Resource Centre that is resuming certification after suspension for security reasons, the Operations Centre MUST contact the EGI CSIRT to verify that all requested repair operations have been successfully applied to fix the issue. <br />
#*For other suspension cases, the Operations Center MUST ensure that the issue that caused the suspension has been resolved. <br />
#The Operations Centre is responsible for verifying that all tests during the 3 calendar day certification process are successfully passed. The Operations Centre SHOULD only proceed with changing the Resource Centre status in the GOCDB to ''certified'' if this condition is met.<br />
<br />
= Workflow =<br />
<br />
The various steps required by both the Resource Infrastructure Operations Manager and the Resource Centre Operations Manager are explained in the tables below. The first part for a '''new''' Resource Centre is the registration process. The actual certification process, in the second table, is applicable to both new and suspended Resource Centres. <br />
<br />
The general status flow that a Resource Centre is allowed to follow is illustrated by the following diagram. Information on Resource Centre status and on how to manipulate it is available from [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Changing_Site_Certification_Status GOCDB Documentation]. <br />
<br />
[[Image:SiteStatusFlow.png|300px|SiteStatusFlow.png]] <br />
<br />
<br> <br />
<br />
A Resource Centre '''cannot '''be in <br />
<br />
*'''Candidate '''state for '''more than two months''' <br />
*'''Suspended''' state for '''more than four months'''<br />
<br />
After this period the Resource Centre SHOULD be closed. <br />
<br />
== Resource Centre registration ==<br />
<br />
=== Requirements ===<br />
<br />
#A Resource Centre MUST be part of a Resource Infrastructure and gets operational services offered by a Operations Centre. If a provider is not yet available for your country, then an alternative existing Operations Centre can be contacted. A procedure exists for this, and it is documented in the [[PROC02|Operations Centre creation]] procedure. <!-- text extracted from the Resource Centre registration procedure, which will likely disappear in the future--> <br />
#To satisfy Grid security requirements during the registration procedure the following information must be collected. The comprehensive list of required information is available ([[Operations/HOWTO01|here]]). <br />
#*The full name of the Resource Centre. <br />
#*An abbreviated name for the Resource Centre, which must be unique within the Grid, and preferably globally unique. <br />
#*The name, email address and telephone number of the Resource Centre Operations Manager and Resource Centre Security Contact in accordance with the requirements of the [https://documents.egi.eu/document/75 Resource Centre Operations Policy]. <br />
#*The email address of a managed list for contact with Resource Centre Administrators at the Resource Centre. <!-- Resource Administrators replaced by Site Administrators--> <br />
#*The email address of a managed list for contact with the Resource Centre security incident response team. <!--# A signed copy of the Site (Resource Centre) Operations Policy (https://documents.egi.eu/document/75).--><br />
<br />
Notes: <br />
<br />
#If a Resource Centre wishes to leave the Grid or the Grid decides to remove the Resource Centre, the registration information MUST be kept by [[GOCDB|GOCDB]] for at least the same period defined for logging in the [https://documents.egi.eu/document/81 Traceability and Logging Policy]. Personal registration information of the Resource Centre Operations Manager and Security Contact of the Resource Centre leaving the Grid MUST NOT be retained for longer than one year. <!--"Review and acceptance procedures and any operational requirements should be documented in a Grid specific<br />
document describing the implementation of the Resource Centre Registration Procedure." Comment: a maintenance procedure is currently missing. To check: what are the operational requirements? --> <br />
#It is RECOMMENDED that email contacts for the Resource Centre Administrators and Security Officer(s) are mailing lists, and not individuals.The contacts information SHOULD be available at the moment of the Resource Centre registration in GOCDB.<br />
<br />
<br> <br />
<br />
=== Steps ===<br />
<br />
The following steps are only applicable if '''the Resource Centre is not already registered in GOCDB'''. They describe the steps for a Resource Centre Operations Manager that is requesting the respective Resource Centre to join the EGI infrastructure. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RC <br />
| <br />
#Contact your Resource Infrastructure Operations Manager (contact information is available at [http://www.egi.eu/community/resource-providers/ http://www.egi.eu/community/resource-providers/]). <br />
#Provide your Resource Infrastructure Operations Manager the required information according to the template available in the [[Operations/HOWTO01|Required information]] page.<br />
<br />
|- valign="top"<br />
| 1 <br />
| RP <br />
| <br />
#Parse the Resource Centre registration request, decide to accept or reject it, and communicate this result back to applicant. <br />
#If the Resource Centre is accepted, notify the relevant Operations Centre, handle the Resource Centre information received, and put the Operations Centre in contact with the Resource Centre Operations Manager.<br />
<br />
|- valign="top"<br />
| 2 <br />
| OC <br />
| <br />
#The following actions can be done in parallel: <br />
#*Forward all [[Operations/HOWTO02|necessary and required documentation]] to install and configure the Resource Centre services to the Resource Centre Operations Manager. <br />
#*Communicate with the Operations Manager to clarify any doubts or questions. Include the Operations Centre ROD, CSIRT,&nbsp; or help-desk teams in the step if necessary.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#Add the Resource Centre to the [https://goc.egi.eu/ GOCDB ]and flag it as "Candidate". Note that all users with a GOCDB role at regional level can add a Resource Centre in scope (this includes Operations Manager, deputy and regional staff). Currently, GOCDB applies the same permissions to all of the "regional level roles". <br />
#Notify the Resource Centre Operations Manager that they should request for [http://www.eugridpma.org/ grid certificate], register in [https://voms.hellasgrid.gr:8443/vo/dteam/vomrs Dteam VO], register themself in the [https://goc.egi.eu/ GOCDB ]and request the Resource Centre Administrator role. Approve it when done.<br />
<br />
|- valign="top"<br />
| 4 <br />
| RC <br />
| <br />
#Complete any missing information for the Resource Centre's entry in the GOCDB, including services that are to be integrated into the infrastructure. <br />
#Request in the GOCDB (or ask the relevant Resource Centre security staff to request) the mandatory Resource Centre Security Officer role. A security expert is the most appropriate actor for this role. See the [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Understanding_and_manipulating_roles GOCDB Input System User Documentation] for more information on roles. <br />
#Accept or deny all the requested roles under the Resource Centre scope. Note: If the Resource Centre Operations Manager can not approve roles, they should request the Operations Centre to do so. This is a current flaw in GOCDB. <br />
#Notify the Operations Centre that the Resource Centre information update is concluded.<br />
<br />
|- valign="top"<br />
| 5 <br />
| RC or OC <br />
| <br />
#Check whether the Resource Centre appears in the "Notified Site" field in [https://ggus.eu/ws/ticket_search.php https://ggus.eu/ws/ticket_search.php] <br />
#Note that this step should happen automatically when the Resource Centre is correctly entered into the GOCDB. If this is still not visible 2 days after the GOCDB entries have been created, the Operations Centre should be informed and should then contact GGUS administrators through [https://ggus.eu/pages/ticket.php GGUS]. <br />
#A new Resource Centre Administrator should register in GGUS ([https://ggus.eu/admin/get_account.php?accounttype=support https://ggus.eu/admin/get_account.php?accounttype=support]) but not specify any role, unless directed to by the Operations Centre.<br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the Resource Centre's information is correct (Resource Centre (site) roles and any other additional information.) <br />
#Check that contacts receive email (if they are mailing lists, check that outside EGI members are allowed to post there). Site administrator MUST reply to the test email.<br> <br />
#Check that the required services for a Resource Centre are properly registered. Note that for Resource Centre adopting APEL, by registering a new glite-APEL node in GOCDB as gLite-APEL service including the correct DN, the APEL broker Access Control List gets automatically updated and Resource Centres can start publishing usage records in about two hours (for more information see the [https://twiki.cern.ch/twiki/bin/view/EMI/Glite-APELInstallation gLite-APEL documentation]). <br />
#Check domain names and forward and reverse DNS.<br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#Any other Operations Centre-specific requirements (e.g. join a certain VO and/or mailing list, etc.)<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#If all previous actions have been completed with success, notify the Resource Centre Operations Manager that the Registration is completed, and contact the Resource Infrastructure Operations Manager to notify that a new candidate Resource Centre exists and is ready to be certified.<br />
<br />
|}<br />
<br />
After the successful completion of all these steps, the registration phase is completed and the Resource Centre is ready for the start of the <span class="il">certification</span> phase. <br />
<br />
== Resource Centre certification ==<br />
<br />
=== Requirements ===<br />
<br />
#The Resource Centre Certification procedure is only applicable for '''both Resource Centres in "Candidate" or "Suspended"''' status state.<br> <br />
#The following procedure is only applicable if '''the Resource Centre is already registered in GOCDB'''. <br />
#In order to enter certification the Resource Centre Operations Managers SHALL accept the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
#A Resource Centre can successfully pass certification only if the conditions required by the [https://documents.egi.eu/document/31 Resource Centre OLA] are met.<br />
<br />
=== Steps ===<br />
<br />
The following is a detailed description of the steps required for the transition from the "Uncertified" to the "Certified" state of the Resource Centre. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Resource Centre Operations Manager to request the subscription of the [https://documents.egi.eu/public/ShowDocument?docid=31 Resource Centre OLA].<br />
<br />
|- valign="top"<br />
| 1 <br />
| RC <br />
| <br />
#The Resource Centre Operations Manager notifies the Resource Infrastructure Operations Manager that the Resource Centre OLA is accepted (if the Resource Centre is has not already endorsed it before for example in case of a suspended Resource Centre), and the Resource Centre is ready to start certification.<br />
<br />
|- valign="top"<br />
| 2 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Operations Centre asking to start the certification process.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#If the Resource Centre is in the "Candidate" or "Suspended" state, then flag the Resource Centre as "Uncertified". If it was in the "Suspended" state then check that the reason for suspension has been cleared. If the suspension cause is a security issue, then the EGI CSIRT needs to be contacted to verify that all requested repair operations were successully applied by the Resource Centre Administrators to fix the issue that caused suspension. See [[SAM#Monitoring_uncertified_sites|instructions]] on how to monitor uncertified RCs.<br />
<br />
|- valign="top"<br />
| 4 <br />
| OC <br />
| <br />
#Add Resource Centre contact information to any regional mailing list and provide access to regional tools as required<br />
<br />
|- valign="top"<br />
| 5 <br />
| OC <br />
| <br />
#Check that the GIIS (gLite: BDII) is working, and publishing coherent values, namely: <br />
#*the correct NGI is being published in GlueSiteOtherInfo (see manual MAN01 [[MAN1 How to publish Site Information|How to Publish Site Information]]). <br />
#*all services are registered in GOCDB according to the requirements of the [https://documents.egi.eu/document/31 Resource Centre OLA], these are published and ALSO that services published in the GOCDB are valid. <br />
#*the [[OPS vo|OPS VO]] (monitoring) and the [[Dteam vo|DTEAM VO]] (troubleshooting) are configured and supported by the Resource Centre. <br />
#*regional VOs are configured and supported as needed by the Operations Centre. <br />
#*the Resource Centre is integrated in any regional tool as needed (for example, the regional accounting infrastructure if present).<br />
<br />
There are detailed examples for how to do this in [[Operations/HOWTO03|GIIS/BDII check]]. <br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the registered services are fully functional by performing manual tests. e.g. from the UI or the Operations Centre monitoring infrastructure for uncertified Resource Centres. Note that monitoring of uncertified Resource Centres through the NGI Nagios production service is possible ([[SAM#Monitoring_uncertified_sites|instructions]]). Contact the Resource Centre admins if there are problems, and ensure that they fix them. Include the ROD, CSIRT and help-desk teams if necessary. Iterate this step with the Resource Centre admins until tests pass successfully. The prime tests to check are: <br />
#*network connectivity. <br />
#*CE job submission. <br />
#*SE data transfer<br />
<br />
Details for submitting manual tests can be found at [[Operations/HOWTO04|Grid manual tests]]. <br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#If all preliminary tests are passed for 3 consecutive calendar days, declare an initial maintenance downtime and switch the Resource Centre status to Certified. This ensures that Resource Centre will appear in NAGIOS and GSTAT.<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#The downtime should not be closed until the Resource Centre appears in all operational tools '''and''' accounting data is properly published. The major tools that are relevant are: <br />
#*Regional NAGIOS (NAGIOS) <br />
#**And all Nagios tests are passed <br />
#*Operations [https://operations-portal.egi.eu/dashboard Dashboard] (Dashboard-Siteview) <br />
#*[http://gridview.cern.ch/GRIDVIEW/same_index.php GridView] <br />
#*[http://gstat.egi.eu/ GSTAT] <br />
#**GSTAT is not in an error state. Note: There may be some problems with this tool and ARC Resource Centres. <br />
#*[https://grid-monitoring.cern.ch/myegi/ MyEGI]<br />
<br />
If there are problems with a specific tool, open GGUS tickets to the relevant Support Units. Wait at least two days after the switch to the ''Certified'' status to open the ticket, the propagation of the new status to the operational tools or the publication of accounting data may take one or two days.<br> <br />
<br />
|- valign="top"<br />
| 9 <br />
| OC <br />
| <br />
#Notify the Resource Centre Operations Manager that the Resource Centre is certified<br><br />
<br />
|- valign="top"<br />
| 10 <br />
| OC <br />
| <br />
#The NGI can broadcast that a new Resource Centre is now part of the EGI infrastructure. This step is OPTIONAL.<br />
<br />
|}<br />
<br />
After the successful completion of these steps, the Resource Centre is considered as "Certified". <!--<br />
= Revision history =<br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center"<br />
|-<br />
! Version <br />
! Authors <br />
! Date <br />
! Comments<br />
|-<br />
| 1.11 <br />
| Peter Solagna <br />
| 2011-05-17 <br />
| According to OMB comments: Modified the maximum duration of different site statuses. Removed the two days suggested period of downtime. The definition of Resource Centre will point to the Site OLA.&nbsp;<br />
|-<br />
| 1.1 <br />
| Peter Soalgna <br />
| 2011-05-1 <br />
| Updated cert step 6: downtime period lasts at least two days. Moved Cert step #10 to #4. Changed ''"If there is no suitable provider for your country, it maybe that the an Operations Centre MUST first be created."'' with ''"If a'' <br />
provider is not yet available for your country, then an alternative existing Operations Centre can be contacted."''. Now site responsiveness through its mail contacts is requested from the being of the certification process.'' <br />
<br />
|-<br />
| 0.8 <br />
| Tiziana Ferrari <br />
| 2011-03-11 <br />
| Updated introduction, adopted MUST SHALL etc. terminology, proposed some changes to terminology, added a section with a list of responsibilities, added a few comments into the text to request clarifications.<br />
|-<br />
| 0.7 <br />
| Vera Hansper <br />
| 2011-02-02 <br />
| Updated introduction to include roles, etc. and added required documentation link for policies<br />
|}<br />
--> <br> <br />
<br />
= Revision History =<br />
<br />
*7/09/2012: (editorial, M.&nbsp;Krakowian) typos and adding links where necessary<br><br />
*25/10/2011: (editorial, T. Ferrari) Replacement of RIP with "RP" standing for Resource infrastructure Provider<br />
<br />
{{Template:Creative_commons}} <br />
<br />
[[Category:Procedures]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=PROC09_Resource_Centre_Registration_and_Certification&diff=40230PROC09 Resource Centre Registration and Certification2012-09-07T12:41:59Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}}&nbsp; {{TOC_right}} <br />
<br />
{| border="1"<br />
|-<br />
| '''Title''' <br />
| ''Resource Centre Registration and Certification Procedure''<br />
|-<br />
| '''Document link''' <br />
| https://wiki.egi.eu/wiki/PROC09<br />
|-<br />
| '''Version - last modified''' <br />
| 1.0 - 17 May 2011<br><br />
|-<br />
| '''Policy Group Acronym''' <br />
| ''OMB''<br />
|-<br />
| '''Policy Group Name''' <br />
| ''Operations Management Board''<br />
|-<br />
| '''Contact Person''' <br />
| operational-documentation@mailman.egi.eu<br />
|-<br />
| '''Document Status''' <br />
| ''APPROVED''<br />
|-<br />
| '''Approved Date''' <br />
| 17 May 2011<br><br />
|-<br />
| '''Procedure Statement''' <br />
| ''A procedure for the steps involved to both register and certify new Resource Centres (sites) in the EGI infrastructure. The certification step can also be used to re-certify suspended Resource Centres (sites).''<br />
|}<br />
<br />
= Resource Centre Registration and Certification Procedure =<br />
<br />
Certification is a prerequisite for a [[#Definitions|Resource Centre]] (aka site) to become part of a Resource Infrastructure such as a National Grid Initiative (NGI), an EIRO, or a multi-country Resource Infrastructure. <br />
<br />
This document describes the steps required <br />
<br />
#to register and certify a new Resource Centre, <br />
#to re-certify a Resource Centre which has been suspended.<br />
<br />
Note: A separate document provides the [[PROC11|process for decommissioning a Resource Centre]]. <br />
<br />
Through its parent Resource Infrastructure, a certified Resource Centre becomes a member of the EGI Resource Infrastructure to make resources available to international user communities. <br />
<br />
The main difference between a certified Resource Centre and an uncertified or test Resource Centre is that a certified Resource Centre provides and guarantees a minimum quality of service of the resources (currently expressed in terms of monthly availability and reliability): the certified Resource Centre must ensure problems are handled in a timely fashion and the certified Resource Centre must understand and adhere to a common set of policies and procedures. All the requirements can be found in the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
<br />
= Definitions =<br />
<br />
*'''Resource Centre''' refers to the definition in the "[https://documents.egi.eu/document/31 Resource Centre OLA]".<br />
<br />
:''In this document, the term "'''site'''" is '''deprecated''', and '''Resource Centre''' has been used in its place.''<br />
<br />
*Other entities involved in this procedure are defined in the [[Glossary|EGI Glossary]].<br />
<br />
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. <br />
<br />
= Entities involved in the procedure =<br />
<br />
<!-- There are minimally two sets of players involved in this procedure --> <br />
<br />
*'''Resource Centre Operations Manager''': person who is responsible for initiating the certification process by applying for membership to a Resource Infrastructure. <br />
*'''Resource Infrastructure Operations Manager''': person who is responsible for approving the integration of a new Resource Centre into the respective Infrastructure. <br />
*'''Operations Centre''': entity which is technically responsible for carrying out the Resource Centre certification part of the procedure, once the membership is approved.<br />
<br />
The Resource Infrastructure Operations Manager can determine with the Resource Centre Operations Manager the level of involvement of other actors. <br />
<br />
= Contact information =<br />
<br />
*EGI Operations: operations (at) mailman.egi.eu <br />
*EGI Resource infrastructure Providers are listed on the EGI [https://www.egi.eu/infrastructure/Resource-providers/index.html web site] <br />
*A list of EGI Operations Centres with their respective contact information is available from the [http://go.egi.eu/operations-centres GOCDB] <br />
*EGI CSIRT: egi-csirt-team (at) mailman.egi.eu<br />
<br />
= Actions and responsibilities =<br />
<br />
== Resource Centre Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is responsible for all Resource Centres within its respective jurisdiction (for example, an NGI is responsible for all Resource Centres in its country). For this reason, the Resource Centre Operations Manager of a new Resource Centre is REQUIRED <br />
#*to contact the respective NGI if the Resource Centre is located in Europe, <br />
#*to contact the respective Resource infrastructure Provider active in a relevant geographical area if the Resource Centre is outside Europe, about the intention of the Resource Centre to join the EGI infrastructure. If needed, EGI Operations can assist the Resource Centre Operations Manager to get in contact with the relevant partners (see the Contact information section).<br> <br />
#The Resource Centre Operations Manager is REQUIRED to provide the necessary Resource Centre information needed to complete the registration process, and he/she is responsible for its accuracy and maintenance.<br> <br />
#In order to be certified, the Resource Centre Operations Manager is responsible for reading, understanding and accepting the [https://documents.egi.eu/document/31 Resource Centre Operational Level Agreement], which defines the obligations of a Resource Centre and the commitment to deliver a minimum quality of service to its future users. Endorsement of the OLA implies - among other things - the acceptance of: <br />
#*the [https://documents.egi.eu/document/86 Grid Security Policy] <br />
#*the [https://documents.egi.eu/document/75 Grid Resource Centre Operations Policy] <br />
#*the [https://documents.egi.eu/document/76 Resource Centre Registration Security Policy] <br />
#*all other policies for all EGI participants from the [https://wiki.egi.eu/wiki/SPG:Documents Security Policy Group]<br />
<br />
== Resource Infrastructure Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is REQUIRED to be responsible for all Resource Centres within its respective jurisdiction. For example, an NGI is responsible for all Resource Centres in its respective country. <br />
#The Resource Infrastructure Operations Managers MUST attend Resource Centre certification applications and MUST provide feedback to the requesting partners in a timely manner to accept or reject the requests received. <br />
#If the Resource Centre needs to be certified, s/he MUST provide information to the Resource Centre Operations Manager about the Resource Centre OLA, and is responsible for keeping records of the Resource Centre Operations Manager agreement, as deemed suitable by the Resource infrastructure Provider (for example, through a signed e-mail agreement, a collection of signatories on a paper copy of the OLA, or other means). <br />
#For the case where a request is accepted, the Resource Infrastructure Operations Manager MUST contact the relevant Operations Centre to start the Resource Centre registration as a candidate for the certification procedure. Registration is only needed for the case of new Resource Centres.<br />
<br />
== Operations Centre ==<br />
<br />
#The Operations Centre is responsible for registering (if applicable) and for certifying the Resource Centre. <br />
#The Operations Centre is responsible for registering an accepted Resource Centre in the EGI configuration repository [[GOCDB|GOCDB]]. <br />
#The Operations Centre MUST collect the mandatory information specified by the Resource Centre registration procedure, and MUST accurately input the data supplied into the GOCDB. <br />
#The Operations Centre MUST integrate Resource Centre information in all operations tools as needed, such as the local NAGIOS server for monitoring of certified Resource Centres, the local helpdesk (if available) for the registration of the Resource Centre support staff, etc. <br />
#In the case of an existing Resource Centre that is resuming certification after suspension for security reasons, the Operations Centre MUST contact the EGI CSIRT to verify that all requested repair operations have been successfully applied to fix the issue. <br />
#*For other suspension cases, the Operations Center MUST ensure that the issue that caused the suspension has been resolved. <br />
#The Operations Centre is responsible for verifying that all tests during the 3 calendar day certification process are successfully passed. The Operations Centre SHOULD only proceed with changing the Resource Centre status in the GOCDB to ''certified'' if this condition is met.<br />
<br />
= Workflow =<br />
<br />
The various steps required by both the Resource Infrastructure Operations Manager and the Resource Centre Operations Manager are explained in the tables below. The first part for a '''new''' Resource Centre is the registration process. The actual certification process, in the second table, is applicable to both new and suspended Resource Centres. <br />
<br />
The general status flow that a Resource Centre is allowed to follow is illustrated by the following diagram. Information on Resource Centre status and on how to manipulate it is available from [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Changing_Site_Certification_Status GOCDB Documentation]. <br />
<br />
[[Image:SiteStatusFlow.png|300px|SiteStatusFlow.png]] <br />
<br />
<br> <br />
<br />
A Resource Centre '''cannot '''be in <br />
<br />
*'''Candidate'''state for'''more than two month''''''s''' <br />
*'''Suspended''' state for '''more than four months'''<br />
<br />
After this period the Resource Centre SHOULD be closed. <br />
<br />
== Resource Centre registration ==<br />
<br />
=== Requirements ===<br />
<br />
#A Resource Centre MUST be part of a Resource Infrastructure and gets operational services offered by a Operations Centre. If a provider is not yet available for your country, then an alternative existing Operations Centre can be contacted. A procedure exists for this, and it is documented in the [[PROC02|Operations Centre creation]] procedure. <!-- text extracted from the Resource Centre registration procedure, which will likely disappear in the future--> <br />
#To satisfy Grid security requirements during the registration procedure the following information must be collected. The comprehensive list of required information is available ([[Operations/HOWTO01|here]]). <br />
#*The full name of the Resource Centre. <br />
#*An abbreviated name for the Resource Centre, which must be unique within the Grid, and preferably globally unique. <br />
#*The name, email address and telephone number of the Resource Centre Operations Manager and Resource Centre Security Contact in accordance with the requirements of the [https://documents.egi.eu/document/75 Resource Centre Operations Policy]. <br />
#*The email address of a managed list for contact with Resource Centre Administrators at the Resource Centre. <!-- Resource Administrators replaced by Site Administrators--> <br />
#*The email address of a managed list for contact with the Resource Centre security incident response team. <!--# A signed copy of the Site (Resource Centre) Operations Policy (https://documents.egi.eu/document/75).--><br />
<br />
Notes: <br />
<br />
#If a Resource Centre wishes to leave the Grid or the Grid decides to remove the Resource Centre, the registration information MUST be kept by [[GOCDB|GOCDB]] for at least the same period defined for logging in the [https://documents.egi.eu/document/81 Traceability and Logging Policy]. Personal registration information of the Resource Centre Operations Manager and Security Contact of the Resource Centre leaving the Grid MUST NOT be retained for longer than one year. <!--"Review and acceptance procedures and any operational requirements should be documented in a Grid specific<br />
document describing the implementation of the Resource Centre Registration Procedure." Comment: a maintenance procedure is currently missing. To check: what are the operational requirements? --> <br />
#It is RECOMMENDED that email contacts for the Resource Centre Administrators and Security Officer(s) are mailing lists, and not individuals.The contacts information SHOULD be available at the moment of the Resource Centre registration in GOCDB.<br />
<br />
<br> <br />
<br />
=== Steps ===<br />
<br />
The following steps are only applicable if '''the Resource Centre is not already registered in GOCDB'''. They describe the steps for a Resource Centre Operations Manager that is requesting the respective Resource Centre to join the EGI infrastructure. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RC <br />
| <br />
#Contact your Resource Infrastructure Operations Manager (contact information is available at [http://www.egi.eu/community/resource-providers/ http://www.egi.eu/community/resource-providers/]). <br />
#Provide your Resource Infrastructure Operations Manager the required information according to the template available in the [[Operations/HOWTO01|Required information]] page.<br />
<br />
|- valign="top"<br />
| 1 <br />
| RP <br />
| <br />
#Parse the Resource Centre registration request, decide to accept or reject it, and communicate this result back to applicant. <br />
#If the Resource Centre is accepted, notify the relevant Operations Centre, handle the Resource Centre information received, and put the Operations Centre in contact with the Resource Centre Operations Manager.<br />
<br />
|- valign="top"<br />
| 2 <br />
| OC <br />
| <br />
#The following actions can be done in parallel: <br />
#*Forward all [[Operations/HOWTO02|necessary and required documentation]] to install and configure the Resource Centre services to the Resource Centre Operations Manager. <br />
#*Communicate with the Operations Manager to clarify any doubts or questions. Include the Operations Centre ROD, CSIRT,&nbsp; or help-desk teams in the step if necessary.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#Add the Resource Centre to the [https://goc.egi.eu/ GOCDB ]and flag it as "Candidate". Note that all users with a GOCDB role at regional level can add a Resource Centre in scope (this includes Operations Manager, deputy and regional staff). Currently, GOCDB applies the same permissions to all of the "regional level roles". <br />
#Notify the Resource Centre Operations Manager that they should request for [http://www.eugridpma.org/ grid certificate], register in [https://voms.hellasgrid.gr:8443/vo/dteam/vomrs Dteam VO], register themself in the [https://goc.egi.eu/ GOCDB ]and request the Resource Centre Administrator role. Approve it when done.<br />
<br />
|- valign="top"<br />
| 4 <br />
| RC <br />
| <br />
#Complete any missing information for the Resource Centre's entry in the GOCDB, including services that are to be integrated into the infrastructure. <br />
#Request in the GOCDB (or ask the relevant Resource Centre security staff to request) the mandatory Resource Centre Security Officer role. A security expert is the most appropriate actor for this role. See the [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Understanding_and_manipulating_roles GOCDB Input System User Documentation] for more information on roles. <br />
#Accept or deny all the requested roles under the Resource Centre scope. Note: If the Resource Centre Operations Manager can not approve roles, they should request the Operations Centre to do so. This is a current flaw in GOCDB. <br />
#Notify the Operations Centre that the Resource Centre information update is concluded.<br />
<br />
|- valign="top"<br />
| 5 <br />
| RC or OC <br />
| <br />
#Check whether the Resource Centre appears in the "Notified Site" field in [https://ggus.eu/ws/ticket_search.php https://ggus.eu/ws/ticket_search.php] <br />
#Note that this step should happen automatically when the Resource Centre is correctly entered into the GOCDB. If this is still not visible 2 days after the GOCDB entries have been created, the Operations Centre should be informed and should then contact GGUS administrators through [https://ggus.eu/pages/ticket.php GGUS]. <br />
#A new Resource Centre Administrator should register in GGUS ([https://ggus.eu/admin/get_account.php?accounttype=support https://ggus.eu/admin/get_account.php?accounttype=support]) but not specify any role, unless directed to by the Operations Centre.<br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the Resource Centre's information is correct (Resource Centre (site) roles and any other additional information.) <br />
#Check that contacts receive email (if they are mailing lists, check that outside EGI members are allowed to post there). Site administrator MUST reply to the test email.<br> <br />
#Check that the required services for a Resource Centre are properly registered. Note that for Resource Centre adopting APEL, by registering a new glite-APEL node in GOCDB as gLite-APEL service including the correct DN, the APEL broker Access Control List gets automatically updated and Resource Centres can start publishing usage records in about two hours (for more information see the [https://twiki.cern.ch/twiki/bin/view/EMI/Glite-APELInstallation gLite-APEL documentation]). <br />
#Check domain names and forward and reverse DNS.<br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#Any other Operations Centre-specific requirements (e.g. join a certain VO and/or mailing list, etc.)<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#If all previous actions have been completed with success, notify the Resource Centre Operations Manager that the Registration is completed, and contact the Resource Infrastructure Operations Manager to notify that a new candidate Resource Centre exists and is ready to be certified.<br />
<br />
|}<br />
<br />
After the successful completion of all these steps, the registration phase is completed and the Resource Centre is ready for the start of the <span class="il">certification</span> phase. <br />
<br />
== Resource Centre certification ==<br />
<br />
=== Requirements ===<br />
<br />
#The Resource Centre Certification procedure is only applicable for '''both Resource Centres in "Candidate" or "Suspended"''' status state.<br> <br />
#The following procedure is only applicable if '''the Resource Centre is already registered in GOCDB'''. <br />
#In order to enter certification the Resource Centre Operations Managers SHALL accept the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
#A Resource Centre can successfully pass certification only if the conditions required by the [https://documents.egi.eu/document/31 Resource Centre OLA] are met.<br />
<br />
=== Steps ===<br />
<br />
The following is a detailed description of the steps required for the transition from the "Uncertified" to the "Certified" state of the Resource Centre. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Resource Centre Operations Manager to request the subscription of the Resource Centre OLA.<br />
<br />
|- valign="top"<br />
| 1 <br />
| RC <br />
| <br />
#The Resource Centre Operations Manager notifies the Resource Infrastructure Operations Manager that the Resource Centre OLA is accepted (if the Resource Centre is has not already endorsed it before for example in case of a suspended Resource Centre), and the Resource Centre is ready to start certification.<br />
<br />
|- valign="top"<br />
| 2 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Operations Centre asking to start the certification process.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#If the Resource Centre is in the "Candidate" or "Suspended" state, then flag the Resource Centre as "Uncertified". If it was in the "Suspended" state then check that the reason for suspension has been cleared. If the suspension cause is a security issue, then the EGI CSIRT needs to be contacted to verify that all requested repair operations were successully applied by the Resource Centre Administrators to fix the issue that caused suspension. See [[SAM#Monitoring_uncertified_sites|instructions]] on how to monitor uncertified RCs.<br />
<br />
|- valign="top"<br />
| 4 <br />
| OC <br />
| <br />
#Add Resource Centre contact information to any regional mailing list and provide access to regional tools as required<br />
<br />
|- valign="top"<br />
| 5 <br />
| OC <br />
| <br />
#Check that the GIIS (gLite: BDII) is working, and publishing coherent values, namely: <br />
#*the correct NGI is being published in GlueSiteOtherInfo (see manual MAN01 [[MAN1 How to publish Site Information|How to Publish Site Information]]). <br />
#*all services are registered in GOCDB according to the requirements of the [https://documents.egi.eu/document/31 Resource Centre OLA], these are published and ALSO that services published in the GOCDB are valid. <br />
#*the [[OPS vo|OPS VO]] (monitoring) and the [[Dteam vo|DTEAM VO]] (troubleshooting) are configured and supported by the Resource Centre. <br />
#*regional VOs are configured and supported as needed by the Operations Centre. <br />
#*the Resource Centre is integrated in any regional tool as needed (for example, the regional accounting infrastructure if present).<br />
<br />
There are detailed examples for how to do this in [[Operations/HOWTO03|GIIS/BDII check]]. <br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the registered services are fully functional by performing manual tests. e.g. from the UI or the Operations Centre monitoring infrastructure for uncertified Resource Centres. Note that monitoring of uncertified Resource Centres through the NGI Natios production service is possible ([[SAM#Monitoring_uncertified_sites|instructions]]). Contact the Resource Centre admins if there are problems, and ensure that they fix them. Include the ROD and help-desk teams if necessary. Iterate this step with the Resource Centre admins until tests pass successfully. The prime tests to check are: <br />
#*network connectivity. <br />
#*CE job submission. <br />
#*SE data transfer<br />
<br />
Details for submitting manual tests can be found at [[Operations/HOWTO04|Grid manual tests]]. <br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#If all preliminary tests are passed for 3 consecutive calendar days, declare an initial maintenance downtime and switch the Resource Centre status to Certified. This ensures that Resource Centre will appear in NAGIOS and GSTAT.<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#The downtime should not be closed until the Resource Centre appears in all operational tools '''and''' accounting data is properly published. The major tools that are relevant are: <br />
#*Regional NAGIOS (NAGIOS) <br />
#**And all Nagios tests are passed <br />
#*Operations [https://operations-portal.egi.eu/dashboard Dashboard] (Dashboard-Siteview) <br />
#*[http://gridview.cern.ch/GRIDVIEW/same_index.php GridView] <br />
#*[http://gstat.egi.eu/ GSTAT] <br />
#**GSTAT is not in an error state. CAVEAT: There may be some problems with this tool and ARC Resource Centres. <br />
#*[https://grid-monitoring.cern.ch/myegi/ MyEGI]<br />
<br />
If there are problems with a specific tool, open GGUS tickets to the relevant Support Units. Wait at least two days after the switch to the ''Certified'' status to open the ticket, the propagation of the new status to the operational tools or the publication of accounting data may take one or two days. <br />
<br />
<br> <br />
<br />
|- valign="top"<br />
| 9 <br />
| OC <br />
| <br />
#Notify the Resource Centre Operations Manager that the Resource Centre is certified<br />
<br />
<br> <br />
<br />
|- valign="top"<br />
| 10 <br />
| OC <br />
| <br />
#The NGI can broadcast that a new Resource Centre is now part of the EGI infrastructure. This step is OPTIONAL.<br />
<br />
|}<br />
<br />
After the successful completion of these steps, the Resource Centre is considered as "Certified". <!--<br />
= Revision history =<br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center"<br />
|-<br />
! Version <br />
! Authors <br />
! Date <br />
! Comments<br />
|-<br />
| 1.11 <br />
| Peter Solagna <br />
| 2011-05-17 <br />
| According to OMB comments: Modified the maximum duration of different site statuses. Removed the two days suggested period of downtime. The definition of Resource Centre will point to the Site OLA.&nbsp;<br />
|-<br />
| 1.1 <br />
| Peter Soalgna <br />
| 2011-05-1 <br />
| Updated cert step 6: downtime period lasts at least two days. Moved Cert step #10 to #4. Changed ''"If there is no suitable provider for your country, it maybe that the an Operations Centre MUST first be created."'' with ''"If a'' <br />
provider is not yet available for your country, then an alternative existing Operations Centre can be contacted."''. Now site responsiveness through its mail contacts is requested from the being of the certification process.'' <br />
<br />
|-<br />
| 0.8 <br />
| Tiziana Ferrari <br />
| 2011-03-11 <br />
| Updated introduction, adopted MUST SHALL etc. terminology, proposed some changes to terminology, added a section with a list of responsibilities, added a few comments into the text to request clarifications.<br />
|-<br />
| 0.7 <br />
| Vera Hansper <br />
| 2011-02-02 <br />
| Updated introduction to include roles, etc. and added required documentation link for policies<br />
|}<br />
--> <br> <br />
<br />
= Revision History =<br />
<br />
*25/10/2011: (editorial, T. Ferrari) Replacement of RIP with "RP" standing for Resource infrastructure Provider<br />
<br />
{{Template:Creative_commons}} <br />
<br />
[[Category:Procedures]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=PROC09_Resource_Centre_Registration_and_Certification&diff=40229PROC09 Resource Centre Registration and Certification2012-09-07T12:41:32Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} <br />
<br />
{| border="1"<br />
|-<br />
| '''Title''' <br />
| ''Resource Centre Registration and Certification Procedure''<br />
|-<br />
| '''Document link''' <br />
| https://wiki.egi.eu/wiki/PROC09<br />
|-<br />
| '''Version - last modified''' <br />
| 1.0 - 17 May 2011<br><br />
|-<br />
| '''Policy Group Acronym''' <br />
| ''OMB''<br />
|-<br />
| '''Policy Group Name''' <br />
| ''Operations Management Board''<br />
|-<br />
| '''Contact Person''' <br />
| operational-documentation@mailman.egi.eu<br />
|-<br />
| '''Document Status''' <br />
| ''APPROVED''<br />
|-<br />
| '''Approved Date''' <br />
| 17 May 2011<br><br />
|-<br />
| '''Procedure Statement''' <br />
| ''A procedure for the steps involved to both register and certify new Resource Centres (sites) in the EGI infrastructure. The certification step can also be used to re-certify suspended Resource Centres (sites).''<br />
|}<br />
<br />
= Resource Centre Registration and Certification Procedure =<br />
<br />
Certification is a prerequisite for a [[#Definitions|Resource Centre]] (aka site) to become part of a Resource Infrastructure such as a National Grid Initiative (NGI), an EIRO, or a multi-country Resource Infrastructure. <br />
<br />
This document describes the steps required <br />
<br />
#to register and certify a new Resource Centre, <br />
#to re-certify a Resource Centre which has been suspended.<br />
<br />
Note: A separate document provides the [[PROC11|process for decommissioning a Resource Centre]]. <br />
<br />
Through its parent Resource Infrastructure, a certified Resource Centre becomes a member of the EGI Resource Infrastructure to make resources available to international user communities. <br />
<br />
The main difference between a certified Resource Centre and an uncertified or test Resource Centre is that a certified Resource Centre provides and guarantees a minimum quality of service of the resources (currently expressed in terms of monthly availability and reliability): the certified Resource Centre must ensure problems are handled in a timely fashion and the certified Resource Centre must understand and adhere to a common set of policies and procedures. All the requirements can be found in the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
<br />
= Definitions =<br />
<br />
*'''Resource Centre''' refers to the definition in the "[https://documents.egi.eu/document/31 Resource Centre OLA]".<br />
<br />
:''In this document, the term "'''site'''" is '''deprecated''', and '''Resource Centre''' has been used in its place.''<br />
<br />
*Other entities involved in this procedure are defined in the [[Glossary|EGI Glossary]].<br />
<br />
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119. <br />
<br />
= Entities involved in the procedure =<br />
<br />
<!-- There are minimally two sets of players involved in this procedure --> <br />
<br />
*'''Resource Centre Operations Manager''': person who is responsible for initiating the certification process by applying for membership to a Resource Infrastructure. <br />
*'''Resource Infrastructure Operations Manager''': person who is responsible for approving the integration of a new Resource Centre into the respective Infrastructure. <br />
*'''Operations Centre''': entity which is technically responsible for carrying out the Resource Centre certification part of the procedure, once the membership is approved.<br />
<br />
The Resource Infrastructure Operations Manager can determine with the Resource Centre Operations Manager the level of involvement of other actors. <br />
<br />
= Contact information =<br />
<br />
*EGI Operations: operations (at) mailman.egi.eu <br />
*EGI Resource infrastructure Providers are listed on the EGI [https://www.egi.eu/infrastructure/Resource-providers/index.html web site] <br />
*A list of EGI Operations Centres with their respective contact information is available from the [http://go.egi.eu/operations-centres GOCDB] <br />
*EGI CSIRT: egi-csirt-team (at) mailman.egi.eu<br />
<br />
= Actions and responsibilities =<br />
<br />
== Resource Centre Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is responsible for all Resource Centres within its respective jurisdiction (for example, an NGI is responsible for all Resource Centres in its country). For this reason, the Resource Centre Operations Manager of a new Resource Centre is REQUIRED <br />
#*to contact the respective NGI if the Resource Centre is located in Europe, <br />
#*to contact the respective Resource infrastructure Provider active in a relevant geographical area if the Resource Centre is outside Europe, about the intention of the Resource Centre to join the EGI infrastructure. If needed, EGI Operations can assist the Resource Centre Operations Manager to get in contact with the relevant partners (see the Contact information section).<br> <br />
#The Resource Centre Operations Manager is REQUIRED to provide the necessary Resource Centre information needed to complete the registration process, and he/she is responsible for its accuracy and maintenance.<br> <br />
#In order to be certified, the Resource Centre Operations Manager is responsible for reading, understanding and accepting the [https://documents.egi.eu/document/31 Resource Centre Operational Level Agreement], which defines the obligations of a Resource Centre and the commitment to deliver a minimum quality of service to its future users. Endorsement of the OLA implies - among other things - the acceptance of: <br />
#*the [https://documents.egi.eu/document/86 Grid Security Policy] <br />
#*the [https://documents.egi.eu/document/75 Grid Resource Centre Operations Policy] <br />
#*the [https://documents.egi.eu/document/76 Resource Centre Registration Security Policy] <br />
#*all other policies for all EGI participants from the [https://wiki.egi.eu/wiki/SPG:Documents Security Policy Group]<br />
<br />
== Resource Infrastructure Operations Manager ==<br />
<br />
#A Resource infrastructure Provider is REQUIRED to be responsible for all Resource Centres within its respective jurisdiction. For example, an NGI is responsible for all Resource Centres in its respective country. <br />
#The Resource Infrastructure Operations Managers MUST attend Resource Centre certification applications and MUST provide feedback to the requesting partners in a timely manner to accept or reject the requests received. <br />
#If the Resource Centre needs to be certified, s/he MUST provide information to the Resource Centre Operations Manager about the Resource Centre OLA, and is responsible for keeping records of the Resource Centre Operations Manager agreement, as deemed suitable by the Resource infrastructure Provider (for example, through a signed e-mail agreement, a collection of signatories on a paper copy of the OLA, or other means). <br />
#For the case where a request is accepted, the Resource Infrastructure Operations Manager MUST contact the relevant Operations Centre to start the Resource Centre registration as a candidate for the certification procedure. Registration is only needed for the case of new Resource Centres.<br />
<br />
== Operations Centre ==<br />
<br />
#The Operations Centre is responsible for registering (if applicable) and for certifying the Resource Centre. <br />
#The Operations Centre is responsible for registering an accepted Resource Centre in the EGI configuration repository [[GOCDB|GOCDB]]. <br />
#The Operations Centre MUST collect the mandatory information specified by the Resource Centre registration procedure, and MUST accurately input the data supplied into the GOCDB. <br />
#The Operations Centre MUST integrate Resource Centre information in all operations tools as needed, such as the local NAGIOS server for monitoring of certified Resource Centres, the local helpdesk (if available) for the registration of the Resource Centre support staff, etc. <br />
#In the case of an existing Resource Centre that is resuming certification after suspension for security reasons, the Operations Centre MUST contact the EGI CSIRT to verify that all requested repair operations have been successfully applied to fix the issue. <br />
#*For other suspension cases, the Operations Center MUST ensure that the issue that caused the suspension has been resolved. <br />
#The Operations Centre is responsible for verifying that all tests during the 3 calendar day certification process are successfully passed. The Operations Centre SHOULD only proceed with changing the Resource Centre status in the GOCDB to ''certified'' if this condition is met.<br />
<br />
= Workflow =<br />
<br />
The various steps required by both the Resource Infrastructure Operations Manager and the Resource Centre Operations Manager are explained in the tables below. The first part for a '''new''' Resource Centre is the registration process. The actual certification process, in the second table, is applicable to both new and suspended Resource Centres. <br />
<br />
The general status flow that a Resource Centre is allowed to follow is illustrated by the following diagram. Information on Resource Centre status and on how to manipulate it is available from [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Changing_Site_Certification_Status GOCDB Documentation]. <br />
<br />
[[Image:SiteStatusFlow.png|300px|SiteStatusFlow.png]] <br />
<br />
<br> <br />
<br />
A Resource Centre '''cannot '''be in <br />
<br />
*'''Candidate''' state for'''more than two month''''''s'''<br />
*'''Suspended''' state for '''more than four months'''<br />
<br />
After this period the Resource Centre SHOULD be closed.<br />
<br />
== Resource Centre registration ==<br />
<br />
=== Requirements ===<br />
<br />
#A Resource Centre MUST be part of a Resource Infrastructure and gets operational services offered by a Operations Centre. If a provider is not yet available for your country, then an alternative existing Operations Centre can be contacted. A procedure exists for this, and it is documented in the [[PROC02|Operations Centre creation]] procedure. <!-- text extracted from the Resource Centre registration procedure, which will likely disappear in the future--> <br />
#To satisfy Grid security requirements during the registration procedure the following information must be collected. The comprehensive list of required information is available ([[Operations/HOWTO01|here]]). <br />
#*The full name of the Resource Centre. <br />
#*An abbreviated name for the Resource Centre, which must be unique within the Grid, and preferably globally unique. <br />
#*The name, email address and telephone number of the Resource Centre Operations Manager and Resource Centre Security Contact in accordance with the requirements of the [https://documents.egi.eu/document/75 Resource Centre Operations Policy]. <br />
#*The email address of a managed list for contact with Resource Centre Administrators at the Resource Centre. <!-- Resource Administrators replaced by Site Administrators--> <br />
#*The email address of a managed list for contact with the Resource Centre security incident response team. <!--# A signed copy of the Site (Resource Centre) Operations Policy (https://documents.egi.eu/document/75).--><br />
<br />
Notes: <br />
<br />
#If a Resource Centre wishes to leave the Grid or the Grid decides to remove the Resource Centre, the registration information MUST be kept by [[GOCDB|GOCDB]] for at least the same period defined for logging in the [https://documents.egi.eu/document/81 Traceability and Logging Policy]. Personal registration information of the Resource Centre Operations Manager and Security Contact of the Resource Centre leaving the Grid MUST NOT be retained for longer than one year. <!--"Review and acceptance procedures and any operational requirements should be documented in a Grid specific<br />
document describing the implementation of the Resource Centre Registration Procedure." Comment: a maintenance procedure is currently missing. To check: what are the operational requirements? --><br />
#It is RECOMMENDED that email contacts for the Resource Centre Administrators and Security Officer(s) are mailing lists, and not individuals.The contacts information SHOULD be available at the moment of the Resource Centre registration in GOCDB.<br />
<br />
<br> <br />
<br />
=== Steps ===<br />
<br />
The following steps are only applicable if '''the Resource Centre is not already registered in GOCDB'''. They describe the steps for a Resource Centre Operations Manager that is requesting the respective Resource Centre to join the EGI infrastructure. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RC <br />
| <br />
#Contact your Resource Infrastructure Operations Manager (contact information is available at [http://www.egi.eu/community/resource-providers/ http://www.egi.eu/community/resource-providers/]). <br />
#Provide your Resource Infrastructure Operations Manager the required information according to the template available in the [[Operations/HOWTO01|Required information]] page.<br />
<br />
|- valign="top"<br />
| 1 <br />
| RP <br />
| <br />
#Parse the Resource Centre registration request, decide to accept or reject it, and communicate this result back to applicant. <br />
#If the Resource Centre is accepted, notify the relevant Operations Centre, handle the Resource Centre information received, and put the Operations Centre in contact with the Resource Centre Operations Manager.<br />
<br />
|- valign="top"<br />
| 2 <br />
| OC <br />
| <br />
#The following actions can be done in parallel: <br />
#*Forward all [[Operations/HOWTO02|necessary and required documentation]] to install and configure the Resource Centre services to the Resource Centre Operations Manager. <br />
#*Communicate with the Operations Manager to clarify any doubts or questions. Include the Operations Centre ROD, CSIRT,&nbsp; or help-desk teams in the step if necessary.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#Add the Resource Centre to the [https://goc.egi.eu/ GOCDB ]and flag it as "Candidate". Note that all users with a GOCDB role at regional level can add a Resource Centre in scope (this includes Operations Manager, deputy and regional staff). Currently, GOCDB applies the same permissions to all of the "regional level roles". <br />
#Notify the Resource Centre Operations Manager that they should request for [http://www.eugridpma.org/ grid certificate], register in [https://voms.hellasgrid.gr:8443/vo/dteam/vomrs Dteam VO], register themself in the [https://goc.egi.eu/ GOCDB ]and request the Resource Centre Administrator role. Approve it when done.<br />
<br />
|- valign="top"<br />
| 4 <br />
| RC <br />
| <br />
#Complete any missing information for the Resource Centre's entry in the GOCDB, including services that are to be integrated into the infrastructure. <br />
#Request in the GOCDB (or ask the relevant Resource Centre security staff to request) the mandatory Resource Centre Security Officer role. A security expert is the most appropriate actor for this role. See the [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Understanding_and_manipulating_roles GOCDB Input System User Documentation] for more information on roles. <br />
#Accept or deny all the requested roles under the Resource Centre scope. Note: If the Resource Centre Operations Manager can not approve roles, they should request the Operations Centre to do so. This is a current flaw in GOCDB. <br />
#Notify the Operations Centre that the Resource Centre information update is concluded.<br />
<br />
|- valign="top"<br />
| 5 <br />
| RC or OC <br />
| <br />
#Check whether the Resource Centre appears in the "Notified Site" field in [https://ggus.eu/ws/ticket_search.php https://ggus.eu/ws/ticket_search.php] <br />
#Note that this step should happen automatically when the Resource Centre is correctly entered into the GOCDB. If this is still not visible 2 days after the GOCDB entries have been created, the Operations Centre should be informed and should then contact GGUS administrators through [https://ggus.eu/pages/ticket.php GGUS]. <br />
#A new Resource Centre Administrator should register in GGUS ([https://ggus.eu/admin/get_account.php?accounttype=support https://ggus.eu/admin/get_account.php?accounttype=support]) but not specify any role, unless directed to by the Operations Centre.<br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the Resource Centre's information is correct (Resource Centre (site) roles and any other additional information.) <br />
#Check that contacts receive email (if they are mailing lists, check that outside EGI members are allowed to post there). Site administrator MUST reply to the test email.<br> <br />
#Check that the required services for a Resource Centre are properly registered. Note that for Resource Centre adopting APEL, by registering a new glite-APEL node in GOCDB as gLite-APEL service including the correct DN, the APEL broker Access Control List gets automatically updated and Resource Centres can start publishing usage records in about two hours (for more information see the [https://twiki.cern.ch/twiki/bin/view/EMI/Glite-APELInstallation gLite-APEL documentation]). <br />
#Check domain names and forward and reverse DNS.<br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#Any other Operations Centre-specific requirements (e.g. join a certain VO and/or mailing list, etc.)<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#If all previous actions have been completed with success, notify the Resource Centre Operations Manager that the Registration is completed, and contact the Resource Infrastructure Operations Manager to notify that a new candidate Resource Centre exists and is ready to be certified.<br />
<br />
|}<br />
<br />
After the successful completion of all these steps, the registration phase is completed and the Resource Centre is ready for the start of the <span class="il">certification</span> phase. <br />
<br />
== Resource Centre certification ==<br />
<br />
=== Requirements ===<br />
<br />
#The Resource Centre Certification procedure is only applicable for '''both Resource Centres in "Candidate" or "Suspended"''' status state.<br><br />
#The following procedure is only applicable if '''the Resource Centre is already registered in GOCDB'''.<br />
#In order to enter certification the Resource Centre Operations Managers SHALL accept the [https://documents.egi.eu/document/31 Resource Centre OLA]. <br />
#A Resource Centre can successfully pass certification only if the conditions required by the [https://documents.egi.eu/document/31 Resource Centre OLA] are met.<br />
<br />
=== Steps ===<br />
<br />
The following is a detailed description of the steps required for the transition from the "Uncertified" to the "Certified" state of the Resource Centre. <br />
<br />
*Actions tagged '''RC''' are the responsibility of the Resource Centre Operations Manager. <br />
*Actions tagged '''RP''' are the responsibility of the Resource Infrastructure Operations Manager. <br />
*Actions tagged '''OC''' are the responsibility of the Operations Centre<br />
<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! # <br />
! Responsible <br />
! Action<br />
|- valign="top"<br />
| 0 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Resource Centre Operations Manager to request the subscription of the Resource Centre OLA.<br />
<br />
|- valign="top"<br />
| 1 <br />
| RC <br />
| <br />
#The Resource Centre Operations Manager notifies the Resource Infrastructure Operations Manager that the Resource Centre OLA is accepted (if the Resource Centre is has not already endorsed it before for example in case of a suspended Resource Centre), and the Resource Centre is ready to start certification.<br />
<br />
|- valign="top"<br />
| 2 <br />
| RP <br />
| <br />
#The Resource Infrastructure Operations Manager contacts the Operations Centre asking to start the certification process.<br />
<br />
|- valign="top"<br />
| 3 <br />
| OC <br />
| <br />
#If the Resource Centre is in the "Candidate" or "Suspended" state, then flag the Resource Centre as "Uncertified". If it was in the "Suspended" state then check that the reason for suspension has been cleared. If the suspension cause is a security issue, then the EGI CSIRT needs to be contacted to verify that all requested repair operations were successully applied by the Resource Centre Administrators to fix the issue that caused suspension. See [[SAM#Monitoring_uncertified_sites|instructions]] on how to monitor uncertified RCs.<br />
<br />
|- valign="top"<br />
| 4 <br />
| OC <br />
| <br />
#Add Resource Centre contact information to any regional mailing list and provide access to regional tools as required<br />
<br />
|- valign="top"<br />
| 5 <br />
| OC <br />
| <br />
#Check that the GIIS (gLite: BDII) is working, and publishing coherent values, namely: <br />
#*the correct NGI is being published in GlueSiteOtherInfo (see manual MAN01 [[MAN1 How to publish Site Information|How to Publish Site Information]]). <br />
#*all services are registered in GOCDB according to the requirements of the [https://documents.egi.eu/document/31 Resource Centre OLA], these are published and ALSO that services published in the GOCDB are valid. <br />
#*the [[OPS vo|OPS VO]] (monitoring) and the [[Dteam vo|DTEAM VO]] (troubleshooting) are configured and supported by the Resource Centre. <br />
#*regional VOs are configured and supported as needed by the Operations Centre. <br />
#*the Resource Centre is integrated in any regional tool as needed (for example, the regional accounting infrastructure if present).<br />
<br />
There are detailed examples for how to do this in [[Operations/HOWTO03|GIIS/BDII check]]. <br />
<br />
|- valign="top"<br />
| 6 <br />
| OC <br />
| <br />
#Check that the registered services are fully functional by performing manual tests. e.g. from the UI or the Operations Centre monitoring infrastructure for uncertified Resource Centres. Note that monitoring of uncertified Resource Centres through the NGI Natios production service is possible ([[SAM#Monitoring_uncertified_sites|instructions]]). Contact the Resource Centre admins if there are problems, and ensure that they fix them. Include the ROD and help-desk teams if necessary. Iterate this step with the Resource Centre admins until tests pass successfully. The prime tests to check are: <br />
#*network connectivity. <br />
#*CE job submission. <br />
#*SE data transfer<br />
<br />
Details for submitting manual tests can be found at [[Operations/HOWTO04|Grid manual tests]]. <br />
<br />
|- valign="top"<br />
| 7 <br />
| OC <br />
| <br />
#If all preliminary tests are passed for 3 consecutive calendar days, declare an initial maintenance downtime and switch the Resource Centre status to Certified. This ensures that Resource Centre will appear in NAGIOS and GSTAT.<br />
<br />
|- valign="top"<br />
| 8 <br />
| OC <br />
| <br />
#The downtime should not be closed until the Resource Centre appears in all operational tools '''and''' accounting data is properly published. The major tools that are relevant are: <br />
#*Regional NAGIOS (NAGIOS) <br />
#**And all Nagios tests are passed <br />
#*Operations [https://operations-portal.egi.eu/dashboard Dashboard] (Dashboard-Siteview) <br />
#*[http://gridview.cern.ch/GRIDVIEW/same_index.php GridView] <br />
#*[http://gstat.egi.eu/ GSTAT] <br />
#**GSTAT is not in an error state. CAVEAT: There may be some problems with this tool and ARC Resource Centres. <br />
#*[https://grid-monitoring.cern.ch/myegi/ MyEGI]<br />
<br />
If there are problems with a specific tool, open GGUS tickets to the relevant Support Units. Wait at least two days after the switch to the ''Certified'' status to open the ticket, the propagation of the new status to the operational tools or the publication of accounting data may take one or two days. <br />
<br />
<br> <br />
<br />
|- valign="top"<br />
| 9 <br />
| OC <br />
| <br />
#Notify the Resource Centre Operations Manager that the Resource Centre is certified<br />
<br />
<br> <br />
<br />
|- valign="top"<br />
| 10 <br />
| OC <br />
| <br />
#The NGI can broadcast that a new Resource Centre is now part of the EGI infrastructure. This step is OPTIONAL.<br />
<br />
|}<br />
<br />
After the successful completion of these steps, the Resource Centre is considered as "Certified". <!--<br />
= Revision history =<br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center"<br />
|-<br />
! Version <br />
! Authors <br />
! Date <br />
! Comments<br />
|-<br />
| 1.11 <br />
| Peter Solagna <br />
| 2011-05-17 <br />
| According to OMB comments: Modified the maximum duration of different site statuses. Removed the two days suggested period of downtime. The definition of Resource Centre will point to the Site OLA.&nbsp;<br />
|-<br />
| 1.1 <br />
| Peter Soalgna <br />
| 2011-05-1 <br />
| Updated cert step 6: downtime period lasts at least two days. Moved Cert step #10 to #4. Changed ''"If there is no suitable provider for your country, it maybe that the an Operations Centre MUST first be created."'' with ''"If a'' <br />
provider is not yet available for your country, then an alternative existing Operations Centre can be contacted."''. Now site responsiveness through its mail contacts is requested from the being of the certification process.'' <br />
<br />
|-<br />
| 0.8 <br />
| Tiziana Ferrari <br />
| 2011-03-11 <br />
| Updated introduction, adopted MUST SHALL etc. terminology, proposed some changes to terminology, added a section with a list of responsibilities, added a few comments into the text to request clarifications.<br />
|-<br />
| 0.7 <br />
| Vera Hansper <br />
| 2011-02-02 <br />
| Updated introduction to include roles, etc. and added required documentation link for policies<br />
|}<br />
--> <br> <br />
<br />
= Revision History =<br />
<br />
*25/10/2011: (editorial, T. Ferrari) Replacement of RIP with "RP" standing for Resource infrastructure Provider<br />
<br />
{{Template:Creative_commons}} <br />
<br />
[[Category:Procedures]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Operations_Procedures&diff=40222Operations Procedures2012-09-07T08:59:04Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Doc_menubar}}<br />
[[Category:Procedures|!]]<br />
[[category:Index]]<br />
__TOC__<br />
<br />
= Operations =<br />
<br />
EGI Operational Procedures are prescriptive documents that describe step-by-step processes involving several partners. The purpose of a procedure is define the related workflow. Procedures are approved by the OMB and are periodically reviewed. <br />
<br />
{| border="1" class="wikitable sortable"<br />
|- style="background-color: lightgray;"<br />
| '''Number''' <br />
| '''Status''' <br />
| '''Area''' <br />
| '''Relevant to''' <br />
| '''Title''' <br />
| '''Comment'''<br />
|-<br />
| [[PROC01|PROC 01]] <br />
| ''approved'', October 26 2010 <br />
| Ticket Management <br />
| Resource Centre Administrators, Operations Centres, COD <br />
| [[PROC01|COD Escalation Procedure]] <br />
| Operations ticket escation<br />
|-<br />
| [[PROC02|PROC 02]] <br />
| ''approved'', August 17 2010 <br />
| Operations Centre Management <br />
| Operations Centres, COD <br />
| [[PROC02|Operations Centre Creation]] <br />
| Step-by-step instructions on how to create a new Operations Centre<br />
|-<br />
| [[PROC03|PROC 03]] <br />
| ''approved'', October 26 2010 <br />
| Operations Centre Management <br />
| Operations Centres, COD <br />
| [[PROC03|Operations Centre decommissioning]] <br />
| Step-by-step instructions on how to decommission an Operations Centre<br />
|-<br />
| [[Availability and reliability monthly statistics#Process_for_quality_verification|PROC 04]] <br />
| ''approved'', August 17 2010 <br />
| Availability and Monitoring <br />
| Resource Centre Administrators, Operations Centres, COD <br />
| [[Availability and reliability monthly statistics#Process_for_quality_verification|Quality verification of monthly availability and reliability statistcs]] <br />
| Instructions RODs and Operations Centres on how to handle justification for poor monthly performance through GGUS<br />
|-<br />
| [[PROC05|PROC 05]] <br />
| ''approved'', August 17 2010 <br />
| Availability and Monitoring <br />
| Operations Centres, COD <br />
| [https://twiki.cern.ch/twiki/bin/view/EGEE/ValidateROCNagios Validation of a Operations Centre Nagios] <br />
| This procedure is part of the [[Operations Centre creation process coordination|Operations Centre creation]] procedure.<br />
|-<br />
| [[PROC06|PROC 06]] <br />
| ''approved'', Nov 23 2010 <br />
| Availability and Monitoring <br />
| Operations Centres, COD <br />
| [[PROC06|Setting a Nagios test status to OPERATIONS]] <br />
| A Nagios probe is set to OPERATIONS when its results are used to generate notifications for the Operations Dashboard. This procedure details the steps to turn a Nagios test to OPERATIONs.<br />
|-<br />
| [[PROC07|PROC 07]] <!-- Procedure number --> <br />
| ''approved'', Mar 28 2011 <!-- Status --> <br />
| Availability and Monitoring <!-- Area --> <br />
| Resource Centre Administrators, Operations Centres, COD <!-- Relevant to --> <br />
| [[PROC07|Adding new probes to SAM]] <!-- Title --> <br />
| Addition of new OPS Nagios probes to the SAM release. <!-- Comment --><br />
|-<br />
| [[PROC08|PROC 08]] <!-- Procedure number --> <br />
| ''approved'', Mar 28 2011 <!-- Status --> <br />
| Availability and Monitoring <!-- Area --> <br />
| Resource Centre Administrators, Operations Centres, COD <!-- Relevant to --> <br />
| [[PROC08|Management of the EGI OPS Availability and Reliability Profile]] <!-- Title --> <br />
| Request of a OPS EGI Availability and Reliability profile. A change in the profile is needed every time a new Nagios test needs to be added/removed to/from the profile, in order to have its results included/removed in/from Availability and Reliability monthly statistics. <!-- Comment --><br />
|-<br />
|[[PROC09|PROC 09]] <!-- Procedure number --> <br />
| ''approved May 17 2011''<br />
| Resource Centre Management<br />
| Resource Centre Administrator, Operations Centres<br />
| [[PROC09|Resource Centre Registration and Certification Procedure]] <!-- Title --><br />
| Registration of a new Resource Centre in the GOCDB<br />
|-<br />
|[[PROC10|PROC 10]] <!-- Procedure number --> <br />
| ''approved'', Oct 17 2011 <!-- Status --> <br />
| Availability and Monitoring <!-- Area --> <br />
| Resource Centre Administrators, Operations Centres<!-- Relevant to --> <br />
| [[PROC10|Recomputation of monitoring results and availability statistics]] <!-- Title --> <br />
| Notification of problems with the monitoring results gathered by SAM and to request a recomputation of results and the related availability and reliability statistics<br />
|-<br />
| [[PROC11|PROC 11]]<br />
| ''approved'', Feb 28 2012<br />
| Resource Centre Management<br />
| Resource Centre Administrator, Operations Centres<br />
| [[PROC11|Resource Centre Decommissioning Procedure]]<br />
| Decommissioning of a Resource Centre before it is turned into CLOSED in GOCDB<br />
|-<br />
| [[PROC12|PROC 12]]<br />
| ''approved'', Feb 28 2012<br />
| Resource Centre Management<br />
| Resource Centre Administrator, Operations Centres<br />
| [[PROC12|Production Service Decommissioning Procedure]]<br />
| Decommissioning of a EGI production service <br />
|-<br />
| [[PROC13|PROC 13]]<br />
| ''approved'', Jul 17 2012<br />
| VO Management<br />
| VO Managers, Operations Manager<br />
| [[PROC13|Vo Deregistration Procedure]]<br />
| Decommissioning of a Virtual Organization supported by the European Grid Infrastructure <br />
|}<br />
<br />
= Security =<br />
{|border="1" class="wikitable sortable" border="1<br />
|- style="background-color:lightgray;"<br />
| '''Number'''<br />
| '''Status'''<br />
| '''Area'''<br />
| '''Relevant to'''<br />
| '''Title'''<br />
| '''Comment'''<br />
|-<br />
| SEC 01<br />
| ''approved'', July 2010 (MS405)<br />
| Security <br />
| Resource Centres, EGI CSIRT<br />
| [https://documents.egi.eu/document/710 EGI Security Incident Handling]<br />
| The "Security Incident Handling Procedure" define site and incident coordinator responsibilities when handling Grid-related security incident. ALL EGI sites are required to follow this procedure to report and handle Grid-related security incident. <br />
|-<br />
| SEC 02 <!-- number --><br />
| ''approved'', July 2010 (MS405) <!-- status, date of approval --><br />
| Security <!-- area --><br />
| Resource Centres, Risk Assessment Team, Technology Providers, SVG <!-- Relevant to --><br />
| [https://documents.egi.eu/document/717 EGI Vulnerability issue handling process] <!-- title and wiki link --><br />
| The process used to report and resolve Grid Software vulnerabilities in the EGI Inspire project. <!-- comment--><br />
|-<br />
| [[SEC03|SEC 03]] <!-- number --><br />
| ''approved'', March 15 2011 <!-- status, date of approval --><br />
| Security <!-- area --><br />
| Resource Centres, Operations Centres, EGI-CSIRT, SVG <!-- Relevant to --><br />
| [https://documents.egi.eu/document/283 Critical Vulnerability Operational Procedure] <!-- title and wiki link --><br />
| After a problem has been assessed as critical, and a solution is available, then sites are required to take action. This document primarily defines the procedure from this time, where sites are asked to take action, and what steps are taken if they do not respond or do not take action. If a site fails to take action, this may lead to site suspension. <!-- comment--><br />
|-<br />
|}<br />
<br />
[https://wiki.egi.eu/wiki/EGI_CSIRT:Policies#EGI_Operational_Security_Procedures More information]<br />
<br />
= EGI Policies and Procedures =<br />
<br />
See all [https://wiki.egi.eu/wiki/SPG:Documents EGI policies and procedures]<br />
<br />
= Contacts =<br />
If you wish to report problems with this page, or want to suggest additions and improvements please contact:<br />
<br />
'''operational-documentation-manuals[at]mailman.egi.eu '''</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=WI03_RC_and_RP_OLA_violation_report_followup&diff=39579WI03 RC and RP OLA violation report followup2012-08-10T14:21:28Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
= Internal procedure for COD - '''Availability and reliability work instruction for COD''' =<br />
<br />
This page describes steps which should be taken by COD shifter to follow availability/reliability issues. <br />
<br />
<br> When GGUS ticket about availability/reliability metrics is assigned to COD: <br />
<br />
<br> <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! Timelines <br />
! Step <br />
! Substep <br />
! Description<br />
|-<br />
| <br />
| 1 <br />
| <br />
| Add ticket url to [https://wiki.egi.eu/wiki/Underperforming_sites_and_suspensions Underperforming_sites_and_suspensions] page<br />
|-<br />
| <br />
| 2 <br />
| <br />
| Ava/Rel report review<br />
|-<br />
| <br />
| <br />
| 1 <br />
| Prepare ''''sites for suspension'''' list: Look at&nbsp; availability metics for two previous months in AR report and the current one. If all are below 70% then sites qualifies for suspension. <br />
Check if the site was mentioned in [https://wiki.egi.eu/wiki/List_of_underperforming_sites List of sites for which the availability followup procedures were not applicable] page. In some cases there could be no need to open a ticket. <br />
<br />
|-<br />
| <br />
| <br />
| 2 <br />
| Prepare ''''sites to be asked for explanation'''' list: Look at current months in AR report. If Ava. is below 70% or Rel. below 75% then sites qualifies to be asked for explanation. This list should be prepared according to requirements for input file for [https://wiki.egi.eu/wiki/Availability_and_reliability_internal_procedure_for_COD#How_to_use_ticket_generator ticket generator]. <br />
Check if the site was mentioned in [https://wiki.egi.eu/wiki/List_of_underperforming_sites List of sites for which the availability followup procedures were not applicable] page In some cases there could be no need to open a ticket. <br />
<br />
|-<br />
| <br />
| 3 <br />
| <br />
| Create tickets for each case as a child to the tickets assigned to COD<br />
|-<br />
| <br />
| <br />
| 1 <br />
| For ''''sites for suspension'''' list please use [https://wiki.egi.eu/wiki/Availability_and_reliability_internal_procedure_for_COD#How_to_use_ticket_generator ticket generator]<br />
|-<br />
| <br />
| <br />
| 2 <br />
| For ''''sites to be asked for explanation'''' list please use [https://wiki.egi.eu/wiki/Availability_and_reliability_internal_procedure_for_COD#How_to_use_ticket_generator ticket generator]<br />
|-<br />
| '''Within''' 10 working days from when the tickets are created. <br />
| 4 <br />
| <br />
| <br />
'''Handling of sites below targets''' <br />
<br />
When explanation is provided and is found satisfactory put as a solution of the ticket <br />
<pre>'The explanation is satisfactory. Thank you!'. </pre> <br />
After that you should set child ticket to 'verified' status. <br />
<br />
|-<br />
| '''After''' 10 working days from when the tickets are created. <br />
| 5 <br />
| <br />
| Final actions.<br />
|-<br />
| <br />
| <br />
| 1 <br />
| '''Handling of sites that are eligible for suspension''' <br />
*in the case of '''no''' NGI intervention, the site is suspended in GOC DB - as a reason put a link to GGUS ticket created for the site <br />
*in the case of NGI intervention, non suspension will occur if both the COD and COO agree on the reasoning provided by the NGI <br />
**COO should be involved to the ticket<br />
<br />
|-<br />
| <br />
| <br />
| 2 <br />
| '''Handling of sites below targets''' <br />
If the explanation is not given in due time, or the explanation is found inadequate, COD send mail to NGI/ROC manager with CC to ROD and GGUS: <br />
<br />
*informing that NGI/ROC manager should make the site react on the ticket or suspend the site within 3 days <br />
*if NGI will not react COD will suspend the site on the 4th day.<br />
<pre>Dear XX<br />
<br />
I would like to inform you that 10 working days passed.<br />
Please make the site react on the ticket or suspend the site within 3 days.<br />
If NGI will not react COD will suspend the site on the 4th day.<br />
<br />
Best Regards<br />
XXX<br />
On behalf of COD team<br />
</pre><br />
|-<br />
| <br />
| 6 <br />
| <br />
| Prepare summary report (it should be placed in parent ticket): <br />
#sites which are not responsive and didn't provided satisfactory explanation <br />
#sites which were suspended <br />
#ROCs/NGIs which are not responsive <br />
#...<br />
<br />
|-<br />
| <br />
| 7 <br />
| <br />
| Update [https://wiki.egi.eu/wiki/List_of_underperforming_sites List of sites for which the availability followup procedures were not applicable] page. Put here outstanding cases which should be recorded. This could be used for example to avoid opening a ticket next month for a solved issue.<br />
|-<br />
| <br />
| 8 <br />
| <br />
| Update [https://wiki.egi.eu/wiki/Underperforming_sites_and_suspensions Underperforming_sites_and_suspensions] page.<br />
|}<br />
<br />
= Questions/issues =<br />
<br />
''MR: what do we do with sites marked with "n/a"?'' <br />
<br />
''MK: we don't take into account months with "N/A" '' <br />
<br />
<br> <span style="color: rgb(255, 0, 0);">'''VERY IMPORTANT'''</span> <br />
<br />
<span style="background: none repeat scroll 0% 0% rgb(255, 0, 0);"> In grid view NGIs/ROCs are named differently then in GGUS. You should change NGI/ROC name according to GGUS.</span> <br />
<br />
<br> <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! GGUS <br />
! Gridview<br />
|-<br />
| ROC_DECH <br />
| GermanySwitzerland<br />
|-<br />
| NGI_FRANCE <br />
| NGI_France<br />
|-<br />
| ROC_Asia/Pacific <br />
| AsiaPacific<br />
|-<br />
| ROC_Italy <br />
| Italy<br />
|-<br />
| ROC_CERN <br />
| CERN<br />
|-<br />
| ROC_Russia <br />
| Russia<br />
|-<br />
| ROC_North <br />
| NorthernEurope<br />
|-<br />
| ROC_UK/Ireland <br />
| UKI<br />
|-<br />
| ROC_SE <br />
| SouthEasternEurope<br />
|-<br />
| ROC_SW <br />
| SouthWesternEurope<br />
|}<br />
<br />
= Tickets content =<br />
<br />
== Request for explanation ==<br />
<pre>Subject:$SU/$siteName - availability/reliability statistics for $date<br />
<br />
Dear $SU,<br />
<br />
According to recent availability/reliability report $siteName has achieved<br />
poor performance Ava. $availability Rel. $realiability.<br />
More details: https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_statistics.<br />
<br />
Could you please provide explanations for poor performance of the $siteName site?<br />
<br />
Your explanation must be returned within 10 working days from when the ticket is created.<br />
If the explanation is not given in due time, or the explanation is found inadequate,<br />
COD escalation procedure will be followed https://wiki.egi.eu/wiki/Operations:COD_Escalation_Procedure<br />
<br />
If the site was certified during last month please close this ticket and <br />
put this info in a ticket solution field. There is known bug in report <br />
generation tool being worked on.<br />
<br />
<br />
Best Regards,<br />
EGI Central Operator on Duty<br />
</pre> <br />
== Site for suspension ==<br />
<pre>Subject:$SU/$siteName site suspension<br />
<br />
Dear $SU,<br />
<br />
According to recent availability/reliability report $siteName has achieved<br />
poor performance below target Ava. 50% or Rel. 50% in three consecutive months.<br />
More details: https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_statistics.<br />
<br />
According to procedures approved on OMB 17.08, site will be suspended within 10 working days unless the NGI intervene.<br />
If you think that the site should not be suspended please provide justification within 10 working days.<br />
<br />
Best Regards,<br />
EGI Central Operator on Duty<br />
</pre> <br />
= How to use ticket generator =<br />
<br />
current version of the script: 3.0 <br />
<br />
features: <br />
<br />
*bulk child ticket creation <br />
*'assigned to' set <br />
*'affected site' set <br />
*'type of problem' set to Operations<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
*'''Configure the script'''.<br />
<br />
In start-explanations.pl/start-suspend.pl file at the beginning of the script you have to fill in following variable: <br />
<pre># PRODUCTION<br />
my $endpoint = "https://gusiwr.fzk.de/arsys/services/ARService?server=gusiwr&amp;webService=Grid_HelpDesk";<br />
my $user = ""; # login to GGUS web-services<br />
my $pass = ""; # password to GGUS web-services<br />
<br />
# Submitter data, Those data will be used as submitter's data to create tickets<br />
my $Mail = ""; # your email address<br />
my $DN = ""; # your DN<br />
my $Name = ""; # Name and Surname<br />
</pre> <br />
<br> <br />
<br />
*'''Prepare input file.'''<br />
<br />
The input plain file format for both scripts is as follow: <br />
<br />
''ROC/NGI support unit in GGUS; Site name; Availability; Reliability;'' <br />
<br />
Remember that in each line should be one site and the number of semicolons should be always 4. For start-suspend.pl script Availability and Reliability values are omitted but semicolons are necessary. <br />
<br />
example: <br />
<pre>NGI_PL; CYFRONET_LCG2; 50%; 10%;<br />
NGI_PL; IFJ-PAN; 15%; 3%;<br />
</pre> <br />
*'''Execute the tool'''<br />
<br />
Login to machine with perl installed and execute the script as follow: <br />
<br />
''perl start-explanations.pl/start-suspend.pl PARENT_TICKET_ID "DATE" FILE_NAME'' <br />
<br />
PARENT_TICKET_ID - number of "Availability/reliability statistics for *" ticket <br />
<br />
DATE - date of the report. Format: "month year" <br />
<br />
FILE_NAME - file with input availability/reliability data <br />
<br />
example: <br />
<pre> perl start-explanations.pl 4121 "May 2010" dane.txt<br />
</pre> <br />
= Best practice =<br />
<br />
*If the site explaining that site administrator was on holidays put as a solution "This time the explanation is found satisfactory, although for the future in case of administrators holidays site should provide administrator deputy. If it is not possible then NGI should put site which is failing in downtime. Thank you!". Close the ticket and verify it.<br />
<br />
[[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=WI03_RC_and_RP_OLA_violation_report_followup&diff=39578WI03 RC and RP OLA violation report followup2012-08-10T14:16:43Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
= Internal procedure for COD - '''Availability and reliability work instruction for COD''' =<br />
<br />
This page describes steps which should be taken by COD shifter to follow availability/reliability issues. <br />
<br />
<br> When GGUS ticket about availability/reliability metrics is assigned to COD: <br />
<br />
<br> <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! Timelines <br />
! Step <br />
! Substep <br />
! Description<br />
|-<br />
| <br />
| 1 <br />
| <br />
| Add ticket url to [https://wiki.egi.eu/wiki/Underperforming_sites_and_suspensions Underperforming_sites_and_suspensions] page<br />
|-<br />
| <br />
| 2 <br />
| <br />
| Ava/Rel report review<br />
|-<br />
| <br />
| <br />
| 1 <br />
| Prepare ''''sites for suspension'''' list: Look at&nbsp; availability metics for two previous months in AR report and the current one. If all are below 70% then sites qualifies for suspension. <br />
Check if the site was mentioned in [https://wiki.egi.eu/wiki/List_of_underperforming_sites List of sites for which the availability followup procedures were not applicable] page. In some cases there could be no need to open a ticket. <br />
<br />
|-<br />
| <br />
| <br />
| 2 <br />
| Prepare ''''sites to be asked for explanation'''' list: Look at current months in AR report. If Ava. is below 70% or Rel. below 75% then sites qualifies to be asked for explanation. This list should be prepared according to requirements for input file for [https://wiki.egi.eu/wiki/Availability_and_reliability_internal_procedure_for_COD#How_to_use_ticket_generator ticket generator]. <br />
Check if the site was mentioned in [https://wiki.egi.eu/wiki/List_of_underperforming_sites List of sites for which the availability followup procedures were not applicable] page In some cases there could be no need to open a ticket. <br />
<br />
|-<br />
| <br />
| 3 <br />
| <br />
| Create tickets for each case as a child to the tickets assigned to COD<br />
|-<br />
| <br />
| <br />
| 1 <br />
| For ''''sites for suspension'''' list please use [https://wiki.egi.eu/wiki/Availability_and_reliability_internal_procedure_for_COD#How_to_use_ticket_generator ticket generator]<br />
|-<br />
| <br />
| <br />
| 2 <br />
| For ''''sites to be asked for explanation'''' list please use [https://wiki.egi.eu/wiki/Availability_and_reliability_internal_procedure_for_COD#How_to_use_ticket_generator ticket generator]<br />
|-<br />
| '''Within''' 10 working days from when the tickets are created. <br />
| 4 <br />
| <br />
| <br />
'''Handling of sites below targets'''<br />
When explanation is provided and is found satisfactory put as a solution of the ticket<br />
<pre>'The explanation is satisfactory. Thank you!'. </pre> <br />
After that you should set child ticket to 'verified' status. <br />
<br />
|-<br />
| '''After''' 10 working days from when the tickets are created. <br />
| 5 <br />
| <br />
| Final actions.<br />
|-<br />
| <br />
| <br />
| 1 <br />
| '''Handling of sites that are eligible for suspension''' <br />
*in the case of '''no''' NGI intervention, the site is suspended in GOC DB - as a reason put a link to GGUS ticket created for the site <br />
*in the case of NGI intervention, non suspension will occur if both the COD and COO agree on the reasoning provided by the NGI <br />
**COO should be involved to the ticket<br />
<br />
|-<br />
| <br />
| <br />
| 2 <br />
| '''Handling of sites below targets''' <br />
If the explanation is not given in due time, or the explanation is found inadequate, COD send mail to NGI/ROC manager with CC to ROD and GGUS: <br />
<br />
*informing that NGI/ROC manager should make the site react on the ticket or suspend the site within 3 days <br />
*if NGI will not react COD will suspend the site on the 4th day.<br />
<pre>Dear XX<br />
<br />
I would like to inform you that 10 working days passed.<br />
Please make the site react on the ticket or suspend the site within 3 days.<br />
If NGI will not react COD will suspend the site on the 4th day.<br />
<br />
Best Regards<br />
XXX<br />
On behalf of COD team<br />
</pre><br />
|-<br />
| <br />
| 6 <br />
| <br />
| Prepare summary report (it should be placed in parent ticket): <br />
#sites which are not responsive and didn't provided satisfactory explanation <br />
#sites which were suspended <br />
#ROCs/NGIs which are not responsive <br />
#...<br />
<br />
|-<br />
| <br />
| 7 <br />
| <br />
| Update [https://wiki.egi.eu/wiki/List_of_underperforming_sites List of sites for which the availability followup procedures were not applicable] page. Put here outstanding cases which should be recorded. This could be used for example to avoid opening a ticket next month for a solved issue.<br />
|-<br />
| <br />
| 8 <br />
| <br />
| Update [https://wiki.egi.eu/wiki/Underperforming_sites_and_suspensions Underperforming_sites_and_suspensions] page.<br />
|}<br />
<br />
= Questions/issues =<br />
<br />
''MR: what do we do with sites marked with "n/a"?'' <br />
<br />
''MK: we don't take into account months with "N/A" '' <br />
<br />
<br> <span style="color: rgb(255, 0, 0);">'''VERY IMPORTANT'''</span> <br />
<br />
<span style="background: none repeat scroll 0% 0% rgb(255, 0, 0);"> In grid view NGIs/ROCs are named differently then in GGUS. You should change NGI/ROC name according to GGUS.</span> <br />
<br />
<br> <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! GGUS <br />
! Gridview<br />
|-<br />
| ROC_DECH <br />
| GermanySwitzerland<br />
|-<br />
| NGI_FRANCE <br />
| NGI_France<br />
|-<br />
| ROC_Asia/Pacific <br />
| AsiaPacific<br />
|-<br />
| ROC_Italy <br />
| Italy<br />
|-<br />
| ROC_CERN <br />
| CERN<br />
|-<br />
| ROC_Russia <br />
| Russia<br />
|-<br />
| ROC_North <br />
| NorthernEurope<br />
|-<br />
| ROC_UK/Ireland <br />
| UKI<br />
|-<br />
| ROC_SE <br />
| SouthEasternEurope<br />
|-<br />
| ROC_SW <br />
| SouthWesternEurope<br />
|}<br />
<br />
= Tickets content =<br />
<br />
== Request for explanation ==<br />
<pre>Subject:$SU/$siteName - availability/reliability statistics for $date<br />
<br />
Dear $SU,<br />
<br />
According to recent availability/reliability report $siteName has achieved<br />
poor performance Ava. $availability Rel. $realiability.<br />
More details: https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_statistics.<br />
<br />
Could you please provide explanations for poor performance of the $siteName site?<br />
<br />
Your explanation must be returned within 10 working days from when the ticket is created.<br />
If the explanation is not given in due time, or the explanation is found inadequate,<br />
COD escalation procedure will be followed https://wiki.egi.eu/wiki/Operations:COD_Escalation_Procedure<br />
<br />
If the site was certified during last month please close this ticket and <br />
put this info in a ticket solution field. There is known bug in report <br />
generation tool being worked on.<br />
<br />
<br />
Best Regards,<br />
EGI Central Operator on Duty<br />
</pre> <br />
== Site for suspension ==<br />
<pre>Subject:$SU/$siteName site suspension<br />
<br />
Dear $SU,<br />
<br />
According to recent availability/reliability report $siteName has achieved<br />
poor performance below target Ava. 50% or Rel. 50% in three consecutive months.<br />
More details: https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_statistics.<br />
<br />
According to procedures approved on OMB 17.08, site will be suspended within 10 working days unless the NGI intervene.<br />
If you think that the site should not be suspended please provide justification within 10 working days.<br />
<br />
Best Regards,<br />
EGI Central Operator on Duty<br />
</pre> <br />
= How to use ticket generator =<br />
<br />
current version of the script: 3.0 <br />
<br />
features: <br />
<br />
*bulk child ticket creation <br />
*'assigned to' set <br />
*'affected site' set <br />
*'type of problem' set to Operations<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
*'''Configure the script'''.<br />
<br />
In start-explanations.pl/start-suspend.pl file at the beginning of the script you have to fill in following variable: <br />
<pre># PRODUCTION<br />
my $endpoint = "https://gusiwr.fzk.de/arsys/services/ARService?server=gusiwr&amp;webService=Grid_HelpDesk";<br />
my $user = ""; # login to GGUS web-services<br />
my $pass = ""; # password to GGUS web-services<br />
<br />
# Submitter data, Those data will be used as submitter's data to create tickets<br />
my $Mail = ""; # your email address<br />
my $DN = ""; # your DN<br />
my $Name = ""; # Name and Surname<br />
</pre> <br />
<br> <br />
<br />
*'''Prepare input file.'''<br />
<br />
The input plain file format for both scripts is as follow: <br />
<br />
''ROC/NGI support unit in GGUS; Site name; Availability; Reliability;'' <br />
<br />
Remember that in each line should be one site and the number of semicolons should be always 4. For start-suspend.pl script Availability and Reliability values are omitted but semicolons are necessary. <br />
<br />
example: <br />
<pre>NGI_PL; CYFRONET_LCG2; 50%; 10%;<br />
NGI_PL; IFJ-PAN; 15%; 3%;<br />
</pre> <br />
*'''Execute the tool'''<br />
<br />
Login to machine with perl installed and execute the script as follow: <br />
<br />
''perl start-explanations.pl/start-suspend.pl PARENT_TICKET_ID "DATE" FILE_NAME'' <br />
<br />
PARENT_TICKET_ID - number of "Availability/reliability statistics for *" ticket <br />
<br />
DATE - date of the report. Format: "month year" <br />
<br />
FILE_NAME - file with input availability/reliability data <br />
<br />
example: <br />
<pre> perl start-explanations.pl 4121 "May 2010" dane.txt<br />
</pre> <br />
= Best practice =<br />
<br />
*If the site explaining that site administrator was on holidays put as a solution "This time the explanation is found satisfactory, although for the future in case of administrators holidays site should provide administrator deputy. If it is not possible then NGI should put site which is failing in downtime. Thank you!". Close the ticket and verify it.<br />
<br />
[[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Regional_Operator_on_Duty&diff=38055Regional Operator on Duty2012-07-06T10:01:32Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
= Introduction =<br />
<br />
ROD team is responsible for solving problems on the infrastructure within own Operations Centre according to agreed procedures. They ensure that problems are properly recorded and progress according to specified time lines. They ensure that necessary information is available to all parties. The team is provided by each Operations Centre and requires procedural knowledge on the process. <br />
<br />
The purpose of this page is to collect in one place all materials related to ROD work. <br />
<br />
<br> <br />
<br />
'''If you are new in this activity please see first page '''[https://wiki.egi.eu/wiki/Grid_operations_oversight/ROD_Welcome_page '''ROD Welcome'''] <br />
<br />
= People and Contact =<br />
<br />
The list of people responsible for NGI oversight and contact points can be found in [https://operations-portal.in2p3.fr/dashboard/regionalPreferences Operations Portal]. <br />
<br />
To contact with all ROD teams can be used following mailing list where are subscribed all RODs' mailing lists: <br />
<br />
*'''all-operator-on-duty''' AT mailman.egi.eu<br />
<br />
= ROD duties =<br />
<br />
The Regional Operations team is responsible for detecting problems, coordinating the diagnosis, and monitoring the problems through to a resolution. It monitors sites in their region, and react to problems identified by the monitors, either<br>directly or indirectly, provide support to sites as needed, add to the knowledge base, and provide informational flow to oversight bodies in cases of non-reactive or non-responsive sites. ROD is a team responsible for solving problems on the infrastructure according to agreed procedures. They ensure that problems are properly recorded and progress according to specified time lines. They ensure that necessary information is available to all parties. The team is provided by each ROC and requires procedural knowledge on the process (rather than technical skills) for their work. <br />
<br />
All duties listed are mandatory for ROD team:<br> <br />
<br />
*'''Handling incidents '''- The main responsibility of ROD is to deal with incidents at sites in the region. This includes making sure that the tickets are opened and handled properly. The procedure for handling tickets is described in [https://wiki.egi.eu/wiki/PROC01 COD esclation procedure]<br> <br />
*'''Propagate actions from COD down to sites''' - ROD is responsible for ensuring that decisions taken on the COD level are propagated to sites. <br />
*'''Putting a site in downtime or suspend for urgent matters''' - In general, ROD can place a site in downtime (in the GOCDB) if it is either requested by the site, or ROD sees an urgent need to put the site into downtime. ROD may also suspend a site, under exceptional circumstances, without going through all the steps of the escalation procedure. For example, if a security hazard occurs, ROD must suspend a site on the spot in the case of such an emergency. It is important to know that COD can also suspend a site in the case of an emergency e.g. security incidents or lack of response. <br />
*'''Notify COD about core or urgent matters''' - ROD should create tickets to COD in the case of core or urgent matters.<br />
<br />
= Manuals and procedures =<br />
<br />
In this section are linked manuals and procedures which RODs should be familiar with&nbsp;: <br />
<br />
*[[PROC01|COD Escalation Procedure]] <br />
*[https://documents.egi.eu/document/301 Dashboard HowTOs and Training Guides]<br />
<br />
*[[Grid operations oversight/ROD FAQ|ROD FAQ ]] <br />
*[[Operations Best Practices|Operations Best practices]]<br />
<br />
== Video tutorials ==<br />
<br />
*[http://www.youtube.com/watch?v=p-SrqJMDlOo 1. How to become a ROD member] - 7 steps which should be done to become a ROD member<br />
<br />
*[http://www.youtube.com/watch?v=bNm4oupAmqI 2. Operations tools] - brief introduction of operations tools which a ROD mamber needs to perform duties<br />
<br />
*[http://www.youtube.com/watch?v=rmgdaziDhUk 3. How to handle alarms] - an instruction how to manage alarms on the Operations Portal (ticket creation from an alarm, closing and masking alarms)&nbsp;&nbsp;<br />
<br />
*[http://www.youtube.com/watch?v=NKkbnwWnADw 4. How to handle tickets] - an instruction how to manage tickets on the Operations Portal (ticket creation, updating and closing tickets)<br />
<br />
*[http://www.youtube.com/watch?v=5EEInTO2dVE 5. Issues escalated to COD] - an introduction of cases which are escalated to COD and how to deal with<br />
<br />
*[http://www.youtube.com/watch?v=tsbcYoGNZls 6. Operations portal tools] - a brief introduction of the Operations Portal tools<br />
<br />
= ROD performance - Operations Support Metrics =<br />
<br />
The Operations Support Metrics are designed to provide an overview of operations support process in grid infrastructure. The operations support means all actions related to identification, investigation and operational problem solution. <br />
<br />
More information about metrics can be found in&nbsp; [[Grid operations oversight/OperationsSupportMetrics|Operations Support Metrics introduction]] <br />
<br />
*2011 <br />
**[https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-01.ods Jan]|[https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-02.ods Feb]| [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-03.ods Mar] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-04.ods Apr] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-05.ods May]|[https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-06.ods Jun]|[https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-07.ods Jul] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-08.ods Sept]| [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-09.ods Aug] <br />
*2010 <br />
**[https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-05.ods May] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-06.ods Jun] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-07.ods Jul] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-08.ods Aug] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-09.ods Sep] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-10.ods Oct] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-11.ods Nov] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-12.ods Dec]<br />
<br />
<br> <br />
<br />
Old [https://documents.egi.eu/secure/ShowDocument?docid=829 EGEE 3 metrics] <br />
<br />
= Newsletter<br> =<br />
<br />
A ROD Newsletter is periodically released since December 2010 to consolidate the Grid oversight teams (central and local ones). The purpose of this newsletter is to inform about recent and upcoming developments related to Grid Oversight and to show the support performance indicators during the month.&nbsp; <span lang="en" class="short_text" id="result_box"><span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">It</span> <span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">is</span> <span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">issued</span> <span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">every month</span></span> and the information about new releases is sent to all RODs mailing list and to NGI managers.<br> <br />
<br />
*2012 <br />
**[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2001-2012.pdf Jan] | |[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2002-2012.pdf Feb] | [Mar] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2004-2012.pdf Apr] | [May]|[Jun]| [July]<br> <br />
*2011 <br />
**[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%201-2011.pdf Jan] | |[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2002-2011.pdf Feb] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2003-2011.pdf Mar] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2004-2011.pdf Apr] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2005-2011.pdf May]| [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2006-2011.pdf Jun] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2010-2011.pdf Oct] |&nbsp;[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2011-2011.pdf Nov] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2012-2011.pdf Dec]<br />
<br />
*2010 <br />
**[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2012-2010.pdf Dec]<br />
<br />
= ROD presentations =<br />
<br />
This section is created to collect all ROD presentations which took place on our f2f meetings. <br />
<br />
*[https://www.egi.eu/indico/getFile.py/access?contribId=210&sessionId=9&resId=0&materialId=slides&confId=207 NGI_IBERGRID]<br />
<br />
= Events =<br />
<br />
Technical Forum 2011 <br />
<br />
*[https://www.egi.eu/indico/contributionDisplay.py?contribId=35&confId=452 Grid Oversight session]<br><br />
<br />
User Forum 2011 <br />
<br />
*[https://www.egi.eu/indico/contributionDisplay.py?sessionId=9&contribId=91&confId=207 ROD teams training session] <br />
*[https://www.egi.eu/indico/contributionDisplay.py?sessionId=9&contribId=92&confId=207 Grid Oversight, ensuring the quality of the Grid infrastructure]<br />
<br />
EGI technical Forum 2010 <br />
<br />
*[https://www.egi.eu/indico/sessionDisplay.py?sessionId=117&confId=48#20100915 Grid Oversight, ensuring the quality of the Grid infrastructure] <br />
*[https://www.egi.eu/indico/sessionDisplay.py?sessionId=116&confId=48#all Grid Oversight Training]<br />
<br />
ROD teams workshop Jun 2010 <br />
<br />
*[https://www.egi.eu/indico/conferenceDisplay.py?ovw=True&confId=29 ROD teams workshop]<br />
<br />
= Resources =<br />
<br />
*[[Tools|Operations tools]] <br />
*[https://wiki.egi.eu/wiki/Operations_Procedures Operations Procedures]<br />
<br />
[[Category:COD]] [[Category:ROD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Underperforming_sites_and_suspensions&diff=37993Underperforming sites and suspensions2012-07-05T07:54:35Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
Information about underperforming and suspended Resource Centres is provided in the table below. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! date <br />
! GGUSID <br />
! nb. sites <br />
below 75%/70% targets <br />
<br />
! nb. sites <br />
below the target for 3 months <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
which didn't provide explanation <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
suspended by COD <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
! nb. sites <br />
suspended by CSIRT <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
|-<br />
| May 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=82784 82784] <br />
| 33 <br />
| 0<br> <br />
| 0<br />
| 0<br> <br />
| <br><br />
|-<br />
| April 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=81843 81843] <br />
| 34 <br />
| 3 <br />
*CEFET-RJ, ROC_IGALC, low availability for three months, suspended by ROC, [https://ggus.eu/ws/ticket_info.php?ticket=81974 81974] <br />
*ID-ITB, AsiaPacific, low availability for three months suspended by ROC, [https://ggus.eu/ws/ticket_info.php?ticket=81972 81972] <br />
*PH-ASTI-LIKNAYAN AsiaPacific, low availability for three months, site was suspended but set to certified in order to recertify it, [https://ggus.eu/ws/ticket_info.php?ticket=81973 81973]<br />
<br />
| 0 <br />
| 0 <br />
| <br><br />
|-<br />
| March 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=80900 80900] <br />
| 25 <br />
| <br />
2 <br />
<br />
*BY-BNTU, NGI_BY, not suspended because it achieves 86% in April, [https://ggus.eu/ws/ticket_info.php?ticket=81086 81086]<br> <br />
*AM-05-YSU, NGI_ARMENIA, site suspended by ROC, [https://ggus.eu/ws/ticket_info.php?ticket=81087 81087]<br><br />
<br />
| 0<br> <br />
| <br />
| <br><br />
|-<br />
| February 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79844 79844] <br />
| 35 <br />
| 3 <br />
| 0 <br />
| 2 suspended by ROC<br> <br />
*IN-DAE-VECC-02, 80037 <br />
*MY-UM-CRYSTAL, 80038<br />
<br />
| 0<br />
|-<br />
| January 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79020 79020] <br />
| 30 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 1; GARR-01-DIR, NGI_IT due to issue (EGI-20120116-01) recorded in RTIR ticket #3300)<br />
|-<br />
| December 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=78040 78040] <br />
| 28 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| November 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=77170 77170] <br />
| 26 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| October 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=76305 76305] <br />
| 45 <br />
| 3 <br />
| <br />
3<br> <br />
<br />
*ROC_Russia/RRC-KI, 76408 <br />
*NGI_IL/WEIZMANN-LCG2, 76386 <br />
*NGI_IL/TECHNION-HEP, 76384<br />
<br />
| <br />
1<br> <br />
<br />
*NGI_ARMGRID/AM-04-YERPHI,76428<br />
<br />
| 0<br />
|-<br />
| September 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74965 74965] <br />
| 25 <br />
| 6 <br />
| 0 <br />
| <br />
2<br> <br />
<br />
*ROC_Asia/Pacific/TW-NCUHEP, 3 consecutive months below the target (site suspended by ROC), #75041<br> <br />
*ROC_Asia/Pacific/IN-DAE-VECC-02, 4 consecutive months below the target (site suspended by COD), #75040<br />
<br />
| 0<br />
|-<br />
| August 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74147 74147] <br />
| 31 <br />
| 3 <br />
| 0 <br />
| 0 <br />
| 0<br />
|-<br />
| July 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=73193 73193] <br />
| 35 <br />
| 4 <br />
| 0 <br />
| <br />
2 <br />
<br />
*ROC_Asia/Pacific/TW-eScience, 3 consecutive months below the target(site suspended by ROC), ticket #73539<br> <br />
*ROC_Asia/Pacific/TW-NYMU-GRID,3 consecutive months below the target(site suspended by ROC), ticket #73540<br />
<br />
| 0<br />
|-<br />
| June 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=72259 72259] <br />
| 31 <br />
| 8 <br />
| 0 <br />
| 5 <br />
*ROC_Asia, Pacific/PH-ASTI-LIKNAYAN, 3 consecutive months below target, ticket #72435 <br />
*ROC_Asia, Pacific/TH-HAI, 3 consecutive months below target, #72436 <br />
*NGI_IBERGRID, UOGRID, 3 consecutive months below target, #72439 <br />
*ROC_IGALC, CEFET-RJ, 3 consecutive months below target, #72440 <br />
*ROC_IGALC, LA-MERIDA, 3 consecutive months below target, #72441<br />
<br />
| 0<br><br />
|-<br />
| May 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=71643 71643] <br />
| 23 <br />
| <br />
4 <br />
<br />
this month first time targed was changed to ava 70% rel 75% <br />
<br />
| 0 <br />
| 2 <br />
*UOGRID, NGI_IBERGRID, below 50%/50% for three months, 71787 <br />
*PH-ASTI-LIKNAYAN, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 71789&nbsp;<br />
<br />
| 0<br><br />
|-<br />
| April 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=70289 70289] <br />
| 39 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| March 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=69629 69629] <br />
| 30 <br />
| 0 <br />
| <br />
1 <br />
<br />
*ru-Moscow-SINP-LCG2, ROC_Russia, 69765<br><br />
<br />
| 0 <br />
| 0<br><br />
|-<br />
| February 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=68299 68299] / See also [https://gus.fzk.de/ws/ticket_info.php?ticket=68229 68229] <br />
| 28 <br />
| 0 <br />
| 1 <br />
*RU-SPbSU, ROC_Russia<br />
<br />
| <br> <br />
| 0<br><br />
|-<br />
| Jan 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=67008 67008] <br />
| 27 <br />
| 2 <br />
| 1 <br />
*ru-IMPB-LCG2,ROC_Russia, 67038<br />
<br />
| 2 <br />
*MY-UM-PANG5, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 67010 <br />
*ru-IMPB-LCG2,ROC_Russia, sites didn't provided explanation,67038<br />
<br />
| 0 <br><br />
|-<br />
| Dec 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=65971 65971] <br />
| 30 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0 <br><br />
|-<br />
| Nov 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=64892 64892] <br />
| 40 <br />
| 1 <br />
| 0 <br />
| 1 <br />
*ID-ITB, ROC_Asia/Pacific,below 50%/50% for three months (site suspended by ROC),64951<br />
<br />
| 0<br><br />
|-<br />
| Oct 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=63658 63658] <br />
| 37 <br />
| 4 <br />
| 1 <br />
*AM-04-YERPHI, NGI_ARMGRID, 63854<br />
<br />
| 2 <br />
*AM-01-IIAP-NAS-RA, NGI_ARMGRID, below 50%/50% for three months, 63837 <br />
*AM-04-YERPHI, NGI_ARMGRID, no explanation given, 63854<br />
<br />
| 0<br><br />
|-<br />
| Sep 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=62853 62853] <br />
| 39 <br />
| 2 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Aug 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61797 61797] <br />
| 43 <br />
| 3 <br />
| 10 <br />
*JP-HIROSHIMA-WLCG, ROC AP, 62323 <br />
*AU-PPS, ROC AP,62316 <br />
*MY-UTM-GRID, ROC AP, 62312 <br />
*TH-NECTEC-LSR, ROC AP, 62304 <br />
*MY-UM-CRYSTAL, ROC AP, 62300 <br />
*ID-ITB, ROC AP, 62296 <br />
*GRISU-COMETA-INFN-LNS, ROC Italy, 62314 <br />
*UNIGE-DPNC, NGI_NDGF, 62308 <br />
*ru-IMPB-LCG2, ROC_Russia, 62305 <br />
*IL-TAU-HEP,ROC_SE, 62306<br />
<br />
| 1 <br />
*TW-NCUHEP, ROC AP, below 50%/50% for three months, 62340<br />
<br />
| 0<br><br />
|-<br />
| Jul 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61115 61115] <br />
| 47 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Jun 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=60216 60216] <br />
| 59 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| May 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=59736 59736] <br />
| 38 <br />
| 3 <br />
| 1 <br />
*ru-Chernogolovka-IPCP-LCG2, ROC RU, 59819<br />
<br />
| 0 <br />
| 0<br><br />
|}<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]] [[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Underperforming_sites_and_suspensions&diff=37794Underperforming sites and suspensions2012-06-19T10:05:22Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
Information about underperforming and suspended Resource Centres is provided in the table below. <br />
<br />
{| cellspacing="0" cellpadding="5" border="1" align="center"<br />
|-<br />
! date <br />
! GGUSID <br />
! nb. sites <br />
below 75%/70% targets <br />
<br />
! nb. sites <br />
below the target for 3 months <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
which didn't provide explanation <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
suspended by COD <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
! nb. sites <br />
suspended by CSIRT <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
|-<br />
| May 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=82784 82784] <br />
| 33<br />
| 0<br> <br />
| <br />
| <br> <br />
| <br><br />
|-<br />
| April 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=81843 81843] <br />
| 34 <br />
| 3 <br />
*CEFET-RJ, ROC_IGALC, low availability for three months, suspended by ROC, [https://ggus.eu/ws/ticket_info.php?ticket=81974 81974] <br />
*ID-ITB, AsiaPacific, low availability for three months suspended by ROC, [https://ggus.eu/ws/ticket_info.php?ticket=81972 81972] <br />
*PH-ASTI-LIKNAYAN AsiaPacific, low availability for three months, site was suspended but set to certified in order to recertify it, [https://ggus.eu/ws/ticket_info.php?ticket=81973 81973]<br />
<br />
| 0 <br />
| 0 <br />
| <br><br />
|-<br />
| March 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=80900 80900] <br />
| 25 <br />
| <br />
2 <br />
<br />
*BY-BNTU, NGI_BY, not suspended because it achieves 86% in April, [https://ggus.eu/ws/ticket_info.php?ticket=81086 81086]<br> <br />
*AM-05-YSU, NGI_ARMENIA, site suspended by ROC, [https://ggus.eu/ws/ticket_info.php?ticket=81087 81087]<br><br />
<br />
| 0<br> <br />
| <br />
| <br><br />
|-<br />
| February 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79844 79844] <br />
| 35 <br />
| 3 <br />
| 0 <br />
| 2 suspended by ROC<br> <br />
*IN-DAE-VECC-02, 80037 <br />
*MY-UM-CRYSTAL, 80038<br />
<br />
| 0<br />
|-<br />
| January 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79020 79020] <br />
| 30 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 1; GARR-01-DIR, NGI_IT due to issue (EGI-20120116-01) recorded in RTIR ticket #3300)<br />
|-<br />
| December 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=78040 78040] <br />
| 28 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| November 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=77170 77170] <br />
| 26 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| October 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=76305 76305] <br />
| 45 <br />
| 3 <br />
| <br />
3<br> <br />
<br />
*ROC_Russia/RRC-KI, 76408 <br />
*NGI_IL/WEIZMANN-LCG2, 76386 <br />
*NGI_IL/TECHNION-HEP, 76384<br />
<br />
| <br />
1<br> <br />
<br />
*NGI_ARMGRID/AM-04-YERPHI,76428<br />
<br />
| 0<br />
|-<br />
| September 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74965 74965] <br />
| 25 <br />
| 6 <br />
| 0 <br />
| <br />
2<br> <br />
<br />
*ROC_Asia/Pacific/TW-NCUHEP, 3 consecutive months below the target (site suspended by ROC), #75041<br> <br />
*ROC_Asia/Pacific/IN-DAE-VECC-02, 4 consecutive months below the target (site suspended by COD), #75040<br />
<br />
| 0<br />
|-<br />
| August 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74147 74147] <br />
| 31 <br />
| 3 <br />
| 0 <br />
| 0 <br />
| 0<br />
|-<br />
| July 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=73193 73193] <br />
| 35 <br />
| 4 <br />
| 0 <br />
| <br />
2 <br />
<br />
*ROC_Asia/Pacific/TW-eScience, 3 consecutive months below the target(site suspended by ROC), ticket #73539<br> <br />
*ROC_Asia/Pacific/TW-NYMU-GRID,3 consecutive months below the target(site suspended by ROC), ticket #73540<br />
<br />
| 0<br />
|-<br />
| June 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=72259 72259] <br />
| 31 <br />
| 8 <br />
| 0 <br />
| 5 <br />
*ROC_Asia, Pacific/PH-ASTI-LIKNAYAN, 3 consecutive months below target, ticket #72435 <br />
*ROC_Asia, Pacific/TH-HAI, 3 consecutive months below target, #72436 <br />
*NGI_IBERGRID, UOGRID, 3 consecutive months below target, #72439 <br />
*ROC_IGALC, CEFET-RJ, 3 consecutive months below target, #72440 <br />
*ROC_IGALC, LA-MERIDA, 3 consecutive months below target, #72441<br />
<br />
| 0<br><br />
|-<br />
| May 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=71643 71643] <br />
| 23 <br />
| <br />
4 <br />
<br />
this month first time targed was changed to ava 70% rel 75% <br />
<br />
| 0 <br />
| 2 <br />
*UOGRID, NGI_IBERGRID, below 50%/50% for three months, 71787 <br />
*PH-ASTI-LIKNAYAN, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 71789&nbsp;<br />
<br />
| 0<br><br />
|-<br />
| April 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=70289 70289] <br />
| 39 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| March 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=69629 69629] <br />
| 30 <br />
| 0 <br />
| <br />
1 <br />
<br />
*ru-Moscow-SINP-LCG2, ROC_Russia, 69765<br><br />
<br />
| 0 <br />
| 0<br><br />
|-<br />
| February 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=68299 68299] / See also [https://gus.fzk.de/ws/ticket_info.php?ticket=68229 68229] <br />
| 28 <br />
| 0 <br />
| 1 <br />
*RU-SPbSU, ROC_Russia<br />
<br />
| <br> <br />
| 0<br><br />
|-<br />
| Jan 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=67008 67008] <br />
| 27 <br />
| 2 <br />
| 1 <br />
*ru-IMPB-LCG2,ROC_Russia, 67038<br />
<br />
| 2 <br />
*MY-UM-PANG5, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 67010 <br />
*ru-IMPB-LCG2,ROC_Russia, sites didn't provided explanation,67038<br />
<br />
| 0 <br><br />
|-<br />
| Dec 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=65971 65971] <br />
| 30 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0 <br><br />
|-<br />
| Nov 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=64892 64892] <br />
| 40 <br />
| 1 <br />
| 0 <br />
| 1 <br />
*ID-ITB, ROC_Asia/Pacific,below 50%/50% for three months (site suspended by ROC),64951<br />
<br />
| 0<br><br />
|-<br />
| Oct 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=63658 63658] <br />
| 37 <br />
| 4 <br />
| 1 <br />
*AM-04-YERPHI, NGI_ARMGRID, 63854<br />
<br />
| 2 <br />
*AM-01-IIAP-NAS-RA, NGI_ARMGRID, below 50%/50% for three months, 63837 <br />
*AM-04-YERPHI, NGI_ARMGRID, no explanation given, 63854<br />
<br />
| 0<br><br />
|-<br />
| Sep 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=62853 62853] <br />
| 39 <br />
| 2 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Aug 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61797 61797] <br />
| 43 <br />
| 3 <br />
| 10 <br />
*JP-HIROSHIMA-WLCG, ROC AP, 62323 <br />
*AU-PPS, ROC AP,62316 <br />
*MY-UTM-GRID, ROC AP, 62312 <br />
*TH-NECTEC-LSR, ROC AP, 62304 <br />
*MY-UM-CRYSTAL, ROC AP, 62300 <br />
*ID-ITB, ROC AP, 62296 <br />
*GRISU-COMETA-INFN-LNS, ROC Italy, 62314 <br />
*UNIGE-DPNC, NGI_NDGF, 62308 <br />
*ru-IMPB-LCG2, ROC_Russia, 62305 <br />
*IL-TAU-HEP,ROC_SE, 62306<br />
<br />
| 1 <br />
*TW-NCUHEP, ROC AP, below 50%/50% for three months, 62340<br />
<br />
| 0<br><br />
|-<br />
| Jul 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61115 61115] <br />
| 47 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Jun 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=60216 60216] <br />
| 59 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| May 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=59736 59736] <br />
| 38 <br />
| 3 <br />
| 1 <br />
*ru-Chernogolovka-IPCP-LCG2, ROC RU, 59819<br />
<br />
| 0 <br />
| 0<br><br />
|}<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]] [[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Regional_Operator_on_Duty&diff=37314Regional Operator on Duty2012-06-04T08:44:56Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
= Introduction =<br />
<br />
ROD team is responsible for solving problems on the infrastructure within own Operations Centre according to agreed procedures. They ensure that problems are properly recorded and progress according to specified time lines. They ensure that necessary information is available to all parties. The team is provided by each Operations Centre and requires procedural knowledge on the process. <br />
<br />
The purpose of this page is to collect in one place all materials related to ROD work. <br />
<br />
<br> <br />
<br />
'''If you are new in this activity please see first page '''[https://wiki.egi.eu/wiki/Grid_operations_oversight/ROD_Welcome_page '''ROD Welcome'''] <br />
<br />
= People and Contact =<br />
<br />
The list of people responsible for NGI oversight and contact points can be found in [https://operations-portal.in2p3.fr/dashboard/regionalPreferences Operations Portal]. <br />
<br />
To contact with all ROD teams can be used following mailing list where are subscribed all RODs' mailing lists: <br />
<br />
*'''all-operator-on-duty''' AT mailman.egi.eu<br />
<br />
= ROD duties =<br />
<br />
The Regional Operations team is responsible for detecting problems, coordinating the diagnosis, and monitoring the problems through to a resolution. It monitors sites in their region, and react to problems identified by the monitors, either<br>directly or indirectly, provide support to sites as needed, add to the knowledge base, and provide informational flow to oversight bodies in cases of non-reactive or non-responsive sites. ROD is a team responsible for solving problems on the infrastructure according to agreed procedures. They ensure that problems are properly recorded and progress according to specified time lines. They ensure that necessary information is available to all parties. The team is provided by each ROC and requires procedural knowledge on the process (rather than technical skills) for their work. <br />
<br />
All duties listed are mandatory for ROD team:<br> <br />
<br />
*'''Handling incidents '''- The main responsibility of ROD is to deal with incidents at sites in the region. This includes making sure that the tickets are opened and handled properly. The procedure for handling tickets is described in [https://wiki.egi.eu/wiki/PROC01 COD esclation procedure]<br> <br />
*'''Propagate actions from COD down to sites''' - ROD is responsible for ensuring that decisions taken on the COD level are propagated to sites. <br />
*'''Putting a site in downtime or suspend for urgent matters''' - In general, ROD can place a site in downtime (in the GOCDB) if it is either requested by the site, or ROD sees an urgent need to put the site into downtime. ROD may also suspend a site, under exceptional circumstances, without going through all the steps of the escalation procedure. For example, if a security hazard occurs, ROD must suspend a site on the spot in the case of such an emergency. It is important to know that COD can also suspend a site in the case of an emergency e.g. security incidents or lack of response. <br />
*'''Notify COD about core or urgent matters''' - ROD should create tickets to COD in the case of core or urgent matters.<br />
<br />
= Manuals and procedures =<br />
<br />
In this section are linked manuals and procedures which RODs should be familiar with&nbsp;: <br />
<br />
*[[PROC01|COD Escalation Procedure]] <br />
*[https://documents.egi.eu/document/301 Dashboard HowTOs and Training Guides]<br />
<br />
*[[Grid operations oversight/ROD FAQ|ROD FAQ ]] <br />
*[[Operations Best Practices|Operations Best practices]]<br />
<br />
== Video tutorials ==<br />
<br />
*[http://www.youtube.com/watch?v=p-SrqJMDlOo 1. How to become a ROD member] - 7 steps which should be done to become a ROD member<br />
<br />
*[http://www.youtube.com/watch?v=bNm4oupAmqI 2. Operations tools] - brief introduction of operations tools which a ROD mamber needs to perform duties<br />
<br />
*[http://www.youtube.com/watch?v=rmgdaziDhUk 3. How to handle alarms] - an instruction how to manage alarms on the Operations Portal (ticket creation from an alarm, closing and masking alarms)&nbsp;&nbsp;<br />
<br />
*[http://www.youtube.com/watch?v=NKkbnwWnADw 4. How to handle tickets] - an instruction how to manage tickets on the Operations Portal (ticket creation, updating and closing tickets)<br />
<br />
*[http://www.youtube.com/watch?v=5EEInTO2dVE 5. Issues escalated to COD] - an introduction of cases which are escalated to COD and how to deal with<br />
<br />
*[http://www.youtube.com/watch?v=tsbcYoGNZls 6. Operations portal tools] - a brief introduction of the Operations Portal tools<br />
<br />
= ROD performance - Operations Support Metrics =<br />
<br />
The Operations Support Metrics are designed to provide an overview of operations support process in grid infrastructure. The operations support means all actions related to identification, investigation and operational problem solution. <br />
<br />
More information about metrics can be found in&nbsp; [[Grid operations oversight/OperationsSupportMetrics|Operations Support Metrics introduction]] <br />
<br />
*2011 <br />
**[https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-01.ods Jan]|[https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-02.ods Feb]| [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-03.ods Mar] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-04.ods Apr] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-05.ods May]|[https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-06.ods Jun]|[https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-07.ods Jul] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-08.ods Sept]| [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2011-09.ods Aug] <br />
*2010 <br />
**[https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-05.ods May] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-06.ods Jun] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-07.ods Jul] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-08.ods Aug] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-09.ods Sep] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-10.ods Oct] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-11.ods Nov] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=2&filename=EGI-Operations_Support_Metrics-2010-12.ods Dec]<br />
<br />
<br> <br />
<br />
Old [https://documents.egi.eu/secure/ShowDocument?docid=829 EGEE 3 metrics] <br />
<br />
= Newsletter<br> =<br />
<br />
A ROD Newsletter is periodically released since December 2010 to consolidate the Grid oversight teams (central and local ones). The purpose of this newsletter is to inform about recent and upcoming developments related to Grid Oversight and to show the support performance indicators during the month.&nbsp; <span lang="en" id="result_box" class="short_text"><span title="Kliknij, aby wyświetlić alternatywne tłumaczenia" class="hps">It</span> <span title="Kliknij, aby wyświetlić alternatywne tłumaczenia" class="hps">is</span> <span title="Kliknij, aby wyświetlić alternatywne tłumaczenia" class="hps">issued</span> <span title="Kliknij, aby wyświetlić alternatywne tłumaczenia" class="hps">every month</span></span> and the information about new releases is sent to all RODs mailing list and to NGI managers.<br> <br />
<br />
*2012 <br />
**[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2001-2012.pdf Jan] | |[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2002-2012.pdf Feb] | [Mar] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2004-2012.pdf Apr] | [May]| <br />
*2011 <br />
**[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%201-2011.pdf Jan] | |[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2002-2011.pdf Feb] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2003-2011.pdf Mar] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2004-2011.pdf Apr] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2005-2011.pdf May]| [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2006-2011.pdf Jun] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2010-2011.pdf Oct] |&nbsp;[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2011-2011.pdf Nov] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2012-2011.pdf Dec]<br />
<br />
*2010 <br />
**[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2012-2010.pdf Dec]<br />
<br />
= ROD presentations =<br />
<br />
This section is created to collect all ROD presentations which took place on our f2f meetings. <br />
<br />
*[https://www.egi.eu/indico/getFile.py/access?contribId=210&sessionId=9&resId=0&materialId=slides&confId=207 NGI_IBERGRID]<br />
<br />
= Events =<br />
<br />
Technical Forum 2011 <br />
<br />
*[https://www.egi.eu/indico/contributionDisplay.py?contribId=35&confId=452 Grid Oversight session]<br><br />
<br />
User Forum 2011 <br />
<br />
*[https://www.egi.eu/indico/contributionDisplay.py?sessionId=9&contribId=91&confId=207 ROD teams training session] <br />
*[https://www.egi.eu/indico/contributionDisplay.py?sessionId=9&contribId=92&confId=207 Grid Oversight, ensuring the quality of the Grid infrastructure]<br />
<br />
EGI technical Forum 2010 <br />
<br />
*[https://www.egi.eu/indico/sessionDisplay.py?sessionId=117&confId=48#20100915 Grid Oversight, ensuring the quality of the Grid infrastructure] <br />
*[https://www.egi.eu/indico/sessionDisplay.py?sessionId=116&confId=48#all Grid Oversight Training]<br />
<br />
ROD teams workshop Jun 2010 <br />
<br />
*[https://www.egi.eu/indico/conferenceDisplay.py?ovw=True&confId=29 ROD teams workshop]<br />
<br />
= Resources =<br />
<br />
*[[Tools|Operations tools]] <br />
*[https://wiki.egi.eu/wiki/Operations_Procedures Operations Procedures]<br />
<br />
[[Category:COD]] [[Category:ROD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=WI05_Unresponsive_NGI_escalation&diff=37142WI05 Unresponsive NGI escalation2012-05-31T09:06:16Z<p>Mkrakowi: </p>
<hr />
<div>In case of not responding NGI, COD should:<br> <br />
<br />
#Send an email to NGI managers mailing list and to each of NGI managers and ask for action (email can be taken from [http://tinyurl.com/724emw5 GOC&nbsp;DB - NGIs List] or in Dashboard) <br />
#Make a phone call to NGI&nbsp;manager (phone number can be found in GOC&nbsp;DB&nbsp;- look at given NGI's detailes - do not forgot about time zones&nbsp;;) . If first one was unsuccesful please make a second call. <br />
#Set the ticket assigned to NGI to unsolved and create a new ticket to COO&nbsp;with full report about the situation.<br />
<br />
<br></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=WI05_Unresponsive_NGI_escalation&diff=37048WI05 Unresponsive NGI escalation2012-05-28T08:53:16Z<p>Mkrakowi: </p>
<hr />
<div>In case of not responding NGI, COD should:<br> <br />
<br />
#Send an email to NGI managers mailing list and to each of NGI managers and ask for action (email can be taken from [http://tinyurl.com/724emw5 GOC&nbsp;DB - NGIs List] or in Dashboard) <br />
#Make a phone call to NGI&nbsp;manager (phone number can be found in GOC&nbsp;DB&nbsp;- look at given NGI's detailes - do not forgot about time zones&nbsp;;) . If first one was unsuccesful please make a second call. <br />
#Mail to COO&nbsp;with full report about the situation.<br />
<br />
<br></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=WI05_Unresponsive_NGI_escalation&diff=37047WI05 Unresponsive NGI escalation2012-05-28T08:52:03Z<p>Mkrakowi: </p>
<hr />
<div>In case of not responding NGI, COD should:<br> <br />
<br />
#Send an email to NGI managers mailing list and to each of NGI managers and ask for action (email can be taken from [http://tinyurl.com/724emw5 GOC&nbsp;DB - NGIs List] or in Dashboard) <br />
#Make a phone call to NGI&nbsp;manager (phone number can be found in GOC&nbsp;DB&nbsp;- look at given NGI's detailes - do not forgot about time zones&nbsp;;) ) <br />
#Mail to COO&nbsp;with full report about the situation.<br />
<br />
<br></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=WI05_Unresponsive_NGI_escalation&diff=37046WI05 Unresponsive NGI escalation2012-05-28T08:07:33Z<p>Mkrakowi: </p>
<hr />
<div>In case of not responding NGI, COD should:<br> <br />
<br />
#Send an email to NGI managers mailing list and to each of NGI managers and ask for action (email can be taken from [http://tinyurl.com/724emw5 GOC&nbsp;DB - NGIs List]) <br />
#Make a phone call to NGI&nbsp;manager (phone number can be found in GOC&nbsp;DB&nbsp;- look at given NGI's detailes - do not forgot about time zones&nbsp;;) )<br />
<br />
<br></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=WI05_Unresponsive_NGI_escalation&diff=36826WI05 Unresponsive NGI escalation2012-05-17T10:09:05Z<p>Mkrakowi: </p>
<hr />
<div>In case of not responding NGI, COD should:<br> <br />
<br />
#Send an email to NGI managers and ask for action (email can be taken from [http://tinyurl.com/724emw5 GOC&nbsp;DB - NGIs List]) <br />
#Make a phone call to NGI&nbsp;manager (phone number can be found in GOC&nbsp;DB&nbsp;- look at given NGI's detailes - do not forgot about time zones&nbsp;;) )<br />
<br />
<br></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=WI05_Unresponsive_NGI_escalation&diff=36825WI05 Unresponsive NGI escalation2012-05-17T10:07:50Z<p>Mkrakowi: </p>
<hr />
<div>In case of not responding NGI, COD should:<br><br />
<br />
#Send an email to NGI managers and ask for action (email can be taken from [https://goc.egi.eu/portal/index.php?Page_Type=Table&query=Get_ROCs&parameters[]=NAME&start_row=0&end_row=100&Title=NGIs/ROCs GOC&nbsp;DB - NGIs List]) <br />
#Make a phone call to NGI&nbsp;manager (phone number can be found in GOC&nbsp;DB&nbsp;- look at given NGI's detailes - do not forgot about time zones ;) )<br />
<br />
<br></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=WI05_Unresponsive_NGI_escalation&diff=36824WI05 Unresponsive NGI escalation2012-05-17T10:02:02Z<p>Mkrakowi: Created page with "#mail #phone call"</p>
<hr />
<div>#mail <br />
#phone call</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Operations_and_Operations_Support&diff=36823Operations and Operations Support2012-05-17T10:00:18Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
= Introduction =<br />
<br />
'''COD team '''is a small team responsible for coordination of RODs, provided on a global layer. COD represents the whole ROD structure in terms of technical requirements for operations tools as well as on political level. <br />
<br />
The purpose of this page is to collect all materials needed by COD team to perform the Grid operations oversight activities. <br />
<br />
= People and contact =<br />
<br />
COD team is formed from Dutch and Polish team and includes COD managers (people responsible for managerial issues) and COD shifters (people performing day-to-day COD work) <br />
<br />
;'''COD managers:'''&nbsp; <br />
:Ron Trompert (Chair), Marcin Radecki, Luuk Uljee, Małgorzata Krakowian <br />
;'''COD shifters:'''&nbsp; <br />
:Małgorzata Krakowian, Ron Trompert, Luuk Uljee, Maarten van Ingen, Ernst Pijper, Alexander Verkooijen<br />
<br />
<br> [[Grid operations oversight/Photo|People behind the names]] <br />
<br />
<br> There are 2 mailing lists used for different cases: <br />
<br />
*'''manager-central-operator-on-duty''' AT mailman.egi.eu - for COD managerial issues like suggesting changes in procedures, tools. '''COD managers''' are recipients of this list. <br />
*'''central-operator-on-duty''' AT mailman.egi.eu - for reporting COD day-to-day issues like problems with tools or Nagios tests. '''COD shifters''' are recipients of this list.<br />
<br />
= COD Duties =<br />
<br />
*COD managers <br />
**'''representing RODs/COD in OTAG, OMB and Operations meetings''' - collecting requirements and improvements proposals from RODs concerning operations tools and procedures <br />
**'''suspending Resource Centres''' in case of operational issues <br />
**'''taking part in OLA task force''' <br />
**'''writing new procedures''' - in case of need COD is taking part in procedures creation process <br />
**'''preparing ROD newsletters''' - informing RODs about recent and upcoming developments related to Grid Oversight <br />
**'''preparing ROD metrics reports''' - providing an overview of operations support process in grid infrastructure. <br />
*COD shifters <br />
**'''escalation of operational problems with RODs''' <br />
**'''dealing with GGUS tickets assigned to COD''' <br />
**'''process coordination''' of: <br />
***creation and decommission of Operations Centre <br />
***setting a Nagios test to an operations test <br />
***getting explanations for low availability and reliability metrics<br />
<br />
= COD shifters work instructions =<br />
<br />
In this section are collected all work instructions containing detailed information specifying exactly what steps are to be followed to carry out an activity. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! Action <br />
! Description <br />
! Related procedures<br />
|-<br />
| '''GGUS tickets assigned to COD''' <br />
| <br />
COD shifter is obliged to check the current status of all '''GGUS tickets assigned to COD''' <br />
<br />
*see [http://tinyurl.com/2ws735h Link to all GGUS tickets assigned to COD] <br />
*If the ticket is waiting for COD action then he/she should perform the action<br />
<br />
<br> In case of a request for: <br />
<br />
*'''ROD certification''' <br />
**see [[Grid operations oversight/WI01|New ROD team certification work instructions]] <br />
*'''Creation of a new NGI''' <br />
**see [[PROC02|Creation of a new Operations Centre process coordination]] <br />
**see [https://wiki.egi.eu/wiki/Grid_operations_oversight/WI02 work instruction] <br />
**In case where COD is also the Integration Process Coordinator, COD is responsible for the whole procedure. <br />
*'''Operations Centre decommission''' <br />
**see [[PROC03|Operations Centre decommission process coordination]] <br />
**COD validates the request and removes ROD information from all-operators mailing list <br />
*'''Setting a Nagios test to an operations test''' <br />
**see [[PROC06|Procedure for setting a Nagios test to an operations test]] <br />
**COD is responsible for coordinating the whole process.<br />
<br />
If the shifter doesn't know what kind of action should be taken, he/she should contact COD managers <br />
<br />
| <br />
*[[PROC02|Creation of a new Operations Centre process coordination]] <br />
*[[PROC03|Operations Centre decommission process coordination]] <br />
*[[PROC06|Procedure for setting Nagios test an operations test]]<br />
<br />
|-<br />
| '''Availability/reliability reports''' <br />
| <br />
*Handling availability/reliability reports: [[Grid operations oversight/WI03|Availability and reliability work instruction]] <br />
**[[Underperforming sites and suspensions|AR reports metrics]]<br />
<br />
| <br />
*[[Operations:COD Escalation Procedure|COD escalation procedure]] <br />
*[[Availability and reliability monthly statistics|Availability and reliability monthly statistics procedure]]<br />
<br />
|-<br />
| '''Operational portal dashboard issues''' <br />
| <br />
*[https://operations-portal.egi.eu/dashboard/ccodView COD dashboard link]<br />
<br />
| <br />
*[[PROC01|COD escalation procedure]]<br />
<br />
|-<br />
| '''Handover''' <br />
| <br />
[https://operations-portal.egi.eu/dashboard/ccodView COD dashboard link] <br />
<br />
*At the end of the shift a handover should be submitted (send to COD) via Handover tool in the Operational Portal <br />
**Problems on the dashboard which will pass to next week: the ggus id of the ticket and when next escalation step should be taken <br />
**GGUS tickets assigned to COD: for each ticket its last status and the action taken by the shifter should be provided <br />
**Other issues: problems with tools etc.<br />
<br />
| <br><br />
|}<br />
<br />
<br> ''NOTE: all procedures should contain the following template: https://wiki.egi.eu/wiki/PDT:Procedure_Template'' <br />
<br />
== ''Work Instructions''<br> ==<br />
<br />
*[[Grid operations oversight/WI01|New ROD team certification work instructions]] <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/WI02 New Opertions Centre creation work instruction] <br />
*[[Grid operations oversight/WI03|Availability and reliability work instruction]]<br />
<br />
= Events =<br />
<br />
*[https://www.egi.eu/indico/categoryDisplay.py?categId=11 EGI indico page] with COD meeting agendas. <br />
*All open actions can be found from [[Grid operations oversight/CODOD actions|COD actions]]<br />
<br />
= Resources =<br />
<br />
*[https://documents.egi.eu/secure/ShowDocument?docid=298 Document server: ROD newsletter] <br />
*[https://documents.egi.eu/secure/ShowDocument?docid=155 Document server: Operations Support Metrics] <br />
*[https://wiki.egi.eu/wiki/Operations_Procedures Operations Procedures] <br />
*[http://www.youtube.com/user/EGIGridOversight Youtube channel]<br />
<br />
== ROD and COD Performance ==<br />
<br />
Definition of [[Grid operations oversight/ROD performance index|ROD performance index]] <!--*[[Grid operations oversight/OperationsSupportMetrics summary|Operations Support Metrics - reports summary]]--><br />
<br />
=== Oct 2011 to date ===<br />
<br />
*Please provide a link here<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
Definition of [[Grid operations oversight/OperationsSupportMetrics|Operations Support metrics]]<br />
<br />
=== May 2010-Sep 2011 ===<br />
<br />
*Operations Support [https://documents.egi.eu/document/155 metrics]<br />
<br />
=== Until April 2010 ===<br />
<br />
*EGEE-III Operations Support [https://documents.egi.eu/document/829 metrics]<br />
<br />
== Nagios tests ==<br />
<br />
*[[Operations:Operations tests|Operations tests list ]]: list of Nagios probes generating alarms for visualization in the Operations Dashboard <br />
*[http://grid-monitoring.cern.ch/myegi/sam-pi/metrics_in_profiles?vo_name=ops&profile_name=ROC_CRITICAL Availability and reliability tests list]: list of Nagios probes whose results are used for Availability and Reliability computation<br />
<br />
== OTAG topics ==<br />
<br />
=== Operational Portal: Dashboard ===<br />
<br />
*[http://bit.ly/dZ3RWN RT tickets] <br />
*[[Grid operations oversight/COD interaction with Dashboard team|COD interactions with Dashboard team (draft)]] <br />
*[[Grid operations oversight/COD OTAG topics|COD topics to be discussed on OTAG meeting]]<br />
<br />
=== GOC DB ===<br />
<br />
*[[Grid operations oversight/COD GOCDB requirements|Collection of GOC DB requirements regarding COD work (draft)]]<br />
<br />
== Pages in draft state ==<br />
<br />
*[[Grid operations oversight/COD Improvements to availability procedure|Improvements to Availability Calculation Procedure (draft)]]<br />
<br />
*[[Grid operations oversight/A/R fixing procedure|A/R fixing procedure (draft)]][[Grid operations oversight/ROD FAQ|<br>]]<br />
<br />
<br> <br />
<br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/Unknown_issue UNKNOWN issue ]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/Unknown_issue-internal UNKNOWN issue Internal ]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/ROD_performance_index ROD&nbsp;performance&nbsp;index]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/CandidateSuspendedSitesList Candidate Suspended Sites List]<br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/WI05 Work instruction - handling issues with unresponsive NGIs]<br />
<br />
[[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Underperforming_sites_and_suspensions&diff=36767Underperforming sites and suspensions2012-05-14T10:01:44Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
Information about underperforming and suspended Resource Centres is provided in the table below. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! date <br />
! GGUSID <br />
! nb. sites <br />
below 75%/70% targets <br />
<br />
! nb. sites <br />
below the target for 3 months <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
which didn't provide explanation <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
suspended by COD <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
! nb. sites <br />
suspended by CSIRT <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
|-<br />
| April 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=81843 81843] <br />
| 34 <br />
| 3 <br />
| <br> <br />
| <br> <br />
| <br><br />
|-<br />
| March 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=80900 80900] <br />
| 25 <br />
| <br />
2 <br />
<br />
*BY-BNTU, NGI_BY, not suspended because it achieves 86% in April, [https://ggus.eu/ws/ticket_info.php?ticket=81086 81086]<br> <br />
*AM-05-YSU, NGI_ARMENIA, site suspended by ROC, [https://ggus.eu/ws/ticket_info.php?ticket=81087 81087]<br><br />
<br />
| 0<br> <br />
| <br />
| <br><br />
|-<br />
| February 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79844 79844] <br />
| 35 <br />
| 3 <br />
| 0 <br />
| 2 suspended by ROC<br> <br />
*IN-DAE-VECC-02, 80037 <br />
*MY-UM-CRYSTAL, 80038<br />
<br />
| 0<br />
|-<br />
| January 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79020 79020] <br />
| 30 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 1; GARR-01-DIR, NGI_IT due to issue (EGI-20120116-01) recorded in RTIR ticket #3300)<br />
|-<br />
| December 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=78040 78040] <br />
| 28 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| November 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=77170 77170] <br />
| 26 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| October 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=76305 76305] <br />
| 45 <br />
| 3 <br />
| <br />
3<br> <br />
<br />
*ROC_Russia/RRC-KI, 76408 <br />
*NGI_IL/WEIZMANN-LCG2, 76386 <br />
*NGI_IL/TECHNION-HEP, 76384<br />
<br />
| <br />
1<br> <br />
<br />
*NGI_ARMGRID/AM-04-YERPHI,76428<br />
<br />
| 0<br />
|-<br />
| September 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74965 74965] <br />
| 25 <br />
| 6 <br />
| 0 <br />
| <br />
2<br> <br />
<br />
*ROC_Asia/Pacific/TW-NCUHEP, 3 consecutive months below the target (site suspended by ROC), #75041<br> <br />
*ROC_Asia/Pacific/IN-DAE-VECC-02, 4 consecutive months below the target (site suspended by COD), #75040<br />
<br />
| 0<br />
|-<br />
| August 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74147 74147] <br />
| 31 <br />
| 3 <br />
| 0 <br />
| 0 <br />
| 0<br />
|-<br />
| July 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=73193 73193] <br />
| 35 <br />
| 4 <br />
| 0 <br />
| <br />
2 <br />
<br />
*ROC_Asia/Pacific/TW-eScience, 3 consecutive months below the target(site suspended by ROC), ticket #73539<br> <br />
*ROC_Asia/Pacific/TW-NYMU-GRID,3 consecutive months below the target(site suspended by ROC), ticket #73540<br />
<br />
| 0<br />
|-<br />
| June 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=72259 72259] <br />
| 31 <br />
| 8 <br />
| 0 <br />
| 5 <br />
*ROC_Asia, Pacific/PH-ASTI-LIKNAYAN, 3 consecutive months below target, ticket #72435 <br />
*ROC_Asia, Pacific/TH-HAI, 3 consecutive months below target, #72436 <br />
*NGI_IBERGRID, UOGRID, 3 consecutive months below target, #72439 <br />
*ROC_IGALC, CEFET-RJ, 3 consecutive months below target, #72440 <br />
*ROC_IGALC, LA-MERIDA, 3 consecutive months below target, #72441<br />
<br />
| 0<br><br />
|-<br />
| May 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=71643 71643] <br />
| 23 <br />
| <br />
4 <br />
<br />
this month first time targed was changed to ava 70% rel 75% <br />
<br />
| 0 <br />
| 2 <br />
*UOGRID, NGI_IBERGRID, below 50%/50% for three months, 71787 <br />
*PH-ASTI-LIKNAYAN, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 71789&nbsp;<br />
<br />
| 0<br><br />
|-<br />
| April 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=70289 70289] <br />
| 39 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| March 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=69629 69629] <br />
| 30 <br />
| 0 <br />
| <br />
1 <br />
<br />
*ru-Moscow-SINP-LCG2, ROC_Russia, 69765<br><br />
<br />
| 0 <br />
| 0<br><br />
|-<br />
| February 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=68299 68299] / See also [https://gus.fzk.de/ws/ticket_info.php?ticket=68229 68229] <br />
| 28 <br />
| 0 <br />
| 1 <br />
*RU-SPbSU, ROC_Russia<br />
<br />
| <br> <br />
| 0<br><br />
|-<br />
| Jan 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=67008 67008] <br />
| 27 <br />
| 2 <br />
| 1 <br />
*ru-IMPB-LCG2,ROC_Russia, 67038<br />
<br />
| 2 <br />
*MY-UM-PANG5, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 67010 <br />
*ru-IMPB-LCG2,ROC_Russia, sites didn't provided explanation,67038<br />
<br />
| 0 <br><br />
|-<br />
| Dec 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=65971 65971] <br />
| 30 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0 <br><br />
|-<br />
| Nov 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=64892 64892] <br />
| 40 <br />
| 1 <br />
| 0 <br />
| 1 <br />
*ID-ITB, ROC_Asia/Pacific,below 50%/50% for three months (site suspended by ROC),64951<br />
<br />
| 0<br><br />
|-<br />
| Oct 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=63658 63658] <br />
| 37 <br />
| 4 <br />
| 1 <br />
*AM-04-YERPHI, NGI_ARMGRID, 63854<br />
<br />
| 2 <br />
*AM-01-IIAP-NAS-RA, NGI_ARMGRID, below 50%/50% for three months, 63837 <br />
*AM-04-YERPHI, NGI_ARMGRID, no explanation given, 63854<br />
<br />
| 0<br><br />
|-<br />
| Sep 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=62853 62853] <br />
| 39 <br />
| 2 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Aug 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61797 61797] <br />
| 43 <br />
| 3 <br />
| 10 <br />
*JP-HIROSHIMA-WLCG, ROC AP, 62323 <br />
*AU-PPS, ROC AP,62316 <br />
*MY-UTM-GRID, ROC AP, 62312 <br />
*TH-NECTEC-LSR, ROC AP, 62304 <br />
*MY-UM-CRYSTAL, ROC AP, 62300 <br />
*ID-ITB, ROC AP, 62296 <br />
*GRISU-COMETA-INFN-LNS, ROC Italy, 62314 <br />
*UNIGE-DPNC, NGI_NDGF, 62308 <br />
*ru-IMPB-LCG2, ROC_Russia, 62305 <br />
*IL-TAU-HEP,ROC_SE, 62306<br />
<br />
| 1 <br />
*TW-NCUHEP, ROC AP, below 50%/50% for three months, 62340<br />
<br />
| 0<br><br />
|-<br />
| Jul 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61115 61115] <br />
| 47 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Jun 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=60216 60216] <br />
| 59 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| May 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=59736 59736] <br />
| 38 <br />
| 3 <br />
| 1 <br />
*ru-Chernogolovka-IPCP-LCG2, ROC RU, 59819<br />
<br />
| 0 <br />
| 0<br><br />
|}<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]] [[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR8&diff=36744EGI-InSPIRE:Poland-QR82012-05-11T09:35:07Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 8<br> <br />
| NGI_PL<br> <br />
| CYFRONET<br> <br />
| Małgorzata Krakowian<br><br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 26.03-30.03.2012<br> <br />
| Munich, Germany<br> <br />
| Community forum<br> <br />
| 9<br> <br />
| http://cf2012.egi.eu/<br><br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance for vo.plgrid.pl: Unicore tests integrated; UNICORE&nbsp;probes generate alarms in Operations Portal for vo.plgrid.pl<br> <br />
#'''Unicore''' <br />
##Staged rollout testing: UNICORE/X 6.4.2 https://rt.egi.eu/rt/Ticket/Display.html?id=3485<br> <br />
##Monitoring:&nbsp;testing nad verification of SAM Update 17 <br />
##Accounting:&nbsp;taking part in phone conferences about UNICORE&nbsp;and EGI accounting integration <br />
##<span lang="en" class="short_text" id="result_box"><span class="hps alt-edited">Preparation of an analysis about SSM </span></span>(<span class="st">''Secure Stomp Messenger''</span>) <span lang="en" class="short_text" id="result_box"><span class="hps alt-edited">and UNICORE integration</span></span> <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; February ava 92% rel 93%, March ava 94% rel 95% , April ava 85% rel 86%&nbsp;;All sites above the targets. <br />
##BDII metrics: February 100%, March 100%, April 100%<br> <br />
#'''NGI_PL security team ''' <br />
##Regular operational actions within EGI CSIRT IRTF<br> <br />
##Taking part in weekly and monthly meetings of EGI CSIRT<br> <br />
##Participation in EGI CSIRT F2F meeting in Bologna (1 attendant)<br> <br />
##Work within Risk Assessment Metagroup, preparing D4.4 "Security Risk<br> <br />
##Assessment of the EGI Infrastructure" - 1 representative<br> <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Registration of Unicore and QCG core services in NGI_PL_SERVICES site <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##PSNC <br />
###New services: UNICORE-UI<br> <br />
###New hardware: storage - 90 TB <br> <br />
##WCSS <br />
###New services: WMS (VO: gaussian, vo.plgrid.pl ), UNICORE Registry 6.4.0 and UVOS 1.5.0. <br />
##WARSAW-EGEE <br />
###Actualization of <br />
####UNICORE/X (unicore-unicorex6) and TSI (unciore-tsi6) v. 6.4.2 <br />
####UNICORE FTP v. 1.2.0; <br />
####UNICORE Workflow Service v. 6.4.0; <br />
####UNICORE Service Orchestrator v. 6.4.0; <br />
####UNICORE Registry v. 6.4.0; <br />
####qcg-Computing v. 2.6.1.<br> <br />
###New hardware: 16x servers with 4 x AMD 6272 (16 core) and 512GB RAM<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF <br />
#'''Community Forum 2012'''<br> <br />
##NGI_PL took part in [https://www.egi.eu/indico/contributionDisplay.py?sessionId=63&contribId=41&confId=679 Service Management maturity assesment ]activity prepared by gSLM project. Results were presented during the Community Forum.<br><br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. NGI_PL&nbsp;is working to apply ITILv3 recomendation to provide best value (</span></span><span class="st">utility and warranty</span><span lang="en" id="result_box" class="short_text"><span class="hps">) to the users.<br />
</span></span> <br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR8&diff=36743EGI-InSPIRE:Poland-QR82012-05-11T08:59:22Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 8<br> <br />
| NGI_PL<br> <br />
| CYFRONET<br> <br />
| Małgorzata Krakowian<br><br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 26.03-30.03.2012<br> <br />
| Munich, Germany<br> <br />
| Community forum<br> <br />
| 9<br> <br />
| http://cf2012.egi.eu/<br><br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance for vo.plgrid.pl: Unicore tests integrated; UNICORE&nbsp;probes generate alarms in Operations Portal for vo.plgrid.pl<br> <br />
#'''Unicore''' <br />
##Staged rollout testing: UNICOER/X 6.4.2 https://rt.egi.eu/rt/Ticket/Display.html?id=3485<br> <br />
##Monitoring:&nbsp;testing nad verification of SAM Update 17 <br />
##Accounting:&nbsp;taking part in phone conferences about UNICORE&nbsp;and EGI accounting integration <br />
##<span lang="en" id="result_box" class="short_text"><span class="hps alt-edited">Preparation of an analysis about SSM </span></span>(<span class="st">''Secure Stomp Messenger''</span>) <span lang="en" id="result_box" class="short_text"><span class="hps alt-edited">and UNICORE integration</span></span> <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; February ava 92% rel 93%, March ava 94% rel 95% , April ava 85% rel 86%&nbsp;;All sites above the targets. <br />
##BDII metrics: February 100%, March 100%, April 100%<br> <br />
#'''NGI_PL security team ''' <br />
##Regular operational actions within EGI CSIRT IRTF<br> <br />
##Taking part in weekly and monthly meetings of EGI CSIRT<br> <br />
##Participation in EGI CSIRT F2F meeting in Bologna (1 attendant)<br> <br />
##Work within Risk Assessment Metagroup, preparing D4.4 "Security Risk<br> <br />
##Assessment of the EGI Infrastructure" - 1 representative<br> <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Registration of Unicore and QCG core services in NGI_PL_SERVICES site <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##PSNC <br />
###New services: UNICORE-UI<br> <br />
###New hardware: storage - 90 TB <br> <br />
##WCSS <br />
###New services: WMS (VO: gaussian, vo.plgrid.pl ), UNCORE Registry 6.4.0 and UVOS 1.5.0. <br />
##WARSAW_EGEE <br />
###Actualization of <br />
####UNICORE/X (unicore-unicorex6) and TSI (unciore-tsi6) v. 6.4.2 <br />
####UNICORE FTP v. 1.2.0; <br />
####UNICORE Workflow Service v. 6.4.0; <br />
####UNICORE Service Orchestrator v. 6.4.0; <br />
####UNICORE Registry v. 6.4.0; <br />
####qcg-Computing v. 2.6.1.<br> <br />
###New hardware: 16x servers with 4 x AMD 6272 (16 core) and 512GB RAM<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF <br />
#'''Community Forum 2012'''<br> <br />
##NGI_PL took part in [https://www.egi.eu/indico/contributionDisplay.py?sessionId=63&contribId=41&confId=679 Service Management maturity assesment ]activity prepared by gSLM project. Results were presented during the Community Forum.<br><br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" class="short_text" id="result_box"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" class="short_text" id="result_box"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. NGI_PL&nbsp;is working to apply ITILv3 recomendation to provide best value (</span></span><span class="st">utility and warranty</span><span lang="en" class="short_text" id="result_box"><span class="hps">) to the users.<br />
</span></span> <br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR8&diff=36742EGI-InSPIRE:Poland-QR82012-05-11T08:57:12Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 8<br> <br />
| NGI_PL<br> <br />
| CYFRONET<br> <br />
| Małgorzata Krakowian<br><br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 26.03-30.03.2012<br> <br />
| Munich, Germany<br> <br />
| Community forum<br> <br />
| 9<br> <br />
| http://cf2012.egi.eu/<br><br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance for vo.plgrid.pl: Unicore tests integrated; UNICORE&nbsp;probes generate alarms in Operations Portal for vo.plgrid.pl<br> <br />
#'''Unicore''' <br />
##Staged rollout testing: UNICOER/X 6.4.2 https://rt.egi.eu/rt/Ticket/Display.html?id=3485<br> <br />
##Monitoring:&nbsp;testing nad verification of SAM Update 17 <br />
##Accounting:&nbsp;taking part in phone conferences about UNICORE&nbsp;and EGI accounting integration <br />
##<span lang="en" class="short_text" id="result_box"><span class="hps alt-edited">Preparation of an analysis about SSM </span></span>(<span class="st">''Secure Stomp Messenger''</span>) <span lang="en" class="short_text" id="result_box"><span class="hps alt-edited">and UNICORE integration</span></span> <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; February ava 92% rel 93%, March ava 94% rel 95% , April ava 85% rel 86%&nbsp;;All sites above the targets. <br />
##BDII metrics: February 100%, March 100%, April 100%<br> <br />
#'''NGI_PL security team ''' <br />
##Regular operational actions within EGI CSIRT IRTF<br> <br />
##Taking part in weekly and monthly meetings of EGI CSIRT<br> <br />
##Participation in EGI CSIRT F2F meeting in Bologna (1 attendant)<br> <br />
##Work within Risk Assessment Metagroup, preparing D4.4 "Security Risk<br> <br />
##Assessment of the EGI Infrastructure" - 1 representative<br> <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Registration of Unicore and QCG core services in NGI_PL_SERVICES site <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##PSNC <br />
###New services: UNICORE-UI<br> <br />
###New hardware: storage - 90 TB <br> <br />
##WCSS <br />
###New services: WMS (VO: gaussian, vo.plgrid.pl ), UNCORE Registry 6.4.0 and UVOS 1.5.0. <br />
##WARSAW_EGEE <br />
###Actualization of <br />
####UNICORE/X (unicore-unicorex6) and TSI (unciore-tsi6) v. 6.4.2 <br />
####UNICORE FTP v. 1.2.0; <br />
####UNICORE Workflow Service v. 6.4.0; <br />
####UNICORE Service Orchestrator v. 6.4.0; <br />
####UNICORE Registry v. 6.4.0; <br />
####qcg-Computing v. 2.6.1.<br> <br />
###New hardware: 16x servers with 4 x AMD 6272 (16 core) and 512GB RAM<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF <br />
#'''Community Forum 2012'''<br> <br />
##NGI_PL took part in [https://www.egi.eu/indico/contributionDisplay.py?sessionId=63&contribId=41&confId=679 Service Management maturity assesment ]activity. Results were presented by gSLM project during the Community Forum.<br><br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. NGI_PL&nbsp;is working to apply ITILv3 recomendation to provide best value (</span></span><span class="st">utility and warranty</span><span lang="en" id="result_box" class="short_text"><span class="hps">) to the users.<br />
</span></span> <br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR8&diff=36739EGI-InSPIRE:Poland-QR82012-05-11T08:55:11Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 8<br> <br />
| NGI_PL<br> <br />
| CYFRONET<br> <br />
| Małgorzata Krakowian<br><br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 26.03-30.03.2012<br> <br />
| Munich, Germany<br> <br />
| Community forum<br> <br />
| 9<br> <br />
| http://cf2012.egi.eu/<br><br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance for vo.plgrid.pl: Unicore tests integrated; probes generates alarms in Operations Portal <br> <br />
#'''Unicore''' <br />
##Staged rollout testing: UNICOER/X 6.4.2 https://rt.egi.eu/rt/Ticket/Display.html?id=3485<br> <br />
##Monitoring:&nbsp;testing nad verification of SAM Update 17 <br />
##Accounting:&nbsp;taking part in phone conferences about UNICORE&nbsp;and EGI accounting integration <br />
##<span lang="en" id="result_box" class="short_text"><span class="hps alt-edited">Preparation of an analysis about SSM </span></span>(<span class="st">''Secure Stomp Messenger''</span>) <span lang="en" id="result_box" class="short_text"><span class="hps alt-edited">and UNICORE integration</span></span> <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; February ava 92% rel 93%, March ava 94% rel 95% , April ava 85% rel 86%&nbsp;;All sites above the targets. <br />
##BDII metrics: February 100%, March 100%, April 100%<br> <br />
#'''NGI_PL security team ''' <br />
##Regular operational actions within EGI CSIRT IRTF<br> <br />
##Taking part in weekly and monthly meetings of EGI CSIRT<br> <br />
##Participation in EGI CSIRT F2F meeting in Bologna (1 attendant)<br> <br />
##Work within Risk Assessment Metagroup, preparing D4.4 "Security Risk<br> <br />
##Assessment of the EGI Infrastructure" - 1 representative<br> <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Registration of Unicore and QCG core services in NGI_PL_SERVICES site <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##PSNC <br />
###New services: UNICORE-UI<br> <br />
###New hardware: storage - 90 TB <br> <br />
##WCSS <br />
###New services: WMS (VO: gaussian, vo.plgrid.pl ), UNCORE Registry 6.4.0 and UVOS 1.5.0. <br />
##WARSAW_EGEE <br />
###Actualization of <br />
####UNICORE/X (unicore-unicorex6) and TSI (unciore-tsi6) v. 6.4.2 <br />
####UNICORE FTP v. 1.2.0; <br />
####UNICORE Workflow Service v. 6.4.0; <br />
####UNICORE Service Orchestrator v. 6.4.0; <br />
####UNICORE Registry v. 6.4.0; <br />
####qcg-Computing v. 2.6.1.<br> <br />
###New hardware: 16x servers with 4 x AMD 6272 (16 core) and 512GB RAM<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF <br />
#'''Community Forum 2012'''<br> <br />
##NGI_PL took part in [https://www.egi.eu/indico/contributionDisplay.py?sessionId=63&contribId=41&confId=679 Service Management maturity assesment ]activity. Results were presented by gSLM project during the Community Forum.<br><br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. NGI_PL&nbsp;is working to apply ITILv3 recomendation to provide best value (</span></span><span class="st">utility and warranty</span><span lang="en" id="result_box" class="short_text"><span class="hps">) to the users.<br />
</span></span> <br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR8&diff=36738EGI-InSPIRE:Poland-QR82012-05-11T08:54:53Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 8<br> <br />
| NGI_PL<br> <br />
| CYFRONET<br> <br />
| Małgorzata Krakowian<br><br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 26.03-30.03.2012<br> <br />
| Munich, Germany<br> <br />
| Community forum<br> <br />
| 9<br> <br />
| http://cf2012.egi.eu/<br><br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance for vo.plgrid.pl: Unicore tests integrated; probes generates alarms in Operations Portal &lt;span style="font-weight: bold;" /&gt;<br> <br />
#'''Unicore*''' <br />
##Staged rollout testing: UNICOER/X 6.4.2 https://rt.egi.eu/rt/Ticket/Display.html?id=3485<br> <br />
##Monitoring:&nbsp;testing nad verification of SAM Update 17 <br />
##Accounting:&nbsp;taking part in phone conferences about UNICORE&nbsp;and EGI accounting integration<br />
##<span lang="en" class="short_text" id="result_box"><span class="hps alt-edited">Preparation of an analysis about SSM </span></span>(<span class="st">''Secure Stomp Messenger''</span>) <span lang="en" class="short_text" id="result_box"><span class="hps alt-edited">and UNICORE integration</span></span> <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; February ava 92% rel 93%, March ava 94% rel 95% , April ava 85% rel 86%&nbsp;;All sites above the targets. <br />
##BDII metrics: February 100%, March 100%, April 100%<br> <br />
#'''NGI_PL security team ''' <br />
##Regular operational actions within EGI CSIRT IRTF<br> <br />
##Taking part in weekly and monthly meetings of EGI CSIRT<br> <br />
##Participation in EGI CSIRT F2F meeting in Bologna (1 attendant)<br> <br />
##Work within Risk Assessment Metagroup, preparing D4.4 "Security Risk<br> <br />
##Assessment of the EGI Infrastructure" - 1 representative<br> <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Registration of Unicore and QCG core services in NGI_PL_SERVICES site <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##PSNC <br />
###New services: UNICORE-UI<br> <br />
###New hardware: storage - 90 TB <br> <br />
##WCSS <br />
###New services: WMS (VO: gaussian, vo.plgrid.pl ), UNCORE Registry 6.4.0 and UVOS 1.5.0. <br />
##WARSAW_EGEE <br />
###Actualization of <br />
####UNICORE/X (unicore-unicorex6) and TSI (unciore-tsi6) v. 6.4.2<br />
####UNICORE FTP v. 1.2.0;<br />
####UNICORE Workflow Service v. 6.4.0;<br />
####UNICORE Service Orchestrator v. 6.4.0;<br />
####UNICORE Registry v. 6.4.0;<br />
####qcg-Computing v. 2.6.1.<br> <br />
###New hardware: 16x servers with 4 x AMD 6272 (16 core) and 512GB RAM<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF <br />
#'''Community Forum 2012'''<br> <br />
##NGI_PL took part in [https://www.egi.eu/indico/contributionDisplay.py?sessionId=63&contribId=41&confId=679 Service Management maturity assesment ]activity. Results were presented by gSLM project during the Community Forum.<br><br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. NGI_PL&nbsp;is working to apply ITILv3 recomendation to provide best value (</span></span><span class="st">utility and warranty</span><span lang="en" id="result_box" class="short_text"><span class="hps">) to the users.<br />
</span></span> <br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR8&diff=36737EGI-InSPIRE:Poland-QR82012-05-11T08:42:10Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 8<br> <br />
| NGI_PL<br> <br />
| CYFRONET<br> <br />
| Małgorzata Krakowian<br><br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br> <br />
| <br><br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 26.03-30.03.2012<br> <br />
| Munich, Germany<br> <br />
| Community forum<br> <br />
| 9<br> <br />
| http://cf2012.egi.eu/<br><br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance for vo.plgrid.pl: Unicore tests integrated; probes generates alarms in Operations Portal &lt;span style="font-weight: bold;" /&gt;<br> <br />
#'''Unicore*''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##<br> <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; February ava 92% rel 93%, March ava 94% rel 95% , April ava 85% rel 86%&nbsp;;All sites above the targets. <br />
##BDII metrics: February 100%, March 100%, April 100%<br> <br />
#'''NGI_PL security team ''' <br />
##Regular operational actions within EGI CSIRT IRTF<br> <br />
##Taking part in weekly and monthly meetings of EGI CSIRT<br> <br />
##Participation in EGI CSIRT F2F meeting in Bologna (1 attendant)<br> <br />
##Work within Risk Assessment Metagroup, preparing D4.4 "Security Risk<br> <br />
##Assessment of the EGI Infrastructure" - 1 representative<br> <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Registration of Unicore and QCG core services in NGI_PL_SERVICES site <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: <br />
###NGI_PL_SERVICES - contains NGI_PL core services<br> <br />
###ICM - contains QCG&nbsp;and UNICORE services <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF <br />
#'''Community Forum 2012'''<br> <br />
##NGI_PL took part in [https://www.egi.eu/indico/contributionDisplay.py?sessionId=63&contribId=41&confId=679 Service Management maturity assesment ]activity. Results were presented by gSLM project during the Community Forum.<br><br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. NGI_PL&nbsp;is working to apply ITILv3 recomendation to provide best value (</span></span><span class="st">utility and warranty</span><span lang="en" id="result_box" class="short_text"><span class="hps">) to the users.<br />
</span></span> <br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Underperforming_sites_and_suspensions&diff=35849Underperforming sites and suspensions2012-04-25T08:00:03Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
Information about underperforming and suspended Resource Centres is provided in the table below. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! date <br />
! GGUSID <br />
! nb. sites <br />
below 75%/70% targets <br />
<br />
! nb. sites <br />
below the target for 3 months <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
which didn't provide explanation <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
suspended by COD <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
! nb. sites <br />
suspended by CSIRT <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
|-<br />
| March 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=80900 80900] <br />
| 25 <br />
| <br />
2 <br />
<br />
*BY-BNTU, NGI_BY, not suspended because it achieves 86% in April, [https://ggus.eu/ws/ticket_info.php?ticket=81086 81086]<br> <br />
*AM-05-YSU, NGI_ARMENIA, site suspended by ROC, [https://ggus.eu/ws/ticket_info.php?ticket=81087 81087]<br><br />
<br />
| 0<br> <br />
| 1<br> <br />
*AM-05-YSU, NGI_ARMENIA, site suspended by ROC, [https://ggus.eu/ws/ticket_info.php?ticket=81087 81087]<br />
<br />
| <br><br />
|-<br />
| February 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79844 79844] <br />
| 35 <br />
| 3 <br />
| 0 <br />
| 2 suspended by ROC<br> <br />
*IN-DAE-VECC-02, 80037 <br />
*MY-UM-CRYSTAL, 80038<br />
<br />
| 0<br />
|-<br />
| January 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79020 79020] <br />
| 30 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 1; GARR-01-DIR, NGI_IT due to issue (EGI-20120116-01) recorded in RTIR ticket #3300)<br />
|-<br />
| December 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=78040 78040] <br />
| 28 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| November 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=77170 77170] <br />
| 26 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| October 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=76305 76305] <br />
| 45 <br />
| 3 <br />
| <br />
3<br> <br />
<br />
*ROC_Russia/RRC-KI, 76408 <br />
*NGI_IL/WEIZMANN-LCG2, 76386 <br />
*NGI_IL/TECHNION-HEP, 76384<br />
<br />
| <br />
1<br> <br />
<br />
*NGI_ARMGRID/AM-04-YERPHI,76428<br />
<br />
| 0<br />
|-<br />
| September 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74965 74965] <br />
| 25 <br />
| 6 <br />
| 0 <br />
| <br />
2<br> <br />
<br />
*ROC_Asia/Pacific/TW-NCUHEP, 3 consecutive months below the target (site suspended by ROC), #75041<br> <br />
*ROC_Asia/Pacific/IN-DAE-VECC-02, 4 consecutive months below the target (site suspended by COD), #75040<br />
<br />
| 0<br />
|-<br />
| August 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74147 74147] <br />
| 31 <br />
| 3 <br />
| 0 <br />
| 0 <br />
| 0<br />
|-<br />
| July 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=73193 73193] <br />
| 35 <br />
| 4 <br />
| 0 <br />
| <br />
2 <br />
<br />
*ROC_Asia/Pacific/TW-eScience, 3 consecutive months below the target(site suspended by ROC), ticket #73539<br> <br />
*ROC_Asia/Pacific/TW-NYMU-GRID,3 consecutive months below the target(site suspended by ROC), ticket #73540<br />
<br />
| 0<br />
|-<br />
| June 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=72259 72259] <br />
| 31 <br />
| 8 <br />
| 0 <br />
| 5 <br />
*ROC_Asia, Pacific/PH-ASTI-LIKNAYAN, 3 consecutive months below target, ticket #72435 <br />
*ROC_Asia, Pacific/TH-HAI, 3 consecutive months below target, #72436 <br />
*NGI_IBERGRID, UOGRID, 3 consecutive months below target, #72439 <br />
*ROC_IGALC, CEFET-RJ, 3 consecutive months below target, #72440 <br />
*ROC_IGALC, LA-MERIDA, 3 consecutive months below target, #72441<br />
<br />
| 0<br><br />
|-<br />
| May 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=71643 71643] <br />
| 23 <br />
| <br />
4 <br />
<br />
this month first time targed was changed to ava 70% rel 75% <br />
<br />
| 0 <br />
| 2 <br />
*UOGRID, NGI_IBERGRID, below 50%/50% for three months, 71787 <br />
*PH-ASTI-LIKNAYAN, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 71789&nbsp;<br />
<br />
| 0<br><br />
|-<br />
| April 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=70289 70289] <br />
| 39 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| March 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=69629 69629] <br />
| 30 <br />
| 0 <br />
| <br />
1 <br />
<br />
*ru-Moscow-SINP-LCG2, ROC_Russia, 69765<br><br />
<br />
| 0 <br />
| 0<br><br />
|-<br />
| February 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=68299 68299] / See also [https://gus.fzk.de/ws/ticket_info.php?ticket=68229 68229] <br />
| 28 <br />
| 0 <br />
| 1 <br />
*RU-SPbSU, ROC_Russia<br />
<br />
| <br> <br />
| 0<br><br />
|-<br />
| Jan 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=67008 67008] <br />
| 27 <br />
| 2 <br />
| 1 <br />
*ru-IMPB-LCG2,ROC_Russia, 67038<br />
<br />
| 2 <br />
*MY-UM-PANG5, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 67010 <br />
*ru-IMPB-LCG2,ROC_Russia, sites didn't provided explanation,67038<br />
<br />
| 0 <br><br />
|-<br />
| Dec 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=65971 65971] <br />
| 30 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0 <br><br />
|-<br />
| Nov 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=64892 64892] <br />
| 40 <br />
| 1 <br />
| 0 <br />
| 1 <br />
*ID-ITB, ROC_Asia/Pacific,below 50%/50% for three months (site suspended by ROC),64951<br />
<br />
| 0<br><br />
|-<br />
| Oct 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=63658 63658] <br />
| 37 <br />
| 4 <br />
| 1 <br />
*AM-04-YERPHI, NGI_ARMGRID, 63854<br />
<br />
| 2 <br />
*AM-01-IIAP-NAS-RA, NGI_ARMGRID, below 50%/50% for three months, 63837 <br />
*AM-04-YERPHI, NGI_ARMGRID, no explanation given, 63854<br />
<br />
| 0<br><br />
|-<br />
| Sep 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=62853 62853] <br />
| 39 <br />
| 2 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Aug 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61797 61797] <br />
| 43 <br />
| 3 <br />
| 10 <br />
*JP-HIROSHIMA-WLCG, ROC AP, 62323 <br />
*AU-PPS, ROC AP,62316 <br />
*MY-UTM-GRID, ROC AP, 62312 <br />
*TH-NECTEC-LSR, ROC AP, 62304 <br />
*MY-UM-CRYSTAL, ROC AP, 62300 <br />
*ID-ITB, ROC AP, 62296 <br />
*GRISU-COMETA-INFN-LNS, ROC Italy, 62314 <br />
*UNIGE-DPNC, NGI_NDGF, 62308 <br />
*ru-IMPB-LCG2, ROC_Russia, 62305 <br />
*IL-TAU-HEP,ROC_SE, 62306<br />
<br />
| 1 <br />
*TW-NCUHEP, ROC AP, below 50%/50% for three months, 62340<br />
<br />
| 0<br><br />
|-<br />
| Jul 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61115 61115] <br />
| 47 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Jun 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=60216 60216] <br />
| 59 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| May 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=59736 59736] <br />
| 38 <br />
| 3 <br />
| 1 <br />
*ru-Chernogolovka-IPCP-LCG2, ROC RU, 59819<br />
<br />
| 0 <br />
| 0<br><br />
|}<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]] [[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Underperforming_sites_and_suspensions&diff=35520Underperforming sites and suspensions2012-04-18T10:02:37Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
Information about underperforming and suspended Resource Centres is provided in the table below. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! date <br />
! GGUSID <br />
! nb. sites <br />
below 75%/70% targets <br />
<br />
! nb. sites <br />
below the target for 3 months <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
which didn't provide explanation <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
suspended by COD <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
! nb. sites <br />
suspended by CSIRT <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
|-<br />
| March 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=80900 80900] <br />
| 25 <br />
| <br />
2 <br />
<br />
*BY-BNTU, NGI_BY, ,<br> <br />
*AM-05-YSU, NGI_ARMENIA, site suspended by ROC, [https://ggus.eu/ws/ticket_info.php?ticket=81087 81087]<br><br />
<br />
| <br> <br />
| 1<br><br />
*AM-05-YSU, NGI_ARMENIA, site suspended by ROC, [https://ggus.eu/ws/ticket_info.php?ticket=81087 81087]<br />
<br />
| <br><br />
|-<br />
| February 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79844 79844] <br />
| 35 <br />
| 3 <br />
| 0 <br />
| 2 suspended by ROC<br> <br />
*IN-DAE-VECC-02, 80037 <br />
*MY-UM-CRYSTAL, 80038<br />
<br />
| 0<br />
|-<br />
| January 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79020 79020] <br />
| 30 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 1; GARR-01-DIR, NGI_IT due to issue (EGI-20120116-01) recorded in RTIR ticket #3300)<br />
|-<br />
| December 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=78040 78040] <br />
| 28 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| November 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=77170 77170] <br />
| 26 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| October 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=76305 76305] <br />
| 45 <br />
| 3 <br />
| <br />
3<br> <br />
<br />
*ROC_Russia/RRC-KI, 76408 <br />
*NGI_IL/WEIZMANN-LCG2, 76386 <br />
*NGI_IL/TECHNION-HEP, 76384<br />
<br />
| <br />
1<br> <br />
<br />
*NGI_ARMGRID/AM-04-YERPHI,76428<br />
<br />
| 0<br />
|-<br />
| September 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74965 74965] <br />
| 25 <br />
| 6 <br />
| 0 <br />
| <br />
2<br> <br />
<br />
*ROC_Asia/Pacific/TW-NCUHEP, 3 consecutive months below the target (site suspended by ROC), #75041<br> <br />
*ROC_Asia/Pacific/IN-DAE-VECC-02, 4 consecutive months below the target (site suspended by COD), #75040<br />
<br />
| 0<br />
|-<br />
| August 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74147 74147] <br />
| 31 <br />
| 3 <br />
| 0 <br />
| 0 <br />
| 0<br />
|-<br />
| July 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=73193 73193] <br />
| 35 <br />
| 4 <br />
| 0 <br />
| <br />
2 <br />
<br />
*ROC_Asia/Pacific/TW-eScience, 3 consecutive months below the target(site suspended by ROC), ticket #73539<br> <br />
*ROC_Asia/Pacific/TW-NYMU-GRID,3 consecutive months below the target(site suspended by ROC), ticket #73540<br />
<br />
| 0<br />
|-<br />
| June 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=72259 72259] <br />
| 31 <br />
| 8 <br />
| 0 <br />
| 5 <br />
*ROC_Asia, Pacific/PH-ASTI-LIKNAYAN, 3 consecutive months below target, ticket #72435 <br />
*ROC_Asia, Pacific/TH-HAI, 3 consecutive months below target, #72436 <br />
*NGI_IBERGRID, UOGRID, 3 consecutive months below target, #72439 <br />
*ROC_IGALC, CEFET-RJ, 3 consecutive months below target, #72440 <br />
*ROC_IGALC, LA-MERIDA, 3 consecutive months below target, #72441<br />
<br />
| 0<br><br />
|-<br />
| May 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=71643 71643] <br />
| 23 <br />
| <br />
4 <br />
<br />
this month first time targed was changed to ava 70% rel 75% <br />
<br />
| 0 <br />
| 2 <br />
*UOGRID, NGI_IBERGRID, below 50%/50% for three months, 71787 <br />
*PH-ASTI-LIKNAYAN, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 71789&nbsp;<br />
<br />
| 0<br><br />
|-<br />
| April 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=70289 70289] <br />
| 39 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| March 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=69629 69629] <br />
| 30 <br />
| 0 <br />
| <br />
1 <br />
<br />
*ru-Moscow-SINP-LCG2, ROC_Russia, 69765<br><br />
<br />
| 0 <br />
| 0<br><br />
|-<br />
| February 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=68299 68299] / See also [https://gus.fzk.de/ws/ticket_info.php?ticket=68229 68229] <br />
| 28 <br />
| 0 <br />
| 1 <br />
*RU-SPbSU, ROC_Russia<br />
<br />
| <br> <br />
| 0<br><br />
|-<br />
| Jan 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=67008 67008] <br />
| 27 <br />
| 2 <br />
| 1 <br />
*ru-IMPB-LCG2,ROC_Russia, 67038<br />
<br />
| 2 <br />
*MY-UM-PANG5, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 67010 <br />
*ru-IMPB-LCG2,ROC_Russia, sites didn't provided explanation,67038<br />
<br />
| 0 <br><br />
|-<br />
| Dec 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=65971 65971] <br />
| 30 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0 <br><br />
|-<br />
| Nov 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=64892 64892] <br />
| 40 <br />
| 1 <br />
| 0 <br />
| 1 <br />
*ID-ITB, ROC_Asia/Pacific,below 50%/50% for three months (site suspended by ROC),64951<br />
<br />
| 0<br><br />
|-<br />
| Oct 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=63658 63658] <br />
| 37 <br />
| 4 <br />
| 1 <br />
*AM-04-YERPHI, NGI_ARMGRID, 63854<br />
<br />
| 2 <br />
*AM-01-IIAP-NAS-RA, NGI_ARMGRID, below 50%/50% for three months, 63837 <br />
*AM-04-YERPHI, NGI_ARMGRID, no explanation given, 63854<br />
<br />
| 0<br><br />
|-<br />
| Sep 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=62853 62853] <br />
| 39 <br />
| 2 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Aug 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61797 61797] <br />
| 43 <br />
| 3 <br />
| 10 <br />
*JP-HIROSHIMA-WLCG, ROC AP, 62323 <br />
*AU-PPS, ROC AP,62316 <br />
*MY-UTM-GRID, ROC AP, 62312 <br />
*TH-NECTEC-LSR, ROC AP, 62304 <br />
*MY-UM-CRYSTAL, ROC AP, 62300 <br />
*ID-ITB, ROC AP, 62296 <br />
*GRISU-COMETA-INFN-LNS, ROC Italy, 62314 <br />
*UNIGE-DPNC, NGI_NDGF, 62308 <br />
*ru-IMPB-LCG2, ROC_Russia, 62305 <br />
*IL-TAU-HEP,ROC_SE, 62306<br />
<br />
| 1 <br />
*TW-NCUHEP, ROC AP, below 50%/50% for three months, 62340<br />
<br />
| 0<br><br />
|-<br />
| Jul 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61115 61115] <br />
| 47 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Jun 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=60216 60216] <br />
| 59 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| May 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=59736 59736] <br />
| 38 <br />
| 3 <br />
| 1 <br />
*ru-Chernogolovka-IPCP-LCG2, ROC RU, 59819<br />
<br />
| 0 <br />
| 0<br><br />
|}<br />
<br />
<br> <br />
<br />
[[Category:Service_Level_Management]] [[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Underperforming_sites_and_suspensions&diff=35303Underperforming sites and suspensions2012-04-05T08:45:07Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
Information about underperforming and suspended Resource Centres is provided in the table below. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! date <br />
! GGUSID <br />
! nb. sites <br />
below 75%/70% targets <br />
<br />
! nb. sites <br />
below the target for 3 months <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
which didn't provide explanation <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
suspended by COD <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
! nb. sites <br />
suspended by CSIRT <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
|-<br />
| March 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=80900 80900] <br />
| 25 <br />
| <br />
2 <br />
<br />
*BY-BNTU, NGI_BY, ,<br><br />
*AM-05-YSU, NGI_ARMENIA,&nbsp; , <br><br />
<br />
| <br><br />
| <br><br />
| <br><br />
|-<br />
| February 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79844 79844] <br />
| 35 <br />
| 3 <br />
| 0 <br />
| 2 suspended by ROC<br> <br />
*IN-DAE-VECC-02, 80037 <br />
*MY-UM-CRYSTAL, 80038<br />
<br />
| 0<br />
|-<br />
| January 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79020 79020] <br />
| 30 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 1; GARR-01-DIR, NGI_IT due to issue (EGI-20120116-01) recorded in RTIR ticket #3300)<br />
|-<br />
| December 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=78040 78040] <br />
| 28 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| November 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=77170 77170] <br />
| 26 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| October 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=76305 76305] <br />
| 45 <br />
| 3 <br />
| <br />
3<br> <br />
<br />
*ROC_Russia/RRC-KI, 76408 <br />
*NGI_IL/WEIZMANN-LCG2, 76386 <br />
*NGI_IL/TECHNION-HEP, 76384<br />
<br />
| <br />
1<br> <br />
<br />
*NGI_ARMGRID/AM-04-YERPHI,76428<br />
<br />
| 0<br />
|-<br />
| September 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74965 74965] <br />
| 25 <br />
| 6 <br />
| 0 <br />
| <br />
2<br> <br />
<br />
*ROC_Asia/Pacific/TW-NCUHEP, 3 consecutive months below the target (site suspended by ROC), #75041<br> <br />
*ROC_Asia/Pacific/IN-DAE-VECC-02, 4 consecutive months below the target (site suspended by COD), #75040<br />
<br />
| 0<br />
|-<br />
| August 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74147 74147] <br />
| 31 <br />
| 3 <br />
| 0 <br />
| 0 <br />
| 0<br />
|-<br />
| July 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=73193 73193] <br />
| 35 <br />
| 4 <br />
| 0 <br />
| <br />
2 <br />
<br />
*ROC_Asia/Pacific/TW-eScience, 3 consecutive months below the target(site suspended by ROC), ticket #73539<br> <br />
*ROC_Asia/Pacific/TW-NYMU-GRID,3 consecutive months below the target(site suspended by ROC), ticket #73540<br />
<br />
| 0<br />
|-<br />
| June 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=72259 72259] <br />
| 31 <br />
| 8 <br />
| 0 <br />
| 5 <br />
*ROC_Asia, Pacific/PH-ASTI-LIKNAYAN, 3 consecutive months below target, ticket #72435 <br />
*ROC_Asia, Pacific/TH-HAI, 3 consecutive months below target, #72436 <br />
*NGI_IBERGRID, UOGRID, 3 consecutive months below target, #72439 <br />
*ROC_IGALC, CEFET-RJ, 3 consecutive months below target, #72440 <br />
*ROC_IGALC, LA-MERIDA, 3 consecutive months below target, #72441<br />
<br />
| 0<br><br />
|-<br />
| May 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=71643 71643] <br />
| 23 <br />
| <br />
4 <br />
<br />
this month first time targed was changed to ava 70% rel 75% <br />
<br />
| 0 <br />
| 2 <br />
*UOGRID, NGI_IBERGRID, below 50%/50% for three months, 71787 <br />
*PH-ASTI-LIKNAYAN, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 71789&nbsp;<br />
<br />
| 0<br><br />
|-<br />
| April 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=70289 70289] <br />
| 39 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| March 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=69629 69629] <br />
| 30 <br />
| 0 <br />
| <br />
1 <br />
<br />
*ru-Moscow-SINP-LCG2, ROC_Russia, 69765<br><br />
<br />
| 0 <br />
| 0<br><br />
|-<br />
| February 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=68299 68299] / See also [https://gus.fzk.de/ws/ticket_info.php?ticket=68229 68229] <br />
| 28 <br />
| 0 <br />
| 1 <br />
*RU-SPbSU, ROC_Russia<br />
<br />
| <br> <br />
| 0<br><br />
|-<br />
| Jan 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=67008 67008] <br />
| 27 <br />
| 2 <br />
| 1 <br />
*ru-IMPB-LCG2,ROC_Russia, 67038<br />
<br />
| 2 <br />
*MY-UM-PANG5, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 67010 <br />
*ru-IMPB-LCG2,ROC_Russia, sites didn't provided explanation,67038<br />
<br />
| 0 <br><br />
|-<br />
| Dec 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=65971 65971] <br />
| 30 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0 <br><br />
|-<br />
| Nov 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=64892 64892] <br />
| 40 <br />
| 1 <br />
| 0 <br />
| 1 <br />
*ID-ITB, ROC_Asia/Pacific,below 50%/50% for three months (site suspended by ROC),64951<br />
<br />
| 0<br><br />
|-<br />
| Oct 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=63658 63658] <br />
| 37 <br />
| 4 <br />
| 1 <br />
*AM-04-YERPHI, NGI_ARMGRID, 63854<br />
<br />
| 2 <br />
*AM-01-IIAP-NAS-RA, NGI_ARMGRID, below 50%/50% for three months, 63837 <br />
*AM-04-YERPHI, NGI_ARMGRID, no explanation given, 63854<br />
<br />
| 0<br><br />
|-<br />
| Sep 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=62853 62853] <br />
| 39 <br />
| 2 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Aug 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61797 61797] <br />
| 43 <br />
| 3 <br />
| 10 <br />
*JP-HIROSHIMA-WLCG, ROC AP, 62323 <br />
*AU-PPS, ROC AP,62316 <br />
*MY-UTM-GRID, ROC AP, 62312 <br />
*TH-NECTEC-LSR, ROC AP, 62304 <br />
*MY-UM-CRYSTAL, ROC AP, 62300 <br />
*ID-ITB, ROC AP, 62296 <br />
*GRISU-COMETA-INFN-LNS, ROC Italy, 62314 <br />
*UNIGE-DPNC, NGI_NDGF, 62308 <br />
*ru-IMPB-LCG2, ROC_Russia, 62305 <br />
*IL-TAU-HEP,ROC_SE, 62306<br />
<br />
| 1 <br />
*TW-NCUHEP, ROC AP, below 50%/50% for three months, 62340<br />
<br />
| 0<br><br />
|-<br />
| Jul 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61115 61115] <br />
| 47 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Jun 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=60216 60216] <br />
| 59 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| May 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=59736 59736] <br />
| 38 <br />
| 3 <br />
| 1 <br />
*ru-Chernogolovka-IPCP-LCG2, ROC RU, 59819<br />
<br />
| 0 <br />
| 0<br><br />
|}<br />
<br />
[[Category:Service_Level_Management]] [[Category:COD]]<br />
<br />
<br></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Underperforming_sites_and_suspensions&diff=35302Underperforming sites and suspensions2012-04-05T08:43:44Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
Information about underperforming and suspended Resource Centres is provided in the table below. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! date <br />
! GGUSID <br />
! nb. sites <br />
below 75%/70% targets <br />
<br />
! nb. sites <br />
below the target for 3 months <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
which didn't provide explanation <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
suspended by COD <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
! nb. sites <br />
suspended by CSIRT <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
|-<br />
| March 2012<br />
| [https://ggus.eu/ws/ticket_info.php?ticket=80900 80900]<br />
| 25<br />
| 2<br />
| <br />
| <br />
| <br />
|-<br />
| February 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79844 79844] <br />
| 35 <br />
| 3 <br />
| 0 <br />
| 2 suspended by ROC<br> <br />
*IN-DAE-VECC-02, 80037 <br />
*MY-UM-CRYSTAL, 80038<br />
<br />
| 0<br />
|-<br />
| January 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79020 79020] <br />
| 30 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 1; GARR-01-DIR, NGI_IT due to issue (EGI-20120116-01) recorded in RTIR ticket #3300)<br />
|-<br />
| December 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=78040 78040] <br />
| 28 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| November 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=77170 77170] <br />
| 26 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| October 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=76305 76305] <br />
| 45 <br />
| 3 <br />
| <br />
3<br> <br />
<br />
*ROC_Russia/RRC-KI, 76408 <br />
*NGI_IL/WEIZMANN-LCG2, 76386 <br />
*NGI_IL/TECHNION-HEP, 76384<br />
<br />
| <br />
1<br> <br />
<br />
*NGI_ARMGRID/AM-04-YERPHI,76428<br />
<br />
| 0<br />
|-<br />
| September 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74965 74965] <br />
| 25 <br />
| 6 <br />
| 0 <br />
| <br />
2<br> <br />
<br />
*ROC_Asia/Pacific/TW-NCUHEP, 3 consecutive months below the target (site suspended by ROC), #75041<br> <br />
*ROC_Asia/Pacific/IN-DAE-VECC-02, 4 consecutive months below the target (site suspended by COD), #75040<br />
<br />
| 0<br />
|-<br />
| August 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74147 74147] <br />
| 31 <br />
| 3 <br />
| 0 <br />
| 0 <br />
| 0<br />
|-<br />
| July 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=73193 73193] <br />
| 35 <br />
| 4 <br />
| 0 <br />
| <br />
2 <br />
<br />
*ROC_Asia/Pacific/TW-eScience, 3 consecutive months below the target(site suspended by ROC), ticket #73539<br> <br />
*ROC_Asia/Pacific/TW-NYMU-GRID,3 consecutive months below the target(site suspended by ROC), ticket #73540<br />
<br />
| 0<br />
|-<br />
| June 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=72259 72259] <br />
| 31 <br />
| 8 <br />
| 0 <br />
| 5 <br />
*ROC_Asia, Pacific/PH-ASTI-LIKNAYAN, 3 consecutive months below target, ticket #72435 <br />
*ROC_Asia, Pacific/TH-HAI, 3 consecutive months below target, #72436 <br />
*NGI_IBERGRID, UOGRID, 3 consecutive months below target, #72439 <br />
*ROC_IGALC, CEFET-RJ, 3 consecutive months below target, #72440 <br />
*ROC_IGALC, LA-MERIDA, 3 consecutive months below target, #72441<br />
<br />
| 0<br><br />
|-<br />
| May 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=71643 71643] <br />
| 23 <br />
| <br />
4 <br />
<br />
this month first time targed was changed to ava 70% rel 75% <br />
<br />
| 0 <br />
| 2 <br />
*UOGRID, NGI_IBERGRID, below 50%/50% for three months, 71787 <br />
*PH-ASTI-LIKNAYAN, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 71789&nbsp;<br />
<br />
| 0<br><br />
|-<br />
| April 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=70289 70289] <br />
| 39 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| March 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=69629 69629] <br />
| 30 <br />
| 0 <br />
| <br />
1 <br />
<br />
*ru-Moscow-SINP-LCG2, ROC_Russia, 69765<br><br />
<br />
| 0 <br />
| 0<br><br />
|-<br />
| February 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=68299 68299] / See also [https://gus.fzk.de/ws/ticket_info.php?ticket=68229 68229] <br />
| 28 <br />
| 0 <br />
| 1 <br />
*RU-SPbSU, ROC_Russia<br />
<br />
| <br> <br />
| 0<br><br />
|-<br />
| Jan 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=67008 67008] <br />
| 27 <br />
| 2 <br />
| 1 <br />
*ru-IMPB-LCG2,ROC_Russia, 67038<br />
<br />
| 2 <br />
*MY-UM-PANG5, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 67010 <br />
*ru-IMPB-LCG2,ROC_Russia, sites didn't provided explanation,67038<br />
<br />
| 0 <br><br />
|-<br />
| Dec 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=65971 65971] <br />
| 30 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0 <br><br />
|-<br />
| Nov 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=64892 64892] <br />
| 40 <br />
| 1 <br />
| 0 <br />
| 1 <br />
*ID-ITB, ROC_Asia/Pacific,below 50%/50% for three months (site suspended by ROC),64951<br />
<br />
| 0<br><br />
|-<br />
| Oct 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=63658 63658] <br />
| 37 <br />
| 4 <br />
| 1 <br />
*AM-04-YERPHI, NGI_ARMGRID, 63854<br />
<br />
| 2 <br />
*AM-01-IIAP-NAS-RA, NGI_ARMGRID, below 50%/50% for three months, 63837 <br />
*AM-04-YERPHI, NGI_ARMGRID, no explanation given, 63854<br />
<br />
| 0<br><br />
|-<br />
| Sep 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=62853 62853] <br />
| 39 <br />
| 2 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Aug 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61797 61797] <br />
| 43 <br />
| 3 <br />
| 10 <br />
*JP-HIROSHIMA-WLCG, ROC AP, 62323 <br />
*AU-PPS, ROC AP,62316 <br />
*MY-UTM-GRID, ROC AP, 62312 <br />
*TH-NECTEC-LSR, ROC AP, 62304 <br />
*MY-UM-CRYSTAL, ROC AP, 62300 <br />
*ID-ITB, ROC AP, 62296 <br />
*GRISU-COMETA-INFN-LNS, ROC Italy, 62314 <br />
*UNIGE-DPNC, NGI_NDGF, 62308 <br />
*ru-IMPB-LCG2, ROC_Russia, 62305 <br />
*IL-TAU-HEP,ROC_SE, 62306<br />
<br />
| 1 <br />
*TW-NCUHEP, ROC AP, below 50%/50% for three months, 62340<br />
<br />
| 0<br><br />
|-<br />
| Jul 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61115 61115] <br />
| 47 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Jun 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=60216 60216] <br />
| 59 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| May 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=59736 59736] <br />
| 38 <br />
| 3 <br />
| 1 <br />
*ru-Chernogolovka-IPCP-LCG2, ROC RU, 59819<br />
<br />
| 0 <br />
| 0<br><br />
|}<br />
<br />
[[Category:Service_Level_Management]] [[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Underperforming_sites_and_suspensions&diff=35170Underperforming sites and suspensions2012-04-02T12:55:02Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
Information about underperforming and suspended Resource Centres is provided in the table below. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! date <br />
! GGUSID <br />
! nb. sites <br />
below 75%/70% targets <br />
<br />
! nb. sites <br />
below the target for 3 months <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
which didn't provide explanation <br />
<br />
*site name, NGI/ROC, short reason to not suspend&nbsp;(if applicable), GGUS ID<br />
<br />
! nb. sites <br />
suspended by COD <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
! nb. sites <br />
suspended by CSIRT <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
|-<br />
| February 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79844 79844] <br />
| 35 <br />
| 3 <br />
| 0 <br />
| 2 suspended by ROC<br> <br />
*IN-DAE-VECC-02, 80037 <br />
*MY-UM-CRYSTAL, 80038<br />
<br />
| 0<br />
|-<br />
| January 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79020 79020] <br />
| 30 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 1; GARR-01-DIR, NGI_IT due to issue (EGI-20120116-01) recorded in RTIR ticket #3300)<br />
|-<br />
| December 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=78040 78040] <br />
| 28 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| November 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=77170 77170] <br />
| 26 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| 0<br />
|-<br />
| October 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=76305 76305] <br />
| 45 <br />
| 3 <br />
| <br />
3<br> <br />
<br />
*ROC_Russia/RRC-KI, 76408 <br />
*NGI_IL/WEIZMANN-LCG2, 76386 <br />
*NGI_IL/TECHNION-HEP, 76384<br />
<br />
| <br />
1<br> <br />
<br />
*NGI_ARMGRID/AM-04-YERPHI,76428<br />
<br />
| 0<br />
|-<br />
| September 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74965 74965] <br />
| 25 <br />
| 6 <br />
| 0 <br />
| <br />
2<br> <br />
<br />
*ROC_Asia/Pacific/TW-NCUHEP, 3 consecutive months below the target (site suspended by ROC), #75041<br> <br />
*ROC_Asia/Pacific/IN-DAE-VECC-02, 4 consecutive months below the target (site suspended by COD), #75040<br />
<br />
| 0<br />
|-<br />
| August 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74147 74147] <br />
| 31 <br />
| 3 <br />
| 0 <br />
| 0 <br />
| 0<br />
|-<br />
| July 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=73193 73193] <br />
| 35 <br />
| 4 <br />
| 0 <br />
| <br />
2 <br />
<br />
*ROC_Asia/Pacific/TW-eScience, 3 consecutive months below the target(site suspended by ROC), ticket #73539<br> <br />
*ROC_Asia/Pacific/TW-NYMU-GRID,3 consecutive months below the target(site suspended by ROC), ticket #73540<br />
<br />
| 0<br />
|-<br />
| June 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=72259 72259] <br />
| 31 <br />
| 8 <br />
| 0 <br />
| 5 <br />
*ROC_Asia, Pacific/PH-ASTI-LIKNAYAN, 3 consecutive months below target, ticket #72435 <br />
*ROC_Asia, Pacific/TH-HAI, 3 consecutive months below target, #72436 <br />
*NGI_IBERGRID, UOGRID, 3 consecutive months below target, #72439 <br />
*ROC_IGALC, CEFET-RJ, 3 consecutive months below target, #72440 <br />
*ROC_IGALC, LA-MERIDA, 3 consecutive months below target, #72441<br />
<br />
| 0<br><br />
|-<br />
| May 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=71643 71643] <br />
| 23 <br />
| <br />
4 <br />
<br />
this month first time targed was changed to ava 70% rel 75% <br />
<br />
| 0 <br />
| 2 <br />
*UOGRID, NGI_IBERGRID, below 50%/50% for three months, 71787 <br />
*PH-ASTI-LIKNAYAN, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 71789&nbsp;<br />
<br />
| 0<br><br />
|-<br />
| April 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=70289 70289] <br />
| 39 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| March 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=69629 69629] <br />
| 30 <br />
| 0 <br />
| <br />
1 <br />
<br />
*ru-Moscow-SINP-LCG2, ROC_Russia, 69765<br><br />
<br />
| 0 <br />
| 0<br><br />
|-<br />
| February 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=68299 68299] / See also [https://gus.fzk.de/ws/ticket_info.php?ticket=68229 68229] <br />
| 28 <br />
| 0 <br />
| 1 <br />
*RU-SPbSU, ROC_Russia<br />
<br />
| <br> <br />
| 0<br><br />
|-<br />
| Jan 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=67008 67008] <br />
| 27 <br />
| 2 <br />
| 1 <br />
*ru-IMPB-LCG2,ROC_Russia, 67038<br />
<br />
| 2 <br />
*MY-UM-PANG5, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 67010 <br />
*ru-IMPB-LCG2,ROC_Russia, sites didn't provided explanation,67038<br />
<br />
| 0 <br><br />
|-<br />
| Dec 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=65971 65971] <br />
| 30 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| 0 <br><br />
|-<br />
| Nov 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=64892 64892] <br />
| 40 <br />
| 1 <br />
| 0 <br />
| 1 <br />
*ID-ITB, ROC_Asia/Pacific,below 50%/50% for three months (site suspended by ROC),64951<br />
<br />
| 0<br><br />
|-<br />
| Oct 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=63658 63658] <br />
| 37 <br />
| 4 <br />
| 1 <br />
*AM-04-YERPHI, NGI_ARMGRID, 63854<br />
<br />
| 2 <br />
*AM-01-IIAP-NAS-RA, NGI_ARMGRID, below 50%/50% for three months, 63837 <br />
*AM-04-YERPHI, NGI_ARMGRID, no explanation given, 63854<br />
<br />
| 0<br><br />
|-<br />
| Sep 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=62853 62853] <br />
| 39 <br />
| 2 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Aug 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61797 61797] <br />
| 43 <br />
| 3 <br />
| 10 <br />
*JP-HIROSHIMA-WLCG, ROC AP, 62323 <br />
*AU-PPS, ROC AP,62316 <br />
*MY-UTM-GRID, ROC AP, 62312 <br />
*TH-NECTEC-LSR, ROC AP, 62304 <br />
*MY-UM-CRYSTAL, ROC AP, 62300 <br />
*ID-ITB, ROC AP, 62296 <br />
*GRISU-COMETA-INFN-LNS, ROC Italy, 62314 <br />
*UNIGE-DPNC, NGI_NDGF, 62308 <br />
*ru-IMPB-LCG2, ROC_Russia, 62305 <br />
*IL-TAU-HEP,ROC_SE, 62306<br />
<br />
| 1 <br />
*TW-NCUHEP, ROC AP, below 50%/50% for three months, 62340<br />
<br />
| 0<br><br />
|-<br />
| Jul 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61115 61115] <br />
| 47 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| Jun 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=60216 60216] <br />
| 59 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| 0<br><br />
|-<br />
| May 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=59736 59736] <br />
| 38 <br />
| 3 <br />
| 1 <br />
*ru-Chernogolovka-IPCP-LCG2, ROC RU, 59819<br />
<br />
| 0 <br />
| 0<br><br />
|}<br />
<br />
[[Category:Service_Level_Management]] [[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Operations_and_Operations_Support&diff=34336Operations and Operations Support2012-03-15T20:19:33Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
= Introduction =<br />
<br />
'''COD team '''is a small team responsible for coordination of RODs, provided on a global layer. COD represents the whole ROD structure in terms of technical requirements for operations tools as well as on political level. <br />
<br />
The purpose of this page is to collect all materials needed by COD team to perform the Grid operations oversight activities. <br />
<br />
= People and contact =<br />
<br />
COD team is formed from Dutch and Polish team and includes COD managers (people responsible for managerial issues) and COD shifters (people performing day-to-day COD work) <br />
<br />
;'''COD managers:'''&nbsp; <br />
:Ron Trompert (Chair), Marcin Radecki, Luuk Uljee, Małgorzata Krakowian <br />
;'''COD shifters:'''&nbsp; <br />
:Małgorzata Krakowian, Ron Trompert, Luuk Uljee, Maarten van Ingen, Ernst Pijper, Alexander Verkooijen<br />
<br />
<br> [[Grid operations oversight/Photo|People behind the names]] <br />
<br />
<br> There are 2 mailing lists used for different cases: <br />
<br />
*'''manager-central-operator-on-duty''' AT mailman.egi.eu - for COD managerial issues like suggesting changes in procedures, tools. '''COD managers''' are recipients of this list. <br />
*'''central-operator-on-duty''' AT mailman.egi.eu - for reporting COD day-to-day issues like problems with tools or Nagios tests. '''COD shifters''' are recipients of this list.<br />
<br />
= COD Duties =<br />
<br />
*COD managers <br />
**'''representing RODs/COD in OTAG, OMB and Operations meetings''' - collecting requirements and improvements proposals from RODs concerning operations tools and procedures <br />
**'''suspending Resource Centres''' in case of operational issues <br />
**'''taking part in OLA task force''' <br />
**'''writing new procedures''' - in case of need COD is taking part in procedures creation process <br />
**'''preparing ROD newsletters''' - informing RODs about recent and upcoming developments related to Grid Oversight <br />
**'''preparing ROD metrics reports''' - providing an overview of operations support process in grid infrastructure. <br />
*COD shifters <br />
**'''escalation of operational problems with RODs''' <br />
**'''dealing with GGUS tickets assigned to COD''' <br />
**'''process coordination''' of: <br />
***creation and decommission of Operations Centre <br />
***setting a Nagios test to an operations test <br />
***getting explanations for low availability and reliability metrics<br />
<br />
= COD shifters work instructions =<br />
<br />
In this section are collected all work instructions containing detailed information specifying exactly what steps are to be followed to carry out an activity. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! Action <br />
! Description <br />
! Related procedures<br />
|-<br />
| '''GGUS tickets assigned to COD''' <br />
| <br />
COD shifter is obliged to check the current status of all '''GGUS tickets assigned to COD''' <br />
<br />
*see [http://tinyurl.com/2ws735h Link to all GGUS tickets assigned to COD] <br />
*If the ticket is waiting for COD action then he/she should perform the action<br />
<br />
<br> In case of a request for: <br />
<br />
*'''ROD certification''' <br />
**see [[Grid operations oversight/WI01|New ROD team certification work instructions]] <br />
*'''Creation of a new NGI''' <br />
**see [[PROC02|Creation of a new Operations Centre process coordination]] <br />
**see [https://wiki.egi.eu/wiki/Grid_operations_oversight/WI02 work instruction] <br />
**In case where COD is also the Integration Process Coordinator, COD is responsible for the whole procedure. <br />
*'''Operations Centre decommission''' <br />
**see [[PROC03|Operations Centre decommission process coordination]] <br />
**COD validates the request and removes ROD information from all-operators mailing list <br />
*'''Setting a Nagios test to an operations test''' <br />
**see [[PROC06|Procedure for setting a Nagios test to an operations test]] <br />
**COD is responsible for coordinating the whole process.<br />
<br />
If the shifter doesn't know what kind of action should be taken, he/she should contact COD managers <br />
<br />
| <br />
*[[PROC02|Creation of a new Operations Centre process coordination]] <br />
*[[PROC03|Operations Centre decommission process coordination]] <br />
*[[PROC06|Procedure for setting Nagios test an operations test]]<br />
<br />
|-<br />
| '''Availability/reliability reports''' <br />
| <br />
*Handling availability/reliability reports: [[Grid operations oversight/WI03|Availability and reliability work instruction]] <br />
**[[Underperforming sites and suspensions|AR reports metrics]]<br />
<br />
| <br />
*[[Operations:COD Escalation Procedure|COD escalation procedure]] <br />
*[[Availability and reliability monthly statistics|Availability and reliability monthly statistics procedure]]<br />
<br />
|-<br />
| '''Operational portal dashboard issues''' <br />
| <br />
*[https://operations-portal.egi.eu/dashboard/ccodView COD dashboard link]<br />
<br />
| <br />
*[[PROC01|COD escalation procedure]]<br />
<br />
|-<br />
| '''Handover''' <br />
| <br />
[https://operations-portal.egi.eu/dashboard/ccodView COD dashboard link] <br />
<br />
*At the end of the shift a handover should be submitted (send to COD) via Handover tool in the Operational Portal <br />
**Problems on the dashboard which will pass to next week: the ggus id of the ticket and when next escalation step should be taken <br />
**GGUS tickets assigned to COD: for each ticket its last status and the action taken by the shifter should be provided <br />
**Other issues: problems with tools etc.<br />
<br />
| <br><br />
|}<br />
<br />
<br> ''NOTE: all procedures should contain the following template: https://wiki.egi.eu/wiki/PDT:Procedure_Template'' <br />
<br />
== ''Work Instructions''<br> ==<br />
<br />
*[[Grid operations oversight/WI01|New ROD team certification work instructions]] <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/WI02 New Opertions Centre creation work instruction] <br />
*[[Grid operations oversight/WI03|Availability and reliability work instruction]]<br />
<br />
= Events =<br />
<br />
*[https://www.egi.eu/indico/categoryDisplay.py?categId=11 EGI indico page] with COD meeting agendas. <br />
*All open actions can be found from [[Grid operations oversight/CODOD actions|COD actions]]<br />
<br />
= Resources =<br />
<br />
*[https://documents.egi.eu/secure/ShowDocument?docid=298 Document server: ROD newsletter] <br />
*[https://documents.egi.eu/secure/ShowDocument?docid=155 Document server: Operations Support Metrics] <br />
*[https://wiki.egi.eu/wiki/Operations_Procedures Operations Procedures] <br />
*[http://www.youtube.com/user/EGIGridOversight Youtube channel]<br />
<br />
== ROD and COD Performance ==<br />
<br />
Definition of [[Grid operations oversight/ROD performance index|ROD performance index]] <!--*[[Grid operations oversight/OperationsSupportMetrics summary|Operations Support Metrics - reports summary]]--><br />
<br />
=== Oct 2011 to date ===<br />
<br />
*Please provide a link here<br />
<br />
<br> <br />
<br />
<br> <br />
<br />
Definition of [[Grid operations oversight/OperationsSupportMetrics|Operations Support metrics]]<br />
<br />
=== May 2010-Sep 2011 ===<br />
<br />
*Operations Support [https://documents.egi.eu/document/155 metrics]<br />
<br />
=== Until April 2010 ===<br />
<br />
*EGEE-III Operations Support [https://documents.egi.eu/document/829 metrics]<br />
<br />
== Nagios tests ==<br />
<br />
*[[Operations:Operations tests|Operations tests list ]]: list of Nagios probes generating alarms for visualization in the Operations Dashboard <br />
*[http://grid-monitoring.cern.ch/myegi/sam-pi/metrics_in_profiles?vo_name=ops&profile_name=ROC_CRITICAL Availability and reliability tests list]: list of Nagios probes whose results are used for Availability and Reliability computation<br />
<br />
== OTAG topics ==<br />
<br />
=== Operational Portal: Dashboard ===<br />
<br />
*[http://bit.ly/dZ3RWN RT tickets] <br />
*[[Grid operations oversight/COD interaction with Dashboard team|COD interactions with Dashboard team (draft)]] <br />
*[[Grid operations oversight/COD OTAG topics|COD topics to be discussed on OTAG meeting]]<br />
<br />
=== GOC DB ===<br />
<br />
*[[Grid operations oversight/COD GOCDB requirements|Collection of GOC DB requirements regarding COD work (draft)]]<br />
<br />
== Pages in draft state ==<br />
<br />
*[[Grid operations oversight/COD Improvements to availability procedure|Improvements to Availability Calculation Procedure (draft)]]<br />
<br />
*[[Grid operations oversight/A/R fixing procedure|A/R fixing procedure (draft)]][[Grid operations oversight/ROD FAQ|<br>]]<br />
<br />
<br> <br />
<br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/Unknown_issue UNKNOWN issue ]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/Unknown_issue-internal UNKNOWN issue Internal ]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/ROD_performance_index ROD&nbsp;performance&nbsp;index]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/CandidateSuspendedSitesList Candidate Suspended Sites List]<br />
<br />
[[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Operations_and_Operations_Support&diff=34335Operations and Operations Support2012-03-15T20:19:04Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
= Introduction =<br />
<br />
'''COD team '''is a small team responsible for coordination of RODs, provided on a global layer. COD represents the whole ROD structure in terms of technical requirements for operations tools as well as on political level. <br />
<br />
The purpose of this page is to collect all materials needed by COD team to perform the Grid operations oversight activities. <br />
<br />
= People and contact =<br />
<br />
COD team is formed from Dutch and Polish team and includes COD managers (people responsible for managerial issues) and COD shifters (people performing day-to-day COD work) <br />
<br />
;'''COD managers:'''&nbsp; <br />
:Ron Trompert (Chair), Marcin Radecki, Luuk Uljee, Małgorzata Krakowian <br />
;'''COD shifters:'''&nbsp; <br />
:Małgorzata Krakowian, Ron Trompert, Luuk Uljee, Maarten van Ingen, Ernst Pijper, Alexander Verkooijen<br />
<br />
<br> [[Grid operations oversight/Photo|People behind the names]] <br />
<br />
<br> There are 2 mailing lists used for different cases: <br />
<br />
*'''manager-central-operator-on-duty''' AT mailman.egi.eu - for COD managerial issues like suggesting changes in procedures, tools. '''COD managers''' are recipients of this list. <br />
*'''central-operator-on-duty''' AT mailman.egi.eu - for reporting COD day-to-day issues like problems with tools or Nagios tests. '''COD shifters''' are recipients of this list.<br />
<br />
= COD Duties =<br />
<br />
*COD managers <br />
**'''representing RODs/COD in OTAG, OMB and Operations meetings''' - collecting requirements and improvements proposals from RODs concerning operations tools and procedures <br />
**'''suspending Resource Centres''' in case of operational issues <br />
**'''taking part in OLA task force''' <br />
**'''writing new procedures''' - in case of need COD is taking part in procedures creation process <br />
**'''preparing ROD newsletters''' - informing RODs about recent and upcoming developments related to Grid Oversight <br />
**'''preparing ROD metrics reports''' - providing an overview of operations support process in grid infrastructure. <br />
*COD shifters <br />
**'''escalation of operational problems with RODs''' <br />
**'''dealing with GGUS tickets assigned to COD''' <br />
**'''process coordination''' of: <br />
***creation and decommission of Operations Centre <br />
***setting a Nagios test to an operations test <br />
***getting explanations for low availability and reliability metrics<br />
<br />
= COD shifters work instructions =<br />
<br />
In this section are collected all work instructions containing detailed information specifying exactly what steps are to be followed to carry out an activity. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! Action <br />
! Description <br />
! Related procedures<br />
|-<br />
| '''GGUS tickets assigned to COD''' <br />
| <br />
COD shifter is obliged to check the current status of all '''GGUS tickets assigned to COD''' <br />
<br />
*see [http://tinyurl.com/2ws735h Link to all GGUS tickets assigned to COD] <br />
*If the ticket is waiting for COD action then he/she should perform the action<br />
<br />
<br> In case of a request for: <br />
<br />
*'''ROD certification''' <br />
**see [[Grid operations oversight/WI01|New ROD team certification work instructions]] <br />
*'''Creation of a new NGI''' <br />
**see [[PROC02|Creation of a new Operations Centre process coordination]] <br />
**see [https://wiki.egi.eu/wiki/Grid_operations_oversight/WI02 work instruction] <br />
**In case where COD is also the Integration Process Coordinator, COD is responsible for the whole procedure. <br />
*'''Operations Centre decommission''' <br />
**see [[PROC03|Operations Centre decommission process coordination]] <br />
**COD validates the request and removes ROD information from all-operators mailing list <br />
*'''Setting a Nagios test to an operations test''' <br />
**see [[PROC06|Procedure for setting a Nagios test to an operations test]] <br />
**COD is responsible for coordinating the whole process.<br />
<br />
If the shifter doesn't know what kind of action should be taken, he/she should contact COD managers <br />
<br />
| <br />
*[[PROC02|Creation of a new Operations Centre process coordination]] <br />
*[[PROC03|Operations Centre decommission process coordination]] <br />
*[[PROC06|Procedure for setting Nagios test an operations test]]<br />
<br />
|-<br />
| '''Availability/reliability reports''' <br />
| <br />
*Handling availability/reliability reports: [[Grid operations oversight/WI03|Availability and reliability work instruction]] <br />
**[[Underperforming sites and suspensions|AR reports metrics]]<br />
<br />
| <br />
*[[Operations:COD Escalation Procedure|COD escalation procedure]] <br />
*[[Availability and reliability monthly statistics|Availability and reliability monthly statistics procedure]]<br />
<br />
|-<br />
| '''Operational portal dashboard issues''' <br />
| <br />
*[https://operations-portal.egi.eu/dashboard/ccodView COD dashboard link]<br />
<br />
| <br />
*[[PROC01|COD escalation procedure]]<br />
<br />
|-<br />
| '''Handover''' <br />
| <br />
[https://operations-portal.egi.eu/dashboard/ccodView COD dashboard link] <br />
<br />
*At the end of the shift a handover should be submitted (send to COD) via Handover tool in the Operational Portal <br />
**Problems on the dashboard which will pass to next week: the ggus id of the ticket and when next escalation step should be taken <br />
**GGUS tickets assigned to COD: for each ticket its last status and the action taken by the shifter should be provided <br />
**Other issues: problems with tools etc.<br />
<br />
| <br><br />
|}<br />
<br />
<br> ''NOTE: all procedures should contain the following template: https://wiki.egi.eu/wiki/PDT:Procedure_Template'' <br />
<br />
== ''Work Instructions''<br> ==<br />
<br />
*[[Grid operations oversight/WI01|New ROD team certification work instructions]] <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/WI02 New Opertions Centre creation work instruction] <br />
*[[Grid operations oversight/WI03|Availability and reliability work instruction]]<br />
<br />
= Events =<br />
<br />
*[https://www.egi.eu/indico/categoryDisplay.py?categId=11 EGI indico page] with COD meeting agendas. <br />
*All open actions can be found from [[Grid operations oversight/CODOD actions|COD actions]]<br />
<br />
= Resources =<br />
<br />
*[https://documents.egi.eu/secure/ShowDocument?docid=298 Document server: ROD newsletter] <br />
*[https://documents.egi.eu/secure/ShowDocument?docid=155 Document server: Operations Support Metrics] <br />
*[https://wiki.egi.eu/wiki/Operations_Procedures Operations Procedures] <br />
*[http://www.youtube.com/user/EGIGridOversight Youtube channel]<br />
<br />
== ROD and COD Performance ==<br />
<br />
*Definition of [[Grid operations oversight/ROD performance index|ROD performance index]] <!--*[[Grid operations oversight/OperationsSupportMetrics summary|Operations Support Metrics - reports summary]]--><br />
<br />
=== Oct 2011 to date ===<br />
<br />
Please provide a link here <br />
<br />
<br />
<br />
<br />
<br />
*Definition of [[Grid operations oversight/OperationsSupportMetrics|Operations Support metrics]]<br />
<br />
=== May 2010-Sep 2011 ===<br />
<br />
*Operations Support [https://documents.egi.eu/document/155 metrics]<br />
<br />
=== Until April 2010 ===<br />
<br />
*EGEE-III Operations Support [https://documents.egi.eu/document/829 metrics]<br />
<br />
== Nagios tests ==<br />
<br />
*[[Operations:Operations tests|Operations tests list ]]: list of Nagios probes generating alarms for visualization in the Operations Dashboard <br />
*[http://grid-monitoring.cern.ch/myegi/sam-pi/metrics_in_profiles?vo_name=ops&profile_name=ROC_CRITICAL Availability and reliability tests list]: list of Nagios probes whose results are used for Availability and Reliability computation<br />
<br />
== OTAG topics ==<br />
<br />
=== Operational Portal: Dashboard ===<br />
<br />
*[http://bit.ly/dZ3RWN RT tickets] <br />
*[[Grid operations oversight/COD interaction with Dashboard team|COD interactions with Dashboard team (draft)]] <br />
*[[Grid operations oversight/COD OTAG topics|COD topics to be discussed on OTAG meeting]]<br />
<br />
=== GOC DB ===<br />
<br />
*[[Grid operations oversight/COD GOCDB requirements|Collection of GOC DB requirements regarding COD work (draft)]]<br />
<br />
== Pages in draft state ==<br />
<br />
*[[Grid operations oversight/COD Improvements to availability procedure|Improvements to Availability Calculation Procedure (draft)]]<br />
<br />
*[[Grid operations oversight/A/R fixing procedure|A/R fixing procedure (draft)]][[Grid operations oversight/ROD FAQ|<br>]]<br />
<br />
<br> <br />
<br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/Unknown_issue UNKNOWN issue ]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/Unknown_issue-internal UNKNOWN issue Internal ]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/ROD_performance_index ROD&nbsp;performance&nbsp;index]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/CandidateSuspendedSitesList Candidate Suspended Sites List]<br />
<br />
[[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Operations_and_Operations_Support&diff=34334Operations and Operations Support2012-03-15T20:14:41Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
= Introduction =<br />
<br />
'''COD team '''is a small team responsible for coordination of RODs, provided on a global layer. COD represents the whole ROD structure in terms of technical requirements for operations tools as well as on political level. <br />
<br />
The purpose of this page is to collect all materials needed by COD team to perform the Grid operations oversight activities. <br />
<br />
= People and contact =<br />
<br />
COD team is formed from Dutch and Polish team and includes COD managers (people responsible for managerial issues) and COD shifters (people performing day-to-day COD work) <br />
<br />
;'''COD managers:'''&nbsp; <br />
:Ron Trompert (Chair), Marcin Radecki, Luuk Uljee, Małgorzata Krakowian <br />
;'''COD shifters:'''&nbsp; <br />
:Małgorzata Krakowian, Ron Trompert, Luuk Uljee, Maarten van Ingen, Ernst Pijper, Alexander Verkooijen<br />
<br />
<br> [[Grid operations oversight/Photo|People behind the names]] <br />
<br />
<br> There are 2 mailing lists used for different cases: <br />
<br />
*'''manager-central-operator-on-duty''' AT mailman.egi.eu - for COD managerial issues like suggesting changes in procedures, tools. '''COD managers''' are recipients of this list. <br />
*'''central-operator-on-duty''' AT mailman.egi.eu - for reporting COD day-to-day issues like problems with tools or Nagios tests. '''COD shifters''' are recipients of this list.<br />
<br />
= COD Duties =<br />
<br />
*COD managers <br />
**'''representing RODs/COD in OTAG, OMB and Operations meetings''' - collecting requirements and improvements proposals from RODs concerning operations tools and procedures <br />
**'''suspending Resource Centres''' in case of operational issues <br />
**'''taking part in OLA task force''' <br />
**'''writing new procedures''' - in case of need COD is taking part in procedures creation process <br />
**'''preparing ROD newsletters''' - informing RODs about recent and upcoming developments related to Grid Oversight <br />
**'''preparing ROD metrics reports''' - providing an overview of operations support process in grid infrastructure. <br />
*COD shifters <br />
**'''escalation of operational problems with RODs''' <br />
**'''dealing with GGUS tickets assigned to COD''' <br />
**'''process coordination''' of: <br />
***creation and decommission of Operations Centre <br />
***setting a Nagios test to an operations test <br />
***getting explanations for low availability and reliability metrics<br />
<br />
= COD shifters work instructions =<br />
<br />
In this section are collected all work instructions containing detailed information specifying exactly what steps are to be followed to carry out an activity. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! Action <br />
! Description <br />
! Related procedures<br />
|-<br />
| '''GGUS tickets assigned to COD''' <br />
| <br />
COD shifter is obliged to check the current status of all '''GGUS tickets assigned to COD''' <br />
<br />
*see [http://tinyurl.com/2ws735h Link to all GGUS tickets assigned to COD] <br />
*If the ticket is waiting for COD action then he/she should perform the action<br />
<br />
<br> In case of a request for: <br />
<br />
*'''ROD certification''' <br />
**see [[Grid operations oversight/WI01|New ROD team certification work instructions]] <br />
*'''Creation of a new NGI''' <br />
**see [[PROC02|Creation of a new Operations Centre process coordination]] <br />
**see [https://wiki.egi.eu/wiki/Grid_operations_oversight/WI02 work instruction] <br />
**In case where COD is also the Integration Process Coordinator, COD is responsible for the whole procedure. <br />
*'''Operations Centre decommission''' <br />
**see [[PROC03|Operations Centre decommission process coordination]] <br />
**COD validates the request and removes ROD information from all-operators mailing list <br />
*'''Setting a Nagios test to an operations test''' <br />
**see [[PROC06|Procedure for setting a Nagios test to an operations test]] <br />
**COD is responsible for coordinating the whole process.<br />
<br />
If the shifter doesn't know what kind of action should be taken, he/she should contact COD managers <br />
<br />
| <br />
*[[PROC02|Creation of a new Operations Centre process coordination]] <br />
*[[PROC03|Operations Centre decommission process coordination]] <br />
*[[PROC06|Procedure for setting Nagios test an operations test]]<br />
<br />
|-<br />
| '''Availability/reliability reports''' <br />
| <br />
*Handling availability/reliability reports: [[Grid operations oversight/WI03|Availability and reliability work instruction]] <br />
**[[Underperforming sites and suspensions|AR reports metrics]]<br />
<br />
| <br />
*[[Operations:COD Escalation Procedure|COD escalation procedure]] <br />
*[[Availability and reliability monthly statistics|Availability and reliability monthly statistics procedure]]<br />
<br />
|-<br />
| '''Operational portal dashboard issues''' <br />
| <br />
*[https://operations-portal.egi.eu/dashboard/ccodView COD dashboard link]<br />
<br />
| <br />
*[[PROC01|COD escalation procedure]]<br />
<br />
|-<br />
| '''Handover''' <br />
| <br />
[https://operations-portal.egi.eu/dashboard/ccodView COD dashboard link] <br />
<br />
*At the end of the shift a handover should be submitted (send to COD) via Handover tool in the Operational Portal <br />
**Problems on the dashboard which will pass to next week: the ggus id of the ticket and when next escalation step should be taken <br />
**GGUS tickets assigned to COD: for each ticket its last status and the action taken by the shifter should be provided <br />
**Other issues: problems with tools etc.<br />
<br />
| <br><br />
|}<br />
<br />
<br> ''NOTE: all procedures should contain the following template: https://wiki.egi.eu/wiki/PDT:Procedure_Template'' <br />
<br />
== ''Work Instructions''<br> ==<br />
<br />
*[[Grid operations oversight/WI01|New ROD team certification work instructions]] <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/WI02 New Opertions Centre creation work instruction] <br />
*[[Grid operations oversight/WI03|Availability and reliability work instruction]]<br />
<br />
= Events =<br />
<br />
*[https://www.egi.eu/indico/categoryDisplay.py?categId=11 EGI indico page] with COD meeting agendas. <br />
*All open actions can be found from [[Grid operations oversight/CODOD actions|COD actions]]<br />
<br />
= Resources =<br />
<br />
*[https://documents.egi.eu/secure/ShowDocument?docid=298 Document server: ROD newsletter] <br />
*[https://documents.egi.eu/secure/ShowDocument?docid=155 Document server: Operations Support Metrics] <br />
*[https://wiki.egi.eu/wiki/Operations_Procedures Operations Procedures] <br />
*[http://www.youtube.com/user/EGIGridOversight Youtube channel]<br />
<br />
== ROD and COD Performance ==<br />
<br />
*Definition of [[Grid_operations_oversight/ROD_performance_index|ROD performance index]] <!--*[[Grid operations oversight/OperationsSupportMetrics summary|Operations Support Metrics - reports summary]]--><br />
<br />
=== Oct 2011 to date ===<br />
<br />
Please provide a link here <br />
<br />
*Definition of [[Grid operations oversight/OperationsSupportMetrics|Operations Support metrics]]<br />
<br />
=== May 2010-Sep 2011 ===<br />
<br />
*Operations Support [https://documents.egi.eu/document/155 metrics]<br />
<br />
=== Until April 2010 ===<br />
<br />
*EGEE-III Operations Support [https://documents.egi.eu/document/829 metrics]<br />
<br />
== Nagios tests ==<br />
<br />
*[[Operations:Operations tests|Operations tests list ]]: list of Nagios probes generating alarms for visualization in the Operations Dashboard <br />
*[http://grid-monitoring.cern.ch/myegi/sam-pi/metrics_in_profiles?vo_name=ops&profile_name=ROC_CRITICAL Availability and reliability tests list]: list of Nagios probes whose results are used for Availability and Reliability computation<br />
<br />
== OTAG topics ==<br />
<br />
=== Operational Portal: Dashboard ===<br />
<br />
*[http://bit.ly/dZ3RWN RT tickets] <br />
*[[Grid operations oversight/COD interaction with Dashboard team|COD interactions with Dashboard team (draft)]] <br />
*[[Grid operations oversight/COD OTAG topics|COD topics to be discussed on OTAG meeting]]<br />
<br />
=== GOC DB ===<br />
<br />
*[[Grid operations oversight/COD GOCDB requirements|Collection of GOC DB requirements regarding COD work (draft)]]<br />
<br />
== Pages in draft state ==<br />
<br />
*[[Grid operations oversight/COD Improvements to availability procedure|Improvements to Availability Calculation Procedure (draft)]]<br />
<br />
*[[Grid operations oversight/A/R fixing procedure|A/R fixing procedure (draft)]][[Grid operations oversight/ROD FAQ|<br>]]<br />
<br />
<br> <br />
<br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/Unknown_issue UNKNOWN issue ]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/Unknown_issue-internal UNKNOWN issue Internal ]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/ROD_performance_index ROD&nbsp;performance&nbsp;index]<br> <br />
*[https://wiki.egi.eu/wiki/Grid_operations_oversight/CandidateSuspendedSitesList Candidate Suspended Sites List]<br />
<br />
[[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=Underperforming_sites_and_suspensions&diff=32585Underperforming sites and suspensions2012-02-09T09:53:34Z<p>Mkrakowi: </p>
<hr />
<div>{{Template:Op menubar}} {{TOC_right}} <br />
<br />
Information about underperforming and suspended Resource Centres is provided in the table below. <br />
<br />
{| align="center" cellspacing="0" cellpadding="5" border="1"<br />
|-<br />
! date <br />
! GGUSID <br />
! nb. sites <br />
below 75%/70% targets <br />
<br />
! nb. sites <br />
below the target for 3 months <br />
<br />
! nb. sites <br />
which didn't provided explanation <br />
<br />
*site name, NGI/ROC, GGUS ID<br />
<br />
! nb. sites <br />
suspended by COD <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
! nb. sites <br />
suspended by CSIRT <br />
<br />
*site name, NGI/ROC, short reason, GGUS ID<br />
<br />
|-<br />
| January 2012 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=79020 79020] <br />
| 30<br />
| 3 <br />
| <br />
| <br />
| <br />
|-<br />
| December 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=78040 78040] <br />
| 28 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| <br />
|-<br />
| November 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=77170 77170] <br />
| 26 <br />
| 3 <br />
| 0<br> <br />
| 0<br> <br />
| <br />
|-<br />
| October 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=76305 76305] <br />
| 45 <br />
| 3 <br />
| <br />
3<br> <br />
<br />
*ROC_Russia/RRC-KI, 76408 <br />
*NGI_IL/WEIZMANN-LCG2, 76386 <br />
*NGI_IL/TECHNION-HEP, 76384<br />
<br />
| <br />
1<br> <br />
<br />
*NGI_ARMGRID/AM-04-YERPHI,76428<br />
<br />
| <br />
|-<br />
| September 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74965 74965] <br />
| 25 <br />
| 6 <br />
| 0 <br />
| <br />
2<br> <br />
<br />
*ROC_Asia/Pacific/TW-NCUHEP, 3 consecutive months below the target (site suspended by ROC), #75041<br> <br />
*ROC_Asia/Pacific/IN-DAE-VECC-02, 4 consecutive months below the target (site suspended by COD), #75040<br />
<br />
| <br />
|-<br />
| August 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=74147 74147] <br />
| 31 <br />
| 3 <br />
| 0 <br />
| 0 <br />
| <br />
|-<br />
| July 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=73193 73193] <br />
| 35 <br />
| 4 <br />
| 0 <br />
| <br />
2 <br />
<br />
*ROC_Asia/Pacific/TW-eScience, 3 consecutive months below the target(site suspended by ROC), ticket #73539<br> <br />
*ROC_Asia/Pacific/TW-NYMU-GRID,3 consecutive months below the target(site suspended by ROC), ticket #73540<br />
<br />
| <br />
|-<br />
| June 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=72259 72259] <br />
| 31 <br />
| 8 <br />
| 0 <br />
| 5 <br />
*ROC_Asia, Pacific/PH-ASTI-LIKNAYAN, 3 consecutive months below target, ticket #72435 <br />
*ROC_Asia, Pacific/TH-HAI, 3 consecutive months below target, #72436 <br />
*NGI_IBERGRID, UOGRID, 3 consecutive months below target, #72439 <br />
*ROC_IGALC, CEFET-RJ, 3 consecutive months below target, #72440 <br />
*ROC_IGALC, LA-MERIDA, 3 consecutive months below target, #72441<br />
<br />
| <br><br />
|-<br />
| May 2011 <br />
| [https://ggus.eu/ws/ticket_info.php?ticket=71643 71643] <br />
| 23 <br />
| <br />
4 <br />
<br />
this month first time targed was changed to ava 70% rel 75% <br />
<br />
| 0 <br />
| 2 <br />
*UOGRID, NGI_IBERGRID, below 50%/50% for three months, 71787 <br />
*PH-ASTI-LIKNAYAN, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 71789&nbsp;<br />
<br />
| <br><br />
|-<br />
| April 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=70289 70289] <br />
| 39 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| <br><br />
|-<br />
| March 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=69629 69629] <br />
| 30 <br />
| 0 <br />
| <br />
1 <br />
<br />
*ru-Moscow-SINP-LCG2, ROC_Russia, 69765<br><br />
<br />
| 0 <br />
| <br><br />
|-<br />
| February 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=68299 68299] / See also [https://gus.fzk.de/ws/ticket_info.php?ticket=68229 68229] <br />
| 28 <br />
| 0 <br />
| 1 <br />
*RU-SPbSU, ROC_Russia<br />
<br />
| <br> <br />
| <br><br />
|-<br />
| Jan 2011 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=67008 67008] <br />
| 27 <br />
| 2 <br />
| 1 <br />
*ru-IMPB-LCG2,ROC_Russia, 67038<br />
<br />
| 2 <br />
*MY-UM-PANG5, ROC_Asia/Pacific, below 50%/50% for three months(site suspended by ROC), 67010 <br />
*ru-IMPB-LCG2,ROC_Russia, sites didn't provided explanation,67038<br />
<br />
| <br><br />
|-<br />
| Dec 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=65971 65971] <br />
| 30 <br />
| 0 <br />
| 0 <br />
| 0 <br />
| <br><br />
|-<br />
| Nov 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=64892 64892] <br />
| 40 <br />
| 1 <br />
| 0 <br />
| 1 <br />
*ID-ITB, ROC_Asia/Pacific,below 50%/50% for three months (site suspended by ROC),64951<br />
<br />
| <br><br />
|-<br />
| Oct 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=63658 63658] <br />
| 37 <br />
| 4 <br />
| 1 <br />
*AM-04-YERPHI, NGI_ARMGRID, 63854<br />
<br />
| 2 <br />
*AM-01-IIAP-NAS-RA, NGI_ARMGRID, below 50%/50% for three months, 63837 <br />
*AM-04-YERPHI, NGI_ARMGRID, no explanation given, 63854<br />
<br />
| <br><br />
|-<br />
| Sep 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=62853 62853] <br />
| 39 <br />
| 2 <br />
| 0 <br />
| 0 <br />
| <br><br />
|-<br />
| Aug 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61797 61797] <br />
| 43 <br />
| 3 <br />
| 10 <br />
*JP-HIROSHIMA-WLCG, ROC AP, 62323 <br />
*AU-PPS, ROC AP,62316 <br />
*MY-UTM-GRID, ROC AP, 62312 <br />
*TH-NECTEC-LSR, ROC AP, 62304 <br />
*MY-UM-CRYSTAL, ROC AP, 62300 <br />
*ID-ITB, ROC AP, 62296 <br />
*GRISU-COMETA-INFN-LNS, ROC Italy, 62314 <br />
*UNIGE-DPNC, NGI_NDGF, 62308 <br />
*ru-IMPB-LCG2, ROC_Russia, 62305 <br />
*IL-TAU-HEP,ROC_SE, 62306<br />
<br />
| 1 <br />
*TW-NCUHEP, ROC AP, below 50%/50% for three months, 62340<br />
<br />
| <br><br />
|-<br />
| Jul 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=61115 61115] <br />
| 47 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| <br><br />
|-<br />
| Jun 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=60216 60216] <br />
| 59 <br />
| 4 <br />
| 0 <br />
| 0 <br />
| <br><br />
|-<br />
| May 2010 <br />
| [https://gus.fzk.de/ws/ticket_info.php?ticket=59736 59736] <br />
| 38 <br />
| 3 <br />
| 1 <br />
*ru-Chernogolovka-IPCP-LCG2, ROC RU, 59819<br />
<br />
| 0 <br />
| <br><br />
|}<br />
<br />
[[Category:Service_Level_Management]] [[Category:COD]]</div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=32352EGI-InSPIRE:Poland-QR72012-02-06T13:41:51Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| &nbsp;The Netherlands <br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br><br />
|-<br />
| 3-4/11/2011 <br />
| &nbsp; The Netherlands <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br><br />
|-<br />
| 23-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| OMB <br />
| 1 <br />
| <br><br />
|-<br />
| 26-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br><br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, USA <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE probes testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in regional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
#'''Stage rollout components tested''' <br />
##UNICORE:&nbsp;UNICORE Gateway, UVOS <br />
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: <br />
###NGI_PL_SERVICES - contains NGI_PL core services<br> <br />
###ICM - contains QCG&nbsp;and UNICORE services <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF<br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. All the services are registerd in GOC&nbsp;DB.<br />
</span></span> <br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=32351EGI-InSPIRE:Poland-QR72012-02-06T13:41:33Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| &nbsp;The Netherlands<br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br><br />
|-<br />
| 3-4/11/2011 <br />
| &nbsp; The Netherlands <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br><br />
|-<br />
| 23-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| OMB <br />
| 1 <br />
| <br><br />
|-<br />
| 26-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br><br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, USA <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE probes testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in regional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
#'''Stage rollout components tested''' <br />
##UNICORE:&nbsp;UNICORE Gateway, UVOS <br />
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: <br />
##NGI_PL_SERVICES - contains NGI_PL core services<br><br />
##ICM - contains QCG&nbsp;and UNICORE services <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF<br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" class="short_text" id="result_box"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" class="short_text" id="result_box"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. All the services are registerd in GOC&nbsp;DB.<br />
</span></span><br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=32302EGI-InSPIRE:Poland-QR72012-02-06T13:13:52Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| &nbsp;The Netherlands<br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br><br />
|-<br />
| 3-4/11/2011 <br />
| &nbsp; The Netherlands <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br><br />
|-<br />
| 23-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| OMB <br />
| 1 <br />
| <br><br />
|-<br />
| 26-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br><br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, USA <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE probes testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in regional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
#'''Stage rollout components tested''' <br />
##UNICORE:&nbsp;UNICORE Gateway, UVOS <br />
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: NGI_PL_SERVICES <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF<br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" class="short_text" id="result_box"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" class="short_text" id="result_box"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. All the services are registerd in GOC&nbsp;DB.<br />
</span></span><br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=32299EGI-InSPIRE:Poland-QR72012-02-06T13:10:46Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| &nbsp;The Netherlands<br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br><br />
|-<br />
| 3-4/11/2011 <br />
| &nbsp; The Netherlands <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br><br />
|-<br />
| 23-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| OMB <br />
| 1 <br />
| <br><br />
|-<br />
| 26-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br><br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, USA <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE probes testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in regional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
#'''Stage rollout components tested''' <br />
##UNICORE:&nbsp;UNICORE Gateway, UVOS <br />
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: NGI_PL_SERVICES<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF<br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All the biggest sites (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" class="short_text" id="result_box"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" class="short_text" id="result_box"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. All the services are registerd in GOC&nbsp;DB.<br />
</span></span><br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=32297EGI-InSPIRE:Poland-QR72012-02-06T13:07:46Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| &nbsp;The Netherlands<br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br><br />
|-<br />
| 3-4/11/2011 <br />
| &nbsp; The Netherlands <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br><br />
|-<br />
| 23-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| OMB <br />
| 1 <br />
| <br><br />
|-<br />
| 26-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br><br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, USA <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE probes testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in regional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
#'''Stage rollout components tested''' <br />
##UNICORE:&nbsp;UNICORE Gateway, UVOS <br />
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: NGI_PL_SERVICES<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF<br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All biggest sties (CYFRONET-LCG2, PSNC, WCSS, TASK, WARSAW-EGEE) in NGI_PL support a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. </span></span><br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=32296EGI-InSPIRE:Poland-QR72012-02-06T13:07:06Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| &nbsp;The Netherlands<br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br><br />
|-<br />
| 3-4/11/2011 <br />
| &nbsp; The Netherlands <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br><br />
|-<br />
| 23-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| OMB <br />
| 1 <br />
| <br><br />
|-<br />
| 26-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br><br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, USA <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE probes testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in regional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
#'''Stage rollout components tested''' <br />
##UNICORE:&nbsp;UNICORE Gateway, UVOS <br />
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: NGI_PL_SERVICES<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF<br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
All biggest sties in NGI_PL support a <span lang="en" class="short_text" id="result_box"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" class="short_text" id="result_box"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. </span></span><br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=32293EGI-InSPIRE:Poland-QR72012-02-06T13:06:11Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| &nbsp;The Netherlands<br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br><br />
|-<br />
| 3-4/11/2011 <br />
| &nbsp; The Netherlands <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br><br />
|-<br />
| 23-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| OMB <br />
| 1 <br />
| <br><br />
|-<br />
| 26-24/01/2012 <br />
| &nbsp; The Netherlands <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br><br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, USA <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--><br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE probes testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in regional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
#'''Stage rollout components tested''' <br />
##UNICORE:&nbsp;UNICORE Gateway, UVOS <br />
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: NGI_PL_SERVICES<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF<br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
We support and introduce a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. </span></span> <br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=32004EGI-InSPIRE:Poland-QR72012-02-03T11:23:56Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| Holand <br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br />
|-<br />
| 3-4/11/2011 <br />
| Holand <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br />
|-<br />
| 23-24/01/2012 <br />
| Holand <br />
| OMB <br />
| 1 <br />
| <br />
|-<br />
| 26-24/01/2012 <br />
| Holand <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, USA <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE probes testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in regional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
#'''Stage rollout components tested''' <br />
##UNICORE:&nbsp;UNICORE Gateway, UVOS <br />
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: NGI_PL_SERVICES<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF<br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
We support and introduce a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. </span></span> <br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=32003EGI-InSPIRE:Poland-QR72012-02-03T11:22:23Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| Holand <br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br />
|-<br />
| 3-4/11/2011 <br />
| Holand <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br />
|-<br />
| 23-24/01/2012 <br />
| Holand <br />
| OMB <br />
| 1 <br />
| <br />
|-<br />
| 26-24/01/2012 <br />
| Holand <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, USA <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE&nbsp;tests testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in reglional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
#'''Stage rollout components tested''' <br />
##UNICORE:&nbsp;UNICORE Gateway, UVOS <br />
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: NGI_PL_SERVICES<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF<br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
We support and introduce a <span lang="en" id="result_box" class="short_text"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" id="result_box" class="short_text"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. </span></span> <br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=31989EGI-InSPIRE:Poland-QR72012-02-03T10:25:46Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| Holand <br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br />
|-<br />
| 3-4/11/2011 <br />
| Holand <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br />
|-<br />
| 23-24/01/2012 <br />
| Holand <br />
| OMB <br />
| 1 <br />
| <br />
|-<br />
| 26-24/01/2012 <br />
| Holand <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, Stany Zjednoczone Ameryki Północnej <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE&nbsp;tests testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in reglional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
#'''Stage rollout components tested''' <br />
##UNICORE:&nbsp;UNICORE Gateway, UVOS <br />
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: NGI_PL_SERVICES<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br> <br />
##Federated Clouds TF<br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
We support and introduce a <span lang="en" class="short_text" id="result_box"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" class="short_text" id="result_box"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. </span></span><br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=31988EGI-InSPIRE:Poland-QR72012-02-03T10:24:07Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| Holand <br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br />
|-<br />
| 3-4/11/2011 <br />
| Holand <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br />
|-<br />
| 23-24/01/2012 <br />
| Holand <br />
| OMB <br />
| 1 <br />
| <br />
|-<br />
| 26-24/01/2012 <br />
| Holand <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, Stany Zjednoczone Ameryki Północnej <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE&nbsp;tests testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in reglional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase.<br />
#'''Stage rollout components tested'''<br />
##UNICORE:&nbsp;UNICORE Gateway, UVOS <br />
##GLITE:&nbsp;EMI.apel, EMI.cream, EMI.dpm <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: NGI_PL_SERVICES<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br><br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
We support and introduce a <span lang="en" class="short_text" id="result_box"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" class="short_text" id="result_box"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. </span></span><br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=31984EGI-InSPIRE:Poland-QR72012-02-03T10:06:29Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| Holand <br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br />
|-<br />
| 3-4/11/2011 <br />
| Holand <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br />
|-<br />
| 23-24/01/2012 <br />
| Holand <br />
| OMB <br />
| 1 <br />
| <br />
|-<br />
| 26-24/01/2012 <br />
| Holand <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, Stany Zjednoczone Ameryki Północnej <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE&nbsp;tests testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in reglional helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and suggesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
##Stage rollout components testing:&nbsp;UNICORE Gateway, UVOS <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for calculation RP availability and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decommission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: NGI_PL_SERVICES<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br><br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
We support and introduce a <span lang="en" class="short_text" id="result_box"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" class="short_text" id="result_box"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. </span></span><br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowihttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Poland-QR7&diff=31982EGI-InSPIRE:Poland-QR72012-02-03T09:50:10Z<p>Mkrakowi: </p>
<hr />
<div>__NOTOC__ <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Quarterly Report Number <br />
! scope="col" | NGI Name <br />
! scope="col" | Partner Name <br />
! scope="col" | Author<br />
|-<br />
| 7 <br />
| NGI_PL <br />
| CYFRONET <br />
| Małgorzata Krakowian<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--> <br />
<br />
==1. MEETINGS AND DISSEMINATION == <!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. Otherwise put: “-“<br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note: Complete the tables below by adding as many rows as needed. <br />
Note: Complete the tables below by adding as many rows as needed. --> <br />
<br />
=== 1.1. CONFERENCES/WORKSHOPS ORGANISED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | Date <br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 4-7.01.2012 <br />
| Zakopane, Poland <br />
| Grid Computing - The Next Decade <br />
| 47 <br />
| <br />
https://gridlab.man.poznan.pl/Meetings/Zakopane2012/indexman.html <br />
<br />
|}<br />
<br />
=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED ===<br />
<br />
{| cellspacing="0" border="1"<br />
|-<br />
! scope="col" | <br />
Date <br />
<br />
! Location <br />
! Title <br />
! Participants <br />
! Outcome (Short report &amp; Indico URL)<br />
|-<br />
| 9-10/11/2011 <br />
| Holand <br />
| NGI Coordinators Kick Off meeting <br />
| 1 <br />
| <br />
|-<br />
| 3-4/11/2011 <br />
| Holand <br />
| Projekt Managment Board <br> EGI-Inspire <br />
| 1 <br />
| <br />
|-<br />
| 23-24/01/2012 <br />
| Holand <br />
| OMB <br />
| 1 <br />
| <br />
|-<br />
| 26-24/01/2012 <br />
| Holand <br />
| PMB EGI-INSPIRE <br />
| 1 <br />
| <br />
|-<br />
| 12-18/11/2011 <br />
| Seattle, Stany Zjednoczone Ameryki Północnej <br />
| Supercomputing 11 <br />
| 1 <br />
| http://sc11.supercomputing.org<br />
|}<br />
<br />
<!--<br />
Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:<br />
|<Date>||<Location>||Title||Participants||Outcome <br />
|-<br />
--> <br />
<br />
===1.3. PUBLICATIONS=== <!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--> <br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Publication title <br />
! Journal / Proceedings title <br />
! align="left" | Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to'' <br />
! align="left" | Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|}<br />
<br />
== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> <br />
<br />
=== 2.1. Progress Summary ===<br />
<br />
#'''Nagios''' <br />
##Production instance: Actualization to version SAM15 <br />
##Testing instance: Actualization to version SAM15 and UNICORE&nbsp;tests testing<br> <br />
#<span style="font-weight: bold;">Regional Helpdesk</span> <br />
##Moving to more automatized process of handling tickets in regliona helpdesk.<br> <br />
#'''Unicore''' <br />
##Monitoring: testing, debugging and sugesting SAM fixes related to UNICORE. Refactoring of UNICORE&nbsp;configuration module for SAM. <br />
##Accounting:&nbsp;Integration with APEL enters testing phase. <br />
##Stage rollout components testing:&nbsp;UNICORE Gateway, UVOS <br />
#'''Availability/Reliability metrics''' <br />
##NGI_PL metrics:&nbsp; November 96%, December 99%; All sites above the targets. <br />
##BDII metrics: November 99%, December 100%; <br />
#'''NGI_PL security team ''' <br />
##Incident response and investigation for security incident at Cyfronet, EGI CSIRT incident id: EGI-20111231-01 <br />
##Regular operational actions within EGI CSIRT IRTF <br />
##Taking part in weekly and monthly meetings of EGI CSIRT <br />
##Removing critical vulnerabilities in IFJ-PAN-BG, including checking whole site infrastructure <br />
##Performing security pentesting for WUT site <br />
##Submission of 1 vulnerability to EGI SVG <br />
##Delegating participant to D4.4 "Security Risk Assessment of the EGI Infrastructure" <br />
#'''ROD&nbsp;NGI_PL''' <br />
##Coordination of lcg-CE decommission within NGI <br />
##Creation of NGI_PL_SERVICES site, designed for caluculation RP availablity and reliability metrics <br />
##ROD&nbsp;team didn't exceed ROD&nbsp;performance index target&nbsp; <br />
#'''Changes on sites ''' <br />
##CYFRONET-LCG2 <br />
###Decomission of lcg-CE <br />
###Upgrade of DPM<br> <br />
###New services:&nbsp; <br />
####cream02.grid - CREAMCE&nbsp; UMD<br> <br />
####wms01.grid&nbsp;&nbsp;&nbsp; - WMS EMI<br> <br />
####myproxy02.grid - MYPROXY&nbsp;UMD <br />
##WCSS-PPS <br />
###Migration from gLite 3.2 to UMD 1.0 <br />
###Moving Site-BDII from CREAM to new host<br> <br />
##PSNC <br />
###New services: UNICORE<br> <br />
##TASK <br />
###New services: UNICORE, CREAM-CE<br> <br />
###New hardware: new cluster Galera Plus (192 nodes, each 12-cores), vSMP machine <br />
##WARSAW_EGEE <br />
###Actualization of unicore-gateway to version 4.2.0 and uvos-server to version 1.5.0 <br />
###New services: QosCosGrid <br />
###New hardware: 12 TFPS <br />
##New site certified: NGI_PL_SERVICES<br> <br />
#'''Task forces in which NGI_PL&nbsp;participate''' <br />
##Regionalisation TF <br />
##UNICORE Integration TF<br><br />
<br />
=== 2.2. Main Achievements ===<br />
<br />
We support and introduce a <span lang="en" class="short_text" id="result_box"><span class="hps">wide range of middlewares (glite, UNICORE, QCG) to </span></span><span lang="en" class="short_text" id="result_box"><span class="hps">adapt to the</span> <span class="hps">demands and</span> <span class="hps">needs of users. </span></span><br />
<br />
=== 2.3. Issues and mitigation ===<br />
<br />
{| cellspacing="0" cellpadding="2" border="1"<br />
|-<br />
! scope="col" | Issue Description <br />
! scope="col" | Mitigation Description<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Mkrakowi