Difference between revisions of "OMB Requirements"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
{{Template:Op menubar}} | {{Template:Op menubar}} | ||
= Summary of requirements collected by EGI = | = Summary of requirements collected by EGI Operations = | ||
{{TOC_right}} | {{TOC_right}} | ||
List of requirements by EGI from the end of 2010 to February 2011. | List of requirements by EGI from the end of 2010 to February 2011. | ||
Line 292: | Line 292: | ||
|O_tp_comment = EMI endorsed the requirement in the objective: "Increase performance of EMI services", that will be in the EMI-2 tech. plan. | |O_tp_comment = EMI endorsed the requirement in the objective: "Increase performance of EMI services", that will be in the EMI-2 tech. plan. | ||
|O_egi_comment =}} | |O_egi_comment =}} | ||
{{Category:Middleware}} |
Revision as of 16:27, 20 May 2011
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Summary of requirements collected by EGI Operations
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.
Note: This is a static page, last update: 19-May-2011 18:30
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 | 1022 |
Requirements title | UI dependencies on python 2.4 |
Requirement description | Middleware components should get rid of obsolete dependencies, that could be not available in more recent s.o. |
Comment from Technology provider | It seems that the main problem is Ubuntu, EMI will make available UI on ubuntu. |
Answer(s) from EGI/requestor | Requester asked to check if also other components have those obsolete deps. |
Status | status |
RT ticket number | 1186 |
Requirements title | New features for target system |
Requirement description | New features for Target System: Support for clusters without a shared FS, Possibility to define resources offered by a site per queue in IDB (assuming full support for queue selection, Possibility to freely split IDB into multiple files. Except of better manageability this would allow us to easy and automatically update some of SSR supported by a site. |
Comment from Technology provider | EMI required more information. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1388 |
Requirements title | Better documentation on service replication and load balancing configurations |
Requirement description | Middleware providers should provide documentation on how to easily migrate stateful services from a machine to another (e.g. how to migrate databases and data files). Documentation on high availability configuration is also needed. |
Comment from Technology provider | EMI will not take a general requirement on documentation. Where available HA configurations descriptions should be already provided being part of the documentation policy of EMI. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1381 |
Requirements title | Improve YAIM configuration |
Requirement description | YAIM functions should automatically get as many parameters as possible. E.g. operating system and architecture, needed in the cluster configuration, should be configured automatically. |
Comment from Technology provider | YAIM is not fully supported by EMI |
Answer(s) from EGI/requestor | |
Status | status |
Portability
RT ticket number | 1202 |
Requirements title | Uniform logging format |
Requirement description | Middleware services should uniform their logging format. |
Comment from Technology provider | EMI won't endorse this requirement. Changing the log format would break a number of monitoring tools that parse the logs. In case of specific problems open a GGUS ticket. |
Answer(s) from EGI/requestor | At least there should be some common rules to avoid common problems in parsing the logs. |
Status | status |
RT ticket number | 1201 |
Requirements title | Homogeneity in service control |
Requirement description | Requirement to have a standard, uniform, way to start/stop services. |
Comment from Technology provider | EMI endorsed this requirement as part of EMI-2 technical plan. |
Answer(s) from EGI/requestor | |
Status | status |
Usability
RT ticket number | 1380 |
Requirements title | Better WMS configuration tools, and monitoring. |
Requirement description | Many configuration/setup tricks are in the manual pages of WMS, but not yet implemented in the automatic configuration of the services. From the max number of connections to automatically clean the ICE persist directory. |
Comment from Technology provider | Open a GGUS ticket to the product team. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1184 |
Requirements title | Brokering and Matchmaking support for new site info system types |
Requirement description | UNICORE: Use of SSr in brokering process, and extensions to service orchestrator. |
Comment from Technology provider | EMI does not support those components. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1282 |
Requirements title | Requirement for VOMS/VOMSAdmin and for the accounting systems |
Requirement description | Requirement for the possibility to force a user to choose a VO-group at the moment of VO registration. This is needed for catch-all VOs, where the VO groups identify the actual user research community. |
Comment from Technology provider | EMI requested clarifications, before the endorsement |
Answer(s) from EGI/requestor | The simplest and probably the most useful scenario is the following: among the available VOs there is the possibility to choose which ones have the "mandatory flag" enabled |
Status | status |
RT ticket number | 1382 |
Requirements title | Documentation on different implementation of the same service |
Requirement description | The technology providers should provide comparison tables for the different implementation of the same service. |
Comment from Technology provider | EMI endorsed the requirement. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1230 |
Requirements title | Uniform API |
Requirement description | Request to have a uniform set of APIs to control all the services. |
Comment from Technology provider | |
Answer(s) from EGI/requestor | |
Status | status |
Operability
RT ticket number | 1674 |
Requirements title | Unify SRMv2.2 port |
Requirement description | Different implementation of the SRM service are answering on different ports (dCache implementation and DPM). In general the same service should provide the same default port in all its implementations. |
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 | 1283 |
Requirements title | MPI-start improvement |
Requirement description | Currently MPI-start does not support hybrid MPI-openMPI application and cpu/memory affinity between worker nodes involved in the process. |
Comment from Technology provider | EMI requested to forward the request to the specific product team. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1385 |
Requirements title | Interactive job monitoring |
Requirement description | Request for more tools to monitor runnign interactive jobs. |
Comment from Technology provider | EMI requested more details, and a more specific requirement. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1386 |
Requirements title | Storm file protocol |
Requirement description | Storm should support the direct access file protocol |
Comment from Technology provider | Storm server already supports the file:// protocol. The endorsed request is to enable it in the clients. |
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 | 1177 |
Requirements title | Archaic DRMAA interface version enabled in glite-TORQUE_server breaks functionality |
Requirement description | Old dependencies are breaking some functionalities of glite_TORQUE |
Comment from Technology provider | Submit bug report. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1183 |
Requirements title | UNICORE: Site info system enhancements |
Requirement description | UNICORE info system should support String, Integer, Enum types for SSR. And information on the expected waiting time of the job in the queue. |
Comment from Technology provider | EMI endorsed the requirement, fill a GGUS ticket with the requirement. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1383 |
Requirements title | cluster information |
Requirement description | The information described by the glite-CLUSTER compoent should be implemented in CREAM and in other implementation of computing capacity. |
Comment from Technology provider | Requested more details |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1188 |
Requirements title | GUI enhancements |
Requirement description | Requirement for enhancements in the UNICORE GUI |
Comment from Technology provider | EMI does not endorse the requirement, because the component is not in EMI |
Answer(s) from EGI/requestor | |
Status | status |
Serviceability
RT ticket number | 881 |
Requirements title | Requirement for VO renaming / migration |
Requirement description | The first part of the requirements is to implement a mechanism to allow users to migrate their data between the VOs they are member of. This would also easy the VO renaming process. The second part of the requirement is to extend the authorization and authentication mechanism to the VO aliases (defined by OPS portal). |
Comment from Technology provider | EMI security team reported that the requirement is not well specified, and not clear. |
Answer(s) from EGI/requestor | Requester reported a use case: Users (and VO administrators) are interested in migrating data from one VO1 to another VO2 in a transparent way. This should be done without doubling the space needed for the data, and without downloading/uploading the files. |
Status | status |
RT ticket number | 1189 |
Requirements title | Server-side management tools |
Requirement description | UNICORE need management tools for: easy identification of orphaned job directories; possibility to convert old state DB to the newer server; current activity status of the server; ability to disable job submission. Easy way to trace a user's job for support purposes. |
Comment from Technology provider | |
Answer(s) from EGI/requestor | |
Status | status |
Availability
RT ticket number | 1181 |
Requirements title | glite-BDII hangs, service status reports "bdii OK" |
Requirement description | The service status for BDII does not report hanging statuses. |
Comment from Technology provider | Fill bug report. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1384 |
Requirements title | DOS attacks |
Requirement description | Services should be able to protect themselves against misuses. E.g. a dCache server can be easily killed by a huge amount of legal requests submitted simultaneously by the same user. |
Comment from Technology provider | EMI makes sure that each service comes with some sort of configurable resource protection. However, general protection against DOS is not possible. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1607 |
Requirements title | accounting monitoring must be sufficient to decide whether all deployed middlewares of a site publish (correct) accounting data |
Requirement description | If a site deploys more than one middleware, the monitoring of accounting should check if all the computing elelment of the different stacks are publishing their accounting data. The same problem could be raised about multiple CE in the same site. |
Comment from Technology provider | |
Answer(s) from EGI/requestor | |
Status | status |
File Access
RT ticket number | 1187 |
Requirements title | Some new features for Data Mgmt and Sharing |
Requirement description | UNICORE. Support for end users collaboration, manipulating permssions, logical SMS |
Comment from Technology provider | EMI does not support that UNICORE component. |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1673 |
Requirements title | SRMv1 to be removed from gLite DPM box |
Requirement description | SRMv1 is not used anymore on DPM. It could be removed |
Comment from Technology provider | Not submitted yet. |
Answer(s) from EGI/requestor | |
Status | status |
Performance
RT ticket number | 1173 |
Requirements title | Increase of LB WS interface performance |
Requirement description | LB performance decrease when the WS interface is used. |
Comment from Technology provider | EMI endorsed the requirement, but it is low priority |
Answer(s) from EGI/requestor | |
Status | status |
RT ticket number | 1182 |
Requirements title | glite-CREAM consumes a lot of memory |
Requirement description | After about a month of uptime CREAM-CE performance decrease because of the memory usage. |
Comment from Technology provider | EMI endorsed the requirement in the objective: "Increase performance of EMI services", that will be in the EMI-2 tech. plan. |
Answer(s) from EGI/requestor | |
Status | status |