1. EMI is partially funded by the European Commission under Grant Agreement RI-261611 Discovering Infrastructures with EMI Registry (EMIR) Emidio Giorgio – INFN - IGI On behalf of Shiraz Memon, Jülich Supercomputing Center ISGC 2012, 29.02.2012

2. EMI INFSO-RI-261611 Motivation Overview High level architecture – Registry Hierarchies – Global level replication – Information Model Integration with EMI Services – UNICORE, ARC Conclusions Outline 12/12/2015ISGC 20122

3. EMI INFSO-RI-261611 EMI Registry (EMIR) Motivation 12/12/2015ISGC 20123 Lack of a common service index; within EMI – UNICORE (Global) Registry – ARC ISIS – Site / Top Level BDII Middleware specific Discovery Various Information Models Not Federation Aware Unfortunately, nothing to do with oil motivation

4. EMI INFSO-RI-261611 Cross Middleware Service Discovery Supports Hierarchies (Theoretically infinite) Common Access Point and Unified Method to service registrations and discovery Lightweight REST-full API Standards based GLUE 2.0 Information Model EMIR: A Unified Service Registry 12/12/2015ISGC 20124 motivation

5. EMI INFSO-RI-261611 Domain Service Registry (DSR) – A registry node at any level of the hierarchy – Registration and Rich Query Interface – PKI based Authentication – XACML or simplified ACL for Authorization – Synchronization with a parent registry node – Filtered Registrations Global Service Registry (GSR) – Similar to DSR – Replication with other GSR using P2P techniques – Bootstrap from publicly available Global List Main Components 12/12/2015ISGC 20125 overview

6. EMI INFSO-RI-261611 High Level Architecture 12/12/2015ISGC 20126 High level architecture

7. EMI INFSO-RI-261611 Communication of DSRs (1/2) 12/12/2015ISGC 20127 > DSR > DSR Servic e publish > GSR Domain Computing Center State/Region Country Publish Liveness at the GSR ∞ Level of Hierarchy High level architecture

8. EMI INFSO-RI-261611 Predefined Parent ref. at the Child DSR Synchronization is done through events Active Sync. – Parent notified as soon as the changes occurred in the child DSR Passive Sync. – Parent notified as soon as it joins the hierarchy (fresh startup or recovered from a failure) – Temporary caching Communication among DSRs (2/2) 12/12/2015ISGC 20128 High level architecture

9. EMI INFSO-RI-261611 Global Level Replication 12/12/2015ISGC 20129 Replication of Registries based on (structured) P2P Data Synchronization at the Global level Why? Federation level Service Discovery Failover Robustness Scalability Load Balancing Same query and registration interface Where to find the GSRs? Publicly known list > GSR > GSR > GSR > GSR > GSR > GSR https://gsr1, https://gsr2, https://gsr3 Bootstrap > GSR > GSR GSR List High level architecture

10. EMI INFSO-RI-261611 Schema free rendering Adopts GLUE 2.0’s generic service entities Supports standard XML as a response on query functions JSON for message exchange (query, de- registration) and service record Expiration time for every service record Constraining service URL as “unique” identifier Information Model 12/12/2015ISGC 201210 High level architecture

11. EMI INFSO-RI-261611 Service Name Service Type Endpoint URL Service Capabilities Downtime Info. JSON Rendering 12/12/2015ISGC 201211 [ { "Service_Name": “EMI Execution Service", "Service_CreationTime": {"$date": "2011-10-16T11:47:24Z"}, "Service_Type": “eu.emi.es", "Service_Capability": [“activity submission", “activity creation"], "Service_QualityLevel": "production", "Service_Endpoint_URL": "http://eu-emi.eu/emi-es", "Service_Endpoint_Technology": “SOAP over HTTP", "Service_Endpoint_InterfaceName": “ActivityManagement", "Service_Endpoint_InterfaceVersion": ["1.0“ ], "Service_Endpoint_WSDL": "http://eu-emi.eu/emi-es ?wsdl", "Service_Endpoint_HealthState": "ok", "Service_Endpoint_HealthStateInfo": “it is OK, I can see it", "Service_Endpoint_ServingState": "production", "Service_Endpoint_StartTime": {"$date": "2011-07-21T11:47:24Z"}, "Service_Endpoint_DowntimeAnnounce": {"$date": "2011-07- 21T11:47:24Z"}, "Service_Endpoint_DowntimeStart": {"$date": "2011-07-21T11:47:24Z"}, "Service_Endpoint_DowntimeEnd": {"$date": "2011-07-21T11:47:24Z"}, "Service_Endpoint_QualityLevel": "production", "Service_ExpireOn": {"$date": "2011-07-21T11:47:24Z"}, "Service_UpdateOn": {"$date": "2011-07-21T11:47:24Z"}, "Service_OwnerDN": “CN=Shiraz Memon,O=FZJ,OU=JSC”}] High level architecture

12. EMI INFSO-RI-261611 Integration with EMI Services 12/12/2015 ISGC 2012 12 Services TargetSystemFactory BESFactory EMI-ES StorageFactory UNICORE Services AREX Compute gridftpd Chelonia Storage ARC Register ARC Client UNICORE Command Line Client (UCC) Lookup & Discover EMI Services Integration with EMI

13. EMI INFSO-RI-261611 Integration with all the EMI Services Automatic (de)commissioning of a Registry node in the hierarchical network Handling synchronization and failures while replicating the large number of service entries Future Work 12/12/2015ISGC 201213 Conclusions

14. EMI INFSO-RI-261611 Common Service Index for EMI Support for federation Architecture Information Model Integration Scenario Summary 12/12/2015ISGC 201214 Conclusions

15. EMI INFSO-RI-261611 Documentation (REST API (WADL Document) Wiki Code Packages Contacts => EMI ForumEMI Forum Links 12/12/2015ISGC 201215 Conclusions

16. EMI INFSO-RI-261611 Questions ? 12/12/2015ISGC 201216 Conclusions