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 "2019-bidding/platforms"

From EGIWiki
Jump to navigation Jump to search
(Replaced content with "{{Template:Deprecated}}")
 
Line 1: Line 1:
{{Template:Op menubar}} {{TOC_right}} {{EGI_services_and_SM_support_menubar}}
{{Template:Deprecated}}
[[Category:Bidding]]
'''Go back to the [https://wiki.egi.eu/wiki/EGI_Services_and_Service_Management_Support:Bidding EGI Services Bidding page].'''
 
= Compute Plaftorms =
 
== Introduction ==
 
EGI Storage and Computing services provide the baseline computing and storage infrastructure on which higher level, but generic platforms can be hosted. Examples of such generic platforms are the [https://www.egi.eu/services/applications-on-demand/ EGI Notebooks] or the DIRAC-based [https://www.egi.eu/services/workload-manager/ EGI Workload Manager]. This call invites platforms that are compatible with the EGI Computing and Storage services, provide high level interfaces/capabilities on top of these for any scientific discipline, and are using the EGI Check-in system for user authentication.
 
== Technical description ==
 
Platforms must comply with the following requirements:
* The platform is relevant for any scientific discipline.
* The platform can exploit computing and storage resources from EGI services. Ideally the platform should dynamically allocate those resources by using the services APIs.
* The platform integrates with Check-in for authenticating users, and delegates those identities as needed for interacting with other EGI services on behalf of the users.
* Provide probes for monitoring the Availability and Reliability of the platform with the EGI Monitoring service.
 
The platform should be offered as a centrally managed instance that will be run by the project and will provide access to ‘long-tail of science’ type use cases on ‘generic clouds’ for any user, and to thematic groups on the ‘thematic clouds’. Additionally, the platform provider should be capable of setting up dedicated instances to specific communities as needed upon request.
 
Optionally, platforms should also be available as ready-to-use artefacts (VM images, containers, helm charts) in the EGI AppDB, docker or Helm repositories alongside with complete documentation for the deployment and operation of the platform so dedicated local instances can be setup on cloud providers as needed.
 
Below follows a list of possible platforms that are expected to respond to this call (a single application may cover multiple of these platforms in a single response):
*Workload manager (DIRAC): A job manager system compatible with EGI HTC and Cloud resources.
* EC3: A VM orchestrator system compatible with EGI Cloud resources
* Notebooks (JupyterHub): A web-based interface to define and run computational notebooks.
* Binder: A web-based environment to reproduce and/or recreate computational environments as notebooks.
* FutureGateway Science Gateway (FGSG): a web-based gateway that provides general purpose scientific applications on demand.
* DODAS: Can turn IaaS cloud sites into ‘batch job execution’ facilities.
* PROMINENCE: Can turn IaaS cloud sites into ‘batch job execution’ facilities and can support clouds to burst out jobs to other clouds.
 
== Coordination ==
 
This activity is responsible for the coordination of the service maintenance activities with the EGI operations team and other relevant technology providers.
 
== Operations ==
 
*Daily running of the service instances. (a catch-all instance and community instances upon request)
*Provisioning of a high availability configuration.
*Creating an Availability and Continuity Plan and implementing countermeasures to mitigate the risks defined in the related risk assessment.
 
== Maintenance ==
 
This activity includes:
*Bug fixing, proactive maintenance, improvement of the system.
*Maintenance of probes to test the functionality of the service.
*Documentation.
 
== Software Compliance ==
 
* Unless explicitly agreed, software being used and developed to provide the service should:
** Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...).
*** The license should provide unlimited access rights to the EGI Foundation and EGI federation member organisations.
** Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the [https://github.com/EGI-Foundation EGI organisation in GitHub].) All releases should be appropriately tagged.
** Adopt best practices:
*** Defining and enforcing code style guidelines.
*** Using Semantic Versioning.
*** Using a Configuration Management frameworks such as Ansible.
*** Taking security aspects into consideration through at every point in time.
*** Having automated testing in place.
*** Using code reviewing.
*** Treating documentation as code.
**** Documentation should be available for Developers, administrators and end users.
 
== IT Service Management compliance ==
 
* Key staff who deliver services should have foundation or basic level ITSM training and certification.
** ITSM training and certification could include FitSM, ITIL, ISO 20000 etc.
* Key staff and service owners should have advanced/professional training and certification covering the key processes for their services.
* Providers should have clear interfaces with the EGI SMS processes and provide the required information.
* Providers should commit to improving their management system used to support the services they provide.
 
== Support ==
 
* Support is provided through the EGI Helpdesk.
* Support hours: eight hours a day, Monday to Friday – excluding public holidays of the hosting organisation(s).
 
== Service level targets ==
 
Catch-all instance must have at least 95% A/R on a monthly basis. Dedicated instances A/R targets will be defined in additional SLA/OLAs.
 
*Response to incident records in EGI Helpdesk within support hours: [[FAQ_GGUS-PT-QoS-Levels#Medium_service|Medium]].

Latest revision as of 17:04, 20 November 2019

Alert.png This article is Deprecated and should no longer be used, but is still available for reasons of reference.