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.

EGI Core activities:PHASE II

From EGIWiki
Jump to navigation Jump to search
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
Alert.png This page is Deprecated and should no longer be used, but is still available for reasons of reference. Please use the new page https://confluence.egi.eu/display/EGIBID/EGI+Bidding+Home


This page will list the EGI.eu core activities provided by EGI.eu partners for the period: May 2016 - December 2017

Proposals are in evaluation phase.

List of the bidding activities

Please, find the information about the biddings in the Bidding page


Documentation:

Each activity is obligated to deliver every 6 months report.

Contact:

  • internal communication across activity leaders: core-egi-activities [at] mailman.egi.eu
  • to contact activity separately please use GGUS Support Unit
  • in case of any general questions: operations [at] egi.eu

Service/Activities

Message brokers

Overview

The message broker network is a fundamental part of the operations infrastructure ensuring message exchange for monitoring, the operations dashboard and accounting. As such it is a critical core infrastructure platform service component whose continuity and high availability configuration must be ensured.

Consortium: GRNET, SRCE

Contact: Christos Kanellopoulos (skanct@grnet.gr), Kostas Koumantaros (kkoum@grnet.gr)

Accounting repositories and portal

Overview

The Accounting Infrastructure provides storage and access to usage information across the EGI Federation. At a central level it includes the repositories for the persistent storage of usage records and a visualization portal for users and resource providers. The central databases are populated through individual usage records published by the Resource Centres, or through the publication of summarised usage records.

Consortium: STFC, CESGA

Contact: Stuart Pullinger (stuart.pullinger@stfc.ac.uk), Carlos Fernández (carlosf@cesga.es), Iván Díaz (idiaz@cesga.es)

Monitoring services

Overview

Central systems are needed for accessing and archiving infrastructure monitoring results of the services provided at many levels (Resource Centres, Operations Centres and EGI.EU), for the generation of service level reports, and for the central monitoring of EGI.eu operational tools and other central monitoring needs.

Infrastructure operations require in some cases monitoring activities to be conducted centrally to support specific service and capability monitoring, like UserDN publishing in accounting records, GLUE information validation, and of software versions of deployed middleware.

Consortium: GRNET SRCE CNRS

Contact: Christos Kanellopoulos (skanct@grnet.gr), Kostas Koumantaros (kkoum@grnet.gr)

Service registry (GOCDB)

Overview

EGI relies on a central registry (GOCDB) to record information about different entities such as the Operations Centres, the Resource Centres, service endpoints and the contact information and roles of people responsible for operations at different levels. GOCDB is a source of information for many other operational tools, such as the broadcast tool, the Aggregated Topology Provider, the Accounting Portal, etc.

Consortium: STFC

Contact: David Meredith (david.meredith@stfc.ac.uk)

Services for AAI

Overview

Services and activities are needed for a flexible multi-technology AAI platform for user authentication and authorization.

Consortium: GRNET

Contact: Christos Kanellopoulos (skanct@grnet.gr), Kostas Koumantaros (kkoum@grnet.gr)

Activities and services for the long tail of science

Overview

Small research collaboration lacking ICT resources and tools need dedicated processes and support systems to easily gain access to services and expertise provided at a European level. The EGI services for the long tail of science aim at reducing the entry barriers by streamlining activities like user management, resource allocation and SLA negotiation.

Consortium: Vrije Universiteit Brussel

Contact: Stephane GERARD stgerard@vub.ac.be

E-GRANT services hosting and technical operations

Overview

This activity will host and technically operate the services to support the resource allocation tool (e-grant.egi.eu) in the version accepted and deployed to the production.

Consortium: CYFRONET

Contact: Tomasz Szepieniec (t.szepieniec@cyfronet.pl)

Helpdesk (GGUS)

Overview

EGI provides support to users and operators through a distributed helpdesk with central coordination (GGUS). The central helpdesk provides a single interface for support. The central system is interfaced to a variety of other ticketing systems at the NGI level in order to allow a bi-directional exchange of tickets.

