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 @ egi.eu.

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

From EGIWiki
Jump to navigation Jump to search
(Placeholder for DIRAC entry)
 
(Redirected page to 2019-bidding/platforms)
 
(23 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Template:Op menubar}}{{Core_services_menubar}} {{TOC_right}}
#REDIRECT[[2019-bidding/platforms]]
'''Go back to the [https://wiki.egi.eu/wiki/EGI_Core_activities:Bidding#Phase_IV_January_2021_-_June_2023|EGI Core Activities Bidding page].'''
 
= Service name: Workload Manager (DIRAC) =
 
==  Introduction ==
 
 
 
== Technical description ==
 
 
== Coordination ==
 
 
== Operations ==
 
== 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.
 
Examples of requested support:
* e-infrastructure service providers, e.g. CRL publishing
* EGI Security: e.g. credentials revocation
* Incident support: to the integrated master portal (end users should not contact directly the OnlineCA, since users' requests for support are directed to the master portal
 
== Maintenance ==
 
== 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.
 
== Service targets ==
 
Service must be provided with an availability and reliability of XX%.
Support level through the helpdesk support unit: Medium.
 
== Effort ==
 
Bids planning a effort of X Person Months/year would allow these services and activities to be addressed appropriately.

Latest revision as of 13:10, 18 November 2019