Difference: HTTPTFProcess (1 vs. 19)

Revision 192016-03-23 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 71 to 71
 

Ticketing Summaries

Changed:
<
<
Ticket Summary 20th Jan
>
>
 

Testing the process

Revision 182016-02-24 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 26 to 26
  Continuous: respond to ticket updates.
Changed:
<
<
To open a ticket:
>
>
To open a ticket:
 
  • check no outstanding ticket for that endpoint and that VO. Search for:
    • Involved support: wlcg-ops-coord-tf-http-rota

Revision 172016-01-19 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 69 to 69
  The WLCG HTTP Deployment TF.
Added:
>
>

Ticketing Summaries

Ticket Summary 20th Jan

 

Testing the process

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

Revision 162016-01-12 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 52 to 52
 

Boilerplate

Added:
>
>
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:
Line: 59 to 61
  probe results :
Added:
>
>
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,

Revision 152016-01-08 - GeorgiosBItzes

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 34 to 34
 
    • Keyword: endpoint
    • Creation date: any
  • create ticket with standard text
Changed:
<
<
    • Notification mode - on every change
    • Subject - HTTP support for endpoint
>
>
    • Subject - HTTP support for endpoint
 
    • Concerned VO - VO
    • Affected Site - See this page
    • Ticket category - Incident

Revision 142016-01-07 - GeorgiosBItzes

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 34 to 34
 
    • Keyword: endpoint
    • Creation date: any
  • create ticket with standard text
Added:
>
>
    • Notification mode - on every change
 
    • Subject - HTTP support for endpoint
    • Concerned VO - VO
    • Affected Site - See this page

Revision 132016-01-07 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 9 to 9
 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.
