1. Information Services July 22 nd 2010, GENI I&M Working Group Jason Zurawski - Internet2

2. Provide 2 Services for the greater I&M Architecture: – Registration Services identify themselves, and the resources they control – Service is purposely vague, could be I&M related or even infrastructure “Push” from the lower (e.g. service) layer to the IS Layer Frequent updates: encompasses changes and reinforces “liveness” Layers of Information Service handle the rest – Local – direct contact with services – Distributed – Maintain contact with local IS to distribute and make info available – Discovery IS Layer builds an index on registered information – Domains, Addresses, Services, Data Types, (more?) APIs to access the data – Use of well known protocols 2 – 6/28/2016, © 2010 Internet2 Information Services

3. Architecture: – “Home” Lookup Service Accepts registrations from services “Summarizes” the useful information Transmits to the “Global” Layer Statistically known to services, or discoverable – “Global” Lookup Service “Cloud” of information services – All individual services working together – Exchange information frequently using dist. Algorithms – Resilent to failure and capable of balancing load Scalable – easy to add or remove services as required APIs for Clients to communicate 3 – 6/28/2016, © 2010 Internet2 Information Services

4. Information Services – Registration 4 – 6/28/2016, © 2010 Internet2 Network A ab c LS A MA A gLS Collect measurement data from network Accept registration from services Summarize data sets Convey information to the gLS cloud

5. Where is link utilization for - IPs d,e,f? Client Network ANetwork B LS ALS B MA A MA B ab cd e f Where is link utilization for – IPs a,b,c? a,b,c : Network A, MA A Get link utilization d,e,f Here you go Get Link utilization a,b,c Here you go Useful graph gLS Where can I get more about network Doman B/IP d,e,f and Domain A/IP a,b,c? LS A, LS B d,e,f : Network B, MA B Information Services – Discovery 5 – 6/28/2016, © 2010 Internet2