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/messaging-service"

From EGIWiki
Jump to navigation Jump to search
m (→‎Support: rephrase support hours, use Helpdesk.)
m (Protected "2019-bidding/messaging-service" ([edit=bidding] (indefinite)))
(No difference)

Revision as of 14:59, 20 November 2019

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 name: Messaging service

Technical description

The Messaging service is a backend service for EGI operational tools that need to use a messaging functionality for message communications purposes (i.e. Argo monitoring, APEL, the Operations Portal, Information System, EGI Fedcloud etc.). The service component to be provided needs to provide scalability and redundancy with its topology in order to keep up with the message load produced by the operations tools. The scalability of the service should be adjusted to support the amount of monitoring and accounting data produced by the sites that are part of the EGI Federation of High Throughput Computing, storage and cloud services.

Currently the number of service endpoints is about 3,000 and the number of resource centres is about 260.

Coordination

This activity is responsible for

  • the coordination of the system operations and upgrade activities with those partners that are in charge of operating other systems that depend on it to ensure continuity of the service.
  • requirements gathering.

Operations

  • Daily running of the system in high availability configuration
  • Maintenance of probes to test the functionality of the service
  • Provisioning of a high availability configuration which includes at least 3 instances running behind a HAproxy configuration in High Availability Mode
  • Creating an Availability and Continuity Plan and implementing countermeasures to mitigate the risks defined in the related risk assessment

Maintenance

  • Bug fixing and proactive maintenance of the software
  • Changes in the system must be rolled in production in a controlled way in order to avoid service disruption.

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 of message production, exchange and consumption process through the EGI Helpdesk.

Support is provided to the operators of systems that rely on the EGI Messaging service Network capability.

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: 99%/99%
  • Response to incident records in EGI Helpdesk within support hours: Medium.

Effort (EGI-related activities)

Bids planning a effort up to 4 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.