Difference between revisions of "2016-bidding/DIRAC4EGI"
(2 intermediate revisions by the same user not shown) | |||
Line 36: | Line 36: | ||
* Provision usage statistics upon request | * Provision usage statistics upon request | ||
== Maintenance == | |||
*Requirements gathering | |||
*Documentation | |||
== Support == | == Support == | ||
Line 45: | Line 49: | ||
Services must have Availability of 99% on a monthly basis. | Services must have Availability of 99% on a monthly basis. | ||
= | = Effort = | ||
Bids planning a total effort of 10 Person Months/year would allow these services and activities to be addressed appropriately. |
Latest revision as of 09:46, 25 October 2016
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: DIRAC4EGI
Introduction
DIRAC 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 service will support established Virtual Organization as well as the long tail of users.
Given the critical nature of the activity bid must contain an availability and continuity plan for the service.
Technical description
The DIRAC4EGI 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 DIRAC both using GUI and API.
The component 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 organizations, 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
- Configure new VOs in the DIRAC4EGI service
- Handle security requests
- Provision usage statistics upon request
Maintenance
- Requirements gathering
- Documentation
Support
Support is provided through the it-support mailing list and the dedicated ggus support unit.
Service level target
Services must have Availability of 99% on a monthly basis.
Effort
Bids planning a total effort of 10 Person Months/year would allow these services and activities to be addressed appropriately.