Consortium: KIT

Contact: Guenter Grein (guenter.grein@kit.edu)


Helpdesk human support

Overview

EGI provides support to users and operators through a distributed helpdesk with central coordination (GGUS). The central helpdesk provides a single interface for support. The helpdesk support activities are grouped in 1st and 2nd level support.

Consortium: CESNET (CZ) CYFRONET

Contact: CESNET: Zdeněk Šustr (sustr4@cesnet.cz) Petr Hanousek (petr.hanousek@cesnet.cz) CYFRONET: Tomasz Szepieniec (t.szepieniec@cyfronet.pl) Patryk Lasoń (p.lason@cyfronet.pl)

Collaboration tools

Overview

Collaborations tools are services needed by the EGI back-office and supporting EGI collaboration.

Consortium: CESNET (CZ)

Contact: Martin Kuba (makub@ics.mun i.cz) (main and administrative contact) Michal Stava (michal.stava@cesnet.cz)

Application DB (virtual appliances and applications library)

Overview

The EGI Applications Database (AppDB) is a central service that provides:

  • Information about software solutions in the form of native software products and virtual appliances, linking the programmers and the scientists who are involved, and the publications derived from the registered solutions
  • The tools for the distribution of the virtual machine images in the cloud sites part of the the federated cloud

Consortium: GRNET

Contact: Kostas Koumantaros (kkoum@grnet.gr), Marios Chatziangelou (mhaggel@iasa.gr)

Operations Portal

Overview

EGI.eu provides a central portal for the operations community that offers a bundle of different capabilities, such as the broadcast tool, VO management facilities, a security dashboard and an operations dashboard that is used to display information about failing monitoring probes and to open tickets to the Resource Centres affected. The dashboard also supports the central infrastructure oversight activities. It is fully interfaced with the EGI Helpdesk and the monitoring system through messaging. It is a critical component as it is used by all EGI Operations Centres to provide support to the respective Resource Centres. Moreover the Operations Portal provides tools supporting security operations, VO management, broadcast, availability reporting.

Consortium: CNRS

Contact: Cyril L’Orphelin (cyril.lorphelin@cc.in2p3.fr)

Security coordination and security tools

Overview

Security is recognised as an important aspect of e-Infrastructures and requires coordination between the EGI participants at various levels, in particular for the prevention and handling of incidents.

To keep a distributed infrastructure secure there is need for a coordination activity of the security effort at NGI and resource center level, and for tools that automatically test the EGI sites for vulnerabilities.

Consortium: STFC (UK), FOM-Nikhef (NL), CERN, CESNET (CZ), GRNET

Contact: David Kelsey (david.kelsey@stfc.ac.uk),  Christos Kanellopoulos (skanct@grnet.gr), Kostas Koumantaros (kkoum@grnet.gr)

UMD quality assurance

Overview

The quality criteria are the functional and nonfunctional requirements that a product must fulfill to be released in UMD; these include generic requirements applicable to every product, and specific requirements applicable to the capabilities supported by a component.

The Staged Rollout is a procedure by which certified updates of the supported middleware are first tested by Early Adopter (EA) sites before being made available to all sites through the production repositories. This procedure permits to test an update in a production environment that exposes the product to more heterogeneous use cases than the certification and verification phase. This allows the discovery of potential issues and the addition of corresponding mitigation information to the UMD release notes.

Consortium: Ibergrid

Contact: Jorge Gomes (jorge@lip.pt), Mário David (david@lip.pt), Joao Pina (jpina @lip.pt) Isabel Campos (isabel@campos-it.es ), Enol Fernandez (enolfc@ifca.unican.es) Carlos Fernandez (carlosf@cesga.es)

UMD software provisioning infrastructure

Overview

The software provisioning infrastructure provides the technical tools to support the UMD release process from pulling packages from the developers repositories to the build of a release.

Consortium: GRNET

Contact: Kostas Koumantaros (kkoum@grnet.gr)