October 2, 2001 Middleware: Pieces and Processes RL Bob Morgan, University of Washington.
description
Transcript of October 2, 2001 Middleware: Pieces and Processes RL Bob Morgan, University of Washington.
October 2, 2001
Middleware: Pieces and Processes
RL "Bob" Morgan, University of Washington
Topics
Internet2 Middleware InitiativeArchitecture and InfrastructureMACEMiddleware activitiesOutreach: Calling All Architects
Internet2 Middleware Initiative
April '99: time to move up the interop stack, start middleware program
I2-initiated, campus-driven"Institutional infrastructure architecture" ...
OK, let's call it "middleware"Intra-campus before Inter-campusStandardization before new development"Somebody should ..."; OK, let's!
Architecture + Infrastructure
Architecture: software modularity on a grand scale
Infrastructure: software architecture implemented as institutional services
Supporting transparent interconnection of resources (when authorized) and no connection (when not)
Infra/Architecture Example
Monolithic Portal user database, authentication scheme, calendar,
channels, legacy access, content management, "all in one seamless bundle"
an integration, support, infra problem
Infra/Arch-based Portal same components, but separable, so can work with
existing elements, support others as infra itself an integration asset, not a burden
Middleware Dichotomies
Infrastructure: concrete, service-orientedArchitecture: abstract, design-orientedDirectory: Finding stuffSecurity: Keeping stuff hiddenIntegration: App-specific functionsConsistency: Making all apps the same
A Map of Middleware
MACE
Steering committee for mware activitiesInitiate, review, track mware projectsEvangelize "architecture" issuesEstablish "shared state" on complex topicsCreate liaisons with European peers, "Grid"
workers, Educause, etc
MACE Members
Ken Klingenstein (Internet2, director) Steven Carmody (Brown), Michael Gettes
(Georgetown), Paul Hill (MIT), Jim Jokl (Virginia), RL "Bob" Morgan (Washington, chair), Mark Poepping (CMU), David Wasley (UCOP)
New members: Bruce Vincent (Stanford), Scott Cantor (Ohio State) (tentatively)
European liaisons: Brian Gilmore (Edinburgh), Ton Verschuren (SURFnet)
Grid liaison: Von Welch (Argonne/NCSA) Educause liaison: Steve Worona
I2-MI Process
Standardization, best practice, integrationIETF-inspired: open, solution-oriented,
energy-driven, self-organizingTechnical working groups with lists, phone
calls, home pages, documentsI2 supplies flywheel, scribing support
Capture that thought!
Directory activities
Directory service: the institutional PDAEduPerson schema: basic standardsHE Dir of Dirs: basic inter-campus
interop, scaling, policyDirectory challenges: privacy, data
ownership, app integration, semantics, multi-directory linkage, objects other than people, groups, ...
Security Activities
Focus: Authentication + AuthorizationHE PKI: establishing basic interop, basic
policy agreements, right "weight", working with US FPKI
Shibboleth: Inter-organizational web authentication and authorization
WebISO: Intra-campus web sign-on
Integration Activities
Video middleware: directory and A&A support for conferencing and streaming conferencing/presence attributes, endpoint
authentication, datastream protection, ITU standards, ...
MaceMed: middleware support for academic medical centers HIPAA, HIPAA, HIPAA
Outreach
Middleware courseware (I2MCP?)New: establishing I2 "IT architect" lists
for announcements and discussionNew: "Joint Architects" meeting (ala I2
Joint Techs) in early 2002TERENA "networks for collaboration"
Limerick, Ireland, June 2002 (www.terena.nl)
Futures
More Inter-campus infra experimentsAuthorizationWeb services, XMLContent control (aka Digital Rights Mgt)But mostly, more integrationAnd more campus participation!
NSF Middleware Initiative
NSF-funded program to establish standard environment for scientific computing
Internet2, Educause, SURA + GRIDSChallenge: linking campus-wide infra with
big-science-specific infraThe work begins now ...