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 @


From EGIWiki
Revision as of 17:27, 15 November 2019 by Mviljoen (talk | contribs)
Jump to navigation Jump to search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

EGI Services and Service Management Support menu: Bids Old Bids Performance

Go back to the EGI Services Bidding page.

Service name: Attribute Management

Technical description

This activity will provide:

  • A group management system used to manage the access to the EGI services for some scientific communities, able to directly manage users, groups, user enrolment, and users synchronisation from existing VOMS servers. It will be offered either a shared instance to host scientific communities or a dedicated instance for those that require it, providing support for (de-)provisioning and continuous update of user account information.
  • Some legacy services for the authorisation and authentication of users in EGI: a Catch-all VO membership management (a VOMS service for the X509 credentials) for small research teams and the long tail of science, as well as for infrastructure VOs including DTEAM


This activity is responsible for the coordination of the system operations in collaboration with those partners that are in charge of operating other systems that depend on the attribute management service.


  • Daily running of the system
  • Support request for changes through the dedicated support unit in the EGI Helpdesk service
  • Provisioning of a high availability configuration
    • For the legacy services, at least regular backup and automation scripts allowing the quick recovery of the service if needed.
  • Creating an Availability and Continuity Plan and implementing countermeasures to mitigate the risks defined in the related risk assessment


  • Requirements gathering
  • Maintenance of probes to test the functionality of the service
  • 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 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 hours: eight hours a day (for example 9-17 CE(S)T), Monday to Friday – excluding public holidays of the hosting organization.

Service level targets

The deployment of the services must ensure:

  • Minimum availability/reliability:
    • for the legacy services (VOMS): 95%/99%
    • for the group management system: 99%/99%
  • Response to incident records in GGUS within support hours: Medium (see Description page)

Effort (EGI-related activities)

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

Effort (EOSC-related activities)

Partners are encouraged to submit details of activities and proposed costing of effort for EOSC related activities. This may include activities related to development of new functionality required by EOSC communities in addition to activities delivering services to these communities.