Agenda-2019-10-14
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 TO UPDATE
Middleware
UMD 4.8.5
- "DPM-dedicated" release to support migration to 1.13.0 (see dedicated section)
- release candidate ready, integration tests in progress, TBR very soon
Preview repository
- released on 2019-08-16
- Preview 1.24.0 AppDB info (sl6): APEL Client/Server 1.8.1, APEL-SSM 2.4.0, ARC 6.1.0, davix 0.7.4, dCache 4.2.40, DMLite/DPM 1.13.1, Dynafed 1.5.0, frontier-squid 4.8.1, gfal2 2.16.3
- Preview 2.24.0 AppDB info (CentOS 7): APEL Client/Server 1.8.1, APEL-SSM 2.4.0, ARC 6.1.0, davix 0.7.4, dCache 4.2.40, DMLite/DPM 1.13.1, Dynafed 1.5.0, frontier-squid 4.8.1, gfal2 2.16.3
Operations
ARGO/SAM
FedCloud
Feedback from DMSU
Known Error Database: https://wiki.egi.eu/wiki/KEDB
Tickets handled by 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
- Under-performed sites in the past A/R reports with issues not yet fixed:
- AsiaPacific: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142591
- INDIACMS-TIFR: SRM service not published in the BDII. No feedback yet
- TW-NTU-HEP: new SRM failures at the end of September due to DPM upgrade
- NGI_GRNET: https://ggus.eu/index.php?mode=ticket_info&ticket_id=140556
- GR-12-TEIKAV: SRM failures
- NGI_IT: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142592
- INFN-LECCE (recovered)
- INFN-MILANO-ATLASC: frequent SRM failures
- NGI_PL: https://ggus.eu/index.php?mode=ticket_info&ticket_id=140557
- TASK: still problems: SRM failures and QCG bug;
- NGI_RO: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142160
- RO-02-NIPNE: Cooling system problem, migration to CentOS7
- NGI_UA: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142980
- UA-BITP: SRM not published in the BDII
- AsiaPacific: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142591
- Under-performed sites after 3 consecutive months, under-performed NGIs, QoS violations: (Sept 2019):
- NGI_PL: https://ggus.eu/index.php?mode=ticket_info&ticket_id=143506
- WCSS64: qcg host certificate failures, CREAM-CE failures
- NGI_PL: https://ggus.eu/index.php?mode=ticket_info&ticket_id=143506
suspended sites: AEGIS01-IPB-SCL (NGI_AEGIS)
IPv6 readiness plans
- INFORMATION ARE 6 MONTHS OLD, please provide updates to the IPv6 assessment (ongoing) https://wiki.egi.eu/w/index.php?title=IPV6_Assessment
- if any relevant, information will be summarised at OMB
LCGDM end of support and migration to / enabling of DOME
- The DPM team has agreed to extend support for security updates for the DPM legacy functionality until 30 September 2019. However, affected service providers should still plan to disable legacy mode well before this date.
- more details: https://wiki.egi.eu/wiki/DPM_End_of_legacy-mode_support
- since DPM 1.10.3 release, it is possible enabling the non-legacy mode DOME (Disk operations Management Engine, see documentation)
- latest DPM release 1.13.1 (to be included in UMD)
- EGI Operations sent a broadcast to site-admins(first bunch and second bunch) and VO managers with a survey to fill in:
- site-admins: to know the upgrade plans: https://www.surveymonkey.com/r/2PBZSNB
- VO Managers: to know any barriers in moving away from using SRM protocol https://www.surveymonkey.com/r/2ZMZJVG
- Deployment statistics: 85 sites (100 servers)
$ ldapsearch -x -LLL -H ldap://bdii.marie.hellasgrid.gr:2170 -b "Mds-Vo-Name=local,o=grid" '(&(objectClass=GlueSE)(GlueSEImplementationName=DPM))' GlueSEImplementationVersion | grep -i ^glue | sort | uniq -c 14 GlueSEImplementationVersion: 1.10.0 21 GlueSEImplementationVersion: 1.12.0 2 GlueSEImplementationVersion: 1.12.1 22 GlueSEImplementationVersion: 1.13.0 17 GlueSEImplementationVersion: 1.8.10 2 GlueSEImplementationVersion: 1.8.11 2 GlueSEImplementationVersion: 1.8.7 4 GlueSEImplementationVersion: 1.8.8 3 GlueSEImplementationVersion: 1.8.9 14 GlueSEImplementationVersion: 1.9.0
- all the sites with older DPM versions than 1.12 are suggested to upgrade to the latest DPM version , following the guide DPM upgrade (chapter 1 Upgrade to DPM 1.10.0 "Legacy Flavour" and chapter 2 Upgrade to DPM 1.10.0 "Dome Flavour")
- DOME and the old LCGDM (srm protocol) will coexist
- the upgrade will be followed-up mainly by WLCG
- EGI Operations will liaise with the non-WLCG sites by opening GGUS tickets after DPM 1.13 is reeleased into UMD
- Monitoring: sites should enable the monitoring of the HTTP/WebDav endpoint
- register the storage service endpoint as WebDav service type, with production flag disabled, providing the URL field (see the HOWTO21
- check if the tests are ok
- switch the production flag to "yes"
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
- to test during the staged rollout
- (in progress) Monitoring: some probes are already available that submit jobs to CondorCe, CREAM and ARC-CE:
- https://gitlab.cern.ch/etf/jess
- ticket to ARGO to deploy the probes on the test instance: https://ggus.eu/index.php?mode=ticket_info&ticket_id=141177
- (Completed) Support: the support unit is https://wiki.egi.eu/wiki/GGUS:HTCondor-CE_FAQ
- (in progress) Accounting:
- Some work has been done: https://twiki.cern.ch/twiki/bin/view/LCG/HtCondorCeAccounting
- ticket https://ggus.eu/index.php?mode=ticket_info&ticket_id=139403 to track the progress on this topic
- APEL 1.8.0-1 adds support for a cputmult scaling factor.
- Liverpool site managed to publish accounting records
- To involve more (UK) sites in the testing
- INFN-T1 joined the tests
- problems should have been fixed with APEL 1.8.1
- (Completed) Documentation
- (Completed) Security
- Condor team filled in the questionnaire and sent it to Linda
- (in progress) 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