2019-bidding/IaaS Orchestration

From EGIWiki
Revision as of 14:25, 20 November 2019 by Enolfc (talk | contribs) (Technical description)
Jump to: navigation, search
Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security



EGI Services and Service Management Support menu: Bids Old Bids Performance

Go back to the EGI Services Bidding page.

Service component name: IaaS Orchestration

Technical description

IaaS Orchestration services automate the deployment of resources on IaaS cloud providers. These tools normally use some sort of domain specific language or script that defines your application deployment process, that is translated to a set of tasks that interact with the cloud services to start Virtual Machines, Storage, Networks and other kind of resources and services where your application will be installed and run.

Services in this category should :

  • integrate with EGI Check-in for authentication and authorisation of users
  • support the main IaaS APIs available in EGI Cloud (OpenStack, OpenNebula) and optionally support other IaaS APIs of commercial cloud providers (AWS, GCP, Azure)
  • integrate with EGI information discovery to facilitate the use of resources

Services in this category are: IM or terraform.

Coordination

This activity is responsible for the coordination of the service maintenance activities with EGI operations team and other technology providers for the EGI Core Infrastructure.

Operations

  • Daily running of the service.
  • 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:

  • Requirements gathering
  • 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 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 through the EGI Helpdesk.

Support hours: eight hours a day, Monday to Friday – excluding public holidays of the hosting organisation(s).

Service level targets

The deployment of the services must ensure:

  • Minimum availability/reliability: 90%/90%
  • Response to incident records in EGI Helpdesk within support hours: Medium.

Effort (EGI-related activities)

Expressions of interest planning an effort of about 3 Person Months/year would allow these services and activities to be addressed appropriately.

Effort (EOSC-related activities)

Partners are encouraged to submit details of activities and proposed costing of effort for EOSC related activities. This may include activities related to development of new functionality required by EOSC communities in addition to activities delivering services to these communities.