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/marketplace"

From EGIWiki
Jump to navigation Jump to search
(Software and ITSM compliance added)
m (→‎Operations: Req for AvCo plan added)
Line 30: Line 30:
*Provisioning of a high availability configuration
*Provisioning of a high availability configuration
*Standard backup policy for all relevant data
*Standard backup policy for all relevant data
*Monitoring of both hardware and software services including performance and capacity  
*Monitoring of both hardware and software services including performance and capacity
*Creating an Availability and Continuity Plan and implementing countermeasures to mitigate the risks defined in the related risk assessment


== Maintenance  ==
== Maintenance  ==

Revision as of 17:28, 5 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 Core Activities Bidding page. 

Service name: Marketplace Services

Introduction

The Marketplace Services will run the EGI systems and underpinning human processes necessary to enable discovery, selection and access to services of the EGI external catalogue (https://www.egi.eu/services/). This will comprise handling of service requests including pay-for-use services, authentication and authorization processes of long-tail of science, users brokering, compute/storage resource matchmaking and SLA/OLA negotiations.

Technical description

The Marketplace provides functionality necessary for bringing together offering and demand for making research. These functions include basic services for registering business entities, publishing and retrieving offerings and demands, search and discover offerings according to specific research communities requirements, submitting and managing service orders as well as lateral functions like review, rating and recommendation.

The service provide access and ordering capabilities for the following scopes:

  • Services of the EGI external service catalogue (EGI Marketplace). The definition of the services in scope is defined by the EGI Service Portfolio Management process and governed by the EGI Service and Solution Board.
  • Services of the EOSC-portal external service catalogue (EOSC Portal Marketplace). The definition of the services in scope is defined by the EOSC-hub project service portfolio management process. These services are publicized and offered through the EOSC Portal.
  • The EOSC Portal Marketplace is complemented by the EOSC Portal website, which provides information content about the EOSC initiative.

The Marketplace Services include various sub-components that have to be deployed in a high-availability configuration. Authentication modules have to be integrated with EGI Check-in service.

Coordination

The activity will coordinate with:

  • In the EOSC Portal context: the operators of other components of the EOSC Portal, e.g. partners of the e-InfraCentral project and follow-on projects, for coordinated joint support to users and service providers.
  • In the EGI context: the managers of relevant EGI Service Management System Processes like Service Portfolio Management, SLA Management, Service Report Management, Customer Relationship Management, and Supplier, Federation Member Relationship Management.
  • Service providers and technology providers for the integration of services into the Marketplace.

Operations

  • Daily running and maintenance of the Marketplace
  • Provisioning of a high availability configuration
  • Standard backup policy for all relevant data
  • Monitoring of both hardware and software services including performance and capacity
  • Creating an Availability and Continuity Plan and implementing countermeasures to mitigate the risks defined in the related risk assessment

Maintenance

  • Bux fixing, proactive maintenance, and deployment of software updates.
  • Requirements gathering
  • 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 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

Support is provided the end users and to the service providers via EGI Service Desk Support Unit: Marketplace (http://helpdesk.egi.eu/).

Support hours: eight hours a day, Monday to Friday – excluding public holidays of all organizations involved in the provisioning of the services.

The activity will also maintain the policies and documentation needed for the Marketplace.

Service level targets

Response to incident records in GGUS within support hours: Advanced (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Advanced_service)

Response to service requests in GGUS within support hours: Advanced (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Advanced_service)

Availability of the technical services: Availability 90%, Reliability 95%

Effort (TBD)

Bids planning a total effort of ... Person Months/year would allow these services and activities to be addressed appropriately.