Co-ordination & Harmonisation of Advanced e-Infrastructures for Research and Education Data Sharing Research Infrastructures Grant Agreement n Information System Overview Christos Kanellopoulos, GRNET AA ROC All-Hands Meeting, 25 March 2013

Information System Overview  Mission Critical component  Provide Information about Grid Services  Built upon the Berkley Database Information Index (BDII)  The BDII can be visualized as an LDAP database 2 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

Information System Overview  Hierarchical Structure of 3 levels  Resource Level BDII  Site Level BDII  Top Level BDII 3 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

Information System Overview 4

 Resource Level BDII  usually co-located with the grid service  Provides information about the specific service (e.g. SE) 5 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

Information System Overview  Site Level BDII  Each Grid Site runs an instance of a Site Level BDII  Aggregates the information from all the Resource Level BDIIs of the Site  In the past it was common that the Site BDII was co- located with the CE. Nowadays, it is advised that the Site BDII runs as a standalone service 6 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

Information System Overview  TOP Level BDII  Aggregates all the information from the Site Level BDII  Contains all the Information about the Grid Services  The information system clients query a top level BDII to find the information that they require  There are multiple instances of the top level BDII in order to provide a fault tolerant, load balanced service 7 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

Information System Overview  The BDII are populated with information by running Information Providers (IP)  Scripts which obtain information  Format it as LDIF  Print the result in stdout  Can be used in order to query other BDIIs  This is how the BDII hierarchy is being created  The information provided by the BDII conforms to the Glue Schema  Glue v1.x (Old version of the Glue Schema)  Glue v2.x (New version)  The BDII supports both Glue1 and Glue2 in parallel 8 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

Information System Overview 9 Node TypeGlue 1Glue 2Notes LCG-CEYesNoObsolete CREAMYes Full support in EMI 2 CLUSTERYes Full support in EMI 2 WMSYes LBYes DPMYesEMI 2 dCacheYesEMI 2 StoRMYesEMI 2 LFCYesEMI 2 FTSYesEMI 2Channels not yet published HydraEMI 1EMI 2Not yet released in EMI 2 AMGAYesEMI 2 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

Information System Overview 10 Node TypeGlue 1Glue 2Notes VOMSYes MyProxyYes ArgusNoEMI 2Publication for Deployment Monitoring Site BDIIYes Top BDIIYes R-GMAYesNoObsolete VOBOXYes APELNo Internal Service. Publishing not yet requested SquidNo Configuration exists but not enabled NagiosYes

Information System Overview  Freedom of Choice for Resources mechanism (FCR) is used within a top level BDII to enable the Virtual Organization (VO) to influence their usage of specific service  generates a list of services available to a VO  can be used by the VO manager to either white list or black list sites  downloaded by the top level BDII and it deletes the ACL for the VO on that specific service from the database  The information system is bootstrapped from the information in the Grid Operations Center Database (GOCDB)  Site enter the URL of their Site Level BDII3  A list of LDAP URLs for all the sites in the Grid is generated by the GOCDB  This list is downladed by the Information Provider to the Top Level BDII 11 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

Tags  The IS can be used to publish specific tags  Two types of tags  VO Specific Tags (usually managed by the VO Admins)  Site wide Tags (usually managed by the Site Admins) 12 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

Tags  Publishing VO Specific tags  The VO published for a specific VO can be found in the CE at the path: /opt/edg/var/info/ /.list  The Tag format follows the pattern: VO- -  Usually the VO Manager runs a script that modifies the vo tag file and appends any new Tags  globus-job-run srvslngrd004.uct.ac.za:2119/jobmanager-fork -s hello_shared_tag.sh  ldapsearch –LLL –H ldap://srvslngrd001.uct.ac.za:2170 –x –b \ 'mds-vo-name=local,o=grid'\ '(GlueHostApplicationSoftwareRunTimeEnvironment=VO-sagrid-hello)' \ GlueChunKey 13 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

Tags  Publishing Site wide Tags  In site-info.def the CE_RUNTIMEENV holds a space separated list of software tags supported by the site  E.g. CE_RUNTIMEENV="LCG-2 LCG-2_1_0 LCG-2_1_1 LCG-2_2_0 GLITE-3_0_0 GLITE-3_1_0 GLITE-3_2_0 TAG1 TAG2" 14 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

High Availability Setup for TOP BDII  Hardware Requirements:  Dual core CPU  10GB of Hard Disk  4GB of RAM  Best Practices  DNS Round Robin load balancing  Fault Tolerance DNS Updater 15 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

High Availability Setup for TOP BDII  DNS Round Robin Load Balancer  Instances should have the same hardware configurations. If not, a load balancing arbiter is needed  It is recommended to have 3 instances running  Fault Tolerance DNS Updater  Test the group of the HA (E.g. nagios)  ldapsearch -x -h -p b "o=infosys"  remove or add DNS entries through DNS dynamic updates 16 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |

Further Information   mation mation    info_configuration_variables#site_BDII info_configuration_variables#site_BDII 17 Christos Kanellopoulos | | AA Roc All Hands Meeting 03/2013 |