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 "2016-bidding/Marketplace and Resource allocation"

From EGIWiki
Jump to navigation Jump to search
Line 15: Line 15:
* maintenance of an up to date external service catalogue in the marketplace,  
* maintenance of an up to date external service catalogue in the marketplace,  
* handling of support and requests of service quotes,
* handling of support and requests of service quotes,
* user management for access to the long tail of science services, including but not limited to: validation of the user affiliation and user suspension when service quotas are exceeded, through the access.egi.eu service
* user management for access to the long tail of science services, including but not limited to: validation of the user affiliation and user suspension when service quotas are exceeded
* support to the creation of new VOs when necessary,
* activities for the configuration of the EGI infrastructure necessary to support access depending on the service selected
* brokering and matchmaking of compute/storage resources to meet the service request
* brokering and matchmaking of compute/storage resources to meet the service request
* SLA/OLA negotiation
* SLA/OLA negotiation
Line 34: Line 34:
* access.egi.eu
* access.egi.eu
* marketplace, relying on the finding and outcomes of the EGI-Engage project
* marketplace, relying on the finding and outcomes of the EGI-Engage project
The above-mentioned list of systems may be subject to changes and additional information on technical specification will be provided to the interested partners by December 2016.


Tools may require sub-components: e.g. authentication modules, database back-end, therefore services require multiple hosts (a good approximation is 2 for each service).
Tools may require sub-components: e.g. authentication modules, database back-end, therefore services require multiple hosts (a good approximation is 2 for each service).

Revision as of 14:27, 21 October 2016

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 and Resource allocation


Introduction

This activity 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

This activity will run the services and the processes that support the workflow from service discovery to access:

  • maintenance of an up to date external service catalogue in the marketplace,
  • handling of support and requests of service quotes,
  • user management for access to the long tail of science services, including but not limited to: validation of the user affiliation and user suspension when service quotas are exceeded
  • activities for the configuration of the EGI infrastructure necessary to support access depending on the service selected
  • brokering and matchmaking of compute/storage resources to meet the service request
  • SLA/OLA negotiation
  • management of communications with the user during service activation

Coordination

The activity will coordinate with:

  • EGI Technical outreach and user support for the VO SLA negotiation
  • EGI Operations for the support of the operational activities related to service provisioning and SLA monitoring
  • EGI Resource providers and other service providers for the integration of new resources and services in the Marketplace and long tail of science platform
  • Thematic platform providers and other EGI partners for the integration of their services in the Marketplace

Operations

The activity will take care of the daily operations and maintenance of the following tools:

  • e-grant.egi.eu
  • access.egi.eu
  • marketplace, relying on the finding and outcomes of the EGI-Engage project

The above-mentioned list of systems may be subject to changes and additional information on technical specification will be provided to the interested partners by December 2016.

Tools may require sub-components: e.g. authentication modules, database back-end, therefore services require multiple hosts (a good approximation is 2 for each service).

Maintenance

Bux fixing, proactive maintenance, and deployment of software updates.

Support

Support will be provided to the end users and to the service providers through dedicated GGUS support unit(s).

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: Medium (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service)

Effort

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