- Compact style
- Indico style
- Indico style - inline minutes
- Indico style - numbered
- Indico style - numbered + minutes
- Indico Weeks View
Indico celebrates its 20th anniversary! Check our blog post for more information!
To dial in to the conference:
a. Dial +41227676000
b. Enter access code 0157610
OR click HERE
NB: Reports were not received in advance of the meeting from:
See also this weekly summary of past / upcoming interventions at WLCG Tier0 and Tier1 sites (extracted manually from EGEE broadcasts and other sources).
Time at WLCG
T0 and T1 sites.
A single batch worker node per site is expected to be sufficient, both for load and availability services, the latter being addressed by the use of a R/O replica at another site in case of problems.
The target date for entering production for these LFC services is end September (so as not to conflict with other pressing issues, such as SL4 WNs for CMS CSA07 et al, FTS 2.0 services, SRM 2.2 etc etc).
Dear All,
I have included the following Tier1 sites in the LFC Streams environment: IN2P3, GridKA, PIC and RAL. The LFC data has been imported in the appropriate schemas at the Tier1 sites LHCb databases and the replication using Streams has been successfully enabled.
Tier1 database administrators and LFC team should now validate the copy and open the LFC service to production on their side.
Please let me know if you have any question.
Cheers, Eva
As per the draft agenda for the operations session (see above), sites are requested to send their top 5 operations issues to Nick by August 10th so that these can be consolidated into a single list.
Suggestions for additional topics for this session should be sent by July 31st.
Suggestion from Gonzalo Merino:
Experiences from sites/experiments operating the FTS servers
Some months ago, a channel configuration at the FTS servers in the T1s was suggested (essentially T1s host channels where they are the destination). This configuration seems not to fit for instance the needs of CMS. It seems problematic also since sites have no control of the files being read from them, so if many sites start to request reading from a given T1, this could collapse the storage service. If this is the situation, we should make sure that the different SRM/Storage implementations provide sites with the tools to control these situations.