OMB Requirements
Jump to navigation
Jump to search
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 | [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 |
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 |
RT ticket number | [8] |
Requirements title | ' |
Requirement description | |
Comment from Technology provider | |
Answer(s) from EGI/requestor | |
Status | status |