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 "OMB Requirements"
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
|O_tp_comment = EMI: Most of the EMI services already comply with the requirement, nevertheless covered by EMI objective, will be included in the EMI-2 plans. | |O_tp_comment = EMI: Most of the EMI services already comply with the requirement, nevertheless covered by EMI objective, will be included in the EMI-2 plans. | ||
|O_egi_comment =}} | |O_egi_comment =}} | ||
{{Template:Requirement_description | |||
| O_tn=1379 | |||
| O_title=Better configuration of services using mysql backend. | |||
| O_desc=Many services need a custom configuration of the database backend to improve their performance. This configuration should be provided with the service, and automatically applied where possible. | |||
|O_tp_comment = The requirement will be part of EMI-2 workplan. | |||
|O_egi_comment =}} | |||
| Line 43: | Line 52: | ||
|O_tp_comment = | |O_tp_comment = | ||
|O_egi_comment =}} | |O_egi_comment =}} | ||
{{Template:Requirement_description | {{Template:Requirement_description | ||
| Line 51: | Line 61: | ||
|O_egi_comment =}} | |O_egi_comment =}} | ||
===Usability=== | |||
{{Template:Requirement_description | {{Template:Requirement_description | ||
| O_tn= | | O_tn=1378 | ||
| O_title= | | O_title=Publishing middleware service versions | ||
| O_desc= | | O_desc=All the services should publish in the information system the service version, and the middleware release. Other additional request, automatically gathered from the operating system, should also be published: o.s., architecture.. | ||
|O_tp_comment = | |O_tp_comment = EMI endorsed the request, more information about what and how will be published are needed. | ||
|O_egi_comment =}} | |O_egi_comment = A proposal about how to map these information on GLUE2 has been forwarded to EMI}} | ||
{{Template:Requirement_description | {{Template:Requirement_description | ||
| Line 72: | Line 85: | ||
| O_desc= | | O_desc= | ||
|O_tp_comment = | |O_tp_comment = | ||
|O_egi_comment =}} | |O_egi_comment =}} | ||
{{Template:Requirement_description | {{Template:Requirement_description | ||
Revision as of 14:22, 19 May 2011
Summary of requirements collected by EGI
List of requirements by EGI from the end of 2010 to February 2011.
Every ticket is briefly described, with a summary of the feedback from the technology providers if any. For a more exhaustive description of the request, and to read the discussion that followed the ticket submission, follow the ticket link.
Installability
| RT ticket number | 1357 |
| Requirements title | Middleware use standard file locations |
| Requirement description | Currently services create a huge amount of temporary files and logs, not all of them are in standard locations. Services should create all the logs files under /var/logs, and the temporary files under /tmp.
Having all the files under the same path makes easier to parse and collect the logs. |
| Comment from Technology provider | EMI: Most of the EMI services already comply with the requirement, nevertheless covered by EMI objective, will be included in the EMI-2 plans. |
| Answer(s) from EGI/requestor | |
| Status | status |
| RT ticket number | 1379 |
| Requirements title | Better configuration of services using mysql backend. |
| Requirement description | Many services need a custom configuration of the database backend to improve their performance. This configuration should be provided with the service, and automatically applied where possible. |
| Comment from Technology provider | The requirement will be part of EMI-2 workplan. |
| Answer(s) from EGI/requestor | |
| Status | status |
| RT ticket number | [1] |
| Requirements title | ' |
| Requirement description | |
| Comment from Technology provider | |
| Answer(s) from EGI/requestor | |
| Status | status |
Job Management
| RT ticket number | 1235 |
| Requirements title | Batch systems supported by EMI |
| Requirement description | The EMI computing elements should support a larger set of batch systems, the support (at least for the more important LRMS) should be guaranteed for the future. Another request was to have a common set of batch systems explicitly supported by all the Middleware stacks. |
| Comment from Technology provider | (It is not a requirement directly addressed to EMI) EMI endorsed the requirement, but more clarifications are needed, starting from a list of needed batch systems needed/required by sites. |
| Answer(s) from EGI/requestor | A survey on the batch systems deployed/wanted has been launched by EGI in May-June 2011 |
| Status | status |
| RT ticket number | [2] |
| Requirements title | ' |
| Requirement description | |
| Comment from Technology provider | |
| Answer(s) from EGI/requestor | |
| Status | status |
| RT ticket number | [3] |
| Requirements title | ' |
| Requirement description | |
| Comment from Technology provider | |
| Answer(s) from EGI/requestor | |
| Status | status |
Usability
| RT ticket number | 1378 |
| Requirements title | Publishing middleware service versions |
| Requirement description | All the services should publish in the information system the service version, and the middleware release. Other additional request, automatically gathered from the operating system, should also be published: o.s., architecture.. |
| Comment from Technology provider | EMI endorsed the request, more information about what and how will be published are needed. |
| Answer(s) from EGI/requestor | A proposal about how to map these information on GLUE2 has been forwarded to EMI |
| Status | status |
| RT ticket number | [4] |
| Requirements title | ' |
| Requirement description | |
| Comment from Technology provider | |
| Answer(s) from EGI/requestor | |
| Status | status |
| RT ticket number | [5] |
| Requirements title | ' |
| Requirement description | |
| Comment from Technology provider | |
| Answer(s) from EGI/requestor | |
| Status | status |
| RT ticket number | [6] |
| Requirements title | ' |
| Requirement description | |
| Comment from Technology provider | |
| Answer(s) from EGI/requestor | |
| Status | status |
| RT ticket number | [7] |
| Requirements title | ' |
| Requirement description | |
| Comment from Technology provider | |
| Answer(s) from EGI/requestor | |
| Status | status |