Changed:
<
<
  • In general the "services of host" summary page should be sent to the site (for example, this page
>
>
  • In general the "services of host" summary page should be sent to the site (for example, this page).
 

Test results

Line: 29 to 29
 To open a ticket:

  • check no outstanding ticket for that endpoint and that VO. Search for:
Changed:
<
<
    • Involve others: wlcg-ops-coord-tf-http-rota
    • Notified site:
>
>
    • Involved support: wlcg-ops-coord-tf-http-rota
    • Notified site: sitename
    • Keyword: endpoint
 
    • Creation date: any
  • create ticket with standard text
Changed:
<
<
    • ensure "affected VO" is filled in - one ticket per VO.
    • ensure the "affected site" is filled in (see below)
    • ticket category - Incident
    • type of issue - storage systems
    • notify site - choose site (again).
>
>
    • 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.
Line: 63 to 65
  The WLCG HTTP Deployment TF.
Deleted:
<
<

Finding the right site name

 
Deleted:
<
<

ldapsearch

ldapsearch -x -H ldap://lcg-bdii.cern.ch:2170 -b o=glue '(GLUE2ServiceID=*endpoint.fqdn*)' GLUE2ServiceAdminDomainForeignKey

If the above search doesn't return a result, try with just the domain (rather than full endpoint).

GOCdb

wget -O - --no-check-certificate "https://goc.egi.eu/gocdbpi/public/?method=get_service&hostname=endpoint.fqdn"

 

Testing the process

Revision 122016-01-06 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Objective

Changed:
<
<
The objective is to get all the sites green. "Read only" sites with the appropriate standard file are shown as green in the summary pages.
>
>
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.
Line: 20 to 20
 

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

Changed:
<
<
the TF if necessary. All interaction with a site related to a particular VO should be on the same ticket (until closed).
>
>
the TF if necessary. All interaction with a site related to a particular endpoint and VO should be on the same ticket (until closed).
 
Changed:
<
<
Once per week: review non green sites and open a ticket against any which do not have one open.
>
>
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:

Changed:
<
<
  • check no outstanding ticket for that site and that VO. Search for:
>
>
  • check no outstanding ticket for that endpoint and that VO. Search for:
 
    • Involve others: wlcg-ops-coord-tf-http-rota
    • Notified site:
    • Creation date: any

Revision 112015-12-16 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Objective

Changed:
<
<
The objective is to get all the sites green. "Read only" sites with the appropriate standard file in place are also acceptable.
>
>
The objective is to get all the sites green. "Read only" sites with the appropriate standard file are shown as green in the summary pages.
  Notes:
Changed:
<
<
  • The "state" field in the test results is not relevant to us and is the result of a ping test
  • The results of tests unrelated to the TF are also displayed - when the service is in pre-prod we'll tackle how to make this easier to navigate
>
>
  • 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

Revision 102015-12-16 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 12 to 12
 

Test results

Changed:
<
<
Atlas: https://etf-atlas-dev.cern.ch/etf/check_mk/index.py
>
>
Atlas results
 
Changed:
<
<
LHCb: https://etf-lhcb-dev.cern.ch/etf/check_mk/index.py
>
>
LHCb:results
 

Process

Revision 92015-11-30 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 19 to 19
 

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

Changed:
<
<
the TF if necessary. All interaction with a site should be on the same ticket (until closed).
>
>
the TF if necessary. All interaction with a site related to a particular VO should be on the same ticket (until closed).
  Once per week: review non green sites and open a ticket against any which do not have one open.
Line: 27 to 27
  To open a ticket:
Changed:
<
<
  • check no outstanding ticket for that site. Search for:
>
>
  • check no outstanding ticket for that site and that VO. Search for:
 
    • Involve others: wlcg-ops-coord-tf-http-rota
    • Notified site:
    • Creation date: any
  • create ticket with standard text
Changed:
<
<
    • ensure "affected VO" is filled in
>
>
    • ensure "affected VO" is filled in - one ticket per VO.
 
    • ensure the "affected site" is filled in (see below)
    • ticket category - Incident
    • type of issue - storage systems

Revision 82015-11-25 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 90 to 90
 
  • Glasgow
    • Atlas: svr018.gla.scotgrid.ac.uk
  • Bristol
Changed:
<
<
    • Atlas:
>
>
    • Currently not in the endpoint lists provided by Atlas & LHCb
  -- OliverKeeble - 2015-11-20

Revision 72015-11-25 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 68 to 68
  ldapsearch -x -H ldap://lcg-bdii.cern.ch:2170 -b o=glue '(GLUE2ServiceID=*endpoint.fqdn*)' GLUE2ServiceAdminDomainForeignKey
Changed:
<
<
If the above search doesn't return a result, you can still find the site name in the dn string, GLUE2DomainID.
>
>
If the above search doesn't return a result, try with just the domain (rather than full endpoint).
 

GOCdb

wget -O - --no-check-certificate "https://goc.egi.eu/gocdbpi/public/?method=get_service&hostname=endpoint.fqdn"

Added:
>
>

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
    • Atlas:
 

-- OliverKeeble - 2015-11-20 \ No newline at end of file

Revision 62015-11-25 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Objective

Changed:
<
<
The objective is to get all the sites green. The way the tests are set up, even "read only" sites with the appropriate standard file in place can appear green.
>
>
The objective is to get all the sites green. "Read only" sites with the appropriate standard file in place are also acceptable.
  Notes:
  • The "state" field in the test results is not relevant to us and is the result of a ping test

Revision 52015-11-24 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Added:
>
>

Objective

The objective is to get all the sites green. The way the tests are set up, even "read only" sites with the appropriate standard file in place can appear green.

Notes:

  • The "state" field in the test results is not relevant to us and is the result of a ping test
  • The results of tests unrelated to the TF are also displayed - when the service is in pre-prod we'll tackle how to make this easier to navigate

Test results

Atlas: https://etf-atlas-dev.cern.ch/etf/check_mk/index.py

LHCb: https://etf-lhcb-dev.cern.ch/etf/check_mk/index.py

 

Process

Changed:
<
<
The TF has a GGUS Support Unit (of the same name). All interaction with a site should be on the same ticket (until closed).
>
>
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 should be on the same ticket (until closed).

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

Continuous: respond to ticket updates.

To open a ticket:

 
Changed:
<
<
  • check no outstanding ticket for that site
>
>
  • check no outstanding ticket for that site. Search for:
    • Involve others: wlcg-ops-coord-tf-http-rota
    • Notified site:
    • Creation date: any
 
  • create ticket with standard text
Deleted:
<
<
    • cc to: wlcg-ops-coord-tf-http-rota
 
    • ensure "affected VO" is filled in
    • ensure the "affected site" is filled in (see below)
    • ticket category - Incident
    • type of issue - storage systems
    • notify site - choose site (again).
    • leave other fields as they are
Added:
>
>
  • 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

Revision 42015-11-24 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 8 to 8
 
  • check no outstanding ticket for that site
  • create ticket with standard text
Changed:
<
<
    • subject: HTTPTF ... (this will help with searching tickets)
    • notification mode - "on every change"
>
>
    • cc to: wlcg-ops-coord-tf-http-rota
 
    • ensure "affected VO" is filled in
    • ensure the "affected site" is filled in (see below)
    • ticket category - Incident

Revision 32015-11-24 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Line: 8 to 8
 
  • check no outstanding ticket for that site
  • create ticket with standard text
Added:
>
>
    • subject: HTTPTF ... (this will help with searching tickets)
    • notification mode - "on every change"
 
    • ensure "affected VO" is filled in
    • ensure the "affected site" is filled in (see below)
    • ticket category - Incident
Line: 38 to 40
 

Finding the right site name

Added:
>
>

ldapsearch

 ldapsearch -x -H ldap://lcg-bdii.cern.ch:2170 -b o=glue '(GLUE2ServiceID=*endpoint.fqdn*)' GLUE2ServiceAdminDomainForeignKey
Changed:
<
<
ldapsearch -x -H ldap://lcg-bdii.cern.ch:2170 -b o=glue '(GLUE2ServiceID=*endpoint.fqdn*)' 1.1 # Use the GLUE2DomainID attribute in the DN
>
>
If the above search doesn't return a result, you can still find the site name in the dn string, GLUE2DomainID.

GOCdb

  wget -O - --no-check-certificate "https://goc.egi.eu/gocdbpi/public/?method=get_service&hostname=endpoint.fqdn"

Revision 22015-11-20 - OliverKeeble

Line: 1 to 1
 
META TOPICPARENT name="HTTPDeployment"
Deleted:
<
<
 

Process for contacting sites

Process

Line: 10 to 9
 
  • check no outstanding ticket for that site
  • create ticket with standard text
    • ensure "affected VO" is filled in
Changed:
<
<
    • ensure the "affected site" is filled in
      • ldapsearch -x -H ldap://lcg-bdii.cern.ch:2170 -b o=glue  '(GLUE2ServiceID=[endpoint])' GLUE2ServiceAdminDomainForeignKey
>
>
    • ensure the "affected site" is filled in (see below)
 
    • ticket category - Incident
    • type of issue - storage systems
    • notify site - choose site (again).
Added:
>
>
    • leave other fields as they are

Duty rota

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

Thereafter: tbd.

 

Boilerplate

The WLCG HTTP Deployment Task Force has been given the responsibility of promoting the deployment of HTTP interfaces to storage on the infrastructure.

Changed:
<
<
As part of this effort, we are contacting you to ask for your help in fixing the following endpoint: whose probe results can be found here: You can find more information about the TF and hints for configuring your service here: You can reassign this to the TF SU if you like.
>
>
As part of this effort, we are contacting you to ask for your help in fixing the following service:

endpoint:

probe results:

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.

Finding the right site name

ldapsearch -x -H ldap://lcg-bdii.cern.ch:2170 -b o=glue '(GLUE2ServiceID=*endpoint.fqdn*)' GLUE2ServiceAdminDomainForeignKey

ldapsearch -x -H ldap://lcg-bdii.cern.ch:2170 -b o=glue '(GLUE2ServiceID=*endpoint.fqdn*)' 1.1 # Use the GLUE2DomainID attribute in the DN

wget -O - --no-check-certificate "https://goc.egi.eu/gocdbpi/public/?method=get_service&hostname=endpoint.fqdn"

 

Revision 12015-11-20 - OliverKeeble

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="HTTPDeployment"

Process for contacting sites

Process

The TF has a GGUS Support Unit (of the same name). All interaction with a site should be on the same ticket (until closed).

  • check no outstanding ticket for that site
  • create ticket with standard text
    • ensure "affected VO" is filled in
    • ensure the "affected site" is filled in
      • ldapsearch -x -H ldap://lcg-bdii.cern.ch:2170 -b o=glue  '(GLUE2ServiceID=[endpoint])' GLUE2ServiceAdminDomainForeignKey
    • ticket category - Incident
    • type of issue - storage systems
    • notify site - choose site (again).

Boilerplate

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 endpoint: whose probe results can be found here: You can find more information about the TF and hints for configuring your service here: You can reassign this to the TF SU if you like.

-- OliverKeeble - 2015-11-20

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback