OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Assessment John Graybeal, Michael Meisinger Life Cycle Architecture Review La Jolla, CA

OOI CI LCA REVIEW August Overview Architecture Assessment Development Assessment Conclusions

OOI CI LCA REVIEW August Architectural Assessment Proof of Core Principles Messaging Service-Orientation Technology Independence and Interoperability (Python, Java) Proof of core architectural elements Capability container Scaling, available execution and deployment strategy Data publish/subscribe Science data representation in messages and storage Instrument management and agent interaction UI integration Confluence and Enterprise Architect Materials updated and baselined for LCA based on findings in elaboration Designer Process established

OOI CI LCA REVIEW August Proof of the Operational Architecture Iterative, Test-Driven Development Approach Functional testing Coverage of central use cases of the Product Description Comprehensive unit test suite: 340+ tests Automatic test every 30 min Deployment testing Automatic test in EC2 target deployment environment Test in embedded platform environment: TS-7370, OK Performance testing Scalability test: successful scaling to 200+ server nodes

OOI CI LCA REVIEW August Architectural Assessment: Issues No complete architectural coverage yet COI: Identity Management and Goverance CEI: Resource Management services DM: Some of preservation and presentation S&A: Instrument direct access and full instrument life cycle See Use Case and Service Emergent Risks Some technology choices still not final (see technology list) Gaps in the tracing from requirements to the architecture and use cases Limited resources in the architecture and SE teams Refinement of designer process needed to optimize input for developers

OOI CI LCA REVIEW August Development Assessment Use Cases accomplished for LCA: 12 out of 35 Live integrated demo CEI presented demo results Use Cases architecturally covered for LCA: 21 out of 35 Collected metrics about development performance used for construction planning Entrained development team in technologies, architecture vision and system integration Documented, refined and enacted central development processes Built out a core development infrastructure: automatic build, test, source code control

OOI CI LCA REVIEW August Development Achievements AMQP message broker installation Primary code base “LCAarch” across all subsystems More than 25K lines of code ~15 Developers across 6 teams Initial integration across all subsystems All core services defined; end-to-end scenarios exercised Initial Java technology capability container Presentation Platform: Web UI based on Java CC Interoperability with Java platform Deployment on EC2 (at scale) and in embedded platforms

OOI CI LCA REVIEW August Implementation Assessment: Issues No Substantial Use Case Coverage: 14 of 35 Staffing behind plans Required training for newer members of the development team in technologies and architecture as they join Refining the development processes

OOI CI LCA REVIEW August Conclusions Achieved Elaboration Goals Implementation of core elements of the architecture Integration across subsystems along scenarios Functional, deployment and scalability testing Construction Plan defined Work Ahead Switch to “Construction Mode” Qualify Construction Planning including system level Integration and Test/Validation activities Prepare for Release 2: Pick up descoped use cases after decision

OOI CI LCA REVIEW August Thanks ! Questions ?