Improving pS-PS Service Improving pS-PS Service ArchitectureArchitecture

2010-01-31, perfSONAR-PS Developers MeetingAaron Brown, Andrew Lake, Eric Pouyoul

• Problems– It’s difficult to add new metrics, or build new services using the

existing architecture.– There is duplication of effort between service implementations

which can lead to inconsistency between services.• Goal

– Improve Code Reuse– Increase modularity– Cordon off outside dependencies– Ease development of new services, or new metrics for existing

services– Improve performance, or minimize the performance impact

2 – 04/20/23, © 2009 Internet2

pS-PS Service Architecture

• Short Term Tasks– Develop a list of services to support, and document the

commonalities between them– Look to existing projects (e.g. OSCARS) for ideas on how to better

modularize the codebase– Begin design of new service architecture

3 – 04/20/23, © 2009 Internet2

pS-PS Service Architecture

• Measurement Archives– Registers metadata with a lookup service– Accepts requests

• Retrieve metadata• Retrieve data• Store metadata• Store data

– Allows for authentication/authorization• Measurement Points

– Registers its presence with a lookup service, and possibly where it can test to

– Accepts requests• Request measurement• Initiate measurement• Retrieve results of measurement

– Allows for authentication/authorization

4 – 04/20/23, © 2009 Internet2

Types Of Services

• Global Lookup Service– Exchanges summaries with other gLSes– Accepts requests

• Retrieve lookup service containing information on IP, domain, keyword.• Retrieve a summary of all lookup services known to the gLS

– Allows for authentication/authorization(?)• Home Lookup Service

– Registers its presence with gLSes– Accepts requests

• Request a service containing some metadata• Request metadata from a given service• Store a service’s metadata

– Allows for authentication/authorization• Transformation Service• Others?

5 – 04/20/23, © 2009 Internet2

Types Of Services

• New Measurement Metrics– Highly likely

• New Measurement Points– If we have AA, highly likely

• New Transformation Services– Unknown

• Lookup Service?– It is unlikely that we would have a variety of lookup services in the

same way we support a variety of metrics or a variety of measurement points

6 – 04/20/23, © 2009 Internet2

Likely New Functionality

• Authentication/Authorization• Lookup service registration (and maintenance)• Schema parsing• Message handling• Response construction• Others?

7 – 04/20/23, © 2009 Internet2

Common Components

8 – 04/20/23, © 2009 Internet2

OSCARSNotification Broker•Forward Notifications

AuthN• Authentication

Path Setup• Network Element

Interface

Coordinator• Workflow Coordinator

PCE• Constrained Path

Computations

Topology Bridge

• Topology Service

WS API• Manages External WS

Communications

Resource Manager

• Manage Reservations• Auditing

Lookup• Lookup service

AuthZ*• Authorization• Costing

Web Browser User Interface

• Expect research projects may replace some modules– PCE– Path Setup

• Libraries provided by OSCARS– Currently only have Java– CXF based classes for message parsing– Threading of asynchronous requests– Business logic up to developer

• Still a work in progress

9 – 04/20/23, © 2009 Internet2

Developing New OSCARS Services

10 – 04/20/23, © 2009 Internet2

Sample Component Breakout

Authentication

Measurement Point

ServiceCoordinator

Metric Database

Measurement Archive

WS API• Manages External

Communication

Lookup Service Registration

Authorization

Tool BackendLookup Service

Backend

• Integration of Authentication/Authorization• Backward compatibility• Self-update functionality

11 – 04/20/23, © 2009 Internet2

Other Open Design Questions

Improving pS-PS Service Improving pS-PS Service ArchitectureArchitecture2010-01-31, perfSONAR-PS Developers MeetingAaron Brown, Andrew Lake, Eric Pouyoul

For more information, visit www.internet2.edu

12 – 04/20/23, © 2009 Internet2