Alert.png 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:Macedonia-QR7

From EGIWiki
(Redirected from Macedonia-QR7)
Jump to navigation Jump to search
EGI Inspire Main page


Inspire reports menu: Home SA1 weekly Reports SA1 Task QR Reports NGI QR Reports NGI QR User support Reports



Quarterly Report Number NGI Name Partner Name Author


1. MEETINGS AND DISSEMINATION

1.1. CONFERENCES/WORKSHOPS ORGANISED

Date Location Title Participants Outcome (Short report & Indico URL)

1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED

Date Location Title Participants Outcome (Short report & Indico URL)
10.11.2011 Amsterdam NGI International Liaison Officer Kick off meeting Boro Jakimovski


1.3. PUBLICATIONS

Publication title Journal / Proceedings title Journal references
Volume number
Issue

Pages from - to
Authors
1.
2.
3.
Et al?

2. ACTIVITY REPORT

2.1. Progress Summary

  • Coordination and follow-up of security-related kernel update
  • Attendance or follow the minutes of OMB and Grid operations meetins
  • Regular site maintainance support within the NGI_MARGI
  • Coordination of middleware deployment and management of Grid operations in Macedonia
  • Operation of WMS/LB/VOMS/PX/LFC/BDII services for NGI_MARGI
  • All NGI_MARGI sites successfully implemented EGI Trust Anchor release 1.43
  • Regular middleware updates on all NGI_MARGI sites.
  • Operation of MARGI CA
  • Operation and maintenance of NGI_MARGI Nagios box
  • Installation of the new HPC Cluster with 2000 Logical CPU

2.2. Main Achievements

  • MK-03-FINKI site successfuly installed, ready for certification.

2.3. Issues and mitigation

Issue Description Mitigation Description

Low availability of MK sites. There were many problems with MK sited durring this quarter. Main problems were due to problems originating from faulty hardware. Also a very hard to locate problem was faulty reverse DNS server.

Main problem of the slow response to these issues was the overload of the staff due to the installation of new server room and migration of many of the services. This issues are now over and in January the sites showed over 90% availability.