Difference between revisions of "2019-bidding/egi-workload"
(Add effort) |
(→Effort) |
||
Line 83: | Line 83: | ||
== Effort == | == Effort == | ||
Bids planning a effort of 6 Person Months/year would allow these services and activities to be addressed appropriately. | Bids planning a effort of 5 to 6 Person Months/year would allow these services and activities to be addressed appropriately. |
Revision as of 16:58, 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 Core Activities Bidding page.
Service name: Workload Manager (DIRAC)
Introduction
EGI Workload manager (previously known as DIRAC4EGI) is a service is 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 technical configuration and training
With EGI user support team and Operations:
- to gather requirements and use cases
Operations
- Operate the technical services
- hardware operation
- software operation
- Configure support for new VOs
- Handle security requests
- Provision usage statistics upon request
- 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
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
- 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.
- Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...).
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.
Service targets
Service must be provided with an availability and reliability of 99%. Support level through the helpdesk support unit: Medium.
Effort
Bids planning a effort of 5 to 6 Person Months/year would allow these services and activities to be addressed appropriately.