Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Agenda-2019-01-14"

From EGIWiki
Jump to navigation Jump to search
 
(8 intermediate revisions by 2 users not shown)
Line 11: Line 11:
= Middleware  =
= Middleware  =


* UMD 4.8.0 to be released in November (delayed)
* UMD 4.8.0 released on November 29th http://repository.egi.eu/2018/11/29/release-umd-4-8-0/ including APEL-SSM 2.3.0, XRootD 4.8.4, CernVM-FS 2.5.1, CERN Frontier squid 3.5.28-3.1, DPM 1.10.4, Dynafed 1.3.2, BDII 5.2.25, glite-info-update-endpoint 3.0.1, GRAM5 14.1.0, GridFTP 13.8.1
* CMD-ONE 1.1.0 released http://repository.egi.eu/2018/11/12/release-cmd-one-1-1-0/
* UMD 4.8.1 is an emergency fix of the fourth Major release of UMD. It adds a fix for FTS-Monitoring in CentOS7 that updates dependencies from python-django to python-django16 http://repository.egi.eu/2018/12/12/release-umd-4-8-1/
** siteBDII 1.2.1, Gridsite 2.3.4, rOCCI server 2.0.4, Keystorm 1.1.0, Cloudkeeper 1.6.0, Cloudkeeper ONE 1.3.0


== Preview repository  ==
== Preview repository  ==
Line 25: Line 24:


== FedCloud  ==
== FedCloud  ==
* CYFRONET-CLOUD publishes very old data (last timestamp is 2018-08-21 09:00:50), to be contacted
* UPV-GRyCAP seem to have still oneacct-export/0.4.5, and last timestamp is 2018-07-24 02:59:29, to be contacted
* NCG-INGRID-PT accounting never set up https://ggus.eu/?mode=ticket_info&ticket_id=136309, will escalate to NGI_IBERGRID


== Feedback from DMSU  ==
== Feedback from DMSU  ==
Line 76: Line 72:
**NGI_PL:  
**NGI_PL:  
***ICM: https://ggus.eu/index.php?mode=ticket_info&ticket_id=138062 very long downtime, recommended the suspension
***ICM: https://ggus.eu/index.php?mode=ticket_info&ticket_id=138062 very long downtime, recommended the suspension
***WCSS64: SRM not in BDII https://ggus.eu/index.php?mode=ticket_info&ticket_id=138672
***WCSS64: SRM not in BDII https://ggus.eu/index.php?mode=ticket_info&ticket_id=138672 (SOLVED)
*Under-performed sites after 3 consecutive months, under-performed NGIs, QoS violations: ('''December 2018'''):
*Under-performed sites after 3 consecutive months, under-performed NGIs, QoS violations: ('''December 2018'''):
**AfricaArabia: https://ggus.eu/index.php?mode=ticket_info&ticket_id=139056
**AfricaArabia: https://ggus.eu/index.php?mode=ticket_info&ticket_id=139056
Line 110: Line 106:
*BUDAPEST: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137553 (SOLVED)
*BUDAPEST: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137553 (SOLVED)
*WCSS64: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137555 (SOLVED)
*WCSS64: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137555 (SOLVED)
*CYFRONET: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137557 (procedure not started yet)
*CYFRONET-LGC2: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137557 (to decide if replacing it with DIRAC or shut it down)
*AEGIS01-IPB-SCL: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137558 (SOLVED)
*AEGIS01-IPB-SCL: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137558 (SOLVED)
*MA-01-CNRST: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137559 (downtime till end of November)
*MA-01-CNRST: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137559 (downtime expired, to check the WMS status)
*SARA-MATRIX: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137560 (planned to set-up a national DIRAC server for replacing the WMS, Q1 2019)
*SARA-MATRIX: https://ggus.eu/index.php?mode=ticket_info&ticket_id=137560 (planned to set-up a national DIRAC server for replacing the WMS, Q1 2019)


== IPv6 readiness plans  ==
== IPv6 readiness plans  ==


