Difference between revisions of "GGUS:SNOW Interface FAQ"
Line 25: | Line 25: | ||
| ELOG Operations | | ELOG Operations | ||
| ELOG Operations | | ELOG Operations | ||
| | | Monitoring Service | ||
| ELOG Operations 3rd Line Support | | ELOG Operations 3rd Line Support | ||
|- | |- | ||
Line 65: | Line 65: | ||
| WLCG Data Management Monitoring | | WLCG Data Management Monitoring | ||
| WLCG Data Management Monitoring | | WLCG Data Management Monitoring | ||
| | | Monitoring Service | ||
| WLCG Data Management Monitoring 3rd Line Support | | WLCG Data Management Monitoring 3rd Line Support | ||
|- | |- | ||
| WLCG Experiment Probe Submission Framework | | WLCG Experiment Probe Submission Framework | ||
| WLCG Experiment Probe Submission Framework | | WLCG Experiment Probe Submission Framework | ||
| | | Monitoring Service | ||
| WLCG Experiment Probe Submission Framework 3rd Line Support | | WLCG Experiment Probe Submission Framework 3rd Line Support | ||
|- | |- | ||
| WLCG Google Earth Dashboard | | WLCG Google Earth Dashboard | ||
| WLCG Google Earth Dashboard | | WLCG Google Earth Dashboard | ||
| | | Monitoring Service | ||
| WLCG Google Earth Dashboard 3rd Line Support | | WLCG Google Earth Dashboard 3rd Line Support | ||
|- | |- | ||
| WLCG Grid Monitoring | | WLCG Grid Monitoring | ||
| WLCG Grid Monitoring | | WLCG Grid Monitoring | ||
| | | Monitoring Service | ||
| WLCG Grid Monitoring 3rd Line Support | | WLCG Grid Monitoring 3rd Line Support | ||
|- | |- | ||
| WLCG HammerCloud | | WLCG HammerCloud | ||
| WLCG HammerCloud | | WLCG HammerCloud | ||
| | | Monitoring Service | ||
| WLCG HammerCloud 3rd Line Support | | WLCG HammerCloud 3rd Line Support | ||
|- | |- | ||
| WLCG Infrastructure Monitoring | | WLCG Infrastructure Monitoring | ||
| WLCG Infrastructure Monitoring | | WLCG Infrastructure Monitoring | ||
| | | Monitoring Service | ||
| WLCG Infrastructure Monitoring 3rd Line Support | | WLCG Infrastructure Monitoring 3rd Line Support | ||
|- | |- | ||
| WLCG Job Monitoring | | WLCG Job Monitoring | ||
| WLCG Job Monitoring | | WLCG Job Monitoring | ||
| | | Monitoring Service | ||
| WLCG Job Monitoring 3rd Line Support | | WLCG Job Monitoring 3rd Line Support | ||
|- | |- | ||
| WLCG Network Monitoring | | WLCG Network Monitoring | ||
| WLCG Network Monitoring | | WLCG Network Monitoring | ||
| | | Monitoring Service | ||
| WLCG Network Monitoring 3rd Line Support | | WLCG Network Monitoring 3rd Line Support | ||
|} | |} | ||
<br> | <br> |
Revision as of 16:30, 15 November 2016
GGUS wiki / GGUS FAQ / GGUS Documentation / GGUS Helpdesk
Mapping table for GGUS support units, SNOW FE's, SNOW SE's and SNOW Assignment Groups
GGUS support unit | SNow Functional Element | SNow Service Element | SNow Assignment Group |
---|---|---|---|
Data Management Clients Development | Data Management Clients Development | GRID Development Service | Data Management Clients Development 3rd Line Support |
DPM Development | DPM Development | GRID Development Service | DPM Development 3rd Line Support |
ELOG Operations | ELOG Operations | Monitoring Service | ELOG Operations 3rd Line Support |
FTS Development | FTS Development | GRID Development Service | FTS Development 3rd Line Support |
Grid Monitoring | Grid Monitoring | GRID Infrastructure Monitoring Service | Grid Monitoring 3rd Line Support |
Information System Development | Information System Development | GRID Development Service | Information System Development 3rd Line Support |
LFC Development | LFC Development | GRID Development Service | LFC Development 3rd Line Support |
REBUS | REBUS | WLCG Resource Monitoring Service | REBUS 3rd Line Support |
ROC_CERN (user tickets) | CERN GRID 2nd Line Support | Tier-0 Support Service | CERN GRID 2nd Line Support 2nd Line Support |
ROC_CERN (team and alarm tickets) | CERN GRID 2nd Line Support | Tier-0 Support Service | CERN GRID 2nd Line Support 3rd Line Support |
WLCG Data Management Monitoring | WLCG Data Management Monitoring | Monitoring Service | WLCG Data Management Monitoring 3rd Line Support |
WLCG Experiment Probe Submission Framework | WLCG Experiment Probe Submission Framework | Monitoring Service | WLCG Experiment Probe Submission Framework 3rd Line Support |
WLCG Google Earth Dashboard | WLCG Google Earth Dashboard | Monitoring Service | WLCG Google Earth Dashboard 3rd Line Support |
WLCG Grid Monitoring | WLCG Grid Monitoring | Monitoring Service | WLCG Grid Monitoring 3rd Line Support |
WLCG HammerCloud | WLCG HammerCloud | Monitoring Service | WLCG HammerCloud 3rd Line Support |
WLCG Infrastructure Monitoring | WLCG Infrastructure Monitoring | Monitoring Service | WLCG Infrastructure Monitoring 3rd Line Support |
WLCG Job Monitoring | WLCG Job Monitoring | Monitoring Service | WLCG Job Monitoring 3rd Line Support |
WLCG Network Monitoring | WLCG Network Monitoring | Monitoring Service | WLCG Network Monitoring 3rd Line Support |
Data transfer from GGUS to SNow
Data transfer from GGUS to SNow is done using SOAP web services provided by SNow. As SNOW is queuing the SOAP requests GGUS does push a ticket to SNow only once. However a delay in the synchronization process may occur.
Due to incompatible data types in several fields GGUS implemented a wrapper tool for covering this issue. The wrapper tool is implemented in PHP.
Used operations are:
- insert,
- update,
- get.
Incidents and requests
If a GGUS 'incident' becomes a GGUS 'change request' nothing will change in the related SNow ticket. It will continue its life as an incident INC999999.
If a GGUS ticket becomes a 'Change request' in GGUS before transferring it to SNow, GGUS will create a "Request" in SNow.
The ticket synchronization will be the same as for incidents.
For further information on SNow SOAP API for requests see also Media:IT_SNowRequestFulfillment.pdf.
Field mapping for create operations from GGUS to SNow
GGUS system | SNow system |
---|---|
Web service (static value) | Contact Type |
Attachment Data | Attachment Data |
Attachment Name | Attachment Name |
Status
|
Incident State
|
Description | Comments |
Last Login (hidden) | Last Login (hidden) |
Last Modifier
|
Last Modifier
|
Support Unit |
Service Element |
Priority
|
Impact
|
Responsible Unit | Functional Element |
Responsible Unit + specific values
|
Assignment Group |
Short Description | Short Description |
Status | Incident State |
Target ID (hidden) | Sys_ID |
Field mapping for modify operations from GGUS to SNow
GGUS system | SNow system |
---|---|
Web service (static value) | Contact Type |
Attachment Data | Attachment Data |
Attachment Name | Attachment Name |
Status
NOTE! Status changes in GGUS may not be accepted by SNow system due to internal business rules. Hence the ticket status may be different in both systems. |
Incident State
|
Detailed Solution | Comments |
Internal Diary | Work Notes (internal) |
Last Login (hidden) | Last Login (hidden) |
Last Modifier
|
Last Modifier
|
|
Close Code |
Support Unit |
Service Element |
Public Diary | Comments |
Priority
|
Impact
|
Responsible Unit | Functional Element |
Responsible Unit + specific values
|
Assignment Group |
Target ID (hidden) | Sys_ID |
Data transfer from SNow to GGUS
Data transfer from SNow to GGUS is depending on SNow internal business rules. SNow tickets with visibility classified as "sensitive" are not visible via the ticket URL in GGUS history. Updates on sensitive tickets are not propagated to GGUS.
Technically the data transfer from SNow to GGUS is done using SOAP web services provided by GGUS system.
Incidents and requests
If a SNow 'incident' INC999999 becomes a SNow "Request" REQ888888, its number will be sent to GGUS and, in the same web service call, the GGUS field " Ticket category" will change value automatically (triggered by SNow) from 'incident' into 'change request'. GGUS will synchronize with the SNow request from now on.
Used operations are:
- TicketModify.
Field mapping for modify operations from SNow to GGUS
SNow system | GGUS system |
---|---|
Attachment Data | Attachment Data |
Attachment Name | Attachment Name |
Incident State
|
Status
|
Comments | Detailed Solution, Public Diary (depending on ticket status) |
Work Notes (internal) | Internal Diary |
Last Login (hidden) | Last Login (hidden) |
Last Modifier
|
Last Modifier
|
Impact
|
Priority
|
Short Description | Short Description |
Incident State | Status |
Attachments
Attachments are handled in a separate web service. The available operation is:
- AddAttachment