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 "EGI-InSPIRE:Plan 2013 SA1.7"
| Line 25: | Line 25: | ||
===Milestones not accomplished=== | ===Milestones not accomplished=== | ||
<!-- list here milestones that were not completed according to the envisaged schedule, saying why they were not completed, and the new schedule is --> | <!-- list here milestones that were not completed according to the envisaged schedule, saying why they were not completed, and the new schedule is --> | ||
''' Unknown status issue'''. In 2012 we want to solve the unknown status issue. This issue renders the computation of the availability and reliability of sites to inaccurate for some sites and/or NGIs. We consider this to be our highest priority. | ''' Unknown status issue'''. In 2012 we want to solve the unknown status issue. This issue renders the computation of the availability and reliability of sites to inaccurate for some sites and/or NGIs. We consider this to be our highest priority. | ||
Revision as of 17:13, 16 January 2013
Grid oversight
Assessment of progress in 2012
Completed Activities and Milestones
OLA enforcement ROD teams. Improve the enforcement of the OLA when it comes to ROD teams. We will collect ROD metrics and follow them up with our RODs.
A/R followup. We will improve the procedure for A/R followup to make it more efficient, effective and less time consuming. One example of this is the implementation of the A/R nagios probe in 2012.
ROD education. This topic is related to the one above. We will monitor the performance of our RODs. When we observe that RODs are not performing well because of a lack of knowledge, we will guide them.
test resources. We will take a look on how to include test resources in the infrastructure. Sites need guide lines on how to include test resources in the infratsructure so that it does not hinder users and it does not generate alarms or adversely affect the availability and reliability of sites.
Milestones not accomplished
Unknown status issue. In 2012 we want to solve the unknown status issue. This issue renders the computation of the availability and reliability of sites to inaccurate for some sites and/or NGIs. We consider this to be our highest priority. We have started up the followup but it appeared that this did not have any effect.
test resources. We will take a look on how to include test resources in the infrastructure. Sites need guide lines on how to include test resources in the infratsructure so that it does not hinder users and it does not generate alarms or adversely affect the availability and reliability of sites. This is still in progress. We have finished discussions with the GOCdb developers and will take this further.