Difference between revisions of "Requirements OMB Jan 2012"
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
*[https://rt.egi.eu/rt/Ticket/Display.html?id=3030: IPv6 compliance of UMD] | *[https://rt.egi.eu/rt/Ticket/Display.html?id=3030: IPv6 compliance of UMD] | ||
*[https://rt.egi.eu/rt/Ticket/Display.html?id=3305: short-lived anonymous HTTP TURL on Storage Elements] | *[https://rt.egi.eu/rt/Ticket/Display.html?id=3305: short-lived anonymous HTTP TURL on Storage Elements] | ||
*[https://rt.egi.eu/rt/Ticket/Display.html?id=2575: Support for global interoperability] | |||
Submitted by COO | Submitted by COO |
Revision as of 12:37, 20 January 2012
Requirements to be analyzed for OMB January 2012
- APEL monitoring does not raise alarm when CE stops to publish
- the BDII must scale with number of sites
- Quick identification of users affected in an SE intervention
- Support for JobProject attribute in gLite
- Midleware installation is too painful
- Support multi-VO services, association to multiple topBDIIs
- Storage monitoring
- Enhance VOMS to send email when a user membership data is coming.
- IPv6 compliance of UMD
- short-lived anonymous HTTP TURL on Storage Elements
- Support for global interoperability
Submitted by COO
- Auotmatic configuration of CE capacity parameters
- Support for local jobs in the accounting system
- Accounting for MPI jobs
- Globus middleware publishes GLUE2 data
- Top-BDII should be able to handle multiple GIIS per site
Not for TCB