Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI Core activities:2013-bidding 2nd level support (community platform)"

From EGIWiki
Jump to navigation Jump to search
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
* Service name:
{{Template:Op menubar}} {{Core_services_menubar}}{{TOC_right}}
* Service category: Operations
'''Go back to the [[EGI_Core_Activities_Bidding|EGI Core Activities Bidding page]].'''
* Service type: Coordination, operation and maintenance
 


= Technical description =
'''Go back to the [[Core EGI Activities|Core EGI activity list]].'''


= Service level targets =


BACKUP
{{TOC_right}}
'''Go back to the [[Core_EGI_Activities|activity list]].'''
* Service name:
* Service name:
* Service category: Operations
* Service category: Operations
* Service type: Coordination, operation and maintenance
* Service type: Coordination, operation and maintenance


The ... is part of the EGI Core Infrastructure Platform ... which supports the daily operations of EGI.
Second level support of the community platforms deployed in EGI is part of the EGI support service delivered through GGUS.


= Introduction =
= Introduction =
EGI provides support to users and operators through a distributed helpdesk with central coordination (GGUS). The central helpdesk provides a single interface for support.


= Technical description =
= Technical description =
This service includes the following components.
Software-related tickets that reach the second level of support are analysed and if necessary are forwarded to 3rd line support units only when there are clear indications of a defect (in software, documentation, etc.). The involved partners provide a pool of experts available for deep analysis and solving the reported issues. This function includes the production of HOWTOs and document known issues of deployed software, and collaboration with operations in case of critical incidents.
 
== Coordination ==
This activity is responsible of the coordination of the system operation and upgrade activities with those partners that are in charge of operating other systems that depend on it.
 
== Support ==
Support through the EGI helpdesk about
 
Support about ... is out of scope and is part of activity ''2nd level support (core platform)''.


'''Support hours''': eight hours a day (9-17 CE(S)T), Monday to Friday – excluding public holidays of the hosting organization.
This service includes 2nd level technical support in the following areas. The list of products below just provides and indication; the list of products will be defined in collaboration with user, operations and federated cloud communities, and it is subject to periodic revisions to reflect changes in the technologies and service deployment models to be supported.


== Operation ==
ARGUS, VOMS, BDII and APEL 2nd level support is part of a separate task.
* Daily running of the system
* Testing and high availability configuration


== Maintenance ==
{|border="1" class="wikitable sortable" border="1
This activity includes:
|- style="background-color:darkgray;"
* core refactoring, bug fixing, proactive maintenance, improvement of the system
| '''Area'''
* coordination of software maintenance activities with other technology providers that provide software for the EGI Core Infrastructure or remote systems deployed by integrated and peer infrastructures that interoperate with the central EGI components of the system.
| '''Product'''
* requirements gathering
|- style="background-color:lightgray;"
| Security
|
* GridSite
* ProxyRenewal
* CANL
|-
| Batch systems
|
* Torque
* LSF
* GE
* Condor
|-style="background-color:lightgray;"
| Storage
|
* StoRM
* DPM
* dCache
|-
| Data
|
* LFC
|-style="background-color:lightgray;"
| Compute
|
* L&B
* CREAM
* WMS
|-
| Complete Grid Middleware stacks
|
* UNICORE
* ARC
* Globus
* QosCosGrid
* Desktop Grid middleware (IDGF)
|}


= Service level targets =
= Service level targets =
*Minimum availability/reliability: ..%/..%
*Response to incident records in GGUS within support hours: [[FAQ_GGUS-PT-QoS-Levels#Advanced_service| Advanced]] (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Advanced_service)
*Response to incident records in GGUS within support hours: [[FAQ_GGUS-PT-QoS-Levels#Medium_service| Medium]] (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service)

Latest revision as of 15:37, 6 June 2016

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


EGI Core services menu: Services PHASE I Services PHASE II Services PHASE III Bids Payments Travel procedure Performance



Go back to the EGI Core Activities Bidding page.


Go back to the Core EGI activity list.


  • Service name:
  • Service category: Operations
  • Service type: Coordination, operation and maintenance

Second level support of the community platforms deployed in EGI is part of the EGI support service delivered through GGUS.

Introduction

EGI provides support to users and operators through a distributed helpdesk with central coordination (GGUS). The central helpdesk provides a single interface for support.

Technical description

Software-related tickets that reach the second level of support are analysed and if necessary are forwarded to 3rd line support units only when there are clear indications of a defect (in software, documentation, etc.). The involved partners provide a pool of experts available for deep analysis and solving the reported issues. This function includes the production of HOWTOs and document known issues of deployed software, and collaboration with operations in case of critical incidents.

This service includes 2nd level technical support in the following areas. The list of products below just provides and indication; the list of products will be defined in collaboration with user, operations and federated cloud communities, and it is subject to periodic revisions to reflect changes in the technologies and service deployment models to be supported.

ARGUS, VOMS, BDII and APEL 2nd level support is part of a separate task.

Area Product
Security
  • GridSite
  • ProxyRenewal
  • CANL
Batch systems
  • Torque
  • LSF
  • GE
  • Condor
Storage
  • StoRM
  • DPM
  • dCache
Data
  • LFC
Compute
  • L&B
  • CREAM
  • WMS
Complete Grid Middleware stacks
  • UNICORE
  • ARC
  • Globus
  • QosCosGrid
  • Desktop Grid middleware (IDGF)

Service level targets