Agenda-2019-04-15

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


General information

Middleware

CREAM End Of Support Notice

Preview repository

  • released on 2019-03-28

Operations

ARGO/SAM

FedCloud

Feedback from DMSU

Notifications from ARGO about the nagios probes failures

In the process of implementing the notification system in ARGO, it was introduced the following changes in GOC-DB:

  • Notifications flag at the site level
  • Notifications flag at the service endpoint level

In this way ARGO will retrieve from GOC-DB the information about the sites and services whom sending the email notification and the related recipients.

The logic of the notifications is the following:

Site Service Notify?
Y Y Y
Y N N
N Y N
N N N

If there isn't any email contact defined at the service endpoint level, it will be used the site contact. Please review your contacts.

You can enable the notifications.

NOTE: It is not mandatory for the sites

Monthly Availability/Reliability

suspended sites: AEGIS04-KG

IPv6 readiness plans

LCGDM end of support and migration to / enabling of DOME

  • on Jun 1st 2019 the support to DPM Legacy (LCGDM) is going to end
  • since DPM 1.10.3 release, it is possible enabling the non-legacy mode DOME (Disk operations Management Engine, see documentation)
    • Legacy mode is when DMLite loads the Adapter+Memcache+MySQL plugins
      • The good old DPM daemon does the coordination work
      • Every process loading dmlite (httpd*4, gridftp, xrootd) needs a new pool of MySQL connections
    • Non-legacy mode is when DMLite loads DOMEAdapter
      • DOME does the coordination work and talks to mysqld
      • DOME does disk server status detection (up/down/space)
      • The DPM daemon coordinates only itself and SRM
      • Only one internal MySQL pool is used for dmlite
    • In non-legacy mode DPM now loads only DMLite::DOMEAdapter
      • dmlite-memcache, dmlite-mysql are no longer necessary
      • Resource consumption (FDs, mysql, etc.) is reduced by an order of magnitude, and so complexity and cost for us all
  • Deployment statistics: 97 sites (112 servers)
$ ldapsearch -x -LLL -H ldap://egee-bdii.cnaf.infn.it:2170 -b "Mds-Vo-Name=local,o=grid" '(&(objectClass=GlueSE)(GlueSEImplementationName=DPM))' GlueSEImplementationVersion | grep -i ^glue | sort | uniq -c
    32 GlueSEImplementationVersion: 1.10.0
    16 GlueSEImplementationVersion: 1.12.0
    21 GlueSEImplementationVersion: 1.8.10
     3 GlueSEImplementationVersion: 1.8.11
     2 GlueSEImplementationVersion: 1.8.7
     4 GlueSEImplementationVersion: 1.8.8
     6 GlueSEImplementationVersion: 1.8.9
    28 GlueSEImplementationVersion: 1.9.0
  • reported some issues with DOME and gridftp redirection that have been fixed in v1.12.0 (not yet in EPEL)
  • wait for DPM 1.12.0 before enabling DOME
  • all the sites with older DPM versions (1.8 and 1.9) are suggested to upgrade to the latest DPM version , following the guide DPM upgrade (chapter 1 Upgrade to DPM 1.10.0 "Legacy Flavour")
    • convenient to address well in advance any problem arising with the upgrade from older versions
  • later on, after v1.12.0 is relased, some other WLCG sites will test it; if no other issues are found, all the EGI sites can upgrade:
    • follow chapter 2 (Upgrade to DPM 1.10.0 "Dome Flavour") of the guide
      • DOME and the old LCGDM (srm protocol) will coexist

HTCondorCE integration

Link to procedure: https://wiki.egi.eu/wiki/PROC19

GGUS ticket: https://ggus.eu/index.php?mode=ticket_info&ticket_id=139377

Steps status:

  • (Completed) Underpinning Agreement:
  • (Completed) Configuration management:
    • Service type already present: org.opensciencegrid.htcondorce
  • (To do) OPS Dashboard:
    • To do when Conf Mgmt and Monitoring are completed.
  • (in progress) Information System: the info-provider is already available: https://github.com/opensciencegrid/htcondor-ce/tree/master/contrib/bdii
  • (in progress) Monitoring: some probes are already available that submit jobs to CondorCe, CREAM and ARC-CE:
    • https://gitlab.cern.ch/etf/jess
    • Available only on CentOS7 for the moment
    • discussions to create probes that directly submit jobs to CondorCE, without the usage of a condor pool
  • (Completed) Support: the support unit is https://wiki.egi.eu/wiki/GGUS:HTCondor-CE_FAQ
  • (in progress) Accounting:
  • (in progress) Documentation
  • (Completed) Security
    • Condor team filled in the questionnaire and sent it to Linda
  • UMD
    • suggested to act in advance because the functional tests could take a lot of time
    • Ticket for the inclusion: https://ggus.eu/index.php?mode=ticket_info&ticket_id=139764
      • HTCondor-CE is released with HTCondor in a version without the dependencies on other OSG software. Moreover, HTCondor-CE depends on HTCondor (though not for use as a batch scheduler), so both packages will need to be distributed.
    • Asked for any automated deployment (ansible, puppets or other) configuration files supported by HTcondor team
      • It is available a copy of the ansible files that OSG uses to configure HTCondor-CE on their internal testbed machines. They can provide help for a non-OSG version of the files
    • Provided information for the UMD card: https://wiki.egi.eu/wiki/UMD_products_ID_cards

webdav probes in OPERATORS profile

The webdav probes was included in the ARGO_MON_OPERATORS profile after the approval in the January 2018 OMB: in this way the failures will generate an alarm on the dashboard, and the ROD teams can open a ticket to the failing sites. If no particular issue occurs, and if at least 75% of webdav endpoint are passing the tests, the probes will be added in the ARGO_MON_CRITICAL profile, so the results of these probes will be taken into account for the A/R figures.


Storage accounting deployment

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

IMPORTANT: be sure to have installed the star-accounting.py script v1.0.4 (http://svnweb.cern.ch/world/wsvn/lcgdm/lcg-dm/trunk/scripts/StAR-accounting/star-accounting.py)

After setting up a daily cron job and running the accounting software, look for your data in the Accounting Portal: http://goc-accounting.grid-support.ac.uk/storagetest/storagesitesystems.html. 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.

Test portal: http://accounting-devel.egi.eu/storage.php

IMPORTANT: Do not encrypt the storage records with your host certificate, please comment out the “server_cert” variable in sender.cfg

List of sites already publishing and of tickets opened is reported here.

Several sites are not publishing the storage accounting data yet. NGIs please follow-up with the sites the configuration of the script in order to speed-up the process.

AOB

Next meeting

May 13th https://indico.egi.eu/indico/event/4323/