Difference between revisions of "2019-bidding/attr-mgm"

From EGIWiki
Jump to: navigation, search
(Effort)
Line 1: Line 1:
 
{{Template:Op menubar}}{{Core_services_menubar}} {{TOC_right}}
 
{{Template:Op menubar}}{{Core_services_menubar}} {{TOC_right}}
 
'''Go back to the [https://wiki.egi.eu/wiki/EGI_Core_activities:Bidding#Phase_IV_January_2021_-_June_2023 EGI Core Activities Bidding page].'''  
 
'''Go back to the [https://wiki.egi.eu/wiki/EGI_Core_activities:Bidding#Phase_IV_January_2021_-_June_2023 EGI Core Activities Bidding page].'''  
 
'''to add requirements on software licenses and fitsm traning&certification'''
 
  
 
'''to clarify the effort'''
 
'''to clarify the effort'''
Line 24: Line 22:
 
*Requirements gathering
 
*Requirements gathering
 
*Documentation
 
*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 [https://github.com/EGI-Foundation 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 ==

Revision as of 16:29, 5 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.

to clarify the effort

Service name: Attribute Management (PERUN)

Technical description

PERUN is a group management system used to manage the access to EGI FedCloud resources for some scientific communities. It is able to directly manage users, groups, user enrolment, and users synchronisation from existing VOMS servers. This activity will provide 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.

Coordination

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 EGI AAI infrastructure.

Operations

  • Daily running of the system
  • Provisioning of a high availability configuration
  • Creating an Availability and Continuity Plan and implementing countermeasures to mitigate the risks defined in the related risk assessment

Maintenance

  • 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 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: 99%/99%
  • Response to incident records in GGUS within support hours: Medium (see Description page)

Effort

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