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
(Created page with "{{Template:Op menubar}}{{Core_services_menubar}} {{TOC_right}} '''Go back to the [[EGI_Services_and_Service_Management_Support:Bidding|EGI Services and Service Management Support...")
 
Line 6: Line 6:
== Introduction ==
== Introduction ==


EGI Storage and Computing services provider the baseline computing and storage resources to deliver research-oriented platforms. Examples of these platforms are the [https://www.egi.eu/use-cases/scientific-applications-tools/ Scientific Applications and tools listed in the EGI website], the [https://www.egi.eu/services/applications-on-demand/ EGI Notebooks], or the [https://www.egi.eu/services/applications-on-demand/ EGI Applications on Demand] services. This bid welcomes any platform compatible with the EGI Computing and Storage services and capable of authenticating users with Check-in.


== Technical description ==


== Technical description ==





Revision as of 15:00, 15 November 2019

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 Services and Service Management Support bidding page.

Compute Plaftorms

Introduction

EGI Storage and Computing services provider the baseline computing and storage resources to deliver research-oriented platforms. Examples of these platforms are the Scientific Applications and tools listed in the EGI website, the EGI Notebooks, or the EGI Applications on Demand services. This bid welcomes any platform compatible with the EGI Computing and Storage services and capable of authenticating users with Check-in.

Technical description

Coordination

Operations

Maintenance

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 community.
    • Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the 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 mature and well maintained ITSM process that are key to support the services they provide.

Support

Service level targets

Effort (EGI-related activities)

Effort (EOSC-related activities)