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.
EGI-InSPIRE:Plan 2013 SA1.7
| EGI Inspire Main page |
| Inspire reports menu: | Home • | SA1 weekly Reports • | SA1 Task QR Reports • | NGI QR Reports • | NGI QR User support Reports |
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.
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.
Plans for 2013
- test resources. Finish the 2012 task.
- Unknown Issue. Nagios probes to generate alarms for the unknown issue.
- New Role. The past followup activities by means of GGUS tickets have shown not to result in any positive effect. We want to shift focus to addressing the persistent issues rather than the incidental ones.
Network support and monitoring/troubleshooting tools
Assessment of progress in 2012
Completed Activities and Milestones
Milestones not accomplished
Plans for 2013
Software support
Assessment of progress in 2012
Completed Activities and Milestones
- Revision of TPM and DMSU activities. These two software-support related activities were thoroughly analysed, overlaps were identified, and reogranzation proposed. The two groups were merged, and responsibilities of the involved partners were reassigned in order to achieve more efficient effort usage. Details are described in EGI doc#1104 and MS 511.
- Implementation of the TPM and DMSU merge. After having been approved by the project review, the proposed reorganization was implemented.
Milestones not accomplished
None.
Plans for 2013
The main goal of the task is provision of smoothly running support and most of the effort is allocated to this recurrent work. The processes are well established (with the exception bellow), and they will be followed as they are.
- Implement low-priority tickets tracking (April 2013). The process was agreed by TCB, and it is described at EGI_DMSU_Ticket_Followup, however, it has not been fully implemented yet. The required support in GGUS will be provided, and the process will be implemented to be followed routinely after EMI-3 release.
- Deployed Middleware Support Unit Operations Procedures (July 2013). Milestone document as of the project DoW. Describe a snapshot of the software support unit procedure.