Difference between revisions of "MPI VT Open Actions"
(Created page with "{| cellspacing="1" cellpadding="1" border="1" align="left" style="width: 1239px; height: 565px;" |- ! scope="col" | ID ! scope="col" | Action Description ! scope="col" | Responsi...") |
|||
Line 1: | Line 1: | ||
[[Category:TODO]] | |||
{| cellspacing="1" cellpadding="1" border="1" align="left" style="width: 1239px; height: 565px;" | {| cellspacing="1" cellpadding="1" border="1" align="left" style="width: 1239px; height: 565px;" | ||
|- | |- |
Revision as of 11:23, 16 October 2012
ID | Action Description | Responsible | Ticket (where applicable) |
---|---|---|---|
Documentation | |||
1. | Update
the user and site administrator MPI documentations when any of the MPI services (e.g. scripts, SAM probes), or relevant parts of the infrastructure are updated. |
EGI-InSPIRE
SA3.2 |
|
SAM MPI probes | |||
2. | Implement
the MPI SAM Nagios probes according to the specification prepared by the MPI VT. |
EGI-InSPIRE
SA3.2 |
|
3. | Test
the MPI SAM Nagios probes, then deliver to EGI Operations for integration. |
EGI-InSPIRE
SA2 and JRA1 |
|
4. | Integration
of the MPI SAM Nagios probes into the production monitoring infrastructure. |
EGI-InSPIRE
SA1 and JRA1 |
|
5. | In
order to improve and check availability and reliability statics for MPI sites a new ‘service type’ need to be added to GOCDB (serial or parallel). |
EGI-InSPIRE
JRA1 |
https://rt.egi.eu/guest/Ticket/Display.html?id=3396 |
Information System | |||
6. | Correct
misconfigured registration of MPI sites in the Information System. |
EGI-InSPIRE
SA1 with resource providers |
|
7. | Enhance
the batch system information providers to properly collect the GlueCEPolicyMaxSlotsPerJob value. |
EMI,
monitored by EGI-InSPIRE SA3.2 |
https://ggus.eu/ws/ticket_info.php?ticket=82902 Savannah tickets for each batch system: LSF: https://savannah.cern.ch/bugs/index.php?95182 SGE: https://savannah.cern.ch/bugs/index.php?95183 Torque: https://savannah.cern.ch/bugs/index.php?95184 |
Accounting | |||
8. | Provide
technical details for a requirement ticket for EMI. |
EGI
OMB |
https://rt.egi.eu/guest/Ticket/Display.html?id=3328 |
9. | The
EMI middleware services need to implement and support the CAR definition that already includes ‘Number of nodes and cores used by a job’ as an accounting metric. This is expected to happen in EMI-3. |
EMI,
monitored by EGI-InSPIRE SA3.2 |
https://rt.egi.eu/guest/Ticket/Display.html?id=4071 |
10. | The
summaries of the EGI Accounting Portal need to be grouped on site, VO, FQAN or UserDN and include ‘Number of cores’ as a new variable to be displayed. |
EGI-InSPIRE
JRA1 |
|
Batch system integration | |||
11. | Release
the MAUI & TORQUE packages from EMI-2 in UMD-2.0.1. |
EGI-InSPIRE
SA2 |
|
VO Setup and user support | |||
12. | Bringing
in more sites to the MPI-Kickstart VO would be beneficial. |
VT members (Demo at TF2012) EGI-InSPIRE SA3.2 |
https://rt.egi.eu/rt/Ticket/Display.html?id=3396 |
13. | Setup
a page in the EGI Wiki that collects and provides information about the MPI services and support mechanisms for application developers and resource providers. |
EGI-InSPIRE
SA3.2 |