Process for contacting sites

Objective

The objective is to get all the endpoints green. "Read only" endpoints with the appropriate standard file are shown as green in the summary pages.

Notes:

• The scheduler is also running tests unrelated to the HTTP TF. In particular, the same host will often receive SRM tests. The results of these may be useful for debugging but failing SRM tests should not result in a ticket from this TF.
• There are various views available, the results links below point to one of the more useful pages.
• In general the "services of host" summary page should be sent to the site (for example, this page).

Test results

Atlas results

LHCb: results

Process

The TF has a GGUS Support Unit (of the same name). Under normal operations the tickets will be assigned to sites, but tickets can always be reassigned to the TF if necessary. All interaction with a site related to a particular endpoint and VO should be on the same ticket (until closed).

Once per week: review non green endpoints and open a ticket against any which do not have one open.

Continuous: respond to ticket updates.

To open a ticket:

• check no outstanding ticket for that endpoint and that VO. Search for:
  • Involved support: wlcg-ops-coord-tf-http-rota
  • Notified site: sitename
  • Keyword: endpoint
  • Creation date: any
• create ticket with standard text
  • Subject - HTTP support for endpoint
  • Concerned VO - VO
  • Affected Site - See this page
  • Ticket category - Incident
  • Type of issue - storage systems
  • Notify site - choose site (again).
  • leave other fields as they are
• add wlcg-ops-coord-tf-http-rota to "involve others" in the newly created ticket
  • this will allow the TF to be notified on updates and will make it easier to search for our tickets.

Duty rota

Initial testing: Cédric, Christophe, Fabrizio, Georgios, Oliver.

Thereafter: tbd.

Boilerplate

Hi,

The WLCG HTTP Deployment Task Force has been given the responsibility of promoting the deployment of HTTP interfaces to storage on the infrastructure. As part of this effort, we are contacting you to ask for your help in fixing the following service:

endpoint :

probe results :

If you click on the service whose name begins "webdav.HTTP-All" you'll find the detailed output from the probe.

You can find more information about the TF and hints for configuring your service at https://twiki.cern.ch/twiki/bin/view/LCG/HTTPTFSAMProbe.

Thanks,

The WLCG HTTP Deployment TF.

Ticketing Summaries

• Ticket Summary 20th Jan
• Ticket Summary 23rd Mar

Testing the process

The following sites have volunteered to participate in the first round:

• KIT
  • Atlas: f01-060-114-e.gridka.de
  • LHCb: f01-080-124-e.gridka.de, f01-080-126-e.gridka.de
• CNAF
  • Atlas: gridhttps-storm-atlas.cr.cnaf.infn.it
  • LHCb: ds-203-03-05.cr.cnaf.infn.it, ds-203-03-07.cr.cnaf.infn.it
• Imperial College
  • Atlas: gfe02.grid.hep.ph.ic.ac.uk
  • LHCb: gfe02.grid.hep.ph.ic.ac.uk
• Glasgow
  • Atlas: svr018.gla.scotgrid.ac.uk
• Bristol
  • Currently not in the endpoint lists provided by Atlas & LHCb

-- OliverKeeble - 2015-11-20