Difference between revisions of "Instructions for centrally-provided services Service Providers"
Line 1: | Line 1: | ||
{{Template:Op menubar}} {{Template:Tools menubar}} {{TOC_right}} | {{Template:Op menubar}} {{Template:Tools menubar}} | ||
{{Template:Under_construction}} | |||
{{TOC_right}} | |||
<!--[if gte mso 9]><xml> | Container for instructions for EGI tools developers<br> <!--[if gte mso 9]><xml> | ||
<o:OfficeDocumentSettings> | <o:OfficeDocumentSettings> | ||
<o:AllowPNG/> | <o:AllowPNG/> | ||
Line 12: | Line 12: | ||
</xml><![endif]--> | </xml><![endif]--> | ||
=== General<br> === | === General<br> === | ||
*name | *name | ||
*provide support email | *provide support email | ||
*point a leader | *point a leader | ||
*EGI url | *EGI url | ||
*Register in GOC DB under Egi.eu NGI | *Register in GOC DB under Egi.eu NGI | ||
<br> | |||
=== Requirements gathering and testing<br> === | |||
*add category in requirements RT tracker and create RT dashboard | |||
*add category in requirements RT tracker and create RT dashboard | |||
*Test instance url | *Test instance url | ||
<br> | |||
=== Monitoring<br> === | |||
*Ava/rel threshold defined with EGI Operations<br> | |||
*Ava/rel threshold defined with EGI Operations<br> | |||
*Develope monitoring probe <br> | *Develope monitoring probe <br> | ||
=== Documentation<br> === | === Documentation<br> === | ||
*wiki page with '''Release schedule, ''' '''Release notes''', '''Roadmap, ''' '''Related OLA''', <br> | *wiki page with '''Release schedule, ''' '''Release notes''', '''Roadmap, ''' '''Related OLA''', <br> | ||
Line 40: | Line 40: | ||
=== Suppor - incident handling === | === Suppor - incident handling === | ||
*declare quality of support | |||
*Support is provided in following language: English | |||
*declare quality of support | |||
*Support is provided in following language: English | |||
*create GGUS SU | *create GGUS SU | ||
*<span>Monday and Friday</span> | *<span>Monday and Friday</span> | ||
*<span>8 h per day</span> | *<span>8 h per day</span> | ||
Support is provided via the GGUS portal [GGUS], which is the single point of contact for infrastructure users to access the EGI Service Desk. The EGI Service Desk within GGUS is organized in Support Units. Every Support Unit is responsible for one or more services. The number and definition of the EGI Support Units in GGUS is not regulated by this OLA and can change at any time to fulfil the EGI Incident and Problem Management requirements.<br> | Support is provided via the GGUS portal [GGUS], which is the single point of contact for infrastructure users to access the EGI Service Desk. The EGI Service Desk within GGUS is organized in Support Units. Every Support Unit is responsible for one or more services. The number and definition of the EGI Support Units in GGUS is not regulated by this OLA and can change at any time to fulfil the EGI Incident and Problem Management requirements.<br> | ||
=== Development<br> === | === Development<br> === | ||
broadcast <br> | broadcast <br> | ||
=== Planed maintenance windows or interruptions<!--[if gte mso 9]><xml> | === Planed maintenance windows or interruptions<!--[if gte mso 9]><xml> | ||
Line 61: | Line 59: | ||
</xml><![endif]--> === | </xml><![endif]--> === | ||
Downtime in GOC DB | Downtime in GOC DB | ||
To be communicated in a timely manner i.e. 24 hours before, to the Customer through the Broadcast Tool [BT]. Typical duration is up to 24 hours otherwise needs to be justified.<br> | To be communicated in a timely manner i.e. 24 hours before, to the Customer through the Broadcast Tool [BT]. Typical duration is up to 24 hours otherwise needs to be justified.<br> | ||
Line 78: | Line 76: | ||
The following rules for information security and data protection apply:<br>• The Provider must define and abide by an information security and data <br>protection policy related to the service being provided. <br>• This must meet all requirements of any relevant EGI policies or procedures [POL] and also must be compliant with the relevant national legislation.<br><br> | The following rules for information security and data protection apply:<br>• The Provider must define and abide by an information security and data <br>protection policy related to the service being provided. <br>• This must meet all requirements of any relevant EGI policies or procedures [POL] and also must be compliant with the relevant national legislation.<br><br> | ||
<br> | |||
[[Category:Tools]] | [[Category:Tools]] | ||
Revision as of 13:12, 18 November 2014
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Tools menu: | • Main page | • Instructions for developers | • AAI Proxy | • Accounting Portal | • Accounting Repository | • AppDB | • ARGO | • GGUS | • GOCDB |
• Message brokers | • Licenses | • OTAGs | • Operations Portal | • Perun | • EGI Collaboration tools | • LToS | • EGI Workload Manager |
This page is under construction. |
Container for instructions for EGI tools developers
General
- name
- provide support email
- point a leader
- EGI url
- Register in GOC DB under Egi.eu NGI
Requirements gathering and testing
- add category in requirements RT tracker and create RT dashboard
- Test instance url
Monitoring
- Ava/rel threshold defined with EGI Operations
- Develope monitoring probe
Documentation
- wiki page with Release schedule, Release notes, Roadmap, Related OLA,
Suppor - incident handling
- declare quality of support
- Support is provided in following language: English
- create GGUS SU
- Monday and Friday
- 8 h per day
Support is provided via the GGUS portal [GGUS], which is the single point of contact for infrastructure users to access the EGI Service Desk. The EGI Service Desk within GGUS is organized in Support Units. Every Support Unit is responsible for one or more services. The number and definition of the EGI Support Units in GGUS is not regulated by this OLA and can change at any time to fulfil the EGI Incident and Problem Management requirements.
Development
broadcast
Planed maintenance windows or interruptions
Downtime in GOC DB
To be communicated in a timely manner i.e. 24 hours before, to the Customer through the Broadcast Tool [BT]. Typical duration is up to 24 hours otherwise needs to be justified.
This manual provides information on how to manage central operational tool unscheduled downtimes. |
https://wiki.egi.eu/wiki/MAN04_Tool_Intervention_Management
Security
The following rules for information security and data protection apply:
• The Provider must define and abide by an information security and data
protection policy related to the service being provided.
• This must meet all requirements of any relevant EGI policies or procedures [POL] and also must be compliant with the relevant national legislation.