*assessment ongoing https://wiki.egi.eu/w/index.php?title=IPV6_Assessment  
* please provide updates to the IPv6 assessment (ongoing) https://wiki.egi.eu/w/index.php?title=IPV6_Assessment information will be summarised at OMB (probably February)
*still missing NGIs/ROCs
*added column in FedCloud wiki to monitor IPv6 readiness of cloud sites https://wiki.egi.eu/wiki/Federated_Cloud_infrastructure_status#Status_of_the_Federated_Cloud


== webdav probes in OPERATORS profile  ==
== webdav probes in OPERATORS profile  ==


The webdav probes was included in the [https://poem.egi.eu/poem/admin/poem/profile/4/ ARGO_MON_OPERATORS] profile after the approval in the [https://indico.egi.eu/indico/event/3616/ January 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 [https://poem.egi.eu/poem/admin/poem/profile/3/ ARGO_MON_CRITICAL] profile, so the results of these probes will be taken into account for the A/R figures.  
The webdav probes was included in the [https://poem.egi.eu/poem/admin/poem/profile/4/ ARGO_MON_OPERATORS] profile after the approval in the [https://indico.egi.eu/indico/event/3616/ 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 [https://poem.egi.eu/poem/admin/poem/profile/3/ ARGO_MON_CRITICAL] profile, so the results of these probes will be taken into account for the A/R figures.  


*webdav endpoints registered in GOC-DB: https://goc.egi.eu/gocdbpi/public/?method=get_service&&service_type=webdav  
*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
*link to nagios results: https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_webdav&style=detail
** '''5 CRITICAL out of 34 (OK status: 85.3%)'''
** '''9 CRITICAL out of 34 (OK status: 73.5%)'''


List of sites that not have completed the configuration yet:  
List of sites that not have completed the configuration yet:  
Line 170: Line 164:
== Next meeting  ==
== Next meeting  ==


*'''January 14th, 2019''' https://indico.egi.eu/indico/event/4319/
*'''February 11th, 2019''' https://indico.egi.eu/indico/event/4320/
*Check meetings for the first half of 2019 in the calendar https://indico.egi.eu/indico/category/32/
*Check meetings for the first half of 2019 in the calendar https://indico.egi.eu/indico/category/32/

Latest revision as of 15:02, 14 January 2019

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

TopBDII flooding unnecessary connections

It has been reported to EGI Operations that the TopBDII is trying many unnecessary connections to 2180/tcp because of how it's configured. This is basically due to the OSG flag still configured to "true" in /etc/glite/glite-info-update-endpoints.conf, resulting in a hourly cronjob to try establishing many useless connections.

It is enough to set OSG=false in order to prevent this useless traffic. Sites providing TopBDII are kindly asked to apply OSG=false to their configuration. An update to the glite-info-update-endpoints package will be released in UMD4 in the next days together with the regular UMD update.

Middleware

Preview repository

  • 2018-11-16

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

Decommissioning EMI WMS

WMS servers can be decommissioned. Please follow the procedure PROC12. The plan is:

  • Starting from January 2018, put the WMS servers in draining: this will block the submission of new jobs and will allow the jobs previously submitted to finish
    • inform in advance your users that you are going to put in draining and then dismiss the WMS servers (as per PROC12)
    • there might be several VOs enabled on your WMS servers: in case only few of them need to use the service for few weeks more, you might disable the other VOs
  • On Dec 14th EGI Operations sent a new broadcast to the VOs reminding the users the forthcoming WMS decommission
  • From March, the nagios probe eu.egi.sec.WMS will return a CRITICAL status for the servers still in production, and the ROD teams will open a ticket to the sites that haven't finished the decommission process yet

WMS servers in downtime on GOC-DB

5 WMS still registered on GOC-DB as production and monitored

Status on nagios

Tickets opened Oct 4th:

IPv6 readiness plans

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.

List of sites that not have completed the configuration yet:

List of sites that disabled webdav: UNIGE-DPNC, GR-01-AUTH, HG-03-AUTH, CETA-GRID, WUT

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

Retrieved from "https://wiki.egi.eu/w/index.php?title=Agenda-2019-01-14&oldid=100911"