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
m (→‎Support: Clarify that support is via EGI Helpdesk)
(Replaced content with "{{Template:Deprecated}}")
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
{{Template:Op menubar}} {{TOC_right}} {{EGI_services_and_SM_support_menubar}}
{{Template:Deprecated}}
[[Category:Bidding]]
'''Go back to the [https://wiki.egi.eu/wiki/EGI_Services_and_Service_Management_Support:Bidding EGI Services 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/).
 
== 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 service catalogue (EOSC Portal Marketplace). The definition of the services in scope is defined by the EOSC-hub project service portfolio management process and follow-on projects. 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 and the white-label AAI for the EOSC Portal Marketplace.
 
== 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 enhanceEOSC 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 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 [https://github.com/EGI-Foundation 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 is provided the end users and to the service providers via EGI Helpdesk.
 
Support hours: eight hours a day, Monday to Friday – excluding public holidays of the hosting organisation(s).
 
The activity will also maintain the policies and documentation needed for the Marketplace.
 
== Service level targets  ==
 
Minimum availability: 99%
 
Minimum reliability: 99%
 
Response to incidents records in EGI Helpdesk within support hours: [[FAQ_GGUS-PT-QoS-Levels#Advanced_service|Advanced]].
 
== Effort ==
 
Partners are invited to submit details of activities and proposed costing of effort for this service and activity.

Latest revision as of 16:54, 20 November 2019

Alert.png This article is Deprecated and should no longer be used, but is still available for reasons of reference.