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/service-registry"

From EGIWiki
Jump to navigation Jump to search
m
m (Undo revision 103028 by Catalin (talk))
Line 69: Line 69:
== Effort (TBD) ==
== Effort (TBD) ==


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

Revision as of 13:49, 11 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: Service registry (GOCDB)

Introduction

EGI relies on a central registry (GOCDB) to record information about the topology of an e-Infrastructure. This includes entities such as Operations Centres, Resource Centres, service endpoints and their downtimes, contact information and roles of users responsible for operations at different levels. The service enforces a number of business rules and defines different grouping mechanisms and object-tagging for the purposes of fine-grained resource filtering. GOCDB is a source of information for many other operational tools, such as ARGO, the Accounting Portal, the Operations Portal, etc.

Technical description

The GOCDB service must be deployed in master-slave distributed high-availability configuration. The two instances cannot be deployed on the same site. Monitoring components have to be integrated within the in-house production monitoring system.

The service authentication must integrate with EGI Check-in service.

Coordination

This activity is responsible for the coordination of the system operation and upgrade activities with those partners that are in charge of operating other systems that depend on it.

Operations

  • Daily running of the system
  • Provisioning of a high availability configuration
  • A test infrastructure to verify interoperability and the impact of software upgrades on depending systems
  • Implementing all the measures for mitigating the risks listed in the Availability and Continuity Plan for GOCDB

Maintenance

  • Bug fixing, proactive maintenance, improvement of the system
  • Coordination of software maintenance activities with other technology providers that provide software for the EGI Core Infrastructure or remote systems deployed by integrated and peer infrastructures that interoperate with the central EGI components of the system
  • 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 via EGI Service Desk Support Unit: GOC DB (http://helpdesk.egi.eu/).

Support hours: eight hours a day, Monday to Friday – excluding public holidays of the hosting organization.

Service level targets

Effort (TBD)

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

Retrieved from "https://wiki.egi.eu/w/index.php?title=2019-bidding/service-registry&oldid=103029"