COSMOS Architecture Meetings

Meeting Information

Meeting Title:	Conference Call on Overall COSMOS Architecture
Link to information on Wiki:	Architecture and design documents
Date & Time:	Febuary 6, 2008 at 10:00AM EST
Tie line:	8-421-0033
Toll-free Dial-in number:	+1 (877) 421 0033
Primary International Dial-in:	TBD
Passcode:	COSMOS (267667)#

i9 integration build: status report on our first targeted build (10 min)
QA Discussion carry over from Monday's summit COSMOS_QA_Criteria (50 min)
CMDBf Registration APIs
- http://wiki.eclipse.org/COSMOS_Design_214672
- http://wiki.eclipse.org/Talk:COSMOS_Design_214672
Should we use command line or web UI to manage COSMOS components? (e.g. register broker with management domain, etc.)
- Is the command line client a temporary solution?
- Bug 215502
Target environment for data managers in the demo:
- Should we package all 4 data managers for Tomcat in the demo for i9?
- We need to put together a deployment and dependency diagrams for i9
Eclipse version: 3.3.x vs. 3.4
- Eclipse 3.4 and the Ganymede simultaineous release will release in June.
- Web development for data visualization and data managers require WTP 3.0, which runs with eclipse 3.4.
- The build is currently using eclipse 3.3.
- Need to decide if we want to change development and build environment to eclipse 3.4.
Documentation plan Proposed Table of Contents

Review build wish list at http://wiki.eclipse.org/COSMOS_RE_AND_BUILD_WISH_LIST
Review "Scoping of the COSMOS Security Infrastructure" http://wiki.eclipse.org/COSMOS_Design_209337 and determine if any i9 ERs are needed as a consequence - Jimmy Mohsin (time permitting)
- Review the updated use cases
- Analyze the flow of a typical query and determine what security artifacts are contained in the payload
- Analyze the flow of a non-query "management-style" (e.g. shot down the broker) requests, assuming we even support these, and determine what security artifacts are contained in the payload