NGI_TR Emrah Akkoyun TR-Grid Operational Center EGI-InSPIRE – SA1 Kickoff Meeting1

Transition Plans to depart from existing ROC and become independent TR-Grid is a large NGI with all operational tools to become independent were installed during EGEE projects.  Regional Nagios  It will be completed within this month  Waiting for the validation  Ticketing System  RT already exists  Integration process is on progress  The ticket for enabling NGI_TR is opened  All the transition to NGI activities will be run autonomously

Becoming part of EGI: Governance Governance –Is the NGI committing itself to participate to the NGI Operations Managers meeting (1 meeting per month)? – YES –Is the NGI operations staff committing to participate fortnightly operations meetings for discussion of topics related to the middleware (releases, urgent patches, priorities...) - YES –NGI has already a representative inOperations Tool Advisory Group – OTAG – who developed HGSM site management tool Suggestions to improve your NGI representation in operations meetings and boards – Enabling video or voice conference facilities is much more important for NGIs in our region – We have been in several regional projects with SEE, Caucaus, EUMED countries and enabling usable video conference facilities was a must for attendance to such meetings.

Becoming part of EGI: Infrastructure Is the NGI expected to increase its infrastructure (number of sites, resources)? In the first year of EGI, we are not planning a change at the middleware stack of the sites. TR-01-ULAKBIM, TR-03-METU, TR-05-BOUN and TR-10-ULAKBIM will continue with gLite. ARC middleware has already been installed on TR- 07-PAMUKKALE. Following sites will be migrated from gLite to ARC: TR-04-ERCIYES, TR-09-ITU

Becoming part of EGI: Infrastructure Is the NGI expected to increase its infrastructure (number of sites, resources)? Infrastructure has being supported by State Planning Organization since the start of Current project is a five year, 15MEuro project. For 2010 following purchases are on the bidding process: – Storage Resources Expanding with additional ~650 TB storage, totally ~1.3 PB storage will be available – Computing Resources and Performance Network Nearly 4800 CPU cores will be added, totally ~7400 cores will be available Current infiniband infrastructure (144 port DDR and 648 port QDR) at ULAKBIM will be densely used for computing and storage network in grid resources also.

Becoming part of EGI: Procedures and policies EGEE procedures/policies –Is the NGI familiar with existing procedures/policies? TR-Grid initiative which was established in 2003 is one of the pioneer NGIs and does have its own operational, security and managerial procedures. Thus during preparation of EGI project EGEE and EGI procedures was reinvestigated for possible conflicts to be prepared for fully independent NGI transition. –If the NGIs deploys different mw stacks (gLite, ARC, other...): what EGEE procedures need to be adapted? –Nagios should include full test suite for other MW stacks –Ticketing and vulnerability reporting can be distinguished based on MW stacks

Becoming part of EGI: Procedures and policies Does the NGI deploy own procedures that are not integrated with EGEE ones? Turkish national infrastructure has HPC sites that works with special authorization, distributed storage layers. Both operational issues and monitoring of these sites are not integrated with EGEE. Are the (EGEE) procedures well documented? Feel free to provide suggestions for improvement For those who doesn’t like to read deliverables or project Annex there are Wiki pages which describe that procedures both summarized and in detail.

Becoming part of EGI: Support ULAKBIM manages both NGI and NREN activities in Turkey OS and middleware are fully controlled by TR-Grid operation center in the same office. Local system administrators manage the failure of Network Hardware Operating System

Becoming part of EGI: Tools Which “regional” tools is the NGI interested in deploying directly rather than using a central instance/view: –O-N-1 national Grid configuration database (GOCDB or equivalent tool) Central GOCDB will be used at the start. Both regional GOCDB and HGSM are on test in ULAKBIM. Our plan is to migrate to a national configuration database before the end of first year. –O-N-2 national accounting infrastructure (repositories and portal) Local instances of repositories and portal are already used. Portal is being developed to better serve to the needs of national research groups and TR-Grid-HPC infrastructure. –O-N-3 NGI monitoring infrastructure Local instance of nagios, pakiti, ganglia, mrtg are already used –O-N-7 helpdesk: interested in using a central “NGI view” of GGUS or deploying own system? How is it going to be interfaced to GGUS? OneorZero in use but doesn’t provide elasticitiy to add customizations. RT which is used for submitting network problems to NREN will be integrated with GGUS interface soon

Becoming part of EGI: Tools Which own tools (if any) does the NGI deploy? HGSM Developed in the framework of SEE-GRID projects and has been used by all SEE- GRID countries for nearly five years Monitoring dashboard which combines and reports problems from all deployed monitoring tools Is the NGI planning to run Scientific Gateways for Vos? – National P-Grade instance is enabled for to be used by trgrid* VO communities by Middle East Technical University – National seismology repositories was combined in the framework of SEE- GRID-SCI project. With a project that will be supported by State Planning Organization these repositories and tools that was developed during SEE- GRID-SCI will be enabled to seismic researchers with a portal like in IRIS.

Availability and Operations Level Agreements What overall level of functional availability/reliability is the NGI ready to commit? Current NGI_TR infrastructure is a production infrastructure which is professionally supported by leading support agencies in Turkey. Since our HPC users (whose runs need longer runtimes) demand a 7/24 infrastructure, we are willing to respond on non-office hours Will the NGI be able to comply to EGI Operations Level Agreements defining for example –Minimum availability of core middleware services (top-BDII, WMS/LB, LFC, VOMS, etc.) - YES –Minimum availability of core operational services such as: nagios-based monitoring, helpdesk - YES –Minimum response time of operations staff to trouble tickets - YES –Minimum esponse time of the NGI CSIRT in case of vulnerability threats? – YES

Training Is the NGI ready to provide training to its own site managers and operations staff? Both national and regional training events were organized before. There are 5 EGEE accredited trainers in NGI_TR On operations portal, there are already plenty amount of documents prepared in national language for site managers and operations staffs –NGI_TR is willing to share material and also can organize training events which can be attended by other NGI community also.

Your best knowhow Is there any specific Grid operations field where your NGI feels advanced/expert, and about which your NGI is willing to provide guidance to other NGIs? HGSM – Hierarchical Grid Site Management Tool (Alternative to GOCDB) Infiniband support Seismological repositories and enabling grid use of these repositories to seismic researchers MPI support