Difference between revisions of "Agenda-2019-10-14"
Jump to navigation
Jump to search
(37 intermediate revisions by 3 users not shown) | |||
Line 6: | Line 6: | ||
= Middleware = | = Middleware = | ||
== UMD | == UMD == | ||
* | * UMD 4.9.0 release scheduled in October https://wiki.egi.eu/wiki/UMD_Release_Schedule | ||
* release | ** HTCondor-CE and dCache 5.2 to be included | ||
** Argo-ams-library, dynafed, APEL, StoRM, Xrootd, squid, gfal, davix | |||
** ARC 6.2 needs interaction with the PT => postponed | |||
== CMD == | |||
* TCB-Cloud + CMD PTs meeting on October 8th | |||
* discussion about the future of CMD, to be aligned with the upcoming "centralised operations" project | |||
* items: review the product list, distribute packages + images, use CI/CD, use a "fake site" as staged-rollout (if all probes green, deployment is OK) | |||
* next release is November (schedule to be fixed at the end of the year to be more realistic) | |||
== Preview repository == | == Preview repository == | ||
Line 24: | Line 32: | ||
== Feedback from DMSU == | == Feedback from DMSU == | ||
Known Error Database: https://wiki.egi.eu/wiki/KEDB | Known Error Database: https://wiki.egi.eu/wiki/KEDB | ||
*added the following problems: | |||
**CREAM-CE at CentOS 7: could not create connection to database server, [https://ggus.eu/index.php?mode=ticket_info&ticket_id=142425 GGUS 142425] (which was solved) | |||
**BDII udpate & base64 encoded ldif entries, [https://ggus.eu/index.php?mode=ticket_info&ticket_id=142928 GGUS 142928] (which is still open) | |||
Tickets handled by DMSU: | Tickets handled by DMSU: | ||
* | * [https://ggus.eu/index.php?mode=ticket_info&ticket_id=143303 GGUS #143303]: libcurl does not use CRLs correctly, SSL connection can fail unexpectedly, revoked cert can be accepted | ||
* [https://ggus.eu/index.php?mode=ticket_info&ticket_id=143438 GGUS #143438]: Issues with Caso (cloud accounting) | |||
* [https://ggus.eu/index.php?mode=ticket_info&ticket_id=143513 GGUS #143513]: problem with Ceph based WebDAV service | |||
* | |||
* | |||
== Monthly Availability/Reliability == | == Monthly Availability/Reliability == | ||
Line 92: | Line 47: | ||
**AsiaPacific: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142591 | **AsiaPacific: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142591 | ||
***INDIACMS-TIFR: SRM service not published in the BDII. No feedback yet | ***INDIACMS-TIFR: SRM service not published in the BDII. No feedback yet | ||
***TW-NTU-HEP: new SRM failures at the end of September | ***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 | **NGI_GRNET: https://ggus.eu/index.php?mode=ticket_info&ticket_id=140556 | ||
***GR-12-TEIKAV: SRM | ***GR-12-TEIKAV: SRM failures | ||
**NGI_IT: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142592 | **NGI_IT: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142592 | ||
***INFN-LECCE (recovered) | ***INFN-LECCE (recovered) | ||
***INFN-MILANO-ATLASC | ***INFN-MILANO-ATLASC: frequent SRM failures | ||
**NGI_PL: https://ggus.eu/index.php?mode=ticket_info&ticket_id=140557 | **NGI_PL: https://ggus.eu/index.php?mode=ticket_info&ticket_id=140557 | ||
***TASK: still problems: SRM failures and QCG bug; | ***TASK: still problems: SRM failures and QCG bug; The probe [https://poem.egi.eu/poem/admin/poem/public_probe/81/change/ eu.egi.QCG-Computing-CertValidity] doesn't manage to get the certificate information from the [https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_QCG.Computing&style=detail qcg computing hosts]. | ||
**NGI_RO: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142160 | **NGI_RO: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142160 | ||
***RO-02-NIPNE: Cooling system problem, migration to CentOS7 | ***RO-02-NIPNE: Cooling system problem, migration to CentOS7 | ||
**NGI_UA: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142980 | **NGI_UA: https://ggus.eu/index.php?mode=ticket_info&ticket_id=142980 | ||
***UA-BITP | ***UA-BITP: SRM not published in the BDII | ||
** | *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. The probe [https://poem.egi.eu/poem/admin/poem/public_probe/81/change/ eu.egi.QCG-Computing-CertValidity] doesn't manage to get the certificate information from the [https://argo-mon.egi.eu/nagios/cgi-bin/status.cgi?servicegroup=SERVICE_QCG.Computing&style=detail qcg computing hosts]. | |||
***the sites providing qcg computing can ask for a re-computation https://wiki.egi.eu/wiki/PROC10 | |||
suspended sites: AEGIS01-IPB-SCL (NGI_AEGIS) | suspended sites: AEGIS01-IPB-SCL (NGI_AEGIS) | ||
Line 124: | Line 78: | ||
**more details: https://wiki.egi.eu/wiki/DPM_End_of_legacy-mode_support | **more details: https://wiki.egi.eu/wiki/DPM_End_of_legacy-mode_support | ||
* since [http://lcgdm.web.cern.ch/dpm-1103-released-epel DPM 1.10.3 release], it is possible enabling the non-legacy mode DOME (Disk operations Management Engine, [https://gitlab.cern.ch/lcgdm/dmlite/blob/master/doc/dome/dome.pdf see documentation]) | * since [http://lcgdm.web.cern.ch/dpm-1103-released-epel DPM 1.10.3 release], it is possible enabling the non-legacy mode DOME (Disk operations Management Engine, [https://gitlab.cern.ch/lcgdm/dmlite/blob/master/doc/dome/dome.pdf see documentation]) | ||
**latest [http://lcgdm.web.cern.ch/dmlitedpm-1131-epel DPM release 1.13.1] | **latest [http://lcgdm.web.cern.ch/dmlitedpm-1131-epel DPM release 1.13.1] has been also released in [http://repository.egi.eu/2019/09/10/release-umd-4-8-5/ UMD 4.8.5] | ||
* '''EGI Operations sent a broadcast to site-admins([https://operations-portal.egi.eu/broadcast/archive/2426 first bunch] and [https://operations-portal.egi.eu/broadcast/archive/2438 second bunch]) and [https://operations-portal.egi.eu/broadcast/archive/2420 VO managers] with a survey to fill in''': | * '''EGI Operations sent a broadcast to site-admins([https://operations-portal.egi.eu/broadcast/archive/2426 first bunch] and [https://operations-portal.egi.eu/broadcast/archive/2438 second bunch]) and [https://operations-portal.egi.eu/broadcast/archive/2420 VO managers] with a survey to fill in''': | ||
**site-admins: to know the upgrade plans: https://www.surveymonkey.com/r/2PBZSNB | **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 | **VO Managers: to know any barriers in moving away from using SRM protocol https://www.surveymonkey.com/r/2ZMZJVG | ||
* '''Deployment statistics | * '''Deployment statistics (Oct 10th):''' | ||
$ ldapsearch -x -LLL -H ldap://bdii. | $ ldapsearch -x -LLL -H ldap://egee-bdii.cnaf.infn.it:2170 -b "GLUE2GroupID=grid,o=glue" '(&(objectClass=GLUE2Manager)(GLUE2ManagerProductName=DPM))' GLUE2ManagerProductVersion GLUE2ManagerID | grep GLUE2ManagerProductVersion | sort | uniq -c | ||
11 GLUE2ManagerProductVersion: 1.10.0 | |||
5 GLUE2ManagerProductVersion: 1.12.0 | |||
47 GLUE2ManagerProductVersion: 1.13.0 | |||
4 GLUE2ManagerProductVersion: 1.13.1 | |||
10 GLUE2ManagerProductVersion: 1.8.10 | |||
2 | 2 GLUE2ManagerProductVersion: 1.8.11 | ||
1 GLUE2ManagerProductVersion: 1.8.7 | |||
1 GLUE2ManagerProductVersion: 1.8.8 | |||
4 GLUE2ManagerProductVersion: 1.8.9 | |||
10 GLUE2ManagerProductVersion: 1.9.0 | |||
Liasing with WLCG to follow-up the upgrade. Opened GGUS tickets asking the following: | |||
* all the sites with older DPM versions than 1.12 are suggested to upgrade to the latest DPM version , following the guide [https://twiki.cern.ch/twiki/bin/view/DPM/DpmSetup1100 DPM upgrade] (chapter 1 Upgrade to DPM 1.10.0 "Legacy Flavour" and chapter 2 Upgrade to DPM 1.10.0 "Dome Flavour") | * all the sites with older DPM versions than 1.12 are suggested to upgrade to the latest DPM version , following the guide [https://twiki.cern.ch/twiki/bin/view/DPM/DpmSetup1100 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 | **DOME and the old LCGDM (srm protocol) will coexist | ||
*'''Monitoring''': sites should enable the monitoring of the HTTP/WebDav and/or GridFTP endpoints | |||
**register the storage service endpoint as webdav and/or globus-GRIDFTP service type, with production flag disabled, providing respectively the URL field and the Extension Properties information as explained in the [https://wiki.egi.eu/wiki/HOWTO21#webdav HOWTO21] | |||
*'''Monitoring''': sites should enable the monitoring of the HTTP/WebDav | |||
**register the storage service endpoint as | |||
**check if the tests are ok | **check if the tests are ok | ||
**switch the production flag to "yes" | **switch the production flag to "yes" | ||
List of tickets: | |||
* [https://ggus.eu/index.php?mode=ticket_search&show_columns_check%5B%5D=TICKET_TYPE&show_columns_check%5B%5D=AFFECTED_VO&show_columns_check%5B%5D=AFFECTED_SITE&show_columns_check%5B%5D=PRIORITY&show_columns_check%5B%5D=RESPONSIBLE_UNIT&show_columns_check%5B%5D=STATUS&show_columns_check%5B%5D=DATE_OF_CHANGE&show_columns_check%5B%5D=SHORT_DESCRIPTION&show_columns_check%5B%5D=SCOPE&ticket_id=&supportunit=&su_hierarchy=0&former_su=&vo=&user=&keyword=DOME+enabling&involvedsupporter=&assignedto=&affectedsite=&specattrib=none&status=&priority=&typeofproblem=all&ticket_category=all&mouarea=&date_type=creation+date&tf_radio=1&timeframe=any&from_date=10+Oct+2019&to_date=11+Oct+2019&untouched_date=&scope=&orderticketsby=REQUEST_ID&orderhow=desc&search_submit=GO%21 DPM upgrade, DOME enabling, and monitoring] (33) | |||
* [https://ggus.eu/index.php?mode=ticket_search&show_columns_check%5B%5D=TICKET_TYPE&show_columns_check%5B%5D=AFFECTED_VO&show_columns_check%5B%5D=AFFECTED_SITE&show_columns_check%5B%5D=PRIORITY&show_columns_check%5B%5D=RESPONSIBLE_UNIT&show_columns_check%5B%5D=STATUS&show_columns_check%5B%5D=DATE_OF_CHANGE&show_columns_check%5B%5D=SHORT_DESCRIPTION&show_columns_check%5B%5D=SCOPE&ticket_id=&supportunit=&su_hierarchy=0&former_su=&vo=&user=&keyword=enabling+DOME&involvedsupporter=&assignedto=&affectedsite=&specattrib=none&status=&priority=&typeofproblem=all&ticket_category=all&mouarea=&date_type=creation+date&tf_radio=1&timeframe=any&from_date=10+Oct+2019&to_date=11+Oct+2019&untouched_date=&scope=&orderticketsby=REQUEST_ID&orderhow=desc&search_submit=GO%21 enabling DOME and proper monitoring] (6) | |||
* tickets opened by WLCG: [https://ggus.eu/index.php?mode=ticket_search&show_columns_check%5B%5D=TICKET_TYPE&show_columns_check%5B%5D=AFFECTED_VO&show_columns_check%5B%5D=AFFECTED_SITE&show_columns_check%5B%5D=PRIORITY&show_columns_check%5B%5D=RESPONSIBLE_UNIT&show_columns_check%5B%5D=STATUS&show_columns_check%5B%5D=DATE_OF_CHANGE&show_columns_check%5B%5D=SHORT_DESCRIPTION&show_columns_check%5B%5D=SCOPE&ticket_id=&supportunit=&su_hierarchy=0&former_su=&vo=&user=&keyword=has+to+be+configured+with+DOME&involvedsupporter=&assignedto=&affectedsite=&specattrib=none&status=&priority=&typeofproblem=all&ticket_category=all&mouarea=&date_type=creation+date&tf_radio=1&timeframe=any&from_date=10+Oct+2019&to_date=11+Oct+2019&untouched_date=&scope=&orderticketsby=REQUEST_ID&orderhow=desc&search_submit=GO%21 13] and [https://ggus.eu/index.php?mode=ticket_search&show_columns_check%5B%5D=TICKET_TYPE&show_columns_check%5B%5D=AFFECTED_VO&show_columns_check%5B%5D=AFFECTED_SITE&show_columns_check%5B%5D=PRIORITY&show_columns_check%5B%5D=RESPONSIBLE_UNIT&show_columns_check%5B%5D=STATUS&show_columns_check%5B%5D=DATE_OF_CHANGE&show_columns_check%5B%5D=SHORT_DESCRIPTION&show_columns_check%5B%5D=SCOPE&ticket_id=&supportunit=&su_hierarchy=0&former_su=&vo=&user=&keyword=Upgrade+and+reconfigure+DPM+at&involvedsupporter=&assignedto=&affectedsite=&specattrib=none&status=&priority=&typeofproblem=all&ticket_category=all&mouarea=&date_type=creation+date&tf_radio=1&timeframe=any&from_date=10+Oct+2019&to_date=11+Oct+2019&untouched_date=&scope=&orderticketsby=REQUEST_ID&orderhow=desc&search_submit=GO%21 7] | |||
== HTCondorCE integration == | == HTCondorCE integration == | ||
Line 169: | Line 128: | ||
**https://gitlab.cern.ch/etf/jess | **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 | **ticket to ARGO to deploy the probes on the test instance: https://ggus.eu/index.php?mode=ticket_info&ticket_id=141177 | ||
***there is a bug on CentOS6 due to python version; the probe will be tested on the CentOS7 nagios instance | |||
*('''Completed''') Support: the support unit is https://wiki.egi.eu/wiki/GGUS:HTCondor-CE_FAQ | *('''Completed''') Support: the support unit is https://wiki.egi.eu/wiki/GGUS:HTCondor-CE_FAQ | ||
*( | *('''Completed''') Accounting: | ||
**Some work has been done: https://twiki.cern.ch/twiki/bin/view/LCG/HtCondorCeAccounting | **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 | **ticket https://ggus.eu/index.php?mode=ticket_info&ticket_id=139403 to track the progress on this topic | ||
***problems should have been fixed with [https://github.com/apel/apel/releases APEL 1.8.1] | ***problems should have been fixed with [https://github.com/apel/apel/releases APEL 1.8.1] | ||
*(Completed) Documentation | *(Completed) Documentation | ||
Line 188: | Line 144: | ||
***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 | ***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 | **Provided information for the UMD card: https://wiki.egi.eu/wiki/UMD_products_ID_cards | ||
**plan to release by the end of the month | |||
= AOB = | = AOB = | ||
Line 193: | Line 150: | ||
== Next meeting == | == Next meeting == | ||
November https://indico.egi.eu/indico/event/ | November https://indico.egi.eu/indico/event/4830/ and there will be no meeting in December https://indico.egi.eu/indico/category/32/ |
Latest revision as of 13:52, 14 October 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 TO UPDATE
Middleware
UMD
- UMD 4.9.0 release scheduled in October https://wiki.egi.eu/wiki/UMD_Release_Schedule
- HTCondor-CE and dCache 5.2 to be included
- Argo-ams-library, dynafed, APEL, StoRM, Xrootd, squid, gfal, davix
- ARC 6.2 needs interaction with the PT => postponed
CMD
- TCB-Cloud + CMD PTs meeting on October 8th
- discussion about the future of CMD, to be aligned with the upcoming "centralised operations" project
- items: review the product list, distribute packages + images, use CI/CD, use a "fake site" as staged-rollout (if all probes green, deployment is OK)
- next release is November (schedule to be fixed at the end of the year to be more realistic)
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
- added the following problems:
- CREAM-CE at CentOS 7: could not create connection to database server, GGUS 142425 (which was solved)
- BDII udpate & base64 encoded ldif entries, GGUS 142928 (which is still open)
Tickets handled by DMSU:
- GGUS #143303: libcurl does not use CRLs correctly, SSL connection can fail unexpectedly, revoked cert can be accepted
- GGUS #143438: Issues with Caso (cloud accounting)
- GGUS #143513: problem with Ceph based WebDAV service
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; The probe eu.egi.QCG-Computing-CertValidity doesn't manage to get the certificate information from the qcg computing hosts.
- 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. The probe eu.egi.QCG-Computing-CertValidity doesn't manage to get the certificate information from the qcg computing hosts.
- the sites providing qcg computing can ask for a re-computation https://wiki.egi.eu/wiki/PROC10
- 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 has been also released in UMD 4.8.5
- 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 (Oct 10th):
$ ldapsearch -x -LLL -H ldap://egee-bdii.cnaf.infn.it:2170 -b "GLUE2GroupID=grid,o=glue" '(&(objectClass=GLUE2Manager)(GLUE2ManagerProductName=DPM))' GLUE2ManagerProductVersion GLUE2ManagerID | grep GLUE2ManagerProductVersion | sort | uniq -c 11 GLUE2ManagerProductVersion: 1.10.0 5 GLUE2ManagerProductVersion: 1.12.0 47 GLUE2ManagerProductVersion: 1.13.0 4 GLUE2ManagerProductVersion: 1.13.1 10 GLUE2ManagerProductVersion: 1.8.10 2 GLUE2ManagerProductVersion: 1.8.11 1 GLUE2ManagerProductVersion: 1.8.7 1 GLUE2ManagerProductVersion: 1.8.8 4 GLUE2ManagerProductVersion: 1.8.9 10 GLUE2ManagerProductVersion: 1.9.0
Liasing with WLCG to follow-up the upgrade. Opened GGUS tickets asking the following:
- 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
- Monitoring: sites should enable the monitoring of the HTTP/WebDav and/or GridFTP endpoints
- register the storage service endpoint as webdav and/or globus-GRIDFTP service type, with production flag disabled, providing respectively the URL field and the Extension Properties information as explained in the HOWTO21
- check if the tests are ok
- switch the production flag to "yes"
List of tickets:
- DPM upgrade, DOME enabling, and monitoring (33)
- enabling DOME and proper monitoring (6)
- tickets opened by WLCG: 13 and 7
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
- there is a bug on CentOS6 due to python version; the probe will be tested on the CentOS7 nagios instance
- (Completed) Support: the support unit is https://wiki.egi.eu/wiki/GGUS:HTCondor-CE_FAQ
- (Completed) 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
- 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
- plan to release by the end of the month
AOB
Next meeting
November https://indico.egi.eu/indico/event/4830/ and there will be no meeting in December https://indico.egi.eu/indico/category/32/