TWiki
>
LCG Web
>
WLCGCommonComputingReadinessChallenges
>
WLCGOperationsMeetings
>
WLCGOpsMeetingWeek171120
(revision 6) (raw view)
Edit
Attach
PDF
---+!! Week of 171120 %TOC% ---++ WLCG Operations Call details * At CERN the meeting room is [[https://maps.cern.ch/mapsearch/?centerX=2492565¢erY=1121070¢erScale=2500][513]] R-068. * For remote participation we use the Vidyo system. Instructions can be found [[https://indico.cern.ch/conferenceDisplay.py?confId=287280][here]]. ---++ General Information * The purpose of the meeting is: * to report significant operational issues (i.e. issues which can or did degrade experiment or site operations) which are ongoing or were resolved after the previous meeting; * to announce or schedule interventions at Tier-1 sites; * to inform about recent or upcoming changes in the experiment activities or systems having a visible impact on sites; * to provide important news about the middleware; * to communicate any other information considered interesting for WLCG operations. * The meeting should run from 15:00 until 15:20, exceptionally to 15:30. * The SCOD rota for the next few weeks is at ScodRota * General information about the WLCG Service can be accessed from the [[https://wlcg-ops.web.cern.ch/][Operations Web]] * Whenever a particular topic needs to be discussed at the daily meeting requiring information from site or experiments, it is highly recommended to announce it by email to wlcg-operations@cernSPAMNOT.ch to make sure that the relevant parties have the time to collect the required information or invite the right people at the meeting. ---++ Tier-1 downtimes Experiments may experience problems if two or more of their Tier-1 sites are inaccessible at the same time. Therefore Tier-1 sites should do their best to avoid scheduling a downtime classified as "outage" in a time slot overlapping with an "outage" downtime already declared by another Tier-1 site supporting the same VO(s). The following procedure is recommended: 1 A Tier-1 should check the downtimes calendar to see if another Tier-1 has already an "outage" downtime in the desired time slot. 1 If there is a conflict, another time slot should be chosen. 1 In case stronger constraints cannot allow to choose another time slot, the Tier-1 will point out the existence of the conflict to the SCOD mailing list and at the next WLCG operations call, to discuss it with the representatives of the experiments involved and the other Tier-1. As an additional precaution, the SCOD will check the downtimes calendar for Tier-1 "outage" downtime conflicts at least once during his/her shift, for the current and the following two weeks; in case a conflict is found, it will be discussed at the next operations call, or offline if at least one relevant experiment or site contact is absent. ---++ Links to Tier-1 downtimes %INCLUDE{ "WLCGDowntimesTemplate" }% ---++ Monday Attendance: * local: * remote: Experiments round table: * ATLAS [[AtlasComputing.ADCOperationsWeeklySummaries2017][reports]] ( [[AtlasComputing.ADCOperationsWeeklySummaries2017?raw=on][raw view]]) - * CMS [[CMS.FacOps_WLCGdailyreports][reports]] ( [[CMS.FacOps_WLCGdailyreports?raw=on][raw view]]) - * ALICE - * High to very high activity on average * CERN: ~all 1.2 M files lost from the EOS namespace were recovered, thanks! * Some calibration DB files were found having zero size. Being followed up. * CERN: EOS failures due to 1 link to Wigner being down Thu/Fri (OTG:0040930). * CERN: CASTOR incident Sun evening due to DB outage (OTG:0040966). * LHCb [[LHCb.ProductionOperationsWLCGdailyReports][reports]] ( [[LHCb.ProductionOperationsWLCGdailyReports?raw=on][raw view]]) - Sites / Services round table: * ASGC: * BNL: * CNAF: * EGI: * FNAL: * !IN2P3: * JINR: * KISTI: * KIT: * NDGF: * NL-T1: * NRC-KI: * OSG: * PIC: * !RAL: * TRIUMF: NTR * CERN computing services: * CERN storage services: * CERN databases: * GGUS: * Monitoring: * Final reports for the Oct 2017 availability sent around * MW Officer: NTR * Networks: * Security: NTR AOB:
Edit
|
Attach
|
Watch
|
P
rint version
|
H
istory
:
r19
|
r8
<
r7
<
r6
<
r5
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r6 - 2017-11-20
-
VincentBrillault
Log In
LCG
LCG Wiki Home
LCG Web Home
Changes
Index
Search
LCG Wikis
LCG Service
Coordination
LCG Grid
Deployment
LCG
Apps Area
Public webs
Public webs
ABATBEA
ACPP
ADCgroup
AEGIS
AfricaMap
AgileInfrastructure
ALICE
AliceEbyE
AliceSPD
AliceSSD
AliceTOF
AliFemto
ALPHA
ArdaGrid
ASACUSA
AthenaFCalTBAna
Atlas
AtlasLBNL
AXIALPET
CAE
CALICE
CDS
CENF
CERNSearch
CLIC
Cloud
CloudServices
CMS
Controls
CTA
CvmFS
DB
DefaultWeb
DESgroup
DPHEP
DM-LHC
DSSGroup
EGEE
EgeePtf
ELFms
EMI
ETICS
FIOgroup
FlukaTeam
Frontier
Gaudi
GeneratorServices
GuidesInfo
HardwareLabs
HCC
HEPIX
ILCBDSColl
ILCTPC
IMWG
Inspire
IPv6
IT
ItCommTeam
ITCoord
ITdeptTechForum
ITDRP
ITGT
ITSDC
LAr
LCG
LCGAAWorkbook
Leade
LHCAccess
LHCAtHome
LHCb
LHCgas
LHCONE
LHCOPN
LinuxSupport
Main
Medipix
Messaging
MPGD
NA49
NA61
NA62
NTOF
Openlab
PDBService
Persistency
PESgroup
Plugins
PSAccess
PSBUpgrade
R2Eproject
RCTF
RD42
RFCond12
RFLowLevel
ROXIE
Sandbox
SocialActivities
SPI
SRMDev
SSM
Student
SuperComputing
Support
SwfCatalogue
TMVA
TOTEM
TWiki
UNOSAT
Virtualization
VOBox
WITCH
XTCA
Welcome Guest
Login
or
Register
Cern Search
TWiki Search
Google Search
LCG
All webs
Copyright &© 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use
Discourse
or
Send feedback