2019-bidding/platforms

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

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.