TWiki
>
LCG Web
>
WLCGCommonComputingReadinessChallenges
>
WLCGOperationsWeb
>
BestPracticesForSchedDT
(2017-12-20,
MaartenLitmaath
)
(raw view)
E
dit
A
ttach
P
DF
---+!! Best practices for scheduled downtimes %TOC{depth="3"}% ---++ Tier-1 downtimes Experiments may experience problems when 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 (see below) to see if another Tier-1 already has an "outage" downtime in the desired time slot. 1 If there is a conflict, the best would be to pick another time slot. 1 In case stronger constraints do not permit another time slot, the Tier-1 should 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 possibly the other Tier-1, to see if a less disruptive scenario can be arranged instead. 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, the SCOD will follow up with the parties involved. ---+++ Links to Tier-1 downtimes %INCLUDE{ "WLCGDowntimesTemplate" }% ---++ Advance notifications of downtimes The experiments have expressed how much in advance they would like to be informed of a scheduled downtime, depending on its duration. In general __the earlier, the better__. The following table summarizes what each of the experiments would appreciate as advance notifications (*N*) for downtimes (*DT*) of various lengths: | *Experiment* | *DT up to 5 days* | *DT up to 1 month* | *DT longer than 1 month* | | ALICE | N = 1 day | N = 1 month | N = 1 month | | ATLAS | N = 1 day | N = 1 month | N = 1 month | | !CMS | N = 1 day | N = 3 days | Allow enough time for data migration | | LHCb | N = 1 day | N = 5 days | N = 1 month, esp. for T1 sites | Note that !CMS would like to have sufficient time to migrate data away from a site that will have a downtime longer than 1 month, to be discussed with !CMS operations.
E
dit
|
A
ttach
|
Watch
|
P
rint version
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
WYSIWYG
|
M
ore topic actions
Topic revision: r2 - 2017-12-20
-
MaartenLitmaath
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
Altair
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-2024 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