Difference between revisions of "2019-bidding/egi-workload"

From EGIWiki
Jump to: navigation, search
(Effort (EOSC-related activities))
(Redirected page to 2019-bidding/platforms)
 
Line 1: Line 1:
{{Template:Op menubar}} {{TOC_right}} {{EGI_services_and_SM_support_menubar}}
+
#REDIRECT[[2019-bidding/platforms]]
[[Category:Bidding]]
 
'''Go back to the [https://wiki.egi.eu/wiki/EGI_Services_and_Service_Management_Support:Bidding EGI Services Bidding page].'''
 
 
 
= Service name: Workload Manager (DIRAC) =
 
 
 
==  Introduction ==
 
 
 
EGI Workload manager (previously known as DIRAC4EGI) is a service provided to the EGI community as a workload management service used to distribute the users' computing tasks among the available resources both HTC and cloud.
 
 
 
The Workload Manager is based on DIRAC technology and is suitable for users that need to exploit distributed resources in a transparent way. The service has a user-friendly interface and also allows easy extensions for the needs of specific applications via APIs.
 
 
 
== Technical description ==
 
 
 
The Workload Manager service is a cluster of instances to allow the users to submit computational tasks to the HTC and Cloud services, monitor the status and  retrieve the results. Users interact with it both using GUI and API.
 
 
 
The components of the DIRAC service are:
 
* DIRAC WMS server (multiple high performance machines)
 
* DIRAC DB (MySQL) server (high performance, large memory machine)
 
* DIRAC REST server (medium sized machine)
 
* DIRAC Web server (low CPU, high memory machine)
 
* DIRAC configuration server (low CPU, high memory machine)
 
* DIRAC data manager service (low CPU, high memory machine)
 
 
 
== Coordination ==
 
 
 
With the Virtual Organisations (VO):
 
*  to support the community user/group management, resource configuration
 
 
 
With EGI user support team and Operations:
 
*  to gather requirements, use cases, training
 
*  customisation/integration to meet communities' needs
 
 
 
With EGI Policy team
 
* Sevice transition mangement
 
* EGI service catalogue on boarding
 
* Access policy
 
 
 
== Operations ==
 
 
 
* Operate the technical services
 
** hardware operation
 
** software operation
 
* Integrate with EGI Check-in
 
* Configure support for new VOs
 
* Configure support for new resources
 
* Handle security requests
 
* Provision and monitoring of usage statistics upon request
 
* Provisioning and monitoring of a high availability configuration
 
* Creating an Availability and Continuity Plan and implementing countermeasures to mitigate the risks defined in the related risk assessment
 
 
 
== Support ==
 
 
 
Support will be provided through GGUS.
 
 
 
Support hours: eight hours a day (for example 9-17 CE(S)T), Monday to Friday – excluding public holidays of the hosting organisation.
 
 
 
== Maintenance ==
 
 
 
* Bug fixing, proactive maintenance, improvement of the system
 
* Integration with new EGI federation services (AAI, HPC)
 
*Maintenance of probes to test the functionality of the service
 
* Requirements gathering, training
 
* Customisation/integration to meeting user communities' needs
 
* 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 [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 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.
 
 
 
== Service targets ==
 
 
 
Minimum availability/reliability: 95%/95%
 
 
 
Response to incident records in GGUS within support hours: Medium (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service)
 
 
 
== Effort (EGI-related activities) ==
 
 
 
Bids planning a total effort for the EGI work of 2 Person Months/year (STC) 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 (e.g. in the case of Workload Manger, supporting other EOSC communities) in addition to activities delivering services to these communities.
 

Latest revision as of 14:10, 18 November 2019