Agenda-09-10-2017

From EGIWiki
Jump to: navigation, search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators


Contents

General information

Middleware

UMD/CMD

Preview repository

Released on 2017-09-22:

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


FedCloud

Feedback from Helpdesk

NTR

Monthly Availability/Reliability

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.

$ 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
$ 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
$ 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

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 February and 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:

EGI contacted these VOs to agree a smooth migration of their activities to DIRAC, only some of them replied till now:

We need the VO feedback for better defining technical details and timeline:

WMS servers can be decommissioned as soon as the supported VOs do not need them any more. The proposal is:

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

Decommissioning of dCache 2.10 and 2.13

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.

Several sites are publishing in the BDII the webdav endpoints:

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).

For registering on GOC-DB the webdav service endpoint, follow the HOWTO21 in order to filling in the proper information. In particular:

Storage accounting deployment

During the September meeting, OMB has approved the full-scale deployment of storage accounting. The APEL team 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 here.

PLEASE NOTE: as in a broadcast circulated on Oct 4th

AOB

Next meeting

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export