|
|
| Line 1: |
Line 1: |
| {{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}}
| | Date mask changed to YYYY-MM-DD, please refer to https://wiki.egi.eu/wiki/Agenda-2017-11-20 |
| [[Category:Grid Operations Meetings]]
| |
| | |
| = General information =
| |
| | |
| = Middleware =
| |
| | |
| == UMD/CMD ==
| |
| | |
| | |
| == Preview repository ==
| |
| | |
| Released on 2017-09-22:
| |
| * '''[[Preview 1.14.0]]''' [https://appdb.egi.eu/store/software/preview.repository/releases/1.0/1.14.0/ AppDB info] (sl6): ARC 15.03 update 16, CVMFS 2.4.1, DMLite 0.8.8, gfal2 2.14.2, gfal2-python 1.9.3, gfal2-utils 1.5.1, STORM 1.11.12, VOMS Admin 3.7.0, XRootD 4.7.0
| |
| * '''[[Preview 2.14.0]]''' [https://appdb.egi.eu/store/software/preview.repository/releases/2.0/2.14.0/ AppDB info] (CentOS 7): ARC 15.03 update 16, ARGUS 1.7.2, CVMFS 2.4.1, DMLite 0.8.8, gfal2 2.14.2, gfal2-python 1.9.3, gfal2-utils 1.5.1, UI 4.0.3, XRootD 4.7.0
| |
| | |
| '''IMPORTANT''': the latest version of Xrootd ( 4.7.0) has "broken" the xrdcp command towards dcache:
| |
| | |
| https://github.com/xrootd/xrootd/issues/593
| |
| | |
| The issue seems to be server side ( a missing field in the response which is now enforced by the client) and a fix will be provided in the upcoming Xrootd 4.7.1.
| |
| | |
| = Operations =
| |
| | |
| == ARGO/SAM ==
| |
| | |
| <br>
| |
| | |
| == FedCloud ==
| |
| | |
| == Feedback from Helpdesk ==
| |
| | |
| == Monthly Availability/Reliability ==
| |
| | |
| *Underperformed sites in the past A/R reports with issues not yet fixed:
| |
| ** '''AsiaPacific'''
| |
| ***TW-NCUHEP: undeperforming in the past months for a network issue with one of the nagios server, now it seems solved: https://ggus.eu/index.php?mode=ticket_info&ticket_id=128083
| |
| ***T2-TH-SUT: CAs upgraded, A/R figures are improving https://ggus.eu/index.php?mode=ticket_info&ticket_id=130558
| |
| **'''NGI_AEGIS''': https://ggus.eu/index.php?mode=ticket_info&ticket_id=130560
| |
| ***AEGIS04-KG: JobPurge probe is failing
| |
| **'''NGI_BG''': BG05-SUGrid Se put out of production https://ggus.eu/index.php?mode=ticket_info&ticket_id=130561
| |
| **'''NGI_DE''': https://ggus.eu/index.php?mode=ticket_info&ticket_id=130563
| |
| ***mainzgrid
| |
| **'''NGI_GRNET''': https://ggus.eu/index.php?mode=ticket_info&ticket_id=130565 QoS
| |
| **'''NGI_NL''': https://ggus.eu/index.php?mode=ticket_info&ticket_id=130567 QoS
| |
| *Underperformed sites after 3 consecutive months (July, August, September), underperformed NGIs, QoS violations:
| |
| **'''NGI_GRNET''': https://ggus.eu/index.php?mode=ticket_info&ticket_id=130908
| |
| ***HG-05-FORTH
| |
| *Suspended sites (in August): UA-IFBG, KR-UOS-SSCC
| |
| | |
| == New weights for the NGIs average A/R values, based on Computation Power ==
| |
| | |
| We would like to implement a new way for computing the weights for the NGIs average A/R values, introducing the concept of CE's "'''computation power'''":
| |
| computation power = hep-spec * LogicalCPUs
| |
| | |
| This is a quantity that can be addable up over the CEs of a site (and over the sites). Until now it has been simply added up the CEs hep-spec values for getting a site global value, but this is not correct, because the hep-spec refers to a particular CE (to the cluster behind that particular CE) and it is not addable up.
| |
| That is why, first of all, we asked VAPOR to implement the "computation power" as well as the site/NGI "average hep-spec". Have a look for example at the "figures" section: http://operations-portal.egi.eu/vapor/resources/GL2ResSummary
| |
| | |
| In the ARGO development instance the new weights have been used for computing the September average A/R values: http://web-egi-devel.argo.grnet.gr/lavoisier/ngi_reports?accept=html
| |
| | |
| We made a comparison between the values and the official ones: http://argo.egi.eu/lavoisier/ngi_reports?accept=html
| |
| | |
| As expected, there were some improvements and some worsening, perhaps more accentuated in the case of NGIs with few sites; with the new way the sites providing more than one CE (either with the same or different hep-spec) weight less than before (in the good and in the evil), because we compute an average hep-spec, not a simple sum over the benchmark values.
| |
| Moreover several sites are still missing the necessary information for computing the weights in both the methods: check on VAPOR the values published by your sites in order to properly publishing in the GLUE2 schema the number of logical CPUs and the Hep-Spec06 benchmark.
| |
| | |
| *'''Example of ldap query for checking if a site is publishing the HepSpec-06 benchmark''':
| |
| | |
| $ ldapsearch -x -LLL -H ldap://egee-bdii.cnaf.infn.it:2170 -b "GLUE2DomainID=pic,GLUE2GroupID=grid,o=glue" '(&(objectClass=GLUE2Benchmark)(GLUE2BenchmarkType=hep-spec06))'
| |
|
| |
| dn: GLUE2BenchmarkID=ce07.pic.es_hep-spec06,GLUE2ResourceID=ce07.pic.es,GLUE2ServiceID=ce07.pic.es_ComputingElement,GLUE2GroupID=resource,GLUE2DomainID=pic,GLUE2GroupID=grid,o=glue
| |
| GLUE2BenchmarkExecutionEnvironmentForeignKey: ce07.pic.es
| |
| GLUE2BenchmarkID: ce07.pic.es_hep-spec06
| |
| GLUE2BenchmarkType: hep-spec06
| |
| objectClass: GLUE2Entity
| |
| objectClass: GLUE2Benchmark
| |
| GLUE2BenchmarkValue: 12.1205
| |
| GLUE2EntityOtherInfo: InfoProviderName=glite-ce-glue2-benchmark-static
| |
| GLUE2EntityOtherInfo: InfoProviderVersion=1.1
| |
| GLUE2EntityOtherInfo: InfoProviderHost=ce07.pic.es
| |
| GLUE2BenchmarkComputingManagerForeignKey: ce07.pic.es_ComputingElement_Manager
| |
| GLUE2EntityName: Benchmark hep-spec06
| |
| GLUE2EntityCreationTime: 2017-06-20T16:50:48Z
| |
|
| |
| dn: GLUE2BenchmarkID=ce01.pic.es_hep-spec06,GLUE2ResourceID=ce01.pic.es,GLUE2ServiceID=ce01.pic.es_ComputingElement,GLUE2GroupID=resource,GLUE2DomainID=pic,GLUE2GroupID=grid,o=glue
| |
| GLUE2BenchmarkExecutionEnvironmentForeignKey: ce01.pic.es
| |
| GLUE2BenchmarkID: ce01.pic.es_hep-spec06
| |
| GLUE2BenchmarkType: hep-spec06
| |
| objectClass: GLUE2Entity
| |
| objectClass: GLUE2Benchmark
| |
| GLUE2BenchmarkValue: 13.4856
| |
| GLUE2EntityOtherInfo: InfoProviderName=glite-ce-glue2-benchmark-static
| |
| GLUE2EntityOtherInfo: InfoProviderVersion=1.1
| |
| GLUE2EntityOtherInfo: InfoProviderHost=ce01.pic.es
| |
| GLUE2BenchmarkComputingManagerForeignKey: ce01.pic.es_ComputingElement_Manager
| |
| GLUE2EntityName: Benchmark hep-spec06
| |
| GLUE2EntityCreationTime: 2017-09-05T07:34:26Z
| |
| | |
| *'''Example of ldap query for getting the number of LogicalCPUs published by an ARC-CE (due to a bug in te info-provider, CREAM-CE publish the total number under the ExecutionEnvironment class)''':
| |
| $ ldapsearch -x -LLL -H ldap://egee-bdii.cnaf.infn.it:2170 -b "GLUE2DomainID=UA_ILTPE_ARC,GLUE2GroupID=grid,o=glue" 'objectClass=GLUE2ComputingManager' GLUE2ComputingManagerTotalLogicalCPUs
| |
|
| |
| dn: GLUE2ManagerID=urn:ogf:ComputingManager:ds4.ilt.kharkov.ua:pbs,GLUE2ServiceID=urn:ogf:ComputingService:ds4.ilt.kharkov.ua:arex,GLUE2GroupID=services,GLUE2DomainID=UA_ILTPE_ARC,GLUE2GroupID=grid,o=glue
| |
| GLUE2ComputingManagerTotalLogicalCPUs: 168
| |
| | |
| *'''Example of ldap query for getting the number of LogicalCPUs published by a CREAM-CE''':
| |
| $ ldapsearch -x -LLL -H ldap://egee-bdii.cnaf.infn.it:2170 -b "GLUE2DomainID=UKI-SOUTHGRID-SUSX,GLUE2GroupID=grid,o=glue" 'objectClass=GLUE2ExecutionEnvironment' GLUE2ExecutionEnvironmentLogicalCPUs
| |
| GLUE2ExecutionEnvironmentPhysicalCPUs GLUE2ExecutionEnvironmentTotalInstances
| |
|
| |
| dn: GLUE2ResourceID=grid-cream-02.hpc.susx.ac.uk,GLUE2ServiceID=grid-cream-02.hpc.susx.ac.uk_ComputingElement,GLUE2GroupID=resource,GLUE2DomainID=UKI-SOUTHGRID-SUSX,GLUE2GroupID=grid,o=glue
| |
| GLUE2ExecutionEnvironmentTotalInstances: 71
| |
| GLUE2ExecutionEnvironmentLogicalCPUs: 568
| |
| GLUE2ExecutionEnvironmentPhysicalCPUs: 71
| |
| | |
| * Manual for [[HEP SPEC06|Hepspec06 benchmark]].
| |
| | |
| '''In November the new way will be moved in production, so if during October many sites fix the information, the new NGIs A/R average values will improve'''.
| |
| | |
| == Decommissioning EMI WMS ==
| |
| | |
| As discussed at the [https://indico.egi.eu/indico/event/3234/ February] and [https://indico.egi.eu/indico/event/3237/ April/May] OMBs, we are making plans for decommissioning the WMS and moving to DIRAC.
| |
| | |
| NGIs provided WMS usage statistics, and in general the usage is relatively low, mainly for local testing
| |
| | |
| Moderate usage by few VOs:
| |
| | |
| *NGI_CZ: eli-beams.eu
| |
| *NGI_GRNET: see
| |
| *NGI_IT: calet.org, compchem, theophys, virgo
| |
| *NGI_PL: gaussian, vo.plgrid.pl, vo.nedm.cyfronet
| |
| *NGI_UK: mice, t2k.org
| |
| | |
| EGI contacted these VOs to agree a smooth migration of their activities to DIRAC, only some of them replied till now:
| |
| | |
| *compchem is already testing DIRAC
| |
| *calet.org: discussing with the users the migration to DIRAC. Interested in a webinar on DIRAC.
| |
| *mice: enabled on the GridPP DIRAC server
| |
| | |
| We need the VO feedback for better defining technical details and timeline:
| |
| | |
| *NGIs with VOs using WMS (not necessarily limited to the VOs above), please contact them to ensure that these VOs have a back-up plan.
| |
| | |
| WMS servers can be decommissioned as soon as the supported VOs do not need them any more. The proposal is:
| |
| | |
| *'''WMS will be removed from production starting from 1st January 2018'''.
| |
| **VOs have '''3 months''' to find alternatives or migrate to DIRAC
| |
| *Considering that this is not an update, the decommission can be performed in few weeks.
| |
| | |
| '''2017-08-21 UPDATE''': eli-beams.eu is interested in testing DIRAC; the process for enabling the VO on te DIRAC4EGI server has started.
| |
| | |
| == IPv6 readiness plans ==
| |
| | |
| **'''Resource Centres: assess the IPv6 readiness of the site infrastructure (real machines, cloud managers)'''
| |
| ***'''NGIs/ROCs please start discussing with sites and provide suggestions for the overall plan'''
| |
| | |
| == Decommissioning of dCache 2.10 and 2.13 ==
| |
| | |
| *support for the '''dCache 2.10''' ended at December 2016, tickets opened by EGI Operations to track decommissioning
| |
| ** still left: CA-ALBERTA-WESTGRID-T2, CA-TRIUMF-T2K
| |
| *'''decommissioning campaign started by EGI Operations''' http://go.egi.eu/decommdcache213
| |
| ** still left: CA-VICTORIA-WESTGRID-T2, UNI-FREIBURG, CA-SCINET-T2, INFN-ROMA1-CMS
| |
| | |
| == webdav probes in production ==
| |
| | |
| The webdav probes have been deployed in production. Some sites have already enablied the monitoring of their webdav endpoints: CYFRONET-LCG2, egee.irb.hr, GRIF, IGI-BOLOGNA, NCG-INGRID-PT, SARA-MATRIX, UKI-NORTHGRID-LIV-HEP, UNI-BONN.
| |
| | |
| *webdav endpoints registered in GOC-DB: https://goc.egi.eu/gocdbpi/public/?method=get_service&&service_type=webdav
| |
| *link to nagios results: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_webdav&style=detail
| |
| | |
| Several sites are publishing in the BDII the webdav endpoints:
| |
| *'''AsiaPacific''': JP-KEK-CRC-02
| |
| *'''NGI_AEGIS''': AEGIS01-IPB-SCL
| |
| *'''NGI_CH''': UNIGE-DPNC, UNIBE-LHEP
| |
| *'''NGI_DE''': UNI-SIEGEN-HEP
| |
| *'''NGI_GRNET''': GR-01-AUTH, HG-03-AUTH
| |
| *'''NGI_HR''': egee.irb.hr, egee.srce.hr
| |
| *'''NGI_IBERGRID''': CETA-GRID, IFIC-LCG2, NCG-INGRID-PT
| |
| *'''NGI_FRANCE''': GRIF-IPNO, GRIF-LAL, GRIF-LPNHE
| |
| *'''NGI_IL''': IL-TAU-HEP, TECHNION-HEP, WEIZMANN-LCG2
| |
| *'''NGI_IT''': IGI-BOLOGNA, INFN-GENOVA, INFN-MILANO-ATLASC, INFN-ROMA3, INFN-T1
| |
| *'''NGI_PL''': CYFRONET-LCG2, WUT
| |
| *'''NGI_UK''': UKI-NORTHGRID-LIV-HEP, UKI-NORTHGRID-MAN-HEP
| |
| *'''ROC_CANADA''': CA-MCGILL-CLUMEQ-T2
| |
| | |
| Checked with:
| |
| | |
| $ ldapsearch -x -LLL -H ldap://egee-bdii.cnaf.infn.it:2170 -b "GLUE2GroupID=grid,o=glue" '(&(objectClass=GLUE2Endpoint)(GLUE2EndpointInterfaceName=webdav))' GLUE2EndpointImplementationName GLUE2EndpointURL
| |
| | |
| '''ACTIONS for NGIs and sites''':
| |
| EGI Operations is going to open GGUS tickets asking the sites to enable the monitoring of their webdav endpoints (after verifying that the protocol is really provided).
| |
| *The webdav service endpoint should be registered in GOC-DB for being properly monitored: '''the nagios probes are executed using the VO ops''', so please ensure that the protocol is enabled for ops VO as well
| |
| *the webdav probes are harmless: they are not in any critical profile, they don't raise any alarm in the operations dashboard, and the A/R figures are not affected. We need time and more sites for gathering statistics on their results before making them critical.
| |
| | |
| For registering on GOC-DB the webdav service endpoint, follow the [[HOWTO21]] in order to filling in the proper information. '''In particular''':
| |
| *register a new service endpoint, separated from the SRM one;
| |
| * on GOC-DB fill in the webdav URL containing also the VO ops folder, for example: https://darkstorm.cnaf.infn.it:8443/webdav/ops or https://hepgrid11.ph.liv.ac.uk/dpm/ph.liv.ac.uk/home/ops/
| |
| ** it corresponds to the value of GLUE2 attribute GLUE2EndpointURL (containing the used port and without the VO folder);
| |
| * verify that the webdav url (for example: https://darkstorm.cnaf.infn.it:8443/webdav ) is properly accessible.
| |
| | |
| == Storage accounting deployment ==
| |
| | |
| During the [https://indico.egi.eu/indico/event/3241/ September meeting], OMB has approved the full-scale deployment of storage accounting. The APEL team [[Storage accounting testing|has tested it with a group of early adopters sites]], and the results prove that storage accounting is now production-ready.
| |
| | |
| Storage accounting is currently supported '''only for the DPM and dCache storage elements''' therefore only the resource centres deploying these kind of storage elements are requested to publish storage accounting data.
| |
| | |
| In order to properly install and configure the storage accounting scripts, please follow the instructions reported in the wiki: https://wiki.egi.eu/wiki/APEL/Storage
| |
| | |
| After setting up a daily cron job and running the accounting software, look for your data in the Accounting Portal: http://accounting-devel.egi.eu/storage.php. If it does not appear within 24 hours, or there are other errors, please open a GGUS ticket to APEL who will help debug the process.
| |
| | |
| Please enable on your resources the storage accounting '''by Oct 30th''': after this day, EGI Operations will open a GGUS ticket to all RCs that haven't started the deployment yet.
| |
| | |
| List of sites already publishing is '''[[Storage accounting deployment|here]]'''.
| |
| | |
| '''PLEASE NOTE''': as in a broadcast circulated on Oct 4th
| |
| *There is currently an issue affecting the display of storage accounting data in the Accounting Portal.
| |
| *Records are being received and loaded at the Accounting Repository and will appear in the Portal once the issue is resolved, so for the moment please only raise tickets if you have errors appearing in your logs.
| |
| | |
| = AOB =
| |
| | |
| == Next meeting ==
| |
| | |
| *'''Nov 13th, 2017''' https://indico.egi.eu/indico/event/3354/
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.