EGI Core activities:PHASE I
|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|
This page lists EGI.eu core activities provided by EGI.eu partners. Partners for each activity have been chosen through EGI Core Activities Bidding process.
Period: May 2014 - April 2016
Each activity is obligated to deliver every 6 months report according to EGI.eu Operation Level Agreements report templates.
- 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
Message Broker Network
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 infrastructure component whose continuity and high availability configuration must be ensured. The Message Broker Network is part of the EGI Core Infrastructure Platform which is needed to support the running of tools used for the daily operations of EGI.
Consortium: GRNET, SRCE
Contact: Christos Kanellopoulos at GRNET
GGUS SU : Messaging
GOC DB: GRIDOPS-MSG
The Operations Portal provides VO management functions and other capabilities which support the daily operations of EGI. It is 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 grid 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. The Operations Portal provides tools supporting the daily running of operations of the entire infrastructure: grid oversight, security operations, VO management, broadcast, availability reporting.
Contact: Cyril L’Orphelin
GGUS SU: Operations Portal
The Accounting Repository stores user accounting records from various services offered by EGI. It is part of the EGI Core Infrastructure Platform, which supports the daily operations of EGI. The EGI Accounting Infrastructure is distributed. At a central level it includes the repositories for the persistent storage of usage records. The central databases are populated through individual usage records published by the Resource Centres, or through the publication of summarised usage records. The Accounting Infrastructure is essential in a service-oriented business model to record usage information.
Contact: Stuart Pullinger
GGUS SU : APEL
GOC DB: GRIDOPS-APEL
Accounting and Metric Portal
The Accounting Portal provides data accounting views for users, VO Managers, NGI operations and the general public. The Accounting Portal is part of the EGI Core Infrastructure Platform which supports the daily operations of EGI. The EGI Accounting Infrastructure is distributed. At a central level it includes the repositories for the persistent storage of usage records. The central databases are populated through individual usage records published by the Resource Centres, or through the publication of summarised usage records. The Accounting Infrastructure is essential in a service-oriented business model to record usage information.
The Metrics Portal aggregates metrics from the EGI Infrastructure from activity leaders and NGI managers in order to quantify and track the infrastructure evolution.
Contact: Carlos Fernandez
GGUS SU : Accounting Portal, Metrics Portal
SAM central services
The Service is part of the EGI Core Infrastructure Platform which supports the daily operations of EGI. Central systems are needed for accessing and archiving infrastructure monitoring results of the services provided at many levels (Resource Centres, NGIs 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.
Consortium: GRNET, SRCE, CNRS
Contact: Christos Kanellopoulos
GGUS SU: ARGO/SAM EGI Support
Monitoring central services
Monitoring Central Services is supporting monitoring of activities to be conducted centrally, like monitoring of e.g. UserDN publishing in accounting records, GLUE information validation, software versions of deployed middleware, security incidents and weaknesses and EGI.eu technical services. Central Monitoring Services is part of the EGI Core Infrastructure Platform, which supports the daily operations of EGI.
Consortium: GRNET, SRCE
Contact: Emir Imamagic
GGUS SU : ARGO/SAM EGI Support
GOC DB: GRIDOPS-MON
Security monitoring and related support tools are part of the EGI Core Infrastructure Platform which supports the daily security operations of EGI. EGI is an interconnected federation where a single vulnerable place may have a huge impact on the whole infrastructure. In order to recognise the risks and to address potential vulnerabilities in a timely manner, the EGI Security Monitoring provides an oversight of the infrastructure from the security standpoint. Also, sites connected to EGI differ significantly in the level of security and detecting weaknesses exposed by the sites allows the EGI security operations to contact the sites before the issue leads to an incident. Information produced by security monitoring is also important during assessment of new risks and vulnerabilities since it enables to identify the scope and impact of a potential security incident.
Contact: Daniel Kouril
GGUS SU :EGI Security Monitoring
GOC DB: GRIDOPS-SECTOOLS
Service registry (GOCDB)
Service Registry (GOCDB) is a central registry 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. GOCDB is part of the EGI Core Infrastructure Platform, which supports the daily operations of EGI.
Contact: David Meredith
GGUS SU : GOC DB
GOC DB: GRIDOPS-GOCDB
(splited from Operations support services)
Catch-All services are auxiliary services needed by the Core Infrastructure Platform and by various operational activities of EGI. Auxiliary services and activities are needed for the good running of Infrastructure Services. Examples of such services are VOMS service and VO membership management for infrastructural VOs (DTEAM), the provisioning of middleware services needed by the monitoring infrastructure (e.g. top-BDII and WMS), and catch-all services for emerging user communities.
Contact: Christos Kanellopoulos
GGUS SU : EGI Catch-all services
GOC DB: GRIDOPS-CATCHALL
(split from Operations support services)
Operations support is auxiliary service needed by the Core Infrastructure Platform and by various operational activities of EGI. Auxiliary activities are needed for the good running of Infrastructure Services. Examples of such are activities for service level management, service level reporting, service management in general and central technical.
Contact: Tomasz Szepieniec, Marcin Radecki
GGUS SU : EGI Operations support and Resource Allocation
Central coordination of the security activities ensures that policies, operational security, and maintenance are compatible amongst all partners, improving integrity and availability and lowering access barriers for use of the infrastructure.
Consortium: STFC, FOM, SNIC
Contact: Dave Kelsey</u
GGUS SU : Security Management
Overview. The Acceptance Criteria are the functional and non-functional requirements that a product must fulfil to be released in UMD, these include generic requirement applicable to every product, and specific requirements applicable to the capabilities supported by a component.
Contact: <u>Pablo Orviz
GGUS SU : EGI UMD Quality Assurance
Collaboration tools/IT support
Overview Collaborations tools are services needed by the EGI back-office and supporting EGI collaboration.
GGUS SU : EGI.eu collaboration tools
GOC DB: GRIDOPS-CTOOLS
The Staged Rollout is an activity 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 potentially to add mitigation information to the UMD release notes.
Contact: Jorge Gomes, Joao Pina/LIP; Isabel Campos, Enol Fernandez/CSIC, Carlos Fernandez, Ivan Diaz/CESGA
GGUS SU : EGI Staged Rollout
Software provisioning infrastructure
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, CESGA
SU : EGI Software provisioning support
GOC DB: GRIDOPS-UMDREPO
Incident management helpdesk
Incident Management (Helpdesk) is 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. GGUS is part of the EGI Collaboration Platform and is needed to support users and infrastructure operators.
Contact: Guenter Grein
GGUS SU : GGUS
GOC DB: GRIDOPS-GGUS
1st and 2nd level support
(merged with second level support)
First level support is responsible for ticket triage and assignment. This activity is also responsible for the coordination with teams responsible for 2nd level and 3rd level support.
Software-related tickets that reach the second level of support are analysed and if necessary are forwarded to 3rd line support units only when there are clear indications of a defect (in software, documentation, etc.).
Consortium: IberGrid, CESNET
Contact: Aleš Křenek, Zdeněk Šustr
GGUS SU : TPM, DMSU
2nd level support (core platform)
(merged with 1st level support (above) )
2nd level support (community platform)
(merged with the other monitoring and accounting tasks)
Document EGI-InSPIRE Operational Tools Sustainability provides more information about the current technical specifications, support and maintenance activities of the following services: Operations Portal, GGUS, GOCDB, SAM, Messaging, Accounting Repository, and Accounting Portal.